Building Disaster Recovery Serviceguard Solutions Using Metrocluster with Continuous Access EVA A.05.01

regularly. For more information about setting the cron job, see Setting up Periodic Cluster Verification
section in the latest version of the Managing Serviceguard manual available at http://www.hp.com/
go/hpux-serviceguard-docs —> HP Serviceguard.
“Validating Metrocluster Package” (page 50) lists the checks made on a Metrocluster Package.
Table 5 Validating Metrocluster Package
RemarkCommandValidations/Checks
For Metrocluster with Continuous Access
EVA, it checks whether the HP P6000
cmcheckconf [–v]
cmapplyconf
Check whether the Array Management
Software is available.
Command View server is accessible
from the nodes.
cmcheckconf [-P/-p]
cmcheckconf [-v]Check whether the contents in the
environment file matches with the
contents in the package present in the
CDB.
Checks the package configuration file
that is passed as an argument for the
cmcheckconf [–v]
cmapplyconf
Check all attributes in the Metrocluster
module.
cmcheckconf [-P/-p] command.
cmcheckconf [-P/-p]
For cmcheckconf, it checks the
Metrocluster environment file that is
available in the Metrocluster package
directory.
Warns you if the disks belonging to a
volume group or a diskgroup are not
cmcheckconf [–v]
cmapplyconf
Verify if the disks belonging to a
volume group or a disk group are
being replicated. ** being replicated. It reports an error if
cmcheckconf [-P/-p]
the disks belong to a different
replication group than what is
mentioned in the environment file or the
package configuration file.
When Metrocluster is integrated with
Site Controller, this check is done only
when the cmcheckconf [-v]
command is executed. During
validation, it creates a list of volume
groups and diskgroups for all the
packages controlled by Site Controller
and performs the check.
Restrictions
Cannot confirm whether the disks are
being replicated in case they are being
used as raw disks or in case they
belong to an Oracle ASM diskgroup.
Skips this check on VxVM diskgroups
if the naming convention used by VxVM
is legacy and if the controller ID is
greater than 512 (This happens when
VxVM uses an internal format to
recognize devices that do not support
legacy dsf format). In such cases, HP
recommends that you change the
naming scheme using the vxddladm
command so that VxVM output shows
the disk names in a persistent dsf
format.
Table 6 (page 51) lists additional checks made on the Site Controller packages.
50 Additional Metrocluster features