GCP Backup and DR API to automatically enable with related services
Beginning September 21, 2026, the Google Cloud Backup and DR API will automatically enable in a project whenever the Compute Engine, Cloud SQL Admin, AlloyDB for PostgreSQL, or Filestore APIs are also enabled. This update aims to provide seamless access to enhanced backup and disaster recovery options, reducing onboarding friction for users. The automatic enablement respects existing resource usage restrictions, Assured Workloads service boundary restrictions, and project/organization-level opt-out requests submitted before the launch date. This change affects engineers and architects managing GCP projects that leverage these core data and compute services.
Notes (1) ›
- Backup and DR
Beginning September 21, 2026, the Backup and DR API ( backupdr.googleapis.com ) is automatically enabled in a project whenever any of the following APIs are enabled: Compute Engine API ( compute.googleapis.com ) Cloud SQL Admin API ( sqladmin.googleapis.com ) AlloyDB for PostgreSQL API ( alloydb.googleapis.com ) Filestore API ( file.googleapis.com ) This update provides seamless access to enhanced backup and disaster recovery options with reduced onboarding friction. To avoid conflicts in environments where the API was intentionally kept disabled or where strict governance is required, automat
https://docs.cloud.google.com/release-notes#September_21_2026
Related releases
- GCP Data Studio Adds Private IP PostgreSQL, Bulk Styling, and Deprecates Older MySQL Versions Google Cloud release notes ·
- Cloud SQL for MySQL Enterprise Plus instances gain C4 machine series Google Cloud release notes ·
- Cloud SQL for PostgreSQL Adds C4 Machine Series in New Regions Google Cloud release notes ·
- C4 Machine Series Now Available for Cloud SQL for SQL Server Google Cloud release notes ·
- Native BM25 Ranking for Hybrid Search in AlloyDB and Cloud SQL Google Cloud Blog ·
- Cloud SQL for PostgreSQL automates PITR after DR and failover Google Cloud release notes ·