Windows 10: Failover Cluster Storage Replication

We have a Windows failover cluster containing a shared disk assigned to a Role and want to set up replication from it.We tried removing the disk from the cluster to use DFS Replication, however we lose access to the network shares of the disk even once they are recreated with the same permissions and pathways. We regained access once we recreated the role with the shared disk.Going off of that, we need to replicate within the cluster. When configuring storage replication, our second shared disk that is in available storage is ineligible due to the flag "Not in a different site."I'm unable to f

:)

 

Failover Cluster

Dears

We upgraded our environment from Windows Server 2012 R2 into Windows 2019

Everything seems to work normally except for Windows Failover Cluster Service

The service is not able to run at all with the event id1090

We removed the failover cluster feature and re-add it again; however, the problem persists

Please advise

Thank you

 

Windows Failover Clustering - SQL Server - Latency on Connection

Hello,

We've just set up a two-node Windows Failover cluster (WFSC) on Windows Server 2019 across AWS regions (Oregon and Ohio) using Sios DataKeeper to replicate the files. We installed two SQL 2017 instances on the cluster. We adjusted the heartbeat settings to be more forgiving of a multi-subnet config with 2 seconds instead of 1 on the cross-subnet settings. (We run 4 other clusters across AWS Availability Zones (AZ) with no problems, this is our first cross-region cluster.)

There were no issues during setup. The two roles can easily move between the two hosts with no hesitation or errors.

The problem we're having is that sporadically, connections to the SQL instances can take up to 5-10 seconds to connect. In a tool like SQL Server Management Studio, it will always eventually connect, but some things time out. Annoyingly, if you disconnect and reconnect, it will sometimes instantly reconnect. Other times, not.

We don't see this behavior on any of our cross-AZ clusters, only this new cross-region cluster. There's no errors or warning in the Windows Logs, or any of the Failover Clustering logs, including verbose.

Anybody have any ideas or suggestions?

Thanks.

 

Windows 10 RSAT - Failover Cluster Manager

I installed the remote server admin tools yesterday to my Win10 enterprise which made me very happy at first. DNS, DHCP, ADUC all worked great. Then I opened failover cluster manager. Problems began.

We have dozens of MS clusters running 2003 and up, mostly 2008R2 or 2012R2. When I try and manage them I get

Connection Not Supported

Cluster XXXXXXX not supported

The cluster to which you are attempting to connect is not a version of the cluster supported by this version of Failover Cluster Manager

This is happening with all the clusters I need to manage. Is this a bug or "working as designed"?