Failover cluster without pausing node
Hi all, We have 2 Exchange 2019 servers in a DAG (Primary and DR sites). Server 2022. We have one witness server which is in the same datacentre as the Exchange server at the primary site. Whenever the witness server is rebooted, failover clustering changes the DAG DNS object to point to the DR site. Both nodes stay up. First of all, can someone advise why this is the case? Both Exchange servers have communication at all times and the cluster is healthy. Secondly, is there a way to failback the cluster without pausing the DR node? I usually Pause and Drain Roles on the DR Exchange node, then Resume without failing the roles back. thanks jc
Cannot create separate storage pool on Windows 2019 Failover cluster.
Hello I am trying to get rid of S2D on our failover cluster and came across the inability to create separate storage pools (without using S2D) on Windows 2016/2019. Every time you set up a Failover Cluster, even without adding eligible disks to storage, it still sets up the Clustered Windows Storage subsystem and assigns all available disks to it. So, you have all the disks, but if you try to create a storage pool, it will fail. Tried to create all storage pools before forming the cluster - to no avail, the pools were created, but any attempt to create a virtual disk instantly fails. I tried to use Set-ClusterS2DDisk to stop the storage subsystem from using those disks - to no avail. Tried to unregister the Clustered Windows Storage subsystem - it's not possible. I have absolutely no idea what to do now. So, is there a way to set up a failover cluster without using S2D?
