Create standard snapshots to periodically back up data from these types of disks:
You can create snapshots from disks even while they are attached to running instances. Snapshots are global resources, so you can use them to restore data to a new disk or VM within the same project. You can also share snapshots across projects.
Before you begin
-
If you haven't already, set up authentication.
Authentication is
the process by which your identity is verified for access to Google Cloud services and APIs.
To run code or samples from a local development environment, you can authenticate to
Compute Engine as follows.
Select the tab for how you plan to use the samples on this page:
Console
When you use the Google Cloud console to access Google Cloud services and APIs, you don't need to set up authentication.
gcloud
-
Install the Google Cloud CLI, then initialize it by running the following command:
gcloud init
- Set a default region and zone.
Terraform
To use the Terraform samples on this page in a local development environment, install and initialize the gcloud CLI, and then set up Application Default Credentials with your user credentials.
- Install the Google Cloud CLI.
-
To initialize the gcloud CLI, run the following command:
gcloud init
-
Create local authentication credentials for your user account:
gcloud auth application-default login
For more information, see Set up authentication for a local development environment.
Go
To use the Go samples on this page in a local development environment, install and initialize the gcloud CLI, and then set up Application Default Credentials with your user credentials.
- Install the Google Cloud CLI.
-
To initialize the gcloud CLI, run the following command:
gcloud init
-
Create local authentication credentials for your user account:
gcloud auth application-default login
For more information, see Set up authentication for a local development environment.
Java
To use the Java samples on this page in a local development environment, install and initialize the gcloud CLI, and then set up Application Default Credentials with your user credentials.
- Install the Google Cloud CLI.
-
To initialize the gcloud CLI, run the following command:
gcloud init
-
Create local authentication credentials for your user account:
gcloud auth application-default login
For more information, see Set up authentication for a local development environment.
Node.js
To use the Node.js samples on this page in a local development environment, install and initialize the gcloud CLI, and then set up Application Default Credentials with your user credentials.
- Install the Google Cloud CLI.
-
To initialize the gcloud CLI, run the following command:
gcloud init
-
Create local authentication credentials for your user account:
gcloud auth application-default login
For more information, see Set up authentication for a local development environment.
Python
To use the Python samples on this page in a local development environment, install and initialize the gcloud CLI, and then set up Application Default Credentials with your user credentials.
- Install the Google Cloud CLI.
-
To initialize the gcloud CLI, run the following command:
gcloud init
-
Create local authentication credentials for your user account:
gcloud auth application-default login
For more information, see Set up authentication for a local development environment.
REST
To use the REST API samples on this page in a local development environment, you use the credentials you provide to the gcloud CLI.
Install the Google Cloud CLI, then initialize it by running the following command:
gcloud init
For more information, see Authenticate for using REST in the Google Cloud authentication documentation.
-
Required roles and permissions
To get the permissions that you need to create a standard snapshot, ask your administrator to grant you the following IAM roles on the project:
-
Compute Instance Admin (v1) (
roles/compute.instanceAdmin.v1
) -
To connect to a VM that can run as a service account:
Service Account User (v1) (
roles/iam.serviceAccountUser
)
For more information about granting roles, see Manage access.
These predefined roles contain the permissions required to create a standard snapshot. To see the exact permissions that are required, expand the Required permissions section:
Required permissions
The following permissions are required to create a standard snapshot:
-
To create a snapshot of a zonal disk:
-
compute.snapshots.create
-
compute.disks.createSnapshot
-
-
To create a snapshot of a regional disk using the data on the disk:
-
compute.snapshots.create
-
compute.instances.useReadOnly
-
compute.disks.createSnapshot
-
-
To create a snapshot of a regional disk from a replica recovery checkpoint:
-
compute.snapshots.create
-
compute.disks.createSnapshot
-
You might also be able to get these permissions with custom roles or other predefined roles.
Prepare for creating snapshots
To prepare for creating Persistent Disk or Hyperdisk snapshots, do the following:
Review Best practices for Compute Engine disk snapshots to prepare your disk for snapshotting.
If you want to customize the default storage location for all your new snapshots, update the snapshot settings for your project. Google Cloud maintains a predefined default storage location value until you update the snapshot settings for the first time. This predefined location is the nearest multi-region to the source disk.
Read Create schedules for disk snapshots to learn about creating a snapshot schedule and attaching it to your disks. Backing up your disks regularly with scheduled snapshots can reduce the risk of unexpected data loss.
Create a snapshot of Persistent Disk volume
The instructions for creating snapshots of Persistent Disk volumes are different, depending on whether you are creating a snapshot of zonal Persistent Disk or regional Persistent Disk.
Create a snapshot of a zonal Persistent Disk volume
Console
-
In the Google Cloud console, go to the VM instances page.
Go to VM instances
The remaining steps will appear automatically in the Google Cloud console. - Select the project that contains your VM instances.
- In the Name column, click the name of the VM that has the disk to back up.
-
In
Storage :- To back up the boot disk, in the Boot disk section, click the Name of the boot disk.
- To back up an attached data disk, in Additional disks, click the Name of the disk.
-
Click
Create snapshot . -
In Name, enter a unique name to help identify the purpose of the snapshot, for example:
boot-disk-snapshot
attached-data-disk-snapshot
-
In Type, the default is a standard snapshot. Standard snapshots are
best for long-term back up and disaster recovery.
Choose Archive snapshot to create a more cost-efficient backup than standard snapshots, but with a longer data recovery time.
For more information, see Snapshot type comparison.
-
In the Location section, choose your snapshot storage location. The predefined or customized default location defined in your snapshot settings is automatically selected. Optionally, you can override the snapshot settings and store your snapshots in a custom storage location by doing the following:
-
Choose the type of storage location that you want for your snapshot.
-
Choose Multi-regional
for higher availability at a higher cost.
- Choose Regional snapshots for more control over the physical location of your data at a lower cost.
-
Choose Multi-regional
for higher availability at a higher cost.
-
In the Select location field, select the specific region or multi-region that you want to use. To use the region or multi-region that is closest to your source disk, choose a location from the section titled Based on disk's location.
-
- To create a snapshot, click Create.
gcloud
You can create your snapshot in the storage location policy defined by your snapshot settings or using an alternative storage location of your choice. For more information, see Choose your snapshot storage location.
To create a snapshot in the predefined or customized default location configured in your snapshot settings, use the
gcloud compute snapshots create
command.gcloud compute snapshots create SNAPSHOT_NAME \ --source-disk-zone=SOURCE_ZONE \ --source-disk=SOURCE_DISK_NAME \ --snapshot-type=SNAPSHOT_TYPE
-
Alternatively, to override the snapshot settings and create a snapshot in a custom storage location, include the
--storage-location
flag to indicate where to store your snapshot.gcloud compute snapshots create SNAPSHOT_NAME \ --source-disk-zone=SOURCE_ZONE \ --source-disk=SOURCE_DISK_NAME \ --snapshot-type=SNAPSHOT_TYPE \ --storage-location=STORAGE_LOCATION
Replace the following:
- SNAPSHOT_NAME: A name for the snapshot.
- SOURCE_ZONE: The zone of the source disk.
- SOURCE_DISK_NAME: The name of the Persistent Disk volume from which you want to create a snapshot.
- SNAPSHOT_TYPE: The snapshot type, either STANDARD or ARCHIVE.
If a snapshot type is not specified, a
STANDARD
snapshot is created. -
STORAGE_LOCATION: Optional: The Cloud Storage multi-region or the Cloud Storage region where you want to store your snapshot. You can specify only one storage location.
Use the
--storage-location
parameter only when you want to override the predefined or customized default storage location configured in your snapshot settings.
Terraform
To create a snapshot of the zonal Persistent Disk volume, use the
google_compute_snapshot
resource.
To learn how to apply or remove a Terraform configuration, see Basic Terraform commands.
Go
Go
Before trying this sample, follow the Go setup instructions in the Compute Engine quickstart using client libraries. For more information, see the Compute Engine Go API reference documentation.
To authenticate to Compute Engine, set up Application Default Credentials. For more information, see Set up authentication for a local development environment.
Java
Java
Before trying this sample, follow the Java setup instructions in the Compute Engine quickstart using client libraries. For more information, see the Compute Engine Java API reference documentation.
To authenticate to Compute Engine, set up Application Default Credentials. For more information, see Set up authentication for a local development environment.
Node.js
Node.js
Before trying this sample, follow the Node.js setup instructions in the Compute Engine quickstart using client libraries. For more information, see the Compute Engine Node.js API reference documentation.
To authenticate to Compute Engine, set up Application Default Credentials. For more information, see Set up authentication for a local development environment.
Python
Python
Before trying this sample, follow the Python setup instructions in the Compute Engine quickstart using client libraries. For more information, see the Compute Engine Python API reference documentation.
To authenticate to Compute Engine, set up Application Default Credentials. For more information, see Set up authentication for a local development environment.
REST
You can create your snapshot in the storage location policy defined by your snapshot settings or using an alternative storage location of your choice. For more information, see Choose your snapshot storage location.
-
To create a snapshot in the predefined or customized default location configured in your snapshot settings, make a
POST
request to thesnapshots.insert
method:POST https://compute.googleapis.com/compute/v1/projects/DESTINATION_PROJECT_ID/global/snapshots { "name": "SNAPSHOT_NAME", "sourceDisk": "projects/SOURCE_PROJECT_ID/zones/SOURCE_ZONE/disks/SOURCE_DISK_NAME", "snapshotType": "SNAPSHOT_TYPE" }
-
Alternatively, to override the snapshot settings and create a snapshot in a custom storage location, make a
POST
request to thesnapshots.insert
method and include thestorageLocations
property in your request:POST https://compute.googleapis.com/compute/v1/projects/DESTINATION_PROJECT_ID/global/snapshots { "name": "SNAPSHOT_NAME", "sourceDisk": "projects/SOURCE_PROJECT_ID/zones/SOURCE_ZONE/disks/SOURCE_DISK_NAME", "snapshotType": "SNAPSHOT_TYPE", "storageLocations": [ "STORAGE_LOCATION" ], }
Replace the following:
- DESTINATION_PROJECT_ID: The ID of project in which you want to create the snapshot.
- SNAPSHOT_NAME: A name for the snapshot.
- SOURCE_PROJECT_ID: The ID of the source disk project.
- SOURCE_ZONE: The zone of the source disk.
- SOURCE_DISK_NAME: The name of the Persistent Disk volume from which you want to create a snapshot.
- SNAPSHOT_TYPE: The snapshot type, either STANDARD or ARCHIVE.
If a snapshot type is not specified, a
STANDARD
snapshot is created. -
STORAGE_LOCATION: Optional: The Cloud Storage multi-region or the Cloud Storage region where you want to store your snapshot. You can specify only one storage location.
Use the
storageLocations
parameter only when you want to override the predefined or customized default storage location configured in your snapshot settings.
Create a snapshot of a regional Persistent Disk volume
You can create snapshots of your regional Persistent Disk volume in one of the following ways:
- By using the data on the source disk. To use this snapshot creation method, you must have a synced zonal replica available.
- By using the replica recovery checkpoint of a degraded disk. You can create snapshots from a checkpoint only by using the Google Cloud CLI or REST.
After you prepare the disk, you can create a snapshot. When creating a snapshot of a regional Persistent Disk, you must indicate the region where the source disk is located.
Console
Go to the Create a Snapshot page in the Google Cloud console.
Go to the Create a Snapshot page- Enter a snapshot Name.
-
Select a Snapshot type. The default is a
STANDARD
snapshot, which is the best option for long-term back up and disaster recovery.Choose Archive snapshot for more cost-efficient data retention.
- Optional: Enter a Description of the snapshot.
- Under Source disk, select the existing disk that you want to create a snapshot of.
In the Location section, choose your snapshot storage location.
The predefined or customized default location defined in your snapshot settings is automatically selected. Optionally, you can override the snapshot settings and store your snapshots in a custom storage location by doing the following:
Choose the type of storage location that you want for your snapshot.
- Choose Multi-regional for higher availability at a higher cost.
- Choose Regional snapshots for more control over the physical location of your data at a lower cost.
- In the Select location field, select the specific region or multi-region that you want to use. To use the region or multi-region that is closest to your source disk, select Based on disk's location.
- Click Create to create the snapshot.
gcloud
You can create a snapshot either by using the source disk's data or its replica recovery checkpoint.
From disk data
You can create a snapshot from your disk's data using the storage location policy defined by your snapshot settings or using an alternative storage location of your choice. For more information, see Choose your snapshot storage location.
To create a snapshot in the predefined or customized default location configured in your snapshot settings, use the
gcloud compute snapshots create
command.gcloud compute snapshots create SNAPSHOT_NAME \ --source-disk-region=SOURCE_REGION \ --source-disk=SOURCE_DISK_NAME \ --snapshot-type=SNAPSHOT_TYPE
-
Alternatively, to override the snapshot settings and create a snapshot in a custom storage location, include the
--storage-location
flag to indicate where to store your snapshot.gcloud compute snapshots create SNAPSHOT_NAME \ --source-disk-region=SOURCE_REGION \ --source-disk=SOURCE_DISK_NAME \ --snapshot-type=SNAPSHOT_TYPE \ --storage-location=STORAGE_LOCATION
Replace the following:
- SNAPSHOT_NAME: A name for the snapshot.
- SOURCE_REGION: The region of the source disk.
- SOURCE_DISK_NAME: The name of the Regional Persistent Disk or Hyperdisk Balanced High Availability volume from which you want to create a snapshot.
- SNAPSHOT_TYPE: The snapshot type, either STANDARD or ARCHIVE.
If a snapshot type is not specified, a
STANDARD
snapshot is created. -
STORAGE_LOCATION: Optional: The Cloud Storage multi-region or the Cloud Storage region where you want to store your snapshot. You can specify only one storage location.
Use the
--storage-location
parameter only when you want to override the predefined or customized default storage location configured in your snapshot settings.
From checkpoint
You can create your snapshot using the replica recovery checkpoint (Preview) of a degraded disk . Your snapshot gets created as long as your incomplete replica is available.
To create a snapshot using the replica recovery checkpoint, use the
gcloud compute snapshots create
command
.
Include the --source-disk-for-recovery-checkpoint
flag to
specify that you want to create the snapshot using a replica recovery
checkpoint. Exclude the --source-disk
and
--source-disk-region
parameters.
gcloud compute snapshots create SNAPSHOT_NAME \ --source-disk-for-recovery-checkpoint=SOURCE_DISK \ --source-disk-for-recovery-checkpoint-region=SOURCE_REGION \ --storage-location=STORAGE_LOCATION \ --snapshot-type=SNAPSHOT_TYPE
Replace the following:
DESTINATION_PROJECT_ID
: The ID of project in which you want to create the snapshot.SNAPSHOT_NAME
: A name for the snapshot.SOURCE_PROJECT_ID
: The project ID of the source disk whose checkpoint you want to use to create the snapshot.SOURCE_REGION
: The region of the source disk whose checkpoint you want to use to create the snapshot.SOURCE_DISK_NAME
: The name of the source disk whose checkpoint you want to use to create the snapshot.STORAGE_LOCATION
: Optional: The Cloud Storagemulti-region or the Cloud Storageregion where you want to store your snapshot. You can specify only one storage location.
Use the only if you want to override the predefined or customized default storage location configured in your snapshot settings.SNAPSHOT_TYPE
: The snapshot type, either STANDARD or ARCHIVE. If a snapshot type is not specified, a STANDARD snapshot is created.
You can use replica recovery checkpoint to create a snapshot only on degraded disks. If you try to create a snapshot from a replica recovery checkpoint when the device is fully replicated, you see the following error message:
The device is fully replicated and should not create snapshots out of a recovery checkpoint. Please create regular snapshots instead.
The Google Cloud CLI waits until the operation returns a status of
READY
, FAILED
, or reaches the maximum timeout and returns the last
known details of the snapshot.
Terraform
The Terraform provider for Google Cloud doesn't support creating a snapshot of a regional Persistent Disk volume. To track this limitation, see the issue on GitHub.
Go
Go
Before trying this sample, follow the Go setup instructions in the Compute Engine quickstart using client libraries. For more information, see the Compute Engine Go API reference documentation.
To authenticate to Compute Engine, set up Application Default Credentials. For more information, see Set up authentication for a local development environment.
Java
Java
Before trying this sample, follow the Java setup instructions in the Compute Engine quickstart using client libraries. For more information, see the Compute Engine Java API reference documentation.
To authenticate to Compute Engine, set up Application Default Credentials. For more information, see Set up authentication for a local development environment.
Node.js
Node.js
Before trying this sample, follow the Node.js setup instructions in the Compute Engine quickstart using client libraries. For more information, see the Compute Engine Node.js API reference documentation.
To authenticate to Compute Engine, set up Application Default Credentials. For more information, see Set up authentication for a local development environment.
Python
Python
Before trying this sample, follow the Python setup instructions in the Compute Engine quickstart using client libraries. For more information, see the Compute Engine Python API reference documentation.
To authenticate to Compute Engine, set up Application Default Credentials. For more information, see Set up authentication for a local development environment.
REST
You can create a snapshot either by using the source disk's data or its replica recovery checkpoint.
From disk data
You can create a snapshot from your disk's data using the storage location policy defined by your snapshot settings or using an alternative storage location of your choice. For more information, see Choose your snapshot storage location.
-
To create a snapshot in the predefined or customized default location configured in your snapshot settings, make a
POST
request to thesnapshots.insert
method:POST https://compute.googleapis.com/compute/v1/projects/DESTINATION_PROJECT_ID/global/snapshots { "name": "SNAPSHOT_NAME", "sourceDisk": "projects/SOURCE_PROJECT_ID/regions/SOURCE_REGION/disks/SOURCE_DISK_NAME", "snapshotType": "SNAPSHOT_TYPE" }
-
Alternatively, to override the snapshot settings and create a snapshot in a custom storage location, make a
POST
request to thesnapshots.insert
method and include thestorageLocations
property in your request:POST https://compute.googleapis.com/compute/v1/projects/DESTINATION_PROJECT_ID/global/snapshots { "name": "SNAPSHOT_NAME", "sourceDisk": "projects/SOURCE_PROJECT_ID/regions/SOURCE_REGION/disks/SOURCE_DISK_NAME", "snapshotType": "SNAPSHOT_TYPE", "storageLocations": [ "STORAGE_LOCATION" ], }
Replace the following:
- DESTINATION_PROJECT_ID: The ID of project in which you want to create the snapshot.
- SNAPSHOT_NAME: A name for the snapshot.
- SOURCE_PROJECT_ID: The ID of the source disk project.
- SOURCE_REGION: The region of the source disk.
- SOURCE_DISK_NAME: The name of the Regional Persistent Disk or Hyperdisk Balanced High Availability volume from which you want to create a snapshot.
- SNAPSHOT_TYPE: The snapshot type, either STANDARD or ARCHIVE.
If a snapshot type is not specified, a
STANDARD
snapshot is created. -
STORAGE_LOCATION: Optional: The Cloud Storage multi-region or the Cloud Storage region where you want to store your snapshot. You can specify only one storage location.
Use the
storageLocations
parameter only when you want to override the predefined or customized default storage location configured in your snapshot settings.
From checkpoint
Alternatively, you can create your snapshot using the replica recovery checkpoint of a degraded disk. Your snapshot gets created as long as your incomplete replica is available.
To create a snapshot using the replica recovery checkpoint, make a
POST
request to the
snapshots.insert
method.
Exclude the sourceDisk
parameter and instead include the
sourceDiskForRecoveryCheckpoint
parameter to specify that
you want to create the snapshot using the checkpoint.
POST https://compute.googleapis.com/compute/v1/projects/DESTINATION_PROJECT_ID/global/snapshots { "name": "SNAPSHOT_NAME", "sourceDiskForRecoveryCheckpoint": "projects/SOURCE_PROJECT_ID/regions/SOURCE_REGION/disks/SOURCE_DISK_NAME", "storageLocations": "STORAGE_LOCATION", "snapshotType": "SNAPSHOT_TYPE" }
Replace the following:
DESTINATION_PROJECT_ID
: The ID of project in which you want to create the snapshot.SNAPSHOT_NAME
: A name for the snapshot.SOURCE_PROJECT_ID
: The project ID of the source disk whose checkpoint you want to use to create the snapshot.SOURCE_REGION
: The region of the source disk whose checkpoint you want to use to create the snapshot.SOURCE_DISK_NAME
: The name of the source disk whose checkpoint you want to use to create the snapshot.STORAGE_LOCATION
: Optional: The Cloud Storagemulti-region or the Cloud Storageregion where you want to store your snapshot. You can specify only one storage location.
Use thestorageLocations
parameter only if you want to override the predefined or customized default storage location configured in your snapshot settings.SNAPSHOT_TYPE
: The snapshot type, either STANDARD or ARCHIVE. If a snapshot type is not specified, a STANDARD snapshot is created.
You can use replica recovery checkpoint to create a snapshot only on degraded disks. If you try to create a snapshot from a replica recovery checkpoint when the device is fully replicated, you see the following error message:
The device is fully replicated and should not create snapshots out of a recovery checkpoint. Please create regular snapshots instead.
Create a snapshot of a Hyperdisk
Console
In the Google Cloud console, go to the VM instances page.
Select the project that contains your VM instances.
In the Name column, click the name of the VM that has the Hyperdisk to back up.
In Storage, in Additional disks, click the Name of the attached Hyperdisk.
Click Create snapshot.
In Name, enter a unique name to help identify the purpose of the snapshot, for example
hyperdisk-data-snapshot
.In Type, the default is a regular snapshot, which is best for long-term back up and disaster recovery.
In the Location section, choose your snapshot storage location.
The predefined or customized default location defined in your snapshot settings is automatically selected. Optionally, you can override the snapshot settings and store your snapshots in a custom storage location by doing the following:
Choose the type of storage location that you want for your snapshot.
- Choose Multi-regional for higher availability at a higher cost.
- Choose Regional snapshots for more control over the physical location of your data at a lower cost.
In the Select location field, select the specific region or multi-region that you want to use. To use the region or multi-region that is closest to your source disk, select Based on disk's location.
Click Create.
gcloud
You can create your snapshot in the storage location policy defined by your snapshot settings or using an alternative storage location of your choice. For more information, see Choose your snapshot storage location.
You must specify a snapshot name. The name must be 1-63 characters long, and comply with RFC 1035.
To create a snapshot in the predefined or customized default location configured in your snapshot settings, use the
gcloud compute snapshots create
command.gcloud compute snapshots create SNAPSHOT_NAME \ --source-disk-zone=SOURCE_ZONE \ --source-disk=SOURCE_DISK_NAME \ --snapshot-type=SNAPSHOT_TYPE
-
Alternatively, to override the snapshot settings and create a snapshot in a custom storage location, include the
--storage-location
flag to indicate where to store your snapshot.gcloud compute snapshots create SNAPSHOT_NAME \ --source-disk-zone=SOURCE_ZONE \ --source-disk=SOURCE_DISK_NAME \ --snapshot-type=SNAPSHOT_TYPE \ --storage-location=STORAGE_LOCATION
Replace the following:
- SNAPSHOT_NAME: A name for the snapshot.
- SOURCE_ZONE: The zone of the source disk.
- SOURCE_DISK_NAME: The name of the Hyperdisk volume from which you want to create a snapshot.
- SNAPSHOT_TYPE: The snapshot type, either STANDARD or ARCHIVE.
If a snapshot type is not specified, a
STANDARD
snapshot is created. -
STORAGE_LOCATION: Optional: The Cloud Storage multi-region or the Cloud Storage region where you want to store your snapshot. You can specify only one storage location.
Use the
--storage-location
parameter only when you want to override the predefined or customized default storage location configured in your snapshot settings.
The gcloud CLI waits until the operation returns a status of
READY
orFAILED
, or reaches the maximum timeout and returns the last known details of the snapshot.
REST
You can create your snapshot in the storage location policy defined by your snapshot settings or using an alternative storage location of your choice. For more information, see Choose your snapshot storage location.
You must specify a snapshot name. The name must be 1-63 characters long, and comply with RFC 1035.
-
To create a snapshot in the predefined or customized default location configured in your snapshot settings, make a
POST
request to thesnapshots.insert
method:POST https://compute.googleapis.com/compute/v1/projects/DESTINATION_PROJECT_ID/global/snapshots { "name": "SNAPSHOT_NAME", "sourceDisk": "projects/SOURCE_PROJECT_ID/zones/SOURCE_ZONE/disks/SOURCE_DISK_NAME", "snapshotType": "SNAPSHOT_TYPE" }
-
Alternatively, to override the snapshot settings and create a snapshot in a custom storage location, make a
POST
request to thesnapshots.insert
method and include thestorageLocations
property in your request:POST https://compute.googleapis.com/compute/v1/projects/DESTINATION_PROJECT_ID/global/snapshots { "name": "SNAPSHOT_NAME", "sourceDisk": "projects/SOURCE_PROJECT_ID/zones/SOURCE_ZONE/disks/SOURCE_DISK_NAME", "snapshotType": "SNAPSHOT_TYPE", "storageLocations": [ "STORAGE_LOCATION" ], }
Replace the following:
- DESTINATION_PROJECT_ID: The ID of project in which you want to create the snapshot.
- SNAPSHOT_NAME: A name for the snapshot.
- SOURCE_PROJECT_ID: The ID of the source disk project.
- SOURCE_ZONE: The zone of the source disk.
- SOURCE_DISK_NAME: The name of the Hyperdisk volume from which you want to create a snapshot.
- SNAPSHOT_TYPE: The snapshot type, either STANDARD or ARCHIVE.
If a snapshot type is not specified, a
STANDARD
snapshot is created. -
STORAGE_LOCATION: Optional: The Cloud Storage multi-region or the Cloud Storage region where you want to store your snapshot. You can specify only one storage location.
Use the
storageLocations
parameter only when you want to override the predefined or customized default storage location configured in your snapshot settings.
What's next
- Learn how to create scheduled snapshots for disks.
- Learn how to view, delete, and share disk snapshots.
- Learn how to create a disk image from your snapshot.