ASR Test Failover VM not starting

Ernest Aduboffour 0

I am currently doing ASR tests in Azure and once the test failover for windows VM is complete, the failover test VM stays in a stopped state, any attempt to start the VM results in it switching to Stopped.

Source VM is in UKSouth and target location is UKWest, Please any idea why this is happening?

SadiqhAhmed-MSFT 42,426 Reputation points Microsoft Employee

2024-07-10T14:45:13.72+00:00
@Ernest Aduboffour Thank you for reaching out to us on Microsoft Q&A platform. Happy to help!

If the failover test VM stays in a stopped state after a failover test for a Windows VM in Azure Site Recovery (ASR), there may be an issue with the VM configuration or with the failover test process.

Here are a few troubleshooting steps you can try:

Check the VM configuration to ensure that it meets the requirements for ASR failover testing. For example, the VM should have the appropriate network settings, storage settings, and operating system configuration. Reference doc link - https://learn.microsoft.com/en-us/azure/site-recovery/azure-to-azure-support-matrix

Network Configuration Issues:

Subnet Availability: Ensure that the subnet where the test failover VM is deployed in UKWest has sufficient IP addresses available. Sometimes, subnet exhaustion can prevent VMs from starting properly.

Network Security Group (NSG) Rules: Check NSG rules that might be blocking traffic necessary for the VM to start or communicate properly with Azure services. Storage Account Availability:

Verify that the storage account where the VM's disks are stored is accessible and not encountering any issues. Issues with storage accounts can prevent VMs from starting.

ASR Configuration Issues:

Replication Health: Verify the replication health status in the Azure Portal for the replication policy associated with your VM. Ensure that replication is healthy and up-to-date.

Recovery Services Vault: Check the configuration of your Recovery Services vault and ensure that it is properly configured for failover and failback operations.

Try starting the VM from the Azure portal or using PowerShell to see if the issue persists. If the VM still cannot be started, there may be an issue with the VM configuration or with the underlying infrastructure.

If the issue persists after trying these steps, you may need to contact Azure support for further assistance. You can submit a support request through the Azure portal. The ticket enables you to work closely with the support engineers and get a quick resolution to your issue. Here is the link - https://docs.microsoft.com/en-us/azure/azure-portal/supportability/how-to-create-azure-support-request to create support case.

Hope this helps. Please let us know if you have any further questions or need assistance.

If the response helped, do "Accept Answer" and up-vote it
Ernest Aduboffour 0 Reputation points

2024-07-30T08:31:42.8566667+00:00

Fixed
SadiqhAhmed-MSFT 42,426 Reputation points Microsoft Employee

2024-07-30T09:56:46.2433333+00:00

@Ernest Aduboffour Thanks for the update. Glad to know that you were able to fix the issue.

1 answer

SadiqhAhmed-MSFT 42,426 Reputation points Microsoft Employee

2024-07-30T10:00:48.1866667+00:00

Update:

@Ernest Aduboffour was able to resolve the issue by disabling replication and re-enabling it. This helped fix the stopped state issue.

Hope this helps!
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Share via

ASR Test Failover VM not starting

1 answer