HP P9000 Replication Manager Software 7.4.0-00 Configuration Guide (TB584-96058, December 2012)

Recognition of the replication configuration
Make sure that Device Manager server correctly recognizes the replication configuration that is
managed by a host or pair management server.
NOTE:
On copy pairs that configure remote copies, you do not need to check this item.
Check the following:
• On the host (pair management server) properties window, make sure that you can click the button
to view the pair information managed by the host.
• On the window displayed by clicking the button to view the pair information, make sure that ex-
isting copy group names and copy pair names are displayed.
If the button is not activated or the information is not displayed, refresh the storage system information.
If it cannot be updated, make sure that the system configuration and specified settings in the P9000
RAID Manager configuration definition file are correct.
Recognition of storage systems
To ensure that Device Manager server correctly recognizes storage systems that comprise existing
copy pairs, confirm that each storage system appears in the list of storage systems. If not, register the
storage system with the Device Manager server.
Items to be checked from the GUI
In the copy pair configuration definition view, select the pair management server that manages the
existing copy pairs to make sure that information about these items are correct:
• The configuration definition file for P9000 RAID Manager that exists on the pair management
server
• Copy groups that are defined in the P9000 RAID Manager configuration definition file
• Copy pairs that configure copy groups.
If the above items are not displayed correctly, refresh the configuration information for Device Manager
server. For details, see the HP P9000 Replication Manager Software User Guide.
Troubleshooting replica operations
This section covers error conditions and log events that may occur and how to address them:
• Replica creation fails silently, page 133
• Backup server is not recognized as a pair management server, page 133
• Restoring a replica with roll-forward fails with error message RPM-11510, page 133
• Restoring a replica fails with event ID 454, page 134
• Creating a replica fails with error message RPM-10006, page 134
• Creating a replica fails with event IDs 17, 1 and 10010, page 134
• Disk status remains online after replica operation is complete, page 134
Troubleshooting132