This section details the steps to follow if an error occurs when protecting volumes with high availability. To identify the cause of the error, review the error reports and messages, then take the necessary actions.
A possible cause of failure is when Ops Center Administrator references incorrect storage system configurations. This might occur when configuration changes are made from other management tools after the last refresh. To identify and resolve this issue, perform the following steps:
After following these steps, if the issue still persists, contact customer support.
To resolve issues with Create, Attach and Protect Volumes with High Availability or Protect Volumes with High Availability:
- Go to Job Details of the failed job.
- Check the corresponding sub-job title.
If the sub-job title matches either of the following descriptions, proceed to the next step.
- sub-job title on creating a new replication group: "Create replication group replication-group-name with HA on storage system storage-system-id."
- sub-job title on using an existing replication group: "Add volumes to replication group replication-group-name on storage system storage-system-id."
If the title does not match, check error reports and messages associated with the failed sub-job to determine the cause, then take appropriate actions to resolve the issue.
- From Job Details of the failed sub-job, check error reports and messages. If any message matches the following descriptions, proceed to the next step:
- Report message on creating a new Replication Group: "Failed to create a replication pair from replication group replicationGroupName for Storage System storageSystemId by Ops Center Protector. One possible cause of failure is when Ops Center Administrator references incorrect storage system configurations which may occur when configuration changes are made from other management tools after the last refresh. To identify and resolve the cause of this issue, refer to "Troubleshooting remote replication groups" in the User Guide."
- Report message on using an existing Replication Group: "Failed to add pairs to a replication related to replication group replicationGroupName for Storage System storageSystemId by Ops Center Protector. One possible cause of failure is when Ops Center Administrator references incorrect storage system configurations which may occur when configuration changes are made from other management tools after the last refresh. To identify and resolve the cause of this issue, refer to "Troubleshooting remote replication groups" in the User Guide."
If the messages do not match, check the sub-job error reports and messages for potential causes and take appropriate actions to resolve them.
- Launch Ops Center Protector and verify the cause of the job failure as follows:
If the expected log message is found as described in these steps, it indicates that Ops Center Administrator referenced an incorrect storage system configuration. Proceed to the next step.
If the expected log message is not found, it suggests that the cause might be different. Contact customer support.
- In the Actioned For Node field, enter the name of the failed replication group, and search for the failed job. If multiple jobs are found, identify the job with the latest timestamp that has a summary matching "Initialize Storage Replicate to Block Device."
- Go to Job Details and check for log messages with either of the following phrases:
- "Volumes do not have unique and consistent LUN IDs for operation configured to enforce this."
- "Could not reserve LUN IDs for operation."
- In the Actioned For Node field, enter the name of the failed replication group, and search for the failed job. If multiple jobs are found, identify the job with the latest timestamp that has a summary matching "Initialize Storage Replicate to Block Device."
- Remove or recover settings of related resources in Ops Center Protector as follows:
- For creating a new Replication Group: Remove Block Host Node, Policy, and Data Flow that have the same name as the failed Replication Group.
- For using an existing Replication Group: Remove the added P-Vol from the Block Host Node. To edit a Block Host Node created by Ops Center Administrator in Ops Center Protector, specify LDEV IDs in decimal format per line and avoid using hex format or range format.
- Confirm that the same LUN intended for the new high availability pair is not already assigned to any of the servers to which you plan to attach the pair. If the LUN is already assigned, use a different LUN or change the existing LUN assigned to the servers:
- Apply a filter to display volumes associated with the LUN and verify that volumes don't appear in the filter results.
- Apply a filter to display volumes associated with the LUN and verify that volumes don't appear in the filter results.
- If you plan to use an existing replication group, confirm that the same LUN intended for the new high availability pair is not assigned to any of the existing high availability pairs of the replication group. If the LUN is already assigned, use a different LUN:
- Click a P-VOL ID or a S-VOL ID to go to Volume Details.
- Check to see if the LUN associated to the P-VOL or S-VOL differs from the LUN intended for the new high availability pair.
- Click a P-VOL ID or a S-VOL ID to go to Volume Details.