winadmins.wordpress.

com
http://winadmins.wordpress.com/2011/11/01/configuration-of-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 using
StarWind storage sof tware.
Failover cluster conf iguration includes two (or more) server nodes that share an external storage. Based on
the iSCSI technology, StarWind Sof twaf e Inc. StarWind enables to create an external storage in Windows
environment without implementation of expensive FC or external SCSI solutions. With StarWind you can create
a shared disk array on a host running Microsof t Windows.
A sample example of two node f ailover cluster using StarWind:
Requirement s f or Windows Server 2008 R2
Failover Clust er
Heres a review of the minimum requirements to create a
Windows Server 2008 R2 Cluster:
Two or more compatible servers: You need
hardware that is compatible with each other, highly
recommended to always use same type of hardware
when you are creating a cluster.
A shared storage: This is where we can use
StarWind iSCSI SAN sof tware.
Two network cards on each server, one public
network (f rom which we usually access Active
Directory network) and a private f or heartbeat
between servers. This is actually an optional requirement since using one network card is possible but
not suitable in almost any environment.
When we are using iSCSI protocol f or our shared storage Microsoft recommends three network
cards on each host: Public network, private, and one dedicated to iSCSI communication f rom servers to
the storage, which in our case will be represented by a server using StarWind iSCSI sof tware.
Windows Server 2008 R2 Enterprise or Datacenter Editions f or hosts which will be part of the
cluster. 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 dont
need a Domain Admin account, but we do need a Domain account which is included in the local
Administrators of each host.
DNS host records of all nodes must be conf igured.
Requirement s f or St arWind iSCSI SAN Sof t ware
Here are the requirements f or installing the component which will be in charge of receiving the iSCSI
connections:
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 youve 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 the
interesting f eatures about it: You can install
the service separately f rom the console f rom
which you can administer the StarWind iSCSI.
This way you can install the console on any
machine compatible to access the server or
servers with StarWind iSCSI and manage
storage, permissions, etc. In this case, Ill be
selecting the f ull installation.
The next steps are pretty straight f orward so
you wont have any problem. Once the f inal
steps are completed youll get a warning about
the iSCSI Service needed bef ore installing the
StarWind iSCSI Service.
You just need to access the Services
console and set the service as started and
automatic.
Af ter you click install, the process only takes
a f ew seconds and you will additionally see
some drivers that will be installed on the
operating system; click Install.
Preparing Quorum Volume:
Start StarWind iSCSI console, In the General
screen well f ind the summary inf ormation plus
how 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 example
the Network options which enable the iSCSI
communications (port 3260) on any of the network
adapters identif ied.
If we are using a special LAN/VLAN to separate our
iSCSI traf f ic as recommended, then we should only
enable the IP address used f or that purpose.
Launch the StarWind Management Console selecting
Start -> All Programs > StarWind Sof tware ->
StarWind -> StarWind. Af ter the console is launched its
icon appears in the system tray. Double click the icon
with the lef t mouse
button or single click it with the right and select Start
Management pop-up menu item. From the StarWind
Servers tree please select the computer you wish to
connect to. Press the right mouse button over the
desired host (computer) and select the Connect menu
item. You will be prompted to enter the login and
password. Def ault ones are: root, starwind. You can
always change them later
With the host added, we can start creating the
storage that will be published through iSCSI: Right-
click the server and select Add target and a new
wizard will appear.
Select the Target alias f rom which well identif y the
LUN we are about to create and then conf igure to
be able to cluster. In my case Im using a simple
name w2k8r2-clstr, click on Next.
Since we are going to be using hard drives to
present our storage, in Storage Type select Hard
Disk, click on Next.
In Device Type please note that we can use
physical as virtual drives to present to our clients
using iSCSI. We are going to select Basic Virtual,
f rom which well create a f ile (.img) that will
represent the LUN; click on Next.
Select Image File device and click on Next.
Since we are creating a new one, select Create
new virtual disk and click on Next.
If you have decided to create a new virtual disk
please specif y the location and the name of the
virtual disk you wish to be created. Also you have
to provide the virtual disk size in megabytes.
Check any additional parameters of the virtual
disk you wish to create. Please ref er to the
online help f or details regarding those additional
parameters (Compressed and Encrypted).
Here, we are using a separate drive where Im
going to save all of my LUNs
In the cache parameters, leave the def ault
options selected Normal (no caching); click on
Next.
In the last screen, just click on Finish and well
have our LUN ready.
As optional and recommended review the
options f or CHAP permissions and Access
Rights. Within these options we can conf igure
all the parameters needed f or secure
environments.
Once weve completed this, we can access this
f ile f rom a Windows Server 2008 R2 host.
Preparing Cluster Nodes:
Change the below settings on Node1:
Network settings:
Each adapter will be assigned a static IP
address. Select the Use the f ollowing IP
address option and type in the IP address you
wish to use. The Subnet mask and DNS server
address must also be provided. All the values
must be
correctly chosen given the networking
conf iguration of the Corporate LAN that the
cluster will be a part of . As this interf ace is f or
the public network, a def ault gateway will need
to be assigned.
Press the OK button.
Just as was done f or the f irst network adapter,
assign appropriate values to the TCP/IP
conf iguration of the second network adapter
using the f ollowing example image as
guidance. This interf ace is used f or iSCSI
target storage communications and a def ault
gateway need not be specif ied.
Configuring iSCSI initiator
Launch the Microsof t iSCSI Sof tware Initiator
application Administrative Tools-> iSCSI
Initiator
Select the Discovery Tab.
In the Target Portals group, click the Add
Portal button.
Press the Add Portal button
In the Add Target Portal dialog enter IP
address or DNS name of the StarWind target
server.
Click on the Targets tab. Select the IQN of
the target just added.
In my case, Ive created two LUNs available
f or the cluster.

Press the Log On button.
The Log On to Target dialog now appears. In
this dialog click on the checkbox
Automatically restore this connection when
the system boots to make this connection
persistent.
Initializing, formatting and creating
partitions
When the StarWind Disks are connected,
they show up on the initiator machine as new
disk devices. Bef ore these devices can be
used as cluster disks, they have to be
initialized and f ormatted. Launch the
Computer Management console.
Bring disks online. Press the right mouse
button over the disk and select Online.
Initialize the Disks. Press the right mouse
button over the Disk and select Initialize
Disk. Follow the wizard to initialize the new
disks.
Right-click over the unallocated space and
select New Simple Volume. Follow the
instructions in the wizard to create an NTFS
partition f or use as the quorum disk.
Change the below settings on Node2:
Perf orm the above steps on node 2. Only
changes 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 done
on Node 1.
Install Failover Cluster feature and run
cluster validation
Perform the below steps on both nodes:
Prior to conf igure the cluster, we need to
enable the Failover Cluster f eature on all
hosts in the cluster and well also run the
verif ication tool provided by Microsof t to
validate the consistency and compatibility of
our scenario.
In Server Manager, access Features and
select Failover Cluster. This f eature does
not 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 complete
conf iguration.
Check the parameters are correct. Press the Previous button
should any changes be required
We can also have a detailed report about the results on each
test.
Create a Cluster
It is now time to create the cluster. Click Create a Cluster item
f 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 till Finish
Now that the creation of the cluster is complete it will be shown
in the panel on the lef t. Expand the cluster by clicking on the +
symbol next to the cluster, then click on Storage. The Failover
Cluster Management console should look like the example
picture provided below. Both cluster disk resources will be
shown as online.
Adding services t o a clust er
To add a service, open the Failover Cluster Management tool,
browse to your cluster and right-click Services And
Applications. From the shortcut menu, choose the Conf igure
A Service Or Application option. This starts the High
Availability Wizard.
Select Service Or Application
Af ter the introduction page of the wizard, youre asked to
choose the service or application that you want to make
highly available. Check with your sof tware vendor to
determine cluster compatibility. The next steps of the wizard
will change depending on what you select on this page
For each service you conf igure, you must specif y how clients
will access the service. Remember that the clustered service
will appear as a single entity to client computers. Name the
service and provide the service with a unique IP address
Next, choose the shared storage device that will be used by
the chosen service
Once you make this selection, you have the opportunity to
conf irm your selections. Af terwards, the wizard will make the
selected service highly available on your network
you can see the shared f ile server in action.