Article Number: 000130712
Alert ID | POLICY_SESSION_CREATE_FROM_VOLUME_GROUP_FAILED POLICY_SESSION_CREATE_FROM_VOLUME_FAILED |
Alert Text | Automatic replication session creation from %(source_name) to %(remote_system_name) failed with error: %(error_message_key) |
Error Code | (0x00901001) (0x00900301) |
Description | A protection policy with a replication rule was applied to a storage resource, but the subsequent creation of the replication session failed. There could be one or more causes for this alert, depending on the error message displayed. |
Resolution 1 | Destination system down: Cause The destination system may not be reachable for replication to proceed. Solution Ensure the destination system is accessible from the source system's network. A "Verify and Update" request may be issued from the source for the remote system to check connectivity. |
Resolution 2 | Name conflict on destination: Cause The destination system already contains a user-created volume or volume group with the same name as the source. During replication configuration, a volume is attempted to be created on the destination system with the same name as the source resource. If that volume can't be created on the destination system because it already exists then replication will be unable to proceed. Solution Rename the destination resource to avoid the name collision. Replication will proceed within the next Recovery Point Objective (RPO) period. |
Resolution 3 | Destination out of space: Cause The destination system may have run out of available storage space to receive replicated data. Solution Free storage space on the destination system. |
Alert ID | POLICY_SESSION_CREATE_FROM_REPLICATION_GROUP_FAILED |
Alert Text | Unable to create a replication session from %(source_name) to %(remote_system_name) due to error: %(error_message_key) |
Error Code | 0x00901601 |
Impact | Replication group is not protected. |
Resolution | Cause: Most common reasons: 1. The remote system is unavailable.
Error message: Remote system service for system with management address xx.xx.xx.xx is not available.
2. Misconfigured storage container destination.
Error message: Can't create replication destination for replication group <name> (<id>). Storage container <name> (<id>) has no destination defined on remote system <name> (<id>).
3. System failure to delete empty replication groups after all the Virtual Volumes were removed from these replication groups
Solution:Resolve the issue reported in the error message and wait for the next RPO cycle. The next RPO cycle will automatically clear this alert if the issue has been resolved. For cause #3, see Additional Info section below. |
Alert ID | POLICY_SESSION_CREATE_FROM_NAS_SERVER_FAILED |
Alert Text | Unable to create a replication session from %(source_name) to %(remote_system_name) due to the error: %(error_message_key) |
Error Code | 0x00900E01 |
Impact | The NAS Server is not yet protected by replication. |
Resolution | Cause: Most common reasons:
Solution: Resolve the issue reported in the error message and wait for the next RPO cycle. If the alert is raised when changing the destination of an asynchronous replication to be a different, third, PowerStore Cluster:
|
Alert ID | POLICY_METRO_REPLICATE_FOR_VOLUME_FAILED |
Alert Text | Unable to configure the protection policy on the remote system due to error: %(error_message_key). |
Error Code | 0x00901501 |
Impact | Local protection is not configured for the metro resource on the remote system. |
Resolution | Cause: 1. The remote system is unavailable (ie. either power failure, network failure, or possibly the system is faulted such that management is not available)
Error message: Remote system service for system with management address xx.xx.xx.xx is not available.
2. The system limit has reached for policies, snapshot_rules, or replication_rules.The error message will have the same format but will mention “snapshot rules” and “replication rules” instead.
Error message: A maximum of 64 protection policies are supported per system.
Solution: Resolve the issue reported in the error message. Once the issue has been resolved, the protection policy on the remote system will be created and the alert cleared. |
For alert 0x00901601 with cause software issue resulting in the failure to delete empty replication groups after all the vVOLS were removed from these replication groups:
The issue can be solved by deletion of the replication group on which the alert is raised.
1. Find the id of the replication group causing an alert
curl "https://$cluster_ip/api/rest/replication_group?name=eq.$rg_name"
Where cluster_ip is IP of the PowerStore cluster and rg_name is the value of the 'Resource Name' column from the alerts table
2. Issue a REST DELETE on the replication group
curl -X DELETE "https://$cluster_ip/api/rest/replication_group/$rg_id"
Where rg_id is the id of the replication group found on the previous step
PowerStore
22 Jun 2023
6
Solution