S2D Teardown

Anonymous
2024-01-04T20:12:54+00:00

I have a 3-node Hyper-V S2D cluster that is now leveraging a SAN to host the local storage. I need to delete and teardown the S2D environment correctly WITHOUT affecting the cluster itself. I will be repurposing the attached drive shelves and drives that are attached to the Hyper-V Hosts. All the VMs and their storage has already been Live-Migrated to the SAN volumes. I am ready to delete the S2D volumes and the ClusterPerformanceHistory disk, but I want to be sure the removal of S2D is done in the proper order (if required). Surely it can't be as easy as deleted the S2D volumes and calling it a day.

I can not find any useful links our there about tearing down a S2D environment WITHOUT affecting the cluster itself. Can someone point me in the right direction or provide me some useful links to review?

Your time is greatly appreciated...

Scott

Windows Server High availability Clustering and high availability

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.

0 comments No comments
{count} vote

1 answer

Sort by: Most helpful
  1. Anonymous
    2024-01-05T02:40:26+00:00

    Hi Scott,

    Hope you're doing well.

    To tear down S2D cluster, please refer to the following steps:

    1. Before these operations, you must backup all data to prevent data loss.
    2. And then we need to migrate all VMs to other path.
    3. Stop cluster service.
    4. Disable S2D: please open powershell as an administrator and input the following command:

    Disable-ClusterStorageSpacesDirect

    1. Delete StoragePool which exist in the cluster.
    2. Next, follow the normal steps to destroy the cluster.

    (1)In Failover Cluster Manager, right-click the created Cluster, select "More Actions", and then click "Destory Cluster". However, the window shows that clusters containing cluster roles cannot be destroyed, so you should delete all cluster roles in the cluster first.

    (2) Delete all roles from the group. In the failover group manager, click "Roles," select all high-availability VMS in the right-hand window and right-click and select "Remove," then click OK. Therefore, all high-availability VMS are removed from the cluster role.

    (3) After these roles are deleted, the Cluster can be destroyed. Right-click the created cluster, select "More actions", click "Destory Cluster", and select "Yes" to complete the cluster deletion operation.

    (4) Finally, delete the cluster machine name from the Active Directory user and machine.

    If you have any questions, please let me know.

    Best Regards

    0 comments No comments