• Unable to add or edit HP P6000 Storage Replication Group
Possible causes include:
◦ Matrix recovery management is unable to obtain Storage Replication Group information
from Command View servers to validate the Storage Replication Group information
provided by the user.
• Unable to add or edit HP P9000 Storage Replication Group
Possible causes include:
◦ The Storage Replication Group is not configured to be managed by the RAID manager
instances.
◦ The RAID manager service is not running on the local Storage Management Server.
◦ The parameters entered for the Storage Replication Group (local array, remote array,
serial number, and replication mode) do not match the Storage Replication Group
information on the disk array.
• Unable to add or modify HP 3PAR Storage Management Server
Possible causes include:
◦ The password file for the HP 3PAR storage system is missing from the /storage/3par/
conf directory where Matrix recovery management is installed.
◦ The password for the HP 3PAR storage system has been changed since the password file
was created.
• Unable to add or edit HP 3PAR Storage Replication Group
Possible causes include:
◦ The Storage Replication Group is not configured to be managed by HP 3PAR remote
copy.
◦ The following information entered for the Storage Replication Group cannot be validated
with the HP 3PAR storage system configuration:
– Volume group name on the local HP 3PAR storage system
– Volume group name on the remote HP 3PAR storage system
– Local array remote copy group name
– Remote array remote copy group name
– Local HP 3PAR storage system serial number
– Remote HP 3PAR storage system serial number
– Replication mode
• Matrix recovery management logical server configuration is inconsistent with Matrix OE
logical server management logical server configuration
Possible causes include:
◦ The HP Logical Server Automation service was not running when Recovery Groups were
configured in Matrix recovery management.
◦ The logical server was being actively managed when the Matrix recovery management
configuration was invoked (logical server modification, logical server activation, or logical
server deactivation was in progress).
52 Troubleshooting
