Using the vxprint Display Commands

This section describes the VVR commands that you can use to view the status of the objects that take part in replication.

Displaying a Specific RLINK

Use the vxprint -Pl command to display detailed information about the status of an RLINK. This command prints one record per RLINK. The following table lists the information displayed in the output.

To display detailed information about a specific RLINK:

# vxprint -g diskgroup -Pl rlink_name

Disk Group	Name of the disk group.
RLINK Name	Name of the RLINK.
Info	timeout, packet_size, record_id, latency high, low marks and bandwidth_limit.
State	Displays utility state of the RLINK - ACTIVE, STALE, etc.
synchronous, latencyprot, and srlprot	The current configuration settings for the replication mode, the latency mode, and SRL protection.
assoc	The RVG to which the RLINK is associated.
remote_host/IP_addr/port	The name of the remote host for the RLINK, its IP address, and the port number.
remote_dg	The name of the disk group on the remote system.
remote_dg_dgid	The disk group ID assigned when the disk group was created on the remote system.
remote_rvg_version	The rvg_version of the remote RVG.
remote_rlink	The name of the corresponding RLINK on the remote host.
remote_rlink_rid	The record_id of the corresponding RLINK on the remote host.
local_host/IP_addr/port	The name of the local host, its IP address, and the port number it uses for communication to the remote host.
protocol	The transport protocol used by the RLINK for communicating between the hosts. The protocol can be either UDP/IP or TCP/IP.
checkpoint	Displays the checkpoint only if the Primary RLINK is attached using the checkpoint or the Secondary RLINK has been restored using the checkpoint.
flags	See Interpreting RLINK Flag Settings.

Note To display all the RLINK names in a single column, issue the following command:
# vxrvg -g diskgroup [-1] getrlinks rvg_name

Interpreting RLINK Flag Settings

The following table lists the various flags that can appear in the flags field of the vxprint -Pl output.

Note The Primary and Secondary RLINKs are communicating only when the connected flag is on. However, replication is taking place only if the following set of flags is displayed:
write enabled attached consistent connected
In all other cases, a corrective action may be needed.

autosync	The RDS is in the process of automatic synchronization.
attached	The RLINK is attached to the RVG.
can_sync	If the inconsistent and can_sync flags are set, there is enough information in the Secondary SRL volume to make the Secondary consistent again and capable of taking over.
cant_sync	The RLINK is inconsistent, and this Secondary needs a complete resynchronization before it can take over or replicate.
connected	The RLINK is connected to the corresponding RLINK on the remote host and replication can take place.
consistent	The state of the data volumes on the Secondary is suitable for takeover.
dcm_logging	DCM is in use, due to either autosync, failback sync, or an SRL overflow.
detached	The RLINK is STALE and not taking part in replication.
disabled	The RLINK is not attached and is not replicating.
disconnected	The two RLINKs are not connected and are not replicating.
enabled	The RLINK is attached. If the connected flag is displayed, replication can take place. If the disconnected flag is displayed, replication is not taking place.
fail	An I/O error occurred while writing to a data volume on the Secondary.
inconsistent	The data in the Secondary volumes is not consistent and the Secondary cannot take over.
needs_recovery	State after an import or reboot. The vxrecover command clears this state.
primary_paused	The Primary RLINK has been paused and the RLINKs are not replicating.
resync_started	The resynchronization of the Secondary has been started.
resync_paused	The resynchronization has been started but is not currently active because of some problem.
secondary_config_err	There is a mismatch between the configuration of the volumes on the Primary and the Secondary - either a volume is missing on the Secondary or its length is not the same as that of the corresponding volume on the Primary.
secondary_log_err	An I/O error has occurred on the Secondary SRL; replication cannot continue until the SRL has been dissociated and a new one associated.
secondary_paused	The Secondary RLINK has been paused and the RLINKs are not replicating.

Displaying an Individual RVG

The vxprint -Vl command displays detailed information about the status of an individual RVG. This command is useful to determine the role of the Primary or Secondary RVG and the state of the RVG as seen by the operating system.

To display detailed information about an RVG:

# vxprint -g diskgroup -Vl rvg_name

The following table lists the output of the vxprint -Vl command.

Disk Group	Name of the disk group in which this RVG resides.
RVG	Name of the RVG.
info	Displays the last_tag, record_id, configuration version, and the version of the RVG.
state	The current utility and kernel states.
assoc	Data volumes, SRL, and RLINKs associated with the RVG.
att	The RLINKs that are attached. A Primary can have multiple associated, attached RLINKs. A Secondary can have multiple associated RLINKs, but only one attached RLINK.
flags	See Interpreting RVG Flag Settings

Interpreting RVG Flag Settings

open	This flag is always set on the Secondary when it is waiting to receive an IBC from the Primary.
closed	This flag is always set.
primary/secondary	Indicates the role of the RVG.
enabled/attached	I/O and IOCTLs can be performed.
disabled/detached	I/O and IOCTLs cannot be performed.

Displaying an Individual Data Volume

Use the vxprint -l volume_name command to display information about a specific data volume. The output fields of special interest for VVR are shown in the next table.

assoc	Shows the RVG to which this data volume is associated (rvg=).
logging	Shows the logging type, which should always be DCM for a data volume.

Note To list all data volumes in an RVG in a single column, issue the following command:
# vxrvg -g diskgroup [-1] getdatavols rvg_name

Displaying the Status of a Secondary

Use the vxrlink status command to determine the status of a Secondary. This command displays different information depending on what state the replication is in for that Secondary. For example, whether the Primary is currently replicating to the Secondary, synchronizing the Secondary with a checkpoint, using the DCM to resynchronize the Secondary, or using automatic synchronization for the Secondary. To determine the state of the replication, see Displaying Consolidated Replication Status.

If the state is replicating, the vxrlink status command displays whether the Secondary corresponding to the specified RLINK is up-to-date and if not, how much the Secondary is behind.

Note that outstanding writes are shown even if the Secondary is replicating in synchronous mode. Although for synchronous mode, the write is considered complete to the application when the network acknowledgement is received from the Secondary, VVR still considers the write outstanding until it is written to the data volume on the Secondary.

If automatic synchronization or DCM resynchronization is in progress, the vxrlink status command shows the progress of the automatic synchronization.

To show the status of a Secondary

# vxrlink -g diskgroup status rlink_name

If replication is in progress, the output resembles:

VxVM VVR vxrlink INFO V-5-1-4640 Rlink rlink_name has <x> outstanding writes, occupying <y> Kbytes (17%) on the SRL

If automatic synchronization is in progress, the output resembles:

VxVM VVR vxrlink INFO V-5-1-4464 Rlink rlink_name is in AUTOSYNC. 100864 Kbytes remaining.

If DCM resynchronization is in progress, the output resembles:

VxVM VVR vxrlink INFO V-5-1-4348 DCM is in use on Rlink rlink_name. DCM contains 88832 Kbytes.

To display the Secondary status periodically, specify a time interval using the -i option. For example, to print the status of the Secondary every five seconds, use the command:

# vxrlink -g diskgroup -i5 status rlink_name

If replication is in progress, the output resembles:

VxVM VVR vxrlink INFO V-5-1-4640 Rlink rlink_name has <x> outstanding writes, occupying <y> Kbytes (17%) on the SRL
VxVM VVR vxrlink INFO V-5-1-4640 Rlink rlink_name has <x> outstanding writes, occupying <y> Kbytes (19%) on the SRL

If automatic synchronization is in progress, the output resembles:

VxVM VVR vxrlink INFO V-5-1-4464 Rlink rlink_name is in AUTOSYNC. 100864 Kbytes remaining.
VxVM VVR vxrlink INFO V-5-1-4464 Rlink rlink_name is in AUTOSYNC. 94464 Kbytes remaining.

To display the status of an RLINK with a timestamp, use the vxrlink status command with the -T option. This is useful if the Secondary is not up-to-date. The output of the command displays a timestamp in the locale's appropriate time format to indicate the time by which the Secondary is behind.

For example, if there are pending writes in the Primary SRL, use the following command to check the status of the Primary:

# vxrlink -g diskgroup -T status rlink_name

The output resembles:

VxVM VVR vxrlink INFO V-5-1-4640 Rlink rlink_name has <x> outstanding writes, occupying <y> Kbytes (20%) on the SRL
VxVM VVR vxrlink INFO V-5-1-0 Rlink rlink_name is behind by 0:00:40 hours

The second message indicates the time by which the RLINK is behind.

Note If the system time is reset to a value different from that of the current system time, then, the output of the vxrlink -T status command will appropriately show a negative or an inaccurate value, until the updates that were done before resetting the system time get replicated.

Displaying a List of Checkpoints

VVR enables you to get a list of the Primary checkpoints using the vxrvg cplist command; the vxrlink cplist command enables you to get a list of the Secondary checkpoints. The vxrvg cplist and vxrlink cplist commands can be run on the Primary only. VVR supports a maximum of 46 checkpoints, and hence the list displays a maximum of 46 checkpoints. If you try to create more than the specified number of checkpoints, an error message prompts you to delete older checkpoints before creating new checkpoints.

Primary checkpoints are created using the vxrvg -c checkpoint_name checkstart command on the Primary and are associated with an RVG. Issue the vxrvg cplist command to display a list of the existing Primary checkpoints associated with the specified RVG. The Primary checkpoints can be deleted using the
vxrvg -c checkpoint_name checkdelete rvg_name command.

Secondary checkpoints are created using the vxrlink -c checkpoint_name pause command on the Secondary and are associated with the RLINK. Issue the vxrlink cplist command on the Primary to display a list of the existing Secondary checkpoints associated with the specified RLINK. The Secondary checkpoint can be deleted by using the vxrlink -c checkpoint_name checkdelete rlink_name command.

Note The vxrlink cplist command and the vxrlink checkdelete command must be run on the Primary only.

The displayed information includes details about each checkpoint, such as checkpoint name, size, percentage of SRL used, and whether the checkpoint has been started or completed. If the SRL usage reaches 100%, the checkpoint overflows and becomes unusable. In this case, VVR displays the message Checkpoint overflowed.

To display a list of Primary checkpoints, enter the following command on the Primary:

# vxrvg -g diskgroup cplist rvg_name

To display a list of Secondary checkpoints, enter the following command on the Primary:

# vxrlink -g diskgroup cplist rlink_name

where rlink_name is the name of the Primary RLINK that connects to the Secondary where the vxrlink -c checkpoint_name pause was issued. The output resembles:

Name MBytes % Log Started/Completed
---- ------ ------ -----------------
a8 200 5 Completed
a9 800 20 Completed
a6 2000 40 Started


^ Return to Top	< Previous \| Next >

Product: Volume Replicator Guides
Manual: Volume Replicator 4.1 Administrator's Guide
VERITAS Software Corporation www.veritas.com