Task Statement 4.3: Design cost-optimized database solutions.

📘AWS Certified Solutions Architect – (SAA-C03)

1. What is Backup and Retention?

Backup

A backup is a copy of your data stored separately so that it can be restored if data is lost, corrupted, or deleted.

Retention Policy

A retention policy defines:

How long backups are kept
When backups are deleted automatically

2. Why Backup and Retention Matter

In AWS architecture, backups are needed for:

Data recovery (accidental deletion, corruption)
Disaster recovery
Compliance requirements
Business continuity

However:

Too many backups = high cost
Too few backups = risk of data loss

👉 The goal is to balance cost and recovery requirements

3. Types of Backups in AWS

3.1 Automated Backups

Managed by AWS
Enabled for services like:
- Amazon RDS
- Amazon DynamoDB
Includes:
- Daily snapshots
- Transaction logs (for point-in-time recovery)

Key Features:

Continuous backup
Point-in-time recovery (PITR)
Retention period configurable (e.g., 1–35 days for RDS)

3.2 Manual Backups (Snapshots)

Created manually by users
Do not expire automatically unless deleted
Used for long-term storage

Supported Services:

Amazon RDS
Amazon EBS
Amazon Redshift
Amazon Aurora

3.3 AWS Backup Service

A centralized backup solution for multiple services:

RDS
EBS
DynamoDB
EFS
FSx

Features:

Centralized backup policies
Cross-region backups
Lifecycle management
Automation

4. Snapshot Frequency (VERY IMPORTANT FOR EXAM)

Snapshot frequency determines how often backups are taken.

Common Strategies:

1. Frequent Snapshots

Taken every few minutes or hours
Used for:
- Critical databases
- High transaction systems

✔ Pros:

Minimal data loss

✘ Cons:

Higher storage cost

2. Daily Snapshots

Taken once per day

✔ Pros:

Balanced cost and recovery

✘ Cons:

Possible data loss between backups

3. Weekly/Monthly Snapshots

Used for long-term retention

✔ Pros:

Low cost

✘ Cons:

Not suitable for frequent recovery

Exam Tip:

High critical workload → frequent snapshots + PITR
Low critical workload → less frequent snapshots to save cost

5. Retention Policies (VERY IMPORTANT)

Retention defines how long backups are stored before deletion.

Key Concepts:

5.1 Short-Term Retention

Example: 7–35 days
Used for:
- Operational recovery
- Recent data restoration

5.2 Long-Term Retention

Example: months to years
Used for:
- Compliance
- Auditing

5.3 Lifecycle Policies

Automatically:

Move backups to cheaper storage (e.g., cold storage)
Delete old backups

👉 This is critical for cost optimization

6. Point-in-Time Recovery (PITR)

Allows restoring data to any specific time within retention period.

Supported by:

Amazon RDS
Amazon DynamoDB

How it works:

Uses:
- Continuous backups
- Transaction logs

✔ Very low data loss
✔ Higher storage cost

7. Backup Storage Optimization (Cost-Focused)

7.1 Incremental Backups

Only changes since last backup are stored
Used in:
- Amazon EBS snapshots

✔ Reduces storage cost significantly

7.2 Deduplication

Avoids storing duplicate data blocks

7.3 Compression

Reduces storage size

7.4 Cold Storage Tier

Move old backups to cheaper storage
Example:
- AWS Backup cold storage

✔ Much lower cost
✘ Higher retrieval time

8. Cross-Region and Cross-Account Backups

Cross-Region Backup

Copies backup to another AWS region
Used for:
- Disaster recovery

Cross-Account Backup

Protects against account-level failure or compromise

9. Backup Policies Using AWS Backup

You can define:

Backup frequency (e.g., daily at midnight)
Retention period (e.g., 30 days)
Lifecycle rules (move to cold storage after 7 days)

Benefits:

Automation
Consistency
Cost control

10. Key AWS Services and Their Backup Features

Amazon RDS

Automated backups (1–35 days)
Manual snapshots (indefinite)
PITR supported

Amazon DynamoDB

PITR (up to 35 days)
On-demand backups

Amazon EBS

Snapshot-based backups
Incremental storage

Amazon S3

Versioning for backup
Lifecycle policies
Cross-region replication

11. Designing a Cost-Optimized Backup Strategy

To design properly, consider:

1. Data Criticality

High → frequent backups + long retention
Low → fewer backups + short retention

2. Recovery Objectives

RPO (Recovery Point Objective)
→ How much data loss is acceptable
RTO (Recovery Time Objective)
→ How fast data must be restored

3. Storage Cost Optimization

Use incremental backups
Use lifecycle policies
Move old backups to cold storage
Delete unnecessary snapshots

12. Common Exam Scenarios

Scenario 1:

Need minimal data loss
👉 Use:

Frequent snapshots
PITR

Scenario 2:

Need to reduce cost
👉 Use:

Less frequent backups
Lifecycle policies
Cold storage

Scenario 3:

Need long-term compliance
👉 Use:

Manual snapshots
Long retention

Scenario 4:

Need disaster recovery
👉 Use:

Cross-region backups

13. Important Exam Tips (Must Remember)

Automated backups = limited retention
Manual snapshots = kept until deleted
EBS snapshots = incremental (cost-efficient)
Use AWS Backup for centralized management
Always combine:
- Snapshot frequency + retention + lifecycle policies

14. Quick Summary

Backup = copy of data
Retention = how long backup is stored
Snapshot frequency = how often backup is taken
PITR = restore to any time
Lifecycle policies = optimize cost
Incremental backups = reduce storage cost