HP P9000 Replication Manager Software 7.3.1-00 Configuration Guide

This example shows how to execute the hcmdsdbclustersetup command:
"C:\Program Files\CVXPAE\Base\bin\hcmdsdbclustersetup" /createcluster /
databasepath R:\re_creating_db /exportpath C:\storing_data /auto
Troubleshooting when copy pairs are not recognized
In an environment where Device Manager and P9000 RAID Manager manage copy pairs, if
information about the existing copy pairs cannot be recognized after refreshing the configuration
information, take the following actions to correct the problem:
1. Go to Items to be checked on the pair management server on page 123, to make sure that the
configuration definition files for Device Manager Agent and P9000 RAID Manager are correct.
2. Go to Items to be checked from Device Manager GUI on page 125, to make sure that information
about hosts or pair management servers that are managed by Device Manager server is correct.
3. Go to Items to be checked from the GUI on page 126, to make sure that information about hosts
that are managed by the Replication Manager server is correct.
NOTE:
If you are using Device Manager with the Core CLI/SMI-S License, see Appendix E and then use
Device Manager CLI to check the information about hosts (pair management servers) that are managed
by Device Manager server.
Items to be checked on the pair management server
This section describes how to make sure that the settings in the configuration definition files for Device
Manager Agent and P9000 RAID Manager are correct:
1. Installation of Device Manager Agent, page 124
2. Link between Device Manager server and Device Manager Agent, page 124
3. Properties of Device Manager Agent, page 125
4. Settings in the P9000 RAID Manager configuration definition file, page 125
For details about commands to be executed on the pair management server, how to operate Device
Manager Agent, and how to specify configuration definition files that are supported by Device
Manager, see the HP P9000 Command View Advanced Edition Suite Software Administrator Guide.
NOTE:
When using Device Manager Agent on VMware 4.x, it is necessary to confirm the prerequisite
combination of Device manager server and Device Manager Agent. Even if you use Device Manager
and the Device Manager Agent for which the prior prerequisite combination has been confirmed,
the following precaution must be noted:
If the target volume is set as a command device on the virtual machine, by using Add CMD
Devices, the virtualization server needs to be restarted in order to recognize the set command
device.
Configuration Guide 123