Azure Site Recovery
An Azure native disaster recovery service. Previously known as Microsoft Azure Hyper-V Recovery Manager.
632 questions
Azure site recovery vmware to Azure -Synchronization has been not progressing for the disk '\\.\PHYSICALDRIVE0'
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(278.4, 27%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EHR%3C/text%3E%3C/svg%3E)
Hazem Rajab
1
Reputation point
I have a VM protected on VMware using Azure site recovery, failed over to Azure and initiated fallback and the synchronization started and is now stuck with 83% and showing a critical error "Synchronization has been not progressing for the disk '\.\PHYSICALDRIVE0'
{count} votes
-
Hazem Rajab 1 Reputation point
2023-03-28T08:25:15.23+00:00 the only option for me now is to disable protection any suggestions what else I can do to avoid starting from scratch
-
Hazem Rajab 1 Reputation point
2023-03-28T08:26:47.5466667+00:00 Error ID 531504 Error Message Synchronization has been not progressing for the disk '\\.\PHYSICALDRIVE0' for the source machine 'APP-DC' in the last 120 minutes. Possible causes 1) Review active health issues for source machine. 2) Review active health issues for appliance connected to the source machine. Recommendation 1) Go to source machine and follow the recommendation on any active health issue. 2) Go to appliance connected to this source machine and follow the recommendation on any active health issue. -
SadiqhAhmed-MSFT 37,536 Reputation points Microsoft Employee2023-03-28T09:36:14.74+00:00 @Hazem Rajab Sorry for the inconvenience this must have caused you.
Could you please check the following logs:
C:\Program Files (X86)\Microsoft Azure Site Recovery\agent\svagents*.log
C:\ProgramData\ASR\home\svsystems\eventmanager*.log
C:\ProgramData\ASR\home\svsystems\monitor_protection*.log
See if you could find some directions to fix the issue.
-
Hazem Rajab 1 Reputation point
2023-03-28T17:48:42.6866667+00:00 I wasn't able to login to the VM due RDP port not allowing it for some reason, since not able to login to the VM and not able to fail back I had to cancel the protection to power on the machine on-premise in Vcenter, further to that, the VM on the Vcenter didn't boot correctly and start in recovery mode 2012 r2
-
SadiqhAhmed-MSFT 37,536 Reputation points Microsoft Employee
2023-03-29T04:51:46.65+00:00 @Hazem Rajab Thanks for the update. It sounds like an issue with your on-premise set up. Fixing that should help resolve your original problem mentioned on this post.
Please let us know once everything starts working as expected or if you need any assistance from our end.
-
SadiqhAhmed-MSFT 37,536 Reputation points Microsoft Employee
2023-03-31T10:26:45.6566667+00:00 @Hazem Rajab Any progress on this?
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(294.40000000000003, 48%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBA%3C/text%3E%3C/svg%3E)
Brown, Ashley 0 Reputation points2023-06-19T15:54:16.49+00:00 I am having this same issue also, any updates on how to resolve?
-
SadiqhAhmed-MSFT 37,536 Reputation points Microsoft Employee
2023-06-20T11:28:34.6433333+00:00 @Brown, Ashley Did you try disabling the protection and re-enabling it?
-
SadiqhAhmed-MSFT 37,536 Reputation points Microsoft Employee
2023-06-22T13:10:23.18+00:00 @Brown, Ashley We haven't heard back from you. Please reply if you have any questions in this matter and we will gladly continue the discussion.
Sign in to comment