Google Cloud Backup and DR Service
cloud.google.com
- Free trial
- Linux
- Web
- API
- Self-hosted
What Google Cloud Backup and DR Service is
Google Cloud Backup and DR Service centrally manages backups and recovery for Google Cloud workloads. It protects copies from accidental or malicious deletion through backup vaults in a Google-managed environment that blocks modification and early deletion. Supported workloads include Compute Engine instances and disks, Filestore, Google Cloud VMware Engine VMs, Cloud SQL, AlloyDB, and enterprise databases such as Oracle, Microsoft SQL Server, SAP HANA, MySQL, and PostgreSQL. Backup plans can run intraday, daily, weekly, monthly, or yearly, with configurable locations and retention. Recovery includes file-level restores, full workload recovery, and cloning across regions or projects. Teams can automate operations with gcloud CLI, APIs, or Terraform. Reporting connects to Cloud Monitoring, Cloud Logging, and BigQuery, while security integrations include Security Command Center and Google Security Operations. A 30-day trial is available, then usage converts automatically to paid billing.
Who it suits
This service suits teams protecting Google Cloud workloads, including virtual machines, file storage, and databases. It fits organizations needing scheduled backups, retention controls, and recovery across regions or projects.
Good to know, and what to watch
- Immutable vaults resist modification and early deletion
- Supports granular and full workload recovery
- Schedules range from intraday to yearly
- Automation works with gcloud, APIs, and Terraform
- Integrates monitoring, logging, and security tools
- No free plan after trial
- Trial converts automatically to paid usage
- Retained backups can continue storage charges
- Some workloads require backup appliances
Plans
Every plan and pricePaid usage
30-day introductory trial
30-day trial
The verdict
Google Cloud Backup and DR Service covers broad Google Cloud workloads with scheduled protection and multiple recovery paths. Plan for automatic paid conversion and appliance requirements for certain VMware and database deployments.
What the maker publishes
- Appliance requirement
- Backing up VMware VMs and SAP HANA, IBM Db2, Oracle, or Microsoft SQL Server databases running inside Compute Engine instances requires an appliance management console and one or more backup/recovery appliances. source
- Automation
- Google lists gcloud CLI, APIs, and Terraform as ways to automate backup operations and integrate them with infrastructure-as-code workflows. source
- Encryption
- Backup and DR supports customer-managed encryption keys managed in Cloud Key Management Service for supported workloads. source
- Immutable backups
- Backup vaults store backups in a Google-managed environment and protect them against modification and early deletion. source
- Legacy support notice
- Google states that support for new deployments of affected databases in the legacy appliance management console ended after July 31, 2026. source
- Purpose
- Google Cloud describes the service as centrally managed backup and recovery for Google Cloud workloads, protecting backup data from malicious or accidental deletion. source
- Recovery
- The service supports granular file-level restores, full workload recoveries, and cross-region or cross-project cloning. source
- Reporting integrations
- Backup and DR reporting integrates with Cloud Monitoring, Cloud Logging, and BigQuery for dashboards, alerts, and custom reports. source
- Scheduling and retention
- Backup plans support intraday, daily, weekly, monthly, and yearly schedules with configurable backup locations and retention periods. source
- Security integrations
- The service integrates with Security Command Center and Google Security Operations to surface alerts about high-risk backup activity. source
- Supported workloads
- Supported workloads include Compute Engine instances and disks, Filestore, Google Cloud VMware Engine VMs, Cloud SQL, AlloyDB, and enterprise databases including Oracle, Microsoft SQL Server, SAP HANA, MySQL, and PostgreSQL. source
- Trial conversion
- At the end of the 30-day trial, the project automatically upgrades to paid usage and retained backups can continue to incur storage charges. source
- Trial eligibility
- A project cannot start the introductory trial if it already has an active Backup and DR configuration or used the trial within the past 12 months. source
- Trial SLA
- Google says service level agreements might be limited during the trial period. source
Checked against the maker's pages on 3 Oct 2026.