Why Backup and restore in GCP? - Purpose & Use Cases

The Big Idea

What if your important data vanished tomorrow--would you be ready to get it back fast?

The Scenario

Imagine you run a small online store and keep all your customer orders in a spreadsheet on your computer. One day, your computer crashes or the file gets accidentally deleted. You have no copy saved anywhere else.

Now, all your order data is lost, and you have no way to get it back quickly.

The Problem

Manually copying files or data to save backups is slow and easy to forget. It's hard to keep track of which backup is the latest. If you make a mistake, you might overwrite good data or lose important information.

When disaster strikes, restoring data manually can take hours or days, causing stress and lost business.

The Solution

Backup and restore services in the cloud automatically save copies of your data at regular intervals. They keep multiple versions so you can choose which one to restore. When you need to recover, you can quickly get your data back with just a few clicks.

This removes the worry of losing data and saves you time and effort.

Before vs After

✗ Before

Copy files to USB drive every day
Keep track of dates manually

✓ After

Use GCP Backup service to schedule automatic backups
Restore data from console or API easily

What It Enables

You can protect your data effortlessly and recover from failures quickly, keeping your business running smoothly.

Real Life Example

A company uses GCP Backup to save daily snapshots of their database. When a software bug deletes some records, they restore the database to the previous day's snapshot within minutes, avoiding major losses.

Key Takeaways

Manual backups are slow, risky, and easy to forget.

Cloud backup services automate saving and restoring data.

This ensures fast recovery and peace of mind.

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