A disk is either a boot disk that is used to start and run the operating system on a compute instance or a non-boot disk that an instance uses only for data storage.
You can use snapshots to backup and restore disk data in the following ways:
After you take a snapshot of a boot or non-boot disk, create a new disk based on the snapshot.
After you take a snapshot of a boot disk, create a new instance based on the boot disk snapshot.
After you take a snapshot of a non-boot disk, create a new instance with a new non-boot disk based on the snapshot.
Before you begin
-
If you haven't already, set up authentication.
Authentication verifies your identity for access to Google Cloud services and APIs. To run
code or samples from a local development environment, you can authenticate to
Compute Engine by selecting one of the following options:
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. After installation, initialize the Google Cloud CLI by running the following command:
gcloud initIf you're using an external identity provider (IdP), you must first sign in to the gcloud CLI with your federated identity.
- Set a default region and zone.
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.
If you're using an external identity provider (IdP), you must first sign in to the gcloud CLI with your federated identity.
If you're using a local shell, then create local authentication credentials for your user account:
gcloud auth application-default login
You don't need to do this if you're using Cloud Shell.
If an authentication error is returned, and you are using an external identity provider (IdP), confirm that you have signed in to the gcloud CLI with your federated identity.
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.
If you're using an external identity provider (IdP), you must first sign in to the gcloud CLI with your federated identity.
If you're using a local shell, then create local authentication credentials for your user account:
gcloud auth application-default login
You don't need to do this if you're using Cloud Shell.
If an authentication error is returned, and you are using an external identity provider (IdP), confirm that you have signed in to the gcloud CLI with your federated identity.
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.
If you're using an external identity provider (IdP), you must first sign in to the gcloud CLI with your federated identity.
If you're using a local shell, then create local authentication credentials for your user account:
gcloud auth application-default login
You don't need to do this if you're using Cloud Shell.
If an authentication error is returned, and you are using an external identity provider (IdP), confirm that you have signed in to the gcloud CLI with your federated identity.
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.
If you're using an external identity provider (IdP), you must first sign in to the gcloud CLI with your federated identity.
If you're using a local shell, then create local authentication credentials for your user account:
gcloud auth application-default login
You don't need to do this if you're using Cloud Shell.
If an authentication error is returned, and you are using an external identity provider (IdP), confirm that you have signed in to the gcloud CLI with your federated identity.
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.
If you're using an external identity provider (IdP), you must first sign in to the gcloud CLI with your federated identity.
For more information, see Authenticate for using REST in the Google Cloud authentication documentation.
-
Required roles
To get the permissions that
you need to restore from a snapshot,
ask your administrator to grant you the
Compute Instance Admin (v1) (roles/compute.instanceAdmin.v1)
IAM role on the project.
For more information about granting roles, see Manage access to projects, folders, and organizations.
This predefined role contains the permissions required to restore from a snapshot. To see the exact permissions that are required, expand the Required permissions section:
Required permissions
The following permissions are required to restore from a snapshot:
-
To create a disk from a globally scoped snapshot (default):
-
compute.disks.createon the project -
compute.instances.attachDiskon the instance -
compute.disks.useon the disk to attach -
compute.snapshots.useReadOnly,compute.snapshots.create, orcompute.disks.createSnapshoton the project
-
- (Preview) To create a disk from a regionally scoped snapshot
-
To create an instance from a boot disk and non-boot disk snapshot, at a minimum, you need the following permissions :
-
compute.instances.createon the project -
compute.snapshots.useReadOnlyon the snapshot -
compute.disks.createon the project -
compute.disks.useon the disk -
compute.instances.attachDiskon the instance
-
You might also be able to get these permissions with custom roles or other predefined roles.
Limitations
The new disk must be at least the same size as the original source disk for the snapshot. If you create a disk that is larger than the original source disk for the snapshot, you must resize the file system on that disk to include the additional disk space. Depending on your operating system and file system type, you might need to use a different file system resizing tool. For more information, see your operating system documentation.
You can create a new zonal or regional disks from a given snapshot at most once every ten minutes. If you want to issue a burst of requests to snapshot your disks, you can issue at most 6 requests in 60 minutes. This limit does not apply when creating regional disks from a snapshot. For more information, see Snapshot frequency limits.
Create a disk from a snapshot and optionally attach it to an instance
If you backed up a boot or non-boot disk with a snapshot, you can create a new disk based on the snapshot.
Console
In the Google Cloud console, go to the Snapshots page.
Find the name of the snapshot that you want to restore.
Go to the Disks page.
Click Create new disk.
Specify the following configuration parameters:
- A name for the disk.
- A type for the disk.
- Optionally, you can override the default region and zone selection. You can select any region and zone, regardless of the storage location of the source snapshot.
Under Source type, click Snapshot.
Select the name of the snapshot to restore.
Select the size of the new disk, in gigabytes. This number must be equal to or larger than the original source disk for the snapshot.
Click Create to create the disk.
Optionally, you can then attach a non-boot disk to a instance.
gcloud
Use the
gcloud compute snapshots listcommand to find the name of the snapshot you want to restore:gcloud compute snapshots list
Use the
gcloud compute snapshots describecommand to find the size of the snapshot you want to restore:gcloud compute snapshots describe SNAPSHOT_NAME
Replace SNAPSHOT_NAME with the name of the snapshot being restored.
Use the
gcloud compute disks createcommand to create a new regional or zonal disk from your snapshot. You can include the--typeflag to specify the type of disk to create.- To create a zonal disk from a globally scoped snapshot:
gcloud compute disks create DISK_NAME \ --zone=ZONE \ --size=DISK_SIZE \ --source-snapshot=SNAPSHOT_NAME \ --type=DISK_TYPE- (Preview) To create a zonal disk from a regionally scoped snapshot:
gcloud beta compute disks create DISK_NAME \ --zone=ZONE \ --source-snapshot=SNAPSHOT_NAME \ --source-snapshot-region=SOURCE_REGION \ --type=DISK_TYPE- To create a regional disk from a globally scoped snapshot:
gcloud beta compute disks create DISK_NAME \ --size=DISK_SIZE \ --source-snapshot=SNAPSHOT_NAME \ --type=DISK_TYPE \ --region=REGION \ --replica-zones=ZONE1,ZONE2- (Preview) To create a regional disk from a regionally scoped snapshot:
gcloud beta compute disks create DISK_NAME \ --size=DISK_SIZE \ --source-snapshot=SNAPSHOT_NAME \ --source-snapshot-region=SOURCE_REGION \ --type=DISK_TYPE \ --region=REGION \ --replica-zones=ZONE1,ZONE2Replace the following:
- DISK_NAME: the name of the new disk
- DISK_SIZE: the size of the new disk, in gibibytes (GiB). This number must be equal to or larger than the original source disk for the snapshot.
- SNAPSHOT_NAME: the name of the snapshot being restored
- DISK_TYPE: the
type of the disk, for example,
pd-ssd,hyperdisk-throughputorhyperdisk-balanced-high-availability - REGION: the region for the regional disk to reside in,
for example:
europe-west1 - SOURCE_REGION: the region that the source snapshot is scoped to
- ZONE: the zone where the new disk will reside
- ZONE1,ZONE2: the zones within the region where the two
disk replicas are located, for example:
europe-west1-bandeurope-west1-c
Optional: Attach the new disk to an existing instance by using the
gcloud compute instances attach-diskcommand:gcloud compute instances attach-disk INSTANCE_NAME \ --disk DISK_NAMEReplace the following:
- INSTANCE_NAME: the name of the instance
- DISK_NAME: the name of the disk made from your snapshot
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
Construct a
GETrequest tosnapshots.listto display the list of snapshots in your project.GET https://compute.googleapis.com/compute/v1/projects/PROJECT_ID/global/snapshots
Replace PROJECT_ID with your project ID.
Construct a
POSTrequest to create a zonal disk or a regional disk using the respectivedisks.insertmethod:- For zonal disks:
disks.insert - For regional disks:
regionDisks.insert
Include the
name,sizeGb, andtypeproperties. To restore a disk using a snapshot, you must include thesourceSnapshotproperty.- To create a zonal disk from a globally scoped snapshot:
POST https://compute.googleapis.com/compute/v1/projects/PROJECT_ID/zones/ZONE/disks { "name": "DISK_NAME", "sourceSnapshot": "SNAPSHOT_NAME", "sizeGb": "DISK_SIZE", "type": "zones/ZONE/diskTypes/DISK_TYPE" }- (Preview) To create a zonal disk from a regionally scoped snapshot:
POST https://compute.googleapis.com/compute/beta/projects/PROJECT_ID/zones/ZONE/disks { "name": "DISK_NAME", "sourceSnapshot": "projects/PROJECT_ID/regions/SOURCE_REGION/snapshots/SNAPSHOT_NAME", "sizeGb": "DISK_SIZE", "type": "projects/PROJECT_ID/zones/ZONE/diskTypes/DISK_TYPE", "zone": "projects/PROJECT_ID/zones/ZONE" }- To create a regional disk from a globally scoped snapshot:
POST https://compute.googleapis.com/compute/beta/projects/PROJECT_ID/regions/REGION/disks { "name": "DISK_NAME", "sourceSnapshot": "SNAPSHOT_NAME", "region": "projects/PROJECT_ID/regions/REGION", "replicaZones": [ "projects/PROJECT_ID/zones/ZONE1", "projects/PROJECT_ID/zones/ZONE2" ], "sizeGb": "DISK_SIZE", "type": "zones/ZONE/diskTypes/DISK_TYPE" }- (Preview) To create a regional disk from a regionally scoped snapshot:
POST https://compute.googleapis.com/compute/beta/projects/PROJECT_ID/regions/REGION/disks { "name": "DISK_NAME", "sourceSnapshot": "projects/PROJECT_ID/regions/SOURCE_REGION/snapshots/SNAPSHOT_NAME", "replicaZones": [ "projects/PROJECT_ID/zones/ZONE1", "projects/PROJECT_ID/zones/ZONE2" ], "sizeGb": "DISK_SIZE", "type": "projects/PROJECT_ID/regions/REGION/diskTypes/DISK_TYPE" }Replace the following:
- PROJECT_ID: your project ID
- ZONE: the zone where your instance and new disk are located
- DISK_NAME: the name of the new disk
- SNAPSHOT_NAME: the source snapshot for the disk that you are restoring
- REGION: the region for the regional disk to reside in,
for example:
europe-west1 - SOURCE_REGION: the region that the source snapshot is scoped to
- ZONE1, ZONE2: the zones where replicas of the new disk should be located
- DISK_SIZE: the size of the new disk, in gibibytes (GiB). This number must be equal to or larger than the original source disk for the snapshot.
- DISK_TYPE: full or partial URL for the
type
of the disk, for example,
PROJECT_ID/zones/ZONE/diskTypes/pd-ssd,PROJECT_ID/zones/ZONE/diskTypes/hyperdisk-balancedorPROJECT_ID/zones/ZONE/diskTypes/hyperdisk-balanced-high-availability
- For zonal disks:
Optional. Attach the new disk to an existing instance.
Construct a
POSTrequest to theinstances.attachDiskmethod, and include the URL to the disk that you just created from your snapshot.For zonal disks:
POST https://compute.googleapis.com/compute/v1/projects/PROJECT_ID/zones/ZONE/instances/INSTANCE_NAME/attachDisk { "source": "/compute/v1/projects/PROJECT_ID/zones/ZONE/disks/DISK_NAME" }For regional disks:
POST https://compute.googleapis.com/compute/v1/projects/PROJECT_ID/zones/ZONE/instances/INSTANCE_NAME/attachDisk { "source": "/compute/v1/projects/PROJECT_ID/regions/REGION/disks/DISK_NAME" }Replace the following:
- PROJECT_ID: your project ID
- ZONE: the zone where your instance and new disk are located
- REGION: the region where the regional disk is located. This must be the same region that the compute instance is located in.
- INSTANCE_NAME: the name of the instance where you are adding the new disk
- DISK_NAME: the name of the new disk
After you create and attach a new disk to an instance, you must mount the disk so that the operating system can use the available storage space.
Create an instance from existing disks
You can create boot disks and data disks from snapshots and then attach these disks to a new compute instance.
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.
Create an instance from a boot disk snapshot
If you created a snapshot of the boot disk of a compute instance,you can use that snapshot to create a new instance.
To quickly create more than one instance with the same boot disk, create a custom image, then create instances from that image instead of using a snapshot.
To create a compute instance with a regional boot disk that was created from a snapshot, use the Google Cloud CLI or REST.
Console
In the Google Cloud console, go to the Create an instance page.
If prompted, select your project and click Continue. The Create an instance page appears and displays the Machine configuration pane.
In the Machine configuration pane, do the following:
- In the Name field, specify a name for your instance. For more information, see Resource naming convention.
Optional: In the Zone field, select a zone for this instance.
The default selection is Any. If you don't change this default selection, then Google automatically chooses a zone for you based on machine type and availability.
Select the machine family for your instance. The Google Cloud console then displays the machine series that are available for your selected machine family. The following machine family options are available:
- General purpose
- Compute optimized
- Memory optimized
- Storage optimized
- GPUs
In the Series column, select the machine series for your instance.
If you selected GPUs as the machine family in the previous step, then select the GPU type that you want. The machine series is then automatically selected for the selected GPU type.
In the Machine type section, select the machine type for your instance.
In the navigation menu, click OS and storage. In the Operating system and storage pane that appears, configure your boot disk by doing the following:
- Click Change. The Boot disk pane appears and displays the Public images tab.
- Click Snapshots. The Snapshot tab appears.
- In the Snapshot list, select the snapshot to use.
- In the Boot disk type list, select the type of the boot disk.
- In the Size (GB) field, specify the size of the boot disk.
- Optional: For advanced configuration options, expand the Show advanced configurations section.
- To confirm your boot disk options and return to the Operating system and storage pane, click Select.
In the navigation menu, click Networking. In the Networking pane that appears, do the following:
- Go to the Firewall section.
- To permit HTTP or HTTPS traffic to the instance, select Allow HTTP traffic or Allow HTTPS traffic.
The Google Cloud console adds a network tag to your instance and creates the corresponding ingress firewall rule that allows all incoming traffic on
tcp:80(HTTP) ortcp:443(HTTPS). The network tag associates the firewall rule with the instance. For more information, see Firewall rules overview in the Virtual Private Cloud documentation.Optional: Specify other configuration options. For more information, see Configuration options during instance creation.
To create and start the instance, click Create.
gcloud
Zonal boot disk
Use the
gcloud compute instances create command
and include the --source-snapshot flag.
gcloud compute instances create INSTANCE_NAME
--source-snapshot=BOOT_SNAPSHOT_NAME
--boot-disk-size=BOOT_DISK_SIZE
--boot-disk-type=BOOT_DISK_TYPE
--boot-disk-device-name=BOOT_DISK_NAME
Replace the following:
INSTANCE_NAME: name for the new instanceBOOT_SNAPSHOT_NAME: name of the boot disk snapshot that you want to restore to the boot disk of the new instanceBOOT_DISK_SIZE: Optional: size, in GiB, of the new boot diskThe size must be equal to or larger than the size of the source disk from which the snapshot was made.
BOOT_DISK_TYPE: Optional: type of the boot disk, for examplePROJECT_ID/zones/ZONE/diskTypes/pd-ssdorPROJECT_ID/zones/ZONE/diskTypes/hyperdisk-balancedBOOT_DISK_NAME: name of the new boot disk for this instance
Regional boot disk
Use the
gcloud compute instances create command
and include the --create-disk flag with the source-snapshot,
replica-zones, and boot properties.
gcloud compute instances create INSTANCE_NAME
--zone=ZONE
--create-disk=^:^name=DISK_NAME:source-snapshot=BOOT_SNAPSHOT_NAME:boot=true:type=BOOT_DISK_TYPE:replica-zones=ZONE,REMOTE_ZONE
The characters ^:^ specify that a colon : is used as the separator
between each of the disk properties. This is required so that you can
use a comma , when specifying the zones for replica-zones.
Replace the following:
INSTANCE_NAME: name for the new instanceZONE: To zone to create the instance inDISK_NAME: Optional: a name for the diskBOOT_SNAPSHOT_NAME: name of the boot disk snapshot that you want to restore to the boot disk of the new instance.BOOT_DISK_TYPE: Optional: type of the boot disk, for examplepd-ssdorhyperdisk-balanced-high-availabilityREMOTE_ZONE: The region that the boot disk is replicated to. Thereplica-zonesproperty requires two zones separated by comma, and one of the zones must the same as the zone for the instance.
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
When you use the API to create an instance from a snapshot, the following restrictions apply:
- Only one disk can be used as the boot disk.
- You must attach the boot disk as the first disk for that instance.
- If you specify the
sourceproperty, you cannot also specify theinitializeParamsproperty. Providing asourceindicates that the boot disk exists already, but theinitializeParamsproperty indicates that Compute Engine should create a new boot disk.
Zonal boot disk
To create an instance from a boot disk snapshot, use theinstances.insert method
and specify the sourceSnapshot field under the
disks property. You can optionally specify the
diskSizeGb and diskType properties for the
new boot disk.
POST https://compute.googleapis.com/compute/v1/projects/PROJECT_ID/zones/ZONE/instances
{
"name": "INSTANCE_NAME",
"machineType": "machineTypes/MACHINE_TYPE",
"disks": [{
"boot": true,
"initializeParams": {
"sourceSnapshot": "global/snapshots/BOOT_SNAPSHOT_NAME",
"diskSizeGb": "BOOT_DISK_SIZE",
"diskType": "BOOT_DISK_TYPE"
}
}],
"networkInterfaces": [
{
"nicType": "GVNIC"
}
]
}
PROJECT_ID: your project IDZONE: zone where you want to create the new instanceINSTANCE_NAME: name of the instance that you want to restore a snapshot toMACHINE_TYPE: machine type of the instanceBOOT_SNAPSHOT_NAME: name of the snapshot that you want to use to create the boot disk of the new instanceBOOT_DISK_SIZE: Optional: size, in gibibytes (GiB), for the new boot diskThe size must be equal to or larger than the size of the source disk from which the snapshot was made.
BOOT_DISK_TYPE: Optional: type of the boot disk, for examplePROJECT_ID/zones/ZONE/diskTypes/pd-ssdorPROJECT_ID/zones/ZONE/diskTypes/hyperdisk-balanced
Regional boot disk
To create a compute instance with a regional boot disk using a boot disk snapshot as the source, use theinstances.insert method
and specify the sourceSnapshot and replicaZones
fields in the disks property.
POST https://compute.googleapis.com/compute/v1/projects/PROJECT_ID/zones/ZONE/instances
{
"name": "INSTANCE_NAME",
"disks": [
{
"boot": true,
"initializeParams": {
"sourceSnapshot": "global/snapshots/BOOT_SNAPSHOT_NAME",
"replicaZones": [
"projects/PROJECT_ID/zones/ZONE",
"projects/PROJECT_ID/zones/REMOTE_ZONE"
],
"diskType": "BOOT_DISK_TYPE"
}
}
],
"networkInterfaces": [
{
"nicType": "GVNIC"
}
]
}
Replace the following:
PROJECT_ID: your project IDZONE: the name of the zone where you want to create the instanceINSTANCE_NAME`: a name for the instanceBOOT_SNAPSHOT_NAME: the name of the boot disk snapshotREMOTE_ZONE: the remote zone for the regional diskBOOT_DISK_TYPE: Optional: type of the boot disk, for examplePROJECT_ID/zones/ZONE/diskTypes/pd-ssdorPROJECT_ID/zones/ZONE/diskTypes/hyperdisk-balanced-high-availability
Create a compute instance from a non-boot disk snapshot
If you backed up a non-boot disk with a snapshot, you can create an instance with an additional non-boot disk based on the snapshot.
Console
When restoring non-boot snapshots to a new instance from the console, first create a disk from each snapshot. Then, attach the new disks when you create the instance.
Restore each non-boot snapshot to a new disk.
In the Google Cloud console, go to the Disks page.
Click Create disk.
Specify a Name for your disk. For more information, see Resource naming convention.
Select the Region and Zone for this disk. The disk and instance must be in the same zone for zonal disks, or region for regional disks.
Select a disk Type.
Under Source type, select Snapshot.
Under the new Source snapshot field, select a non-boot snapshot that you want to restore to the new disk.
To create the disk, click Create.
Repeat these steps to create a disk from each snapshot that you want to restore.
In the Google Cloud console, go to the VM instances page.
Select your project and click Continue.
Click Create instance.
Specify a Name for your instance. For more information, see Resource naming convention.
Select the Region and Zone for this instance. The disk and instance must be in the same zone for zonal disks, or region for regional disks.
Select a Machine type for your instance.
If you want to allow incoming external traffic, change the Firewall rules for the instance.
To attach disks to the instance, expand the Advanced options section, and then do the following:
- Expand the Disks section.
- Click Attach existing disk.
- In the Disk list, select a disk to attach to this instance.
- In the Attachment Setting section, select disk's attachment Mode and the Deletion rule. For more information about adding new disks, see Add a Persistent Disk or Add Hyperdisk.
- Click Save.
Repeat these steps for each disk that you want to attach.
To create and start the instance, click Create.
gcloud
Create an instance by using the
gcloud compute instances create command.
For each non-boot snapshot that you want to restore, include the
--create-disk flag, and specify a source-snapshot.
For example, to restore two snapshots of non-boot disks to a new instance, use the following command:
gcloud compute instances create INSTANCE_NAME \
--create-disk source-snapshot=SNAPSHOT_1_NAME,name=DISK_1_NAME,size=DISK_1_SIZE,type=DISK_1_TYPE \
--create-disk source-snapshot=SNAPSHOT_2_NAME,name=DISK_2_NAME,size=DISK_2_SIZE,type=DISK_2_TYPEReplace the following:
INSTANCE_NAME: name for the new instanceSNAPSHOT_1_NAMEandSNAPSHOT_2_NAME: names of the non-boot disk snapshots that you want to restoreDISK_1_NAMEandDISK_2_NAME: names of the new non-boot disks to create for this instanceDISK_1_SIZEandDISK_2_SIZE: Optional: sizes, in gibibytes (GiB), of each new non-boot diskThe sizes must be equal to or larger than the sizes of the source disks from which the snapshot was made.
DISK_1_TYPEandDISK_2_TYPE: Optional: the disk types to create, for examplepd-ssdorhyperdisk-balanced
REST
When using REST to restore a non-boot snapshot to a new instance, the following restrictions apply:
- Only one disk can be the boot disk.
- You must attach the boot disk as the first disk for that instance.
- If you specify the
sourceproperty, you can't also specify theinitializeParamsproperty. Providing asourceindicates that the boot disk exists already, but theinitializeParamsproperty indicates that Compute Engine should create a new boot disk.
Create a POST request to the
instances.insert method
and specify the sourceSnapshot field under the initializeParams
property. You can add multiple non-boot disks
by repeating the initializeParams property for every non-boot disk that
you want to create. You can optionally specify the diskSizeGb and
diskType properties for any of the disks that you create.
For example, to restore two non-boot disk snapshots to a new instance, make the following request:
POST https://compute.googleapis.com/compute/v1/projects/PROJECT_ID/zones/ZONE/instances
{
"name": "INSTANCE_NAME",
"machineType": "machineTypes/MACHINE_TYPE",
"networkInterfaces": [
{
"nicType": "GVNIC"
}
],
"disks": [
{
"autoDelete": "true",
"boot": "true",
"diskSizeGb": "BOOT_DISK_SIZE",
"diskType": "BOOT_DISK_TYPE",
"initializeParams": {
"sourceImage": "projects/IMAGE_PROJECT/global/images/family/IMAGE_FAMILY"
}
},
{
"deviceName": "DEVICE_1_NAME",
"initializeParams": {
"sourceSnapshot": "global/snapshots/SNAPSHOT_1_NAME",
"diskSizeGb": "DISK_1_SIZE",
"diskType": "DISK_1_TYPE"
}
},
{
"deviceName": "DEVICE_2_NAME",
"initializeParams": {
"sourceSnapshot": "global/snapshots/SNAPSHOT_2_NAME",
"diskSizeGb": "DISK_2_SIZE",
"diskType": "DISK_2_TYPE"
}
}
]
}
Replace the following:
PROJECT_ID: your project IDZONE: zone where you want to create the instanceINSTANCE_NAME: a name for the new instanceMACHINE_TYPE: machine type of the instanceDISK_SIZE: Optional: size, in gibibytes (GiB), of the corresponding diskWhen provided, this property must be equal to or larger than the size of the source disk from which the snapshot was made.
DISK_TYPE: Optional: full or partial URL for the type of the corresponding disk, for example,PROJECT_ID/zones/ZONE/diskTypes/pd-ssdorPROJECT_ID/zones/ZONE/diskTypes/hyperdisk-balancedIMAGE_PROJECT: the project containing the image. For example,debian-cloudIMAGE_FAMILY: an image family. This creates the instance from the most recent, non-deprecated OS image in that family. For example, if you specify"sourceImage": "projects/debian-cloud/global/images/family/debian-11", the Compute Engine creates an instance using the latest version of the OS image in the Debian 11 image family.DEVICE_NAME: Optional: the device name displayed in the guest OS of the instanceSNAPSHOT_NAME: the names of corresponding non-boot disk snapshots that you want to restore to new disks on the instance