Article Number: 000128511
PowerStore Alerts: Recovery Point Objective (RPO) Alerts
Summary: Recovery Point Objective (RPO) alerts caused due to Insufficient Replication bandwidth and Low alert threshold.
Article Content
Symptoms
When Dell PowerStore encounters a problem, an error alert is generated to help identify the issue. This article explains the different possible causes and the relevant solutions for these error alerts. If your problem is not resolved despite the solution provided, check the technical support contact options.
Note: Cannot find the information needed? Let us know using the feedback form at the bottom of this article.
Note: Cannot find the information needed? Let us know using the feedback form at the bottom of this article.
Cause
The cause is mentioned in the Resolution section under the respective alerts.
Resolution
| Alert ID |
|
| Alert Text |
|
| Error Code |
|
| Description | RPO is the industry abbreviation for "recovery point objective". RPO indicates the maximum amount of data loss (in time) that is deemed acceptable in a disaster recovery scenario. When replication is unable to meet this objective, the RPO compliance is considered "breached". An extended breach is a major alert and indicates that the RPO has not been met for an extended period of time, for example 4 days. |
| System Impact | Remote protection is not RPO compliant. |
| Resolution | 1. Insufficient replication bandwidth: Cause Replication is the copying of data to a remote array, which may be constrained by low network resources, source system resources or target system resources. Solution #1 Check for any recent changes in the environment such as new hardware or software upgrades, or new workloads which were added to the environment. These may be the cause of the issue and must be reassessed. Ensure that the destination system has enough space and that synchronization jobs that are already in progress are not blocked. Solution #2 Check the source and target systems for relevant alerts which may indicate an issue that could impact the system's available resources. Check for similar events at the network level. Solution #3 Add additional resources to the network, such as additional bandwidth, and improve packet drop rate and latency. Solution #4 Small RPO may consume more system resources. |
| 2. Low alert threshold: Cause Occasionally, the RPO may be breached briefly, but then compliance is quickly achieved. This may be normal if, for example, replication is competing with other high-bandwidth applications on a WAN link. Solution Consider increasing the Alert Threshold setting in the replication rule (%(replication_rule_name)) mentioned in the alert text, without increasing the RPO. |
| Alert ID |
|
| Alert Text |
|
| Error Code |
|
| Impact | Remote protection is not RPO compliant. |
| Resolution | Cause: The alert is raised when RPO compliance is not met due to various reasons including:
Solution: Check network connectivity between the source and destination systems. Ensure that the destination system has enough space, and synchronization jobs that are already in progress are not blocked. If the alert persists, consider increasing the Alert Threshold setting in the replication rule mentioned in the alert text. If the alert was the result of an NDU verify that replication has resumed and is back in synch. |
Article Properties
Affected Product
PowerStore
Last Published Date
22 Feb 2024
Version
7
Article Type
Solution