TH9 ‐ DISASTER RECOVERY ‐ requirement, benefits, consideration - DevWithNehaCloud/Oracle-Cloud-Infrastructure-wiki GitHub Wiki

Disaster Recovery (DR) in Oracle Cloud Infrastructure (OCI)

Overview

Disaster Recovery (DR) is a strategy and set of processes used to recover applications, data, and infrastructure after a disruptive event such as a regional outage, hardware failure, cyberattack, or natural disaster.

The primary goal of Disaster Recovery is to ensure business continuity by minimizing:

  • Downtime (RTO)
  • Data Loss (RPO)

In OCI, Disaster Recovery is typically implemented by maintaining resources in a secondary region and failing over workloads when the primary region becomes unavailable.

Disaster Recovery ensures that critical business applications remain available even during major outages.

Why Disaster Recovery is Required

Organizations rely on applications and data for daily operations. A disaster can lead to:

  • Application downtime
  • Revenue loss
  • Data loss
  • Customer dissatisfaction
  • Compliance issues

Disaster Recovery helps organizations quickly restore services and continue business operations.

Common Disaster Scenarios

Infrastructure Failure

Examples:

  • Compute instance failure
  • Storage failure
  • Network device failure

Regional Outage

Examples:

  • OCI region unavailable
  • Major power outage
  • Data center disruption

Human Error

Examples:

  • Accidental resource deletion
  • Incorrect configuration changes

Cyber Security Incidents

Examples:

  • Ransomware attacks
  • Malware infections
  • Data corruption

Natural Disasters

Examples:

  • Floods
  • Earthquakes
  • Fire incidents

Key DR Objectives

Recovery Time Objective (RTO)

Defines:

How quickly the application must be restored after a disaster.

Example:

RTO = 30 Minutes

The application must be available again within 30 minutes.

Recovery Point Objective (RPO)

Defines:

How much data loss is acceptable after a disaster.

Example:

RPO = 5 Minutes

Maximum acceptable data loss is 5 minutes.

Disaster Recovery Architecture

Primary Region (Mumbai)
        |
        | Replication
        |
        v
DR Region (Hyderabad)

Primary Site  --->  Secondary Site

OCI Components Used in DR

Networking

  • DRG (Dynamic Routing Gateway)
  • Remote Peering Gateway (RPG)
  • FastConnect
  • IPSec VPN

Compute

  • Compute Instances
  • Custom Images
  • Instance Configurations

Storage

  • Block Volume Backups
  • Cross-Region Copy
  • Object Storage Replication

Database

  • Data Guard
  • Autonomous Database DR
  • Cross-Region Replication

Load Balancer

  • Regional Load Balancer
  • Traffic Redirection During Failover

Benefits of Disaster Recovery

1. Business Continuity

Applications remain available even during outages.

Example

If Mumbai region becomes unavailable, users can access the application from Hyderabad.

2. Reduced Downtime

Services can be restored quickly.

Example

RTO reduced from several hours to 30 minutes.

3. Reduced Data Loss

Replication helps protect critical business data.

Example

RPO of 5 minutes limits transaction loss.

4. Improved Customer Experience

Customers continue accessing services during disruptions.

5. Regulatory Compliance

Many industries require DR planning and testing.

Examples:

  • Banking
  • Healthcare
  • Insurance
  • Government

6. Increased Reliability

Provides resilience against regional failures.

DR Design Considerations

Before implementing DR, organizations should evaluate several factors.

1. Business Requirements

Determine:

  • Critical applications
  • Recovery expectations
  • Business impact

Questions:

How much downtime is acceptable?
How much data loss is acceptable?

2. Define RTO and RPO

Example:

RTO = 30 Minutes
RPO = 5 Minutes

These values influence the DR architecture and replication strategy.

3. Region Selection

Choose a DR region geographically separate from the primary region.

Example:

Primary Region  : Mumbai
DR Region       : Hyderabad

This protects against regional disasters.

4. Replication Strategy

Examples:

  • Block Volume Backup Copy
  • Object Storage Replication
  • Data Guard
  • Cross-Region Replication

5. Network Connectivity

Ensure connectivity between regions.

Options:

  • Remote Peering Gateway (RPG)
  • FastConnect
  • IPSec VPN

6. Security

Ensure security controls exist in both regions.

Examples:

  • IAM Policies
  • Security Lists
  • NSGs
  • Vault Keys

7. Cost Considerations

DR environments increase infrastructure costs.

Organizations must balance:

  • Recovery requirements
  • Budget constraints

8. DR Testing

Regular testing is essential.

Examples:

  • Failover Testing
  • Recovery Testing
  • Backup Restoration Testing

A DR plan that is never tested may fail during an actual disaster.

DR Deployment Models

Backup and Restore

Characteristics

  • Lowest cost
  • Longest recovery time

Example:

Backups stored in Hyderabad
Restore resources when disaster occurs

Suitable for:

  • Non-critical workloads

Pilot Light

Characteristics

  • Critical components running in DR
  • Faster recovery

Example:

Database replicated
Application servers started only during failover

Suitable for:

  • Medium-critical applications

Warm Standby

Characteristics

  • Smaller version of production environment running

Example:

Application and database running in DR region
Reduced capacity

Suitable for:

  • Business-critical applications

Active-Active

Characteristics

  • Production running in both regions

Example:

Mumbai and Hyderabad both serve traffic

Suitable for:

  • Mission-critical applications

Highest cost but lowest downtime.

Real-World OCI Example

Food Delivery Application

Primary Region:

Mumbai

DR Region:

Hyderabad

Infrastructure:

Load Balancer
Web Servers
Application Servers
Database
Object Storage

DR Strategy:

Database replicated using Data Guard
Object Storage replicated
Backups copied to Hyderabad
Remote Peering configured

Disaster Scenario:

Mumbai region outage

Action:

Failover to Hyderabad
Redirect users to DR environment

Result:

Application restored within 30 minutes
Maximum data loss less than 5 minutes

Interview Answer

What is Disaster Recovery in OCI?

Disaster Recovery is a strategy used to recover applications, infrastructure, and data after a disaster such as a regional outage, hardware failure, or cyberattack. Its primary objectives are to minimize downtime (RTO) and data loss (RPO). In OCI, DR can be implemented using cross-region backups, Data Guard, Object Storage replication, Remote Peering Gateways, and standby environments. For example, if the primary environment is hosted in Mumbai and a disaster occurs, workloads can be failed over to a DR environment in Hyderabad to maintain business continuity.