Designing Disaster Tolerant High Availability Clusters, 10th Edition, March 2003 (B7660-90013)

Building a Metropolitan Cluster Using MetroCluster/CA
Maintaining a Cluster that uses MetroCluster/CA
Chapter 3 111
Maintaining a Cluster that uses
MetroCluster/CA
While the cluster is running, manual changes of state for devices on the
XP Series disk array can cause the package to halt due to unexpected
conditions or can cause the package to not start up after a failover. In
general, it is recommended that no manual changes of state be
performed while the package and the cluster are running.
NOTE Manual changes can be made when they are required to bring the device
group into a “protected” state. For example, if a package starts up with
data replication suspended, a user can perform a pairresync command
to re-establish data replication while the package is still running.
Viewing the Progress of Copy Operations
While a copy is in progress between XP systems (that is, the volumes are
in a COPY state), you can see the progress of the copy by viewing the %
column in the output of the pairdisplay command:
# pairdisplay -g pkgB -fc -CLI
Group PairVol L/R Port# TID LU Seq# LDEV# P/S Status Fence
% P-LDEV# M
pkgB pkgD-disk0 L CL1-C 0 3 35422 463 P-VOL COPY
NEVER 79 460 -
pkgB pkgD-disk0 R CL1-F 0 3 35663 3 S-VOL COPY
NEVER - 0 -
This display shows that 79% of a current copy operation has completed.
Synchronous fence levels (NEVER and DATA) show 100% in this column
when the volumes are in a PAIR state.
Viewing Side File Size
If you are using asynchronous data replication, you can see the current
size of the side file when the volumes are in a PAIR state by using the
pairdisplay command. The following output, obtained during normal