Azure Site Recovery has supported replicating Azure IaaS to a secondary Azure region for a little while now. The requirement to deploy a Configuration Server as part of the an ASR solution has moved to part of the platform and is a service that is no longer required to be maintained by the customer in an Azure to Azure scenario. Protecting Azure VMs to a secondary site is now so simple and we will run through the process.
Create Recovery Services Vault and enable replication
It is recommended to create the Recovery Service Vault in the target location where you will be replicating. This will just be a very basic replication of a single VM, for more advanced scenario involving multiple VMs you can create a Recovery Plan to determine how the failover sequencing should occur.
From the Recovery Services Vault select the replicate button.
Configure Source environment
- Select the Source “Azure – Preview”
- Select source region
- Select the deployment model
- Select the source Resource Group
Select the Virtual Machines to replicate
Configure the Target environment
There will be default values selected for Resource Group, Virtual Network and Storage Accounts. If there are Availability Sets in use in the source Virtual Machines this can be configured too.
Configure the Replication Policy
The default retention policy settings can be modified.
The snapshots can be configured to occur between 1 and 12 hours and the retention can be a maximum 72 hours.
Recovery point retention: 24 hour(s)
App consistent snapshot frequency: 4 hour(s)
View replicated systems
Under Protected Items you can view the replication status
You can perform a failover or a test failover directly from the portal. A test failover can be performed to a completely isolated Virtual network so as to not impact production.
You can view the progress of the test fail-over operation
Clean-up test failover
After the test has validated you can clean up the deployed VMs.