Stay organized with collections
Save and categorize content based on your preferences.
This page provides instructions for how to create a new volume from an existing
backup.
Considerations
You can restore backups in in-region backup vaults to any pool within the
backup region.
For backups stored in cross-region backup vaults, you can only restore backups
locally, either from the source vault to the source region or from the
destination vault to the destination region. You can't restore to any other
region. Note that this isn't available for the Flex service level.
If you have set a Minimum enforced retention policy on a backup vault that
contains the backup, the backup can't be deleted before the scheduled date in
the Deletable on field. For more information, see Prevent backup deletion.
When restoring a backup of a large capacity volume, the new volume is
automatically created as a large capacity volume.
Create a new volume from a backup
Console
Go to NetApp Volumes page in the Google Cloud console.
In the Backups page, select the backup you want to open.
At the top of the page, click Create new volume from backup.
In the Volume name field, enter a name for the volume. The name must
be unique to the region, use lowercase letters, numbers, hyphens, and
start with a letter. Your choice is permanent.
Optional: in the Description field, enter a description for the
volume.
Under Storage pool details, select an existing storage pool or create
a new storage pool.
For backups in in-region vaults, all storage pools in the region are
available.
For backups in cross-region vaults, all storage pools in the Standard,
Premium, and Extreme service levels are available.
Under Volume details, enter a share name in the Share name field.
The share name must be unique to the region.
In the Capacity field, enter the capacity of the volume.
For backups where the source volume still exists, the Capacity
field is auto-populated with the source volume size and can't be
changed.
For backups where the source volume no longer exists, specify the
new volume size in GiB. The capacity must be larger than the
Volume usage size (restored) size of the backup.
Optional: select Enable auto-tiering if the storage pool you are
restoring to has auto-tiering enabled. You can also enable this later in
volume settings.
Under the Protocol(s) drop-down menu, select the protocol.
For backups where the source volume still exists, the Protocol(s)
field is auto-populated with the source volume protocols and can't be
changed.
For backups where the source volume no longer exists, specify the same
protocols as the original source volume.
For NFS volumes, complete the following steps:
Click Block volume from deletion when clients are connected in the
Configuration for selected protocol(s) for volumes used as GCVE
datastores.
Under Export rules, complete the following steps:
Click Add rule to add a list of allowed clients, their
associated access level (read and write, or read only), and their
root access. For more information, see
Volume access control using export policies.
Click Done.
For SMB volumes, complete the following steps:
For backups where the source volume still exists, SMB protocol options
aren't displayed. However, you can change them later after the volume
is created, or use the Google Cloud CLI command to restore the volume
and specify the SMB options.
For backups where the source volume no longer exists, choose any
optional protocol configurations. For more information about protocol
options, see Create a new volume.
Optional: under Snapshot configuration, configure a schedule for
volume snapshots:
If you want to make your snapshot directory visible to clients, select
the Make snapshot directory visible checkbox.
If you want to allow scheduled snapshots, select the
Allow scheduled snapshots checkbox.
Using the Hourly, Daily, Weekly, and Monthly
tabs, configure your snapshot schedule:
For each interval (hourly, daily, weekly, or monthly), use the
Snapshots To Keep field to enter the amount of snapshots you want
to keep.
Use the Hour (UTC) and Minute (UTC) fields to enter when the
snapshots will be retained.
Optional: under Backup configuration, assign a backup policy and
backup vault to set up scheduled backups for the new volume.
Select the Allow scheduled backups checkbox.
Use the Backup policy drop-down to choose an existing backup policy
or create a new one.
Use the Backup vault drop-down to choose an existing backup vault
or create a new one.
Under the Labels section, click Add labels to add relevant labels
to your volume.
Click Create.
gcloud
Run the following command to create a new volume from a backup:
VOLUME_NAME: the name of the new volume to restore
the backup to.
LOCATION: the location you want to create the
volume in.
CAPACITY: the size for the new volume. Should be
bigger or equal to the Volume usage size (restored) of the backup.
PROTOCOLS: used for the original volume the backup
was taken from.
SHARE_NAME: the share name for the new volume.
STORAGE_POOL: name of the storage pool within
LOCATION to host the volume.
SOURCE_BACKUP: resource name of the backup to
restore. Format as projects/PROJECT_ID/locations/
LOCATION/backupVaults/BACKUP_VAULT_ID/
backups/BACKUP_ID
[[["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-29 UTC."],[],[],null,["# Create a new volume from an existing backup\n\nThis page provides instructions for how to create a new volume from an existing\nbackup.\n\nConsiderations\n--------------\n\n- You can restore backups in in-region backup vaults to any pool within the\n backup region.\n\n- For backups stored in cross-region backup vaults, you can only restore backups\n locally, either from the source vault to the source region or from the\n destination vault to the destination region. You can't restore to any other\n region. Note that this isn't available for the Flex service level.\n\n- If you have set a Minimum enforced retention policy on a backup vault that\n contains the backup, the backup can't be deleted before the scheduled date in\n the **Deletable on** field. For more information, see [Prevent backup deletion](/netapp/volumes/docs/protect-data/about-backups#prevent_backup_deletion).\n\n- When restoring a backup of a large capacity volume, the new volume is\n automatically created as a large capacity volume.\n\nCreate a new volume from a backup\n---------------------------------\n\n### Console\n\n1. Go to **NetApp Volumes** page in the Google Cloud console.\n\n [Go to NetApp Volumes](https://console.cloud.google.com/netapp/volumes)\n2. Under **Data protection** , click **Backups**.\n\n3. In the **Backups** page, select the backup you want to open.\n\n4. At the top of the page, click **Create new volume from backup**.\n\n5. In the **Volume name** field, enter a name for the volume. The name must\n be unique to the region, use lowercase letters, numbers, hyphens, and\n start with a letter. Your choice is permanent.\n\n6. Optional: in the **Description** field, enter a description for the\n volume.\n\n7. Under **Storage pool details**, select an existing storage pool or create\n a new storage pool.\n\n For backups in in-region vaults, all storage pools in the region are\n available.\n\n For backups in cross-region vaults, all storage pools in the Standard,\n Premium, and Extreme service levels are available.\n8. Under **Volume details** , enter a share name in the **Share name** field.\n The share name must be unique to the region.\n\n9. In the **Capacity** field, enter the capacity of the volume.\n\n 1. For backups where the source volume still exists, the **Capacity**\n field is auto-populated with the source volume size and can't be\n changed.\n\n You can use [Google Cloud CLI command](/netapp/volumes/docs/protect-data/create-volume-from-backup#gcloud)\n to specify a different size.\n 2. For backups where the source volume no longer exists, specify the\n new volume size in GiB. The capacity must be larger than the\n **Volume usage size (restored)** size of the backup.\n\n10. Optional: select **Enable auto-tiering** if the storage pool you are\n restoring to has auto-tiering enabled. You can also enable this later in\n [volume settings](/netapp/volumes/docs/configure-and-use/volumes/manage-auto-tiering#edit-auto-tiering-parameters).\n\n11. Under the **Protocol(s)** drop-down menu, select the protocol.\n\n 1. For backups where the source volume still exists, the **Protocol(s)**\n field is auto-populated with the source volume protocols and can't be\n changed.\n\n 2. For backups where the source volume no longer exists, specify the same\n protocols as the original source volume.\n\n | **Important:** The protocols must match the protocols of the source volume. Otherwise, the volume creation will fail.\n12. For NFS volumes, complete the following steps:\n\n | **Important:** The protocols must match the protocols of the source volume. Otherwise, the volume creation will fail.\n 1. Click **Block volume from deletion when clients are connected** in the\n **Configuration for selected protocol(s)** for volumes used as GCVE\n datastores.\n\n | **Important:** This setting is permanent, you can't change it later.\n 2. Under **Export rules**, complete the following steps:\n\n 1. Click **Add rule** to add a list of allowed clients, their\n associated access level (read and write, or read only), and their\n root access. For more information, see\n [Volume access control using export policies](/netapp/volumes/docs/connect-clients/connect-nfs-clients#volume_access_control_using_export_policies).\n\n 2. Click **Done**.\n\n13. For SMB volumes, complete the following steps:\n\n | **Important:** The protocols must match the protocols of the source volume. Otherwise, the volume creation will fail.\n 1. For backups where the source volume still exists, SMB protocol options\n aren't displayed. However, you can change them later after the volume\n is created, or use the Google Cloud CLI command to restore the volume\n and specify the SMB options.\n\n | **Note:** You can't enable continuous availability share support after volume creation.\n 2. For backups where the source volume no longer exists, choose any\n optional protocol configurations. For more information about protocol\n options, see [Create a new volume](/netapp/volumes/docs/configure-and-use/volumes/create-volume).\n\n14. Optional: under **Snapshot configuration**, configure a schedule for\n volume snapshots:\n\n 1. If you want to make your snapshot directory visible to clients, select\n the **Make snapshot directory visible** checkbox.\n\n 2. If you want to allow scheduled snapshots, select the\n **Allow scheduled snapshots** checkbox.\n\n 3. Using the **Hourly, Daily, Weekly, and Monthly**\n tabs, configure your snapshot schedule:\n\n For each interval (hourly, daily, weekly, or monthly), use the\n **Snapshots To Keep** field to enter the amount of snapshots you want\n to keep.\n Use the **Hour (UTC)** and **Minute (UTC)** fields to enter when the\n snapshots will be retained.\n15. Optional: under **Backup configuration**, assign a backup policy and\n backup vault to set up scheduled backups for the new volume.\n\n 1. Select the **Allow scheduled backups** checkbox.\n\n 2. Use the **Backup policy** drop-down to choose an existing backup policy\n or create a new one.\n\n 3. Use the **Backup vault** drop-down to choose an existing backup vault\n or create a new one.\n\n16. Under the **Labels** section, click **Add labels** to add relevant labels\n to your volume.\n\n17. Click **Create**.\n\n### gcloud\n\nRun the following command to create a new volume from a backup: \n\n```bash\ngcloud netapp volumes create VOLUME_NAME \\\n --location=LOCATION \\\n --capacity=CAPACITY \\\n --protocols=PROTOCOLS \\\n --share-name=SHARE_NAME \\\n --storage-pool=STORAGE_POOL \\\n --source-backup=SOURCE_BACKUP \\\n --description=DESCRIPTION\n```\n\nReplace the following information:\n\n- \u003cvar translate=\"no\"\u003eVOLUME_NAME\u003c/var\u003e: the name of the new volume to restore\n the backup to.\n\n- \u003cvar translate=\"no\"\u003eLOCATION\u003c/var\u003e: the location you want to create the\n volume in.\n\n- \u003cvar translate=\"no\"\u003eCAPACITY\u003c/var\u003e: the size for the new volume. Should be\n bigger or equal to the **Volume usage size (restored)** of the backup.\n\n- \u003cvar translate=\"no\"\u003ePROTOCOLS\u003c/var\u003e: used for the original volume the backup\n was taken from.\n\n- \u003cvar translate=\"no\"\u003eSHARE_NAME\u003c/var\u003e: the share name for the new volume.\n\n- \u003cvar translate=\"no\"\u003eSTORAGE_POOL\u003c/var\u003e: name of the storage pool within\n \u003cvar translate=\"no\"\u003eLOCATION\u003c/var\u003e to host the volume.\n\n- \u003cvar translate=\"no\"\u003eSOURCE_BACKUP\u003c/var\u003e: resource name of the backup to\n restore. Format as projects/\u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e/locations/\n \u003cvar translate=\"no\"\u003eLOCATION\u003c/var\u003e/backupVaults/\u003cvar translate=\"no\"\u003eBACKUP_VAULT_ID\u003c/var\u003e/\n backups/\u003cvar translate=\"no\"\u003eBACKUP_ID\u003c/var\u003e\n\n- \u003cvar translate=\"no\"\u003eDESCRIPTION\u003c/var\u003e: the description for the volume.\n\nYou can add other protocol-specific options such as export policies or\nsnapshot policies. For more options, see\n[Google Cloud SDK documentation for NetApp Volumes](/sdk/gcloud/reference/netapp/volumes/create).\n\nWhat's next\n-----------\n\n[Manage your backups](/netapp/volumes/docs/protect-data/manage-backup)."]]