AppSync: RPO failures despite all Service Plan phases completing successfully
Summary: Under certain circumstances, users may see RPO errors despite all Service Plan phases completing successfully. The following error may be seen in the Service Plan events. Recovery Point Objective for Source-Server/Application-Element is out of compliance. Run the service plan after fixing errors to restore compliance. ...
This article applies to
This article does not apply to
This article is not tied to any specific product.
Not all product versions are identified in this article.
Symptoms
Users may see the following error in a service plan despite all phases of the plan completing successfully:
Recovery Point Objective for Source-Server/Application-Element is out of compliance. Run the service plan after fixing errors to restore compliance.
Cause
To understand this error, it is important to note that RPO is not designed to monitor success or failure of any given Service Plan.
RPO is primarily a reporting tool. It is mainly used for sites where there is an Service Level Agreement (SLA) to ensure successful copies within a set period of time.
RPO is a logical value between 1hr and 24 hours that a user can set on any item in a Service Plan. For example, if RPO is set to 6hours, AppSync checks that the latest copy is no older than 6 hours. If it is 6 hours + 1 minute, then AppSync generates an alert.
In the example below, RPO is set to 24 hours. The Service Plans run on time and all phases are successful. The Service Plan is scheduled to make a copy every 24 hours.
On day one, the copy is made at 01:34.
On day two, the copy is made at 01:15. This is 2 minutes later than the day before and triggers an RPO alert.
On day three, the copy is made at 01:12 this is under 24 hours and so no error is generated.
On day four, again the copy is 2 minutes later than the day before and so an RPO alert is generated.
On day five, we see the copy is made in 54 seconds less than 24 hours and so for RPO this is successful.
RPO is primarily a reporting tool. It is mainly used for sites where there is an Service Level Agreement (SLA) to ensure successful copies within a set period of time.
RPO is a logical value between 1hr and 24 hours that a user can set on any item in a Service Plan. For example, if RPO is set to 6hours, AppSync checks that the latest copy is no older than 6 hours. If it is 6 hours + 1 minute, then AppSync generates an alert.
In the example below, RPO is set to 24 hours. The Service Plans run on time and all phases are successful. The Service Plan is scheduled to make a copy every 24 hours.
On day one, the copy is made at 01:34.
2021-01-06 01:13:44.124,Create local and remote copies,24a42657-c303-45ba-8778-f9e847304d65,MILE_000006,APPSYNC-SERVER,Create local and remote copies phase for Application-Element completed successfully
On day two, the copy is made at 01:15. This is 2 minutes later than the day before and triggers an RPO alert.
2021-01-07 01:15:22.289,Create local and remote copies,cf08f54d-06e1-45cc-b924-c307ca39e6ac,MILE_000006,APPSYNC-SERVER,Create local and remote copies phase for Application-Element completed successfully
On day three, the copy is made at 01:12 this is under 24 hours and so no error is generated.
2021-01-08 01:12:15.236,Create local and remote copies,2e27f6b5-ea17-431a-a61d-271129518580,MILE_000006,APPSYNC-SERVER,Create local and remote copies phase for Application-Element completed successfully
On day four, again the copy is 2 minutes later than the day before and so an RPO alert is generated.
2021-01-09 01:14:17.469,Create local and remote copies,fa1c131a-fbbb-41c3-bbe5-dd5116ae5f28,MILE_000006,APPSYNC-SERVER,Create local and remote copies phase for Application-Element completed successfully
On day five, we see the copy is made in 54 seconds less than 24 hours and so for RPO this is successful.
2021-01-10 01:13:23.419,Create local and remote copies,8087f733-0051-4ab0-a5e2-32486bb347d5,MILE_000006,APPSYNC-SERVER,Create local and remote copies phase for Application-Element completed successfully
Out of this 5 day example, we have 2 RPO failures. This is because on day 2 and day 4, the Service Plan took slightly longer to complete than the other days. An RPO failure alert is generated if the copy is 1 second over the 24 hours. Since there are a number of components outside of AppSync’s control (array performance, network performance, VM Snap time, etc), it is impossible to ensure that snaps occur exactly at 24 hours.
Resolution
To avoid RPO failures for successful Service Plans, the following must be done:
- Some thought should be put into considering if RPO alerts are useful in the environment. If AppSync is not being used to generate reports on timely creation of copies, then RPO should be disabled in the Service Plan.
- If RPO is required, then the Service Plan should be scheduled so that it completes with greater frequency than the RPO. For example, for an RPO of 6 hours, the Service Plan could be scheduled to run every 4 hours. This will guarantee that minor fluctuations in server, storage, and network performance do not generate false errors.
Affected Products
AppSyncArticle Properties
Article Number: 000182844
Article Type: Solution
Last Modified: 08 May 2026
Version: 5
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.