Transition from NetApp Cloud Volumes Service to Google Cloud NetApp Volumes

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. CVS-Performance volumes that haven't transitioned to NetApp Volumes remain online to clients. Users can't create, update, or delete volumes. They also can't modify volume policies, take volume snapshots, or manage volume replications including disaster recovery for those volumes. If you need to enable these actions, NetApp can assist you with transitioning projects to NetApp Volumes. You can contact a NetApp sales specialist or send a message to [e-mail] to complete your transition to NetApp Volumes.

The CVS-Performance service is no longer covered by the Service Level Agreement for Cloud Volumes Service for Google Cloud.

You can transition your Cloud Volumes Service CVS-Performance service type project resources to Google Cloud NetApp Volumes with no interruption in service to your clients using the Google Cloud console. Network traffic suspends while the connection switches and volumes can't be managed until the switch completes. The transition service creates new storage pools for your volume and shifts all of the following configuration types to NetApp Volumes:

• Volumes

• Volume snapshots

• Active Directory connections

• Volume replications

• Customer-managed encryption key (CMEK)

Some configurations, such as Identity and Access Management permissions, scripts, and Cloud Monitoring, can't transition to NetApp Volumes. Instead, we recommend creating new configurations for NetApp Volumes.

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 transition process. To set up access, follow the NetApp Volumes configuration steps from Select or create a Google Cloud project up to Set up Identity and Access Management permissions. You must enable NetApp Volumes API and configure network peering or the transition will fail.

  When setting up Virtual Private Cloud peering, don't create a new IP address range as specified in Configure private services access. Instead, you must use the same IP address range that you used for peering the CVS-Performance service type. If you used multiple IP address ranges for Cloud Volumes Service, you must use all of the same IP address ranges for NetApp Volumes.

  Use the following instructions to find the names for the existing IP address ranges using Google Cloud console or Google Cloud CLI.

  Console

  1. In the Google Cloud console, go to the VPC network page.

  2. Select the relevant VPC and click the Private services access tab.

  3. Find the name of the allocated IP address range used for private connection netapp-cv-nw-customer-peer.

  4. Select and copy the name of IP address range for use in NetApp Volumes peering command.

  5. Repeat the previous steps for every VPC used for Cloud Volumes Service.

  gcloud

  Use the following Google Cloud CLI commands to find the names for the existing IP address ranges:

  1. Find all Virtual Private Cloud peered to the CVS-Performance service type:

     gcloud --project PROJECT_NAME compute networks list \
      --filter="peerings[].name=netapp-cv-nw-customer-peer" \
      --format="table(name, peerings.name)"

     Replace the following information:

     • PROJECT_NAME: the name of your project.

  2. For each identified Virtual Private Cloud, list the peering ranges:

     gcloud --project PROJECT_NAME services vpc-peerings list \
      --network=vpc \
      --service cloudvolumesgcp-api-network.netapp.com \
      --format="value(reservedPeeringRanges)"

     Replace the following information:

     • PROJECT_NAME: the name of your project.

     • VPC: enter vpc.

     Use the identified IP address range name for the --ranges parameter as specified in Configure private services access.

     Make sure to peer all Virtual Private Cloud used for the CVS-Performance service type in case you peered more than one network.

• Naming resources must follow Google Cloud resource naming format: if required, you must change Cloud Volumes Service resource names to follow the Google Cloud resource naming format. The names must also be unique in order to transition to NetApp Volumes. If a name isn't unique and doesn't follow the resource naming format, NetApp Volumes automatically renames the resource during the transition to a name that follows both requirements. You can rename your resources in Cloud Volumes Service before you transition. Once your resources are in NetApp Volumes, you can't change or rename them.

• All projects within a Shared VPC must be reviewed before transitioning: if your projects use a Shared VPC, you must review each project, host, and any associated service projects, in each region that contains resources to identify resource naming issues or any other known issues. After you have resolved all issues, use the host project for a final review and to launch the transition of all projects in the Shared VPC.

• Enable the API: enable the Cloud Volumes Service API on the host project, even if it has no CVS resources. Also, enable NetApp Volumes API and Service Networking API on all projects.

Considerations

• Service type: only the CVS-Performance service type can transfer from Cloud Volumes Service to NetApp Volumes.

• Change in access to resources during transition: project administrators can't view or change resources during the transition, which takes 40 minutes for each project.

• No disruption to clients: the network change takes only a few seconds. It appears as a pause in network traffic to clients and servers but falls within file protocol timeout windows, so no error is reported.

  Ongoing client read and write operations aren't impacted, network addresses, your Virtual Private Cloud, and client mount points don't change, and data doesn't move.

• Customer-managed encryption key settings transition to NetApp Volumes: customer-managed encryption key (CMEK) settings transition to NetApp Volumes, but these settings require additional service account changes.

• Review projects using volume replication: when projects use volume replication, the review checks the resources and replication status of the region you select. You must review the other region in the region pair to check its resources. You must resolve all issues in both regions before you can transition the project. After you resolve the issues, you can start the transition from either region, and the two regions transition together.

• Multiple regions must be reviewed and transitioned separately: if you use other regions, each region must be reviewed and transitioned separately. This includes host projects in all regions which use a Shared VPC even if they have no Cloud Volumes Service resources.

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

• NetApp Volumes supports the use of labels: NetApp Volumes resources, such as volumes, support up to 64 labels for reporting and querying purposes. If you have defined a single label for your Cloud Volumes Service volumes, it transitions to NetApp Volumes. If you use the Cloud Volumes Service label for billing, you need to manually update the label on the storage pool after transition because the label is used for billing with NetApp Volumes. Migrated resources list the is_migrated:true label.

• 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 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 transitioned NetApp Volumes resources.

• NetApp Volumes supports the Standard service level: the Standard service level is available with NetApp Volumes, but there are differences in behavior. Replication for Standard service level volumes is limited to only between other Standard service level volumes. Volumes in a Standard service level pool can't be reassigned to a Premium or Extreme service level pool.

• 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 [e-mail] for help with peering to NetApp Volumes for a successful transition.

Review your project resources

To begin the transition process, review your project resources such as volumes, replications, and snapshots. You might find issues with these project resources, which you can fix before you transition your project.

Use the following instructions to review your project resources:

1. Go to the Transition to NetApp Volumes page in the Google Cloud console.

   Go to Transition to NetApp Volumes

2. Read the considerations under Before you start.

3. Select a region used by the current project and click Review.

4. Under Review transition details, review the following details:

   • Instructions for regions and projects: for replication regions and enabled Shared VPC projects, follow any additional instructions provided for running Review (PreMigrateCheck) and Transition (Migrate).

   • Unsupported configuration: resources with unsupported configurations block you from transitioning to NetApp Volumes. For more information, see Issues that block transition to NetApp Volumes.

   • Automatically renamed resources: resources that don't meet the Google Cloud resource naming convention are renamed during transition. You can use the resource name link to edit the resource and change its name before transition. You can ignore the warnings about renamed Active Directory resources which have no name in Cloud Volumes Service.

   • Resources to be transitioned: the identified resources that can be transitioned along with details for the new storage pools that can be created in this project region. Snapshot resources are not listed.

5. You must resolve all open transition issues before you can transition to NetApp Volumes.

Issues that block transition to NetApp Volumes

You might experience the following unsupported configuration issues during the review when transitioning to NetApp Volumes. You can't proceed with the transition to NetApp Volumes until you resolve the following unsupported configurations:

• Disabled projects: disabled projects are those marked for deletion within 30 days, but not yet deleted. Disabled projects in a Shared VPC can block transition. For more information, see Resource Manager documentation on shutting down projects. To complete the transition, you can either restore the disabled projects or wait 30 days for projects to be deleted.

• Resource in error state: any resources in an error state since creation such as volumes, replications, or snapshots must be deleted or corrected by NetApp before you can transition to NetApp Volumes.

  To resolve this, send a message to [e-mail] for help.

• Cross-region replication between Standard and Premium or Extreme service levels is not supported: NetApp Volumes doesn't support replication between Standard service level volumes and Premium or Extreme service level volumes.

  To resolve this issue, change the service level of the volumes in the replication relationship to use only Standard service level, or only Premium or Extreme service levels.

• Specified key in keyring does not exist or service permissions are incorrect: work with NetApp to fix this issue. Send a message to [e-mail] for help.

• Pre migration error - VPCs not peered to first party service: the customer's project needs to be peered with NetApp Volumes to access NetApp Volumes. To resolve this issue, follow the instructions in Before you begin: Requirements.

• Account not found: Cloud Volumes Service has no record for the host project of the Shared VPC.

  To resolve this issue, use the following instructions:

  1. Enable the NetApp Cloud Volumes API in the host project.

  2. Open the Volumes page for the host project.

  3. Return to the service project and click Review to review the project resources.

• Authentication failure: the user account doesn't have Cloud Volumes Service administrator permissions. Make sure the account has all administrative permissions (netappcloudvolumes.admin) as described in Permissions for Cloud Volumes Service.

Transition to Google Cloud NetApp Volumes

This section provides instructions to transition to Google Cloud NetApp Volumes.

Before you begin

Review the following prerequisites before you transition to NetApp Volumes:

• You must first resolve all issues.

• Complete a review of the following details:

  • All regions used by your project.

  • Host projects and service projects if you use a Shared VPC.

Transition to NetApp Volumes

Use the following instructions to transition to NetApp Volumes:

1. Go to the Transition to NetApp Volumes page in the Google Cloud console.

   Go to Transition to NetApp Volumes

2. Click Transition and wait up to 40 minutes for each project to complete its transition.

   Important: You must start the transition for a Shared VPC from the host project.

   Additional regions, replication, service projects, or large numbers of resources, such as snapshots, can increase transition time.

3. Leave the Transition to NetApp Volumes page open until the transition completes.

4. Click Update status every five minutes for the latest updates.

5. Once the transition is complete, click Open Google Cloud NetApp Volumes to manage your resources, and click Open documentation for more information.

Once the transition is complete, it can take up to 15 minutes to display volume metrics.

If a transition failure between Cloud Volumes Service and NetApp Volumes occurs, users should send a message to [e-mail] for help. In most cases, these failures don't affect Cloud Volumes Service resources, and clients can continue to access their data in Cloud Volumes Service.

Once you complete the transition to NetApp Volumes in a project region, you can't create new Cloud Volumes Service resources in that region.

Known limitations

This section provides details on the known limitations of transitioning to NetApp Volumes.

Links shown for replication issues don't work correctly

When replication relationships are listed under Unsupported configurations, Automatically renamed resources, or Resources to be transitioned in CVS, incorrect replication relationship names and links to the replication resource in CVS are shown.

To resolve the replication resource link issues, you can navigate manually to the Volume replication page to check the replication relationship names or service levels.

Some scheduled snapshot names can change

Scheduled snapshot names from 2022 and before don't follow the Google Cloud resource naming format. These snapshots can be renamed using the current format, like weekly.2023-11-27-1500.

After the transition

Once the transition is complete in all regions used by your project and its associated host and service projects within your VPC, the billing for CVS resources stops. When billing stops, you can then unsubscribe from Cloud Volumes Service.

Unsubscribe from Cloud Volumes Service

Use the following instructions to unsubscribe from Cloud Volumes Service:

1. Go to the Google Cloud Marketplace.

2. Open the product details page for NetApp Cloud Volumes Service.

3. Click Purchased link.

4. Click Manage orders.

5. In the Orders page, click the More options icon for NetApp Cloud Volumes Service.

6. Click Cancel order.

After you complete the transition and unsubscribe from Cloud Volumes Service, NetApp begins to remove networking resources. You also have the option to manually delete the peering from your project to NetApp Cloud Volumes Service using the Google Cloud console or Google Cloud CLI.

NetApp recommends that you wait for at least one day after the transition to allow for the resource removal before you clean up your project.

To clean up your project, use the following instructions:

1. Disable the Cloud Volumes Service API: disable cloudvolumesgcp-api.netapp.com API.

2. Delete the VPC peering(s): delete netapp-cv-nw-customer-peer from your customer VPC to the CVS VPC network netapp-tenant-vpc.