Working on a 2022 Failover Cluster File Share testing

Question

Good afternoon, I'm working on a Failover File share cluster. I'm new to the failover cluster configuration so most of the configuration I've done is based on research. I've made it into a stretched cluster with 2 different sites "dc1 and then dc2". I also have replication via storage replica "files1 to files1". I'm working on testing the failover. I have it configured with all 4 servers selected as owners. Then I have the failover set to allow failback. When I try to pause the DC1 nodes to make DC2 primary it fails giving me an 0x138D error telling me it can't move ownership to DC2. What could be causing the error? Could it be the replication?

4 servers:

dc1-files1

dc1-files2

dc2-files1

dc2-files2

Answer 1

Hey,

As mentioned, check if all of your nodes are in possible owners list. Might help: https://www.sqlservercentral.com/forums/topic/after-sql-upgrade-from-sql-2014-to-sql-2016-failover-on-2-node-windows-cluster-fails

In addition, I would recommend you to check if your replica working properly.

As another option, you can use StarWind VSAN to configure replication between your sites.
https://www.starwindsoftware.com/starwind-virtual-san

Cheers,

Alex Bykovskyi

StarWind Software

Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Answer 2

Hi Lukas,

Hope you're doing well.

Potential Causes and Solutions:

1. If the replication via Storage Replica is not configured correctly or there are issues with the replication health, it could prevent the failover from executing as expected. Ensure that the replication is in a healthy state and that there are no underlying issues with the network or storage that could be impacting the replication process.
2. The error might be related to the cluster configuration. Ensure that all nodes have the correct quorum settings and that the cluster is configured to handle the stretched cluster scenario properly.
3. The error could be related to resource ownership within the cluster. Verify that the resources are configured to move correctly between the nodes and that there are no restrictions or dependencies preventing the move.
4. Go through the Failover Cluster configuration and Storage Replica settings to ensure everything is set up correctly. Pay special attention to the quorum configuration and the replication health.
5. Review the cluster logs and event viewer for any additional error messages or warnings that could provide more context to the issue.

Best Regards,

Ian Xue

---

If the Answer is helpful, please click "Accept Answer" and upvote it.

Answer 3

error telling me it can't move ownership to DC2

Then you may forget to check DC2 as "Possible owner" for the cluster resource.