Failover

In this blog we will do the actual failover.

Tip: Before we start it’s advisable to check what VM sizes ASR will provide for our target VMs, here the DS2V2 was resized to A5:

Test Failover

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

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

and confirm we 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 we configured everything well, we should see that everything is now running in the ARM model:

(don’t mind the shutdown problem, this behaviour is actually the result of the failed VM extentions test on ASM)

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.

Overview

This article is part of a series, check for the overview here:  Azure: Moving form ASM to ARM with ASR (TOC)