Availability in Cloud SQL

This page describes operations that impact availability in Cloud SQL.

Cloud SQL helps you maximize the uptime of your database without any changes to your application. With a 99.99% uptime SLA and near-zero downtime for several planned operations, Cloud SQL Enterprise Plus edition offers greater resilience and business continuity for your applications.

Maximizing uptime means reducing the downtime for your database. Downtime is typically caused by both unplanned events and planned operations.

Unplanned events and zonal outage

For applications that require high availability, we recommend configuring the instance for regional availability, also referred to as the high availability (HA) configuration in Cloud SQL. For more information about configuring high availability in Cloud SQL, see About high availability (HA).

For instances configured with regional availability, if the instance encounters a failure, then Cloud SQL automatically brings up the instance in the secondary zone with the same IP address and no data loss so that applications can resume operations on the database. This protects against unplanned events such as the failure of a single VM host, or the failure of one or more infrastructure components that causes the outage of an entire zone.

Cloud SQL high availability is available for both Cloud SQL Enterprise Plus edition and Cloud SQL Enterprise edition.

If you don't configure regional availability for an instance, then the instance is configured for zonal availability, also referred to as a standalone instance.

Cloud SQL recovers standalone instances (instances configured with zonal availability) from VM host failures automatically. However, Cloud SQL doesn't recover standalone instances from a zonal outage automatically. To re-establish a standalone instance in a healthy zone, you must restore any standalone instances manually. You can recover a standalone instance from a zonal outage manually by performing either point-in-time-recovery or by promoting a read replica to become the standalone instance. For more information, see Recovery options for standalone instances.

What's next