This page provides details on known limitations of Google Cloud NetApp Volumes.
General issues
This section describes common known issues of NetApp Volumes.
NetApp Volumes doesn't work in an existing project with NetApp Cloud Volumes Service
NetApp Volumes fails to run in an existing Google Cloud project with NetApp Cloud Volumes Service if the two services have resources in the same region. The following message displays when you try to create resources:
Error, resources from CVS and NetApp Volumes may not be used together in a single region. Project <project_number> is currently using the CVS service.
To resolve this, you can create a new project on a different Virtual Private Cloud (VPC) and try to use NetApp Volumes again.
NetApp Volumes and NetApp Cloud Volumes Service for Google Cloud projects cannot exist on the same Shared VPC
NetApp Volumes and Cloud Volumes Service projects can't coexist on the same Shared VPC. The following message displays when you try to use two projects that use either of the two APIs and are using the same Shared VPC:
Error when creating - Error networks.CreateNetworkV1 - Cannot share VPC between 3P and 1P projects - [400])
message displays when you try to create projects with both services on the same
Shared VPC.
To resolve this, you can create a new project on a different VPC and try to access NetApp Volumes again.
Intermittent connectivity loss when using overlapping Private Services Access connections
When configuring
the netapp.servicenetworking.goog connection, if the CIDR range overlaps with
the CIDR range used by another private services access connection on the same
VPC, it can result in intermittent connectivity loss of the volume mount
connection. Use non-overlapping ranges to avoid this problem.
Active Directory integration issues
Connections to on-premise domain controllers fail due to the following limitations:
VPC peering: NetApp Volumes can only reach domain controllers that are on the storage pool's Virtual Private Cloud (VPC) or are connected to it by VPN. NetApp Volumes can't reach domain controllers in any other VPC, including those that are peered to the storage pool's VPC and that connect to the storage pool.
Firewalls: The on-premise connection fails if you don't allow NetApp Volumes to contact your domain controllers. For more information, Firewall rules for Active Directory access.
CMEK issues
The following sections contains known issues of customer-managed encryption key (CMEK) operations.
ListKmsConfigs returns Invalid value for enum type error
While a volume migrates from system-managed to customer-managed encryption, the
ListKmsConfigs command occasionally returns an
Invalid value for enum type error during migration. After the migration
finishes, the ListKmsConfigs command returns to working normally.
KmsConfig policy creation fails
Occasionally, KmsConfig policy creation fails and blocks you from creating
another policy. If this occurs, contact NetApp Volumes Support
by sending an email to google-netapp-volumes-support-external@google.com.
Metrics limitations
The /volume/throughput_limit reports the maximum throughput allocated for a
volume as a rounded integer value and not as a decimal number. As a result, it's
slightly inaccurate, especially for smaller volumes. For example, a
100 GiB Premium volume reports a throughput limit of 6 MiBps instead of the
correct 6.25 MiBps. This limitation doesn't significantly affect larger volumes.
Metrics unavailable for the Standard service level in Preview
In regions where the Standard service level is in Preview, monitoring metrics are unavailable.
Storage pool issues and limitations
The following sections provide details about known limitations of the storage pools feature.
Storage pool creation fails for every seventh storage pool
In the Google Cloud console, an error message appears and storage pool creation fails for every seventh storage pool.
To resolve this, retry the operation.
Storage pool resize limitation
In regions where the Standard service level is in Preview, there is a limit to how much you can decrease storage pool capacity. When you change the storage pool capacity, the allowed limit is provided.
Volume issues and limitations
The following sections provide details about known issues and limitations of the volumes feature.
Access from clients limited to the same region for Standard service level in Preview
If you use the Standard service level in a region where it is in Preview, client access is only allowed from within the same region. To learn more, see NetApp Volumes key features.
reverse-and-resume operations fail if performed in rapid succession
reverse-and-resume operations performed in rapid succession automatically
enter a Stopped state. When you resume the operation after you stop it,
replication fails.
To resolve this, after you reverse a replication twice, if the replication state appears as Stopped, wait five minutes before you attempt to resume the operation.
Volume replication issues and limitations
The following sections provide details about known issues and limitations of the volume replication feature.
Changes made to a source or destination volume apply to the replication partner
Volume attribute changes such as capacity to either source or destination volume also apply to the replication partner as long as the replication is in a mirrored or transferring state. Changes are replicated to all attributes except the following:
SnapReserveSnapshotDirectorySnapshotPolicyUnixPermissions
Resuming a stopped replication doesn't replicate all source volume settings
When you resume a stopped replication, the source volume doesn't overwrite all destination volume settings with source volume settings. Any changes to the destination volume are retained until a new modify action is applied to an active replication, which updates the settings on both sides.
Replications delete before stopping
When you use the NetApp Volumes API and Google Cloud CLI, replications can delete before they stop, which results in unintentional data loss. To avoid this, use the Google Cloud console to delete replications.
Google Cloud console displays storage pools without associated Active Directory policies
In the Google Cloud console, when you create a volume replication for a source volume, the list of storage pools to choose from to create the destination volume contains storage pools that don't have an Active Directory policy. Selecting a storage pool without an Active Directory policy leads to replication failure.
Backup limitations
The following section describes known limitations and issues of the backup feature
VPC Service Controls
Backups aren't supported for projects in a VPC Service Controls perimeter. Attempting to create a manual backup will fail. Creating a backup schedule will appear to succeed, but no backups will get created subsequently. Reach out to Cloud Customer Care to get a temporary workaround solution.
Customer-managed encryption keys
You can't use a customer-managed encryption key (CMEK) with the backups feature.