SIOS SANless clusters

SIOS SANless clusters High-availability Machine Learning monitoring

  • Home
  • Products
    • SIOS DataKeeper for Windows
    • SIOS Protection Suite for Linux
  • News and Events
  • Clustering Simplified
  • Success Stories
  • Contact Us
  • English
  • 中文 (中国)
  • 中文 (台灣)
  • 한국어
  • Bahasa Indonesia
  • ไทย

How To Configure File Share Witness On A USB Thumb Drive?

October 29, 2018 by Jason Aw Leave a Comment

How-To-Configure-File-Share-Witness-On-A-USB-Thumb-Drive

How-To-Configure-File-Share-Witness-On-A-USB-Thumb-Drive

Cluster Quorum File Share Witness On A USB Stick

There will be a few new features in regards to the File Share Witness for the Failover Cluster Quorum in Windows Server 2019. It’s a feature my customers had been asking for many years – file share witness on a USB thumb drive!

Many wanted to deploy a simple 2-node cluster in each store location, branch office, etc. They didn’t want the added expense of a SAN to leverage a Disk Witness and did not have the connectivity to rely on a Cloud Witness in Azure. As a result, they forgo clustering. Or they used an alternative clustering solution like SIOS Protection Suite.

Now they have a viable alternative –  File Share Witness On A USB Thumb Drive, coming in Windows Server 2019. By leveraging a supported router, a USB disk inserted into the router can be configured with a file share that can be used as the witness. This eliminates the need for a 3rd server or internet connectivity.

file share witness on a USB thumb drive
https://blogs.msdn.microsoft.com/clustering/2018/04/16/new-file-share-witness-feature-in-windows-server-2019/

There are a few scenarios I can imagine. From HCI for Hyper-V, to a simple file server cluster using DataKeeper. Regardless of the scenario, keep in mind unless you plan on building a workgroup cluster, you probably will want to run a VM on each server to act as a redundant Domain Controllers. Or you have a reliable WAN connection back to a Domain Controller hosted in your main datacenter.

For more tips and tricks such as configuring file share witness on a USB thumb drive, read more here.
Reproduced with permission from ClusteringForMereMortals.com

Filed Under: Clustering Simplified Tagged With: File Share Witness, file share witness on a usb thumb drive, Windows Server 2019

Can I Put My File Share Witness On A DFS Share?

October 22, 2018 by Jason Aw Leave a Comment

Can I Put My File Share Witness On A DFS Share?

Can I Put My File Share Witness On A DFS Share?

I get asked this question all the time – Just where can put my File Share Witness On A DFS Share. People are concerned about losing their file share witness. Hence like many of their other shares, they want to leverage DFS for some additional availability. This is a very bad idea and is not supported.

Microsoft recently publish a great blog article that describes exactly why File Share Witness On A DFS Share is not supported.

https://blogs.msdn.microsoft.com/clustering/2018/04/13/failover-cluster-file-share-witness-and-dfs/

Much of this article would also apply to people who ask if they can use a DataKeeper replicated volume resource as a Disk Share. It makes sense. You can use a DataKeeper volume resource in place of a Physical Disk resource for any other workload, so why not a Disk Witness?

This issue is the same as the DFS issue. In the event of a loss of communication between the two servers, there is nothing to guarantee that the volume wouldn’t come online on both servers. It would result in a potential split-brain condition. The Physical Disk resource overcomes this issue by using SCSI reservations. This would ensure the disk is only accessible by one cluster node at a time.

The good news is that Microsoft already blocks you from trying to use a replicated DataKeeper Volume resource. And coming in Windows Server 2019, it looks like they will also block you from using a DFS share as a File Share Witness.

Can I Put My File Share Witness On A DFS Share?
Taken from the Failover Clustering and Network Load Balancing Team Blog Post “Failover Cluster File Share Witness and DFS

Have questions like this about putting File Share Witness On A DFS Share? Read through our blog or contact us!
Reproduced with permission from ClusteringForMereMortals.com

Filed Under: Clustering Simplified, Datakeeper Tagged With: DFS Share, File Share Witness, file share witness on a dfs share

Windows Server Failover Cluster Quorum Types In Windows Server 2012 R2

February 21, 2018 by Jason Aw Leave a Comment

Cluster Quorum types? What Does It Do?

Before we get started with all the great new cluster quorum types in Windows Server 2012 R2, we should take a moment and understand what it does and how we got to where we are today. Rob Hindman describes quorum best in his blog post…

“The quorum configuration in a failover cluster determines the number of failures that the cluster can sustain while still remaining online.”

The Beginning: Disk Only

Prior to Windows Server 2003, there was only one quorum type, Disk Only. Now there are different cluster quorum types. Disk Only is still available today, but is not recommended as the quorum disk is a single point of failure. In Windows Server 2003 Microsoft introduce the Majority Node Set (MNS) quorum. This was an improvement as it eliminated the disk only quorum as a single point of failure in the cluster. However, it did have its limitations. As implied in its name, Majority Node Set must have a majority of nodes to form a quorum and stay online. So, this quorum model is not ideal for a two node cluster where the failure of one node would only leave one node remaining. One out of two is not a majority, so the remaining node would go offline.

The Introduction Of File Share Witness

Microsoft introduced a hotfix that allowed for the creation of a File Share Witness (FSW) on Windows Server 2003 SP1 and 2003 R2 clusters. Essentially the FSW is a simple file share on another server that is given a vote in a MNS cluster. The driving force behind this innovation was Exchange Server 2007 Continuous Cluster Replication (CCR), which allowed for clustering without shared storage. Of course, without shared storage a Disk Only Quorum was not an option. Effective MNS clusters would require three or more cluster nodes. Hence, the introduction of the FSW to support two node Exchange CCR clusters.

The New Disk Witness Keeps A Copy Of Cluster Database

Windows Server 2008 saw the introduction of a new witness type, Disk Witness. Unlike the old Disk Only quorum type, the Disk Witness allows the users to configure a small partition on a shared disk that acts as a vote in the cluster, similar to that of the FSW. However, the Disk Witness is preferable to the FSW. This is because it keeps a copy of the cluster database and eliminates the possibility of “partition in time”. If you’d like to read more about partition in time, I suggest you read the File Share Witness vs. Disk Witness for local clusters.

Improvements

Windows Server 2012 continued to improve upon quorum options. It is my belief that many of these new features were driven by two forces: Hyper-V and SQL Server AlwaysOn Availability Groups. With Hyper-V, we began to see clusters that contained many more nodes than we have typically seen in the past. In a majority node set, as soon as you lose a majority of your votes, the remaining nodes go offline. For example, if you have a Hyper-V cluster with seven nodes, and you were to lose four of those nodes, the remaining nodes would go offline, even though there are three nodes remaining. This might not be exactly what you want to happen. So in Windows Server 2012, Microsoft introduced Dynamic Quorum.

Dynamic Quorum

Dynamic Quorum does what its name implies. It adjusts the quorum dynamically. So in the scenario described about, assuming I didn’t lose all four servers at the same time, as servers in the cluster went offline, the number of votes in the quorum would adjust dynamically. When node one went offline, I would then in theory have a six node cluster. When node two went offline, I would then have a five node cluster, and so on. In reality, if I continued to lose cluster nodes one by one, I could go all the way down to a two node cluster and still remain online. And, if I had configured a witness (Disk or File Share) I could actually go all the way down to a single node and still remain online.

Read more about cluster quorum types at….

http://blogs.msdn.com/b/microsoft_press/archive/2014/04/28/from-the-mvps-understanding-the-windows-server-failover-cluster-quorum-in-windows-server-2012-r2.aspx

Reproduced with permission from https://clusteringformeremortals.com/2014/04/29/understanding-the-windows-server-failover-cluster-quorum-in-windows-server-2012-r2/

Filed Under: Clustering Simplified Tagged With: cluster, cluster quorum types, Disk Only, Disk Witness, File Share Witness, Quorum, Windows Server, Windows Server 2012 R2

Recent Posts

  • Video: The SIOS Advantage
  • Demo Of SIOS DataKeeper For A Three-Node Cluster In AWS
  • 2023 Predictions: Data Democratization To Drive Demand For High Availability
  • Understanding the Complexity of High Availability for Business-Critical Applications
  • Epicure Protects Business Critical SQL Server with Amazon EC2 and SIOS SANLess Clustering Software

Most Popular Posts

Maximise replication performance for Linux Clustering with Fusion-io
Failover Clustering with VMware High Availability
create A 2-Node MySQL Cluster Without Shared Storage
create A 2-Node MySQL Cluster Without Shared Storage
SAP for High Availability Solutions For Linux
Bandwidth To Support Real-Time Replication
The Availability Equation – High Availability Solutions.jpg
Choosing Platforms To Replicate Data - Host-Based Or Storage-Based?
Guide To Connect To An iSCSI Target Using Open-iSCSI Initiator Software
Best Practices to Eliminate SPoF In Cluster Architecture
Step-By-Step How To Configure A Linux Failover Cluster In Microsoft Azure IaaS Without Shared Storage azure sanless
Take Action Before SQL Server 20082008 R2 Support Expires
How To Cluster MaxDB On Windows In The Cloud

Join Our Mailing List

Copyright © 2023 · Enterprise Pro Theme on Genesis Framework · WordPress · Log in