Setting up load balancing on a SharePoint farm running on Windows Server 2008

1. Install Network Load Balancing Feature on each Web Front End

On each front end in the farm, within Server Manager, add the NLB feature:

Click Install and wait a bit

2.Add a New Cluster

Through the start menu, Administrator Tools, click Network Load Balancing Manager:

Right click Network Load Balancing Clusters, and choose New Cluster

Type the IP address of one of the web fronts in the farm to serve as the first host in the cluster

Click Connect.

Click next.

Leave the defaults and click next again:

3.Set Cluster IP Address

This IP Address is the dedicated IP address for the cluster and is what DNS will point to, to get load balanced between the front ends. On the Cluster IP Addresses box, click Add and type an available dedicated IP address and subnet mask:

Optionally, you can setup many clusters IPs for fault tolerance purposes, but for most cases you’ll just have one:

Click next.

4.Specify Cluster Parameters

Select the Multicast operation mode, and click next:

5.Specify Port Rules

Click edit on the default port rule:

Deselect the “All” checkbox, and choose the Network filtering mode:

Click Ok.

Click Finish.

After finish, the NLB manager will show it has begun the configurations changes. If you’re in a remote desktop to the server, you’ll lose your connection temporarily while it re-configures:

6.Add Any Additional Hosts to the Cluster

Now that the cluster is ready to go, you can add additional hosts/web front ends. Right click on the cluster IP address and click Add Host To Cluster and type the IP of another web front end in the farm. Repeat until they’re all added.

Advertisements

Prepare Windows Cluster SharePoint

This part demonstrate how to configure windows cluster for two server, to be used as SQL Cluster.

Before you start

· You need to have two network adapters on each node, one Public and one Private(for heartbeat communication).

· Shared storage (like SAN storage) should be present and connected to both cluster nodes  with at least:

  • Quorum Disk (5GB)
  • DTC Disk (1GB)
  • SQL data files and log file disk(s)

· domain user account (SPSadmin): add SPSadmin user as administrator on both servers

· Prepare a preserved static IP and Cluster Name to be used.

· Prepare a preserved static IP and DTC Name to be used.

Windows Cluster Configuration

1. Install latest windows updates on all server nodes.

2. Install Application role and IIS role on both SQL DB server nodes

3. Install Fail over clustering feature on both SQL DB server nodes.

4. Provide a Cluster Name and Cluster IP for the database nodes:

Note: make sure that the public network is used here not the private (heartbeat)

5. Below are the servers info

6. Cluster Disk files are configured as the following:

7. Configure DTC as clustered service , this is a pre requisite for SQL Cluster installation

8. DTC cluster configuration

9. Assign the DTC a cluster disk

10. Create SQL Group which is a logical group to include all SQL resources in :

Add SQL Server Availability Group to Exiting Failover Cluster Instance–Part1 of 2

Introduction

Microsoft SQL Server 2012/2014 AlwaysOn provides flexible design choices for selecting an appropriate high availability (HA) and disaster recovery (DR) solution for your application. Building on that fact I will be providing a posts that provides a step-by-step configuration for extending a 2 Node SQL Server Failover Cluster Instance with a 3rd Node that host AlwaysOn Availability Group (This scenario is also known as FCI+AG). For more information about SQL Server 2012 AlwaysOn high availability and disaster recovery design patterns, see SQL Server 2012 AlwaysOn High Availability and Disaster Recovery Design Patterns.

Prerequisites

This posts assumes a basic knowledge of failover cluster instances (FCIs), availability groups, high availability, and disaster recovery concepts. For more information about the full AlwaysOn solution feature set, see the Microsoft SQL Server AlwaysOn Solutions Guide for High Availability and Disaster Recovery white paper.

Scenario

In this scenario I will be using a preconfigured FCI with 2 Nodes, and will be walking through the activities needed for adding a 3rd Node as a DR Server with the following software setup:

  1. Windows Server 2012 R2
  2. All servers are joined to the domain

To make the scenario simple I will be using a Domain Account that has a Local Administrator Permission on All Nodes. In addition, the configuration below will be using a combination of PowerShell Scripts (that will be running as Admin) and GUI so let’s get started:

1. Installing SQL Server on DR Node

We need to install a New Standalone Instance on the DR Node. I will do that using the below sample unattended SQL Setup Script:

Setup.exe /q /ACTION=Install /FEATURES=SQL /INSTANCENAME=MSSQLSERVER /SQLSVCACCOUNT=”” /SQLSVCPASSWORD=”” /SQLSYSADMINACCOUNTS=”” /AGTSVCACCOUNT=”” /AGTSVCPASSWORD=”” /IACCEPTSQLSERVERLICENSETERMS<

2. Installing Windows Failover Cluster on DR Node

Login to the DR Node and run the below script using PowerShell:

Import-Module ServerManager
Add-WindowsFeature Failover-Clustering –IncludeAllSubFeature
Install-WindowsFeature -Name Failover-Clustering –IncludeManagementTools

3. Add DR Node to Existing Windows Failover Cluster

Login to the Active Node on the FCI >> Open “Failover Cluster Manager” and Right click on “Nodes”, Then click on “Add Node”

Click on “Next” in “Add Node Wizard”

User keyboard to Enter server name: in “Add Node Wizard” then click on “Add” in “Add Node Wizard”

Click on “Next” in “Add Node Wizard”

Select “No” for Validating Cluster and Click on “Next” in “Add Node Wizard”

Unselect “Add all eligible storage to the cluster. (check box)” in “Add Node Wizard”

Click on “Next” in “Add Node Wizard”

Make sure that the new node appears in the list of nodes.