Backup: Google Cloud Storage (GCS) Costs

The CloudM Backup module operates on a 'Bring Your Own Storage' model, giving you full ownership and control over your data in Google Cloud Storage (GCS). This article explains the GCS costs associated with this model and details how CloudM's features provide the tools to effectively manage and optimize them.

1. Understanding GCS Cost Factors

CloudM Backup stores data in your Google Cloud Storage account. The total cost is determined by three distinct factors appearing on your Google bill:

• Storage Volume: The monthly cost of hosting your data at rest. This depends on the total GB/TB stored and your chosen Storage Class (e.g., Standard or Autoclass).
• Data Retrieval: Charges for accessing or reading your stored data (typically during a Restore).
• Operations: Transaction costs for actions CloudM performs on the bucket, such as writing new files or listing files to check for changes.

Note: CloudM Backup is compatible with Standard and Autoclass Google Cloud Storage classes. While CloudM uses the Standard tier for active operations, enabling Autoclass can result in lower storage bills over time as Google automatically moves aging data to cheaper tiers. 

We recommend using Google's pricing calculator to estimate your costs based on your expected usage.

2. Cost Considerations: Location Matters

Using a storage bucket in a different Google Cloud region from your CloudM instance or Google Workspace tenant can lead to higher costs due to network egress fees. These are charges that apply whenever data is transferred from one Google Cloud region to another.

Recommendation: To minimize these extra costs, create your Google Cloud Storage bucket in a region that is geographically close to your Google Workspace tenant (e.g., us-central1).

3. How CloudM Backup's Features Improve Cost Efficiency

The initial backup for each user is a one-time process that transfers all data, causing a temporary spike in costs. However, subsequent backups are delta backups, meaning they only transfer changes or new items.

CloudM provides specific features to help you control these ongoing costs:

A. Configurable Backup Frequency

Configured at the Connection or Policy level, this allows you to choose how often a user's data is backed up.

• Benefit: By setting a less frequent backup schedule for static or non-critical data (e.g., Weekly instead of Daily), you directly reduce the number of "List" operations billed by Google.

B. Include/Exclude File Types

This gives you granular control over what Drive data is backed up.

• Benefit: You can exclude large, non-essential file types (e.g., .exe, video files) or compressed archives (.zip). This directly reduces the storage volume in GCS and the number of operations required.

4. Overview of Operations

Every action CloudM takes—writing a file, checking a folder, or restoring an email—counts as an "Operation" in Google Cloud. Each GCS account has a free quota of operations per month; exceeding this incurs small transaction fees.

Technical Breakdown: For a detailed list of which specific API calls (Class A vs. Class B) are triggered by CloudM, please see our technical guide: Technical Breakdown of GCS Operations

5. Practical Use Cases

Scenario 1: A Marketing Team's Backup

Context: A marketing employee has 100 GB of data. 80 GB consists of old, rarely accessed project files (.mp4, .psd), while only 20 GB is active data.

• Initial Cost: The first backup captures all 100 GB, causing a one-time spike in storage and operations.
• Strategy: The admin uses File Exclusion to ignore .mp4 files moving forward and sets the Backup Frequency to "3 times per week" instead of every 4 hours.
• Result: CloudM now performs a cheaper weekly backup. It ignores the heavy video files and checks the active data less frequently, significantly lowering the monthly bill.

Scenario 2: A Financial Analyst's File

Context: An analyst saves a critical spreadsheet 20 times a day. Only the final daily version is needed for compliance.

• Challenge: A standard "Every 4 Hours" schedule might catch multiple interim versions, creating redundant backups and unnecessary costs.
• Strategy: The admin uses Configurable Backup Frequency to set the schedule for this user to Every 24 hours.
• Result: CloudM captures only the final, approved version of the file. This creates a secure compliance record while drastically reducing the operation costs associated with interim saves.