Transition from NetApp Cloud Volumes Service to Google Cloud NetApp Volumes
Stay organized with collections
Save and categorize content based on your preferences.
The Flex service level of Google Cloud NetApp Volumes offers all the capabilities of
the Cloud Volumes Service with the following features:
Enhanced Google Cloud integration which includes API access, Google Cloud CLI,
logging, and more resource labels.
Improved backup and independent scaling of capacity and throughput.
Availability across 40 Google Cloud regions.
Robust and scalable design enhanced through Google engineering.
You can migrate data from your Cloud Volumes Service volumes to Flex using data
copy tools like robocopy for SMB or XCP
for NFS. Due to technical modifications, it isn't possible to do an in-place
transition as supported for the CVS-Performance service.
Before you begin
Review the following requirements and considerations before you begin.
Requirements
Access to NetApp Volumes: you need access to
NetApp Volumes before starting the migration process.
To set up access to NetApp Volumes, follow the
configuration steps.
This process includes the creation of a new pool and volumes that serves as
migration targets.
To transfer files between a Cloud Volumes Service and a Flex volume, establish
Virtual Private Cloud peering and create a new IP address range as specified in
Configure private services access.
Use a virtual machine (VM) within your project, and make sure it resides in
the same zone as the source volume to facilitate the transfer.
Considerations
Service type: you will use Flex service level, as it is the only
NetApp Volumes service level available across the 13 Cloud
Volumes Service regions.
Identity and Access Management roles and permissions:
Identity and Access Management permissions for NetApp Volumes
have new names, but are largely the same as those of Cloud Volumes Service.
You can also use the roles/netapp.admin and roles/netapp.viewer roles to
simplify configuration. The basic roles for editor and owner include
roles/netapp.admin permissions.
Metrics for monitoring and alerting for Cloud Volumes Service and
NetApp Volumes:
the metrics available for monitoring NetApp Volumes
are generally the same as Cloud Volumes Service. If you've configured alerts
or have created a dashboard for Cloud Volumes Service, you need to recreate
these for NetApp Volumes. Your existing Cloud Volumes Service
metrics data remains available, but you can't update metrics data again.
Cloud Logging and Cloud Billing is offered for NetApp Volumes:
NetApp Volumes offers more detailed
Cloud Logging entries,
including administrative user identity. Cloud Billing uses
new SKUs. Your
existing Cloud Volumes Service logging and billing entries remain the same.
NetApp Volumes supports the use of labels:
NetApp Volumes resources, such as volumes, support up to 64
labels for reporting and querying purposes.
Custom scripts: Cloud Volumes Service offers a RESTful API to create
and manage your volumes. NetApp Volumes offers
Google Cloud CLI commands and an
API service that you can use similarly
to create and manage volumes. There is no conversion between them, but if
you need assistance, contact your sales team to learn more about services to
help with conversion.
Terraform support: the Google Cloud Terraform provider
lets you manage NetApp Volumes. After you transition to
NetApp Volumes, your Cloud Volumes Service Terraform *.tf
and state files are no longer valid. To address this, delete *.tf and state
files and import the new
NetApp Volumes resources.
Active Directory or Google Cloud VMware Engine: if you use Google managed
Microsoft Active Directory or Google Cloud VMware Engine services with Cloud
Volumes Service, you can send a message to
google-netapp-volumes-support-external@google.com
for help with peering to NetApp Volumes for a successful
migration.
Migrate to NetApp Volumes
This section provides instructions about migrating your Cloud Volumes Service
volume data to NetApp Volumes.
Before you begin
Review the following prerequisites before you migrate to
NetApp Volumes:
Set up NetApp Volumes which include creation of storage pools
and volumes.
Configure an Active Directory policy, if required.
Migrate to NetApp Volumes
Typically, the customers follow a two-step process. First, they create a
baseline copy, and then perform incremental backups to capture any
modifications.
Mount the
CVS-software volume and NetApp Volumes Flex volume to a VM
within your VPC. Use a data copy tool to
transfer the data to the Flex volume.
During a maintenance window, complete the following steps:
Disconnect the clients from the CVS-software volume.
Perform a final incremental copy of the data to the Flex volume.
Verify that all files are transferred correctly to the volume using file
counts, checksums, or similar methods.
Connect the clients to the Flex volume and test the access.
Data copy tools
We recommend to use robocopy to copy SMB files on a windows VM, and either
NetApp XCP or rsync to copy NFS files on a Linux VM.
Robocopy
Robocopy is a robust Microsoft file copy tool
in Windows systems. Some options to consider when using robocopy include the
following:
/mir: copies all subdirectories, including the empty ones.
/sec/secfix: copies security information access control lists (ACLs),
including for the unchanged files with security changes. For more information,
see robocopy mirroring file permissions.
/z: copies files in restartable mode which allows robocopy to pick up
where it left off, if interrupted.
/mt:32: uses 32 threads for multi-threaded copies.
/b: for backup mode to override file and directory ACLs. Robocopy users
must be a member of the backup operators group on both the source and
destination volumes.
/r:2/w:1: to retry failed copies with a one second wait time.
/log:<logfile>: to log robocopy status output.
XCP
NetApp's XCP tool facilitates rapid and parallel file
copies for data migration to Flex service volumes. For any support using this
tool, you can contact a NetApp sales specialist or send a message to
google-netapp-volumes-support-external@google.com.
[[["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-25 UTC."],[],[],null,["# Transition from NetApp Cloud Volumes Service to Google Cloud NetApp Volumes\n\n| **Announcement:** As of September 30, 2024, NetApp Cloud Volumes Service ended support for the CVS-Performance service and replaced it with [Google Cloud NetApp Volumes](/netapp/volumes/docs/discover/overview). The CVS service, including Standard-software and zone redundant Standard-software, will no longer be supported. CVS service users must migrate their data to the Flex service level of NetApp Volumes. You can contact a NetApp sales specialist or send a message to [google-netapp-volumes-support-external@google.com](mailto:google-netapp-volumes-support-external@google.com) to complete your migration to NetApp Volumes.\n\nThe Flex service level of Google Cloud NetApp Volumes offers all the capabilities of\nthe Cloud Volumes Service with the following features:\n\n- Enhanced Google Cloud integration which includes API access, Google Cloud CLI,\n logging, and more resource labels.\n\n- Improved backup and independent scaling of capacity and throughput.\n\n- Availability across 40 Google Cloud regions.\n\n- Robust and scalable design enhanced through Google engineering.\n\nYou can migrate data from your Cloud Volumes Service volumes to Flex using data\ncopy tools like [robocopy](#robocopy) for SMB or [XCP](https://xcp.netapp.com/)\nfor NFS. Due to technical modifications, it isn't possible to do an in-place\ntransition as supported for the CVS-Performance service.\n\nBefore you begin\n----------------\n\nReview the following requirements and considerations before you begin.\n\n### Requirements\n\n- **Access to NetApp Volumes** : you need access to\n NetApp Volumes before starting the migration process.\n To set up access to NetApp Volumes, follow the\n [configuration steps](/netapp/volumes/docs/get-started/configure-access/workflow#configuration_steps).\n This process includes the creation of a new pool and volumes that serves as\n migration targets.\n\n To transfer files between a Cloud Volumes Service and a Flex volume, establish\n Virtual Private Cloud peering and create a new IP address range as specified in\n [Configure private services access](/netapp/volumes/docs/get-started/configure-access/networking#configure_private_services_access).\n Use a virtual machine (VM) within your project, and make sure it resides in\n the same zone as the source volume to facilitate the transfer.\n\n### Considerations\n\n- **Service type**: you will use Flex service level, as it is the only\n NetApp Volumes service level available across the 13 Cloud\n Volumes Service regions.\n\n- **Identity and Access Management roles and permissions** :\n [Identity and Access Management permissions for NetApp Volumes](/netapp/volumes/docs/get-started/configure-access/iam)\n have new names, but are largely the same as those of Cloud Volumes Service.\n You can also use the `roles/netapp.admin` and `roles/netapp.viewer` roles to\n simplify configuration. The basic roles for `editor` and `owner` include\n `roles/netapp.admin` permissions.\n\n- **Metrics for monitoring and alerting for Cloud Volumes Service and\n NetApp Volumes** :\n the [metrics available for monitoring NetApp Volumes](/netapp/volumes/docs/monitor/cloud-monitoring-metrics)\n are generally the same as Cloud Volumes Service. If you've configured alerts\n or have created a dashboard for Cloud Volumes Service, you need to recreate\n these for NetApp Volumes. Your existing Cloud Volumes Service\n metrics data remains available, but you can't update metrics data again.\n\n- **Cloud Logging and Cloud Billing is offered for NetApp Volumes** :\n NetApp Volumes offers more detailed\n [Cloud Logging](/netapp/volumes/docs/monitor/cloud-logging) entries,\n including administrative user identity. Cloud Billing uses\n [new SKUs](https://cloud.google.com/skus?currency=USD&filter=netapp). Your\n existing Cloud Volumes Service logging and billing entries remain the same.\n\n- **NetApp Volumes supports the use of labels**:\n NetApp Volumes resources, such as volumes, support up to 64\n labels for reporting and querying purposes.\n\n- **Custom scripts** : Cloud Volumes Service offers a RESTful API to create\n and manage your volumes. NetApp Volumes offers\n [Google Cloud CLI commands](/sdk/gcloud/reference/netapp) and an\n [API service](/netapp/volumes/docs/reference/rest) that you can use similarly\n to create and manage volumes. There is no conversion between them, but if\n you need assistance, contact your sales team to learn more about services to\n help with conversion.\n\n- **Terraform support** : the [Google Cloud Terraform provider](https://registry.terraform.io/providers/hashicorp/google/latest/docs)\n lets you manage NetApp Volumes. After you transition to\n NetApp Volumes, your Cloud Volumes Service Terraform `*.tf`\n and state files are no longer valid. To address this, delete `*.tf` and state\n files and [import](/docs/terraform/resource-management/import) the new\n NetApp Volumes resources.\n\n- **Active Directory or Google Cloud VMware Engine** : if you use Google managed\n Microsoft Active Directory or Google Cloud VMware Engine services with Cloud\n Volumes Service, you can send a message to\n [google-netapp-volumes-support-external@google.com](mailto:google-netapp-volumes-support-external@google.com)\n for help with peering to NetApp Volumes for a successful\n migration.\n\nMigrate to NetApp Volumes\n-------------------------\n\nThis section provides instructions about migrating your Cloud Volumes Service\nvolume data to NetApp Volumes.\n\n### Before you begin\n\nReview the following prerequisites before you migrate to\nNetApp Volumes:\n\n- Set up NetApp Volumes which include creation of storage pools\n and volumes.\n\n- Configure an Active Directory policy, if required.\n\n### Migrate to NetApp Volumes\n\nTypically, the customers follow a two-step process. First, they create a\nbaseline copy, and then perform incremental backups to capture any\nmodifications.\n\nFor any support with your migration to NetApp Volumes, send a\nmessage to [google-netapp-volumes-support-external@google.com](mailto:google-netapp-volumes-support-external@google.com).\n\nUse the following instructions to migrate to NetApp Volumes.\n\n1. Create an [Active Directory policy](/netapp/volumes/docs/configure-and-use/active-directory/create-ad-policy),\n if needed. This policy is required for volumes using SMB or NFS with LDAP.\n\n2. Create your NetApp Volumes Flex [pool](/netapp/volumes/docs/configure-and-use/storage-pools/create-storage-pool)\n and [volumes](/netapp/volumes/docs/configure-and-use/volumes/create-volume).\n\n3. [Mount](/netapp/volumes/docs/get-started/quickstarts/mount-volume) the\n CVS-software volume and NetApp Volumes Flex volume to a VM\n within your VPC. Use a [data copy tool](#data-copy-tools) to\n transfer the data to the Flex volume.\n\n4. During a maintenance window, complete the following steps:\n\n 1. Disconnect the clients from the CVS-software volume.\n\n 2. Perform a final incremental copy of the data to the Flex volume.\n\n 3. Verify that all files are transferred correctly to the volume using file\n counts, checksums, or similar methods.\n\n5. Connect the clients to the Flex volume and test the access.\n\nData copy tools\n---------------\n\nWe recommend to use robocopy to copy SMB files on a windows VM, and either\nNetApp XCP or rsync to copy NFS files on a Linux VM.\n\n### Robocopy\n\nRobocopy is a robust Microsoft file copy [tool](https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/robocopy)\nin Windows systems. Some options to consider when using robocopy include the\nfollowing:\n\n- **/mir**: copies all subdirectories, including the empty ones.\n\n- **/sec** **/secfix** : copies security information access control lists (ACLs),\n including for the unchanged files with security changes. For more information,\n see [robocopy mirroring file permissions](https://techcommunity.microsoft.com/blog/filecab/robocopy-mir-switch-8211-mirroring-file-permissions/423662).\n\n- **/z**: copies files in restartable mode which allows robocopy to pick up\n where it left off, if interrupted.\n\n- **/mt:32**: uses 32 threads for multi-threaded copies.\n\n- **/b**: for backup mode to override file and directory ACLs. Robocopy users\n must be a member of the backup operators group on both the source and\n destination volumes.\n\n- **/r:2** **/w:1**: to retry failed copies with a one second wait time.\n\n- **/log:\\\u003clogfile\\\u003e**: to log robocopy status output.\n\n### XCP\n\nNetApp's [XCP tool](https://xcp.netapp.com/) facilitates rapid and parallel file\ncopies for data migration to Flex service volumes. For any support using this\ntool, you can contact a NetApp sales specialist or send a message to\n[google-netapp-volumes-support-external@google.com](mailto:google-netapp-volumes-support-external@google.com)."]]
