| Asset ID: |
1-79-1531168.1 |
| Update Date: | 2015-01-13 |
| Keywords: | |
Solution Type
Predictive Self-Healing Sure
Solution
1531168.1
:
Pillar Axiom: MaxRep PCP_EVT_REPL_RPOSLA_THRESHOLD_EXCEEDED
| Related Items |
- Pillar Axiom Replication Engine (MaxRep)
- Pillar Axiom Volume Replicator Appliance
|
| Related Categories |
- PLA-Support>Sun Systems>DISK>Axiom>SN-DK: MaxRep-2x
|
In this Document
Applies to:
Pillar Axiom Volume Replicator Appliance - Version Not Applicable to Not Applicable [Release N/A]
Pillar Axiom Replication Engine (MaxRep) - Version 2.0 to 2.0 [Release 2.0]
Information in this document applies to any platform.
Purpose
Provide steps for system administrators to resolve PCP_EVT_REPL_RPOSLA_THRESHOLD_EXCEEDED events.
Details
Purpose
Event PCP_EVT_REPL_RPOSLA_THRESHOLD_EXCEEDED is an indication that a protection plan on the MaxRep replication engine has exceeded its defined acceptable Recover Point Objective (RPO). The RPO defines the acceptable delta range in time between the source and target LUNs of a replication pair. Because data changes to a source LUN are sporadic, and bandwidth of WAN connections is often limited, the amount of data in flight between the source and target LUNs can vary over time. The amount data in flight, or not yet committed to the target MaxRep engine determines the RPO and any given point in time. When creating a protection plan on a MaxRep engine, a opportunity is given to define an acceptable RPO for that plan. If the amount of data that has changed on the source, but not yet committed to the target exceeds this defined threshold, the ASR event PCP_EVT_REPL_RPOSLA_THRESHOLD_EXCEEDED is triggered.
Troubleshooting Steps
- Log into the MaxRep Engine UI.
- Select the protection plan in the “Protection Health” window.
- Review the current RPO in the “Disks/Volumes/LUNs Replication” table.
- Click on “Details” in the “Disks/Volumes/LUNs Replication” table for the replication pair.
- Identify the defined RPO Threshold from the “Pair Settings” table.
- If the current RPO exceeds the RPO Threshold, the fault is valid. If the fault is valid, proceed to the options below.
- If the current RPO is not exceeding the RPO Threshold, it is possible that there was a sporadic spike in writes to the source LUN or a temporary fault in the WAN link which has been resolved. In either case if there is no further action required. If additional or repeated PCP_EVT_REPL_RPOSLA_THRESHOLD_EXCEEDED events continue to be generated, contact the TSC.
If the fault is valid there are two options to resolve the issue:
- Review the WAN link and utilization. Adequate bandwidth between the source and target MaxRep engines is critical to maintain RPO thresholds. If the available bandwidth between the source and target is insufficient to meet the change rate of the source volume, the MaxRep engines will be incapable of transferring the data at a sufficient speed to maintain a specified RPO. If the WAN link become unreliable, over utilized, or under sized, additional WAN capabilities might need to be added to the overall replication design in order to meet a desired RPO.
- Increase your RPO Threshold. Increasing the RPO Threshold in a protection plan will provide for greater tolerance to sporadic change rates and utilization issues of WAN connectivity. By increasing the RPO threshold, a protection plan can have a greater amount of data uncommitted between the source and target prior to triggering a PCP_EVT_REPL_RPOSLA_THRESHOLD_EXCEEDED alert.
Attachments
This solution has no attachment
