0x3230016 RPO Requirement Is Not Met

Description

Protected group (name: {1}) does not meet the RPO requirement.

Attribute

Impact on the System

The DR data cannot meet the RPO requirement.

Possible Causes

• The protected group fails to be executed.
• Data protection status is abnormal.
• Data replication duration exceeds the preset RPO.

Procedure

1. Check whether the protected group uses the HyperMetro or synchronous replication policy.
   • If no, go to 2.
   • If yes, go to 5.

2. Check whether the last protected group execution is successful.
   • If the last execution is not started according to the preset policy, go to 7.
   • If the command fails to be executed, check the latest execution record of the protected group, locate the fault based on the failure cause, and take corresponding measures to rectify the fault. After that, manually execute the protected group and wait for 5 to 10 minutes to check whether the alarm is cleared. If the alarm persists, go to 3.
   • The protected group is being executed.=>Wait for 5 to 10 minutes after the protected group is executed and check whether the alarm is cleared. If the alarm persists, go to 7.

3. Check whether data protection status is normal.
   • If yes, rectify the data protection configurations, refresh the device and protected group, and manually execute the protected group according to requirements. If the alarm persists, go to 4.
   • If no, go to 4.

4. View execution records of the protected group and check whether the data replication period exceeds the preset RPO period.
   • If yes, increase bandwidth of service networks or adjust protected group execution time to off-peak hours. Wait until the next execution is complete. If the alarm persists, go to 7.
   • If no, go to 7.

5. Refresh the storage and FC and check whether the protected group fails.
   • If yes, go to 3.
   • If no, go to 7.

6. Check whether the status of the pair and consistency group corresponding to the protected group on the storage device is normal.
   • If they are abnormal and in the split state, manually execute the consistency group, refresh the storage and FC on UltraVR, and check whether the alarm is cleared. If no, go to 7.
   • In other cases, go to 7.

7. Contact technical support engineers.

Related Information

None