[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["難以理解","hardToUnderstand","thumb-down"],["資訊或程式碼範例有誤","incorrectInformationOrSampleCode","thumb-down"],["缺少我需要的資訊/範例","missingTheInformationSamplesINeed","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間:2025-09-04 (世界標準時間)。"],[],[],null,["# Availability in Cloud SQL\n\n\u003cbr /\u003e\n\n[MySQL](/sql/docs/mysql/availability \"View this page for the MySQL database engine\") \\| [PostgreSQL](/sql/docs/postgres/availability \"View this page for the PostgreSQL database engine\") \\| SQL Server\n\n\u003cbr /\u003e\n\nThis page describes operations that impact availability in Cloud SQL.\n\nCloud SQL helps you maximize the uptime of your database without any\nchanges to your application. With a 99.99% uptime [SLA](/sql/sla) and\nnear-zero downtime for several planned operations,\nCloud SQL Enterprise Plus edition offers greater resilience and business continuity for your\napplications.\n\nMaximizing uptime means reducing the downtime for your database.\nDowntime is typically caused by both unplanned events and planned operations.\n\nUnplanned events and zonal outage\n---------------------------------\n\nFor applications that require high availability, we recommend configuring\nthe instance for regional availability, also referred to as the\nhigh availability (HA) configuration in Cloud SQL.\nFor more information about configuring high availability in Cloud SQL, see\n[About high availability (HA)](/sql/docs/sqlserver/high-availability).\n\nFor instances configured with regional availability, if the instance\nencounters a failure, then Cloud SQL automatically brings up the\ninstance in the secondary zone with the same IP address and\nno data loss so that applications can resume operations on the database.\nThis protects against unplanned events such as the failure of a single VM\nhost, or the failure of one or more infrastructure components that causes\nthe outage of an entire zone.\n\nCloud SQL high availability is available for both Cloud SQL Enterprise Plus edition and\nCloud SQL Enterprise edition.\n\nIf you don't configure regional availability for an instance, then the instance\nis configured for zonal availability, also referred to as a\nstandalone instance.\n\nCloud SQL recovers standalone instances (instances configured with zonal availability)\nfrom VM host failures automatically.\nHowever, Cloud SQL doesn't recover standalone instances from a zonal\noutage automatically. To re-establish a standalone instance in a healthy zone,\nyou must restore any standalone instances manually.\nYou can recover a standalone instance from a zonal outage manually by\nperforming either point-in-time-recovery or by promoting a read replica to\nbecome the standalone instance. For more information, see\n[Recovery options for standalone instances](/sql/docs/sqlserver/high-availability#recovery-options).\n\nWhat's next\n-----------\n\n- Learn [about high availability (HA)](/sql/docs/sqlserver/high-availability)\n\n- [Enable or disable high availability (HA)](/sql/docs/sqlserver/configure-ha)\n\n- Read [about disaster recovery (DR)](/sql/docs/sqlserver/intro-to-cloud-sql-disaster-recovery)\n\n- View all the [Google Cloud services available in locations worldwide](/about/locations)."]]