Veritas: Displaying the Status of VVR Links

The status of VVR links can be displayed by running the folloing commands, as root, on the appropriate host.

• Log in to the primary host of the relevant VVR link and su to root
• To view the status of the link, run the command

 # /usr/sbin/vxrlink -g disk-group-name status rlink-name

• Or the following command to update every 5 seconds

 # /usr/sbin/vrlink -g disk-group-name -i 5 status rlink-name

• Another option to show link status is to use the following vradmin command. This command displays more information than the previous one, including SRL size, current mode, and the amount of time (if any) that replication is behind.

 # /usr/sbin/vradmin -g disk-group-name repstatus rvg-name

• To view the amount of traffic being sent over the network for a VVR Link, run the following command, notice how I use the option "stats" instead of "status" here.

 # /usr/sbin/vrlink -g disk-group-name -i 5 stats rlink-name

 

veritas: Veritas Volume Replicator (VVR) Commands

Here are some links to Basic Veritas Volume Replicator (VVR) commands for your data replication management environments.

Basic VVR Commands:

veritas: rlinks in 'paused due to network disconnection' state

Had a case open with Symantec with the following issue.

 # vradmin -g dgprdap2 repstatus rvg_prdap2
 Replicated Data Set: rvg_prdap2
 Primary:
   Host name:                  10.150.150.13
   RVG name:                   rvg_prdap2
   DG name:                    dgprdap2
   RVG state:                  enabled for I/O
   Data volumes:               1
   VSets:                      0
   SRL name:                   srl_prdap2
   SRL size:                   25.00 G
   Total secondaries:          1

 Secondary:
   Host name:                  10.150.150.16
   RVG name:                   rvg_prdap2
   DG name:                    dgprdap2
   Data status:                consistent, behind
   Replication status:         paused due to network disconnection
   Current mode:               asynchronous
   Logging to:                 SRL (213278 Kbytes behind, 0% full)
   Timestamp Information:      behind by 2668h 22m 7s

 'vradmin repstatus' shows rlinks in 'paused due to network disconnection' state

Various attempts where made to try continue/attach or resume the replication but failed.  

The following checks must be made to diagnose the problem.

Run the vrport command on both the primary and secondary nodes.

# /usr/sbin/vrport

Check communication on these ports, from primary to secondary and vice versa on each node: 

# ping -p port-number host-name

If the ping command succeeds, try restarting the VVR daemons (both on primary and secondary) in the correct sequence: 

 

Stop vradmin on secondary then on primary

# /usr/sbin/vxstart_vvr stop

Start vradmin on secondary then on primary

# /usr/sbin/vxstart_vvr start 

If for any unknown reason the above does not fix the issue you might need to try to restart the primary and secondary nodes. But if you encounter that a bounce does not fix issue it's a rare possibility that you might need to re-create the rvg's as it was in my case. Another unsolved VVR mystery. 

veritas: Displaying and changing the ports used by VVR

Use the vrport command to display, change or set the port numbers used by VVR. You may have to change the port numbers in the following cases:

• To resolve a port number conflict with other applications.
• To configure VVR to work in your firewall environment.
• To configure VVR to work in your firewall environment when using UDP; to specify a restricted number of ports to replicate data between the Primary and the Secondary.

Port Used For Heartbeats

Use the vrport heartbeat command to display the port number used by VVR, for heartbeats. To change the heartbeat port number on a host, specify the port number with the vrport heartbeat command.
Use the vradmin changeip command to update the RLINKs with the new port information, and then restart the vxnetd daemon on the required system for the changes to take effect.
To display the port number used for heartbeats

 # vrport heartbeat

To change the port number used for heartbeats

 # vrport heartbeat port

This example shows how to change the replication heartbeat port on the host1. Follow the same steps to change the heartbeat port on secondary (host2).

Note:

VVR supports a configuration with different heartbeat port numbers on the primary and secondary.

To change the replication heartbeat port on host1 from 4145 to 5000

 1.  Use the vrport command to change the heartbeat port to 5000 on the required host.

 # vrport heartbeat 5000

 2. Issue the vradmin changeip command without the newpri and newsec attributes.

 # vradmin -g hrdg changeip hr_rvg host2

 3. Verify the changes to the local RLINK by issuing the following command on the required host:

 # vxprint -g hrdg -l rlk_host2_hr_rvg

4. Stop the vxnetd daemon.

 # /usr/sbin/vxnetd stop

 5. Restart the vxnetd daemon.

 # /usr/sbin/vxnetd

Port Used By vramind

To display the port number used by vradmind, use the vrport vradmind command. To change the vradmind port, specify the port number with the vrport vradmind command.
To display the port number used by vradmind

 # vrport vradmind

To change the port number used by vradmind

 # vrport vradmind port

Note:

You must restart the server vradmind for this change to take effect. Make sure you change the port number on all the hosts in the RDS.

Port Used by in.vxrysyncd

To display the port numbers used by in.vxrsyncd, use the vrport vxrsyncd command. To change the port numbers used by in.vxrsyncd, specify the port number with the vrport vxrsyncd command.
To display the port number used by in.vxrsyncd

 # vrport vxrsyncd

To change the port number used by in.vxrsyncd

 # vrport vxrsyncd port

Note:

You must restart the server in.vxrsyncd for this change to take effect. Make sure you change the port number on all the hosts in the RDS.

Ports Used To Replicate Date Using UDP

To display the ports used to replicate data when using UDP, use the vrport data command. To change the ports used to replicate data when using UDP, specify the list of port numbers to use with the vrport data command.

Each RLINK requires one UDP port for replication. Specify an unused, reserved port number that is less than 32768 so that there is no port conflict with other applications. The number of ports specified must be equal to or greater than the number of RLINKs on the system.

Note:

For systems using the TCP protocol for replication, you are not required to select any data port as the connection is established with the listener port on the remote host. The listener uses this port number which is numerically same as the UDP port used for heartbeat messages.

To display ports used to replicate data when using UDP

 # vrport data

To change ports used to replicate data when using UDP

For a system configured with one RLINK, use the following command:

 # vrport data port

For a system configured with multiple RLINKs, you can specify either a range of port numbers or a list of port numbers or both.

To specify a range of port numbers, use the following command:

 # vrport data port1, port2, portlow-porthigh, .... 

For example:

 # vrport data 3400, 3405, 3500-3503, 5756-5760

Note:

To use the new port information, execute /usr/sbin/vxnetd, and then pause and resume all RLINKs.