Backup and DR Service pricing
This document discusses Cloud Backup and DR pricing details.
Overview
Backup and DR Service offers a consumption-based billing model, which is based on the following components:
Backup storage charge. These charges are agnostic to the type of resource being protected.
Backup management charge. These charges are specific to the type of resource being protected.
Inter-region data transfer charge. These charges are agnostic to the type of resource being protected.
Backup storage charge
The SKUs used to bill Backup and DR Service storage charges depend on whether the protected resource is being protected into a backup vault or to self-managed storage.
- If a resource is protected into a backup vault, storage charges will be billed to the project where the backup vault was created, using the Backup and DR service SKUs and with pricing defined in the table below.
| Products / SKUs - Backup | Pricing model | Meter | List Price |
|---|---|---|---|
| BackupDR: Storage - In GCP - Long-Term - Standard - in asia-south1 | Usage-based | Per GiB per month of stored data | $0.052 |
| BackupDR: Storage - In GCP - Long-Term - Standard - in asia-southeast1 | Usage-based | Per GiB per month of stored data | $0.045 |
| BackupDR: Storage - In GCP - Long-Term - Standard - in asia-east1 | Usage-based | Per GiB per month of stored data | $0.045 |
| BackupDR: Storage - In GCP - Long-Term - Standard - in asia-south2 | Usage-based | Per GiB per month of stored data | $0.052 |
| BackupDR: Storage - In GCP - Long-Term - Standard - in australia-southeast1 | Usage-based | Per GiB per month of stored data | $0.052 |
| BackupDR: Storage - In GCP - Long-Term - Standard - in europe-west1 | Usage-based | Per GiB per month of stored data | $0.045 |
| BackupDR: Storage - In GCP - Long-Term - Standard - in europe-west4 | Usage-based | Per GiB per month of stored data | $0.045 |
| BackupDR: Storage - In GCP - Long-Term - Standard - in europe-west2 | Usage-based | Per GiB per month of stored data | $0.052 |
| BackupDR: Storage - In GCP - Long-Term - Standard - in europe-west3 | Usage-based | Per GiB per month of stored data | $0.052 |
| BackupDR: Storage - In GCP - Long-Term - Standard - in southamerica-east1 | Usage-based | Per GiB per month of stored data | $0.079 |
| BackupDR: Storage - In GCP - Long-Term - Standard - in us-central1 | Usage-based | Per GiB per month of stored data | $0.045 |
| BackupDR: Storage - In GCP - Long-Term - Standard - in us-east1 | Usage-based | Per GiB per month of stored data | $0.045 |
| BackupDR: Storage - In GCP - Long-Term - Standard - in us-west1 | Usage-based | Per GiB per month of stored data | $0.045 |
| BackupDR: Storage - In GCP - Long-Term - Standard - in us-east4 | Usage-based | Per GiB per month of stored data | $0.052 |
| BackupDR: Storage - In GCP - Long-Term - Standard - in us-west4 | Usage-based | Per GiB per month of stored data | $0.052 |
| BackupDR: Storage - In GCP - Long-Term - Standard - in us-west2 | Usage-based | Per GiB per month of stored data | $0.052 |
- If a resource is protected into self-managed storage (e.g. a Cloud Storage bucket or persistent disk snapshot), storage charges will be billed using the corresponding SKUs. For more details on Cloud Storage pricing, see Cloud storage pricing. For more details on persistent disk snapshot pricing see, Cloud persistent disk snapshot pricing.
Backup management charge
Each project in Google Cloud has a billing account that is used to define who pays for the usage of Google Cloud resources and APIs in that project. The project and SKUs used for Backup and DR service billing are determined by the protected resource type.
Compute Engine VMs
Compute Engine VM protection into a backup vault (includes protection via Terraform and gCloud CLI)
Management charges for VMs under active protection into a backup vault are billed to the project where the protected VM is located. The following table lists the SKUs and price points for protection into a backup vault.
| Products / SKUs - Backup | Pricing model | Meter | List price |
|---|---|---|---|
| BackupDR: Management - In GCP - GCE VM | Usage-based | Per GiB per month of source (front-end) capacity under protection | $0.02 |
If a VM is no longer under active protection, but has backup data in a backup vault, management charges will be billed as described here.
Compute Engine VM protection into self-managed storage
Management charges for protection into self-managed storage are billed to the project where the Backup and DR service was activated and from which the management console was deployed. This is regardless of the zones, regions, or projects where the backup/recovery appliances are located. The following table lists the SKUs and price points for protection into self-managed storage.
| Products / SKUs - Backup | Pricing model | Meter | List price |
|---|---|---|---|
| VM data: Compute Engine VMs, File Systems | Usage-based | Per GiB per month of source (front-end) capacity under protection | $0.03 |
VMware Engine VMs
VMware Engine VMs are protected via the Backup and DR service management console. Management charges for resources under active protection via the Backup and DR service management console are billed to the project where the Backup and DR service was activated and from which the management console was deployed. This is regardless of the zones, regions, or projects where the backup/recovery appliances are located.
Pricing for backing up Google Cloud VMware Engine is based on consumption and commitment term; options include on-demand or committed use discounts for one- and three-year terms.
The following table lists the SKUs and price points for protecting Google Cloud VMware Engine ve1-standard-72 nodes and ve1-standard-72 storage-only nodes into a backup vault or into self-managed storage.
| Products / SKUs - Backup | Pricing model | Meter | Region | Location | List price (on demand) | 1 yr commitment (Monthly payments USD) | 1 yr commitment (Upfront payment USD) | 3 yr commitment (Monthly payments USD) | 3 yr commitment (Upfront payment USD) |
|---|---|---|---|---|---|---|---|---|---|
| VM data: Google Cloud VMware Engine | Node-based | hourly per node | asia-northeast1 | Tokyo | $0.53 | $0.40 | $0.37 | $0.30 | $0.27 |
| Node-based | hourly per node | asia-south1 | Mumbai | $0.51 | $0.39 | $0.36 | $0.29 | $0.26 | |
| Node-based | hourly per node | asia-southeast1 | Singapore | $0.51 | $0.39 | $0.36 | $0.29 | $0.26 | |
| Node-based | hourly per node | australia-southeast1 | Sydney | $0.51 | $0.39 | $0.36 | $0.29 | $0.26 | |
| Node-based | hourly per node | europe-west2 | London | $0.53 | $0.40 | $0.37 | $0.31 | $0.27 | |
| Node-based | hourly per node | europe-west3 | Frankfurt | $0.53 | $0.40 | $0.37 | $0.31 | $0.27 | |
| Node-based | hourly per node | europe-west4 | Netherlands | $0.53 | $0.40 | $0.37 | $0.31 | $0.27 | |
| Node-based | hourly per node | europe-west6 | Zurich | $0.58 | $0.44 | $0.40 | $0.33 | $0.29 | |
| Node-based | hourly per node | europe-west8 | Milan | $0.54 | $0.41 | $0.38 | $0.31 | $0.27 | |
| Node-based | hourly per node | northamerica-northeast1 | Montreal, Québec, North America | $0.51 | $0.39 | $0.36 | $0.29 | $0.26 | |
| Node-based | hourly per node | northamerica-northeast2 | Toronto, Ontario, North-America | $0.51 | $0.39 | $0.36 | $0.29 | $0.26 | |
| Node-based | hourly per node | southamerica-east1 | Sao Paulo | $0.66 | $0.50 | $0.46 | $0.38 | $0.33 | |
| Node-based | hourly per node | us-central1 | Council Buffs, Iowa, North America | $0.46 | $0.35 | $0.33 | $0.27 | $0.23 | |
| Node-based | hourly per node | us-east4 | Ashburn | $0.46 | $0.35 | $0.33 | $0.27 | $0.23 | |
| Node-based | hourly per node | us-west2 | Los Angeles | $0.50 | $0.38 | $0.35 | $0.29 | $0.25 | |
| Node-based | hourly per node | southamerica-west1 | Santiago | $0.64 | $0.48 | $0.45 | $0.37 | $0.32 | |
| Node-based | hourly per node | asia-south2 | Delhi | $0.51 | $0.39 | $0.36 | $0.29 | $0.26 | |
| Node-based | hourly per node | me-west-1 | Tel Aviv | $0.51 | $0.39 | $0.36 | $0.29 | $0.26 | |
| Node-based | hourly per node | europe-west-12 | Turin | $0.54 | $0.41 | $0.38 | $0.31 | $0.27 |
The following table lists the SKUs and price points for protecting Google Cloud VMware Engine ve2 nodes into a backup vault or into self-managed storage.
| Products / SKUs - Backup | Pricing model | Meter | Region | Location | HCI Nodes | On Demand | 1 Year Post Pay | 1 Year Pre Pay | 3 Year Post Pay | 3 Year Pre Pay |
|---|---|---|---|---|---|---|---|---|---|---|
| VM data: Google Cloud VMware Engine | Node-based | hourly per node | us-east4 | Ashburn | ve2-mega | $0.85 | $0.58 | $0.54 | $0.44 | $0.38 |
| Node-based | hourly per node | us-east4 | Ashburn | ve2-large | $0.79 | $0.54 | $0.50 | $0.41 | $0.36 | |
| Node-based | hourly per node | us-east4 | Ashburn | ve2-standard | $0.73 | $0.49 | $0.46 | $0.38 | $0.33 | |
| Node-based | hourly per node | us-east4 | Ashburn | ve2-small | $0.65 | $0.44 | $0.41 | $0.34 | $0.29 | |
| Node-based | hourly per node | us-west2 | Los Angeles | ve2-mega | $0.91 | $0.62 | $0.57 | $0.47 | $0.41 | |
| Node-based | hourly per node | us-west2 | Los Angeles | ve2-large | $0.84 | $0.57 | $0.53 | $0.44 | $0.38 | |
| Node-based | hourly per node | us-west2 | Los Angeles | ve2-standard | $0.78 | $0.53 | $0.49 | $0.40 | $0.35 | |
| Node-based | hourly per node | us-west2 | Los Angeles | ve2-small | $0.69 | $0.47 | $0.44 | $0.36 | $0.31 | |
| Node-based | hourly per node | us-central1 | Iowa | ve2-mega | $0.85 | $0.58 | $0.54 | $0.44 | $0.38 | |
| Node-based | hourly per node | us-central1 | Iowa | ve2-large | $0.79 | $0.54 | $0.50 | $0.41 | $0.36 | |
| Node-based | hourly per node | us-central1 | Iowa | ve2-standard | $0.73 | $0.49 | $0.46 | $0.38 | $0.33 | |
| Node-based | hourly per node | us-central1 | Iowa | ve2-small | $0.65 | $0.44 | $0.41 | $0.34 | $0.29 | |
| Node-based | hourly per node | europe-west2 | London | ve2-mega | $0.98 | $0.66 | $0.62 | $0.51 | $0.44 | |
| Node-based | hourly per node | europe-west2 | London | ve2-large | $0.91 | $0.62 | $0.57 | $0.47 | $0.41 | |
| Node-based | hourly per node | europe-west2 | London | ve2-standard | $0.83 | $0.57 | $0.52 | $0.43 | $0.37 | |
| Node-based | hourly per node | europe-west2 | London | ve2-small | $0.74 | $0.50 | $0.47 | $0.39 | $0.33 | |
| Node-based | hourly per node | europe-west3 | Frankfurt | ve2-mega | $0.98 | $0.66 | $0.62 | $0.51 | $0.44 | |
| Node-based | hourly per node | europe-west3 | Frankfurt | ve2-large | $0.91 | $0.62 | $0.57 | $0.47 | $0.41 | |
| Node-based | hourly per node | europe-west3 | Frankfurt | ve2-standard | $0.83 | $0.57 | $0.52 | $0.43 | $0.37 | |
| Node-based | hourly per node | europe-west3 | Frankfurt | ve2-small | $0.74 | $0.50 | $0.47 | $0.39 | $0.33 | |
| Node-based | hourly per node | europe-west4 | Netherlands | ve2-mega | $0.98 | $0.66 | $0.62 | $0.51 | $0.44 | |
| Node-based | hourly per node | europe-west4 | Netherlands | ve2-large | $0.91 | $0.62 | $0.57 | $0.47 | $0.41 | |
| Node-based | hourly per node | europe-west4 | Netherlands | ve2-standard | $0.83 | $0.57 | $0.52 | $0.43 | $0.37 | |
| Node-based | hourly per node | europe-west4 | Netherlands | ve2-small | $0.74 | $0.50 | $0.47 | $0.39 | $0.33 | |
| Node-based | hourly per node | asia-northeast1 | Tokyo | ve2-mega | $0.97 | $0.66 | $0.61 | $0.51 | $0.44 | |
| Node-based | hourly per node | asia-northeast1 | Tokyo | ve2-large | $0.90 | $0.61 | $0.57 | $0.47 | $0.41 | |
| Node-based | hourly per node | asia-northeast1 | Tokyo | ve2-standard | $0.83 | $0.56 | $0.52 | $0.43 | $0.37 | |
| Node-based | hourly per node | asia-northeast1 | Tokyo | ve2-small | $0.74 | $0.50 | $0.47 | $0.38 | $0.33 | |
| Node-based | hourly per node | asia-southeast1 | Singapore | ve2-mega | $0.94 | $0.64 | $0.59 | $0.49 | $0.42 | |
| Node-based | hourly per node | asia-southeast1 | Singapore | ve2-large | $0.87 | $0.59 | $0.55 | $0.45 | $0.39 | |
| Node-based | hourly per node | asia-southeast1 | Singapore | ve2-standard | $0.80 | $0.54 | $0.50 | $0.42 | $0.36 | |
| Node-based | hourly per node | asia-southeast1 | Singapore | ve2-small | $0.71 | $0.48 | $0.45 | $0.37 | $0.32 | |
| Node-based | hourly per node | europe-west8 | Milan | ve2-mega | $0.99 | $0.67 | $0.62 | $0.51 | $0.44 | |
| Node-based | hourly per node | europe-west8 | Milan | ve2-large | $0.91 | $0.62 | $0.58 | $0.48 | $0.41 | |
| Node-based | hourly per node | europe-west8 | Milan | ve2-standard | $0.84 | $0.57 | $0.53 | $0.44 | $0.38 | |
| Node-based | hourly per node | europe-west8 | Milan | ve2-small | $0.75 | $0.51 | $0.47 | $0.39 | $0.34 | |
| Node-based | hourly per node | asia-south1 | Mumbai | ve2-mega | $0.94 | $0.64 | $0.59 | $0.49 | $0.42 | |
| Node-based | hourly per node | asia-south1 | Mumbai | ve2-large | $0.87 | $0.59 | $0.55 | $0.45 | $0.39 | |
| Node-based | hourly per node | asia-south1 | Mumbai | ve2-standard | $0.80 | $0.54 | $0.50 | $0.42 | $0.36 | |
| Node-based | hourly per node | asia-south1 | Mumbai | ve2-small | $0.71 | $0.48 | $0.45 | $0.37 | $0.32 | |
| Node-based | hourly per node | asia-south2 | Delhi | ve2-mega | $0.94 | $0.64 | $0.59 | $0.49 | $0.42 | |
| Node-based | hourly per node | asia-south2 | Delhi | ve2-large | $0.87 | $0.59 | $0.55 | $0.45 | $0.39 | |
| Node-based | hourly per node | asia-south2 | Delhi | ve2-standard | $0.80 | $0.54 | $0.50 | $0.42 | $0.36 | |
| Node-based | hourly per node | asia-south2 | Delhi | ve2-small | $0.71 | $0.48 | $0.45 | $0.37 | $0.32 | |
| Node-based | hourly per node | australia-southeast1 | Sydney | ve2-mega | $0.94 | $0.64 | $0.59 | $0.49 | $0.42 | |
| Node-based | hourly per node | australia-southeast1 | Sydney | ve2-large | $0.87 | $0.59 | $0.55 | $0.45 | $0.39 | |
| Node-based | hourly per node | australia-southeast1 | Sydney | ve2-standard | $0.80 | $0.54 | $0.50 | $0.42 | $0.36 | |
| Node-based | hourly per node | australia-southeast1 | Sydney | ve2-small | $0.71 | $0.48 | $0.45 | $0.37 | $0.32 | |
| Node-based | hourly per node | southamerica-east1 | Sao Paulo | ve2-mega | $1.20 | $0.82 | $0.76 | $0.63 | $0.54 | |
| Node-based | hourly per node | southamerica-east1 | Sao Paulo | ve2-large | $1.12 | $0.76 | $0.70 | $0.58 | $0.50 | |
| Node-based | hourly per node | southamerica-east1 | Sao Paulo | ve2-standard | $1.03 | $0.70 | $0.65 | $0.53 | $0.46 | |
| Node-based | hourly per node | southamerica-east1 | Sao Paulo | ve2-small | $0.91 | $0.62 | $0.58 | $0.47 | $0.41 | |
| Node-based | hourly per node | northamerica-northeast1 | Montreal | ve2-mega | $0.94 | $0.64 | $0.59 | $0.49 | $0.42 | |
| Node-based | hourly per node | northamerica-northeast1 | Montreal | ve2-large | $0.87 | $0.59 | $0.55 | $0.45 | $0.39 | |
| Node-based | hourly per node | northamerica-northeast1 | Montreal | ve2-standard | $0.80 | $0.54 | $0.50 | $0.42 | $0.36 | |
| Node-based | hourly per node | northamerica-northeast1 | Montreal | ve2-small | $0.71 | $0.48 | $0.45 | $0.37 | $0.32 | |
| Node-based | hourly per node | northamerica-northeast2 | Toronto | ve2-mega | $0.94 | $0.64 | $0.59 | $0.49 | $0.42 | |
| Node-based | hourly per node | northamerica-northeast2 | Toronto | ve2-large | $0.87 | $0.59 | $0.55 | $0.45 | $0.39 | |
| Node-based | hourly per node | northamerica-northeast2 | Toronto | ve2-standard | $0.80 | $0.54 | $0.50 | $0.42 | $0.36 | |
| Node-based | hourly per node | northamerica-northeast2 | Toronto | ve2-small | $0.71 | $0.48 | $0.45 | $0.37 | $0.32 | |
| Node-based | hourly per node | europe-west6 | Zurich | ve2-mega | $1.06 | $0.72 | $0.67 | $0.55 | $0.48 | |
| Node-based | hourly per node | europe-west6 | Zurich | ve2-large | $0.98 | $0.67 | $0.62 | $0.51 | $0.44 | |
| Node-based | hourly per node | europe-west6 | Zurich | ve2-standard | $0.90 | $0.61 | $0.57 | $0.47 | $0.41 | |
| Node-based | hourly per node | europe-west6 | Zurich | ve2-small | $0.80 | $0.55 | $0.51 | $0.42 | $0.36 | |
| Node-based | hourly per node | southamerica-west1 | Santiago | ve2-mega | $1.18 | $0.80 | $0.74 | $0.61 | $0.53 | |
| Node-based | hourly per node | southamerica-west1 | Santiago | ve2-large | $1.09 | $0.74 | $0.69 | $0.57 | $0.49 | |
| Node-based | hourly per node | southamerica-west1 | Santiago | ve2-standard | $1.00 | $0.68 | $0.63 | $0.52 | $0.45 | |
| Node-based | hourly per node | southamerica-west1 | Santiago | ve2-small | $0.89 | $0.61 | $0.56 | $0.46 | $0.40 | |
| Node-based | hourly per node | me-west1 | Tel Aviv | ve2-mega | $0.94 | $0.64 | $0.59 | $0.49 | $0.42 | |
| Node-based | hourly per node | me-west1 | Tel Aviv | ve2-large | $0.87 | $0.59 | $0.55 | $0.45 | $0.39 | |
| Node-based | hourly per node | me-west1 | Tel Aviv | ve2-standard | $0.80 | $0.54 | $0.50 | $0.42 | $0.36 | |
| Node-based | hourly per node | me-west1 | Tel Aviv | ve2-small | $0.71 | $0.48 | $0.45 | $0.37 | $0.32 | |
| Node-based | hourly per node | europe-west12 | Turin | ve2-mega | $0.99 | $0.67 | $0.62 | $0.51 | $0.44 | |
| Node-based | hourly per node | europe-west12 | Turin | ve2-large | $0.91 | $0.62 | $0.58 | $0.48 | $0.41 | |
| Node-based | hourly per node | europe-west12 | Turin | ve2-standard | $0.84 | $0.57 | $0.53 | $0.44 | $0.38 | |
| Node-based | hourly per node | europe-west12 | Turin | ve2-small | $0.75 | $0.51 | $0.47 | $0.39 | $0.34 |
If a VM is no longer under active protection, but has backup data in a backup vault, management charges will be billed as described here.
Self-managed SQL Server databases
Self-managed SQL Server databases are protected via the Backup and DR service management console. Management charges for resources under active protection via the Backup and DR service management console are billed to the project where the Backup and DR service was activated and from which the management console was deployed. This is regardless of the zones, regions, or projects where the backup/recovery appliances are located.
SQL Server database protection into a backup vault
The following table lists the SKUs and price points for protection into a backup vault.
| Products / SKUs - Backup | Pricing model | Meter | List price |
|---|---|---|---|
| BackupDR: Management - In GCP - Microsoft SQL Server | Usage-based | Per GiB per month of source (front-end) capacity under protection | $0.06 |
If SQL Server is no longer under active protection, but has backup data in a backup vault, management charges will be billed as described here.
SQL Server database protection into self-managed storage
The following table lists the SKUs and price points for protection into self-managed storage.
| Products / SKUs - Backup | Pricing model | Meter | List price |
|---|---|---|---|
| Microsoft SQL Server, MySQL, PostgreSQL, MariaDB | Usage-based | Per GiB per month of source (front-end) capacity under protection | $0.09 |
| Virtual copies (Test data management)1 | Usage-based | Per GiB per month of total virtual cloned capacity | $0.03 |
1 This includes scenarios where virtual mounts are used for backup testing and/or restores.
Self-managed Oracle databases
Self-managed Oracle databases are protected via the Backup and DR service management console. Management charges for resources under active protection via the Backup and DR service management console are billed to the project where the Backup and DR service was activated and from which the management console was deployed. This is regardless of the zones, regions, or projects where the backup/recovery appliances are located.
Oracle database protection into a backup vault
The following table lists the SKUs and price points for protection into a backup vault.
| Products / SKUs - Backup | Pricing model | Meter | List price |
|---|---|---|---|
| BackupDR: Management - In GCP - Oracle | Usage-based | Per GiB per month of source (front-end) capacity under protection | $0.23 |
If Oracle is no longer under active protection, but has backup data in a backup vault, management charges will be billed as described here.
Oracle database protection into self-managed storage
The following table lists the SKUs and price points for protection into self-managed storage.
| Products / SKUs - Backup | Pricing model | Meter | List price |
|---|---|---|---|
| SAP HANA, Oracle, SAP ASE, SAP IQ, SAP MaxDB, IBM Db2 | Usage-based | Per GiB per month of source (front-end) capacity under protection | $0.24 |
| Virtual copies (Test data management)1 | Usage-based | Per GiB per month of total virtual cloned capacity | $0.03 |
1 This includes scenarios where virtual mounts are used for backup testing and/or restores.
Self-managed SAP HANA databases
Self-managed SAP HANA databases are protected via the Backup and DR service management console. Management charges for resources under active protection via the Backup and DR service management console are billed to the project where the Backup and DR service was activated and from which the management console was deployed. This is regardless of the zones, regions, or projects where the backup/recovery appliances are located. The following table lists the SKUs and price points for protection into self-managed storage.
| Products / SKUs - Backup | Pricing model | Meter | List price |
|---|---|---|---|
| SAP HANA, Oracle, SAP ASE, SAP IQ, SAP MaxDB, IBM Db2 | Usage-based | Per GiB per month of source (front-end) capacity under protection | $0.24 |
| Virtual copies (Test data management)1 | Usage-based | Per GiB per month of total virtual cloned capacity | $0.03 |
1 This includes scenarios where virtual mounts are used for backup testing and/or restores.
Other resource types
The Backup and DR service also supports protection of additional resources via the Backup and DR service management console, as listed below (e.g. file systems, MySQL databases, etc.). Management charges for such resources under active protection via the Backup and DR service management console are billed to the project where the Backup and DR service was activated and from which the management console was deployed. This is regardless of the zones, regions, or projects where the backup/recovery appliances are located. The following table lists the SKUs and price points for protection into self-managed storage.
| Products / SKUs - Backup | Pricing model | Meter | List price |
|---|---|---|---|
| VM data: Compute Engine VMs, File Systems | Usage-based | Per GiB per month of source (front-end) capacity under protection | $0.03 |
| SAP HANA, Oracle, SAP ASE, SAP IQ, SAP MaxDB, IBM Db2 | Usage-based | Per GiB per month of source (front-end) capacity under protection | $0.24 |
| Microsoft SQL Server, MySQL, PostgreSQL, MariaDB | Usage-based | Per GiB per month of source (front-end) capacity under protection | $0.09 |
| Virtual copies (Test data management)1 | Usage-based | Per GiB per month of total virtual cloned capacity | $0.03 |
1 This includes scenarios where virtual mounts are used for backup testing and/or restores.
Resources not under active protection, but with backups in a backup vault
If a resource is no longer under active protection (i.e. resource protection is “inactive”) into a given backup vault, but still has backup data in that backup vault, management charges will be billed to the project where the backup vault was created and using the SKU and price point listed below.
| Products / SKUs - Backup | Pricing model | Meter | List price |
|---|---|---|---|
| BackupDR: Management - In GCP - Long-Term Retention | Usage-based | Per GiB per month of stored data | $0.01 |
Also note the following scenarios in which resource protection will be considered “inactive”:
- See billing behavior associated with API disablement
- For resources protected via a backup/recovery appliance:
- If the backup/recovery appliance does not communicate with the backup vault for 24 hours, the associated backup vault resource protection will be considered “inactive”
How is Backup and DR management usage measured?
To calculate management charges, backup and DR measures usage based on the actual workload size at the frontend or the size of the workload it is managing. The unit of measurement is gibibyte (GiB). One gibibyte = 1024 * 1024 * 1024 bytes.
If the workload under management reports the volume size for data, Backup and DR takes into account the volume size reported (for example, the usage calculation for VMware will be consistent with the reported size of the VM in vCenter).
If you manage 10 TiB of Oracle data spread across multiple databases, the Backup and DR usage reports 10 * 1024 GiB of data usage.
Usage measurement for Compute Engine, when backing up to self-managed storage
When backing up to self-managed storage, Backup and DR measures usage for Compute Engine VM backup based on the amount of PD storage attached to a Compute Engine VM at the time of backup. Backup and DR allows you to exclude PD volumes from backup. In such instances, only volumes identified to be backed up are used to measure the usage.
For example, if two PD volumes of one TiB and two TiB are attached to a Compute Engine VM and you configure the backup SLT to exclude the 2TiB volume, the usage for the VM is measured to be one TiB.
Additionally, if the 1TiB VM grows or shrinks, Backup and DR measures usage based on the size of the volume at the time of the latest backup.
Usage measurement for Compute Engine, when backing up to a backup vault
When backing up to a backup vault, Backup and DR measures usage for Compute Engine VM as described below
Management charges are based on the size of the Compute Engine VM at the time of backup. For example, if a VM has a total of 1 TiB storage attached, the management charges will be for the 1 TiB regardless of the storage used.
Additionally, if the 1TiB VM grows or shrinks, Backup and DR measures usage based on the size of the VM at the time of the latest backup.
Usage measurement for agentless Google Cloud VMware Engine
For Google Cloud VMware Engine ve1 and ve2 nodesThe pricing is calculated based on the number and type of ESXi nodes that are being protected. A ESXi node is considered to be protected if one or more of VMs attached to it are being protected by Backup and DR Service.
Below is an example that demonstrates the billing process for Google Cloud VMware Engine:
Price to backup a single Google Cloud VMware Engine ve1 node (VM backups only) in us-central1 region for a month = (List price to backup the node/ hour) X (No. of hours in a day node is active) X (No. of days in a month).
Considering the Google Cloud VMware Engine node is active for 24 hours, there are 30 days in a month, and the price to backup a node will be $0.46 X 24 X 30 = $331 USD.
For ve2 nodes, pricing is based on both number and type (mega, large, standard, small) of ESXi nodes that are being protected.
Pricing is only for protecting Google Cloud VMware Engine—whole VM backups. It does not include backup management charges for any agent-based backups, such as charges for application consistent backups for SAP HANA, SQL Server, MySQL, Postgres, File System agents, etc. To estimate charges for agent-based backups, refer to Usage measurement for agent-based backup.
For Google Cloud VMware Engine ve1 and ve2 storage-only nodeThe pricing for protecting a Google Cloud VMware Engine ve1/ve2 storage-only node is determined by the number of Google Cloud VMware Engine ve1/ve2 storage-only nodes added to a cluster that has at least one or more Google Cloud VMware Engine ve1/ve2 protected nodes.
If you have a cluster with Google Cloud VMware Engine ve1/ve2 protected nodes and you add Google Cloud VMware Engine ve1/ve2 storage-only nodes to the same cluster, all of the storage-only nodes in the cluster will be considered protected by default and you will be charged for protecting all of them. You cannot exclude protection for Google Cloud VMware Engine ve1/ve2 storage-only nodes in a cluster that has at least one or more Google Cloud VMware Engine ve1/ve2 protected nodes.
For example, consider you have an existing cluster of 20 nodes and you are protecting 10 of them using Backup and DR service. If you add 3 storage-only nodes to the cluster, then all 3 storage-only nodes will be considered protected, and you will be charged for protecting 10 + 3 = 13 Google Cloud VMware Engine ve1 nodes.
If you are not protecting any Google Cloud VMware Engine ve1/ve2 nodes on a cluster, Google Cloud VMware Engine v1/ve2 storage-only nodes cannot be protected in that case.
Usage measurement for agent-based backup
Backup and DR measures usage for agent-based backup on the actual size of the workload. For example, if an SQL server database backup uses Backup and DR agent and if the sum of data files from an SQL server is five TiB on a seven TiB volume, the usage is measured as five TiB.
Usage measurement for agent-based backup of databases
For Oracle and SQL Server workloads, only the databases protected are counted towards usage. It does not take log files into consideration:
- Oracle. The allocated size of the database files under protection is counted towards usage. The allocated size includes data files and control files.
- Microsoft SQL Server. The total size of all the database files, including .MDF, .LDF, and .NDF files under protection are counted towards usage.
Database protection with Linux Change Block Tracking (CBT). Backup and DR supports efficient backup of several databases with change block tracking. This backup mode relies on database log and data files to reside on Linux Logical Volume Manager (LVM) managed volumes. For this class of workloads, the usage is measured as the actual used size of the database under protection, using the following queries:
Db2: call get_dbsize_info(?,?,?,-1);
MariaDB: SELECT SUM(data_length + index_length) FROM information_schema.TABLES where table_schema='';
MySQL: SELECT SUM(data_length + index_length) FROM information_schema.TABLES where table_schema='';
PostgreSQL: SELECT pg_database_size('$db');
SAP ASE: sp_spaceused;
SAP IQ: sp_iqdbsize * block_size;
SAP HANA: select sum(TOTAL_SIZE) from sys_databases.M_VOLUME_FILES where file_type='DATA'
SAP MaxDB: dbmcli -d $DBSID $MAXDB_KEY info DATA
SQL dump-based protection without Linux CBT. Backup and DR supports traditional SQL dump based backups. In this mode, usage is measured as the size of the database as reported by the database at the time of backup.
Factors that influence usage measurement
Factors that influence usage measurement in out-of-band scenarios:
- Compressed volumes. When volume is compression enabled, the usage counts the post-compression values. For example, if a two TiB volume has 2.5 TiB of data that is compressed into 1.8 TiB, usage count will be 1.8 TiB, not 2.5 TiB.
- Windows optimized volumes. For Windows optimized volumes, Backup and DR rehydrates the volume for backup, and the usage count will be the rehydrated value. For example, if a one TiB Windows optimized volume contains 800GiB data, when rehydrated for backup ends up as 1.1 TiB, the usage is 1.1 TiB.
- Block sizes. For staging disks, Backup and DR measures usage based on the block size of the staging disk. If the source volume's block size and the staging disk block size match, then the usage values will exactly match the source volume. If the block size used on the staging disk is different from the source volume, then there will be a minor difference because the usage calculation is done on the staging disk.
- Consistency groups. The usage count for a consistency group is the sum of all workload sizes in the consistency group. Workloads are measured individually and summed.
Usage measurement for virtual copies
Backup and DR measures usage for virtual copies starting when a virtual copy of a workload is created. The amount of usage is based on the size of the application at the time of last backup. As new backups are performed, the amount of usage is updated to reflect the current application size. The most common way to create virtual copies is with mount jobs. There are other job types such as prep-mount and reprovision that can also create a virtual copy. Usage charges are prorated based on the time the virtual copy is in use (from the time of the successful mount to the time of its unmounting, measured in 1-hour increments).
Consider the example of an SQL server database of size 500 GiB. Backups of this database incurs a backup usage charge associated with 500GiB. Additionally, consider a virtual copy of this database is provisioned to a test server at noon on the first of the month from the most recent backup. On the 10th of the month the source database shrinks to 400GiB. On the 20th of the month, the virtual copy is unmounted from the test server at 11 AM. In this scenario, a virtual copy usage charge of 500 GiB is incurred for 12 hours on the 1st, and 24 hours a day every day from 2nd to the time of the backup on the 10th. The virtual copy usage charge changes to 400GiB on the 10th (at the time of the backup) and continues until the 20th of the month. The virtual copy usage for the 20th will only count usage for 11 hours and not for the entire day. The usage amount does not change with additional data written to the virtual copy.
Inter-region data transfer charge
If data is transferred from a backup vault when the source and destination are in different Google Cloud regions, inter-region data transfer charges will be billed to the project where the backup vault is located, using the Backup and DR service SKUs and with pricing defined in the table below.
Inter-region data transfer charges currently apply for transfers associated with VMware Engine VMs, Oracle databases, and SQL Server databases.
Inter-region data transfer charges for Compute Engine VMs will apply in the future. Backup and DR customers will be given advance notice before inter-region data transfer charges for Compute Engine VMs begin.
| Products / SKUs - Backup | Pricing model | Meter | List price |
|---|---|---|---|
| BackupDR: Networking Traffic Data Transfer GCP Inter Region within Asia | Usage-based | Per GiB of data transferred | $0.08 |
| BackupDR: Networking Traffic Data Transfer GCP Inter Region between Asia and Africa | Usage-based | Per GiB of data transferred | $0.11 |
| BackupDR: Networking Traffic Data Transfer GCP Inter Region between Asia and Indonesia | Usage-based | Per GiB of data transferred | $0.10 |
| BackupDR: Networking Traffic Data Transfer GCP Inter Region between Asia and Latin America | Usage-based | Per GiB of data transferred | $0.14 |
| BackupDR: Networking Traffic Data Transfer GCP Inter Region between Asia and Middle East | Usage-based | Per GiB of data transferred | $0.11 |
| BackupDR: Networking Traffic Data Transfer GCP Inter Region between Asia and Oceania | Usage-based | Per GiB of data transferred | $0.10 |
| BackupDR: Networking Traffic Data Transfer GCP Inter Region within Europe | Usage-based | Per GiB of data transferred | $0.02 |
| BackupDR: Networking Traffic Data Transfer GCP Inter Region between Europe and Africa | Usage-based | Per GiB of data transferred | $0.11 |
| BackupDR: Networking Traffic Data Transfer GCP Inter Region between Europe and Asia | Usage-based | Per GiB of data transferred | $0.08 |
| BackupDR: Networking Traffic Data Transfer GCP Inter Region between Europe and Indonesia | Usage-based | Per GiB of data transferred | $0.10 |
| BackupDR: Networking Traffic Data Transfer GCP Inter Region between Europe and Latin America | Usage-based | Per GiB of data transferred | $0.14 |
| BackupDR: Networking Traffic Data Transfer GCP Inter Region between Europe and Middle East | Usage-based | Per GiB of data transferred | $0.11 |
| BackupDR: Networking Traffic Data Transfer GCP Inter Region between Europe and Oceania | Usage-based | Per GiB of data transferred | $0.10 |
| BackupDR: Networking Traffic Data Transfer GCP Inter Region between Indonesia and Latin America | Usage-based | Per GiB of data transferred | $0.14 |
| BackupDR: Networking Traffic Data Transfer GCP Inter Region between Indonesia and Oceania | Usage-based | Per GiB of data transferred | $0.08 |
| BackupDR: Networking Traffic Data Transfer GCP Inter Region within Latin America | Usage-based | Per GiB of data transferred | $0.14 |
| BackupDR: Networking Traffic Data Transfer GCP Inter Region between Latin America and Africa | Usage-based | Per GiB of data transferred | $0.14 |
| BackupDR: Networking Traffic Data Transfer GCP Inter Region between Latin America and Middle East | Usage-based | Per GiB of data transferred | $0.14 |
| BackupDR: Networking Traffic Data Transfer GCP Inter Region within North America | Usage-based | Per GiB of data transferred | $0.02 |
| BackupDR: Networking Traffic Data Transfer GCP Inter Region between North America and Africa | Usage-based | Per GiB of data transferred | $0.11 |
| BackupDR: Networking Traffic Data Transfer GCP Inter Region between North America and Asia | Usage-based | Per GiB of data transferred | $0.08 |
| BackupDR: Networking Traffic Data Transfer GCP Inter Region between North America and Europe | Usage-based | Per GiB of data transferred | $0.05 |
| BackupDR: Networking Traffic Data Transfer GCP Inter Region between North America and Indonesia | Usage-based | Per GiB of data transferred | $0.10 |
| BackupDR: Networking Traffic Data Transfer GCP Inter Region between North America and Latin America | Usage-based | Per GiB of data transferred | $0.14 |
| BackupDR: Networking Traffic Data Transfer GCP Inter Region between North America and Middle East | Usage-based | Per GiB of data transferred | $0.11 |
| BackupDR: Networking Traffic Data Transfer GCP Inter Region between North America and Oceania | Usage-based | Per GiB of data transferred | $0.10 |
| BackupDR: Networking Traffic Data Transfer GCP Inter Region within Oceania | Usage-based | Per GiB of data transferred | $0.08 |
| BackupDR: Networking Traffic Data Transfer GCP Inter Region between Oceania and Africa | Usage-based | Per GiB of data transferred | $0.14 |
| BackupDR: Networking Traffic Data Transfer GCP Inter Region between Oceania and Latin America | Usage-based | Per GiB of data transferred | $0.14 |
| BackupDR: Networking Traffic Data Transfer GCP Inter Region between Oceania and Middle East | Usage-based | Per GiB of data transferred | $0.11 |
What happens if the Backup and DR service API is disabled?
API disablement in the project containing a backup vault
When the Backup and DR service API is disabled in a project containing a backup vault, the billing behavior will be as follows:
Storage billing will continue until backups expire according to the user-defined expiration schedule.
For Compute Engine VMs protected into backup vaults
- Management billing for active protection will continue to be billed (to the project where the protected resource is located) for 30 days. After 30 consecutive days in the disabled state, the protection for the stored resources will be considered inactive.
In cases where backup data exists in a backup vault, but the associated resource is no longer under active protection, management billing for resources no longer under active protection will apply.
API disablement in a project containing Compute Engine VMs protected into a backup vault
When the Backup and DR service API is disabled in a project containing a resource protected into a backup vault, the billing behavior will be as follows:
Storage billing will continue until backups expire according to the user-defined expiration schedule.
Management billing for active protection will cease. After 30 consecutive days in the disabled state, the protection for the stored resources will be considered inactive.
In cases where backup data exists in a backup vault, but the associated resource is no longer under active protection, management billing for resources no longer under active protection will apply.
Backup/recovery appliance charge
The backup/recovery appliance runs as a compute engine VM in a customer-chosen project. Backup and DR Service appliances come in three different configurations as listed in Set up and plan a Backup and DR Service deployment. Standard Compute Engine instance charges apply to run these appliances.
What's next
For any questions related to pricing, see Frequently asked questions.