User's Guide

# rcp <package_directory>/<Metrocluster_environment_file>
<new_node_name>:<package_directory>
6. If you are using Metrocluster modular package and if the node names are explicitly specified
for node_name parameter in Metrocluster package configuration, then add the newly added
node in a Metrocluster package by editing the Metrocluster package configuration and
applying the configuration:
# cmapplyconf –P <package_config_file>
Completing and Running a Metrocluster Solution with Continuous Access
P9000 or XP
No additional steps are required after cluster and package configuration to complete the setup of
the metropolitan cluster. In normal operation, the metropolitan cluster with Continuous Access
P9000 or XP starts like any other cluster, and runs and halts packages in the same way as a
standard cluster. However, startup time for packages may be considerably slower because of the
need to check disk status on both disk arrays.
Maintaining a Cluster that uses Metrocluster with Continuous Access for P9000 and
XP
While the cluster is running, performing manual “changes of state” for devices on the P9000 or
XP Series disk array can cause the package to halt. This is due to unexpected conditions and can
cause the package not to 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 P9000 or XP arrays (that is, the volumes are in a COPY state),
the progress of the copy can be viewed by monitoring 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 cluster operation, shows the percentage of the side file that is full:
# 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 PAIR ASYNC 35 3 -
pkgB pkgD-disk0 R CL1-F 0 3 35663 3 S-VOL PAIR ASYNC 0 463 -
This output shows that 35% of the side file is full.
When volumes are in a COPY state, the % column shows the progress of the copying between the
P9000 or XP frames, until it reaches 100%, at which point the display reverts to showing the side
file usage in the PAIR state.
192 Building Disaster Recovery Serviceguard Solutions Using Metrocluster with Continuous Access for P9000 and XP