RetroSearch Browse

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from http://cloud.google.com/compute/docs/disks/create-snapshots below:

Create archive and standard disk snapshots | Compute Engine Documentation

Skip to main content Create archive and standard disk snapshots

Stay organized with collections Save and categorize content based on your preferences.

Create standard snapshots to periodically back up data from zonal and regional Persistent Disk and Google Cloud Hyperdisk volumes.

You can create snapshots from disks even while they are attached to running instances. Snapshots are, by default, global resources, so you can use them to restore data to a new disk or VM within the same project. For additional data protection and cost management, you can control where you can use your snapshots to create new disks. To restrict the regions where your snapshots can restore data, you can create a regionally scoped snapshot and set allowed access locations (Preview). You can also share snapshots across projects.

Before you begin

(Preview) To create regionally scoped snapshots, set your default snapshot creation and restore locations before you complete the steps on this page.
If you haven't already, then 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 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
1. Install the Google Cloud CLI. After installation, initialize the Google Cloud CLI by running the following command:
```
gcloud init
```
  If you're using an external identity provider (IdP), you must first sign in to the gcloud CLI with your federated identity.
  Note: If you installed the gcloud CLI previously, make sure you have the latest version by running gcloud components update.
2. 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.
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.
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.
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.
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.
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.
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 to projects, folders, and organizations.

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 on the project
- compute.disks.createSnapshot on the disk
To create a snapshot of a regional disk using the data on the disk:
- compute.snapshots.create on the project
- compute.instances.useReadOnly on the source VM
- compute.disks.createSnapshot on the disk
To create a snapshot of a regional disk from a replica recovery checkpoint:
- compute.snapshots.create on the project
- compute.disks.createSnapshot on the disk
(Preview) To create a regionally scoped snapshot:
- compute.snapshots.create on the project
- compute.regionSnapshots.create on the project
- compute.disks.useReadOnly on the disk

You might also be able to get these permissions with custom roles or other predefined roles.

Prepare for creating snapshots

To prepare for creating snapshots of Persistent Disk or Hyperdisk volumes, 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 globally scoped 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.

Important: If you pause your applications before creating a snapshot, resume your workloads only after the snapshot resource reaches the UPLOADING status. For more information, see the table in Manually creating application consistent snapshots. Create a snapshot of Persistent Disk or Hyperdisk volume

The steps to create a snapshot of a disk depend on whether you're creating a snapshot of a zonal disk or regional disk.

Caution: If you try to create a snapshot from a disk and the snapshot creation process fails, you won't be able to delete the original disk volume until you clean up the failed snapshot and capture a clean snapshot. This failsafe helps to prevent the accidental deletion of source data in the event of an unsuccessful backup. Create a snapshot of a zonal disk 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:
1. 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.
2. 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 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

(Preview) To create a regionally scoped snapshot in an allowed region, include the --region flag to indicate where to create your snapshot.

gcloud beta compute snapshots create SNAPSHOT_NAME \
    --region=SNAPSHOT_SCOPE_REGION
    --source-disk=SOURCE_DISK_NAME \
    --source-disk-zone=SOURCE_ZONE \
    --snapshot-type=SNAPSHOT_TYPE

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: For globally scoped snapshots, 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.
SNAPSHOT_SCOPE_REGION: Optional: For regionally scoped snapshots, the region that the snapshot is scoped to. If you include this parameter, you can't use the --storage-location parameter. The STORAGE_LOCATION is automatically set to the SNAPSHOT_SCOPE_REGION.

Note: Google recommends using the gcloud compute snapshots create command instead of the gcloud compute disks snapshot command because it supports more features, such as creating snapshots in a project different from the source disk project. 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

To create a snapshot in the predefined or customized default location configured in your snapshot settings, make a POST request to the snapshots.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 the snapshots.insert method and include the storageLocations 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"
    ],
}

(Preview) To create a regionally scoped snapshot in an allowed region, make a POST request to the snapshots.insert method and define the creation region:

POST https://compute.googleapis.com/compute/beta/projects/DESTINATION_PROJECT_ID/regions/SNAPSHOT_SCOPE_REGION/snapshots
{
    "name": "SNAPSHOT_NAME",
    "sourceDisk": "projects/SOURCE_PROJECT_ID/zones/SOURCE_ZONE/disks/SOURCE_DISK_NAME",
    "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 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: For globally scoped snapshots, 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.
SNAPSHOT_SCOPE_REGION: Optional: For regionally scoped snapshots, the region that the snapshot is scoped to. If you include this parameter, you can't use the storageLocations parameter. The STORAGE_LOCATION is automatically set to the SNAPSHOT_SCOPE_REGION.

Note: Google recommends using the snapshots.insert method instead of the disks.createSnapshot method because it supports more features, such as creating snapshots in a project different from the source disk project. Create a snapshot of a regional disk

You can create snapshots of your regional disk 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.

Important: Google recommends that you use the checkpoint to create standard snapshots only when your degraded replicated disk doesn't have a synced replica available. To avoid data loss, if your degraded disk has a synced replica available, always use the data on the disk to create your snapshot.

After you prepare the disk, you can create a snapshot. When creating a snapshot of a regional 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:
1. 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.
2. 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

(Preview) To create a regionally scoped snapshot in an allowed region, include the --region flag to indicate where to create your snapshot.

gcloud beta compute snapshots create SNAPSHOT_NAME \
    --region=SNAPSHOT_SCOPE_REGION \
    --source-disk=SOURCE_DISK_NAME \
    --source-disk-region=SOURCE_REGION \
    --snapshot-type=SNAPSHOT_TYPE

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: For globally scoped snapshots, 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.
SNAPSHOT_SCOPE_REGION: Optional: For regionally scoped snapshots, the region that the snapshot is scoped to. If you include this parameter, you can't use the --storage-location parameter. The STORAGE_LOCATION is automatically set to the SNAPSHOT_SCOPE_REGION.

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, 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 Storage multi-region or the Cloud Storage region 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 disk. 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

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

To authenticate to Compute Engine, set up Application Default Credentials. For more information, see Set up authentication for a local development environment.

Python Python

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

To create a snapshot in the predefined or customized default location configured in your snapshot settings, make a POST request to the snapshots.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"
}

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"
  ],
}

(Preview) To create a regionally scoped snapshot in an allowed region, make a POST request to the snapshots.insert method and define the creation region:

POST https://compute.googleapis.com/compute/beta/projects/DESTINATION_PROJECT_ID/regions/SNAPSHOT_SCOPE_REGION/snapshots
{
  "name": "SNAPSHOT_NAME",
  "sourceDisk": "projects/SOURCE_PROJECT_ID/regions/SOURCE_REGION/disks/SOURCE_DISK_NAME",
  "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 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: For globally scoped snapshots, 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.
SNAPSHOT_SCOPE_REGION: Optional: For regionally scoped snapshots, the region that the snapshot is scoped to. If you include this parameter, you can't use the storageLocations parameter. The STORAGE_LOCATION is automatically set to the SNAPSHOT_SCOPE_REGION.

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 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 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.

The device is fully replicated and should not create snapshots out of a recovery checkpoint. Please
create regular snapshots instead.

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.

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

Last updated 2025-08-07 UTC.

[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-07 UTC."],[[["Snapshots provide a way to back up data from Zonal Persistent Disk, Regional Persistent Disk, and Google Cloud Hyperdisk volumes, even while they are attached to running instances."],["Snapshots are global resources, meaning they can be used to restore data to a new disk or VM within the same project, and can also be shared across different projects."],["To create a snapshot, users must have specific IAM roles and permissions, such as Compute Instance Admin (v1) and Service Account User (v1), and depending on disk type, can utilize different create methods."],["Before creating snapshots, it's important to review best practices, consider customizing the default storage location, and learn about creating snapshot schedules for regular backups."],["Snapshots can be created using the Console, `gcloud` CLI, Terraform, or REST API, with the option to store them in a predefined default location or a custom storage location."]]],[]]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4