You are here: User_Guide > Clustering > Extending a Traditional 2-Node WSFC SQL Server Cluster to a Third Node via DataKeeper

Extending a Traditional 2-Node WSFC SQL Server Cluster to a Third Node via DataKeeper

When replicating from a WSFC SQL Server 2-node cluster to a third node via DataKeeper, the following tasks are required:

The following example details the steps necessary to extend a SQL Server cluster resource group from a 2-node cluster to a third node via DataKeeper.   

  1. Remove physical disk resource from WSFC.

This also removes any dependencies on these physical disk resources.  These dependencies will need to be reestablished to the new DataKeeper volume resource, so please take note of what these dependencies are before completing this first step by viewing the Dependency Report.  Highlight your resource and select Show Dependency Report.  

Use Failover Cluster Manager MMC to perform the following steps:

  1. Offline the SQL Server cluster resource group by right-clicking and selecting Take this service or application offline.

  1. Remove the physical disk from the SQL Server cluster resource group (moves to Available Storage).

  1. Remove the physical disk resource from the SQL Server cluster configuration by deleting the resource from the Available Storage group.  

  1. Configure cluster quorum settings.

Because there will now be a third node in a remote site, the Disk Witness in Quorum is no longer valid; therefore, the Node Majority configuration should be selected.

  1. Right-click the cluster and select More Actions / Configure Cluster Quorum Settings...  

  1. Select Node Majority. Note: Change the quorum type to Node Majority if the final number of nodes is odd as in a 3-node cluster, or Node and File Share Witness Majority if the final number of nodes will be even as in a 4-node cluster.

  2. Delete disk witness from Available Storage.

  1. Online Disk.  

Use Disk Management MMC to perform the following steps:

  1. Online the physical disk.

  1. Change the drive letter to match the previous SQL Server configuration (if needed).

  1. Repeat the above steps, 2a and 2b, on all shared nodes in the cluster.

  1. Make sure the volume of the third node is available to become a target.  It should be formatted and online, and it should be at least as big or bigger than the source volume.  

  2. Create Mirror.  

Use the DataKeeper UI to perform the following steps (Note:  Make sure DataKeeper is running on all servers):

  1. Connect to all shared nodes and the third node. 

The Server Overview Report will show connection to all three nodes:  

  1. Create a job containing a mirror to the third node.

  1. Select a Source.

  1. Select Shared Volumes.

  1. Select a Target.

  1. Configure Details.  Choose compression settings, if applicable, and choose mirror type, Asynchronous or Synchronous.  Select Done.

The mirror will then begin resyncing to the third node.  After resyncing is complete, the Job State will change to Mirroring.

  1. Add DataKeeper Volume Resource.  

To add the DataKeeper Volume Resource to the SQL Server cluster resource group, perform one of the following:

Automatic Creation of a Mirror in WSFC

Manual Creation of a Mirror in WSFC

  1. Add third node into the cluster.

Use Failover Cluster Manager MMC to perform the following steps (Note:  Make sure the Failover Clustering feature is installed on the third node prior to adding into cluster):

  1. Right-click Nodes.

  2. Select Add Node.

  3. In the Add Node Wizard, enter name of server to be added, click Add and select Next.

  4. Yes may be chosen to perform Validation Testing, but be aware that some errors are expected due to the disk being locked on the target side.  Note: When performing validation testing, select Run only the tests I select, then deselect the Storage tests from the Test Selection screen.

Even though the Storage tests were deselected, the Failover Cluster Validation Report will still report a List Cluster Volumes failure in the Cluster Configuration Test.  This, along with a few other  warnings, is expected due to the third node and its volume not being shared with the first two nodes.

  1. After viewing the Validation Report, select Finish.  The Validation Warning screen will reappear.  Select No to add the node without performing the tests again.  

  2. Select Next on the Confirmation screen.

  3. The Summary screen will appear indicating that the node was added successfully.  A Warning may appear on this screen because SQL Server has not yet been installed on the third node.  This installation will be performed in the next step.

  1. Install SQL Server on the third node.  
  1. On third node, run the following command:

Setup /SkipRules=Cluster_VerifyForErrors /Action=AddNode /INSTANCENAME="MSSQLSERVER"

  1. On Setup Support Rules screen, select Okay.

  2. When prompted, enter Product Key and select Next.

  3. Accept License Terms and select Next.

  4. On the Setup Support Files screen, select Install.

  5. The Setup Support Rules screen will appear.  Review the System Configuration Check Report for any failures, then select Next.

  6. Select Next when the Cluster Node Configuration screen appears.

  7. On the Service Accounts screen, enter Passwords for SQL Server services based on setup of the first nodes.  Select Next.

  1. When the Error Reporting screen appears, select Next.

  2. When the Add Node Rules screen appears, select Next.

  3. Once the Ready to Add Node screen appears, select Install.

  4. The Complete screen will appear notifying that the Failover Cluster Add Node operation is complete.  Select Close.

  1. The final step is to reestablish any/all resource dependencies between the SQL Server service resource and the new DataKeeper volume resource.
  1. Right-click the application resource and select Properties.

  2. Select the Dependencies tab.

  3. Click on the Click here to add a dependency tab.

  4. Enter the new DataKeeper volume

  5. Select Apply and then Okay.

Dependencies should now be reestablished.  The Dependency Report may be viewed again to make sure.

of

© 2013 SIOS Technology Corp., the industry's leading provider of business continuity solutions, data replication for continuous data protection.