Backend interview prep

Start

Backup and Recovery Interview Questions and Answers

Learn Backup and Recovery concepts including backup types, recovery strategies, snapshots, replication, RPO, RTO, disaster recovery, and production best practices with diagrams and interview questions.

Module Navigation

Previous: Storage Lifecycle QA | Parent: Storage Learning Path | Next: Storage Best Practices QA

Backup and Recovery Interview Questions and Answers

Cloud Interview Track

Storage Module — Lesson 07 of 08

Introduction

Backup and Recovery are essential components of every cloud architecture.

A backup strategy protects data from:

  • Accidental deletion
  • Hardware failure
  • Software bugs
  • Ransomware attacks
  • Natural disasters
  • Human errors

Recovery ensures applications and data can be restored quickly with minimal business impact.

Backup and Recovery Overview

flowchart LR

Application --> ProductionData

ProductionData --> Backup

Backup --> Recovery

Recovery --> ProductionData

What is Backup?

A backup is a separate copy of data created so that it can be restored if the original data becomes unavailable or corrupted.

A good backup strategy should be:

  • Automated
  • Secure
  • Tested
  • Versioned
  • Geographically redundant

Why Backups Are Important

Without backups, organizations risk:

  • Permanent data loss
  • Long outages
  • Compliance violations
  • Financial loss
  • Customer dissatisfaction

Benefits include:

  • Business continuity
  • Disaster recovery
  • Compliance
  • Data protection
  • Faster recovery

Types of Backups

Full Backup

Copies all selected data.

Advantages

  • Simplest recovery
  • Easy to manage

Disadvantages

  • Largest storage usage
  • Long backup time

Incremental Backup

Backs up only changes since the previous backup.

Advantages

  • Fast backup
  • Lower storage cost

Disadvantages

  • Slower recovery
  • Depends on backup chain

Differential Backup

Backs up all changes since the last full backup.

Advantages

  • Faster recovery than incremental
  • Less storage than full backup

Disadvantages

  • Backup size grows over time

Backup Types

flowchart TB

FullBackup --> Incremental --> Differential

Snapshot vs Backup

Snapshot Backup
Point-in-time copy Separate recoverable copy
Fast creation Longer process
Same storage system Independent storage
Fast restore Disaster recovery
Not a replacement for backup Recommended for recovery

Recovery Process

flowchart LR

Failure --> Detect --> Restore --> Validate --> Production

RPO (Recovery Point Objective)

RPO defines the maximum acceptable amount of data loss measured in time.

Example:

  • RPO = 15 Minutes

A system can lose at most 15 minutes of data.

RTO (Recovery Time Objective)

RTO defines the maximum acceptable downtime before the application must be restored.

Example:

  • RTO = 30 Minutes

The application should be operational within 30 minutes after failure.

RPO vs RTO

RPO RTO
Data Loss Downtime
Time Between Backups Time to Restore
Measured in Minutes/Hours Measured in Minutes/Hours

Backup Architecture

flowchart TB

Application

Application --> PrimaryStorage

PrimaryStorage --> Snapshot

PrimaryStorage --> BackupVault

BackupVault --> SecondaryRegion

Disaster Recovery Levels

Backup and Restore

Lowest cost

Longest recovery time

Pilot Light

Critical services remain running.

Warm Standby

Reduced-capacity environment remains available.

Multi-Site Active

Multiple production environments operate simultaneously.

Highest availability.

Disaster Recovery Architecture

flowchart LR

PrimaryRegion --> Backup

Backup --> SecondaryRegion

SecondaryRegion --> Recovery

Cloud Backup Services

AWS

  • AWS Backup
  • EBS Snapshots
  • S3 Versioning
  • AWS Elastic Disaster Recovery

Microsoft Azure

  • Azure Backup
  • Recovery Services Vault
  • Azure Site Recovery

Google Cloud

  • Backup and DR Service
  • Persistent Disk Snapshots
  • Cloud Storage Versioning

Replication vs Backup

Replication Backup
High Availability Disaster Recovery
Near Real-time Scheduled
Replicates Errors Recover Previous Versions
Supports Failover Supports Restore

Replication improves availability but does not replace backups.

Backup Lifecycle

flowchart LR

Create --> Backup --> Archive --> Delete

Production Architecture

flowchart TB

Users --> Application

Application --> Database

Database --> PrimaryDisk

PrimaryDisk --> Snapshot

Snapshot --> BackupVault

BackupVault --> Archive

Archive --> SecondaryRegion

Production Use Case

Banking Transaction System

Component Backup Strategy
Database Daily Full + Hourly Incremental
Customer Documents Versioned Object Storage
Application Servers Image Backup
Configuration Source Control + Backup
Disaster Recovery Cross-Region Replication

Best Practices

  • Automate backups.
  • Encrypt backup data.
  • Test recovery regularly.
  • Store backups in multiple locations.
  • Follow the 3-2-1 backup rule.
  • Enable versioning.
  • Monitor backup failures.
  • Define RPO and RTO.
  • Retain backups according to compliance requirements.
  • Protect backups from ransomware.

The 3-2-1 Backup Rule

  • 3 copies of your data.
  • 2 different storage media.
  • 1 copy stored offsite or in another region/cloud.

Interview Questions

1. What is a backup?

Answer

A backup is a separate copy of data created to restore information if the original data is lost, corrupted, or deleted.

2. Why are backups important?

Answer

Backups protect against hardware failures, accidental deletion, cyberattacks, software failures, and disasters while ensuring business continuity.

3. What are the different types of backups?

Answer

  • Full Backup
  • Incremental Backup
  • Differential Backup

Each balances backup time, storage usage, and recovery speed differently.

4. What is the difference between incremental and differential backups?

Answer

Incremental backups store changes since the last backup, while differential backups store all changes since the last full backup.

Incremental backups use less storage but require a longer recovery chain.

5. What is the difference between a snapshot and a backup?

Answer

Snapshots are fast point-in-time copies stored within the storage system, while backups are independent copies designed for long-term recovery and disaster recovery.

6. What is RPO?

Answer

Recovery Point Objective (RPO) is the maximum acceptable amount of data loss measured in time.

7. What is RTO?

Answer

Recovery Time Objective (RTO) is the maximum acceptable downtime before services must be restored.

8. What is disaster recovery?

Answer

Disaster Recovery (DR) is the strategy for restoring applications and data after major failures such as natural disasters, cyberattacks, or infrastructure outages.

9. What is the 3-2-1 backup rule?

Answer

Maintain three copies of data, store them on two different storage media, and keep one copy offsite.

10. Does replication replace backups?

Answer

No.

Replication copies data to another location for high availability, but it also replicates accidental deletions or corruption.

Backups provide recoverable historical versions.

11. What cloud backup services are available?

Answer

  • AWS Backup
  • Azure Backup
  • Google Cloud Backup and DR
  • EBS Snapshots
  • Azure Recovery Services Vault
  • Persistent Disk Snapshots

12. What should a production backup strategy include?

Answer

Automated backups, encryption, versioning, cross-region copies, recovery testing, retention policies, monitoring, and clearly defined RPO and RTO.

13. How often should backups be tested?

Answer

Recovery testing should be performed regularly, such as quarterly or after major infrastructure changes, to ensure backups are usable.

14. What are common backup mistakes?

Answer

Not testing restores, relying only on snapshots, storing backups in the same location, ignoring encryption, and not monitoring backup failures.

15. How do you design a production backup and recovery solution?

Answer

Identify critical workloads, define RPO and RTO, automate backups, encrypt backup data, replicate backups to another region, enable monitoring, regularly test recovery procedures, and implement lifecycle policies for backup retention.

Common Mistakes

  • Relying only on snapshots.
  • Never testing restores.
  • Keeping backups in the same region.
  • Ignoring backup encryption.
  • Not monitoring failed backups.
  • No defined RPO or RTO.
  • No retention policy.
  • Deleting backups too early.

Quick Revision

Concept Purpose
Full Backup Complete copy of data
Incremental Backup Changes since last backup
Differential Backup Changes since last full backup
Snapshot Fast point-in-time copy
Backup Recoverable copy
RPO Maximum acceptable data loss
RTO Maximum acceptable downtime
Replication High availability
Disaster Recovery Restore after major failure
3-2-1 Rule Recommended backup strategy

Key Takeaways

  • Backups protect against data loss, corruption, ransomware, and disasters.
  • Full, incremental, and differential backups each provide different trade-offs between storage usage and recovery time.
  • Snapshots are useful for fast recovery but should not replace backups.
  • RPO defines acceptable data loss, while RTO defines acceptable downtime.
  • Replication improves availability but is not a substitute for backup.
  • Cloud providers offer managed backup and disaster recovery services.
  • A strong production strategy includes automation, encryption, versioning, cross-region protection, lifecycle management, and regular recovery testing.