Click to highlight the plan you just created and choose failover (you should do the test failover thatll copy the failover process without impacting the VMs, so thatll be smart to do in production, but for the sake of time of test VMs, just run a failover and itll shutdown your VMs and prepare your VMs for failover). The VMs will be offline for a while as it copies over any new data from the last snapshot it created. A Planned Failover will copy over any unreplicated bits to make sure the target in Azure is most up to date, an unplanned failover will not replicate bits that have not yet been replicated that could lead to data loss. So if you have the ability to do a planned failover, thatll ensure data integrity in the failover process.
When the failover preparation has been completed, you then have to click the commit at the bottom of the Recovery Plan page, thatll then switch the VMs, networking, everything over to Azure
Once the thing shows that the commit took, now you go into the Virtual Machines section of the Azure Portal and within the normal Azure management UI, youll see your VM happily running as a virtual machine.
Obviously to do this right, youd need to do DNS changes so that if you had an app going to a public DNS address, that it now goes to the address that Azure is publishing, so there will be some fine tuning needed after a failover. However for this Preview, to be able to quickly see how you can simply replicate VMs to Azure and then failover the VMs to Azure, this is a pretty incredible offering!
End of the day, On-site Datacenter to Azure DR failover and failback for $27/month per VM!
Sign up for MIS Asia eNewsletters.