Setting up disaster recovery for Azure VM in secondary region
AZURE
To keep business critical applications running 24/7/365 it is important for organizations to have a sound business continuity and disaster recovery strategy. In this article we will discuss how to set up disaster recovery for Azure VM in secondary region.
We will use Azure Site Recovery that helps manage and orchestrate disaster recovery of on-premises machines and Azure virtual machines (VM), including replication, failover, and recovery.
Pre-requisites,
- Recovery services vault
- A Virtual machine
ENABLING REPLICATION
To replicate a VM to secondary region, prepare site recovery infrastructure. In this case we are replicating from one azure region to another.
For replication from Azure to Azure, one can directly go to recovery service vault and replicate the VM.
- Go to recovery services vault >> Replicated Items
- Click on the Replicate icon and follow.
3. Select the following
- Source: Azure
- Source location: Region where the VM is deployed
- Azure virtual machine deployment model: Resource manager
- Source subscription: Subscription where the VM is deployed
- Source Resource group: Resource group where the VM is deployed
4. Select OK to proceed to next step.
5.Select the VM to replicate
6. Target configurations
- Target location: Secondary region where the VM is to be replicated
- Target subscription: Subscription where the VM to be replicated
By default, the following resources are created in target region and can be customized per your need
- Resource group
- Virtual network
- Cache storage account
- Replica managed disks
- Target availability sets (if applicable)
You can set replication policies and view extension details here
7.Click on create target resources
8.Then select Enable replication
Go to recovery services vault >> Monitoring >> Site recovery Jobs to view the jobs that are running during the replication.
Look for the following jobs
- Prerequisites check for enabling protection
- Installing Mobility Service and preparing target
- Enable replication
- Starting initial replication
- Updating the provider states
Once the above-mentioned jobs are over, here is what happens
- Synchronization process begins
- Waiting for first recovery point
- The VM is protected
Once all processes are completed, you can view the VM by going to recovery services vault >> Replicated Items
Share this:
Take a look at the lastest aricles
CloudIQ AI Engineering Series — Part 5 Most teams picked a model and called it a day. The teams shipping faster and spending less are learning that model selection is only one part of the equation. In a multi-agent pipeline, orchestration design can matter just as much — and is often overlooked. There's a bill […]
The QA report came back clean. The developer had migrated an approval workflow module from a legacy stack to a modern stack. Parity check passed. Functionality verified. The page looked right, behaved right, and matched the spec. The bug report came in the next day. Data entered in that module wasn't propagating correctly to a […]
Six months into AI-assisted development, something predictable happens. The team has gotten good at prompting. The spec workflow is running. Output quality is solid. Then the codebase crosses a threshold — too many files to reference manually, too many interdependencies to hold in a session — and the approach that worked at month two stops […]
Let’s shape your AI-powered future together.
Partner with CloudIQ to achieve immediate gains while building a strong foundation for long-term, transformative success.