Storage classes (Standard, Nearline, Coldline, Archive) in GCP - Commands & Configuration

Introduction

Cloud storage offers different classes to save money based on how often you access your data. These classes help you choose the right balance between cost and speed for storing files.

When you need fast access to files you use every day, like website images or app data.

When you want to store backups that you access less than once a month but still need quickly.

When you have data you rarely access, like old project files, but want to keep them available.

When you want to archive data for years, like compliance records, and can wait hours to retrieve it.

When you want to save money by moving data to cheaper storage based on how often you use it.

Config File - bucket-config.yaml

bucket-config.yaml

apiVersion: storage.cnrm.cloud.google.com/v1beta1
kind: StorageBucket
metadata:
  name: example-bucket
spec:
  location: US
  storageClass: NEARLINE
  versioning:
    enabled: true

This file creates a Google Cloud Storage bucket named example-bucket in the US region.

The storageClass is set to NEARLINE, which means the bucket is optimized for data accessed less than once a month.

Versioning is enabled to keep older versions of objects for safety.

Commands

Create a new Google Cloud Storage bucket named example-bucket in the US region with the Nearline storage class for less frequent access.

Terminal

gsutil mb -c nearline -l US gs://example-bucket/

Expected Output

Creating gs://example-bucket/...

→

-c nearline - Sets the storage class to Nearline for cost-effective storage of infrequently accessed data.

→

-l US - Specifies the bucket location as the US region.

List detailed information about the example-bucket to verify its storage class and settings.

Terminal

gsutil ls -L gs://example-bucket/

Expected Output

Bucket: gs://example-bucket/

Location constraint: US

Storage class: NEARLINE

Versioning enabled: True

Upload a file named sample-file.txt to the example-bucket to store it using the Nearline class.

Terminal

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

Expected Output

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

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

Operation completed over 1 objects.

Check if there is a lifecycle policy set on the bucket to automatically change storage classes or delete objects.

Terminal

gsutil lifecycle get gs://example-bucket/

Expected Output

No lifecycle configuration found.

Key Concept

If you remember nothing else from this pattern, remember: choose a storage class based on how often you need to access your data to save money and keep performance balanced.

Common Mistakes

Creating a bucket without specifying the storage class.

The bucket defaults to Standard class, which can cost more if you don't need frequent access.

Always specify the storage class with the -c flag when creating a bucket to match your access needs.

Using Nearline or colder classes for data accessed daily.

Accessing data frequently in these classes leads to higher retrieval costs and slower access times.

Use Standard class for data you access often to avoid extra costs and delays.

Not verifying bucket settings after creation.

You might think the bucket has the right class or versioning, but it could be misconfigured.

Run gsutil ls -L to check bucket details and confirm settings.

Summary

Create a bucket with gsutil mb specifying the storage class and location.

Verify the bucket's storage class and settings with gsutil ls -L.

Upload files to the bucket to store them in the chosen class.

Check lifecycle policies to manage automatic transitions or deletions.

Practice

1. Which Google Cloud Storage class is best for data you need to access frequently and quickly?

easy

A. Standard

B. Nearline

C. Coldline

D. Archive

Solution

1. Step 1: Understand access frequency for each storage class

   Standard is designed for frequent access, Nearline for monthly, Coldline for quarterly, and Archive for rare access.

2. Step 2: Match frequent access requirement

   Since the question asks for frequent and quick access, Standard is the best fit.

3. Final Answer:

   Standard -> Option A

4. Quick Check:

   Frequent access = Standard [OK]

Hint: Frequent access? Choose Standard storage class [OK]

Common Mistakes:

• Choosing Archive for frequent access
• Confusing Nearline with Standard
• Thinking Coldline is for frequent data

2. Which storage class should you specify in the bucket creation command to store data accessed about once a month?

easy

A. gsutil mb -c coldline gs://my-bucket

B. gsutil mb -c nearline gs://my-bucket

C. gsutil mb -c archive gs://my-bucket

D. gsutil mb -c standard gs://my-bucket

Solution

1. Step 1: Identify the storage class for monthly access

   Nearline is designed for data accessed about once a month.

2. Step 2: Match the correct gsutil command syntax

   The command to create a bucket with Nearline storage class is 'gsutil mb -c nearline gs://my-bucket'.

3. Final Answer:

   gsutil mb -c nearline gs://my-bucket -> Option B

4. Quick Check:

   Monthly access = Nearline [OK]

Hint: Nearline = monthly access, use '-c nearline' in command [OK]

Common Mistakes:

• Using '-c coldline' for monthly access
• Using '-c archive' for monthly access
• Confusing command syntax with bucket name

3. You have a bucket with Coldline storage class. You upload a 10 GB file and access it immediately. What is true about the cost and access speed?

medium

A. Low storage cost, slower access speed with retrieval fee

B. High storage cost, slow access speed

C. Low storage cost, fast access speed

D. High storage cost, fast access speed

Solution

1. Step 1: Understand Coldline storage characteristics

   Coldline offers low storage cost but is designed for infrequent access, so access speed is slower and retrieval fees apply.

2. Step 2: Analyze immediate access impact

   Accessing data immediately in Coldline means paying retrieval fees and experiencing slower access compared to Standard.

3. Final Answer:

   Low storage cost, slower access speed with retrieval fee -> Option A

4. Quick Check:

   Coldline = low cost + slower access + retrieval fee [OK]

Hint: Coldline is cheap storage but slow and costly to access [OK]

Common Mistakes:

• Assuming Coldline has fast access speed
• Thinking Coldline has no retrieval fees
• Confusing Coldline with Standard class

4. A user created a bucket with the command gsutil mb -c standard gs://archive-data but wants to store rarely accessed data. What is the best fix?

medium

A. Delete and recreate bucket with -c archive option

B. Change storage class to Coldline using gsutil setclass coldline

C. Use gsutil rewrite -s archive gs://archive-data/** to change storage class

D. No fix needed; Standard is best for rare access

Solution

1. Step 1: Identify the problem with initial bucket creation

   The bucket was created with Standard class, which is costly for rarely accessed data.

2. Step 2: Find the correct method to change storage class without deleting bucket

   Using gsutil rewrite -s archive gs://archive-data/** changes storage class of existing objects to Archive without bucket recreation.

3. Final Answer:

   Use gsutil rewrite -s archive gs://archive-data/** to change storage class -> Option C

4. Quick Check:

   Change storage class with gsutil rewrite [OK]

Hint: Use gsutil rewrite to change storage class without bucket deletion [OK]

Common Mistakes:

• Deleting bucket unnecessarily
• Using non-existent gsutil setclass command
• Thinking Standard is best for rare access

5. A company wants to archive 100 TB of data that is accessed less than once a year but must be retrievable within hours if needed. Which storage class should they choose and why?

hard

A. Standard, because it offers fastest access

B. Nearline, because it balances cost and monthly access

C. Coldline, because it is cheaper and supports quarterly access

D. Archive, because it is lowest cost and retrieval is within hours

Solution

1. Step 1: Analyze access frequency and retrieval time needs

   Data is accessed less than once a year, so very rare access. Retrieval must be within hours.

2. Step 2: Match storage class to access pattern and retrieval speed

   Archive class is designed for rare access with lowest cost and retrieval times within hours, fitting the requirement.

3. Step 3: Compare with other classes

   Standard is costly, Nearline is for monthly access, Coldline is for quarterly access, so Archive is best.

4. Final Answer:

   Archive, because it is lowest cost and retrieval is within hours -> Option D

5. Quick Check:

   Rare yearly access + hours retrieval = Archive [OK]

Hint: Rare yearly access + hours retrieval? Choose Archive [OK]

Common Mistakes:

• Choosing Coldline for yearly access
• Assuming Archive retrieval takes days
• Picking Standard for cost savings