RDS backup and snapshots in AWS - Step-by-Step Execution

Process Flow - RDS backup and snapshots

Create RDS Instance

↓

Enable Automated Backups

↓

RDS Automatically Takes Daily Snapshots

↓

User Creates Manual Snapshot (Optional)

↓

Snapshots Stored in S3 Managed by AWS

↓

Restore from Snapshot When Needed

↓

New RDS Instance Created from Snapshot

This flow shows how RDS instances have automated backups and optional manual snapshots, which are stored safely and can be used to restore databases.

Execution Sample

AWS

aws rds create-db-instance --db-instance-identifier mydb
aws rds modify-db-instance --db-instance-identifier mydb --backup-retention-period 7
aws rds create-db-snapshot --db-instance-identifier mydb --db-snapshot-identifier mydb-snap1
aws rds restore-db-instance-from-db-snapshot --db-instance-identifier mydb-restored --db-snapshot-identifier mydb-snap1

This sequence creates an RDS instance, enables backups, creates a manual snapshot, and restores a new instance from that snapshot.

Process Table

Step	Action	AWS Service Response	Resulting State
1	Create RDS instance 'mydb'	DB instance 'mydb' created	RDS instance 'mydb' is running without backups
2	Enable automated backups with 7 days retention	Backup retention set to 7 days	Automated daily backups enabled for 'mydb'
3	AWS takes daily automated snapshot	Snapshot 'mydb-automated-YYYYMMDD' created	Daily snapshot stored in AWS managed storage
4	User creates manual snapshot 'mydb-snap1'	Snapshot 'mydb-snap1' created	Manual snapshot stored and available
5	Restore new instance 'mydb-restored' from 'mydb-snap1'	DB instance 'mydb-restored' created from snapshot	New RDS instance running with data from snapshot
6	End	No further actions	Ready for use or further backups

💡 Process ends after restoring new instance from snapshot

Status Tracker

Resource	Initial State	After Step 1	After Step 2	After Step 4	After Step 5	Final State
RDS Instance 'mydb'	Not created	Running without backups	Running with automated backups	Running with automated backups	Running with automated backups	Running with automated backups
Snapshots	None	None	Automated daily snapshots start	Manual snapshot 'mydb-snap1' added	Manual snapshot 'mydb-snap1' present	Manual and automated snapshots present
RDS Instance 'mydb-restored'	Not created	Not created	Not created	Not created	Running restored from 'mydb-snap1'	Running restored from 'mydb-snap1'

Key Moments - 3 Insights

Why do automated backups start only after enabling backup retention?

Automated backups require a retention period greater than zero to be enabled, as shown in step 2 of the execution_table where backups start only after setting retention.

What is the difference between automated backups and manual snapshots?

Automated backups happen daily and are managed by AWS automatically (step 3), while manual snapshots are created by the user on demand and kept until deleted (step 4).

Can you restore an RDS instance from an automated backup directly?

You restore from snapshots, which include automated backups converted to snapshots by AWS. Step 5 shows restoring from a manual snapshot, but automated snapshots can also be used similarly.

Visual Quiz - 3 Questions

Look at the execution_table, what is the state of 'mydb' after step 2?

A Running without backups

B Running with automated backups enabled

C Not created yet

D Restored from snapshot

💡 Hint

Check the 'Resulting State' column for step 2 in the execution_table

At which step does the manual snapshot 'mydb-snap1' get created?

A Step 1

B Step 3

C Step 4

D Step 5

💡 Hint

Look for the action mentioning manual snapshot creation in the execution_table

If backup retention was set to 0, what would change in the execution flow?

A Automated backups would not start

B Manual snapshots would be disabled

C Restoring from snapshots would fail

D RDS instance would not be created

💡 Hint

Refer to key_moments about enabling automated backups and retention period

Concept Snapshot

RDS backups include automated daily snapshots and manual snapshots.
Enable automated backups by setting backup retention period > 0.
Manual snapshots are user-triggered and kept until deleted.
Snapshots are stored safely by AWS and used to restore instances.
Restoring creates a new RDS instance from a snapshot.

Full Transcript

This visual execution shows how AWS RDS handles backups and snapshots. First, you create an RDS instance. Then you enable automated backups by setting a backup retention period. AWS takes daily automated snapshots stored safely. Users can create manual snapshots anytime. These snapshots can be used to restore a new RDS instance with the saved data. The execution table traces each step and state change. Key moments clarify common confusions about backup enabling and snapshot types. The quiz tests understanding of states and actions in the process.

Practice

1. What is the main difference between automated backups and manual snapshots in AWS RDS?

easy

A. Automated backups are stored outside AWS; manual snapshots are stored inside AWS.

B. Automated backups happen daily and expire; manual snapshots are created on demand and kept until deleted.

C. Automated backups are created only when the user requests; manual snapshots happen automatically every hour.

D. Automated backups cannot be restored; manual snapshots can only be viewed.

Solution

1. Step 1: Understand automated backups

   Automated backups run daily and keep data for a set retention period, after which they expire automatically.

2. Step 2: Understand manual snapshots

   Manual snapshots are created by the user anytime and remain until explicitly deleted.

3. Final Answer:

   Automated backups happen daily and expire; manual snapshots are created on demand and kept until deleted. -> Option B

4. Quick Check:

   Backup type difference = Automated expire, manual keep [OK]

Hint: Automated expire, manual keep until delete [OK]

Common Mistakes:

• Thinking manual snapshots expire automatically
• Believing automated backups are user-triggered only
• Confusing storage location of backups and snapshots

2. Which AWS CLI command correctly creates a manual snapshot of an RDS instance named mydbinstance?

easy

A. aws rds create-db-snapshot --db-instance-identifier mydbinstance --db-snapshot-identifier mydbsnapshot

B. aws rds backup-db-instance --instance mydbinstance --snapshot mydbsnapshot

C. aws rds snapshot-create --db-instance mydbinstance --snapshot-name mydbsnapshot

D. aws rds make-snapshot --db-instance-id mydbinstance --snapshot-id mydbsnapshot

Solution

1. Step 1: Identify correct AWS CLI syntax

   The correct command to create a manual snapshot is aws rds create-db-snapshot with required flags.

2. Step 2: Match parameters

   Use --db-instance-identifier for the instance and --db-snapshot-identifier for the snapshot name.

3. Final Answer:

   aws rds create-db-snapshot --db-instance-identifier mydbinstance --db-snapshot-identifier mydbsnapshot -> Option A

4. Quick Check:

   Correct CLI command = aws rds create-db-snapshot --db-instance-identifier mydbinstance --db-snapshot-identifier mydbsnapshot [OK]

Hint: Use create-db-snapshot with instance and snapshot IDs [OK]

Common Mistakes:

• Using incorrect command verbs like backup-db-instance
• Mixing parameter names like --snapshot-name instead of --db-snapshot-identifier
• Assuming snapshot creation is automatic without command

3. Given this AWS CLI output snippet after running aws rds describe-db-snapshots --db-instance-identifier mydbinstance:

{
  "DBSnapshots": [
    {"DBSnapshotIdentifier": "snapshot1", "Status": "available"},
    {"DBSnapshotIdentifier": "snapshot2", "Status": "creating"}
  ]
}

What does the status "creating" mean for snapshot2?

medium

A. "snapshot2" is currently being created and not ready for restore.

B. "snapshot2" is ready and can be used to restore the database.

C. "snapshot2" creation failed and needs retry.

D. "snapshot2" is deleted but still listed temporarily.

Solution

1. Step 1: Understand snapshot status meanings

   Status "creating" means the snapshot process is in progress and not yet complete.

2. Step 2: Interpret the impact on usage

   While "creating", the snapshot cannot be used for restore until status changes to "available".

3. Final Answer:

   "snapshot2" is currently being created and not ready for restore. -> Option A

4. Quick Check:

   Status creating = snapshot in progress [OK]

Hint: Creating means snapshot not ready yet [OK]

Common Mistakes:

• Assuming creating means snapshot is ready
• Confusing creating with failed or deleted status
• Thinking snapshot is deleted but still listed

4. You wrote this AWS CLI command to create a manual snapshot but got an error:

aws rds create-db-snapshot --db-instance-identifier mydbinstance

What is missing that causes the error?

medium

A. The --region parameter is required for all commands.

B. The --db-instance-identifier value is incorrect and must be the snapshot name.

C. The --db-snapshot-identifier parameter with a snapshot name is missing.

D. The command must be run with sudo privileges.

Solution

1. Step 1: Check required parameters for create-db-snapshot

   The command requires both --db-instance-identifier and --db-snapshot-identifier to name the snapshot.

2. Step 2: Identify missing parameter

   The command lacks --db-snapshot-identifier, so AWS cannot create the snapshot without a name.

3. Final Answer:

   The --db-snapshot-identifier parameter with a snapshot name is missing. -> Option C

4. Quick Check:

   Missing snapshot ID causes error [OK]

Hint: Always provide snapshot name with --db-snapshot-identifier [OK]

Common Mistakes:

• Forgetting to specify snapshot identifier
• Assuming region is always mandatory
• Thinking sudo is needed for AWS CLI commands

5. You want to keep daily backups of your RDS instance for 7 days automatically and also keep a manual snapshot before a major update that you want to keep indefinitely. Which combination of settings and actions achieves this?

hard

A. Create a manual snapshot daily and delete old ones after 7 days; no automated backups.

B. Disable automated backups and create 7 manual snapshots daily plus one before update.

C. Enable automated backups with 7-day retention and rely only on them for the update.

D. Enable automated backups with 7-day retention and create a manual snapshot before update.

Solution

1. Step 1: Set automated backups retention

   Enable automated backups with a 7-day retention period to keep daily backups automatically.

2. Step 2: Create manual snapshot before update

   Manually create a snapshot before the update to keep a permanent backup unaffected by retention.

3. Final Answer:

   Enable automated backups with 7-day retention and create a manual snapshot before update. -> Option D

4. Quick Check:

   Automated + manual snapshot = daily + permanent backup [OK]

Hint: Automated backups expire; manual snapshots keep forever [OK]

Common Mistakes:

• Disabling automated backups losing daily backups
• Relying only on automated backups for permanent backup
• Manually creating many snapshots instead of using automated backups