Hyper-V prevented starting virtual machine because it is prepared for failover fix

Using Azure Migrate to migrate Virtual Machines from a Hyper-V host to Azure, you may want to start a Hyper-V Virtual Machine (VM) after they have been migrated for various reasons including:-

  • VM not accessible in Azure
  • Azure Migration issue and want to restore back to an earlier version of the VM again on Hyper-V

The problem

When powering on Virtual Machine again in Hyper-V host after migration to Azure using Azure migrate you will have an error as below:-

'tamopsvm' failed to start.

Hyper-V prevented starting virtual machine because it is prepared for failover.

Replication operation for virtual machine 'tamopsvm' failed.

Hyper-V prevented starting virtual machine 'tamopsvm' because it is prepared for planned failover. Virtual machine can be started after cancelling failover preparation.

The fix

With Hyper-V migration to Azure using Azure Migrate, Azure Site Recovery is configured as part of the setup – along with this a recovery services vault is created to enable & configure Azure Site Recovery successfully.

Inside the recovery services vault, review replicated items

You will VMs with status as below if they have been failed over to Azure

Select VM you want to Power on in Hyper-V and disable replication

Once this has been disabled you will be allowed to power on VM successfully again in Hyper-V

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s