Stay organized with collectionsSave and categorize content based on your preferences.
This page describes how to manage your volumes.
Edit a volume
This section provides details about which volume settings are editable and
instructions for how to edit a volume.
Editable settings
You can change the following settings of a volume after it's created:
Storage pool settings: you can re-assign the volumes of Premium and
Extreme service levels to a different pool to change its service level. Note
that this option isn't available for the Flex and Standard service levels.
For example, if the storage pool hosts a Premium service level volume, you
can re-assign the volume to an Extreme service level storage pool and the
other way around. The change to service levels lets you manage volume
throughput limits and per GiB costs.
Volume details: the capacity of a volume is adjustable up and down in 1
GiB increments. The size of the file data in the volume must be smaller than
the volume capacity. When you increase the volume capacity, the pool that
hosts the volume must have enough available capacity to accommodate the
additional capacity requirement.
Changing the volume capacity can impact the maximum achievable throughput of
volumes of Standard, Premium, or Extreme service level.
If the storage pool doesn't have enough capacity to accommodate the
additional capacity requirement, you can increase the capacity of
the pool, seeStorage pool capacity.
Protocol configurations: you can change the configuration for selected
protocols, but you can't change the protocol itself. For example, if the
volume's protocol type is Server Message Block (SMB), you can choose to
enable or disable SMB encryption, hide or show the SMB share, and enable or
disable access-based enumeration.
Export rules: for volumes that use NFSv3 or NFSv4.1 protocol types, you
can edit the export rules.
Auto-tiering: for volumes in storage pools that allow auto-tiering, you
can enable auto-tiering. Once auto-tiering is enabled, it can be paused and
resumed, but can't be disabled. You can change the cooling threshold value
for each volume. For volumes in custom-performance Flex zonal pools, you can
enable or disable the hot tier bypass. For more information, seeManage auto-tiering.
Snapshot schedules: you can modify the snapshot schedule. You can either
make the snapshot directory visible if you want to enable file system access
to snapshot versions by clients or allow scheduled snapshots to configure the
volume to automatically take snapshots.
Backup configuration: you can do the following in backup configuration:
Set a schedule for automatic backups by attaching abackup policy.
Labels: you can add, modify, or delete labels.
Considerations
Consider the following before you edit a volume:
For volumes in an active volume replication, changes to either the source
or destination volume also apply to the replication partner. For volumes
in astopped replication,
changes apply independently from the replication partner.
For volumes in avolume replicationrelationship, when you change the source volume capacity, the destination
volume capacity also changes. The source and destination pools need enough
available capacity to accommodate the change.
You can only move volumes to pools that are in the same location and have the
same Active Directory policy, customer-managed encryption key (CMEK) policy,
LDAP, and Virtual Private Cloud (VPC) settings as the pool that hosts the
volume.
Auto-tiered volumes can only be moved to a storage pool that allows
auto-tiering, regardless of whether auto-tiering is enabled or paused for
the volume.
Only pools that satisfy the conditional criteria are listed for selections.
The target storage pool needs enough available capacity to accommodate the
volume.
The maximum throughput for Standard, Premium, and Extreme service level
volumes depends on the capacity of the volume and the service level you
chose. An Extreme volume goes twice as fast as a Premium volume of the same
capacity. A larger volume provides higher performance based on additional
IOPS or throughput.
Edit a volume
Use the following instructions to edit a volume using the Google Cloud console or
Google Cloud CLI:
Console
Go to theNetApp Volumespage in the Google Cloud console.
This section provides instructions for how to delete a volume.
Before you begin
When you delete a volume, all of the data and volume snapshots within the
volume get deleted and the capacity of the pool returns. Before you delete a
volume, you mustdelete the replication relationship.
Delete a volume
Use the following instructions to delete a volume using the Google Cloud console or
Google Cloud CLI.
Console
Go to theNetApp Volumespage in the Google Cloud console.
[[["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-09-04 UTC."],[],[],null,["# Manage your volume\n\nThis page describes how to manage your volumes.\n\nEdit a volume\n-------------\n\nThis section provides details about which volume settings are editable and\ninstructions for how to edit a volume.\n\n### Editable settings\n\nYou can change the following settings of a volume after it's created:\n\n- **Storage pool settings**: you can re-assign the volumes of Premium and\n Extreme service levels to a different pool to change its service level. Note\n that this option isn't available for the Flex and Standard service levels.\n For example, if the storage pool hosts a Premium service level volume, you\n can re-assign the volume to an Extreme service level storage pool and the\n other way around. The change to service levels lets you manage volume\n throughput limits and per GiB costs.\n\n- **Volume details**: the capacity of a volume is adjustable up and down in 1\n GiB increments. The size of the file data in the volume must be smaller than\n the volume capacity. When you increase the volume capacity, the pool that\n hosts the volume must have enough available capacity to accommodate the\n additional capacity requirement.\n\n Changing the volume capacity can impact the maximum achievable throughput of\n volumes of Standard, Premium, or Extreme service level.\n\n If the storage pool doesn't have enough capacity to accommodate the\n additional capacity requirement, you can increase the capacity of\n the pool, see [Storage pool capacity](/netapp/volumes/docs/configure-and-use/storage-pools/overview#capacity).\n- **Protocol configurations**: you can change the configuration for selected\n protocols, but you can't change the protocol itself. For example, if the\n volume's protocol type is Server Message Block (SMB), you can choose to\n enable or disable SMB encryption, hide or show the SMB share, and enable or\n disable access-based enumeration.\n\n- **Export rules**: for volumes that use NFSv3 or NFSv4.1 protocol types, you\n can edit the export rules.\n\n- **Auto-tiering** : for volumes in storage pools that allow auto-tiering, you\n can enable auto-tiering. Once auto-tiering is enabled, it can be paused and\n resumed, but can't be disabled. You can change the cooling threshold value\n for each volume. For volumes in custom-performance Flex zonal pools, you can\n enable or disable the hot tier bypass. For more information, see\n [Manage auto-tiering](/netapp/volumes/docs/configure-and-use/volumes/manage-auto-tiering).\n\n- **Snapshot schedules**: you can modify the snapshot schedule. You can either\n make the snapshot directory visible if you want to enable file system access\n to snapshot versions by clients or allow scheduled snapshots to configure the\n volume to automatically take snapshots.\n\n- **Backup configuration**: you can do the following in backup configuration:\n\n - Attach a volume to a [backup vault](/netapp/volumes/docs/protect-data/about-backups#backup_vaults).\n\n - Remove a volume from a [backup vault](/netapp/volumes/docs/protect-data/about-backups#backup_vaults).\n\n - Set a schedule for automatic backups by attaching a [backup policy](/netapp/volumes/docs/protect-data/about-backups#backup_policies).\n\n- **Labels**: you can add, modify, or delete labels.\n\n### Considerations\n\nConsider the following before you edit a volume:\n\n- For volumes in an active volume replication, changes to either the source\n or destination volume also apply to the replication partner. For volumes\n in a [stopped replication](/netapp/volumes/docs/protect-data/stop-or-resume-replication),\n changes apply independently from the replication partner.\n\n- For volumes in a [volume replication](/netapp/volumes/docs/protect-data/about-volume-replication)\n relationship, when you change the source volume capacity, the destination\n volume capacity also changes. The source and destination pools need enough\n available capacity to accommodate the change.\n\n- You can only move volumes to pools that are in the same location and have the\n same Active Directory policy, customer-managed encryption key (CMEK) policy,\n LDAP, and Virtual Private Cloud (VPC) settings as the pool that hosts the\n volume.\n Auto-tiered volumes can only be moved to a storage pool that allows\n auto-tiering, regardless of whether auto-tiering is enabled or paused for\n the volume.\n\n- Only pools that satisfy the conditional criteria are listed for selections.\n The target storage pool needs enough available capacity to accommodate the\n volume.\n\n- The maximum throughput for Standard, Premium, and Extreme service level\n volumes depends on the capacity of the volume and the service level you\n chose. An Extreme volume goes twice as fast as a Premium volume of the same\n capacity. A larger volume provides higher performance based on additional\n IOPS or throughput.\n\n### Edit a volume\n\nUse the following instructions to edit a volume using the Google Cloud console or\nGoogle Cloud CLI: \n\n### Console\n\n1. Go to the **NetApp Volumes** page in the Google Cloud console.\n\n [Go to NetApp Volumes](https://console.cloud.google.com/netapp/volumes)\n2. Identify the volume you want to edit.\n\n3. Click more_vert **Show more**\n icon on the volume and click **Edit**.\n\n4. Edit volume details and save your changes.\n\n### gcloud\n\nEdit a volume using the following command: \n\n```bash\ngcloud netapp volumes update VOLUME_ID \\\n --project=PROJECT_ID \\\n --location=LOCATION \\\n --storage-pool=STORAGE_POOL \\\n --description=DESCRIPTION \\\n --capacity=CAPACITY \\\n --share-name=SHARE_NAME\n```\n\nReplace the following information:\n\n- \u003cvar translate=\"no\"\u003eVOLUME_ID\u003c/var\u003e: the ID of the volume.\n\n- \u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e: the name of the project to\n create the volume in.\n\n- \u003cvar translate=\"no\"\u003eLOCATION\u003c/var\u003e: the location for the volume.\n\n- \u003cvar translate=\"no\"\u003eSTORAGE_POOL\u003c/var\u003e: the storage pool to create the volume\n in.\n\n- \u003cvar translate=\"no\"\u003eDESCRIPTION\u003c/var\u003e: the new description of the volume.\n\n- \u003cvar translate=\"no\"\u003eCAPACITY\u003c/var\u003e: the size of the volume. It defines\n the capacity that NAS clients see.\n\n### Example to edit a volume\n\nThe following example shows you how to edit a volume: \n\n```json\ngcloud netapp volumes update volume-id --project=project-id --location=us-central1 --storage-pool=pool-id --description=description --capacity=capacity --share-name=share-name\n```\n\n### Example to edit an auto-tiered volume\n\nThe following example shows you how to edit an auto-tiered volume: \n\n```json\ngcloud beta netapp volumes update volume-id --project=project-id --location=location --tiering-policy=tier-action=ENABLED,cooling-threshold-days=31\n```\n\nFor more information on additional optional flags, see\n[Google Cloud SDK documentation on volumes](/sdk/gcloud/reference/netapp/volumes/update).\n\nDelete a volume\n---------------\n\nThis section provides instructions for how to delete a volume.\n\n### Before you begin\n\nWhen you delete a volume, all of the data and volume snapshots within the\nvolume get deleted and the capacity of the pool returns. Before you delete a\nvolume, you must [delete the replication relationship](/netapp/volumes/docs/protect-data/delete-replication).\n\n### Delete a volume\n\nUse the following instructions to delete a volume using the Google Cloud console or\nGoogle Cloud CLI. \n\n### Console\n\n1. Go to the **NetApp Volumes** page in the Google Cloud console.\n\n [Go to NetApp Volumes](https://console.cloud.google.com/netapp/volumes)\n2. Identify the volume you want to delete.\n\n3. Click the more_vert **Show more**\n icon on the volume and click **Delete**.\n\n4. A confirmation dialog appears. Read through the warnings.\n\n5. To proceed, enter the name of the volume and click **Delete**.\n\n### gcloud\n\nRun the following command: \n\n```bash\n gcloud netapp volumes delete VOLUME_NAME \\\n --project=PROJECT_ID \\\n --location=LOCATION\n```\n\nReplace the following information:\n\n- \u003cvar translate=\"no\"\u003eVOLUME_NAME\u003c/var\u003e: the name of the volume to delete\n\n- \u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e: the name of the project the volume is\n in\n\n- \u003cvar translate=\"no\"\u003eLOCATION\u003c/var\u003e: The location of the volume\n\nFor more information on additional optional flags, see\n[Google Cloud SDK documentation on volumes](/sdk/gcloud/reference/netapp/volumes).\n\nWhat's next\n-----------\n\n[Manage quota rules](/netapp/volumes/docs/configure-and-use/volumes/manage-quota-rules)."]]
