VM Migration: Indore Region to Mumbai Region

Disaster Recovery (DR) Drill

Cross-Region Data Replication Using rsync

Primary Region: Indore DR Region: Mumbai Operating System: Ubuntu 22.04 LTS

1. Objective

The objective of this DR Drill is to:

  • Deploy Ubuntu VM in Indore (Primary)

  • Deploy Ubuntu VM in Mumbai (DR Site)

  • Install and configure rsync

  • Transfer application data from Indore to Mumbai

  • Verify successful replication

  • Validate DR readiness

2. Architecture Overview

Component
Region
Purpose

Primary VM

Region A

Source Server

DR VM

Region B

Disaster Recovery Server

rsync over SSH

Secure Channel

Data Replication

3. Prerequisites

Before starting the DR drill, ensure the following:

Infrastructure Requirements

  • 1 Ubuntu VM in Indore region

  • 1 Ubuntu VM in Mumbai region

  • Public IP assigned to both VMs

  • Port 22 (SSH) open in Security Group

Access

  • Primary VM SSH Key → <PRIMARY_KEY>.pem

  • DR VM SSH Key → <DR_KEY>.pem

  • Laptop with SSH access enabled

4. Phase 1 : Connect to Primary VM & Install rsync


Step 1 : Connect to Primary VM(ssh)

Run from Local Laptop / PowerShell / Terminal(cmd)


Step 2 : Update System

Run inside Primary VM(indore region)


Step 3 : Install rsync

Run inside Primary VM

Expected output:


5. Phase 2 : Create Test Data on Primary VM


Step 4 : Create Test Directory and Files

Run inside Primary VM


Step 5 : Verify Data Creation

Run inside Primary VM

Expected Output:

7. Phase 3 :Prepare SSH Access to DR VM (Mumbai region)


Step 6 : Exit Primary VM

Run inside Primary VM


Step 7: Copy DR SSH Key to Primary VM

Run from Local Laptop


Step 8: Login Back to Primary VM


Step 9: Set Proper Permission


8. Phase 4 : Transfer Data from Primary to DR


Step 10: Execute rsync

Run inside Primary VM

Expected Output:


9. Phase 5 : Verify Data on DR VM


Step 11: Login to DR VM( Mumbai region)

Run from Local Laptop


Step 12: Verify Transferred Data

Run inside DR VM

Expected Output:

10. Disaster Simulation (Optional)

To simulate failure:

  • Stop Primary VM

  • Or Block SSH in Security Group

Then confirm DR VM remains accessible.

Last updated