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

1. Create a configuration input file. This file will contain the names of storage pairs and DR
groups. (A template of this file is available in /opt/cmcluster/toolkit/SGCAEVA/
mceva.conf). An example of the mceva.conf file is given in Appendix D: “mceva.conf file”
(page 87).
2. Copy the template file /opt/cmcluster/toolkit/SGCA EVA/mceva.conf to the /etc/
dtsconf directory.
# cp /opt/cmcluster/toolkit/SGCAEVA/mceva.conf
/etc/dtsconf/mceva.conf
3. For each pair of storage units, enter the WorldWideName (WWN). The WWN is available
on the front panel of the P6000/EVA controller or from the HP P6000 Command View user
interface.
4. For each pair of storage units, enter the names of all DR groups that are managed by that
storage pair.
5. Save the file.
Creating the Storage Map file
After completing the HP P6000/EVA Storages and DR Groups configuration file, use the EVA
discovery utility to create or modify the storage map file.
# evadiscovery -f /etc/dtsconf/mceva.conf
Verifying the storage systems and DR Groups .........
Generating the mapping data .........
Adding the mapping data to the file /etc/dtsconf/caeva.map .........
The mapping data is successfully generated.
The command generates the mapping data and stores it in /etc/dtsconf/caeva.map file.
The mapping file/etc/dtsconf/caeva.map contains information of the Management Servers
and information of the HP P6000/EVA storage cells and DR Groups.
Displaying information about storage devices
Use the evadiscovery command to display information about the storage systems and DR groups
in your configuration. For example:
# evadiscovery -l
% MC EVA Storage Systems and DR Groups map list:
Storage WWN: 5000-1FE1-5000-4280
DR Group Name: DR Group - PkgA
DR Group Name: DR Group - PkgB
Storage WWN: 5000-1FE5-5000-4288
DR Group Name: DR Group - PkgA
DR Group Name: DR Group - PkgB
NOTE: Run the discovery tool after all 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
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 /etc/dtsconf/
caeva.map to all Metrocluster clustered nodes.
Copying the Map file
After running the smispasswd and evadiscovery commands to generate the /etc/dtsconf/
caeva.map file, copy this file in the same location to all cluster nodes so that the map file can be
used by Metrocluster with Continuous Access EVA to communicate with the storage arrays.
20 Configuring an application in a Metrocluster environment