No progress on migration from physical server to azure

Question

I have a physical Windows Server 2019 server (actually a VmWare ESXi VM, but I do not have vCenter), which I am trying to migrate using agent. I have successfully assessed the server, and setup a Replication Server, loaded the agent and registered the server to the replication (process) server. The migration showed as "starting", but after a while I had a "critical" error: "{90078} Replication for APP (10.46.1.18) (Disk0) hasn't progressed in the last 60 minutes.".

I followed the troubleshooting guide for connectivity issues between the server and the process server. I found a problem when running cxpsclient - the error was "invalid id for host". After rebooting the Windows 2019 server, the problem was resolved, and cxpsclient runs without error. However, no data appears to be flowing.

Should I cancel the migration and start it again? I did notice that the "Azure Site Recovery VSS Provider" service was stopped (and set to manual) on the Windows 2019 server, so I started it, but this did not resolve the issue.

The Windows 2019 server has two ethernet interfaces (one with a private IP 10.46.1.18, and one with a public IP). The default route is via the public network.

Answer 1

Sharing the solution with broader community!

Below is a summary of this case for your records:

Based on documentation provided to you, you have configured CS using OVA and we have installed mobility agent on source machine APP.
We have added VM to the replication and Initial replication was completed without App-consistent recovery point due to SQL writers failure.
On source VM, from SQL management server we have verified “AUTO_CLOSE” ON databases and found 2 DBs and then we have turned off “AUTO_CLOSE” for the same. Please refer following documentation for more details & SQL queries https://learn.microsoft.com/en-US/troubleshoot/sql/admin/revocery-jobs-fail-servers
After turning off auto_close, we have recycled SQL VSS, ASR VSS & ASR services and could see SQL writer tuned into stable state.
Initiated App-Consistent recovery point manually from C:\Program Files (x86)\Microsoft Azure Site Recovery\agent>vacp -systemlevel and its completed
We have initiated test failover using latest App-Consistent recovery point, Assigned public IP, assigned NSG rules & connected using RDP. Please refer below documentation for Test Failover & Failover.
Test Failover: https://learn.microsoft.com/en-us/azure/site-recovery/tutorial-dr-drill-azure
Failover: https://learn.microsoft.com/en-us/azure/site-recovery/vmware-azure-tutorial-failover-failback

Please follow above documentation for test failover & failover

Please note that for Physical to Azure Scenario, you can’t failback from Azure to On-prem.

---------------------------------------------------------------------------------------------------------------

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