Export and import using BAK files and transaction log files

MySQL | PostgreSQL | SQL Server

This page describes exporting and importing data into Cloud SQL instances usingBAK files and importing data into Cloud SQL instances using transaction log files.

Note: In Cloud SQL, SQL Server currently supportsthe export of native BAK files.If you're exporting to create a new instance from the exportedfile, consider restoring from a backup to a different instance orcloning the instance.

WARNING! Don't use a BAK file created from a read-only database or from a database that is in single-user mode. If youimport a BAK file created from a read-only database or from a database that's insingle-user mode, then an error might occur.

Before you begin

Important: Before starting a large export, ensure that at least 25 percentof the database size is free (on the instance). Doing so helps preventissues with aggressive autogrowth, which can affect the availabilityof the instance.

Exports use database resources, but exports don't interfere with normaldatabase operations unless the instance is under-provisioned.

For best practices, see Best Practices for Importing andExporting Data.

After completing an import operation,verify theresults.

Export data from Cloud SQL for SQL Server

Cloud SQL supports the export of built-in BAK files.

If you aim to create a new instance from an exported file, thenconsiderrestoring from a backup to a different instanceorcloning the instance.

Cloud SQL performs afull backupof the selected database during an export operation.

Note: For information about striped export, see Use striped export.

Required roles and permissions for exporting from Cloud SQL for SQL Server

To exportdata from Cloud SQL into Cloud Storage, the user initiating the export must have one of the following roles:

TheCloud SQL Editor role
Acustom role, including the following permissions:
- cloudsql.instances.get
- cloudsql.instances.export

Additionally, the service account for the Cloud SQL instance must have one of the following roles:

Thestorage.objectAdmin Identity and Access Management (IAM) role
A custom role, including the following permissions:
- storage.objects.create
- storage.objects.list (for striped export and transaction log export)
- storage.objects.delete (for striped export and transaction log export)
- storage.buckets.get (for transaction log export only)

For help withIAM roles, seeIdentity and Access Management.

Note: The changes that you make to the IAM permissions and roles might take a few minutes to take effect. For more information, see Access change propagation.

Export data to a BAK file from Cloud SQL for SQL Server

Note: You can't export a database snapshotto a BAK file.

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.
ClickExport.
In theFile format section, clickBAK.
In theData to export section, use the drop-down menu to select the database you want to export from.
In theDestination section, selectBrowse to search for a Cloud Storage bucket or folder for your export.
ClickExport to begin the export.

gcloud

Create a Cloud Storage bucket.
Find the service account for the Cloud SQL instance you're exporting from. You can do this running thegcloud sql instances describe command. Look for theserviceAccountEmailAddress field in the output.
```
gcloudsqlinstancesdescribeINSTANCE_NAME
```
Use gcloud storage buckets add-iam-policy-binding to grant thestorage.objectAdminIAM role to the service account. For more information about setting IAM permissions, see Using IAM permissions.
Export the database:
```
gcloudsqlexportbakINSTANCE_NAMEgs://BUCKET_NAME/FILENAME\--database=DATABASE_NAME
```
For information about using thegcloud sql export bak command, see the command reference page.
If you don't need to retain the IAM role you set previously, thenrevoke it now.

REST v1

Create a Cloud Storage bucket for the export.
```
gcloudstoragebucketscreategs://BUCKET_NAME--location=LOCATION_NAME--project=PROJECT_NAME
```
This step isn't required, but strongly recommended, so you don't open upaccess to any other data.
Provide your instance with thestorage.objectAdminIAM role foryour bucket. For more information about setting IAM permissions, seeUsingIAM permissions.
Export your database:
Before using any of the request data, make the following replacements:
- PROJECT_ID: the project ID
- INSTANCE_ID: the instance ID
- BUCKET_NAME: the Cloud Storage bucket name
- PATH_TO_DUMP_FILE: the path to the SQL dump file
- DATABASE_NAME_1: the name of a database inside the Cloud SQL instance
- DATABASE_NAME_2: the name of a database inside the Cloud SQL instance
HTTP method and URL:
```
POST https://sqladmin.googleapis.com/v1/projects/PROJECT_ID/instances/INSTANCE_ID/export
```
Request JSON body:
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 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_ID/export"
```
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 POST `
    -Headers $headers `
    -ContentType: "application/json; charset=utf-8" `
    -InFile request.json `
    -Uri "https://sqladmin.googleapis.com/v1/projects/PROJECT_ID/instances/INSTANCE_ID/export" | 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/TARGET_INSTANCE_ID",  "status": "PENDING",  "user": "user@example.com",  "insertTime": "2020-01-21T22:43:37.981Z",  "operationType": "UPDATE",  "name": "OPERATION_ID",  "targetId": "INSTANCE_ID",  "selfLink": "https://sqladmin.googleapis.com/v1/projects/PROJECT_ID/operations/OPERATION_ID",  "targetProject": "PROJECT_ID"}
```
If you don't need to retain the IAM role you set previously, then remove it now.

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

REST v1beta4

Create a Cloud Storage bucket for the export.
```
gcloud storage buckets create gs://BUCKET_NAME --location=LOCATION_NAME --project=PROJECT_NAME
```
This step isn't required, but strongly recommended, so you don't open upaccess to any other data.
Provide your instance with thestorage.objectAdminIAM role foryour bucket. For more information about setting IAM permissions, seeUsingIAM permissions.
Export your database:
Before using any of the request data, make the following replacements:
- PROJECT_ID: the project ID
- INSTANCE_ID: the instance ID
- BUCKET_NAME: the Cloud Storage bucket name
- PATH_TO_DUMP_FILE: the path to the SQL dump file
- DATABASE_NAME_1: the name of a database inside the Cloud SQL instance
- DATABASE_NAME_2: the name of a database inside the Cloud SQL instance
HTTP method and URL:
```
POST https://sqladmin.googleapis.com/sql/v1beta4/projects/PROJECT_ID/instances/INSTANCE_ID/export
```
Request JSON body:
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 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_ID/export"
```
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 POST `
    -Headers $headers `
    -ContentType: "application/json; charset=utf-8" `
    -InFile request.json `
    -Uri "https://sqladmin.googleapis.com/sql/v1beta4/projects/PROJECT_ID/instances/INSTANCE_ID/export" | 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/TARGET_INSTANCE_ID",  "status": "PENDING",  "user": "user@example.com",  "insertTime": "2020-01-21T22:43:37.981Z",  "operationType": "UPDATE",  "name": "OPERATION_ID",  "targetId": "INSTANCE_ID",  "selfLink": "https://sqladmin.googleapis.com/sql/v1beta4/projects/PROJECT_ID/operations/OPERATION_ID",  "targetProject": "PROJECT_ID"}
```
If you don't need to retain the IAM role you set previously, thenrevoke it now.

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

Export differential database backups

Before exporting adifferential database backup, you must export a differential base.

If other services or features, such as point-in-time recovery and read replica,trigger a full backup between your full backup export and differential backup export,then you must trigger a full backup export again.

To understand this better, consider the following example:

You raise a full backup request at 7:00 AM.
You enable point-in-time recovery at 9:00 AM. This triggers a full backup on yourinstance.
You try to take a differential backup at 5:00 PM. This export request fails withan error message because the last full backup was triggered by point-in-time recovery.

Note: On an instance enabled with point-in-time recovery, Cloud SQL triggers a daily backup and this daily backup also triggers a full database backup. This means that on an instance enabled with point-in-time recovery, you have to take full backup and differential backup within two consecutive daily backups.

Cloud SQL doesn't support database export requests with--differential-base or--bak-type=DIFF on replica instances.

gcloud

Create a Cloud Storage bucket.
Find the service account for the Cloud SQL instance from which you're exporting. You can do this running thegcloud sql instances describe command. Look for theserviceAccountEmailAddress field in the output.
```
gcloudsqlinstancesdescribeINSTANCE_NAME
```
Use gcloud storage buckets add-iam-policy-binding to grant thestorage.objectAdminIAM role to the service account. For more information about setting IAM permissions, see Using IAM permissions.
Export the database as the differential base.
```
gcloudsqlexportbakINSTANCE_NAMEgs://BUCKET_NAME/DIFFERENTIAL_BASE_FILENAME\--database=DATABASE_NAME--differential-base
```
For information about using thegcloud sql export bak command, see the command reference page.
Export a differential backup.
```
gcloudsqlexportbakINSTANCE_NAMEgs://BUCKET_NAME/DIFFERENTIAL_BACKUP_FILENAME\--database=DATABASE_NAME--bak-type=DIFF
```
For information about using thegcloud sql export bak command, see the command reference page.
If you don't need to retain the IAM role you set previously, thenrevoke it now.

REST v1

Create a Cloud Storage bucket for the export.
```
gcloudstoragebucketscreategs://BUCKET_NAME--location=LOCATION_NAME--project=PROJECT_NAME
```
This step isn't required, but strongly recommended, so you don't open upaccess to any other data.
Provide your instance with thestorage.objectAdminIAM role foryour bucket. For more information about setting IAM permissions, seeUsingIAM permissions.

Export your full database backup as the differential base.

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

PROJECT_ID: the project ID
INSTANCE_ID: the instance ID
BUCKET_NAME: the Cloud Storage bucket name
PATH_TO_BAK_FILE: the path to the SQL BAK file
DATABASE_NAME: the name of the database inside of the Cloud SQL instance
offload: to enable and use serverless export, set this value toTRUENote: Serverless export costs extra. See the pricing page.

HTTP method and URL:

POST https://sqladmin.googleapis.com/v1/projects/PROJECT_ID/instances/INSTANCE_ID/export

Request JSON body:

{ "exportContext":   {      "fileType": "BAK",      "uri": "gs://BUCKET_NAME/PATH_TO_BAK_FILE",      "databases": ["DATABASE_NAME"]      "offload":TRUE |FALSE      "bakExportOptions": {        "differentialBase":true      }   }}

To send your request, choose one of these options:

curl

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/INSTANCE_ID/export"

PowerShell

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/INSTANCE_ID/export" | 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/TARGET_INSTANCE_ID",  "status": "PENDING",  "user": "user@example.com",  "insertTime": "2020-01-21T22:43:37.981Z",  "operationType": "EXPORT",  "exportContext": {    "uri": {uri},    "databases": [DATABASE_NAME    ],    "kind": "sql#exportContext",    "fileType": "BAK",    "bakExportOptions": {      "bakType": FULL,      "differentialBase": true,    }  },  "name": "OPERATION_ID",  "targetId": "INSTANCE_ID",  "selfLink": "https://sqladmin.googleapis.com/v1/projects/PROJECT_ID/operations/OPERATION_ID",  "targetProject": "PROJECT_ID"}

Export a differential backup.

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

project-id: The project ID
instance-id: The instance ID
bucket_name: The Cloud Storage bucket name
path_to_dump_file: The path to the SQL dump fle
database_name_1: The name of a database inside the Cloud SQL instance
database_name_2: The name of a database inside the Cloud SQL instance
offload: Enables serverless export. Set totrue to use serverless export.Note: Serverless export costs extra. See the pricing page.

HTTP method and URL:

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

Request JSON body:

{ "exportContext":   {      "fileType": "BAK",      "uri": "gs://bucket_name/path_to_dump_file",      "databases": ["database_name"]      "offload":true |false      "bakExportOptions": {        bakType:"DIFF"      }    }}

To send your request, choose one of these options:

curl

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-id/export"

PowerShell

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-id/export" | 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/target-instance-id",  "status": "PENDING",  "user": "user@example.com",  "insertTime": "2020-01-21T22:43:37.981Z",  "operationType": "EXPORT",  "exportContext": {    "uri": {uri},    "databases": [database_name    ],    "kind": "sql#exportContext",    "fileType": "BAK",    "bakExportOptions": {      "bakType": DIFF,      "differentialBase": false,    }  },  "name": "operation-id",  "targetId": "instance-id",  "selfLink": "https://sqladmin.googleapis.com/v1/projects/project-id/operations/operation-id",  "targetProject": "project-id"}

If you don't need to retain the IAM role you set previously, then remove it now.

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

REST v1beta4

Create a Cloud Storage bucket for the export.
```
gcloud storage buckets create gs://BUCKET_NAME --location=LOCATION_NAME --project=PROJECT_NAME
```
This step isn't required, but strongly recommended, so you don't open upaccess to any other data.
Provide your instance with thestorage.objectAdminIAM role foryour bucket. For more information about setting IAM permissions, seeUsingIAM permissions.

Export your full database backup as the differential base.

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

project-id: the project ID
instance-id: the instance ID
bucket_name: the Cloud Storage bucket name
path_to_dump_file: the path to the SQL dump fle
database_name_1: the name of a database inside the Cloud SQL instance
database_name_2: the name of a database inside the Cloud SQL instance
offload: to enable and use serverless export, set its value totrue.Note: Serverless export costs extra. For more information, see the pricing page.

HTTP method and URL:

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

Request JSON body:

{  "exportContext":    {       "fileType": "BAK",       "uri": "gs://bucket_name/path_to_dump_file",       "databases": ["database_name"]       "offload":true |false       "bakExportOptions": {         "differentialBase":true       }     }}

To send your request, choose one of these options:

curl

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-id/export"

PowerShell

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-id/export" | 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/target-instance-id",  "status": "PENDING",  "user": "user@example.com",  "insertTime": "2020-01-21T22:43:37.981Z",  "operationType": "EXPORT",  "exportContext": {    "uri": {uri},    "databases": [database_name    ],    "kind": "sql#exportContext",    "fileType": "BAK",    "bakExportOptions": {      "bakType": FULL,      "differentialBase": true,    }  },  "name": "operation-id",  "targetId": "instance-id",  "selfLink": "https://sqladmin.googleapis.com/v1/projects/project-id/operations/operation-id",  "targetProject": "project-id"}

Export a differential backup:

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

project-id: the project ID
instance-id: the instance ID
bucket_name: the Cloud Storage bucket name
path_to_dump_file: the path to the SQL dump fle
database_name_1: the name of a database inside the Cloud SQL instance
database_name_2: the name of a database inside the Cloud SQL instance
offload: to enable and use serverless exports, set this value totrue.Note: Serverless export costs extra. For more information, see the pricing page.

HTTP method and URL:

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

Request JSON body:

{  "exportContext":    {       "fileType": "BAK",       "uri": "gs://bucket_name/path_to_dump_file",       "databases": ["database_name"]       "offload":true |false       "bakExportOptions": {        bakType:"DIFF"       }     }}

To send your request, choose one of these options:

curl

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-id/export"

PowerShell

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-id/export" | 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/target-instance-id",  "status": "PENDING",  "user": "user@example.com",  "insertTime": "2020-01-21T22:43:37.981Z",  "operationType": "EXPORT",  "exportContext": {    "uri": {uri},    "databases": [database_name    ],    "kind": "sql#exportContext",    "fileType": "BAK",    "bakExportOptions": {      "bakType": DIFF,      "differentialBase": false,    }  },  "name": "operation-id",  "targetId": "instance-id",  "selfLink": "https://sqladmin.googleapis.com/v1/projects/project-id/operations/operation-id",  "targetProject": "project-id"}

If you don't need to retain the IAM role you set previously, thenrevoke it now.

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

Export transaction logs

You can export the transaction logs for all Cloud SQL for SQL Server instances thathavepoint-in-time recovery (PITR)enabled and their logs stored in Cloud Storage.

gcloud

Create a Cloud Storage bucket for the export.
```
gcloudstoragebucketscreategs://BUCKET_NAME--location=LOCATION_NAME--project=PROJECT_NAME
```
This step isn't required, but strongly recommended, so you don't open upaccess to any other data.
Find the service account for the Cloud SQL instance from which you're exporting. You can do this by running thegcloud sql instances describe command. Look for theserviceAccountEmailAddress field in the output.
```
gcloudsqlinstancesdescribeINSTANCE_NAME
```
Use gcloud storage buckets add-iam-policy-binding to grant thestorage.AdminIAM role to the service account. For more information about setting IAM permissions, see Set and manage IAM policies on buckets.
Export the transaction logs.
```
gcloudsqlexportbakINSTANCE_NAMEgs://BUCKET_NAME/FOLDER_PATH--export-log-start-time=START_DATE_AND_TIME/--export-log-end-time=END_DATE_AND_TIME/--database=DATABASE_NAME--bak-type=TLOG
```
Note: Theexport-log-start-time andexport-log-end-time parameters are optional. The values for theseparameters must be in the UTCtime zone and have theRFC 3339format. For example: 2024-05-26T16:19:00:094Z.
If you don't provide a start date and time and an end date and time for theparameters, then Cloud SQL exports all transaction logs within the logretention period in the Cloud Storage bucket. The log retention periodcan range from 1 to 35 days for Cloud SQL Enterprise Plus edition edition and 1 to 7days for Cloud SQL Enterprise edition edition.
If you want to export transaction logs continually, then don't use the
--export-log-start-time parameterand always export to the same location in Cloud Storage. Cloud SQLdoesn't export any log files that already exist in the destination repeatedly.
For information about using thegcloud sql export bak command, see the command reference page.
If you don't need to retain the IAM role you set previously, thenrevoke it now.

REST

Create a Cloud Storage bucket.
This step isn't required, but strongly recommended, so you don't open upaccess to any other data.
Provide your instance with thestorage.AdminIAM role foryour bucket. For more information about setting IAM permissions, seeSet and manage IAM policies on buckets.
Export the transaction logs.
Before using any of the request data, make the following replacements:
- PROJECT_ID: the project ID.
- INSTANCE_ID: the instance ID.
- BUCKET_NAME: the Cloud Storage bucket name.
- FOLDER_PATH: the path to the folder in the Cloud Storage bucket. Cloud SQL exports the transaction logs to this folder.
- DATABASE_NAME: the name of the database inside of the Cloud SQL instance.
- exportLogStartTime: the start date and time of the trasnasction logs to export.
- exportLogEndTime: the end date and time of the transaction logs to export.
HTTP method and URL:
```
POST https://sqladmin.googleapis.com/v1/projects/PROJECT_ID/instances/INSTANCE_ID/export
```
Request JSON body:
```
{ "exportContext":   {      "fileType": "BAK",      "uri": "gs://BUCKET_NAME/FOLDER_PATH",      "databases": ["DATABASE_NAME"]      "bakExportOptions": {        bakType:"TLOG"        exportLogStartTime:START_DATE_AND_TIME        exportLogEndTime:END_DATE_AND_TIME      }   }}
```
To send your request, choose one of these options:
curl
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 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_ID/export"
PowerShell
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 POST `
-Headers $headers `
-ContentType: "application/json; charset=utf-8" `
-InFile request.json `
-Uri "https://sqladmin.googleapis.com/v1/projects/PROJECT_ID/instances/INSTANCE_ID/export" | 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/TARGET_INSTANCE_ID",  "status": "PENDING",  "user": "user@example.com",  "insertTime": "2020-01-21T22:43:37.981Z",  "operationType": "EXPORT",  "exportContext": {    "uri": {uri},    "databases": [DATABASE_NAME    ],    "kind": "sql#exportContext",    "fileType": "BAK",    "bakExportOptions": {      "bakType": TLOG,      "differentialBase": false,    }  },  "name": "OPERATION_ID",  "targetId": "INSTANCE_ID",  "selfLink": "https://sqladmin.googleapis.com/v1/projects/PROJECT_ID/operations/OPERATION_ID",  "targetProject": "PROJECT_ID"}
```
If you don't need to retain the IAM role you set previously, then remove it now.

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

Use striped export

The advantages of striped export are the following:

Reductions in the time needed for operations to complete
Databases larger than 5 TB can be exported

A potential disadvantage of using striped export is that the backup, rather thanconsisting of one file, is split across a set of files. This set is called a"stripe set"; seeBackup devices in a striped media set (a stripe set).In Cloud SQL, you export to an empty folderin Cloud Storage instead of generating a single file. For more information, seeHow to use striped export.

Planning your operations

Striped export can improve the performance of exports. However, if your usecase requires a single output file, or ifyour database is less than 5 TB in size, and if faster performance isn'tcritical, you may want to use a non-striped export.

If you decide to use striped export, then consider thenumber of stripes. You can specify this value in yourgcloud CLI command or REST API call. However, if you want an optimal number ofstripes for performance, or if you don't know a number, omit the number.An optimal number of stripes is set automatically.

The maximum number of stripes currently supported byCloud SQL for SQL Server is 64.

How to use striped export

gcloud

Create a Cloud Storage bucket.
Find the service account for the Cloud SQL instance you're exporting from. You can do this by running thegcloud sql instances describe command. Look for theserviceAccountEmailAddress field in the output.
```
gcloudsqlinstancesdescribeINSTANCE_NAME
```
Use gcloud storage buckets add-iam-policy-binding to grant thestorage.objectAdminIAM role to the service account. For more information about setting IAM permissions, see Using IAM permissions.
To export the database, specify the--striped parameter and/or specify a value for--stripe_count. Setting a value for--stripe_count implies that the--striped parameter is intended. An error occurs if you specify--no-striped but specify a value for--stripe_count:
```
gcloudbetasqlexportbakINSTANCE_NAME\gs://BUCKET_NAME/STRIPED_EXPORT_FOLDER\--database=DATABASE_NAME--striped--stripe_count=NUMBER
```
For information about using thegcloud beta sql export bak command, see the command reference page.
If you don't need to retain the IAM role you set previously, then revoke it now.

REST v1

Create a Cloud Storage bucket for the export.
```
gcloudstoragebucketscreategs://BUCKET_NAME--location=LOCATION_NAME--project=PROJECT_NAME
```
This step isn't required, but strongly recommended, so you don't open upaccess to any other data.
Provide your instance with thestorage.objectAdminIAM role foryour bucket. For more information about setting IAM permissions, seeUsingIAM permissions.
Export your database:
Before using any of the request data, make the following replacements:
- project-id: The project ID
- instance-id: The instance ID
- bucket_name: The Cloud Storage bucket name
- path_to_folder: The path to the folder (in the Cloud Storage bucket) to which to export the striped set to
- database_name: The name of a database in your Cloud SQL instance
- true | false: Set totrue to use striped export. If you specifytrue without specifying a stripe count, an optimal number of stripes is set automatically
- number_of_stripes: The number of stripes to use. If specified,striped is implied astrue
HTTP method and URL:
```
POST https://sqladmin.googleapis.com/v1/projects/project-id/instances/instance-id/export
```
Request JSON body:
```
{ "exportContext":   {      "fileType": "BAK",      "uri": "gs://bucket_name/path_to_folder",      "databases": ["database_name"],      "bakExportOptions": {        "striped":true |false,        "stripe_count": ["number_of_stripes"]      }    }}
```
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 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-id/export"
```
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 POST `
    -Headers $headers `
    -ContentType: "application/json; charset=utf-8" `
    -InFile request.json `
    -Uri "https://sqladmin.googleapis.com/v1/projects/project-id/instances/instance-id/export" | 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/target-instance-id",  "status": "PENDING",  "user": "user@example.com",  "insertTime": "2022-09-29T22:43:37.981Z",  "operationType": "UPDATE",  "name": "operation-id",  "targetId": "instance-id",  "selfLink": "https://sqladmin.googleapis.com/v1/projects/project-id/operations/operation-id",  "targetProject": "project-id"}
```
If you don't need to retain the IAM role you set previously, then remove it now.

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

REST v1beta4

Create a Cloud Storage bucket for the export.
```
gcloud storage buckets create gs://BUCKET_NAME --location=LOCATION_NAME --project=PROJECT_NAME
```
This step isn't required, but is strongly recommended, so you don't open upaccess to any other data.
Provide your instance with thestorage.objectAdminIAM role foryour bucket. For more information about setting IAM permissions, seeUsingIAM permissions.
Export your database:
Before using any of the request data, make the following replacements:
- project-id: The project ID
- instance-id: The instance ID
- bucket_name: The Cloud Storage bucket name
- path_to_folder: The path to the folder (in the Cloud Storage bucket) to which to export the striped set
- database_name: The name of a database in your Cloud SQL instance
- true | false: Set totrue to use striped export. If you specifytrue without specifying a stripe count, an optimal number of stripes is set automatically
- number_of_stripes: The number of stripes to use. If specified,striped is implied astrue
HTTP method and URL:
```
POST https://sqladmin.googleapis.com/sql/v1beta4/projects/project-id/instances/instance-id/export
```
Request JSON body:
```
{ "exportContext":   {      "fileType": "BAK",      "uri": "gs://bucket_name/path_to_folder",      "databases": ["database_name"],      "bakExportOptions": {        "striped":true |false,        "stripe_count": ["number_of_stripes"]      }    }}
```
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 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-id/export"
```
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 POST `
    -Headers $headers `
    -ContentType: "application/json; charset=utf-8" `
    -InFile request.json `
    -Uri "https://sqladmin.googleapis.com/sql/v1beta4/projects/project-id/instances/instance-id/export" | 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/target-instance-id",  "status": "PENDING",  "user": "user@example.com",  "insertTime": "2022-09-29T22:43:37.981Z",  "operationType": "UPDATE",  "name": "operation-id",  "targetId": "instance-id",  "selfLink": "https://sqladmin.googleapis.com/sql/v1beta4/projects/project-id/operations/operation-id",  "targetProject": "project-id"}
```
If you don't need to retain the IAM role you set previously, then remove it now.

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

Import to Cloud SQL for SQL Server

Required roles and permissions for importing to Cloud SQL for SQL Server

To importdata from Cloud Storage into Cloud SQL, the user initiating the import must haveone of the following roles:

TheCloud SQL Admin role
Acustom role, including the following permissions:
- cloudsql.instances.get
- cloudsql.instances.import

Additionally, the service account for the Cloud SQL instance must have one of the following roles:

Thestorage.objectAdmin IAM role
A custom role, including the following permissions:
- storage.objects.get
- storage.objects.list (for striped import only)

For help withIAM roles, seeIdentity and Access Management.

Note: The changes that you make to the IAM permissions and roles might take a few minutes to take effect. For more information, see Access change propagation.

Import data from a BAK file to Cloud SQL for SQL Server

To use striped import, seeUse striped import.

Various import frameworks are available. For example, Cloud SQL for SQL Serversupportschange data capture (CDC) for the following database versions:

SQL Server 2017 Standard
SQL Server 2017 Enterprise
SQL Server 2019 Standard
SQL Server 2019 Enterprise
SQL Server 2022 Standard
SQL Server 2022 Enterprise

When importing a CDC-enabled database, theKEEP_CDCflag is retained.

Note: You can't import a database that was exportedfrom a higher version of SQL Server or import from a higher compatibility levelinto a lower one. For example, if you exported a SQL Server 2017version, you can't import it into a SQL Server 2014 version.

If your instance version is a Microsoft SQL Server Enterprise Edition, thenyou can import encrypted BAK files.

Microsoft SQL Server Standard Edition instances also import encrypted BAK files,but only through gcloud CLI.

The only supported BAK extensions are.bak and.bak.gz. GPG encrypted backupsare not currently supported.

For the instructions below, prepare to specify a new database; don'tcreate a database before starting the import of your BAK file.

Note: Cloud SQL only supports importing afull backup with a single backup set.

To import data to a Cloud SQL instance using a BAK file:

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.
ClickImport.
In theChoose a file to import from field, enter the path to the bucket and the BAK file to use for the import.
You can import a compressed (.gz) or an uncompressed file.
In theFile format section, selectBAK.
If you're importing data into a Cloud SQL Enterprise Plus edition instance, then you can import encrypted BAK files. Cloud SQL Enterprise edition instances also support importing encrypted BAK files, but only through the gcloud CLI.
To import an encrypted BAK file, do the following:
1. SelectEncrypted BAK.
2. In theCertificate field, select the certificate that you want to import. This certificate is issued by a third-party certificate authority (CA).
3. In thePrivate key field, select the file that contains the private key that you want to import. Theprivate key is used to encrypt and decrypt data that's sent from a source to a destination Cloud SQL instance.
4. In thePassword field, enter the password for the private key.
In theDestination section, specify the database in your Cloud SQL instance where you want to import the BAK file.
To start the import, clickImport.

gcloud

Create a Cloud Storage bucket for the import.
```
gcloudstoragebucketscreategs://BUCKET_NAME--location=LOCATION_NAME--project=PROJECT_NAME
```
This step isn't required, but strongly recommended, so you don't open up access to any other data.
Make sure you have configured the required roles and permissions.
Uploadthe data from the BAK file to the bucket.
Describe the instance that you are importing to:
```
gcloudsqlinstancesdescribeINSTANCE_NAME
```
Copy theserviceAccountEmailAddress field.
Use gcloud storage buckets add-iam-policy-binding to grant thestorage.objectViewerIAM role to the service account for the bucket. For more information about setting IAM permissions, seeUsing IAM permissions.

Import the data from the file:

gcloudsqlimportbakINSTANCE_NAMEgs://BUCKET_NAME/FILE_NAME\--database=DATABASE_NAME

For encrypted imports, use the following command:

gcloudsqlimportbakINSTANCE_NAMEgs://BUCKET_NAME/FILE_NAME--database=DATABASE_NAME--cert-path=gs://BUCKET_NAME/CERTIFICATE_NAME--pvk-path=gs://BUCKET_NAME/KEY_NAME--prompt-for-pvk-password

If you don't need to retain the IAM permissions you set previously, then remove them usinggcloud storage buckets remove-iam-policy-binding.

REST v1

Create a Cloud Storage bucket.
Upload the file to your bucket.
For help with uploading files to buckets, seeUploading objects.
Provide your instance with thestorage.objectAdminIAM role for your bucket. For more information about setting IAM permissions, seeUsing IAM permissions.
Import the data from the file:
Before using any of the request data, make the following replacements:
- project-id: The project ID
- instance-id: The instance ID
- bucket_name: The Cloud Storage bucket name
- path_to_bak_file: The path to the BAK file
- database_name: The name of a database inside the Cloud SQL instance
HTTP method and URL:
```
POST https://sqladmin.googleapis.com/v1/projects/project-id/instances/instance-id/import
```
Request JSON body:
```
{ "importContext":   {      "fileType": "BAK",      "uri": "gs://bucket_name/path_to_bak_file",      "database": "database_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.
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-id/import"
```
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 POST `
    -Headers $headers `
    -ContentType: "application/json; charset=utf-8" `
    -InFile request.json `
    -Uri "https://sqladmin.googleapis.com/v1/projects/project-id/instances/instance-id/import" | 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/target-instance-id",  "status": "PENDING",  "user": "user@example.com",  "insertTime": "2020-01-21T22:43:37.981Z",  "operationType": "UPDATE",  "name": "operation-id",  "targetId": "instance-id",  "selfLink": "https://sqladmin.googleapis.com/v1/projects/project-id/operations/operation-id",  "targetProject": "project-id"}
```
To use a different user for the import, specify theimportContext.importUser property.
For the complete list of parameters for the request, see theinstances:import page.
If you don't need to retain the IAM permissions youset previously, then remove the permissions.

REST v1beta4

Create a Cloud Storage bucket.
Upload the file to your bucket.
For help with uploading files to buckets, seeUploading objects.
Provide your instance with thestorage.objectAdminIAM role for your bucket. For more information about setting IAM permissions, see Using IAM permissions.
Import the data from the file:
Before using any of the request data, make the following replacements:
- project-id: The project ID
- instance-id: The instance ID
- bucket_name: The Cloud Storage bucket name
- path_to_bak_file: The path to the BAK file
- database_name: The name of a database inside the Cloud SQL instance
HTTP method and URL:
```
POST https://sqladmin.googleapis.com/sql/v1beta4/projects/project-id/instances/instance-id/import
```
Request JSON body:
```
{ "importContext":   {      "fileType": "BAK",      "uri": "gs://bucket_name/path_to_bak_file",      "database": "database_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.
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-id/import"
```
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 POST `
    -Headers $headers `
    -ContentType: "application/json; charset=utf-8" `
    -InFile request.json `
    -Uri "https://sqladmin.googleapis.com/sql/v1beta4/projects/project-id/instances/instance-id/import" | 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/target-instance-id",  "status": "PENDING",  "user": "user@example.com",  "insertTime": "2020-01-21T22:43:37.981Z",  "operationType": "UPDATE",  "name": "operation-id",  "targetId": "instance-id",  "selfLink": "https://sqladmin.googleapis.com/sql/v1beta4/projects/project-id/operations/operation-id",  "targetProject": "project-id"}
```
To use a different user for the import, specify theimportContext.importUser property.
For the complete list of parameters for the request, see theinstances:import page.
If you don't need to retain the IAM permissions youset previously, then remove the permissions.

If you get an error such asERROR_RDBMS, ensure the BAKfile exists in the bucket and you have the correctpermissions on the bucket. For help configuring access control inCloud Storage, seeCreate and Manage Access Control Lists.

Import differential database backups

Before you import adifferential database backup, you need a full backup import and your database must be in theRESTORING state after the full backup import.

Cloud SQL doesn't support importing differential database backups on instances that are enabled with point-in-time recovery. This is because importing a database backup with--no-recovery is a prerequisite for importing differential database backups. Additionally, you can't enable point-in-time recovery on an instance if the database is in theRESTORING state.In the case of import failure, do one of the following to enable point-in-time recovery:

Bring the database that's in theRESTORING state online by using the--recovery-onlyflag.
Remove the database.

To import data to a Cloud SQL instance using a differential database backup, perform the following steps:

gcloud

Create a Cloud Storage bucket for the import.
```
gcloudstoragebucketscreategs://BUCKET_NAME--location=LOCATION_NAME--project=PROJECT_NAME
```
This step isn't mandatory, but we strongly recommend that you perform it so that you don't open up access to any other data.
Make sure that you've configured the required roles and permissions.
Uploadthe data from the BAK file to the bucket.
Describe the instance that you are importing to:
```
gcloudsqlinstancesdescribeINSTANCE_NAME
```
Copy theserviceAccountEmailAddress field.
Use gcloud storage buckets add-iam-policy-binding to grant thestorage.objectViewerIAM role to the service account for the bucket. For more information about setting IAM permissions, seeUsing IAM permissions.

Import a full backup with--no-recovery.

gcloudsqlimportbakINSTANCE_NAMEgs://BUCKET_NAME/DIFFERENTIAL_BASE_FILENAME\--database=DATABASE_NAME--bak-type=FULL--no-recovery

Import a differential database backup.

gcloudsqlimportbakINSTANCE_NAMEgs://BUCKET_NAME/DIFFERENTIAL_BACKUP_FILENAME\--database=DATABASE_NAME--bak-type=DIFF--no-recovery

After restoring all the backup files, use the--recovery-onlyflag to bring the imported database online from aRESTORING state.Users are strongly encouraged not to useT-SQLcommands to bring the imported database online.
```
gcloudsqlimportbakINSTANCE_NAME\--database=DATABASE_NAME--recovery-only
```
If you don't need to retain the IAM permissions you set previously, then remove them usinggcloud storage buckets remove-iam-policy-binding.

REST v1

Create a Cloud Storage bucket.
Upload the file to your bucket.
For help with uploading files to buckets, seeUploading objects.
Provide your instance with thestorage.objectAdminIAM role for your bucket. For more information about setting IAM permissions, seeUsing IAM permissions.

Note: In the following steps,specify theimportContext.importUser property to use a different user for the import.For the complete list of parameters for the request, see the

instances:import

Import a full backup withnoRecovery.

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

PROJECT_ID: the project ID.
INSTANCE_ID: the instance ID.
BUCKET_NAME: the Cloud Storage bucket name.
PATH_TO_BAK_FILE: the path to the BAK file.
DATABASE_NAME: the name of a database inside the Cloud SQL instance.

HTTP method and URL:

POST https://sqladmin.googleapis.com/v1/projects/PROJECT_ID/instances/INSTANCE_ID/import

Request JSON body:

{ "importContext":   {      "fileType": "BAK",      "uri": "gs://BUCKET_NAME/PATH_TO_BAK_FILE",      "database": "DATABASE_NAME"      "bakImportOptions": {        "noRecovery": true,        "bakType": "FULL",      }    }}

To send your request, choose one of these options:

curl

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_ID/import"

PowerShell

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_ID/import" | 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/TARGET_INSTANCE_ID",  "status": "PENDING",  "insertTime": "2020-01-21T22:43:37.981Z",  "operationType": "IMPORT",  "importContext": {    "uri": {uri},    "database":DATABASE_NAME,    "kind": "sql#importContext",    "fileType": "BAK",    "bakImportOptions": {      "noRecovery": true,      "bakType": FULL,      "recoveryOnly": false    }  },  "name": "OPERATION_ID",  "targetId": "INSTANCE_ID",  "selfLink": "https://sqladmin.googleapis.com/v1/projects/PROJECT_ID/operations/OPERATION_ID",  "targetProject": "PROJECT_ID"}

Import a differential database backup.

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

project-id: the project ID
instance-id: the instance ID
bucket_name: the Cloud Storage bucket name
path_to_bak_file: the path to the BAK file
database_name: the name of a database inside the Cloud SQL instance

HTTP method and URL:

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

Request JSON body:

{ "importContext":   {      "fileType": "BAK",      "uri": "gs://bucket_name/path_to_bak_file",      "database": "database_name"      "bakImportOptions": {        "bakType": "DIFF",        "noRecovery": true,      }    }}

To send your request, choose one of these options:

curl

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-id/import"

PowerShell

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-id/import" | 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/target-instance-id",  "status": "PENDING",  "insertTime": "2020-01-21T22:43:37.981Z",  "operationType": "IMPORT",  "importContext": {    "uri": {uri},    "database":database_name,    "kind": "sql#importContext",    "fileType": "BAK",    "bakImportOptions": {      "noRecovery": false,      "bakType": DIFF,      "recoveryOnly": false    }  },  "name": "operation-id",  "targetId": "instance-id",  "selfLink": "https://sqladmin.googleapis.com/v1/projects/project-id/operations/operation-id",  "targetProject": "project-id"}

After restoring all the backup files, use therecoveryOnlyflag to bring the imported database online from aRESTORING state.Users are strongly encouraged not to useT-SQLcommands to bring the imported database online.

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

PROJECT_ID: the project ID
INSTANCE_ID: the instance ID
BUCKET_NAME: the Cloud Storage bucket name
PATH_TO_BAK_FILE: the path to the BAK file
DATABASE_NAME: the name of a database inside the Cloud SQL instance

HTTP method and URL:

POST https://sqladmin.googleapis.com/v1/projects/PROJECT_ID/instances/INSTANCE_ID/import

Request JSON body:

{ "importContext":   {      "fileType": "BAK",      "uri": "gs://BUCKET_NAME/PATH_TO_BAK_FILE",      "database": "DATABASE_NAME"      "bakImportOptions": {        "recoveryOnly": true,      }    }}

To send your request, choose one of these options:

curl

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_ID/import"

PowerShell

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_ID/import" | 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/TARGET-INSTANCE_ID",  "status": "PENDING",  "insertTime": "2020-01-21T22:43:37.981Z",  "operationType": "IMPORT",  "importContext": {    "uri": {uri},    "database":DATABASE_NAME,    "kind": "sql#importContext",    "fileType": "BAK",    "bakImportOptions": {      "recoveryOnly": true    }  },  "name": "OPERATION_ID",  "targetId": "INSTANCE_ID",  "selfLink": "https://sqladmin.googleapis.com/v1/projects/PROJECT_ID/operations/OPERATION_ID",  "targetProject": "PROJECT_ID"}

If you don't need to retain the IAM permissions youset previously, then remove the permissions.

REST v1beta4

Create a Cloud Storage bucket.
Upload the file to your bucket.
For help with uploading files to buckets, seeUploading objects.
Provide your instance with thestorage.objectAdminIAM role for your bucket. For more information about setting IAM permissions, see Using IAM permissions.

Note: In the following steps,specify theimportContext.importUser property to use a different user for the import.For the complete list of parameters for the request, see the

instances:import

Import a full backup withnoRecovery.

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

PROJECT-ID: the project ID.
INSTANCE_ID: the instance ID.
BUCKET_NAME: the Cloud Storage bucket name.
PATH_TO_BAK_FILE: the path to the BAK file.
DATABASE_NAME: the name of a database inside the Cloud SQL instance.

HTTP method and URL:

POST https://sqladmin.googleapis.com/sql/v1beta4/projects/PROJECT-ID/instances/INSTANCE_ID/import

Request JSON body:

{ "importContext":   {      "fileType": "BAK",      "uri": "gs://BUCKET_NAME/PATH_TO_BAK_FILE",      "database": "DATABASE_NAME"      "bakImportOptions": {        "noRecovery": true,        "bakType": "FULL",      }    }}

To send your request, choose one of these options:

curl

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_ID/import"

PowerShell

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_ID/import" | 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/TARGET_INSTANCE_ID",  "status": "PENDING",  "user": "user@example.com",  "insertTime": "2020-01-21T22:43:37.981Z",  "operationType": "IMPORT",  "importContext": {    "uri": {uri},    "database":DATABASE_NAME,    "kind": "sql#importContext",    "fileType": "BAK",    "bakImportOptions": {      "noRecovery": true,      "bakType": FULL,      "recoveryOnly": false    }  },  "name": "OPERATION_ID",  "targetId": "INSTANCE_ID",  "selfLink": "https://sqladmin.googleapis.com/sql/v1beta4/projects/PROJECT-ID/operations/operation-id",  "targetProject": "PROJECT-ID"}

Import a differential database backup.

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

project-id: the project ID
instance-id: the instance ID
bucket_name: the Cloud Storage bucket name
path_to_bak_file: the path to the BAK file
database_name: the name of a database inside the Cloud SQL instance

HTTP method and URL:

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

Request JSON body:

{ "importContext":   {      "fileType": "BAK",      "uri": "gs://bucket_name/path_to_bak_file",      "database": "database_name"      "bakImportOptions": {        "bakType": "DIFF",        "noRecovery": true,      }    }}

To send your request, choose one of these options:

curl

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-id/import"

PowerShell

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-id/import" | 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/target-instance-id",  "status": "PENDING",  "user": "user@example.com",  "insertTime": "2020-01-21T22:43:37.981Z",  "operationType": "IMPORT",  "importContext": {    "uri": {uri},    "database":database_name,    "kind": "sql#importContext",    "fileType": "BAK",    "bakImportOptions": {      "noRecovery": false,      "bakType": DIFF,      "recoveryOnly": false    }  },  "name": "operation-id",  "targetId": "instance-id",  "selfLink": "https://sqladmin.googleapis.com/sql/v1beta4/projects/project-id/operations/operation-id",  "targetProject": "project-id"}

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

PROJECT_ID: the project ID
INSTANCE_ID: the instance ID
BUCKET_NAME: the Cloud Storage bucket name
PATH_TO_BAK_FILE: the path to the BAK file
DATABASE_NAME: the name of a database inside the Cloud SQL instance

HTTP method and URL:

POST https://sqladmin.googleapis.com/sql/v1beta4/projects/PROJECT_ID/instances/INSTANCE_ID/import

Request JSON body:

{ "importContext":   {      "fileType": "BAK",      "uri": "gs://BUCKET_NAME/PATH_TO_BAK_FILE",      "database": "DATABASE_NAME"      "bakImportOptions": {        "recoveryOnly": true,      }    }}

To send your request, choose one of these options:

curl

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_ID/import"

PowerShell

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_ID/import" | 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/TARGET_INSTANCE_ID",  "status": "PENDING",  "user": "user@example.com",  "insertTime": "2020-01-21T22:43:37.981Z",  "operationType": "IMPORT",  "importContext": {    "uri": {uri},    "database":DATABASE_NAME,    "kind": "sql#importContext",    "fileType": "BAK",    "bakImportOptions": {      "recoveryOnly": true    }  },  "name": "OPERATION_ID",  "targetId": "INSTANCE_ID",  "selfLink": "https://sqladmin.googleapis.com/sql/v1beta4/projects/PROJECT_ID/operations/OPERATION_ID",  "targetProject": "PROJECT_ID"}

If you don't need to retain the IAM permissions youset previously, remove the permissions.

If you get an error such asERROR_RDBMS, then ensure that the BAKfile exists in the bucket and you have the correctpermissions on the bucket. For help configuring access control inCloud Storage, seeCreate and Manage Access Control Lists.

Import transaction log backups

Atransaction log is a record of your database's transactions and the modifications made by each transaction.You can use it to re-establish database consistency in the event of a system failure.

Note:

Cloud SQL doesn't support striped import of transaction log backups.
Cloud SQL doesn't support importing transaction log backups on instances that are enabled with point-in-time recovery. This is because importing a database backup with--no-recovery is a prerequisite for importing transaction log backups. Additionally, you can't enable point-in-time recovery on an instance if the database is in theRESTORING state.In the case of import failure, do one of the following to enable point-in-time recovery:
- Bring the database that's in theRESTORING state online by using the--recovery-onlyflag.
- Remove the database.

To import data to a Cloud SQL instance using a transaction log backup, perform the following steps:

gcloud

Optional: Create a Cloud Storage bucket for the import.

gcloudstoragebucketscreategs://BUCKET_NAME--location=LOCATION_NAME--project=PROJECT_NAME

Uploadthe backup files to the bucket.
Describe the instance that you are importing to:
```
gcloudsqlinstancesdescribeINSTANCE_NAME
```
Copy theserviceAccountEmailAddress field.
Use gcloud storage buckets add-iam-policy-binding to grant thestorage.objectViewerIAM role to the service account for the bucket. For more information about setting IAM permissions, seeUsing IAM permissions.
Import a full backup using the--no-recovery parameter.Ensure that your database is in theRESTORING state after the full backup import.
```
gcloudsqlimportbakINSTANCE_NAMEgs://BUCKET_NAME/BACKUP_FILENAME\--database=DATABASE_NAME--bak-type=FULL--no-recovery
```
Optional:Import a differential backup.
Import a transaction log backup.
```
gcloudsqlimportbakINSTANCE_NAMEgs://BUCKET_NAME/BACKUP_FILENAME\--database=DATABASE_NAME--bak-type=TLOG--stop-at=STOP_AT_TIMESTAMP--stop-at-mark=STOP_AT_MARK_NAME--no-recovery
```
Replace the following:
- INSTANCE_NAME: the instance name.
- BUCKET_NAME: the Cloud Storage bucket name.
- BACKUP_FILENAME: the name of your backup file.
- DATABASE_NAME: the name of a database inside the Cloud SQL instance.
- STOP_AT_TIMESTAMP: the timestamp at which the transaction log import must stop. This is an optional field and the value must use theRFC 3339 format.
- STOP_AT_MARK_NAME: the marked transaction at which the transaction log import must stop. This is an optional field and can take any string as its value. If the value is in the formatlsn:log-sequence-number, then the transaction log import stops at the given log sequence number.
Repeat this step until all transaction log backups are imported.
After restoring all the backup files, use the--recovery-onlyflag to bring the imported database online from aRESTORING state.Users are strongly encouraged not to useT-SQLcommands to bring the imported database online.
```
gcloudsqlimportbakINSTANCE_NAME\--database=DATABASE_NAME--recovery-only
```
If you don't need to retain the IAM permissions you set previously, then remove them usinggcloud storage buckets remove-iam-policy-binding.

REST v1

Create a Cloud Storage bucket.
Upload the file to your bucket.
For help with uploading files to buckets, seeUploading objects.
Provide your instance with thestorage.objectAdminIAM role for your bucket. For more information about setting IAM permissions, seeUsing IAM permissions.

instances:import

Import a full backup withnoRecovery. Ensure that your database is in theRESTORING state after the full backup import.

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

PROJECT_ID: the project ID.
INSTANCE_ID: the instance ID.
BUCKET_NAME: the Cloud Storage bucket name.
PATH_TO_BAK_FILE: the path to the BAK file.
DATABASE_NAME: the name of a database inside the Cloud SQL instance.

HTTP method and URL:

POST https://sqladmin.googleapis.com/v1/projects/PROJECT_ID/instances/INSTANCE_ID/import

Request JSON body:

{ "importContext":   {      "fileType": "BAK",      "uri": "gs://BUCKET_NAME/PATH_TO_BAK_FILE",      "database": "DATABASE_NAME"      "bakImportOptions": {        "noRecovery": true,        "bakType": "FULL",      }    }}

To send your request, choose one of these options:

curl

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_ID/import"

PowerShell

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_ID/import" | 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/TARGET_INSTANCE_ID",  "status": "PENDING",  "insertTime": "2020-01-21T22:43:37.981Z",  "operationType": "IMPORT",  "importContext": {    "uri": {uri},    "database":DATABASE_NAME,    "kind": "sql#importContext",    "fileType": "BAK",    "bakImportOptions": {      "noRecovery": true,      "bakType": FULL,      "recoveryOnly": false    }  },  "name": "OPERATION_ID",  "targetId": "INSTANCE_ID",  "selfLink": "https://sqladmin.googleapis.com/v1/projects/PROJECT_ID/operations/OPERATION_ID",  "targetProject": "PROJECT_ID"}

Optional:Import a differential backup.
Import a transaction log backup.
Before using any of the request data, make the following replacements:
- PROJECT_ID: the project ID.
- INSTANCE_ID: the instance ID.
- BUCKET_NAME: the Cloud Storage bucket name.
- PATH_TO_TLOG_FILE: the path to the transaction log file.
- DATABASE_NAME: the name of a database inside the Cloud SQL instance.
- STOP_AT_TIMESTAMP: the timestamp at which the transaction log import must stop. This is an optional field and the value must use theRFC 3339 format.
- STOP_AT_MARK_NAME: the marked transaction at which the transaction log import must stop. This is an optional field and can take any string as its value. If the value is in the formatlsn:log-sequence-number, then the transaction log import stops at the given log sequence number.
HTTP method and URL:
```
POST https://sqladmin.googleapis.com/v1/projects/PROJECT_ID/instances/INSTANCE_ID/import
```
Request JSON body:
```
{ "importContext":   {      "fileType": "BAK",      "uri": "gs://BUCKET_NAME/PATH_TO_TLOG_FILE",      "database": "DATABASE_NAME"      "bakImportOptions": {        "bakType": "TLOG",        "stopAt":STOP_AT_TIMESTAMP,        "stopAtMark":STOP_AT_MARK_NAME,        "noRecovery": true,      }    }}
```
To send your request, choose one of these options:
curl
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 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_ID/import"
PowerShell
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 POST `
-Headers $headers `
-ContentType: "application/json; charset=utf-8" `
-InFile request.json `
-Uri "https://sqladmin.googleapis.com/v1/projects/PROJECT_ID/instances/INSTANCE_ID/import" | 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/TARGET_INSTANCE_ID",  "status": "PENDING",  "insertTime": "2020-01-21T22:43:37.981Z",  "operationType": "IMPORT",  "importContext": {    "uri": {uri},    "database":DATABASE_NAME,    "kind": "sql#importContext",    "fileType": "BAK",    "bakImportOptions": {      "noRecovery": false,      "bakType": TLOG,      "recoveryOnly": false    }  },  "name": "OPERATION_ID",  "targetId": "INSTANCE_ID",  "selfLink": "https://sqladmin.googleapis.com/v1/projects/PROJECT_ID/operations/OPERATION_ID",  "targetProject": "PROJECT_ID"}
```
Repeat this step until all transaction log backups are imported.

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

PROJECT_ID: the project ID
INSTANCE_ID: the instance ID
BUCKET_NAME: the Cloud Storage bucket name
PATH_TO_BAK_FILE: the path to the BAK file
DATABASE_NAME: the name of a database inside the Cloud SQL instance

HTTP method and URL:

POST https://sqladmin.googleapis.com/v1/projects/PROJECT_ID/instances/INSTANCE_ID/import

Request JSON body:

{ "importContext":   {      "fileType": "BAK",      "uri": "gs://BUCKET_NAME/PATH_TO_BAK_FILE",      "database": "DATABASE_NAME"      "bakImportOptions": {        "recoveryOnly": true,      }    }}

To send your request, choose one of these options:

curl

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_ID/import"

PowerShell

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_ID/import" | 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/TARGET-INSTANCE_ID",  "status": "PENDING",  "insertTime": "2020-01-21T22:43:37.981Z",  "operationType": "IMPORT",  "importContext": {    "uri": {uri},    "database":DATABASE_NAME,    "kind": "sql#importContext",    "fileType": "BAK",    "bakImportOptions": {      "recoveryOnly": true    }  },  "name": "OPERATION_ID",  "targetId": "INSTANCE_ID",  "selfLink": "https://sqladmin.googleapis.com/v1/projects/PROJECT_ID/operations/OPERATION_ID",  "targetProject": "PROJECT_ID"}

If you don't need to retain the IAM permissions youset previously, then remove the permissions.

REST v1beta4

Create a Cloud Storage bucket.
Upload the file to your bucket.
For help with uploading files to buckets, seeUploading objects.
Provide your instance with thestorage.objectAdminIAM role for your bucket. For more information about setting IAM permissions, see Using IAM permissions.

Note: In the following steps,specify theimportContext.importUser property to use a different user for the import.For the complete list of parameters for the request, see the

instances:import

Import a full backup withnoRecovery. Ensure that your database is in theRESTORING state after the full backup import.

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

PROJECT-ID: the project ID.
INSTANCE_ID: the instance ID.
BUCKET_NAME: the Cloud Storage bucket name.
PATH_TO_BAK_FILE: the path to the BAK file.
DATABASE_NAME: the name of a database inside the Cloud SQL instance.

HTTP method and URL:

POST https://sqladmin.googleapis.com/sql/v1beta4/projects/PROJECT-ID/instances/INSTANCE_ID/import

Request JSON body:

{ "importContext":   {      "fileType": "BAK",      "uri": "gs://BUCKET_NAME/PATH_TO_BAK_FILE",      "database": "DATABASE_NAME"      "bakImportOptions": {        "noRecovery": true,        "bakType": "FULL",      }    }}

To send your request, choose one of these options:

curl

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_ID/import"

PowerShell

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_ID/import" | 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/TARGET_INSTANCE_ID",  "status": "PENDING",  "user": "user@example.com",  "insertTime": "2020-01-21T22:43:37.981Z",  "operationType": "IMPORT",  "importContext": {    "uri": {uri},    "database":DATABASE_NAME,    "kind": "sql#importContext",    "fileType": "BAK",    "bakImportOptions": {      "noRecovery": true,      "bakType": FULL,      "recoveryOnly": false    }  },  "name": "OPERATION_ID",  "targetId": "INSTANCE_ID",  "selfLink": "https://sqladmin.googleapis.com/sql/v1beta4/projects/PROJECT-ID/operations/operation-id",  "targetProject": "PROJECT-ID"}

Optional:Import a differential backup.
Import a transaction log backup. Here,stopAt andstopAtMarkare optional fields.
Before using any of the request data, make the following replacements:
- PROJECT_ID: the project ID.
- INSTANCE_ID: the instance ID.
- BUCKET_NAME: the Cloud Storage bucket name.
- PATH_TO_BAK_FILE: the path to the BAK file.
- DATABASE_NAME: the name of a database inside the Cloud SQL instance.
- STOP_AT_TIMESTAMP: the timestamp at which the transaction log import must stop. This is an optional field and the value must use theRFC 3339 format.
- STOP_AT_MARK_NAME: the marked transaction at which the transaction log import must stop. This is an optional field and can take any string as its value. If the value is in the formatlsn:log-sequence-number, then the transaction log import stops at the given log sequence number.
HTTP method and URL:
```
POST https://sqladmin.googleapis.com/v1/projects/PROJECT_ID/instances/INSTANCE_ID/import
```
Request JSON body:
```
{ "importContext":   {      "fileType": "BAK",      "uri": "gs://BUCKET_NAME/PATH_TO_BAK_FILE",      "database": "DATABASE_NAME"      "bakImportOptions": {        "bakType": "TLOG",        "stopAt":STOP_AT_TIMESTAMP,        "stopAtMark":STOP_AT_MARK_NAME,        "noRecovery": true,      }    }}
```
To send your request, choose one of these options:
curl
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 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_ID/import"
PowerShell
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 POST `
-Headers $headers `
-ContentType: "application/json; charset=utf-8" `
-InFile request.json `
-Uri "https://sqladmin.googleapis.com/v1/projects/PROJECT_ID/instances/INSTANCE_ID/import" | 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/TARGET_INSTANCE_ID",  "status": "PENDING",  "insertTime": "2020-01-21T22:43:37.981Z",  "operationType": "IMPORT",  "importContext": {    "uri": {uri},    "database":DATABASE_NAME,    "kind": "sql#importContext",    "fileType": "BAK",    "bakImportOptions": {      "noRecovery": false,      "bakType": TLOG,      "recoveryOnly": false    }  },  "name": "OPERATION_ID",  "targetId": "INSTANCE_ID",  "selfLink": "https://sqladmin.googleapis.com/v1/projects/PROJECT_ID/operations/OPERATION_ID",  "targetProject": "PROJECT_ID"}
```
Repeat this step until all transaction log backups are imported.

After restoring all the backup files, userecoveryOnly tobring the imported database online.

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

PROJECT_ID: the project ID
INSTANCE_ID: the instance ID
BUCKET_NAME: the Cloud Storage bucket name
PATH_TO_BAK_FILE: the path to the BAK file
DATABASE_NAME: the name of a database inside the Cloud SQL instance

HTTP method and URL:

POST https://sqladmin.googleapis.com/sql/v1beta4/projects/PROJECT_ID/instances/INSTANCE_ID/import

Request JSON body:

{ "importContext":   {      "fileType": "BAK",      "uri": "gs://BUCKET_NAME/PATH_TO_BAK_FILE",      "database": "DATABASE_NAME"      "bakImportOptions": {        "recoveryOnly": true,      }    }}

To send your request, choose one of these options:

curl

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_ID/import"

PowerShell

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_ID/import" | 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/TARGET_INSTANCE_ID",  "status": "PENDING",  "user": "user@example.com",  "insertTime": "2020-01-21T22:43:37.981Z",  "operationType": "IMPORT",  "importContext": {    "uri": {uri},    "database":DATABASE_NAME,    "kind": "sql#importContext",    "fileType": "BAK",    "bakImportOptions": {      "recoveryOnly": true    }  },  "name": "OPERATION_ID",  "targetId": "INSTANCE_ID",  "selfLink": "https://sqladmin.googleapis.com/sql/v1beta4/projects/PROJECT_ID/operations/OPERATION_ID",  "targetProject": "PROJECT_ID"}

If you don't need to retain the IAM permissions youset previously, then remove the permissions.

Use striped import

The advantages of striped import are the following:

Reductions in the time needed for operations to complete
Databases larger than 5 TB can be imported

Note: Striped import does not support the import of encrypted columns.

A potential disadvantage of using striped import is that all of the files in thestriped set (rather than a single file) must be uploaded to the same folder inyour Cloud Storage bucket, before you perform the import.

Planning your operations

In most use cases, striped import enables better performance with nodisadvantages. However, if you can't back up to a striped set from a giveninstance, or if your database is less than 5 TB, and if faster performance isnot critical, you may want to use a non-striped import.

How to use striped import

gcloud

Create a Cloud Storage bucket for the import.
```
gcloudstoragebucketscreategs://BUCKET_NAME--location=LOCATION_NAME--project=PROJECT_NAME
```
This step isn't required, but strongly recommended, so you don't open up access to any other data.
Make sure you have configured the required IAM roles and permissions.
Create a new folder in your bucket.
To import the database, upload the files of the striped set (of the database) to the new folder. Ensure that all the files are uploaded to the folder, and that the folder contains no extra files.
Describe the instance you are exporting from:
```
gcloudsqlinstancesdescribeINSTANCE_NAME
```
Copy theserviceAccountEmailAddress field.
Use gcloud storage buckets add-iam-policy-binding to grant thestorage.objectViewer IAM role to the service account for the bucket. For more information about setting IAM permissions, see Using IAM permissions.
Import the data from the folder. The difference from a non-striped import is the following: The URI links to the name of the folder to which the stripe set was uploaded, rather than to a single file, and you specify the--striped parameter:
```
gcloudbetasqlimportbakINSTANCE_NAMEgs://BUCKET_NAME/FOLDER_NAME\--database=DATABASE_NAME--striped
```
If you don't need to retain the IAM permissions you set previously, then remove them usinggcloud storage buckets remove-iam-policy-binding.

REST v1

Create a Cloud Storage bucket.
Upload the file to your bucket.
For help with uploading files to buckets, seeUploading objects.
Provide your instance with thestorage.objectAdminIAM role for your bucket. For more information about setting IAM permissions, seeUsing IAM permissions.
Import the data from the file:
Before using any of the request data, make the following replacements:
- project-id: The project ID
- instance-id: The instance ID
- bucket_name: The Cloud Storage bucket name
- path_to_folder: The path to the folder (in the Cloud Storage bucket) where the stripe set is located
- database_name: The name of a database to create in your Cloud SQL instance
- true | false: Set totrue to use striped import
HTTP method and URL:
```
POST https://sqladmin.googleapis.com/v1/projects/project-id/instances/instance-id/import
```
Request JSON body:
```
{ "importContext":   {      "fileType": "BAK",      "uri": "gs://bucket_name/path_to_folder",      "database": "database_name",      "bakImportOptions": {        "striped":true |false      }    }}
```
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 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-id/import"
```
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 POST `
    -Headers $headers `
    -ContentType: "application/json; charset=utf-8" `
    -InFile request.json `
    -Uri "https://sqladmin.googleapis.com/v1/projects/project-id/instances/instance-id/import" | 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/target-instance-id",  "status": "PENDING",  "user": "user@example.com",  "insertTime": "2022-09-21T22:43:37.981Z",  "operationType": "UPDATE",  "name": "operation-id",  "targetId": "instance-id",  "selfLink": "https://sqladmin.googleapis.com/v1/projects/project-id/operations/operation-id",  "targetProject": "project-id"}
```
To use a different user for the import, specify theimportContext.importUser property.
For the complete list of parameters for the request, see theinstances:import page.
If you don't need to retain the IAM permissions youset previously, then remove the permissions.

REST v1beta4

Create a Cloud Storage bucket.
Upload the file to your bucket.
For help with uploading files to buckets, seeUploading objects.
Provide your instance with thestorage.objectAdminIAM role for your bucket. For more information about setting IAM permissions, seeUsing IAM permissions.
Import the data from the file:
Before using any of the request data, make the following replacements:
- project-id: The project ID
- instance-id: The instance ID
- bucket_name: The Cloud Storage bucket name
- path_to_folder: The path to the folder (in the Cloud Storage bucket) where the stripe set is located
- database_name: The name of a database to create in your Cloud SQL instance
- true | false: Set totrue to use striped import
HTTP method and URL:
```
POST https://sqladmin.googleapis.com/sql/v1beta4/projects/project-id/instances/instance-id/import
```
Request JSON body:
```
{ "importContext":   {      "fileType": "BAK",      "uri": "gs://bucket_name/path_to_folder",      "database": "database_name",      "bakImportOptions": {        "striped":true |false      }    }}
```
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 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-id/import"
```
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 POST `
    -Headers $headers `
    -ContentType: "application/json; charset=utf-8" `
    -InFile request.json `
    -Uri "https://sqladmin.googleapis.com/sql/v1beta4/projects/project-id/instances/instance-id/import" | 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/target-instance-id",  "status": "PENDING",  "user": "user@example.com",  "insertTime": "2022-09-21T22:43:37.981Z",  "operationType": "UPDATE",  "name": "operation-id",  "targetId": "instance-id",  "selfLink": "https://sqladmin.googleapis.com/sql/v1beta4/projects/project-id/operations/operation-id",  "targetProject": "project-id"}
```
To use a different user for the import, specify theimportContext.importUser property.
For the complete list of parameters for the request, see theinstances:import page.
If you don't need to retain the IAM permissions youset previously, then remove the permissions.

If you get an error such asERROR_RDBMS, then ensure that the tableexists. If the table exists, then confirm that you have the correctpermissions on the bucket. For help configuring access control inCloud Storage, seeCreate and Manage Access Control Lists.

What's next

Learn how tocheck the status of import and export operations.
Learn more aboutbest practices for importing and exporting data.
Known issues for imports and exports.

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 2026-02-19 UTC.

Movatterモバイル変換

Export and import using BAK files and transaction log files Stay organized with collections Save and categorize content based on your preferences.

Before you begin

Export data from Cloud SQL for SQL Server

Required roles and permissions for exporting from Cloud SQL for SQL Server

Export data to a BAK file from Cloud SQL for SQL Server

Console

gcloud

REST v1

curl (Linux, macOS, or Cloud Shell)

PowerShell (Windows)

Response

REST v1beta4

curl (Linux, macOS, or Cloud Shell)

PowerShell (Windows)

Response

Export differential database backups

gcloud

REST v1

curl

PowerShell

Response

curl

PowerShell

Response

REST v1beta4

curl

PowerShell

Response

curl

PowerShell

Response

Export transaction logs

gcloud

REST

curl

PowerShell

Response

Use striped export

Planning your operations

How to use striped export

gcloud

REST v1

curl (Linux, macOS, or Cloud Shell)

PowerShell (Windows)

Response

REST v1beta4

curl (Linux, macOS, or Cloud Shell)

PowerShell (Windows)

Response

Import to Cloud SQL for SQL Server

Required roles and permissions for importing to Cloud SQL for SQL Server

Import data from a BAK file to Cloud SQL for SQL Server

Console

gcloud

REST v1

curl (Linux, macOS, or Cloud Shell)

PowerShell (Windows)

Response

REST v1beta4

curl (Linux, macOS, or Cloud Shell)

PowerShell (Windows)

Response

Import differential database backups

gcloud

REST v1

curl

PowerShell

Response

curl

PowerShell

Response

curl

PowerShell

Response

REST v1beta4

curl

PowerShell

Response

curl

Export and import using BAK files and transaction log files