Windows Server 2008 Enterprise Fail Over Clustering Lab

7/28/2019 Windows Server 2008 Enterprise Fail Over Clustering Lab

1/10

Windows Server 2008Enterprise Failover Clustering

Lab

Microsoft Virtual Labs


2/10

Windows Server 2008 Enterprise Failover Clustering Lab

Table of Contents

Windows Server 2008 Enterprise Failover Clustering Lab ................................................... 1

Exercise 1 Adding a Second Node to the Cluster .......... ........... .......... ........... .......... ........... .......... ........... .......... ........... . 2

Exercise 2 Creating a File Share Cluster ........... .......... ........... .......... ........... .......... ........... ........... .......... ........... .......... ... 3Exercise 3 Creating a Print Share Cluster .......... .......... ........... .......... ........... .......... ........... ........... .......... ........... .......... ... 4

Exercise 4 Creating Failback Policies .......... .......... ........... .......... ........... .......... ........... .......... ........... .......... ........... ........ 5

Exercise 5 Configuring Highly Available WINS .......... ........... .......... ........... .......... ........... .......... ........... .......... ........... . 6

Exercise 6 Configuring Highly Available DHCP .......... ........... .......... ........... .......... ........... .......... ........... .......... ........... . 7

Exercise 7 Bonus Section, Clustering Disks .................................................................................................................. 8


3/10


Page 1 of 8

Windows Server 2008 Enterprise Failover

Clustering Lab

ObjectivesAfter completing this lab, you will be better able to: Add nodes to Windows Server 2008 Enterprise Failover Cluster Create file share cluster Create print share cluster Create failback policies for the cluster Make Windows Internet Naming Service (WINS) highly available on a

Windows Server 2008 Enterprise Failover Cluster

Make a Dynamic Host Configuration Protocol (DHCP) server highlyavailable with a Windows Server 2008 Enterprise Failover Cluster

ScenarioYou are responsible in your organization for the configuration of Windows

Server 2008 Enterprise failover clustering in your organization. You need to be

able to add nodes to the cluster and to configure the cluster to support a variety ofhigh-availability roles, such as file, print, and DHCP server clusters.

Estimated Time toComplete This Lab 60 MinutesComputer used in this Lab

NYC-DC-1

NYC-SRV-1

NYC-SRV-2

The password for the woodgrovebank.com\Administrator account on this

computer is: pass@word1.


4/10


Page 2 of 8

Exercise 1Adding a Second Node to the Cluster

ScenarioThis initial section will walk you through expanding a cluster. The first thing to notice in this lab is how much easierit is to create a cluster. As opposed to the involved process of setting up clusters in Microsoft Windows Server

2003 R2 Enterprise Edition, the new paradigm for Failover Clusters in Window Server 2008 Enterprise is to simply

name the cluster, dictate which servers will be in the cluster, and let the wizard create the cluster.

Note:Due to the limitations imposed by using virtual machines for this lab, you will only add a node to an existing,

one-node cluster as opposed to creating the entire cluster from scratch.

The second item to pay particular attention to is Cluster Validation tool. This tool serves as both a cluster pre-

configuration tool and best-practice analyzer that allows you to know whether or not your proposed cluster will

work and can be supported by Microsoft and as diagnostic tool for your cluster once you have your cluster up and

running.

Tasks Detailed Steps

Complete the following

task on:

NYC-SRV-1

1. Add a Second Nodeto the Cluster

a. Log on to NYC-SRV-1 as Woodgrovebank\administrator (pass@word1).b. ClickStart, Administrative Tools, Failover Clusters Managerc. In the left pane, expand HOL169Cluster.woodgrovebank.com.d. Select Nodes. On the right side of the screen, there is an actions pane. ClickAdd

Node.

e. The Add Node Wizard will pop up. ClickNext.f. In the Enter Server Name box, enter NYC-SRV-2. ClickAdd.g. ClickNext.h. At the Validation Warning screen, leave Yes selected and clickNext.i. ClickNext.

j. Select Run only tests I select then clicknext.k. Deselect Storage from the list and clickNextNote:Normally you would run the storage tests as well, but in the interest of time

these tests will be skipped at this point.

l. ClickNext.m.On the confirmation page, clickNext.n. Please note that the validation test may take some time to complete. View the

report to see what validation tests were executed. If you see a warning for Validate

IP Configuration, it can be ignored.

o. ClickFinish.p. At the Validation Warning screen, click next to the No option, then clicknext

twice.

q. After the task completes, clickFinish.r. If you are prompted to scan the newly recognized drives, select Continue without

scanning.


5/10


Page 3 of 8

Exercise 2Creating a File Share Cluster

ScenarioIn this exercise you will learn how to create a file share cluster. As with cluster creation, this process is extremelystreamlinedyou no longer have to worry about groups, for example. Failover Clusters in Windows Server 2008

Enterprise are designed so that IT generalists can effectively administer and manage clusters and core cluster

workloads, such as highly available file shares.


Complete the following 3

tasks on:

NYC-SRV-1

1. Add a Shared Folder

a. If not already open, launch Failover Clusters Manager.b. In the left side pane, clickServices and Applications.c. In the right side pane, click Configure a Service or Application.d. The High Availability Wizard will appear. ClickNext.e. A list of available services and applications will appear. Select File Server. Click

Next.

f. On the Client Access Point screen, in the Name field, type HOL169FILE.g. In the Address box, type 192.168.100.14. ClickNext.h. Click the check box next to the first available Disk and clickNext.i. ClickNext, then clickFinish.

j. On the left pane, expand Services and Applications and then clickHOL169FILE.

k. In the right pane, clickAdd a Shared Folder. ClickNext.l. ClickBrowse and select the folder icon. ClickMake New Folder and name it

clustershare. ClickOK.

m.ClickNext.n. Choose an appropriate Share Name and Description, and clickNext.o. Select Administrators have full access; other users have read-only access. Click

Finish twice.

2. Create a SharingSubfolder

a. In the middle pane, right-click the shared folder that you just created, and selectProperties.

Note:If there is a share but the columns are empty, repeat steps 10 -12 to create a

second share with another new folder.

b. Go to the General tab. ClickAdvanced.c. Go to the Subdirectories tab. Check the Share Subdirectories box. ClickOK,

Apply, Yes, OK, OK.

d. On the Select Features page, clickNext.3. Check out the Local

and Cluster Shares

a. On the taskbar, clickStart, Administrative Tools, Computer Management.Expand System Tools, Shared Folders, and clickShares. Note that the shared

subdirectories are not visible.

b. At the top of the left pane, right-clickComputer Management (local). SelectConnect to another computer and type HOL169FILE, which is the name of the

file share resource we just created, then clickOK. Note that the shares are now

visible.


6/10


Page 4 of 8

Exercise 3Creating a Print Share Cluster

ScenarioIn this exercise, you will create a print share cluster. Not having to deal with granular details opens up importantfunctionality such as making print shares highly available to administrators and IT professionals.



task on:

NYC-SRV-1

1. Create a Print ShareCluster

a. In the left side pane of Failover Cluster Management console, clickServices andApplications.

b. In the right side pane, clickConfigure a Service or Application.c. The High Availability Wizard will appear. ClickNext.d. A list of available services and applications will appear. Select Print Server. Click

Next.

e. The Client Access Point screen will appear. In the Name field, typeHOL169PRINT

f. In the Address box, type 192.168.100.15. ClickNext.g. Click the checkbox next to the first available disk.h. Click Next twice, then clickFinish.i. Go to the folder: c:\windows\system32\spool\drivers\and notice that there is not

a GUID-identified folder.

j. Right-clickHOL169PRINT and select Move this service or application toanother node and select the other node. ClickYes to confirm.

k. Go back to the folder: c:\windows\system32\spool\drivers\\and noticethat the printer drivers are present there.


7/10


Page 5 of 8

Exercise 4Creating Failback Policies

ScenarioFailback is the process by which a workload, moved from its preferred server to another on the cluster due todowntime on the preferred server, moves back to its original server. This section will walk you through the steps to

configure this functionality.



task on:

NYC-SRV-1

1. Create FailbackPolicies for theCluster

a. In the left pane, right-clickHOL169FILE, and clickProperties.b. Click the box next to NYC-SRV-1 in the Preferred Owners field.c. Go to the Failover tab, select Allow Failback, and select Immediately. ClickOK.d. In the left pane, right-clickHOL169PRINT and clickProperties.e. Click the check box next to NYC-SRV-2 in the Preferred owners field.f. Go to the Failover tab and select Allow Failback and select Immediately. Click

OK.

g. Expand Nodes and right clickNYC-SRV-2, select More Actions, clickStopCluster Service. ClickYes to confirm.

h. ClickNYC-SRV-1 and notice that node 1 now owns all the Services andApplications.

i. Right clickNYC-SRV-2, select More Actions, clickStart Cluster Service.j. ClickNYC-SRV-2 and notice that HOL169PRINT is changed to node 2 as the

owner.

k. Stop the cluster service on NYC-SRV-1, and watch the services change ownershipto node 2. Please note that this could take a few minutes.

l. Start the cluster service on NODE1.Note:If you are disconnected from the cluster, right clickFailover Cluster

Management in the left column and selectManage a Cluster. Select

HOL169Cluster.woodgrovebank.com and clickOK. Then do step m above.


8/10


Page 6 of 8

Exercise 5Configuring Highly Available WINS

ScenarioIn this exercise, you will configure a highly available Windows Internet Naming Service (WINS). One of thescenarios that will be supported in Windows Server 2008 Enterprise Failover Clustering will be the capability to

provide a highly available WINS server. This section will walk you through configuring a 2-node Windows Server

2008 Enterprise WINS server. The cluster will be configured to provide a single, highly available WINS instance.

One of the restrictions on clustering the WINS service is that only one WINS service instance can be configured per

cluster. It is highly recommended that an additional WINS server on a standalone server or on another cluster be

configured for redundancy as needed.

Configure a highly-available WINS. In this section we configure a Client Access Point (CAP) which consists of a

NetBIOS name and the requisite number of IP addresses depending on how network access (Client Access) is

configured for the cluster networks. Here, there is only one network configured for client access. A storage resource

is required to host the WINS database which will be stored by one of the shared disks so it can be accessed by other

nodes in the cluster when the instance is failed over to another node in the cluster.



task on:

NYC-SRV-1

1. Configure HighlyAvailable WINS

a. On the Failover Clusters Manager console, in the left pane, expandHOL169CLUSTER clickServices and Applications.

b. In the right pane, select Configure a Service or Application and clickNext on theWelcome page of the wizard.

c. On the Select Service or Application page, scroll down and select WINS Server;clickNext.

d. On the Client Access Point page, type HOL169WINS in the Name text box. Enter192.168.100.16 in the Address field as the IP Address. ClickNext.

e. On the Select Storage page, select the first available disk and clickNext.f. On the Confirmation page, clickNext. It will take a short while for the wizard to

complete its configuration.

g. View the report, and notice that the WINS database and backup locations are onthe selected drive. After viewing the report, clickFinish.

h. The HOL169WINS service should now be online (if pending, wait a minute andit will change to online). In the center pane, notice which node owns this service.

Test failover: Right-clickHOL169WINS and select Move this service or

application to another node and select the other node. ClickYes on the Please

confirm action dialog. Confirm that ownership of HOL169WINS has changed to a

different node.

i. Refresh WINS registration on NYC-SRV-1: ClickStart, clickrun, and type cmd.From this command line, type nbtstat RR and press ENTER. This step isoptional on HOL169-NODE2.

Note:Manage WINS: In the left pane, click onHOL169WINS. In the right pane, click

onManage WINS. In the left pane, expandWINS, right-clickActive Registrations

and clickDisplay Records. ClickFind Now. Notice the records that are now

associated with the HOL169WINS failover service.


9/10


Page 7 of 8

Exercise 6Configuring Highly Available DHCP

ScenarioOne of the scenarios that will be supported in Windows Server 2008 Enterprise Failover Clustering will be thecapability to provide a highly available Dynamic Host Configuration Protocol (DHCP) server. This module will

walk you through configuring a 2-node Windows Server 2008 Enterprise DHCP server. The cluster will be

configured to provide a single, highly available DHCP instance. One of the restrictions on clustering the DHCP

service is that only one DHCP service instance can be configured per cluster. It is highly recommended that an

additional DHCP server on a standalone server or on another cluster be configured for redundancy as needed.

Configure a highly-available DHCP. It is important to note that a storage resource is required to host the DHCP

database which will be stored on the shared storage so it can be accessed by other nodes in the cluster as needed.



task on:

NYC-SRV-1

1. Configure HighlyAvailable DHCP

a. On the Failover Clusters Manager console, in the left pane, expandHOL169CLUSTER clickServices and Applications.

b. In the right pane, select Configure a Service or Application and clickNext on theWelcome page of the wizard.

c. On the Select Service or Application page, scroll down and select DHCP Server;clickNext.

d. On the Client Access Point page, type HOL169DHCP in the Name text box.Enter 192.168.100.17 in the Address field as the IP Address. ClickNext.

e. On the Select Storage page, select the first available disk. ClickNext.f. On the Confirmation page, clickNext. It will take a short while for the wizard to

complete its configuration.

g. View the report, and notice that the DHCP database and backup locations are onthe selected drive. After viewing the report, clickFinish.

h. The HOL169DHCP service should now be online (if pending, wait a minute andit will change to online). In the center pane, notice which node owns this service.

Test failover: In the left pane, right-clickHOL169DHCP and select Move this

service or application to another node and select the other node. ClickYes on

the Please confirm action dialog. Confirm that ownership of HOL169DHCP has

changed to a different node.

Note:Manage DHCP: In the left pane, click onHOL169DHCP. In the right pane,

click onManage DHCP. In the left pane, right-click

HOL169DHCP.Woodgrovebank.com and selectauthorize. It may take a minute to

for authorization to complete. The DHCP cluster can now be configured for scope,

scope options, etc.


10/10


Page 8 of 8

Exercise 7Bonus Section, Clustering Disks

Tasks Detailed StepsComplete the following

task on:

NYC-DC-1

NYC-SRV-1

NYC-SRV-2

1. Bonus Section,Clustering Disks

Note: This is a bonus extra lab suggestion for people interested in going beyond the

base lab. This lab will not contain step-by step instructions, but is merely a suggestion

for people interested in exploring clustering further. If you would like to play with

clustering some more on your own free time you may find this lab suggestion

interesting.

a. First, you must make the disk available for clustering. To do this, log in to domaincontroller (NYC-DC-1) and clickStart, and clickRun. Type iscsitarget.msc to

bring up the iSCSI target snap-in. Select devices. Right-clickVirtual Disk 5 and

select Assign/Remove Target. ClickAdd, then select iSCSI Resource and click

OK, then OK again. Here you have assigned a virtual disk to an iSCSI resource.

The clients that are already configured to access this will have also have access to

the new disk resource.

b. On NYC-SRV-1, open DiskMgmt.msc. You will notice there is a LUN that hasfree space listed and has not been clustered (most likely Disk 6). Go ahead and

partition and quick format the disk as drive U. Remember that all clustered disks

must be Basic disks and MBR. In the failover cluster manager, select storage on

the left, click the add disk on the right pane. This should bring up a box listing

available disks. Select the new disk, and clickOK. The disk is now part of the

cluster.

c. Create a new file server from Services and Applications, using the newly createddisk. When creation is complete, ensure the new file server is owned by NYC-

SRV-1.

d. Open up Windows Explorer and view the new disk, go ahead and create a test fileon it. Use Cluster Administrator to it over to node 2. You will see that the same

drive letter will be replicated to NYC-SRV-2. Also note how only one node ever

has access to a disk at any given time. Its not a production system, so play all you

want.

Windows Server 2008 Enterprise Fail Over Clustering Lab

Documents

Transcript of Windows Server 2008 Enterprise Fail Over Clustering Lab