RPO has exceeded the configured threshold for source disks 'Disk2, Disk3, Disk4'.

Question

On Azure Site Recovery, I am having problems with disk synchronization on one of my replicated virtual machines. A new drive was added to the physical server, so I disabled the virtual machine and chose the new disk in the configuration to enable it. Only five of the six disks in the Windows virtual machine (VM) are secured; the root disk has been in synchronization mode for the past few days.

Communication between the VM server and the process server is good.

The process server is operating well.

These are the EEROR codes: 78026

 **Error ID**

• 78026
• Error Message RPO has exceeded the configured threshold for source disks 'Disk2, Disk3, Disk4'.
• 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.
  Error ID 78216
• Error Message Process Server is not able to accept more data for the following disk(s). 1. Disk0, ObservationTime : 2024-Apr-15 11:10:15 UTC 2. Disk4, ObservationTime : 2024-Apr-15 13:07:42 UTC 3. Disk2, ObservationTime : 2024-Apr-15 11:10:15 UTC 4. Disk5, ObservationTime : 2024-Apr-15 13:48:30 UTC 5. Disk3, ObservationTime : 2024-Apr-15 11:30:16 UTC.
• Possible causes The Process Server might not be in a healthy state.
• Recommendation Go to the Process Server and check for active health issues and recommendations.

Please assist with this matter.

Answer 1

Hello @azure test

It seems you’re encountering a disk synchronization issue with Azure Site Recovery after adding a new drive to your physical server. Here’s a step-by-step guide to help you resolve this:

Check Replication Health: After adding a new disk, the replication health for the VM might show a warning. This is normal until you enable protection for the new disk1.

Enable Replication for the New Disk:

• Navigate to the vault > Replicated Items, click on the VM to which you added the disk.
  • Click on Disks, and then select the data disk you want to protect (these disks will have a Not protected status).
    • In Disk Details, click Enable replication1.
    Monitor Initial Replication: After enabling replication, monitor the initial replication process. Once it finishes, the replication health warning should disappear1. Troubleshoot Common Problems: If you continue to face issues, you might need to troubleshoot common problems such as high data change rate on the source VM or network connectivity problems2. Verify Disk Support: Ensure that the new disk adheres to Azure Site Recovery’s supported configurations and limits2.

If you’ve followed these steps and the issue persists, it might be beneficial to review the detailed troubleshooting guides provided by Microsoft or contact Azure support for further assistance. Remember, it’s important to ensure that the new disk is properly configured and recognized by the system before attempting to re-enable replication.