Welcome to part 7 of the ASM to ARM with Azure Site Recovery.

In this blog we will do the actual failover,
before we start it’s advisable to check what VM sizes ASR will provide for your target VMs, in my case the DS2V2 was resized to A5:

Test Failover

Running Test Failovers allow to do some pre checking without interupting the production environment and gives you good indication on potential issues.

Test failovers consume resources, so you should clean up the test failover environments if you don’t want large Azure bills at the end of the month 😉

and confirm you want to delete

Unplanned failover

Now instead of selecting test failover plan, we choose unplanned failover were the old environment should be brought down and start the ARM VMs.


Now hold on to your seat, cross your fingers and follow the progress in the portal:

If you configured everything well, you should see that everything is now running in the ARM model:

(don’t mind the shutdown problem, this behaviour has another root cause that is out of scope of this topic)

Checking the new resource group shows that all components are in place 🙂

There are still a few things we need to do here, and that will be discussed in the next and last part of this blog series.
part 8: Final fixes

Previous blogs in this serie:

part 1: create the ASM resources
part 2: create the recovery vault  
part 3: Network Configuration  
part 4: Mobility Agent installation 
part 5: Prepare failover infrastructure 
part 6: create the recovery plan