Recovery Point

Category: microsoft azure site recovery

Question

jen2017 on Mon, 07 Aug 2017 15:22:29


Hi,

I have a replicated VMware that is showing "Critical" but Protected and when you go to the error details it is showing "Error ID
78027". However, recovery point is showing some having apps-consistent. What does this mean? Is my VMware really Protected or do I need to worry that this VMware is not replicated.                                                                                                           

Replies

vikranth s on Mon, 07 Aug 2017 20:10:32


Can you share the screenshot of the error message?

 

Do click on "Mark as Answer" on the post that helps you, this can be beneficial to other community members.

jen2017 on Mon, 07 Aug 2017 20:18:01


Here's the complete details of the error message.

Error ID
78026
Error Message
RPO has exceeded the configured threshold for source disks 'Disk5, Disk3'.
Possible causes

        The RPO for a replicating machine may be impacted if:
        1. The machine is shutdown, the Mobility service components on the machine is not running, or the machine doesn’t have network connectivity to the process server.
        2. The replicating machine is unable to upload changes fast enough to the process server, or the replicating machine has been flow controlled/throttled by the process server, thereby causing the machine to go into a non-data replication mode.
        3. Recovery tag generation failures on the replicating machine.
        4. The process server is unable to upload changes fast enough to the target/log Azure storage account (or the master target server if replicating to an on-premises site). This in turn can happen due to network connectivity issues /glitches or insufficient network throughput/bandwidth between the process server and the Azure log/target storage account.
        5. Storage IOPs/throughput limits are being hit on the log/target storage account resulting in reduced end to end upload throughput from the process server to the log/target storage account in Azure.
   
Recommendation

        1. If there are other errors for the replicating machine, resolve them first.
        2. See the list of recent events for the replicating machine that may be impacting the RPO of the machine by going to the events section of the recovery services vault. If there are any such events, resolve them.
        3. Ensure that you have sufficient network bandwidth between the process server and the log/target Azure storage account (or master target server if replicating to on-premises site) to upload replication data, and that you are replicating to the appropriate tier of storage based on the data change rate characteristics of the replicating machine. Use the ASR deployment planner (https://aka.ms/asr-v2a-deployment-planner) to estimate the necessary network bandwidth requirements and the appropriate tier of storage to replicate to.

        Refer to the article https://aka.ms/asr-v2a-replication-troubleshooting , to learn how to troubleshoot replication issues.

vikranth s on Tue, 08 Aug 2017 16:55:59


Just to clarify, have you tried the recommendations provided by ASR?

Do click on "Mark as Answer" on the post that helps you, this can be beneficial to other community members.