Disaster recovery strategies (backup, pilot light, warm standby) in AWS - Time & Space Complexity

Time Complexity: Disaster recovery strategies (backup, pilot light, warm standby)

O(n)

Understanding Time Complexity

When planning disaster recovery in the cloud, it's important to know how the time to recover grows as your data or resources increase.

We want to understand how the recovery steps scale with the size of your infrastructure.

Scenario Under Consideration

Analyze the time complexity of these disaster recovery strategies.

// Backup: Periodic snapshots of data
// Pilot Light: Minimal core system running
// Warm Standby: Scaled-down duplicate environment

// Recovery involves restoring data and starting services
    

This sequence shows the main steps in each strategy to recover after a failure.

Identify Repeating Operations

Look at what actions happen repeatedly during recovery.

• Primary operation: Restoring data from backups or snapshots.
• How many times: Depends on the amount of data and number of services to restart.

How Execution Grows With Input

As your data size and number of services grow, the recovery time grows roughly in proportion.

Input Size (n)	Approx. Recovery Steps
10 GB data, 2 services	Few restore and start operations
100 GB data, 10 services	Many restore and start operations
1 TB data, 50 services	Much more restore and start operations

Pattern observation: Recovery time grows roughly linearly with data size and number of services.

Final Time Complexity

Time Complexity: O(n)

This means recovery time grows in a straight line as your data and services increase.

Common Mistake

[X] Wrong: "Recovery time stays the same no matter how much data or how many services I have."

[OK] Correct: More data and services mean more to restore and start, so recovery takes longer.

Interview Connect

Understanding how recovery time grows helps you design better disaster plans and explain your choices clearly.

Self-Check

"What if we used a full warm standby environment instead of pilot light? How would the recovery time complexity change?"

Practice

1. Which disaster recovery strategy involves keeping a minimal version of your environment running to quickly scale up after a failure?

easy

A. Pilot light

B. Backup

C. Warm standby

D. Cold standby

Solution

1. Step 1: Understand pilot light strategy

   Pilot light keeps a minimal core of your environment running, like a small copy of critical systems.

2. Step 2: Compare with other strategies

   Backup stores data but requires full rebuild; warm standby runs a scaled-down version ready to take over; cold standby is offline.

3. Final Answer:

   Pilot light -> Option A

4. Quick Check:

   Minimal running core = Pilot light [OK]

Hint: Minimal running core means pilot light strategy [OK]

Common Mistakes:

• Confusing warm standby with pilot light
• Thinking backup keeps systems running
• Assuming cold standby is always active

2. Which AWS service is commonly used to create backups for disaster recovery?

easy

A. Amazon S3

B. Amazon EC2

C. AWS Lambda

D. Amazon VPC

Solution

1. Step 1: Identify backup storage service

   Amazon S3 is designed for durable, scalable storage, ideal for backups.

2. Step 2: Exclude other services

   EC2 is compute, Lambda is serverless code, VPC is networking, none are primarily for backups.

3. Final Answer:

   Amazon S3 -> Option A

4. Quick Check:

   Backup storage = Amazon S3 [OK]

Hint: Backup storage in AWS is Amazon S3 [OK]

Common Mistakes:

• Choosing EC2 as backup storage
• Confusing Lambda with storage
• Selecting VPC for backups

3. Given a warm standby setup in AWS, which of the following best describes its state before a disaster occurs?

medium

A. Fully scaled production environment running in parallel

B. Minimal core systems running, rest offline

C. No environment running, only backups stored

D. Scaled-down but fully functional environment running

Solution

1. Step 1: Understand warm standby state

   Warm standby runs a scaled-down but fully functional environment ready to take over quickly.

2. Step 2: Compare with other options

   Fully scaled parallel is active-active, minimal core is pilot light, no environment is backup only.

3. Final Answer:

   Scaled-down but fully functional environment running -> Option D

4. Quick Check:

   Warm standby = scaled-down functional environment [OK]

Hint: Warm standby runs scaled-down functional environment [OK]

Common Mistakes:

• Confusing warm standby with full production
• Mixing pilot light with warm standby
• Thinking backup means no running environment

4. You set up a pilot light disaster recovery strategy but notice recovery time is longer than expected. What is the most likely cause?

medium

A. Backups are stored in Amazon S3

B. The pilot light environment is not fully configured and requires manual scaling

C. Warm standby environment is running at full capacity

D. The primary environment is still active

Solution

1. Step 1: Analyze pilot light recovery process

   Pilot light requires scaling up minimal systems to full production, so incomplete setup delays recovery.

2. Step 2: Exclude unrelated options

   Backups in S3 are normal; warm standby running full is unrelated; primary active is normal operation.

3. Final Answer:

   The pilot light environment is not fully configured and requires manual scaling -> Option B

4. Quick Check:

   Pilot light slow recovery = incomplete setup [OK]

Hint: Incomplete pilot light setup causes slow recovery [OK]

Common Mistakes:

• Blaming backups for slow recovery
• Confusing warm standby with pilot light
• Assuming primary environment affects recovery time

5. A company wants a disaster recovery solution that balances cost and recovery speed. They want a system running at all times but at reduced capacity, ready to scale up quickly. Which strategy should they choose?

hard

A. Backup only

B. Pilot light

C. Warm standby

D. Cold standby

Solution

1. Step 1: Understand company needs

   They want a running system at reduced capacity that can scale quickly, balancing cost and speed.

2. Step 2: Match needs to strategies

   Backup only is slow recovery; pilot light is minimal core only; cold standby is offline; warm standby runs scaled-down environment ready to scale.

3. Final Answer:

   Warm standby -> Option C

4. Quick Check:

   Running reduced capacity system = Warm standby [OK]

Hint: Running reduced capacity system means warm standby [OK]

Common Mistakes:

• Choosing pilot light for running full system
• Confusing backup with standby strategies
• Selecting cold standby for fast recovery