One thing I would add is that after you have converted this to a Standard cluster topology, to 100% confirm there are no objects that still have a storage policy that would only be able to be compliant in a Stretched-cluster (e.g. affinity to one site or any with SFTT=1/2). Such objects still being present with these policies would prevent tasks such as Maintenance Mode with Ensure Accessibility option or data repair tasks.
As the SPBM UI in the vSphere client only shows policies for objects tied to current vSphere inventory (e.g. registered VMs) it is possible to have objects with such policies but won't show this on the policy in the UI - to check for sure, use the following and then inspect the data it generates:
# esxcli vsan debug object list --all > /tmp/objout
Original Message:
Sent: Nov 15, 2024 12:54 PM
From: UK IT
Subject: Remove Stretched Cluster
We have a vSAN Streched Cluster across 2 Data Centers with a witness server in another. There are 3 hosts each in the Primary and Secondary Fault Domains. Dues to changes to our network we will be removing the Stretched Cluster and just have a standard cluster in one Data Center. I have found the following document on how to do this, but I was wondering if anyone had already done this and have any tips or words of causion?
I assume that I should move all VMs to the Primary Fault Domain, then remove the Stretched Cluster and Witness Server. We would then like to move one of the hosts that is in the Secondary Fault Domain over to the Primary Data Center.
Convert a Stretched Cluster to a Standard vSAN Cluster
| Vmware | remove preview |
 | | Convert a Stretched Cluster to a Standard vSAN Cluster | | You can decommission a stretched cluster and convert it to a standard vSAN cluster. | | View this on Vmware > |
|
|
Many thanks in advance.