您可以透過 Google Cloud 主控台管理延展的私有雲。在延伸私有雲中，所有延伸叢集在每個區域中都會占用一半的容量，舉例來說，延伸私有雲中一個八節點的延伸叢集，必須在每個區域中占用四個節點。只有來自每個區域的節點數量相同，才能在經過延伸的叢集中新增及移除節點。舉例來說，您可以在經過延伸的叢集中，為每個區域新增兩個節點，或從每個區域移除三個節點。
延伸私有雲可以有多個延伸叢集，但每個叢集都必須有兩個資料節點的 Google Cloud 區域，以及一個見證節點的區域。
在延展的私有雲中加密 vSAN 資料
根據預設，在延伸私有雲的所有延伸叢集中，都會啟用 vSAN 靜態資料加密功能。根據預設，vSAN 加密會使用 Google 金鑰供應器。這個金鑰供應器使用 Cloud Key Management Service，並在兩個區域中以高可用性設定部署。您也可以使用任何外部第三方 Cloud KMS 伺服器 (以 HA 組態部署在兩個區域)，並自行管理。
延展私有雲中的儲存空間政策
經過延伸的私有雲的管理 VM 會在第一個經過延伸的叢集 (例如「叢集 0」) 上執行。管理 VM 會使用親和性規則附加至經過延伸叢集的主要網站，並設定下列儲存空間政策：
網站災難容錯度=1 (防範一個網站故障)
FTT=1 (適用於六節點的擴展叢集 (「叢集 0」))
FTT=2 (如果節點的延展值大於或等於 10 (「叢集 0」))
工作負載 VM 在延伸叢集中的預設儲存空間政策也遵循先前的政策。
您可以為工作負載 VM 建立新的儲存空間政策，而延伸私有雲中的每個延伸叢集都可以使用不同的儲存空間政策。
[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["難以理解","hardToUnderstand","thumb-down"],["資訊或程式碼範例有誤","incorrectInformationOrSampleCode","thumb-down"],["缺少我需要的資訊/範例","missingTheInformationSamplesINeed","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間：2025-09-04 (世界標準時間)。"],[],[],null,["# VMware Engine stretched private clouds\n======================================\n\nA Google Cloud VMware Engine stretched private cloud is a private cloud that is\nstretched across two data zones and a witness zone, all within the same Google Cloud region. Stretched private clouds use vSphere and vSAN stretched\nclusters to provide compute and storage high availability against zone-level\nfailures. All clusters of a stretched private cloud are considered VMware Engine stretched clusters, including the primary cluster.\n| **Note:** Once a stretched private cloud is created, it cannot be converted back to a standard private cloud. Additionally, you cannot convert an existing private cloud to a stretched private cloud.\n\nStretched private cloud operation\n---------------------------------\n\nAll of the clusters of a stretched private cloud are stretched across the same\ntwo data zones and share the same witness zone. Each stretched cluster has its\nown set of data nodes in each data zone, and each stretched cluster has a\nwitness node in the witness zone. Stretched qualifies as any two zones in a\ngiven Google Cloud region that are more than 10 Km geodesic distance apart\nbut have less than 5 msec RTT latency between them.\n\nThe witness node is managed by VMware Engine and runs on a\nCompute Engine instance running ESXi in nested mode. You don't need to specify\na witness zone and don't have to manage the lifecycle of the witness node.\n\nEach of the three zones used by a stretched cluster are independent failure\ndomains. The main benefit of this setup is that a cluster stretched across the\nthree zones can survive a complete failure of any single zone.\n\nStretched private cloud node configuration\n------------------------------------------\n\nStretched clusters have an equal number of nodes in data zones. For example,\nthree nodes in each data site - denoted as 3+3, or four nodes in each data site,\ndenoted as 4+4. Configurations such as 4+3, therefore, are not allowed in Google Cloud VMware Engine stretched private clouds. A stretched cluster in Google Cloud VMware Engine must have a minimum of six data nodes (3+3) and a maximum of 32 (16+16) data\nnodes.\n\nStretched private cloud environment\n-----------------------------------\n\nYou manage your stretched private clouds through the Google Cloud console. All\nstretched clusters in a stretched private cloud have half of their capacity in\neach zone - for example, an eight-node stretched cluster in a stretched private\ncloud must have four nodes in each zone. Only an identical number of nodes\nfrom each zone can be added and removed from the stretched clusters. For\nexample, you can add two nodes to each zone or remove three nodes from each zone\nin a stretched cluster.\n\nA stretched private cloud can have multiple stretched clusters, but each must\nhave exactly two Google Cloud zones for data nodes and one zone for the witness\nnode.\n\nvSAN data encryption in stretched private clouds\n------------------------------------------------\n\nvSAN data encryption at rest is enabled by default in all stretched clusters of\na stretched private cloud. By default, a Google key provider is used for vSAN\nencryption. This key provider uses Cloud Key Management Service and is deployed in a highly\navailable configuration across two zones. You can also use any external 3P\nCloud KMS server (deployed as an HA pair across the two zones) and\nmanage it yourself.\n\nStorage policies in stretched private clouds\n--------------------------------------------\n\nThe management VMs of a stretched private cloud run on the first stretched\ncluster (for example, 'cluster 0'). The management VMs are affixed to the\nprimary site of the stretched cluster using affinity rules and are configured\nwith the following storage policy:\n\n- Site Disaster tolerance=1 (protect against one site failure)\n- FTT=1 (for a six-node stretched ('cluster 0'))\n- FTT=2 (for a node stretched greater than or equal to 10 ('cluster 0'))\n\nThe default storage policy in a stretched cluster for workload VMs also follows\nthe previous policy.\n\nYou can create new storage policies for workload VMs, and each stretched cluster\nin a stretched private cloud can use different storage policies.\n\nWhat's next\n-----------\n\n- Learn about [VLANs and subnets](/vmware-engine/docs/concepts-vlans-subnets)."]]
