Enable and disable high availability

MySQL | PostgreSQL | SQL Server

This page describes how to configure an instance for high availability.

You can configure an instance for high availability when you create the instance, oryou can enable high availability on an existing instance.

For more information about high availability, seeOverview of the high availability configuration.

Create a new instance configured for high availability

When you create an instance and configure it forhigh availability, Cloud SQL creates it as a regional instance.

To create an instance configured for high availability:

Console

In the Google Cloud console, go to theCloud SQL Instances page.
Go to Cloud SQL Instances
SelectCreate instance.
Select the database engine.
In theChoose region and zonal availability section, selectMultiple zones(Highly available).
ExpandSpecify zones.
Select the primary and secondary zones. The following conditionsapply when the secondary zone is used during instance creation or edit:
- The zones default toAny for the primary zone andAny (different from primary) for the secondary zone.
ClickSave.
You are returned to the instance page for the primary instance while the instance is updated.

gcloud

Create the regional instance:

gcloudsqlinstancescreateREGIONAL_INSTANCE_NAME\--availability-type=REGIONAL\--database-version=DATABASE_VERSION\--cpu=NUMBER_CPUS\--memory=MEMORY_SIZE

For a complete list of available parameters, see thegcloud sql instances createreference page.

Configure the root user:

gcloudsqlusersset-passwordrootno-host\--instance=REGIONAL_INSTANCE_NAME\--password=PASSWORD

Terraform

To create an instance with high availability, use aTerraform resource.

resource "google_sql_database_instance" "postgres_instance_ha" {  name             = "postgres-instance-ha"  region           = "us-central1"  database_version = "POSTGRES_14"  settings {    tier              = "db-custom-2-7680"    availability_type = "REGIONAL"    backup_configuration {      enabled                        = true      point_in_time_recovery_enabled = true      start_time                     = "20:55"    }  }  # set `deletion_protection` to true, will ensure that one cannot accidentally delete this instance by  # use of Terraform whereas `deletion_protection_enabled` flag protects this instance at the GCP level.  deletion_protection = false}

Apply the changes

To apply your Terraform configuration in a Google Cloud project, complete the steps in the following sections.

Prepare Cloud Shell

LaunchCloud Shell.
Set the default Google Cloud project where you want to apply your Terraform configurations.
You only need to run this command once per project, and you can run it in any directory.
```
export GOOGLE_CLOUD_PROJECT=PROJECT_ID
```
Environment variables are overridden if you set explicit values in the Terraform configuration file.

Prepare the directory

Each Terraform configuration file must have its own directory (alsocalled aroot module).

InCloud Shell, create a directory and a new file within that directory. The filename must have the.tf extension—for examplemain.tf. In this tutorial, the file is referred to asmain.tf.
```
mkdirDIRECTORY && cdDIRECTORY && touch main.tf
```
If you are following a tutorial, you can copy the sample code in each section or step.
Copy the sample code into the newly createdmain.tf.
Optionally, copy the code from GitHub. This is recommended when the Terraform snippet is part of an end-to-end solution.
Review and modify the sample parameters to apply to your environment.
Save your changes.
Initialize Terraform. You only need to do this once per directory.
```
terraform init
```
Optionally, to use the latest Google provider version, include the-upgrade option:
```
terraform init -upgrade
```

Apply the changes

Review the configuration and verify that the resources that Terraform is going to create or update match your expectations:
```
terraform plan
```
Make corrections to the configuration as necessary.
Apply the Terraform configuration by running the following command and enteringyes at the prompt:
```
terraform apply
```
Wait until Terraform displays the "Apply complete!" message.
Open your Google Cloud project to view the results. In the Google Cloud console, navigate to your resources in the UI to make sure that Terraform has created or updated them.

Note: Terraform samples typically assume that the required APIs are enabled in your Google Cloud project.

Delete the changes

To delete your changes, do the following:

To disable deletion protection, in your Terraform configuration file set thedeletion_protection argument tofalse.
```
deletion_protection =  "false"
```
Apply the updated Terraform configuration by running the following command and enteringyes at the prompt:
```
terraform apply
```

Remove resources previously applied with your Terraform configuration by running the following command and enteringyes at the prompt:
```
terraform destroy
```

REST v1

For the complete list of parameters for the request, see the instances:insert page.

Create the regional instance.

Before using any of the request data, make the following replacements:

project-id: The project ID
instance-name: The instance name
database-version: The database version enum string
region The GCP region
machine-type The machine type

HTTP method and URL:

POST https://sqladmin.googleapis.com/v1/projects/project-id/instances

Request JSON body:

{  "name": "instance-name",  "region": "region",  "databaseVersion": "database-version",   "settings": {     "tier": "machine-type",     "backupConfiguration": {         "enabled": true,         "pointInTimeRecoveryEnabled": true      },      "availabilityType": "REGIONAL"   }}

To send your request, expand one of these options:

curl (Linux, macOS, or Cloud Shell)

Note: The following command assumes that you have logged in to thegcloud CLI with your user account by running gcloud init orgcloud auth login , or by usingCloud Shell, which automatically logs you into thegcloud CLI . You can check the currently active account by runninggcloud auth list.

Save the request body in a file namedrequest.json, and execute the following command:

curl -X POST \
     -H "Authorization: Bearer $(gcloud auth print-access-token)" \
     -H "Content-Type: application/json; charset=utf-8" \
     -d @request.json \
     "https://sqladmin.googleapis.com/v1/projects/project-id/instances"

PowerShell (Windows)

Note: The following command assumes that you have logged in to thegcloud CLI with your user account by running gcloud init orgcloud auth login . You can check the currently active account by runninggcloud auth list.

Save the request body in a file namedrequest.json, and execute the following command:

$cred = gcloud auth print-access-token
$headers = @{ "Authorization" = "Bearer $cred" }

Invoke-WebRequest `
    -Method POST `
    -Headers $headers `
    -ContentType: "application/json; charset=utf-8" `
    -InFile request.json `
    -Uri "https://sqladmin.googleapis.com/v1/projects/project-id/instances" | Select-Object -Expand Content

You should receive a JSON response similar to the following:

Response

{  "kind": "sql#operation",  "targetLink": "https://sqladmin.googleapis.com/v1/projects/project-id/instances/instance-name",  "status": "PENDING",  "user": "user@example.com",  "insertTime": "2020-01-21T22:43:37.981Z",  "operationType": "CREATE",  "name": "operation-id",  "targetId": "instance-name",  "selfLink": "https://sqladmin.googleapis.com/v1/projects/project-id/operations/operation-id",  "targetProject": "project-id"}

When the instance finishes initializing, update the root password on the instance:
Before using any of the request data, make the following replacements:
- project-id: The project ID
- instance-id: The instance ID
- password: The new root user password
HTTP method and URL:
```
PATCH https://sqladmin.googleapis.com/v1/projects/project-id/instances/instance-id/users?host=%25&name=postgres'
```
Request JSON body:
```
{   "name": "postgres",   "host": "nohost",   "password": "password"}
```
To send your request, expand one of these options:
curl (Linux, macOS, or Cloud Shell)
Note: The following command assumes that you have logged in to thegcloud CLI with your user account by runninggcloud init orgcloud auth login , or by usingCloud Shell, which automatically logs you into thegcloud CLI . You can check the currently active account by runninggcloud auth list.
Save the request body in a file namedrequest.json, and execute the following command:
```
curl -X PATCH \
     -H "Authorization: Bearer $(gcloud auth print-access-token)" \
     -H "Content-Type: application/json; charset=utf-8" \
     -d @request.json \
     "https://sqladmin.googleapis.com/v1/projects/project-id/instances/instance-id/users?host=%25&name=postgres'"
```
PowerShell (Windows)
Note: The following command assumes that you have logged in to thegcloud CLI with your user account by runninggcloud init orgcloud auth login . You can check the currently active account by runninggcloud auth list.
Save the request body in a file namedrequest.json, and execute the following command:
```
$cred = gcloud auth print-access-token
$headers = @{ "Authorization" = "Bearer $cred" }

Invoke-WebRequest `
    -Method PATCH `
    -Headers $headers `
    -ContentType: "application/json; charset=utf-8" `
    -InFile request.json `
    -Uri "https://sqladmin.googleapis.com/v1/projects/project-id/instances/instance-id/users?host=%25&name=postgres'" | Select-Object -Expand Content
```
You should receive a successful status code (2xx) and an empty response.

REST v1beta4

For the complete list of parameters for the request, see theinstances:insert page.

Create the regional instance.

Before using any of the request data, make the following replacements:

project-id: The project ID
instance-name: The instance name
database-version: The database version enum string
region The GCP region
machine-type The machine type

HTTP method and URL:

POST https://sqladmin.googleapis.com/sql/v1beta4/projects/project-id/instances

Request JSON body:

{  "name": "instance-name",  "region": "region",  "databaseVersion": "database-version",   "settings": {     "tier": "machine-type",     "backupConfiguration": {         "enabled": true,         "pointInTimeRecoveryEnabled": true      },      "availabilityType": "REGIONAL"   }}

To send your request, expand one of these options:

curl (Linux, macOS, or Cloud Shell)

Save the request body in a file namedrequest.json, and execute the following command:

curl -X POST \
     -H "Authorization: Bearer $(gcloud auth print-access-token)" \
     -H "Content-Type: application/json; charset=utf-8" \
     -d @request.json \
     "https://sqladmin.googleapis.com/sql/v1beta4/projects/project-id/instances"

PowerShell (Windows)

Save the request body in a file namedrequest.json, and execute the following command:

$cred = gcloud auth print-access-token
$headers = @{ "Authorization" = "Bearer $cred" }

Invoke-WebRequest `
    -Method POST `
    -Headers $headers `
    -ContentType: "application/json; charset=utf-8" `
    -InFile request.json `
    -Uri "https://sqladmin.googleapis.com/sql/v1beta4/projects/project-id/instances" | Select-Object -Expand Content

You should receive a JSON response similar to the following:

Response

{  "kind": "sql#operation",  "targetLink": "https://sqladmin.googleapis.com/sql/v1beta4/projects/project-id/instances/instance-name",  "status": "PENDING",  "user": "user@example.com",  "insertTime": "2020-01-21T22:43:37.981Z",  "operationType": "CREATE",  "name": "operation-id",  "targetId": "instance-name",  "selfLink": "https://sqladmin.googleapis.com/sql/v1beta4/projects/project-id/operations/operation-id",  "targetProject": "project-id"}

When the instance finishes initializing, update the root password on the instance:
Before using any of the request data, make the following replacements:
- project-id: The project ID
- instance-id: The instance ID
- password: The new root user password
HTTP method and URL:
```
PATCH https://sqladmin.googleapis.com/sql/v1beta4/projects/project-id/instances/instance-id/users?host=%25&name=postgres'
```
Request JSON body:
```
{   "name": "postgres",   "host": "nohost",   "password": "password"}
```
To send your request, expand one of these options:
curl (Linux, macOS, or Cloud Shell)
Note: The following command assumes that you have logged in to thegcloud CLI with your user account by runninggcloud init orgcloud auth login , or by usingCloud Shell, which automatically logs you into thegcloud CLI . You can check the currently active account by runninggcloud auth list.
Save the request body in a file namedrequest.json, and execute the following command:
```
curl -X PATCH \
     -H "Authorization: Bearer $(gcloud auth print-access-token)" \
     -H "Content-Type: application/json; charset=utf-8" \
     -d @request.json \
     "https://sqladmin.googleapis.com/sql/v1beta4/projects/project-id/instances/instance-id/users?host=%25&name=postgres'"
```
PowerShell (Windows)
Note: The following command assumes that you have logged in to thegcloud CLI with your user account by runninggcloud init orgcloud auth login . You can check the currently active account by runninggcloud auth list.
Save the request body in a file namedrequest.json, and execute the following command:
```
$cred = gcloud auth print-access-token
$headers = @{ "Authorization" = "Bearer $cred" }

Invoke-WebRequest `
    -Method PATCH `
    -Headers $headers `
    -ContentType: "application/json; charset=utf-8" `
    -InFile request.json `
    -Uri "https://sqladmin.googleapis.com/sql/v1beta4/projects/project-id/instances/instance-id/users?host=%25&name=postgres'" | Select-Object -Expand Content
```
You should receive a successful status code (2xx) and an empty response.

For more details about creating an instance, seeCreating Instances.

Configure an existing instance for high availability

You can configure a Cloud SQL instance for high availability by using the Google Cloud console,gcloud CLI, or the API.

Note: After you start the high availability configuration for an instance, you can't stop it. Reconfiguring the instance restarts it. It typically takes only a few minutes for Cloud SQL to reconfigure the instance and restart it. However, if the instance has a large disk or load, then it might take up to an hour.

Console

Important:You can't use the Google Cloud console to configure instances that have Private Service Connect enabled for high availability. To configure these instances, usegcloud CLI or the API.

To configure an instance for high availability:

In the Google Cloud console, go to theCloud SQL Instances page.
Go to Cloud SQL Instances
To open theOverview page of an instance, click the instance name.
ClickEdit.
In theAuto backups and high availability configuration option section, selectHigh availability (regional). It's also recommended that you enableAutomate backups.
ClickSave.

gcloud

To configure an instance to be a regional, high availability instance, use thegcloud sql instances patch command:

gcloudsqlinstancespatchINSTANCE_NAME\--availability-typeREGIONAL

ReplaceINSTANCE_NAME with the name of the Cloud SQL instance that you're configuring for high availability.

REST v1

To configure an instance to be a regional, high availability instance:

Check the instance to see if automatic backups and point-in-time recovery are enabled. These are required for high availability instances.
Before using any of the request data, make the following replacements:
- PROJECT_ID: the ID orproject number of the Google Cloud project that contains the instance
- INSTANCE_NAME: the name of the instance that you're configuring for high availability
HTTP method and URL:
```
GET https://sqladmin.googleapis.com/v1/projects/PROJECT_ID/instances/INSTANCE_NAME
```
To send your request, expand one of these options:
curl (Linux, macOS, or Cloud Shell)
Note: The following command assumes that you have logged in to thegcloud CLI with your user account by runninggcloud init orgcloud auth login , or by usingCloud Shell, which automatically logs you into thegcloud CLI . You can check the currently active account by runninggcloud auth list.
Execute the following command:
```
curl -X GET \
     -H "Authorization: Bearer $(gcloud auth print-access-token)" \
     "https://sqladmin.googleapis.com/v1/projects/PROJECT_ID/instances/INSTANCE_NAME"
```
PowerShell (Windows)
Note: The following command assumes that you have logged in to thegcloud CLI with your user account by runninggcloud init orgcloud auth login . You can check the currently active account by runninggcloud auth list.
Execute the following command:
```
$cred = gcloud auth print-access-token
$headers = @{ "Authorization" = "Bearer $cred" }

Invoke-WebRequest `
    -Method GET `
    -Headers $headers `
    -Uri "https://sqladmin.googleapis.com/v1/projects/PROJECT_ID/instances/INSTANCE_NAME" | Select-Object -Expand Content
```
You should receive a JSON response similar to the following:
```
{  "kind": "sql#instance",  "state": "RUNNABLE",  "databaseVersion": "POSTGRES_13"}
```
The output contains a section similar to the following:
```
  "backupConfiguration": {    "kind": "sql#backupConfiguration",    "startTime": "12:00",    "enabled": true,    "pointInTimeRecoveryEnabled": true    }
```
If eitherenabled orpointInTimeRecoveryEnabled arefalse, then use theinstances:patch method to enable them both. To enable backups, setenabled totrue andstartTime to a value which is the start of the backup window. To enable binary logging, setpointInTimeRecoveryEnabled totrue.
Before using any of the request data, make the following replacements:
- PROJECT_ID: the ID orproject number of the Google Cloud project that contains the instance
- INSTANCE_NAME: the name of the primary or read replica instance that you're configuring for high availability
- START_TIME: the time (in hours and minutes)
HTTP method and URL:
```
PATCH https://sqladmin.googleapis.com/v1/projects/PROJECT_ID/instances/INSTANCE_NAME
```
Request JSON body:
```
{  "settings":  {    "backupConfiguration":    {      "startTime": "START_TIME",      "enabled": true,      "pointInTimeRecoveryEnabled": true    }  }}
```
To send your request, expand one of these options:
curl (Linux, macOS, or Cloud Shell)
Note: The following command assumes that you have logged in to thegcloud CLI with your user account by runninggcloud init orgcloud auth login , or by usingCloud Shell, which automatically logs you into thegcloud CLI . You can check the currently active account by runninggcloud auth list.
Save the request body in a file namedrequest.json, and execute the following command:
```
curl -X PATCH \
     -H "Authorization: Bearer $(gcloud auth print-access-token)" \
     -H "Content-Type: application/json; charset=utf-8" \
     -d @request.json \
     "https://sqladmin.googleapis.com/v1/projects/PROJECT_ID/instances/INSTANCE_NAME"
```
PowerShell (Windows)
Note: The following command assumes that you have logged in to thegcloud CLI with your user account by runninggcloud init orgcloud auth login . You can check the currently active account by runninggcloud auth list.
Save the request body in a file namedrequest.json, and execute the following command:
```
$cred = gcloud auth print-access-token
$headers = @{ "Authorization" = "Bearer $cred" }

Invoke-WebRequest `
    -Method PATCH `
    -Headers $headers `
    -ContentType: "application/json; charset=utf-8" `
    -InFile request.json `
    -Uri "https://sqladmin.googleapis.com/v1/projects/PROJECT_ID/instances/INSTANCE_NAME" | Select-Object -Expand Content
```
You should receive a JSON response similar to the following:
Response
```
{  "kind": "sql#operation",  "targetLink": "https://sqladmin.googleapis.com/v1/projects/PROJECT_ID/instances/INSTANCE_NAME",  "status": "PENDING",  "user": "user@example.com",  "insertTime": "2020-01-21T22:43:37.981Z",  "operationType": "UPDATE",  "name": "OPERATION_ID",  "targetId": "INSTANCE_NAME",  "selfLink": "https://sqladmin.googleapis.com/v1/projects/PROJECT_ID/operations/OPERATION_ID",  "targetProject": "PROJECT_ID"}
```
Configure the instance to be a regional, high availability instance:
Before using any of the request data, make the following replacements:
- PROJECT_ID: the ID orproject number of the Google Cloud project that contains the instance
- INSTANCE_NAME: the name of the instance that you're configuring for high availability
HTTP method and URL:
```
PATCH https://sqladmin.googleapis.com/v1/projects/PROJECT_ID/instances/INSTANCE_NAME
```
Request JSON body:
```
{  "settings": {"availabilityType": "REGIONAL" }}
```
To send your request, expand one of these options:
curl (Linux, macOS, or Cloud Shell)
Note: The following command assumes that you have logged in to thegcloud CLI with your user account by runninggcloud init orgcloud auth login , or by usingCloud Shell, which automatically logs you into thegcloud CLI . You can check the currently active account by runninggcloud auth list.
Save the request body in a file namedrequest.json, and execute the following command:
```
curl -X PATCH \
     -H "Authorization: Bearer $(gcloud auth print-access-token)" \
     -H "Content-Type: application/json; charset=utf-8" \
     -d @request.json \
     "https://sqladmin.googleapis.com/v1/projects/PROJECT_ID/instances/INSTANCE_NAME"
```
PowerShell (Windows)
Note: The following command assumes that you have logged in to thegcloud CLI with your user account by runninggcloud init orgcloud auth login . You can check the currently active account by runninggcloud auth list.
Save the request body in a file namedrequest.json, and execute the following command:
```
$cred = gcloud auth print-access-token
$headers = @{ "Authorization" = "Bearer $cred" }

Invoke-WebRequest `
    -Method PATCH `
    -Headers $headers `
    -ContentType: "application/json; charset=utf-8" `
    -InFile request.json `
    -Uri "https://sqladmin.googleapis.com/v1/projects/PROJECT_ID/instances/INSTANCE_NAME" | Select-Object -Expand Content
```
You should receive a successful status code (2xx) and an empty response.

REST v1beta4

To configure an instance to be a regional, high availability instance:

Check the instance to see if automatic backups and point-in-time recovery are enabled. These are required for high availability instances.
Before using any of the request data, make the following replacements:
- PROJECT_ID: the ID orproject number of the Google Cloud project that contains the instance
- INSTANCE_NAME: the name of the instance that you're configuring for high availability
HTTP method and URL:
```
GET https://sqladmin.googleapis.com/sql/v1beta4/projects/PROJECT_ID/instances/INSTANCE_NAME
```
To send your request, expand one of these options:
curl (Linux, macOS, or Cloud Shell)
Note: The following command assumes that you have logged in to thegcloud CLI with your user account by runninggcloud init orgcloud auth login , or by usingCloud Shell, which automatically logs you into thegcloud CLI . You can check the currently active account by runninggcloud auth list.
Execute the following command:
```
curl -X GET \
     -H "Authorization: Bearer $(gcloud auth print-access-token)" \
     "https://sqladmin.googleapis.com/sql/v1beta4/projects/PROJECT_ID/instances/INSTANCE_NAME"
```
PowerShell (Windows)
Note: The following command assumes that you have logged in to thegcloud CLI with your user account by runninggcloud init orgcloud auth login . You can check the currently active account by runninggcloud auth list.
Execute the following command:
```
$cred = gcloud auth print-access-token
$headers = @{ "Authorization" = "Bearer $cred" }

Invoke-WebRequest `
    -Method GET `
    -Headers $headers `
    -Uri "https://sqladmin.googleapis.com/sql/v1beta4/projects/PROJECT_ID/instances/INSTANCE_NAME" | Select-Object -Expand Content
```
You should receive a JSON response similar to the following:
```
{  "kind": "sql#instance",  "state": "RUNNABLE",  "databaseVersion": "POSTGRES_13",}
```
The output contains a section similar to the following:
```
  "backupConfiguration": {    "kind": "sql#backupConfiguration",    "startTime": "12:00",    "enabled": true,    "pointInTimeRecoveryEnabled": true    }
```
If eitherenabled orpointInTimeRecoveryEnabled arefalse, then use theinstances:patch method to enable them both. To enable backups, setenabled totrue andstartTime to a value which is the start of the backup window. To enable binary logging, setpointInTimeRecoveryEnabled totrue.
Before using any of the request data, make the following replacements:
- PROJECT_ID: the ID orproject number of the Google Cloud project that contains the instance
- INSTANCE_NAME: the name of the primary or read replica instance that you're configuring for high availability
- START_TIME: the time (in hours and minutes)
HTTP method and URL:
```
PATCH https://sqladmin.googleapis.com/sql/v1beta4/projects/PROJECT_ID/instances/INSTANCE_NAME
```
Request JSON body:
```
{  "settings":  {    "backupConfiguration":    {      "startTime": "START_TIME",      "enabled": true,      "pointInTimeRecoveryEnabled": true    }  }}
```
To send your request, expand one of these options:
curl (Linux, macOS, or Cloud Shell)
Note: The following command assumes that you have logged in to thegcloud CLI with your user account by runninggcloud init orgcloud auth login , or by usingCloud Shell, which automatically logs you into thegcloud CLI . You can check the currently active account by runninggcloud auth list.
Save the request body in a file namedrequest.json, and execute the following command:
```
curl -X PATCH \
     -H "Authorization: Bearer $(gcloud auth print-access-token)" \
     -H "Content-Type: application/json; charset=utf-8" \
     -d @request.json \
     "https://sqladmin.googleapis.com/sql/v1beta4/projects/PROJECT_ID/instances/INSTANCE_NAME"
```
PowerShell (Windows)
Note: The following command assumes that you have logged in to thegcloud CLI with your user account by runninggcloud init orgcloud auth login . You can check the currently active account by runninggcloud auth list.
Save the request body in a file namedrequest.json, and execute the following command:
```
$cred = gcloud auth print-access-token
$headers = @{ "Authorization" = "Bearer $cred" }

Invoke-WebRequest `
    -Method PATCH `
    -Headers $headers `
    -ContentType: "application/json; charset=utf-8" `
    -InFile request.json `
    -Uri "https://sqladmin.googleapis.com/sql/v1beta4/projects/PROJECT_ID/instances/INSTANCE_NAME" | Select-Object -Expand Content
```
You should receive a JSON response similar to the following:
Response
```
{  "kind": "sql#operation",  "targetLink": "https://sqladmin.googleapis.com/sql/v1beta4/projects/PROJECT_ID/instances/INSTANCE_NAME",  "status": "PENDING",  "user": "user@example.com",  "insertTime": "2020-01-21T22:43:37.981Z",  "operationType": "UPDATE",  "name": "OPERATION_ID",  "targetId": "INSTANCE_NAME",  "selfLink": "https://sqladmin.googleapis.com/sql/v1beta4/projects/PROJECT_ID/operations/OPERATION_ID",  "targetProject": "PROJECT_ID"}
```
Configure the instance to be a regional, high availability instance:
Before using any of the request data, make the following replacements:
- PROJECT_ID: the ID orproject number of the Google Cloud project that contains the instance
- INSTANCE_NAME: the name of the instance that you're configuring for high availability
HTTP method and URL:
```
PATCH https://sqladmin.googleapis.com/sql/v1beta4/projects/PROJECT_ID/instances/INSTANCE_NAME
```
Request JSON body:
```
{  "settings": {"availabilityType": "REGIONAL" }}
```
To send your request, expand one of these options:
curl (Linux, macOS, or Cloud Shell)
Note: The following command assumes that you have logged in to thegcloud CLI with your user account by runninggcloud init orgcloud auth login , or by usingCloud Shell, which automatically logs you into thegcloud CLI . You can check the currently active account by runninggcloud auth list.
Save the request body in a file namedrequest.json, and execute the following command:
```
curl -X PATCH \
     -H "Authorization: Bearer $(gcloud auth print-access-token)" \
     -H "Content-Type: application/json; charset=utf-8" \
     -d @request.json \
     "https://sqladmin.googleapis.com/sql/v1beta4/projects/PROJECT_ID/instances/INSTANCE_NAME"
```
PowerShell (Windows)
Note: The following command assumes that you have logged in to thegcloud CLI with your user account by runninggcloud init orgcloud auth login . You can check the currently active account by runninggcloud auth list.
Save the request body in a file namedrequest.json, and execute the following command:
```
$cred = gcloud auth print-access-token
$headers = @{ "Authorization" = "Bearer $cred" }

Invoke-WebRequest `
    -Method PATCH `
    -Headers $headers `
    -ContentType: "application/json; charset=utf-8" `
    -InFile request.json `
    -Uri "https://sqladmin.googleapis.com/sql/v1beta4/projects/PROJECT_ID/instances/INSTANCE_NAME" | Select-Object -Expand Content
```
You should receive a successful status code (2xx) and an empty response.

Initiate failover

Testing failover is optional, but is recommended so that you can see how yourapplication responds in the event of a failover.

This feature helps you test your application's response to an automatic failover. Make sure that your instance has completed any previous failover(so it's responding to connection requests) before you trigger anotherfailover. Also, before you initiate failover for your instance,configure the instance for high availability.

To learn more about failovers, see theFailover overview.

Console

In the Google Cloud console, go to theCloud SQL Instances page.
Go to Cloud SQL Instances
To open theOverview page of an instance, click the instance name.
ClickFailover.
In theManually trigger a failover dialog box, enter the ID of your instance in the text field, and then clickTrigger Failover.

gcloud

Initiate the failover:

gcloudsqlinstancesfailoverPRIMARY_INSTANCE_NAME

REST v1

Describe the primary instance to get the value of thesettingsVersion field.
Before using any of the request data, make the following replacements:
- PROJECT_ID: the ID orproject number of the Google Cloud project that contains the instance
- INSTANCE_NAME: the name of the instance that you're configuring for high availability
HTTP method and URL:
```
GET https://sqladmin.googleapis.com/v1/projects/PROJECT_ID/instances/INSTANCE_NAME
```
To send your request, expand one of these options:
curl (Linux, macOS, or Cloud Shell)
Note: The following command assumes that you have logged in to thegcloud CLI with your user account by runninggcloud init orgcloud auth login , or by usingCloud Shell, which automatically logs you into thegcloud CLI . You can check the currently active account by runninggcloud auth list.
Execute the following command:
```
curl -X GET \
     -H "Authorization: Bearer $(gcloud auth print-access-token)" \
     "https://sqladmin.googleapis.com/v1/projects/PROJECT_ID/instances/INSTANCE_NAME"
```
PowerShell (Windows)
Note: The following command assumes that you have logged in to thegcloud CLI with your user account by runninggcloud init orgcloud auth login . You can check the currently active account by runninggcloud auth list.
Execute the following command:
```
$cred = gcloud auth print-access-token
$headers = @{ "Authorization" = "Bearer $cred" }

Invoke-WebRequest `
    -Method GET `
    -Headers $headers `
    -Uri "https://sqladmin.googleapis.com/v1/projects/PROJECT_ID/instances/INSTANCE_NAME" | Select-Object -Expand Content
```
You should receive a JSON response similar to the following:
```
{  "kind": "sql#instance",  "state": "RUNNABLE",  "databaseVersion": "POSTGRES_13"}
```

Initiate the failover:

Before using any of the request data, make the following replacements:

project-id: The project ID
instance-name: The instance name
settings-version: The settingsVersion from instanceInfo

HTTP method and URL:

POST https://sqladmin.googleapis.com/v1/projects/project-id/instances/instance-name/failover

Request JSON body:

{  "failoverContext":     {        "settingsVersion":"settings-version"     }}

To send your request, expand one of these options:

curl (Linux, macOS, or Cloud Shell)

Save the request body in a file namedrequest.json, and execute the following command:

curl -X POST \
     -H "Authorization: Bearer $(gcloud auth print-access-token)" \
     -H "Content-Type: application/json; charset=utf-8" \
     -d @request.json \
     "https://sqladmin.googleapis.com/v1/projects/project-id/instances/instance-name/failover"

PowerShell (Windows)

Save the request body in a file namedrequest.json, and execute the following command:

$cred = gcloud auth print-access-token
$headers = @{ "Authorization" = "Bearer $cred" }

Invoke-WebRequest `
    -Method POST `
    -Headers $headers `
    -ContentType: "application/json; charset=utf-8" `
    -InFile request.json `
    -Uri "https://sqladmin.googleapis.com/v1/projects/project-id/instances/instance-name/failover" | Select-Object -Expand Content

You should receive a JSON response similar to the following:

Response

{  "kind": "sql#operation",  "targetLink": "https://sqladmin.googleapis.com/v1/projects/project-id/instances/instance-name",  "status": "PENDING",  "user": "user@example.com",  "insertTime": "2020-01-21T22:43:37.981Z",  "operationType": "CREATE",  "name": "operation-id",  "targetId": "instance-name",  "selfLink": "https://sqladmin.googleapis.com/v1/projects/project-id/operations/operation-id",  "targetProject": "project-id"}

REST v1beta4

Describe the primary instance to get the value of thesettingsVersion field.
Before using any of the request data, make the following replacements:
- PROJECT_ID: the ID orproject number of the Google Cloud project that contains the instance
- INSTANCE_NAME: the name of the instance that you're configuring for high availability
HTTP method and URL:
```
GET https://sqladmin.googleapis.com/sql/v1beta4/projects/PROJECT_ID/instances/INSTANCE_NAME
```
To send your request, expand one of these options:
curl (Linux, macOS, or Cloud Shell)
Note: The following command assumes that you have logged in to thegcloud CLI with your user account by runninggcloud init orgcloud auth login , or by usingCloud Shell, which automatically logs you into thegcloud CLI . You can check the currently active account by runninggcloud auth list.
Execute the following command:
```
curl -X GET \
     -H "Authorization: Bearer $(gcloud auth print-access-token)" \
     "https://sqladmin.googleapis.com/sql/v1beta4/projects/PROJECT_ID/instances/INSTANCE_NAME"
```
PowerShell (Windows)
Note: The following command assumes that you have logged in to thegcloud CLI with your user account by runninggcloud init orgcloud auth login . You can check the currently active account by runninggcloud auth list.
Execute the following command:
```
$cred = gcloud auth print-access-token
$headers = @{ "Authorization" = "Bearer $cred" }

Invoke-WebRequest `
    -Method GET `
    -Headers $headers `
    -Uri "https://sqladmin.googleapis.com/sql/v1beta4/projects/PROJECT_ID/instances/INSTANCE_NAME" | Select-Object -Expand Content
```
You should receive a JSON response similar to the following:
```
{  "kind": "sql#instance",  "state": "RUNNABLE",  "databaseVersion": "POSTGRES_13"}
```

Initiate the failover:

Before using any of the request data, make the following replacements:

project-id: The project ID
instance-name: The instance name
settings-version: The settingsVersion from instanceInfo

HTTP method and URL:

POST https://sqladmin.googleapis.com/sql/v1beta4/projects/project-id/instances/instance-name/failover

Request JSON body:

{  "failoverContext":     {        "settingsVersion":"settings-version"     }}

To send your request, expand one of these options:

curl (Linux, macOS, or Cloud Shell)

Save the request body in a file namedrequest.json, and execute the following command:

curl -X POST \
     -H "Authorization: Bearer $(gcloud auth print-access-token)" \
     -H "Content-Type: application/json; charset=utf-8" \
     -d @request.json \
     "https://sqladmin.googleapis.com/sql/v1beta4/projects/project-id/instances/instance-name/failover"

PowerShell (Windows)

Save the request body in a file namedrequest.json, and execute the following command:

$cred = gcloud auth print-access-token
$headers = @{ "Authorization" = "Bearer $cred" }

Invoke-WebRequest `
    -Method POST `
    -Headers $headers `
    -ContentType: "application/json; charset=utf-8" `
    -InFile request.json `
    -Uri "https://sqladmin.googleapis.com/sql/v1beta4/projects/project-id/instances/instance-name/failover" | Select-Object -Expand Content

You should receive a JSON response similar to the following:

Response

{  "kind": "sql#operation",  "targetLink": "https://sqladmin.googleapis.com/sql/v1beta4/projects/project-id/instances/instance-name",  "status": "PENDING",  "user": "user@example.com",  "insertTime": "2020-01-21T22:43:37.981Z",  "operationType": "CREATE",  "name": "operation-id",  "targetId": "instance-name",  "selfLink": "https://sqladmin.googleapis.com/sql/v1beta4/projects/project-id/operations/operation-id",  "targetProject": "project-id"}

The instance fails over and it isn't available to serve data for a few minutes.

Verify an instance's high availability configuration

To verify an instance has high availability and to view the zones in which it is running:

Console

In the Google Cloud console, go to theCloud SQL Instances page.
Go to Cloud SQL Instances
To open theOverview page of an instance, click the instance name.
Confirm the following high availability settings are displayed in theConfiguration section:

Highly available (regional)
Located in shows the current primary zone of the instance.

gcloud

gcloudsqlinstancesdescribeINSTANCE_NAME

The output indicatesavailabilityType isREGIONAL. ThegceZone andsecondaryGceZone fields show the current primary and secondary zones of the instance.

REST v1

Before using any of the request data, make the following replacements:

PROJECT_ID: the ID orproject number of the Google Cloud project that contains the instance
INSTANCE_NAME: the name of the instance that you're configuring for high availability

HTTP method and URL:

GET https://sqladmin.googleapis.com/v1/projects/PROJECT_ID/instances/INSTANCE_NAME

To send your request, expand one of these options:

curl (Linux, macOS, or Cloud Shell)

Execute the following command:

curl -X GET \
     -H "Authorization: Bearer $(gcloud auth print-access-token)" \
     "https://sqladmin.googleapis.com/v1/projects/PROJECT_ID/instances/INSTANCE_NAME"

PowerShell (Windows)

Execute the following command:

$cred = gcloud auth print-access-token
$headers = @{ "Authorization" = "Bearer $cred" }

Invoke-WebRequest `
    -Method GET `
    -Headers $headers `
    -Uri "https://sqladmin.googleapis.com/v1/projects/PROJECT_ID/instances/INSTANCE_NAME" | Select-Object -Expand Content

You should receive a JSON response similar to the following:

{  "kind": "sql#instance",  "state": "RUNNABLE",  "databaseVersion": "POSTGRES_13"}

The output indicatesavailabilityType isREGIONAL. ThegceZone andsecondaryGceZone fields show the current primary and secondary zones of the instance.

REST v1beta4

Before using any of the request data, make the following replacements:

PROJECT_ID: the ID orproject number of the Google Cloud project that contains the instance
INSTANCE_NAME: the name of the instance that you're configuring for high availability

HTTP method and URL:

GET https://sqladmin.googleapis.com/sql/v1beta4/projects/PROJECT_ID/instances/INSTANCE_NAME

To send your request, expand one of these options:

curl (Linux, macOS, or Cloud Shell)

Execute the following command:

curl -X GET \
     -H "Authorization: Bearer $(gcloud auth print-access-token)" \
     "https://sqladmin.googleapis.com/sql/v1beta4/projects/PROJECT_ID/instances/INSTANCE_NAME"

PowerShell (Windows)

Execute the following command:

$cred = gcloud auth print-access-token
$headers = @{ "Authorization" = "Bearer $cred" }

Invoke-WebRequest `
    -Method GET `
    -Headers $headers `
    -Uri "https://sqladmin.googleapis.com/sql/v1beta4/projects/PROJECT_ID/instances/INSTANCE_NAME" | Select-Object -Expand Content

You should receive a JSON response similar to the following:

{  "kind": "sql#instance",  "state": "RUNNABLE",  "databaseVersion": "POSTGRES_13",}

The output indicatesavailabilityType isREGIONAL. ThegceZone andsecondaryGceZone fields show the current primary and secondary zones of the instance.

Change the zones of a high availability instance

Changing one or both zones of an existing high availability instance causes afew minutes of downtime while the instance is reconfigured. To see the currentprimary and secondary zones that the high availability instance is running in,seeVerify aninstance's high availability configuration.

Note: Once you start the zone change operation on an instance, you cannot stop it. This operation restarts the instance. It typically takes only a few minutes for the configuration and restart to complete. But if the instance has a large disk or load, it might take up to an hour.

To change the zones of a high availability instance:

Console

In the Google Cloud console, go to theCloud SQL Instances page.
Go to Cloud SQL Instances
To open theOverview page of an instance, click the instance name.
ClickEdit.
In theChoose region and zonal availability section, expandSpecify zones and select new zones. The zones default toAny for the primary zone andAny (different from primary) for the secondary zone. The following restrictions apply:
- You can specify the primary zone only, or both the primary and secondary zones.
- If both the primary and secondary zones are specified, they must be different zones.
ClickSave.
You are returned to the instance page for the primary instance while the instance is updated.

gcloud

Change the zone in which the instance is running:

gcloudsqlinstancespatchINSTANCE_NAME\--zone=PRIMARY_ZONE--secondary-zone=SECONDARY_ZONE

The--secondary-zone parameter is optional. If you omit it, Cloud SQL will select an available zone that is different from the primary zone.

The following restrictions apply:

The zones must be valid zones belonging to the same region as the Cloud SQL instance.
If the secondary zone is specified, it must be different from the primary zone.

REST v1

Change the zones of the regional instance:
Before using any of the request data, make the following replacements:
- PROJECT_ID: The project ID
- INSTANCE_NAME: The instance name
- PRIMARY_ZONE: The primary zone
- SECONDARY_ZONE: The secondary zone
HTTP method and URL:
```
PATCH https://sqladmin.googleapis.com/v1/projects/PROJECT_ID/instances/INSTANCE_NAME
```
Request JSON body:
```
{"settings": {"locationPreference": {"zone": "PRIMARY_ZONE", "secondaryZone": "SECONDARY_ZONE"}}}
```
To send your request, expand one of these options:
curl (Linux, macOS, or Cloud Shell)
Note: The following command assumes that you have logged in to thegcloud CLI with your user account by runninggcloud init orgcloud auth login , or by usingCloud Shell, which automatically logs you into thegcloud CLI . You can check the currently active account by runninggcloud auth list.
Save the request body in a file namedrequest.json, and execute the following command:
```
curl -X PATCH \
     -H "Authorization: Bearer $(gcloud auth print-access-token)" \
     -H "Content-Type: application/json; charset=utf-8" \
     -d @request.json \
     "https://sqladmin.googleapis.com/v1/projects/PROJECT_ID/instances/INSTANCE_NAME"
```
PowerShell (Windows)
Note: The following command assumes that you have logged in to thegcloud CLI with your user account by runninggcloud init orgcloud auth login . You can check the currently active account by runninggcloud auth list.
Save the request body in a file namedrequest.json, and execute the following command:
```
$cred = gcloud auth print-access-token
$headers = @{ "Authorization" = "Bearer $cred" }

Invoke-WebRequest `
    -Method PATCH `
    -Headers $headers `
    -ContentType: "application/json; charset=utf-8" `
    -InFile request.json `
    -Uri "https://sqladmin.googleapis.com/v1/projects/PROJECT_ID/instances/INSTANCE_NAME" | Select-Object -Expand Content
```
You should receive a successful status code (2xx) and an empty response.
ThesecondaryZone parameter is optional. If you omit it, Cloud SQL will select an available zone that is different from the primary zone.
The following restrictions apply:
- The zones must be valid zones.
- Any zones that you choose must belong to the same region as the Cloud SQL instance.

REST v1beta4

Change the zones of the regional instance:
Before using any of the request data, make the following replacements:
- PROJECT_ID: The project ID
- INSTANCE_NAME: The instance name
- PRIMARY_ZONE: The primary zone
- SECONDARY_ZONE: The secondary zone
HTTP method and URL:
```
PATCH https://sqladmin.googleapis.com/sql/v1beta4/projects/PROJECT_ID/instances/INSTANCE_NAME
```
Request JSON body:
```
{"settings": {"locationPreference": {"zone": "PRIMARY_ZONE", "secondaryZone": "SECONDARY_ZONE"}}}
```
To send your request, expand one of these options:
curl (Linux, macOS, or Cloud Shell)
Note: The following command assumes that you have logged in to thegcloud CLI with your user account by runninggcloud init orgcloud auth login , or by usingCloud Shell, which automatically logs you into thegcloud CLI . You can check the currently active account by runninggcloud auth list.
Save the request body in a file namedrequest.json, and execute the following command:
```
curl -X PATCH \
     -H "Authorization: Bearer $(gcloud auth print-access-token)" \
     -H "Content-Type: application/json; charset=utf-8" \
     -d @request.json \
     "https://sqladmin.googleapis.com/sql/v1beta4/projects/PROJECT_ID/instances/INSTANCE_NAME"
```
PowerShell (Windows)
Note: The following command assumes that you have logged in to thegcloud CLI with your user account by runninggcloud init orgcloud auth login . You can check the currently active account by runninggcloud auth list.
Save the request body in a file namedrequest.json, and execute the following command:
```
$cred = gcloud auth print-access-token
$headers = @{ "Authorization" = "Bearer $cred" }

Invoke-WebRequest `
    -Method PATCH `
    -Headers $headers `
    -ContentType: "application/json; charset=utf-8" `
    -InFile request.json `
    -Uri "https://sqladmin.googleapis.com/sql/v1beta4/projects/PROJECT_ID/instances/INSTANCE_NAME" | Select-Object -Expand Content
```
You should receive a successful status code (2xx) and an empty response.
ThesecondaryZone parameter is optional. If you omit it, Cloud SQL will select an available zone that is different from the primary zone.
The following restrictions apply:
- The zones must be valid zones.
- Any zones that you choose must belong to the same region as the Cloud SQL instance.

Deactivate high availability for an instance

You can deactivate high availability for a Cloud SQL instance by using the Google Cloud console,gcloud CLI, or the API.

Note:Before you perform this procedure, make sure that no operations are running on the instance.

If you deactivate high availability for an instance, then in the event of a zonal outage,you need to recover the instance manually. For more information, see Recovery options for standalone instances.

Console

Important:You can't use the Google Cloud console to deactivate high availability for instances that have Private Service Connect enabled. To deactivate these instances, usegcloud CLI or the API.

To deactivate high availability for an instance:

In the Google Cloud console, go to theCloud SQL Instances page.
Go to Cloud SQL Instances
To open theOverview page of an instance, click the instance name.
ClickEdit.
OpenAuto backups.
In theAvailability section, clickSingle zone.
ClickSave. This edit requires you to restart the instance.
When the dialog appears, clickSave and restart.

gcloud

To deactivate high availability for an instance, use thegcloud sql instances patch command:

gcloudsqlinstancespatchINSTANCE_NAME\--availability-typeZONAL

ReplaceINSTANCE_NAME with the name of the Cloud SQL instance for which you're deactivating high availability.

REST v1

To change the availability type of the instance toZONAL, use theinstances:patch method. This method deactivates high availability for the instance.

Before using any of the request data, make the following replacements:

PROJECT_ID: the ID orproject number of the Google Cloud project that contains the instance
INSTANCE_NAME: the name of the instance for which you're deactivating high availability

HTTP method and URL:

PATCH https://sqladmin.googleapis.com/v1/projects/PROJECT_ID/instances/INSTANCE_NAME

Request JSON body:

{  "settings": {"availabilityType": "ZONAL" }}

To send your request, expand one of these options:

curl (Linux, macOS, or Cloud Shell)

Save the request body in a file namedrequest.json, and execute the following command:

curl -X PATCH \
     -H "Authorization: Bearer $(gcloud auth print-access-token)" \
     -H "Content-Type: application/json; charset=utf-8" \
     -d @request.json \
     "https://sqladmin.googleapis.com/v1/projects/PROJECT_ID/instances/INSTANCE_NAME"

PowerShell (Windows)

Save the request body in a file namedrequest.json, and execute the following command:

$cred = gcloud auth print-access-token
$headers = @{ "Authorization" = "Bearer $cred" }

Invoke-WebRequest `
    -Method PATCH `
    -Headers $headers `
    -ContentType: "application/json; charset=utf-8" `
    -InFile request.json `
    -Uri "https://sqladmin.googleapis.com/v1/projects/PROJECT_ID/instances/INSTANCE_NAME" | Select-Object -Expand Content

You should receive a successful status code (2xx) and an empty response.

REST v1beta4

To change the availability type of the instance toZONAL, use theinstances:patch method. This method deactivates high availability for the instance.

Before using any of the request data, make the following replacements:

PROJECT_ID: the ID orproject number of the Google Cloud project that contains the instance
INSTANCE_NAME: the name of the instance for which you're deactivating high availability

HTTP method and URL:

PATCH https://sqladmin.googleapis.com/sql/v1beta4/projects/PROJECT_ID/instances/INSTANCE_NAME

Request JSON body:

{  "settings": {"availabilityType": "ZONAL" }}

To send your request, expand one of these options:

curl (Linux, macOS, or Cloud Shell)

Save the request body in a file namedrequest.json, and execute the following command:

curl -X PATCH \
     -H "Authorization: Bearer $(gcloud auth print-access-token)" \
     -H "Content-Type: application/json; charset=utf-8" \
     -d @request.json \
     "https://sqladmin.googleapis.com/sql/v1beta4/projects/PROJECT_ID/instances/INSTANCE_NAME"

PowerShell (Windows)

Save the request body in a file namedrequest.json, and execute the following command:

$cred = gcloud auth print-access-token
$headers = @{ "Authorization" = "Bearer $cred" }

Invoke-WebRequest `
    -Method PATCH `
    -Headers $headers `
    -ContentType: "application/json; charset=utf-8" `
    -InFile request.json `
    -Uri "https://sqladmin.googleapis.com/sql/v1beta4/projects/PROJECT_ID/instances/INSTANCE_NAME" | Select-Object -Expand Content

You should receive a successful status code (2xx) and an empty response.

Troubleshoot

Issue	Troubleshooting
You can't find the metrics for a manual failover.	Only automatic failovers go into the metrics.
Cloud SQL instance resources (CPU and RAM) are near 100% usage, causing the high availability instance to go down.	The instance machine size is too small for the load. Edit the instance to upgrade to a larger machine size to get more CPUs and memory.

What's next

Learn more abouthow the high availability configuration works.
Test how your application responds to lost connections byrestarting your instance.
Learn more aboutmanaging your database connections.
Learn more aboutGoogle Cloud Observability.
Create read replicas for your instance.

Except as otherwise noted, the content of this page is licensed under theCreative Commons Attribution 4.0 License, and code samples are licensed under theApache 2.0 License. For details, see theGoogle Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2025-07-16 UTC.

Movatterモバイル変換

Enable and disable high availability Stay organized with collections Save and categorize content based on your preferences.

Create a new instance configured for high availability

Console

gcloud

Terraform

Apply the changes

Prepare Cloud Shell

Prepare the directory

Apply the changes

Delete the changes

REST v1

curl (Linux, macOS, or Cloud Shell)

PowerShell (Windows)

Response

curl (Linux, macOS, or Cloud Shell)

PowerShell (Windows)

REST v1beta4

curl (Linux, macOS, or Cloud Shell)

PowerShell (Windows)

Response

curl (Linux, macOS, or Cloud Shell)

PowerShell (Windows)

Configure an existing instance for high availability

Console

gcloud

REST v1

curl (Linux, macOS, or Cloud Shell)

PowerShell (Windows)

curl (Linux, macOS, or Cloud Shell)

PowerShell (Windows)

Response

curl (Linux, macOS, or Cloud Shell)

PowerShell (Windows)

REST v1beta4

curl (Linux, macOS, or Cloud Shell)

PowerShell (Windows)

curl (Linux, macOS, or Cloud Shell)

PowerShell (Windows)

Response

curl (Linux, macOS, or Cloud Shell)

PowerShell (Windows)

Initiate failover

Console

gcloud

REST v1

curl (Linux, macOS, or Cloud Shell)

PowerShell (Windows)

curl (Linux, macOS, or Cloud Shell)

PowerShell (Windows)

Response

REST v1beta4

curl (Linux, macOS, or Cloud Shell)

PowerShell (Windows)

curl (Linux, macOS, or Cloud Shell)

PowerShell (Windows)

Response

Verify an instance's high availability configuration

Console

gcloud

REST v1

curl (Linux, macOS, or Cloud Shell)

PowerShell (Windows)

REST v1beta4

curl (Linux, macOS, or Cloud Shell)

PowerShell (Windows)

Change the zones of a high availability instance

Console

gcloud

REST v1

curl (Linux, macOS, or Cloud Shell)

PowerShell (Windows)

REST v1beta4

curl (Linux, macOS, or Cloud Shell)

PowerShell (Windows)

Deactivate high availability for an instance

Console

gcloud

REST v1

curl (Linux, macOS, or Cloud Shell)

Enable and disable high availability