Backup and restore in GCP - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the main purpose of backup in cloud infrastructure?

Backup is to create copies of data or system states to protect against data loss or corruption, allowing recovery if something goes wrong.

beginner

Name a common GCP service used for backing up virtual machine disks.

Google Cloud Compute Engine Snapshots are used to back up persistent disks attached to virtual machines.

intermediate

What is the difference between incremental and full backups?

A full backup copies all data every time. An incremental backup copies only data changed since the last backup, saving time and storage.

beginner

How does Google Cloud Storage help in backup and restore?

Google Cloud Storage provides durable, scalable storage to save backup files securely and retrieve them when needed for restore.

intermediate

Why is it important to test restore procedures regularly?

Testing restores ensures backups are valid and recovery works, preventing surprises during actual failures.

Which GCP service is best suited for backing up database snapshots?

A Cloud Functions

B Cloud SQL automated backups

C Cloud Pub/Sub

D Cloud Run

Cloud SQL automated backups create consistent backups of managed databases for restore.

What type of backup copies only data changed since the last backup?

A Incremental backup

B Differential backup

C Full backup

D Snapshot backup

Incremental backups copy only changes since the last backup, saving space and time.

Where should you store backups for best durability in GCP?

A Local VM disk

B Compute Engine instance memory

C Cloud Storage buckets

D Cloud DNS

Cloud Storage buckets provide durable, redundant storage ideal for backups.

What is a snapshot in GCP Compute Engine?

A A live copy of a VM instance

B A database export

C A network configuration backup

D A backup of a persistent disk at a point in time

Snapshots capture the state of a persistent disk at a specific time for backup or restore.

Why should backups be stored in a different location than the original data?

A To protect against site failures or disasters

B To improve network speed

C To increase data duplication

D To reduce storage costs

Storing backups separately protects data if the original site is damaged or lost.

Explain the key steps involved in backing up and restoring a virtual machine in GCP.

Think about how you save and recover your computer files but in the cloud.

Describe why regular testing of backup restore processes is critical in cloud infrastructure.

Imagine practicing a fire drill to be ready for a real fire.

Practice

1. What is the main purpose of creating a backup in Google Cloud SQL?

easy

A. To save a copy of your database data safely for recovery

B. To increase the speed of your database queries

C. To permanently delete old data from your database

D. To automatically update your database schema

Solution

1. Step 1: Understand backup purpose

   Backups are copies of data saved to protect against data loss.

2. Step 2: Identify backup use in Cloud SQL

   In Cloud SQL, backups allow restoring data if something goes wrong.

3. Final Answer:

   To save a copy of your database data safely for recovery -> Option A

4. Quick Check:

   Backup = Safe data copy [OK]

Hint: Backup means saving data safely for later recovery [OK]

Common Mistakes:

• Confusing backup with performance improvement
• Thinking backup deletes data
• Assuming backup changes database structure

2. Which gcloud command correctly creates an on-demand backup for a Cloud SQL instance named my-instance?

easy

A. gcloud sql backup create --name=my-instance

B. gcloud sql instances backup create my-instance

C. gcloud sql backups create --instance=my-instance

D. gcloud sql create backup --instance=my-instance

Solution

1. Step 1: Recall correct gcloud backup syntax

   The correct command to create a backup is gcloud sql backups create --instance=INSTANCE_NAME.

2. Step 2: Match command to instance name

   Replacing INSTANCE_NAME with my-instance gives the correct command.

3. Final Answer:

   gcloud sql backups create --instance=my-instance -> Option C

4. Quick Check:

   Backup command = gcloud sql backups create [OK]

Hint: Use 'gcloud sql backups create --instance=NAME' to backup [OK]

Common Mistakes:

• Using 'instances backup' instead of 'backups create'
• Incorrect flag names like --name instead of --instance
• Wrong command order or missing 'create'

3. Given this command output snippet after restoring a Cloud SQL backup:

Restoring backup 2024-06-01_12-00 to instance my-instance... DONE

What does this output indicate?

medium

A. The backup was successfully restored to the instance

B. The backup creation failed

C. The instance was deleted

D. The backup is scheduled for later restoration

Solution

1. Step 1: Read the command output carefully

   The message says 'Restoring backup ... DONE', indicating completion.

2. Step 2: Understand the meaning of 'DONE'

   'DONE' means the restore process finished successfully.

3. Final Answer:

   The backup was successfully restored to the instance -> Option A

4. Quick Check:

   Restore output 'DONE' = success [OK]

Hint: Look for 'DONE' to confirm successful restore [OK]

Common Mistakes:

• Confusing restore success with backup failure
• Assuming instance deletion from restore message
• Thinking restore is scheduled, not completed

4. You run the command gcloud sql backups create --instance=my-instance but get an error: ERROR: (gcloud.sql.backups.create) The instance does not support on-demand backups.
What is the most likely cause?

medium

A. You typed the instance name incorrectly

B. The Cloud SQL instance is a First Generation instance which does not support on-demand backups

C. You need to enable billing on your Google Cloud project

D. The backup command requires a different flag for on-demand backups

Solution

1. Step 1: Understand error message about backup support

   The error says the instance does not support on-demand backups.

2. Step 2: Recall Cloud SQL instance generations

   First Generation instances do not support on-demand backups; only Second Generation and later do.

3. Final Answer:

   The Cloud SQL instance is a First Generation instance which does not support on-demand backups -> Option B

4. Quick Check:

   First Gen instances lack on-demand backup support [OK]

Hint: Check instance generation; First Gen lacks on-demand backups [OK]

Common Mistakes:

• Assuming typo in instance name causes this error
• Thinking billing is the cause
• Believing backup flag is incorrect

5. You want to restore a Cloud SQL instance prod-db to a previous state using a backup from June 1, 2024. Which sequence of steps correctly achieves this with minimal downtime?

hard

A. Restore the backup directly to the current instance while it is serving traffic

B. Delete the current instance, then restore the backup to the same instance name immediately

C. Export the backup to Cloud Storage, then import it back to the instance

D. Create a new instance from the backup, then switch your application to use the new instance

Solution

1. Step 1: Understand restore options for minimal downtime

   Restoring directly to a live instance causes downtime; better to create a new instance.

2. Step 2: Create new instance from backup and switch traffic

   Create a new instance restored from backup, then update your app to use it, minimizing downtime.

3. Final Answer:

   Create a new instance from the backup, then switch your application to use the new instance -> Option D

4. Quick Check:

   New instance restore + switch = minimal downtime [OK]

Hint: Restore to new instance, then switch app to avoid downtime [OK]

Common Mistakes:

• Deleting instance before restore causing data loss
• Restoring live instance causing service interruption
• Using export/import which is slower and more complex