Building Disaster Recovery Serviceguard Solutions Using Metrocluster with Continuous Access EVA P6000 for Linux B.12.00.00

NOTE: Run the evadiscovery tool after all the storage DR Groups are configured or when
there is any change to the storage device. For example, the user removes and recreates a DR
group that is used by an application package. In this case the DR Group's internal IDs are
regenerated by the P6000/EVA system. If any name of storage systems or DR groups is changed,
update the external configuration file, run the evadiscovery utility, and redistribute the map file
caeva.map to all Metrocluster clustered nodes.
Starting from release B.12.00.00 and B.01.00.02 (B.01.00.00 + SGLX_00461-463) onwards,
for all changes including addition or removal of a disk, update the external configuration file, run
the evadiscovery utility, and redistribute the map file caeva.map to all Metrocluster clustered
nodes.
Before running the evadiscovery command, the management server configuration must be
completed using the smispasswd command, else the evadiscovery command fails.
Copying the Map file
After running the smispasswd and evadiscovery commands to generate the caeva.map file,
copy this file in the same location to all cluster nodes so that the map file can be used by this
product to communicate with the storage arrays.
Copy the caeva.map file to all nodes in the cluster.
# scp $SGCONF/mccaeva/caeva.map node:$SGCONF/mccaeva/caeva.map
Similarly, whenever new Management Servers are added or the existing Server credentials are
changed, generate and redistribute the map file to all Metrocluster clustered nodes.
Configuring volume groups
This section describes the required steps to create a volume group for use in a Metrocluster
environment.
To configure volume groups, you must first identify the device special files for the source and target
VDisks in the DR Group. After that, create volume groups for source volumes, export them for
access by other nodes and import them on all other cluster nodes.
Identify the device special files for Vdisk in DR group
To configure volume groups, you must get the device special files for the DR Group's source and
target VDisks on nodes in both the sites.
See the “ Identifying the devices to be used with packages” (page 44) for identifying device
filenames for Vdisks.
NOTE: While using Cluster Device Special Files (cDSF) feature, the device special file name is
same on all nodes for a source and target VDisk.
Identifying special device files
The following is the sample output of the evainfo command on Linux environment.
Table 3 evainfo command output
# evainfo —d /dev/sdj
Controller/Port/ModeCapacityWWNNArrayDevicefile
Ctl-B/FP–4/NonOptimized1024MB6005-08B4-0010-78F1-0002-4000-0143-00005000-1FE1-5007-DBA0/dev/sdj
For more information on using the evainfo tool, see HP P6000 Evainfo Release Notes.
Use HP P6000 Command View to identify the WWN for a Vdisk. The HP P6000 Command View
for the WWN Identifier of the Vdisk is shown in Figure 3.
18 Configuring an application in a Metrocluster environment