1. In the Google Cloud console, go to theClusters page.
   

   Go to Clusters

2. If you haven't already provisioned a cluster, clickStart a free trial. If you have an existing cluster, clickMigrate data.
3. ClickCopy from Cloud SQL backup.
4. In theCopy from Cloud SQL backup page, enable the required APIs. If you already enabled the APIs, you don't need to re-enable the APIs.
5. In theSelect cluster type page, clickFree trial cluster. If you aren't eligible for a free trial cluster, this field is grayed out.
6. ClickSelect Cluster Type.
7. Select the Cloud SQL instance that you want to make a copy from and then clickSelect instance. You can filter Cloud SQL instances.
   Only compatible database versions are displayed. Replicas don't have backups and aren't displayed in the list of available instances.
8. Select the backup you want to import from and then clickSelect backup. This page displays the most recent 1,000 backups.
9. In theCreate your free cluster page, enter the cluster ID and your networking information.
10. ClickStart a free trial.

After the operation completes, a primary instance is automatically created. You see a new AlloyDB cluster with the data that is copied from the Cloud SQL for PostgreSQL backup that you selected.

When you copy a Cloud SQL for PostgreSQL backup into an AlloyDB cluster, database flags and resource level permissions aren't automatically migrated. After the copy is complete, you must set up these flags and permissions manually.

You can check which database flags in Cloud SQL for PostgreSQL are supported in AlloyDB in theCreate your free cluster page.

gcloud

To use thegcloud CLI, you caninstall and initialize thegcloud CLI, or you can useCloud Shell.

1. Run thegcloud beta alloydb clusters migrate-cloud-sql command:
   

         gcloud beta alloydb clusters migrate-cloud-sql CLUSTER_ID
           --cluster-id=CLUSTER_ID \
           --cloud-sql-backup-id=CLOUD_SQL_BACKUP_ID \
           --cloud-sql-instance-id=CLOUD_SQL_INSTANCE_ID \
           --cloud-sql-project-id=CLOUD_SQL_PROJECT_ID
           --password=PASSWORD \
           --region=REGION \
           --database-version=DATABASE_VERSION \
           --subscription-type=TRIAL

   Replace the following:

   • CLUSTER: Cloud SQL for PostgreSQL cluster ID.
   • CLOUD_SQL_BACKUP_ID: CloudSQL backup ID to migrate from. This must be the backup ID.
   • CLOUD_SQL_INSTANCE_ID: CloudSQL instance ID to migrate from. This must be the instance ID.
   • CLOUD_SQL_PROJECT_ID: CloudSQL project to migrate from. This must be the project ID.
   • PASSWORD: initial PostgreSQL user password to set up during cluster creation.
   • REGION: location, for example,asia-east1 orus-east1. See the full list of regions atregional locations.
   • DATABASE_VERSION: database version of the cluster. This must be one of:POSTGRES_14,POSTGRES_15, orPOSTGRES_16. The database version must be same as the version of the Cloud SQL backup.
   • SUBSCRIPTION_TYPE: subscription type of the cluster. This must be one of:STANDARD orTRIAL.
2. Run thegcloud beta alloydb operations describe command to confirm the status of the backup operation:
   

         gcloud beta alloydb operations describe OPERATION_ID \        --region=REGION_ID \        --project=PROJECT_ID

   Replace the following:

   • OPERATION_ID: the name of the AlloyDB operation.
   • REGION_ID: the region in which the AlloyDB cluster is deployed.
   • PROJECT_ID: the project ID.
3. Use thegcloud alloydb instances create command tocreate a primary instance.

REST API

1. To get a list of backups for the instance from which you want to restore your backup, call thebackupsRuns.list method:
   

         GET "https://sqladmin.googleapis.com/v1/projects/PROJECT_ID/instances/INSTANCE_ID/backupRuns"

   Replace the following:

   • PROJECT_ID: the project ID.
   • INSTANCE_ID: the instance ID.

   Request JSON body:

         {        "kind": string,        "items": [          {            object (BackupRun)          }        ],        "nextPageToken": string      }

   To send your request, use one of these options:

   curl (Linux, macOS, or Cloud Shell)

   The following command assumes that you signed into thegcloud CLI with your user account by runninggcloud init orgcloud auth login, or by usingCloud Shell, which automatically signs you into thegcloud CLI.

   You can check the active account by runninggcloud auth list.

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

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

   PowerShell (Windows)

   The following command assumes that you signed into thegcloud CLI with your user account by runninggcloud init orgcloud auth login, or by usingCloud Shell, which automatically signs you into thegcloud CLI.

   You can check the 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 GET `          -Headers $headers `          -ContentType: "application/json; charset=utf-8" `          -Uri          "https://sqladmin.googleapis.com//sql/v1beta4/projects/PROJECT_ID/instances/INSTANCE_ID/backupRuns"|Select-Object -Expand Content

   You receive a JSON response similar to the following:

   Response

   If successful, the response body contains a list ofBackupRun.

   The API response returns a list of backups for the instance as an array list, including"id": string,.

2. Call therestoreFromCloudSQL method:

           POST https://alloydb.googleapis.com/v1beta/projects/PROJECT_ID/locations/REGION/clusters:restoreFromCloudSQL

   Replace the following:

   • PROJECT_ID: the project ID.
   • REGION: the region in which the AlloyDB cluster is deployed.

   Request JSON body:

         {        "clusterId": string,        "cluster": {          "databaseVersion": "POSTGRES_14/POSTGRES_15/POSTGRES_16","subscriptionType": "TRIAL"        },        // Union field source can be only one of the following:        "cloudsqlBackupRunSource": {          object (CloudSQLBackupRunSource)        }        // End of list of possible types for union field source.      }

   To send your request, use one of these options:

   curl (Linux, macOS, or Cloud Shell)

   The following command assumes that you signed into thegcloud CLI with your user account by runninggcloud init orgcloud auth login, or by usingCloud Shell, which automatically signs you into thegcloud CLI.

   You can check the 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://alloydb.googleapis.com/v1beta/projects/PROJECT_ID/locations/REGION/clusters:restoreFromCloudSQL"

   PowerShell (Windows)

   The following command assumes that you signed into thegcloud CLI with your user account by runninggcloud init orgcloudauth login, or by usingCloud Shell, which automatically signs you into thegcloud CLI.

   You can check the 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://alloydb.googleapis.com/v1beta/projects/PROJECT_ID/locations/REGION/clusters:restoreFromCloudSQL"|Select-Object -Expand Content

   You receive a JSON response similar to the following:

   Response

   If successful, the response body contains an instance ofOperation.

   A new cluster is created in the specified project and location, with a volume restored from the backup pointed in theCloudSQLBackupRunSource message.

3. When the cluster is in aREADY state, create the primary instance by calling theprojects.locationsinstances.create method:
   

         POST https://alloydb.googleapis.com/v1beta/{parent=projects/PROJECT_ID/locations/REGION/clusters/CLUSTER_ID}/instances

   Replace the following:

   • PROJECT_ID: the project ID.
   • REGION: the region in which the AlloyDB cluster is deployed.
   • CLUSTER_ID: the cluster ID.

   Request JSON body:

           {          "instanceId": "string",          "instance": {            "object": "Instance"          }        }

   The request body contains an instance ofInstance.

   To send your request, use one of these options:

   curl (Linux, macOS, or Cloud Shell)

   The following command assumes that you signed into thegcloud CLI with your user account by runninggcloud init orgcloud auth login, or by usingCloud Shell, which automatically signs you into thegcloud CLI.

   You can check the 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://alloydb.googleapis.com/v1beta/projects/PROJECT_ID/locations/REGION/clusters/CLUSTER_ID/instances"

   PowerShell (Windows)

   The following command assumes that you signed into thegcloud CLI with your user account by runninggcloud init orgcloud auth login, or by usingCloud Shell, which automatically signs you into thegcloud CLI.

   You can check the 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://alloydb.googleapis.com/v1beta/projects/PROJECT_ID/locations/REGION/clusters/CLUSTER_ID/instances"|Select-Object -Expand Content

   You receive a JSON response similar to the following:

   Response

   If successful, the response body contains a newly created instance ofOperation.

4. After the instance is updated to theREADY state, connect to the instance and access the restored data from the Cloud SQL snapshot.