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

NOTE: The desired location is where you have placed the modified mceva.conf file.
The command generates the mapping data and stores it in caeva.map file.
The mapping file 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 System and DR Groups map list:
Storage WWN: 50001FE15007DBA0
DR Group Name: \Data Replication\drg_cc
DR Group Name: \Data Replication\drg_1
Storage WWN: 50001FE15007DBD0
DR Group Name: \Data Replication\drg_cc
DR Group Name: \Data Replication\drg_1
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.
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 43) for identifying device
filenames for Vdisks.
Configuring volume groups 17