Yunsung on Fri, 30 Nov 2018 10:13:09
I'm trying to replicate a VM ( in VMware) to Azure but after it reaches 100% the status is "waiting for first recovery point".
I already followed this Troubleshooting https://docs.microsoft.com/en-us/azure/site-recovery/vmware-azure-troubleshoot-replication but it seems all okay.
I restarted Source Server and Process server but the problem still exists.
What else can i do?
Femisulu on Wed, 05 Dec 2018 18:57:13
Hi Yunsung, is this still an issue? If yes, we may need to engage Azure technical support to investigate further.
If you have a support plan, follow these steps to raise a support ticket. If you do not have a plan, send mail to AzCommunity@Microsoft.com with your subscription ID, a link to this MSDN issue and include "ATTN Femi" in the subject line and we will gladly assist you with raising a support ticket to help resolve your issue.
Mara Ram on Fri, 07 Dec 2018 07:07:26
You will be seeing this behavior when changes are still pending on your source VM which are yet to be committed. Can you check what does the pending data shows in Replication Item -> Click on the VM -> Disks and check the pending data.
Here, Microsoft should at-least propose an estimated time to get a new recovery point instead of saying like waiting for a new recovery point. This will at-least help or fix this issue.
Yunsung on Mon, 10 Dec 2018 15:23:44
Now the status is "Protected" but when i try to start a Planned Failover ( Test Failover) it says that it didn't generate a recovery point.
I have this warning:
Error ID: 78188
Error Message: The data change rate(churn) for one or more replicating disks has exceeded the Azure Site Recovery supported limits: https://aka.ms/asr-v2a-target-limits.
Possible Causes: The data change rate (write bytes/sec) on one or more disks of the virtual machine is more than the Azure Site Recovery supported limits for the selected replication target storage type.
1. Review the Azure Site Recovery supported limits https://aka.ms/asr-v2a-target-limits. 2. If the problem continues
to persist, use the Azure Site Recovery deployment planner to help plan target storage selection to replicate the virtual machine https://aka.ms/asr-v2a-deployment-planner.
Is it the problem for not creating recovery points?
Mara Ram on Tue, 11 Dec 2018 03:59:27
It means still data changes are pending. You can login into the server and run below commands and check the pending data changes:
ASR agent installation path --> bin >> drvutil --ps
It will show you all the disks status along with pending information and each disks status should be in DataMode.. I it is in Non-Data or BitMap then still data has not drained to cloud.