winadmins.wo rdpress.co mhttp://winadmins.wordpress.com/2011/11/01/configuration-o f-two-node-file-server-failover-clustering-part-2/

Configuration of two node file server failover clustering – Part 2

In this article, i will show you step by steps conf iguration of two node f ile server f ailover clustering usingStarWind storage sof tware.

Failover cluster conf iguration includes two (or more) server nodes that share an external storage. Based onthe iSCSI technology, StarWind Sof twaf e Inc. StarWind enables to create an external storage in Windowsenvironment without implementation of expensive FC or external SCSI solutions. With StarWind you can createa shared disk array on a host running Microsof t Windows.

A sample example of two node f ailover cluster using StarWind:

Requirements for Windows Server 2008 R2Failover Cluster

Here’s a review of the minimum requirements to create aWindows Server 2008 R2 Cluster:

Two or more compatible servers: You needhardware that is compatible with each other, highlyrecommended to always use same type of hardwarewhen you are creating a cluster.

A shared storage : This is where we can useStarWind iSCSI SAN sof tware.

Two network cards on each server, one publicnetwork (f rom which we usually access ActiveDirectory network) and a private f or heartbeatbetween servers. This is actually an optional requirement since using one network card is possible butnot suitable in almost any environment. When we are using iSCSI protocol f or our shared storage Microsoft recommends three networkcards on each host : Public network, private, and one dedicated to iSCSI communication f rom servers tothe storage, which in our case will be represented by a server using StarWind iSCSI sof tware.

Windows Server 2008 R2 Enterprise or Datacenter Edit ions f or hosts which will be part of thecluster. Always keep in mind that cluster is not supported in Standard Editions.

All hosts must be member f rom an Active Directory domain. To install and conf igure a cluster we don’tneed a Domain Admin account, but we do need a Domain account which is included in the localAdministrators of each host.

DNS host records of all nodes must be conf igured.

Requirements for StarWind iSCSI SAN Software

Here are the requirements f or installing the component which will be in charge of receiving the iSCSIconnections:

Windows Server 2008 or Windows Server 2008 R2

10 GB of disk space f or StarWind application data and log f iles

[Highly Recommended] 4 GB of RAM

1 Gigabit Ethernet or 10 Gigabit Ethernet.

Installing StarWind iSCSI SAN Software:

Perform the below steps on a Windows 2008 Server for which you want to treat as SAN:

Download the StarWind sof tware f rom http://www.starwindsof tware.com/starwind-f ree

Af ter you’ve downloaded the installation f ile, just double click it and the wizard will start.

Follow the wizard normally as any installation.In the process you will f ind one of theinteresting f eatures about it: You can installthe service separately f rom the console f romwhich you can administer the StarWind iSCSI.

This way you can install the console on anymachine compatible to access the server orservers with StarWind iSCSI and managestorage, permissions, etc. In this case, I’ll beselecting the f ull installation.

The next steps are pretty straight f orward soyou won’t have any problem. Once the f inalsteps are completed you’ll get a warning aboutthe iSCSI Service needed bef ore installing theStarWind iSCSI Service.

You just need to access the “Services”console and set the service as started andautomatic.

Af ter you click install, the process only takesa f ew seconds and you will additionally seesome drivers that will be installed on theoperating system; click “Install”.

Preparing Quorum Volume:

Start StarWind iSCSI console, In the “General”screen we’ll f ind the summary inf ormation plushow to connect to local or remote StarWind host.

In the “Conf iguration” section we can f ind the common

parameters to conf igure iSCSI StarWind, f or examplethe “Network” options which enable the iSCSIcommunications (port 3260) on any of the networkadapters identif ied.

If we are using a special LAN/VLAN to separate ouriSCSI traf f ic as recommended, then we should onlyenable the IP address used f or that purpose.

Launch the StarWind Management Console selectingStart -> All Programs –> StarWind Sof tware ->StarWind -> StarWind. Af ter the console is launched itsicon appears in the system tray. Double click the iconwith the lef t mouse button or single click it with the right and select StartManagement pop-up menu item. From the StarWindServers tree please select the computer you wish toconnect to. Press the right mouse button over thedesired host (computer) and select the Connect menuitem. You will be prompted to enter the login andpassword. Def ault ones are: root, starwind. You canalways change them later

With the host added, we can start creating thestorage that will be published through iSCSI: Right-click the server and select “Add target” and a newwizard will appear.

Select the “Target alias” f rom which we’ll identif y theLUN we are about to create and then conf igure tobe able to cluster. In my case I’m using a simplename “w2k8r2-clstr”, click on “Next”.

Since we are going to be using hard drives topresent our storage, in “Storage Type” select “HardDisk”, click on “Next”.

In “Device Type” please note that we can usephysical as virtual drives to present to our clientsusing iSCSI. We are going to select “Basic Virtual”,f rom which we’ll create a f ile (.img) that willrepresent the LUN; click on “Next”.

Select “Image File device” and click on “Next”.

Since we are creating a new one, select “Createnew virtual disk” and click on “Next”.

If you have decided to create a new virtual diskplease specif y the location and the name of thevirtual disk you wish to be created. Also you haveto provide the virtual disk size in megabytes.

Check any additional parameters of the virtualdisk you wish to create. Please ref er to theonline help f or details regarding those additionalparameters (Compressed and Encrypted).

Here, we are using a separate drive where I’mgoing to save all of my LUNs

In the cache parameters, leave the def aultoptions selected “Normal (no caching)”; click on“Next”.

In the last screen, just click on “Finish” and we’llhave our LUN ready.

As optional and recommended review theoptions f or “CHAP permissions” and “AccessRights”. Within these options we can conf igureall the parameters needed f or secureenvironments.

Once we’ve completed this, we can access thisf ile f rom a Windows Server 2008 R2 host.

Preparing Cluster Nodes:

Change the below sett ings on Node1:

Network sett ings:

Each adapter will be assigned a static IPaddress. Select the Use the f ollowing IPaddress option and type in the IP address youwish to use. The Subnet mask and DNS serveraddress must also be provided. All the valuesmust be correctly chosen given the networkingconf iguration of the Corporate LAN that thecluster will be a part of . As this interf ace is f orthe public network, a def ault gateway will needto be assigned.

Press the OK button.

Just as was done f or the f irst network adapter,assign appropriate values to the TCP/IPconf iguration of the second network adapterusing the f ollowing example image asguidance. This interf ace is used f or iSCSItarget storage communications and a def aultgateway need not be specif ied.

Configuring iSCSI init iator

Launch the Microsof t iSCSI Sof tware Init iatorapplication Administrative Tools-> iSCSIInit iator

Select the Discovery Tab.

In the Target Portals group, click the AddPortal… button.

Press the Add Portal… button

In the Add Target Portal dialog enter IPaddress or DNS name of the StarWind targetserver.

Click on the Targets tab. Select the IQN ofthe target just added.

In my case, I’ve created two LUNs availablef or the cluster.

Press the Log On… button.

The Log On to Target dialog now appears. Inthis dialog click on the checkboxAutomatically restore this connection whenthe system boots to make this connectionpersistent.

Init ializing, formatting and creatingpartit ions When the StarWind Disks are connected,they show up on the init iator machine as newdisk devices. Bef ore these devices can beused as cluster disks, they have to beinit ialized and f ormatted. Launch theComputer Management console.

Bring disks online. Press the right mousebutton over the disk and select Online.

Init ialize the Disks. Press the right mousebutton over the Disk and select Init ializeDisk. Follow the wizard to init ialize the newdisks.

Right-click over the unallocated space andselect New Simple Volume. Follow theinstructions in the wizard to create an NTFSpartit ion f or use as the quorum disk.

Change the below sett ings on Node2:

Perf orm the above steps on node 2. Onlychanges needs to be done:

IP address f or network adapter 1 –192.168.1.22 (LAN)

IP address f or network adapter 2 –192.168.2.22 (heartbeat)

Rest, conf igure the settings as it was doneon Node 1.

Install Failover Cluster feature and runcluster validation

Perform the below steps on both nodes:

Prior to conf igure the cluster, we need toenable the “Failover Cluster” f eature on allhosts in the cluster and we’ll also run theverif ication tool provided by Microsof t tovalidate the consistency and compatibility ofour scenario.

In “Server Manager”, access “Features” andselect “Failover Cluster”. This f eature doesnot need a reboot to complete.

Once installed, access the console f rom“Administrative Tools”. Within the console,the option we are interested in this stage is“Validate a Conf iguration”.

Select Next and Select Run all tests(recommended) f or testing the completeconf iguration.

Check the parameters are correct. Press the Previous buttonshould any changes be required

We can also have a detailed report about the results on eachtest.

Create a Cluster It is now time to create the cluster. Click Create a Cluster itemf rom the Actions panel shown on the right.

Add the names of servers you wish to use as cluster nodes.

Next, Specif y Cluster Name and Cluster IP address.

Click Next t ill Finish

Now that the creation of the cluster is complete it will be shownin the panel on the lef t. Expand the cluster by clicking on the ‘+’symbol next to the cluster, then click on Storage. The FailoverCluster Management console should look like the examplepicture provided below. Both cluster disk resources will beshown as online.

Adding services to a cluster

To add a service, open the Failover Cluster Management tool,browse to your cluster and right-click Services AndApplications. From the shortcut menu, choose the Conf igureA Service Or Application option. This starts the HighAvailability Wizard.

Select Service Or Application

Af ter the introduction page of the wizard, you’re asked tochoose the service or application that you want to makehighly available. Check with your sof tware vendor todetermine cluster compatibility. The next steps of the wizardwill change depending on what you select on this page

For each service you conf igure, you must specif y how clientswill access the service. Remember that the clustered servicewill appear as a single entity to client computers. Name theservice and provide the service with a unique IP address

Next, choose the shared storage device that will be used bythe chosen service

Once you make this selection, you have the opportunity toconf irm your selections. Af terwards, the wizard will make theselected service highly available on your network

you can see the shared f ile server in action.