How to Manage SQL Server Failover Cluster using Command Line

The SQL Server failover cluster management tools are a set of utilities that help you manage and monitor your SQL Server failover clusters. These tools include the Cluster Administrator, the SQL Server Configuration Manager, and the Failover Cluster Management console.

SQL Server grouping is the term used to depict an assortment of at least two actual servers (hubs), associated by means of a LAN, every one of which have a SQL server example and have a similar admittance to shared capacity. Grouping SQL servers gives high accessibility and insurance from calamities at whatever point a server facilitating the SQL Server example fizzles.

On the off chance that you are on an independent server, an equipment disappointment can stop your tasks. Notwithstanding, with grouping, on the off chance that a hub has issues, you can naturally failover to another hub – with insignificant margin time – and keep on allowing your clients to continue to work while IT attempts to determine the issue. At the point when the essential server is fixed, you can rapidly return tasks.

Open Command Line and Type “bunch gathering” and press enter to list all the accessible asset gatherings of SQL Server Failover Cluster as displayed in the piece underneath. This order will list the Group, Node and Status of each gathering.

Microsoft SQL Server Always On Failover Cluster Instances (FCI) let you run a solitary SQL Server example across different Windows Server Failover Cluster (WSFC) hubs. Anytime, one of the bunch hubs effectively has the SQL occurrence. In case of a disappointment, WSFC naturally moves responsibility for example’s assets to another hub.

SQL Server FCI expects information to be situated on shared capacity with the goal that it very well may be gotten to across all WSFC hubs. This guide depicts how you can send a SQL Server 2019 failover group occurrence that utilizes Storage Spaces Direct (S2D) for shared capacity. S2D gives a product based virtual SAN that can utilize Compute Engine VM information circles to store the SQL data set.

To introduce a failover bunch, you should utilize a space account with nearby overseer privileges, consent to sign on as a help, and to go about as a feature of the working framework on all hubs in the failover group.

You can set OR conditions when the hubs on the group are on various subnets. In any case, every hub in the SQL Server multi-subnet failover bunch should be a potential proprietor of something like one of IP address determined.

In this article, we will focus on how to manage your SQL Server failover cluster using the command line. We will cover the following topics:

1. Creating a New Failover Cluster: You can use the New-Cluster cmdlet to create a new failover cluster.

2. Adding Nodes to a Failover Cluster: You can use the Add-ClusterNode cmdlet to add nodes to an existing failover cluster.

3. Removing Nodes from a Failover Cluster: You can use the Remove-ClusterNode cmdlet to remove nodes from a failover cluster.

4. Checking the Status of a Failover Cluster: You can use the Get-ClusterNode cmdlet to check the status of nodes in a failover cluster.

5. Moving Roles within a Failover Cluster: You can use the Move-ClusterGroup cmdlet to move roles within a failover cluster.

6. Deleting a Failover Cluster: You can use the Remove-Cluster cmdlet to delete a failover cluster.

Creating a New Failover Cluster:

You can use the New-Cluster cmdlet to create a new failover cluster. This cmdlet requires that you specify the name of the failover cluster, as well as the names of the nodes that you want to add to the cluster. You can also use this cmdlet to specify the IP address and subnet mask for the failover cluster, as well as the path to the quorum disk.

To create a new failover cluster named “Contoso” with two nodes named “Node1” and “Node2”, you would use the following command:

New-Cluster -Name “Contoso” -Node “Node1″,”Node2” -StaticAddress 10.0.0.1 -SubnetMask 255.255.255.0 -QuorumDrive “Q:\”

Adding Nodes to a Failover Cluster:

You can use the Add-ClusterNode cmdlet to add nodes to an existing failover cluster. This cmdlet requires that you specify the name of the failover cluster, as well as the names of the nodes that you want to add to the cluster. You can also use this cmdlet to specify the IP address and subnet mask for the failover cluster, as well as the path to the quorum disk.

To add two nodes named “Node3” and “Node4” to the failover cluster named “Contoso”, you would use the following command:

Add-ClusterNode -Name “Contoso” -Node “Node3″,”Node4”

This document describes how to manage SQL Server failover clusters using the command line. It covers the following topics:

• Creating a new failover cluster
• Adding nodes to an existing failover cluster
• Modifying failover cluster properties
• Viewing failover cluster information
• Deleting a failover cluster

Creating a New Failover Cluster:

To create a new failover cluster, use the New-Cluster cmdlet. This cmdlet creates a new failover cluster and sets its initial configuration. The following example creates a new two-node failover cluster named “ContosoCluster” with nodes “Node1” and “Node2”.

New-Cluster –Name ContosoCluster –Node Node1,Node2

Adding Nodes to an Existing Failover Cluster:

To add nodes to an existing failover cluster, use the Add-ClusterNode cmdlet. This cmdlet adds one or more nodes to an existing failover cluster. The following example adds two nodes, “Node3” and “Node4”, to the failover cluster named “ContosoCluster”.

Add-ClusterNode –Name ContosoCluster –Node Node3,Node4

Modifying Failover Cluster Properties:

To modify failover cluster properties, use the Set-Cluster cmdlet. This cmdlet modifies the settings of an existing failover cluster. The following example sets the quorum model of the failover cluster named “ContosoCluster” to NodeMajority.

Set-Cluster –Name ContosoCluster –QuorumMode NodeMajority

Viewing Failover Cluster Information:

To view failover cluster information, use the Get-Cluster cmdlet. This cmdlet gets the properties and settings of an existing failover cluster. The following example gets information about the failover cluster named “ContosoCluster”.

Get-Cluster –Name ContosoCluster

Deleting a Failover Cluster:

To delete a failover cluster, use the Remove-Cluster cmdlet. This cmdlet removes an entire failover cluster, including all nodes, resources, and quorum configurations. The following example removes the failover cluster named “ContosoCluster”.

Remove-Cluster –Name ContosoCluster

Clients speak with the SQL Server occurrence over an inside TCP load balancer. This heap balancer utilizes the Windows Server Failover Clustering specialist to figure out which WSFC hub is presently facilitating the SQL case and courses traffic to that occurrence.

The article accepts that you have proactively sent Active Directory on Google Cloud and that you have essential information on SQL Server, Active Directory, and Compute Engine.

Conclusion:

This document has described how to manage SQL Server failover clusters using Windows PowerShell. For more information about failover clustering, see the Failover Clustering Technical Preview page on the Microsoft website. So keep in mind all the above things for better results & make it user friendly.