How to Manage Failover Clusters?

 

Configure roles/features on nodes for high availability

1. Server manager → Add roles and features.
2. In the select installation type page, select Role based installation.
3. Select destination server for this role.
4. In the list of roles displayed, select Hyper-v .The 'Add features that are required for Hyper-V window' is displayed. This window shows the dependencies that will be installed. Click Add features.

   

5. The select features window is displayed next. Select Failover Clustering. The features that are required for Failover Clustering will pop up in the next window. This window shows the dependencies that will be installed with this feature. Click Add features.

   

6. Next, the Hyper-V window is displayed.

   

7. The Create Virtual Switches window is displayed. In Network adapters, select the network that you want your virtual machine to use for the cluster. If you have multiple NIC’s listed here, choose the appropriate ones.

   

8. The Virtual Machine Migration window is displayed.Select "Allow this server to send" and "Receive live migrations of virtual machines". This allows the VM to transfer between your nodes where required.

   

9. The Default Stores window is displayed. Do not change the default stores.

   

10. Confirm your installation selections and click Install.

Connecting to iSCI network drives

1. Start the iSCI initiator and connect to your two SAN drives:
   • Click Start → Windows Administrative Tools → iSCI Initiator.
   • Ensure the drives are set to allow simultaneous connections. This is configured on your SAN. Make sure you have granted access to your two cluster servers.
2. Connect to the SAN drives:
   • Open the iSCI initiator → Targets tab→ Enter the IP address for the SAN.

     

   • Click Quick Connect.Your drives are displayed.
   • Highlight a drive, then click connect to connect to each drive.
   • When a drive is connected, click Done.
   • Click the Volumes and Devices tab.

     

   • Click Auto-configure → OK. When you are connected on the first machine, click Start → WIndows Administrative tools → Computer Management → Disk Management.

     

3. Bring the disks online
   • Right-click the disk number.
   • Select Online.
4. Repeat the above step for the second drive.
5. Initialize the disks:
   • Right-click the disk number next to one of the new drives.
   • Select Initialize disk.
   • In the box that appears, ensure that both your new disks have a check mark next to them.
   • Set as MBR.
   • Click OK.
6. Configure the new drive:
   • Right-click the first drive.

     

   • Select Create New Simple Volume.
   • Leave the defaults in place.
   • Choose a drive letter to assign.
   • Label your drives:
     • 5GB drive—label the drive as Quorum
     • 150GB (larger drive)—label it as ClusterStorage
7. Repeat the above steps for the second drive.

Create the failover cluster

From the OS of any of the nodes created in the above steps, do the following:

1. Click Start → Windows Administrative tools → Failover Cluster Manager to launch the Failover Cluster Manager. Click "create cluster". Click Next on the 'Before you begin' window.

   

2. In the next window, enter the server names that you want to add to the cluster. Alternatively, you can locate them via Browse. Click Add → next.

   

3. Validation warning window is displayed. Select Yes to "allow verification of the cluster services".

   

4. When you click next, the Validate a Configuration wizard is displayed. Continue by clicking Next.
5. In the testing options window, select "Run all tests" (recommended).The next window will let you confirm the list of tests that will be run by Windows.

   

6. The Validating window is displayed while all of the clustering tests are being run. This process may take several minutes depending on your network infrastructure and the number of nodes you have chosen to add to your cluster. When the tests are completed, check the report, and fix configuration errors, if any. The cluster setup will fail if any errors exist.

   

7. The 'Access Point for Administering the Cluster' window in the Create Cluster wizard is displayed. In Cluster Name, enter a name for your cluster. In the available network provide an IP address for the cluster.

   

8. After clicking next, the confirmation window is displayed. This window lists the settings to be applied to your new cluster.
   • Select the "Add all eligible storage to the cluster" check box. The system will now try to assign any storage it can find. The system attempts to create the new cluster in your domain.
   • This may take a while as there are several checks and tests are conducted while the system is configured.
   • When the process is complete, the Summary window is displayed stating that the cluster wizard completed successfully.

     

9. Check to confirm that the cluster is configured correctly
   • In the Failover Cluster Manager, navigate to Nodes.

     

   • Check that all nodes in the cluster are online. If they are not, go to the server that is offline and bring the system online to join the cluster.
10. Navigate to Storage → Disks.
    • a. The system detects the SCSI drives and displays them here. If you were setting this up with only two nodes, then the 5GB Quorum cluster would have been assigned as Disk Witness in Quorum.The configured storage space is assigned to Available Storage.

      

11. Configure this storage to be part of the cluster.
    • Right-click the disk assigned to available storage; then select "Add to Cluster Shared Volumes". The cluster is now assigned to Cluster Shared Volume.

      

12. Check the Cluster Events folder for any issues with the cluster. If there are no issues, you can configure your virtual machine in the cluster environment.

Force a Windows Server Failover Clustering (WSFC) Cluster to Start Without a Quorum

  This topic describes how to force a Windows Server Failover Clustering (WSFC) cluster node to start without a quorum. This may be required in disaster recovery and multi-subnet scenarios to recover data and fully re-establish high-availability for Always On availability groups and SQL Server Failover Cluster Instances.

• Before you start: Recommendations, Security
  
• To force a cluster to start without a quorum using: Using Failover Cluster Manager, Using Powershell, Using Net.exe
  
• Follow up: Follow Up: After Forcing Cluster to Start without a Quorum
  

Before You Start

Recommendations

Except where explicitly directed, the procedures in this topic should work if you execute them from any node in the WSFC cluster. However, you may obtain better results, and avoid networking issues, by executing these steps from the node that you intend to force to start without a quorum.

Security

The user must be a domain account that is member of the local Administrators group on each node of the WSFC cluster.

Using Failover Cluster Manager

To force a cluster to start without a quorum

1. Open a Failover Cluster Manager and connect to the desired cluster node to force online.
   
2. In the Actions pane, click Force Cluster Start, and then click Yes - Force my cluster to start.
   
3. In the left pane, in the Failover Cluster Manager tree, click the cluster name.
   
4. In the summary pane, confirm that the current Quorum Configuration value is: Warning: Cluster is running in ForceQuorum state.
   

Using Powershell

To force a cluster to start without a quorum

1. Start an elevated Windows PowerShell via Run as Administrator.
   
2. Import the FailoverClusters module to enable cluster commandlets.
   
3. Use Stop-ClusterNode to make sure that the cluster service is stopped.
   
4. Use Start-ClusterNode with -FixQuorum to force the cluster service to start.
   
5. Use Get-ClusterNode with -Propery NodeWieght = 1 to set the value the guarantees that the node is a voting member of the quorum.
   
6. Output the cluster node properties in a readable format.
   

Example (Powershell)

The following example forces the Always OnSrv02 node cluster service to start without a quorum, sets the NodeWeight = 1, and then enumerates cluster node status from the newly forced node.

PowerShell

Import-Module FailoverClusters  

$node = "Always OnSrv02"  
Stop-ClusterNode -Name $node  
Start-ClusterNode -Name $node -FixQuorum  

(Get-ClusterNode $node).NodeWeight = 1  

$nodes = Get-ClusterNode -Cluster $node  
$nodes | Format-Table -property NodeName, State, NodeWeight  

Using Net.exe

To force a cluster to start without a quorum

1. Use Remote Desktop to connect to the desired cluster node to force online.
   
2. Start an elevated Command Prompt via Run as Administrator.
   
3. Use net.exe to make sure that the local cluster service is stopped.
   
4. Use net.exe with /forcequorum to force the local cluster service to start.
   

Example (Net.exe)

The following example forces a node cluster service to start without a quorum, sets the NodeWeight = 1, and then enumerates cluster node status from the newly forced node.

ms-dos

net.exe stop clussvc  
net.exe start clussvc /forcequorum  

Follow Up: After Forcing Cluster to Start without a Quorum

• You must re-evaluate and reconfigure NodeWeight values to correctly construct a new quorum before bringing other nodes back online. Otherwise, the cluster may go back offline again.
  For more information, see WSFC Quorum Modes and Voting Configuration (SQL Server).
  
• The procedures in this topic are only one step in bringing the WSFC cluster back online if an un-planned quorum failure were to occur. You may also want to take additional steps to prevent other WSFC cluster nodes from interfering with the new quorum configuration.
  
• Other SQL Server features such as Always On availability groups, database mirroring, and log shipping may also require subsequent actions to recover data and to fully re-establish high-availability.
  For more information:
  Perform a Forced Manual Failover of an Availability Group (SQL Server)
  Force Service in a Database Mirroring Session (Transact-SQL)
  
  Fail Over to a Log Shipping Secondary (SQL Server)