ASR Replication of a 16TB VMware VM to Azure stuck at "Waiting for first recovery point"

Question

I setup ASR replication from on-prem VMware Win2019 SQL server (16TB) to a Premium SSD target disk. Replication completed and its stuck at 'Waiting for first recovery point". Its been over 24hours.

I'm replicating 5 other VMware servers just fine.

Any assistance would be apprciated.

thank you.

Answer 1

Hello @Ted Lemery Thank you for reaching out to us on Microsoft Q&A platform. Happy to help!

Based on the information you provided, I understand that you are trying to replicate on-prem VMware Win2019 SQL server (16TB) to a Premium SSD target disk. However, the replication is stuck at 'Waiting for first recovery point".

If your ASR replication is stuck at "Waiting for first recovery point" for over 24 hours, there could be several reasons for this issue.

Ensure that there are no network issues between your on-premises VMware environment and Azure. Check for any firewall rules, network configurations, or connectivity issues that might be preventing data transfer.

Double-check the replication settings for the VM in ASR. Ensure that the replication policy, target disk type (Premium SSD), and other settings are configured correctly.

Monitor the replication health in the Azure portal. Look for any error messages or warnings that might provide insight into why the replication is stuck.

Check the VMware environment for any issues that might be affecting replication. Ensure that the VMware environment meets the requirements for ASR replication and that there are no issues with the VM itself, such as disk corruption or resource constraints.

Check the version of the ASR agent installed on the on-premises server to ensure that it is up to date and compatible with the version of the target disk in Azure.

In some cases, restarting the replication process can help resolve issues. Try stopping and restarting the replication for the affected VM in the Azure portal.

If you're unable to resolve the issue using the above steps, consider contacting Azure support for further assistance. They can help diagnose the problem and provide guidance on resolving it.

Hope this helps. Please write back to us if you have any further questions or need assistance!

---

If the response helped, do "Accept Answer" and up-vote it