Object versioning in GCP - Commands & Configuration

Introduction

Sometimes files in cloud storage get overwritten or deleted by mistake. Object versioning helps keep old copies of files so you can recover them later.

When you want to keep backups of files automatically in cloud storage.

When multiple people edit files and you want to track changes over time.

When you want to protect important data from accidental deletion.

When you need to audit or review previous versions of files.

When you want to restore a file to an earlier state after a mistake.

Commands

This command turns on object versioning for the bucket named example-bucket. It means old versions of files will be kept when overwritten or deleted.

Terminal

gsutil versioning set on gs://example-bucket

Expected Output

Setting versioning configuration on gs://example-bucket/...

Success.

Uploads a file named file.txt to the bucket. If the file already exists, the old version is saved because versioning is on.

Terminal

gsutil cp file.txt gs://example-bucket/file.txt

Expected Output

Copying file.txt [Content-Type=text/plain]...

/ [1 files][   12.0 B/   12.0 B]                                 

Operation completed over 1 objects/12.0 B.

Uploads a new version of file.txt. The previous version is kept as a noncurrent version because versioning is enabled.

Terminal

gsutil cp file_v2.txt gs://example-bucket/file.txt

Expected Output

Copying file_v2.txt [Content-Type=text/plain]...

/ [1 files][   15.0 B/   15.0 B]                                 

Operation completed over 1 objects/15.0 B.

Lists all versions of file.txt in the bucket, including old versions saved by versioning.

Terminal

gsutil ls -a gs://example-bucket/file.txt

Expected Output

gs://example-bucket/file.txt#1589281234567890

gs://example-bucket/file.txt#1589281234567891

Downloads a specific old version of file.txt by its version ID to restore or review it.

Terminal

gsutil cp gs://example-bucket/file.txt#1589281234567890 restored_file.txt

Expected Output

Copying gs://example-bucket/file.txt#1589281234567890...

/ [1 files][   12.0 B/   12.0 B]                                 

Operation completed over 1 objects/12.0 B.

Key Concept

If you remember nothing else from this pattern, remember: turning on object versioning saves old copies of files automatically so you can recover them later.

Common Mistakes

Not enabling versioning before uploading files

Old versions won't be saved if versioning is off, so you can't recover previous file states.

Always enable versioning on the bucket before uploading files you want to keep versions of.

Trying to list versions without the -a flag

The command will only show the latest version, hiding older versions.

Use 'gsutil ls -a' to see all versions of an object.

Deleting files without specifying version ID

Deletes the latest version but older versions remain; this can cause confusion if you want to fully remove a file.

Specify version ID to delete specific versions or disable versioning if you want to stop keeping old versions.

Summary

Enable object versioning on a bucket to keep old copies of files automatically.

Upload files normally; old versions are saved when files are overwritten or deleted.

Use 'gsutil ls -a' to list all versions and specify version IDs to restore or delete specific versions.

Practice

1. What is the main purpose of enabling Object Versioning in a Google Cloud Storage bucket?

easy

A. To keep multiple versions of an object to recover from accidental deletion or overwrite

B. To increase the storage capacity of the bucket automatically

C. To encrypt objects with a stronger encryption key

D. To restrict access to objects based on user roles

Solution

1. Step 1: Understand Object Versioning concept

   Object Versioning allows storing multiple versions of the same object in a bucket.

2. Step 2: Identify the main benefit

   This helps recover previous versions if an object is deleted or overwritten by mistake.

3. Final Answer:

   To keep multiple versions of an object to recover from accidental deletion or overwrite -> Option A

4. Quick Check:

   Object Versioning = Data recovery [OK]

Hint: Versioning means saving old copies to recover later [OK]

Common Mistakes:

• Confusing versioning with encryption
• Thinking versioning increases storage automatically
• Assuming versioning controls access permissions

2. Which of the following commands correctly enables Object Versioning on a Google Cloud Storage bucket named my-bucket?

easy

A. gsutil versioning set on my-bucket

B. gsutil versioning enable gs://my-bucket

C. gsutil versioning set enabled gs://my-bucket

D. gsutil versioning set on gs://my-bucket

Solution

1. Step 1: Recall gsutil syntax for enabling versioning

   The correct command is gsutil versioning set on gs://bucket-name.

2. Step 2: Match the command to the bucket name

   gsutil versioning set on gs://my-bucket matches the correct syntax and bucket name format.

3. Final Answer:

   gsutil versioning set on gs://my-bucket -> Option D

4. Quick Check:

   Enable versioning = gsutil versioning set on [OK]

Hint: Use 'gsutil versioning set on gs://bucket' to enable [OK]

Common Mistakes:

• Omitting 'gs://' prefix
• Using 'enable' instead of 'set on'
• Adding extra words like 'enabled'

3. Consider a bucket with Object Versioning enabled. If you upload a file named report.txt three times with different content, how many versions of report.txt will exist in the bucket?

medium

A. 3

B. 1

C. 2

D. 4

Solution

1. Step 1: Understand versioning behavior on multiple uploads

   Each upload creates a new version if versioning is enabled.

2. Step 2: Count versions after three uploads

   Uploading three times creates three distinct versions of the same object.

3. Final Answer:

   3 -> Option A

4. Quick Check:

   Uploads = Versions when versioning on [OK]

Hint: Each upload creates a new version if versioning is enabled [OK]

Common Mistakes:

• Assuming only one version exists
• Counting versions as uploads minus one
• Confusing versions with copies

4. You enabled Object Versioning on a bucket but notice that old versions are not visible when listing objects. What is the most likely cause?

medium

A. Old versions are automatically deleted after 24 hours

B. Versioning was not actually enabled on the bucket

C. You used gsutil ls which only shows live versions by default

D. You need to enable versioning on each object separately

Solution

1. Step 1: Understand default listing behavior

   By default, gsutil ls shows only the current live versions, not older ones.

2. Step 2: How to list all versions

   Use gsutil ls -a to see all versions including old ones.

3. Final Answer:

   You used gsutil ls which only shows live versions by default -> Option C

4. Quick Check:

   Default list hides old versions [OK]

Hint: Use 'gsutil ls -a' to see all versions [OK]

Common Mistakes:

• Assuming versioning not enabled without checking
• Believing old versions auto-delete quickly
• Thinking versioning applies per object

5. You want to keep only the latest 5 versions of objects in a bucket with Object Versioning enabled to save storage costs. Which approach should you use?

hard

A. Disable Object Versioning and re-enable it every month

B. Set a lifecycle rule to delete noncurrent versions older than a certain age

C. Manually delete old versions using the Cloud Console every week

D. Rename objects to avoid creating new versions

Solution

1. Step 1: Understand lifecycle management for versioned objects

   Lifecycle rules can automatically delete old versions based on age or count.

2. Step 2: Choose the best automated approach

   Setting a lifecycle rule to delete noncurrent versions older than a set time saves costs without manual work.

3. Final Answer:

   Set a lifecycle rule to delete noncurrent versions older than a certain age -> Option B

4. Quick Check:

   Use lifecycle rules to manage old versions [OK]

Hint: Use lifecycle rules to auto-delete old versions [OK]

Common Mistakes:

• Relying on manual deletion which is error-prone
• Disabling versioning loses all version history
• Renaming objects does not control version count