Building a Failover Cluster with Server Core Part 2

  • Article

In my previous post I've talked about how to use base images to quickly deploy new servers in my Hyper-V environment. In this post we will configure the shared storage based on the microsoft iSCSI target software, in a real life environment you could use either a Windows Storage Server or another iSCSI or FC based storage environment.

Before actually digging into the failover clustering installation I want to briefly explain what I have setup so far to be able to build a cluster in the first place.

First I have created a Domain Controller and installed the iSCSI target software to be able to emulate a shared storage environment. I've created two disks one which is 100MB in size and will be used as a witness disk (used to be called Quorum disk) and I have a second disk which is is 1GB of size and will be used as a data disk.

Secondly I have installed two Server Core machines and added the to the domain (read Configuring Windows Server 2008 Server Core or use the Coreconfigurator tool). Make sure your Server core machines have at least two network cards, one for the normal traffic and one for the cluster heartbeat. After having configured all basic things we are now ready to start with the installation and configuration of the clustering software.

Let's do this step by step:

Step 1: Install the Failover Cluster role

failovercluster-1

Make sure you do this on both Server Core machines

Step 2: Configure and Start the iSCSI initiator service

failovercluster-2

Again perform this on both machines. Now the Microsoft iSCSI initiator service is configured and will start up during boot time.

Step 3: Connecting the Server Core boxes to the iSCSI storage box

Here are all steps you should take on both Server Core boxes to connect to the storage.

  1. iSCSIcli QAddTargetPortal <Storage Box, Portal IP Address>
    Required to refresh the new target built,

  2. iSCSIcli ListTargets
    You should see the iQN of the target created

    failovercluster-3

  3. iSCSIcli QloginTarget <Target IQN>
    You should see a connection and session id

  4. iSCSIcli PersistentLoginTarget <target_iqn> T * * * * * * * * * * * * * * * 0

    NOTE: There are 15 “space” + “*”
    You do this so you can survive a reboot

  5. iSCSIcli ListPersistentTargets
    You should see a target

    failovercluster-4

  6. iSCSIcli ReportTargetMappings

    You should see the target and a LUN x mapping for every LUN defined in the target

At this stage you have assigned both disks to the server core machines the next step will be to configure the disks

Step 4: Configuring the clustered disks

By being GUI less you need to do this onto the command line.

First list the disks in your boxes by using the diskpart commandline tool:

diskpart

list disk (this will return the disks available in your system in my case I had disk 0, 1 and 2 with 0 being my OS disk and the other two the disks for my cluster)

select disk 1
attribute disk clear readonly
online disk
create part primary
select part 1
assign letter=Q

select disk 2
attribute disk clear readonly
online disk
create part primary
select part 1
assign letter=S

exit

image

Format each disk by typing format x: /q where X is your drive letter and don't provide any label name.

The servers are now completely configured to form a Windows Failover Cluster, this process will be explained in Part III of this post.

Technorati Tags: Server Core,Windows Failover Clustering,Windows Server 2008

Comments

  • Anonymous
    March 31, 2008
    PingBack from http://msft.starsports.info/msft/building-a-failover-cluster-with-server-core-part-2/

  • Anonymous
    July 02, 2008
    Lately it's been very quiet on my blog. There are a couple of things to that. First and foremost there

  • Anonymous
    February 26, 2009
    Last time I took a look at Hyper-V Server 2008 R2 Beta, I shared the surprise of having Failover Clustering

  • Anonymous
    March 17, 2009
    Here is a free version of iSCSI Target, named iStorage Server: http://www.kernsafe.com/product.aspx?id=5 It is powerful and beautiful

  • Anonymous
    February 25, 2010
    The comment has been removed

  • Anonymous
    February 25, 2012
    The comment has been removed