Migrate on-premises machines to Azure
Prerequisites
Devices exported by paravirtualized drivers aren't supported.
Create a Recovery Services vault
- Sign in to the Azure portal > Recovery Services.
- Click Create a resource > Monitoring & Management > Backup and Site Recovery.
- In Name, specify the friendly name ContosoVMVault. If you have more than one subscription, select the appropriate one.
- Create a resource group ContosoRG.
- Specify an Azure region. To check supported regions, see geographic availability in Azure Site Recovery Pricing Details.
-
To quickly access the vault from the dashboard, click Pin to dashboard and then click Create.
The new vault is added to the Dashboard under All resources, and on the main Recovery Services vaults page.
Select a replication goal
Select what you want to replicate, and where you want to replicate to.
- Click Recovery Services vaults > vault.
- In the Resource Menu, click Site Recovery > Prepare Infrastructure > Protection goal.
- In Protection goal, select what you want to migrate.
- VMware: Select To Azure > Yes, with VMWare vSphere Hypervisor.
- Physical machine: Select To Azure > Not virtualized/Other.
- Hyper-V: Select To Azure > Yes, with Hyper-V. If Hyper-V VMs are managed by VMM, select Yes.
Set up the source environment
- Set up the source environment for VMware VMs.
- Set up the source environment for physical servers.
- Set up the source environment for Hyper-V VMs.
Set up the target environment
Select and verify target resources.
- Click Prepare infrastructure > Target, and select the Azure subscription you want to use.
- Specify the Resource Manager deployment model.
- Site Recovery checks that you have one or more compatible Azure storage accounts and networks.
Set up a replication policy
- Set up a replication policy for VMware VMs.
- Set up a replication policy for physical servers.
- Set up a replication policy for Hyper-V VMs.
Enable replication
- Enable replication for VMware VMs.
- Enable replication for physical servers.
- Enable replication for Hyper-V VMs with or without VMM.
Run a test migration
Run a test failover to Azure, to make sure everything's working as expected.
Migrate to Azure
Run a failover for the machines you want to migrate.
- In Settings > Replicated items click the machine > Failover.
- In Failover select a Recovery Point to fail over to. Select the latest recovery point.
- The encryption key setting isn't relevant for this scenario.
- Select Shut down machine before beginning failover. Site Recovery will attempt to do a shutdown of source virtual machines before triggering the failover. Failover continues even if shutdown fails. You can follow the failover progress on the Jobspage.
- Check that the Azure VM appears in Azure as expected.
-
In Replicated items, right-click the VM > Complete Migration. This finishes the migration process, stops replication for the VM, and stops Site Recovery billing for the VM.
Warning
Don't cancel a failover in progress: VM replication is stopped before failover starts. If you cancel a failover in progress, failover stops, but the VM won't replicate again.
In some scenarios, failover requires additional processing that takes around eight to ten minutes to complete. You might notice longer test failover times for physical servers, VMware Linux machines, VMware VMs that don't have the DHCP service enables, and VMware VMs that don't have the following boot drivers: storvsc, vmbus, storflt, intelide, atapi.