某些网络附加存储 (NAS) 协议或协议变体需要访问外部目录服务。NetApp Volumes 仅支持 Active Directory 作为目录服务。Active Directory 政策可为服务提供加入 Windows 网域所需的所有必要信息。由于路由、防火墙设置或凭据不正确等原因，连接到 Active Directory 可能会失败。因此，在配置 Active Directory 政策时，NetApp Volumes 会为您提供连接测试。连接测试用于检查 Active Directory 政策是否已正确连接到 Active Directory 服务。
虽然您可以为每个区域创建多个 Active Directory 政策，但单个存储池只能附加一个 Active Directory 政策。池中的所有卷都使用相同的政策。不同的池可以使用不同的政策。
[[["易于理解","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-08-17。"],[],[],null,["# Storage pools overview\n\nThis page provides a detailed overview of the Google Cloud NetApp Volumes storage\npools feature.\n\nAbout storage pools\n-------------------\n\nStorage pools act as a container for volumes. All volumes in a storage pool\nshare the same location, service level, Virtual Private Cloud network,\n[Active Directory policy](/netapp/volumes/docs/configure-and-use/active-directory/about-ad),\nand [customer-managed encryption key (CMEK) policy](/netapp/volumes/docs/configure-and-use/cmek/cmek-overview). You can assign the capacity of the pool to volumes within the\npool. Billing is based on the location, service level, and capacity allocated to a\npool independent of consumption at the volume level.\n\nSupported locations\n-------------------\n\nAll volumes in a storage pool live in the same location as the pool. For more\ninformation on supported locations, see\n[NetApp Volumes supported locations](/netapp/volumes/docs/locations).\n\nService levels\n--------------\n\nThe service level is a property of the storage pool. Service levels have\ncapacity-dependent throughput limits. NetApp Volumes offers\nfour service levels: Flex, Standard, Premium, and Extreme. For more information,\nsee [NetApp Volumes service levels table](/netapp/volumes/docs/discover/service-levels).\n\nThe following table provides the throughput of allocated capacity for each\nservice level and what each service level is best used for:\n\nYou can reassign the Premium service level volume to an Extreme service level\nstorage pool and the other way around. This allows instant adjustments to\nchanging performance requirements.\n\nAvailability\n------------\n\nPools in different service levels have different availability. For more\ninformation, see [NetApp Volumes service level agreement](/netapp/volumes/sla).\nPools of Flex service level lets you choose between zonal and regional\navailability.\n\nA regional pool maintain two synchronous replicas of your data in two different\nzones. When creating a regional pool, you can choose the active zone and a\nreplica zone. All volumes of your pool are available from the active zone, while\nthe replica zone acts as a standby. In case the active zone fails or you are\ntriggering a manual zone switch, all volume access moves to the replica zone,\nwhich then becomes the new active zone. The previous active zone becomes the new\nreplica zone. This zone switch can cause a pause of file service activity. After\nthe zone switch is completed, the file services starts again.\n\nIf the regional Flex active zone and the workload VMs are in the same\nGoogle Cloud zone, it optimizes I/O latency and helps you achieve better\nperformance.\n\nNetwork\n-------\n\nA pool defines which Virtual Private Cloud (VPC) its volumes connect to. The\nvolumes are accessible only for clients that are on the same VPC\nor those connected to it with a VPN.\n\nActive Directory settings\n-------------------------\n\nSome network-attached storage (NAS) protocols or protocol variations require\naccess to an external directory service.\n[NetApp Volumes supports Active Directory](/netapp/volumes/docs/configure-and-use/active-directory/about-ad)\nas the only directory service. An [Active Directory policy](/netapp/volumes/docs/configure-and-use/active-directory/about-ad)\nprovides the service with all necessary information to join a Windows domain.\nSince connecting to Active Directory might fail for reasons such as incorrect\nrouting, firewall settings, or credentials, NetApp Volumes\nprovides you with a [connectivity test](/netapp/volumes/docs/configure-and-use/active-directory/test-ad-policy-connection)\nwhen you configure the Active Directory policy. The connectivity test checks\nwhether an Active Directory policy is correctly connected to the Active\nDirectory service.\n\nWhile you can create multiple Active Directory policies per region, a single\nstorage pool can only have one Active Directory policy attached to it. All\nvolumes in the pool use the same policy. Different pools can use different\npolicies.\n\nCustomer-managed encryption key settings\n----------------------------------------\n\nNetApp Volumes encrypts the data of all volumes at rest using\na Google-owned and Google-managed encryption key, however, you can choose to encrypt the volumes using a\ncustomer-managed encryption key (CMEK). You can attach a CMEK policy during\nstorage pool creation; all of the volumes created in that pool use the policy.\n\nCMEK supports the Flex, Standard, Premium, and Extreme service levels storage\npools.\n\nCapacity\n--------\n\nNetApp Volumes lets you add or remove capacity to your\nvolume as needed to adjust for any application changes. Capacity is allocated\nto storage pools and volumes, and can be modified. The following table shows how\nyou can allocate capacities to NetApp Volumes storage pools and\nvolumes for each service level.\n\nAuto-tiering\n------------\n\n| **Note:** The auto-tiering feature for the Flex service level is in Preview, and available only for custom-performance Flex zonal pools.\n\nAuto-tiering needs to be allowed on a storage pool before auto-tiering can be\nenabled for any of the volumes in the pool. Once you allow auto-tiering for the\npool, the selection is permanent. Allowing auto-tiering on the pool doesn't\nchange existing volumes, nor does it affect how new volumes are created by\ndefault. Instead, you have to explicitly enable auto-tiering for individual\nvolumes by updating existing volumes or when creating a new volume. For more\ninformation, see [Manage auto-tiering](/netapp/volumes/docs/configure-and-use/volumes/manage-auto-tiering).\n\nVolumes\n-------\n\nYou can assign volumes to storage pools, and also move a volume within a pool\nto a different pool with the same settings\n(location, network, Active Directory policy, and CMEK policy) as long as the\nservice level allows and the target pool has enough spare capacity.\n\nBefore you can start to create volumes, you need to provision a storage pool to\nhost the volumes.\n\nWhat's next\n-----------\n\n[Create a storage pool](/netapp/volumes/docs/configure-and-use/storage-pools/create-storage-pool)."]]
