[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2025-09-04。"],[],[],null,["# Using NFS volume as vSphere datastore hosted by Cloud Volumes Service\n=====================================================================\n\nYou can use [NetApp Cloud Volumes Service for Google Cloud](/solutions/partners/netapp-cloud-volumes) (CVS) as an external datastore\nfor ESXi hosts in Google Cloud VMware Engine. To do so, you must create CVS-Performance\nvolumes in select regions and then mount them as external datastores to their existing ESXi hosts in Google Cloud VMware Engine.\n\nThis solution supports CVS-Performance only and has the following functionality\nfor datastores:\n\n- NFSv3 protocol\n- CVS-Performance with crash-resistant snapshots and cross-region replication\n\nBefore you begin\n----------------\n\nThe steps in this document assume that you have done the following:\n\n- Earmarked a `/26` CIDR for the Google Cloud VMware Engine service network to be used for external NFS storage.\n\nConfiguring Service Subnets\n---------------------------\n\n| **Note:** NSX-T gateway and distributed firewall rules don't apply to any service subnet.\n\nService subnets don't have a CIDR allocation on initial creation. You must\nspecify a non-overlapping CIDR range and prefix. The first usable address\nbecomes the gateway address. To allocate a CIDR range and prefix, edit one of\nthe service subnets. Service subnets can be updated if CIDR requirements change.\nModification of an existing service subnet CIDR can cause network availability\ndisruption for VMs attached to that service subnet.\n\nPeering CVS Service with Google Cloud VMware Engine\n---------------------------------------------------\n\n| **Note:** You don't need to repeat this process if you have already completed network peering to use CVS volumes as in-guest file shares.\n\nYou must peer your CVS tenant project with your Google Cloud VMware Engine tenant project\nto enable ESXi hosts to communicate with the CVS file servers. To achieve this,\nfollow the instructions provided under the **Get VPC network details** and\n**Create a peering connection** in [Using NFS shares hosted by CVS in workload VM Guests](/vmware-engine/docs/vmware-ecosystem/howto-cloud-volumes-service).\n\nCreating CVS volumes\n--------------------\n\nYou can create and manage CVS volumes using the CVS UI, VMware Engine API, and\ngcloud CLI by following the steps at [Workflow for managing cloud volumes](/solutions/partners/netapp-cloud-volumes/workflow).\n| **Note:** When using a CVS volume as a VMware Engine data store, don't select **Secondary** under the **Volume Replication** field. Selecting **Secondary** marks the volume read-only and prevents ESXi hosts from mounting the volume. For more details on the volume replication field, refer to [Use volume replication to protect your data](/architecture/partners/netapp-cloud-volumes/volume-replication).\n\nMarking CVS volumes as non-deletable\n------------------------------------\n\nBefore you can mount CVS volume as an external NFS datastore to ESXi hosts in\nGoogle Cloud VMware Engine, you must block users from accidentally deleting the volumes to\navoid disruption. Follow the instructions found under [Creating an NFS volume](/architecture/partners/netapp-cloud-volumes/creating-nfs-volumes#creating_an_nfs_volume)\nto select this option in the CVS UI.\n\nAfter creating the initial volume, you can perform CVS volume management (for\nexample, grow or monitor), using the CVS Google Cloud console, VMware Engine API, or\ngcloud CLI. Refer to [Workflow for managing cloud volumes](/solutions/partners/netapp-cloud-volumes/workflow)\nfor more information on completing management tasks.\n\nAfter the datastores are mounted and available, users can use the vCenter UI to\nprovision VMs against the external datastores, view metrics and view logs\nrelated to I/O operations performed against external datastores.\n\nFor more information on CVS, see [NetApp Cloud Volumes Service for Google Cloud documentation](/solutions/partners/netapp-cloud-volumes).\nYou can also find general background information at [VMware vSphere for ONTAP](https://docs.netapp.com/us-en/netapp-solutions/virtualization/vsphere_ontap_ontap_for_vsphere.html).\n\nContact your account team if you need help completing onboarding."]]
