Step-by-Step Guide for Configuring a Two-

Node Print Server Failover Cluster in

Windows Server 2008
Microsoft Corporation
Published: September 2007
Author: Jan Keller
Editor: Ronald oi
bstra!t
A failo!er cluster is a "roup of independent computers that #or$ to"ether to increase the
a!ailabilit% of applications and ser!ices& 'he clustered ser!ers (called nodes) are connected b%
ph%sical cables and b% soft#are& *f one of the cluster nodes fails+ another node be"ins to pro!ide
ser!ice (a process $no#n as failo!er)& 'his "uide describes the steps for installin" and
confi"urin" a print ser!er failo!er cluster that has t#o nodes& ,% creatin" the confi"uration in this
"uide+ %ou can learn about failo!er clusters and familiari-e %ourself #ith the .ailo!er Cluster
Mana"ement snap/in&
0
This is a preliminary document and may be changed substantially prior to final commercial
release of the software described herein. The information contained in this document represents
the current view of Microsoft Corporation on the issues discussed as of the date of publication.
Because Microsoft must respond to changing market conditions, it should not be interpreted to be
a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any
information presented after the date of publication.
This White Paper is for informational purposes only. MC!"#"$T M%&'# (" W%!!%(T'#,
')P!'##, MP*'+ "! #T%T,T"!-, %# T" T.' ($"!M%T"( ( T.# +"C,M'(T.
Complying with all applicable copyright laws is the responsibility of the user. Without limiting the
rights under copyright, no part of this document may be reproduced, stored in or introduced into a
retrieval system, or transmitted in any form or by any means /electronic, mechanical,
photocopying, recording, or otherwise0, or for any purpose, without the e1press written
permission of Microsoft Corporation.
Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual
property rights covering sub2ect matter in this document. '1cept as e1pressly provided in any
written license agreement from Microsoft, the furnishing of this document does not give you any
license to these patents, trademarks, copyrights, or other intellectual property.
3 4556 Microsoft Corporation. %ll rights reserved.
Microsoft, M#7+"#, Windows, Windows #erver, Windows 8ista, and %ctive +irectory are either
registered trademarks or trademarks of Microsoft Corporation in the ,nited #tates and9or other
countries.
%ll other trademarks are property of their respective owners.
2
Contents
Step/b%/Step 1uide for Confi"urin" a '#o/2ode Print Ser!er .ailo!er Cluster in 3indo#s Ser!er
2004&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& 0
Abstract&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& 0
Contents&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& 5
Step/b%/Step 1uide for Confi"urin" a '#o/2ode Print Ser!er .ailo!er Cluster in 3indo#s Ser!er
2004&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& 6
*n this "uide&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& 6
7!er!ie# for a t#o/node print ser!er cluster&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& 6
Re8uirements for a t#o/node failo!er cluster&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& 7
9ard#are re8uirements for a t#o/node failo!er cluster&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&7
:eplo%in" stora"e area net#or$s #ith failo!er clusters&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&4
Soft#are re8uirements for a t#o/node failo!er cluster&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&;
2et#or$ infrastructure and domain account re8uirements for a t#o/node failo!er cluster&&&&&00
Steps for installin" a t#o/node print ser!er cluster&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&00
Step 0: Connect the cluster ser!ers to the net#or$s and stora"e&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&00
Step 2: *nstall the failo!er cluster feature&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&02
Step 5: <alidate the cluster confi"uration&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&0=
Step =: Create the cluster&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& 0>
Steps for confi"urin" a t#o/node print ser!er cluster&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&07
Additional references&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& 20
5
Step-by-Step Guide for Configuring a Two-
Node Print Server Failover Cluster in
Windows Server 2008
A failo!er cluster is a "roup of independent computers that #or$ to"ether to increase the
a!ailabilit% of applications and ser!ices& 'he clustered ser!ers (called nodes) are connected b%
ph%sical cables and b% soft#are& *f one of the cluster nodes fails+ another node be"ins to pro!ide
ser!ice (a process $no#n as failo!er)& ?sers e@perience a minimum of disruptions in ser!ice&
'his "uide describes the steps for installin" and confi"urin" a print ser!er failo!er cluster that has
t#o nodes& ,% creatin" the confi"uration in this "uide+ %ou can learn about failo!er clusters and
familiari-e %ourself #ith the .ailo!er Cluster Mana"ement snap/in interface in
3indo#s Ser!erA 2004 Enterprise or 3indo#s Ser!erA 2004 :atacenter&
Note
'he failo!er cluster feature is not a!ailable in 3indo#s 3eb Ser!er 2004 or 3indo#s
Ser!er 2004 Standard&
*n 3indo#s Ser!er 2004+ the impro!ements to failo!er clusters (formerl% $no#n as ser!er
clusters) are aimed at simplif%in" clusters+ ma$in" them more secure+ and enhancin" cluster
stabilit%& Cluster setup and mana"ement are easier& Securit% and net#or$in" in clusters ha!e
been impro!ed+ as has the #a% a failo!er cluster communicates #ith stora"e& .or more
information about impro!ements to failo!er clusters+ see http:BB"o&microsoft&comBf#lin$BC
in$*dD>25>4&
"n t#is guide
7!er!ie# for a t#o/node print ser!er cluster
Re8uirements for a t#o/node failo!er cluster
Steps for installin" a t#o/node print ser!er cluster
Steps for confi"urin" a t#o/node print ser!er cluster
Additional resources
$verview for a two-node print server !luster
Ser!ers in a failo!er cluster can function in a !ariet% of roles+ includin" the roles of file ser!er+ print
ser!er+ mail ser!er+ or database ser!er+ and the% can pro!ide hi"h a!ailabilit% for a !ariet% of other
ser!ices and applications& 'his "uide describes ho# to confi"ure a t#o/node print ser!er cluster&
6
A failo!er cluster usuall% includes a stora"e unit that is ph%sicall% connected to all the ser!ers in
the cluster+ althou"h an% "i!en !olume in the stora"e is onl% accessed b% one ser!er at a time&
'he follo#in" dia"ram sho#s a t#o/node failo!er cluster connected to a stora"e unit&
Failover !luster wit# two nodes !onne!ted to a storage unit
Stora"e !olumes or lo"ical unit numbers (?2s) e@posed to the nodes in a cluster must not be
e@posed to other ser!ers+ includin" ser!ers in another cluster& 'he follo#in" dia"ram illustrates
this&
Two failover !lusters% ea!# wit# its own &'Ns
2ote that for the ma@imum a!ailabilit% of an% ser!er+ it is important to follo# best practices for
ser!er mana"ementEfor e@ample+ carefull% mana"in" the ph%sical en!ironment of the ser!ers+
>
testin" soft#are chan"es before full% implementin" them+ and carefull% $eepin" trac$ of soft#are
updates and confi"uration chan"es on all clustered ser!ers&
'he follo#in" scenario describes ho# a print ser!er failo!er cluster can be confi"ured&
(e)uire*ents for a two-node failover !luster
'o create a failo!er cluster #ith t#o nodes (re"ardless of the ser!ice or application that the nodes
pro!ide)+ %ou need the hard#are+ soft#are+ accounts+ and net#or$ infrastructure described in the
sections that follo#&
3e recommend that %ou first use the information pro!ided in this "uide in a test lab en!ironment&
A Step/b%/Step "uide is not necessaril% meant to be used to deplo% 3indo#s Ser!er features
#ithout the accompan%in" documentation (as listed in the Additional references section)+ and it
should be used #ith discretion as a stand/alone document&
+ardware re)uire*ents for a two-node failover !luster
Fou #ill need the follo#in" hard#are for a t#o/node failo!er cluster:
Servers: 3e recommend that %ou use a set of matchin" computers that contain the
same or similar components&
"*portant
Fou should use onl% hard#are components that are compatible #ith 3indo#s
Ser!er 2004&
Networ, adapters and !able -for networ, !o**uni!ation.: 'he net#or$ hard#are+
li$e other components in the failo!er cluster solution+ must be compatible #ith 3indo#s
Ser!er 2004& *f %ou use iSCS*+ %our net#or$ adapters must be dedicated to either net#or$
communication or iSCS*+ not both&
*n the net#or$ infrastructure that connects %our cluster nodes+ a!oid ha!in" sin"le points of
failure& 'here are multiple #a%s of accomplishin" this& Fou can connect %our cluster nodes b%
multiple+ distinct net#or$s& Alternati!el%+ %ou can connect %our cluster nodes #ith one net#or$
that is constructed #ith teamed net#or$ adapters+ redundant s#itches+ redundant routers+ or
similar hard#are that remo!es sin"le points of failure&
Note
*f %ou connect cluster nodes #ith a sin"le net#or$+ the net#or$ #ill pass the
redundanc% re8uirement in the <alidate a Confi"uration 3i-ard& 9o#e!er+ the report
from the #i-ard #ill include a #arnin" that the net#or$ should not ha!e sin"le points
of failure&
.or more details about the net#or$ confi"uration re8uired for a failo!er cluster+ see 2et#or$
infrastructure and domain account re8uirements for a t#o/node failo!er cluster+ later in this
topic&
7
/evi!e !ontrollers or appropriate adapters for t#e storage:
For Serial tta!#ed SCS" or Fibre C#annel: *f %ou are usin" Serial Attached SCS*
or .ibre Channel+ in all clustered ser!ers+ the mass/stora"e de!ice controllers that are
dedicated to the cluster stora"e should be identical& 'he% should also use the same
firm#are !ersion&
Note
3ith 3indo#s Ser!er 2004+ %ou cannot use parallel SCS* to connect the stora"e
to the clustered ser!ers&
For iSCS": *f %ou are usin" iSCS*+ each clustered ser!er must ha!e one or more
net#or$ adapters or host bus adapters that are dedicated to the cluster stora"e& 'he
net#or$ %ou use for iSCS* cannot be used for net#or$ communication& *n all clustered
ser!ers+ the net#or$ adapters %ou use to connect to the iSCS* stora"e tar"et should be
identical+ and #e recommend that %ou use 1i"abit Ethernet or hi"her&
.or iSCS*+ %ou cannot use teamed net#or$ adapters+ because the% are not supported
#ith iSCS*&
.or more information about iSCS*+ see the iSCS* .AG on the Microsoft 3eb site
(http:BB"o&microsoft&comBf#lin$BCin$*dD>0576)&
Storage: Fou must use shared stora"e that is compatible #ith 3indo#s Ser!er 2004&
.or a t#o/node failo!er cluster+ the stora"e should contain at least t#o separate !olumes
(?2s)+ confi"ured at the hard#are le!el& 7ne !olume #ill function as the #itness dis$
(described in the ne@t para"raph)& 7ne !olume #ill contain the print dri!ers+ print spooler
director%+ and print monitors& Stora"e re8uirements include the follo#in":
'o use the nati!e dis$ support included in failo!er clusterin"+ use basic dis$s+ not
d%namic dis$s&
3e recommend that %ou format the partitions #ith 2'.S (for the #itness dis$+ the
partition must be 2'.S)&
.or the partition st%le of the dis$+ %ou can use either master boot record (M,R) or
1?*: partition table (1P')&
'he #itness dis$ is a dis$ in the cluster stora"e that is desi"nated to hold a cop% of the
cluster confi"uration database& (A #itness dis$ is part of some+ not all+ 8uorum
confi"urations&) .or this t#o/node cluster+ the 8uorum confi"uration #ill be Node and /is,
0a1ority+ the default for a cluster #ith an e!en number of nodes& Node and /is, 0a1ority
means that the nodes and the #itness dis$ each contain copies of the cluster confi"uration+
and the cluster has 8uorum as lon" as a maHorit% (t#o out of three) of these copies are
a!ailable&
/eploying storage area networ,s wit# failover !lusters
3hen deplo%in" a stora"e area net#or$ (SA2) #ith a failo!er cluster+ follo# these "uidelines:
4
Confir* !o*patibility of t#e storage: Confirm #ith manufacturers and !endors that the
stora"e+ includin" dri!ers+ firm#are+ and soft#are used for the stora"e+ are compatible #ith
failo!er clusters in 3indo#s Ser!er 2004&
"*portant
Stora"e that #as compatible #ith ser!er clusters in 3indo#s Ser!er 2005 mi"ht not
be compatible #ith failo!er clusters in 3indo#s Ser!er 2004& Contact %our !endor to
ensure that %our stora"e is compatible #ith failo!er clusters in 3indo#s Ser!er 2004&
.ailo!er clusters include the follo#in" ne# re8uirements for stora"e:
,ecause impro!ements in failo!er clusters re8uire that the stora"e respond correctl%
to specific SCS* commands+ the stora"e must follo# the standard called SCS* Primar%
Commands/5 (SPC/5)& *n particular+ the stora"e must support Persistent Reser!ations as
specified in the SPC/5 standard&
'he miniport dri!er used for the stora"e must #or$ #ith the Microsoft Storport
stora"e dri!er&
"solate storage devi!es% one !luster per devi!e: Ser!ers from different clusters must
not be able to access the same stora"e de!ices& *n most cases+ a ?2 that is used for one
set of cluster ser!ers should be isolated from all other ser!ers throu"h ?2 mas$in" or
-onin"&
Consider using *ultipat# "2$ software: *n a hi"hl% a!ailable stora"e fabric+ %ou can
deplo% failo!er clusters #ith multiple host bus adapters b% usin" multipath *B7 soft#are& 'his
pro!ides the hi"hest le!el of redundanc% and a!ailabilit%& .or 3indo#s Ser!er 2004+ %our
multipath solution must be based on Microsoft Multipath *B7 (MP*7)& Four hard#are !endor
#ill usuall% suppl% an MP*7 de!ice/specific module (:SM) for %our hard#are+ althou"h
3indo#s Ser!er 2004 includes one or more :SMs as part of the operatin" s%stem&
"*portant
9ost bus adapters and multipath *B7 soft#are can be !er% !ersion sensiti!e& *f %ou
are implementin" a multipath solution for %our cluster+ %ou should #or$ closel% #ith
%our hard#are !endor to choose the correct adapters+ firm#are+ and soft#are for
3indo#s Ser!er 2004&
Software re)uire*ents for a two-node failover !luster
'he ser!ers for a t#o/node failo!er cluster must run the same !ersion of 3indo#s Ser!er 2004+
includin" the same hard#are !ersion (52/bit+ @>=/based+ or *tanium architecture/based)& 'he%
should also ha!e the same soft#are updates (patches) and ser!ice pac$s&
;
Networ, infrastru!ture and do*ain a!!ount re)uire*ents for a
two-node failover !luster
Fou #ill need the follo#in" net#or$ infrastructure for a t#o/node failo!er cluster and an
administrati!e account #ith the follo#in" domain permissions:
Networ, settings and "P addresses: 3hen %ou use identical net#or$ adapters for a
net#or$+ also use identical communication settin"s on those adapters (for e@ample+ Speed+
:uple@ Mode+ .lo# Control+ and Media '%pe)& Also+ compare the settin"s bet#een the
net#or$ adapter and the s#itch it connects to and ma$e sure that no settin"s are in conflict&
*f %ou ha!e pri!ate net#or$s that are not routed to the rest of %our net#or$ infrastructure+
ensure that each of these pri!ate net#or$s uses a uni8ue subnet& 'his is necessar% e!en if
%ou "i!e each net#or$ adapter a uni8ue *P address& .or e@ample+ if %ou ha!e a cluster node
in a central office that uses one ph%sical net#or$+ and another node in a branch office that
uses a separate ph%sical net#or$+ do not specif% 00&0&0&0B2= for both net#or$s+ e!en if %ou
"i!e each adapter a uni8ue *P address&
.or more information about the net#or$ adapters+ see 9ard#are re8uirements for a t#o/node
failo!er cluster+ earlier in this "uide&
/NS: 'he ser!ers in the cluster must be usin" :omain 2ame S%stem (:2S) for name
resolution& 'he :2S d%namic update protocol can be used&
/o*ain role: All ser!ers in the cluster must be in the same Acti!e :irector% domain& As a
best practice+ all clustered ser!ers should ha!e the same domain role (either member ser!er
or domain controller)& 'he recommended role is member ser!er&
/o*ain !ontroller: 3e recommend that %our clustered ser!ers be member ser!ers& *f
the% are+ %ou need an additional ser!er that acts as the domain controller in the domain that
contains %our failo!er cluster&
Clients: As needed for testin"+ %ou can connect one or more net#or$ed clients to the
failo!er cluster that %ou create+ and obser!e the effect on a client #hen %ou mo!e or fail o!er
the clustered print ser!er from one cluster node to the other&
!!ount for ad*inistering t#e !luster: 3hen %ou first create a cluster or add ser!ers
to it+ %ou must be lo""ed on to the domain #ith an account that has administrator ri"hts and
permissions on all ser!ers in that cluster& 'he account does not need to be a :omain Admins
account+ but can be a :omain ?sers account that is in the d*inistrators "roup on each
clustered ser!er& *n addition+ if the account is not a :omain Admins account+ the account (or
the "roup that the account is a member of) must be "i!en the Create Co*puter $b1e!ts
permission in the domain&
Note
'here is a chan"e in the #a% the Cluster ser!ice runs in 3indo#s Ser!er 2004+ as
compared to 3indo#s Ser!er 2005& *n 3indo#s Ser!er 2004+ there is no Cluster
ser!ice account& *nstead+ the Cluster ser!ice automaticall% runs in a special conte@t
00
that pro!ides the specific permissions and pri!ile"es that are necessar% for the
ser!ice (similar to the local s%stem conte@t+ but #ith reduced pri!ile"es)&
Steps for installing a two-node print server !luster
Fou must complete the follo#in" steps to install a t#o/node print ser!er failo!er cluster&
Step 0: Connect the cluster ser!ers to the net#or$s and stora"e
Step 2: *nstall the failo!er cluster feature
Step 5: <alidate the cluster confi"uration
Step =: Create the cluster
*f %ou ha!e alread% installed the cluster nodes and #ant to confi"ure a file ser!er failo!er cluster+
see Steps for confi"urin" a t#o/node file ser!er cluster+ later in this "uide&
Step 34 Conne!t t#e !luster servers to t#e networ,s and storage
?se the follo#in" instructions to connect %our selected cluster ser!ers to net#or$s and stora"e&
Note
Re!ie# 9ard#are Re8uirements for a '#o/2ode .ailo!er Cluster earlier in this "uide+ for
details about the $inds of net#or$ adapters and de!ice controllers that %ou can use #ith
3indo#s Ser!er 2004&
.or a failo!er cluster net#or$+ a!oid ha!in" sin"le points of failure& 'here are multiple #a%s of
accomplishin" this& Fou can connect %our cluster nodes b% multiple+ distinct net#or$s&
Alternati!el%+ %ou can connect %our cluster nodes #ith one net#or$ that is constructed #ith
teamed net#or$ adapters+ redundant s#itches+ redundant routers+ or similar hard#are that
remo!es sin"le points of failure (*f %ou use a net#or$ for iSCS*+ %ou must create this net#or$ in
addition to the other net#or$s)&
.or a t#o/node print ser!er cluster+ #hen %ou connect the ser!ers to the cluster stora"e+ %ou
must e@pose at least t#o !olumes (?2s)& Fou can e@pose additional !olumes as needed for
thorou"h testin" of %our confi"uration& :o not e@pose the clustered !olumes to ser!ers that are
not in the cluster&
To !onne!t t#e !luster servers to t#e networ,s and storage
0& Re!ie# the details about net#or$s in 9ard#are Re8uirements for a '#o/2ode
.ailo!er Cluster and 2et#or$ infrastructure and domain account re8uirements for a t#o/
node failo!er cluster+ earlier in this "uide&
2& Connect and confi"ure the net#or$s that the ser!ers in the cluster #ill use&
5& *f %our test confi"uration includes clients or a non/clustered domain controller+ ma$e
sure that these computers can connect to the clustered ser!ers throu"h at least one
net#or$&
00
=& .ollo# the manufacturerIs instructions for ph%sicall% connectin" the ser!ers to the
stora"e&
6& Ensure that the dis$s (?2s) that %ou #ant to use in the cluster are e@posed to the
ser!ers that %ou #ill cluster (and onl% those ser!ers)& Fou can use an% of the follo#in"
interfaces to e@pose dis$s or ?2s:
'he interface pro!ided b% the manufacturer of the stora"e&
*f %ou are usin" iSCS*+ an appropriate iSCS* interface&
Microsoft Stora"e Mana"er for SA2s (part of the operatin" s%stem in 3indo#s
Ser!er 2004)& 'o use this interface+ %ou need to contact the manufacturer of %our
stora"e for a <irtual :is$ Ser!ice (<:S) pro!ider pac$a"e that is desi"ned for %our
stora"e&
>& *f %ou ha!e purchased soft#are that controls the format or function of the dis$+ follo#
instructions from the !endor about ho# to use that soft#are #ith 3indo#s Ser!er 2004&
7& 7n one of the ser!ers that %ou #ant to cluster+ clic$ Start+ clic$ d*inistrative
Tools+ clic$ Co*puter 0anage*ent+ and then clic$ /is, 0anage*ent& (*f the 'ser
!!ount Control dialo" bo@ appears+ confirm that the action it displa%s is #hat %ou #ant+
and then clic$ Continue&) *n :is$ Mana"ement+ confirm that the cluster dis$s are !isible&
4& *f %ou #ant to ha!e a stora"e !olume lar"er than 2 terab%tes+ and %ou are usin" the
3indo#s interface to control the format of the dis$+ con!ert that dis$ to the partition st%le
called 1?*: partition table (1P')& 'o do this+ bac$ up an% data on the dis$+ delete all
!olumes on the dis$ and then+ in :is$ Mana"ement+ ri"ht/clic$ the dis$ (not a partition)
and clic$ Convert to GPT /is,&
.or !olumes smaller than 2 terab%tes+ instead of usin" 1P'+ %ou can use the partition
st%le called master boot record (M,R)&
"*portant
Fou can use either M,R or 1P' for a dis$ that is used b% a failo!er cluster+ but %ou cannot
use a dis$ that %ou con!erted to d%namic b% usin" :is$ Mana"ement&
*f %ou purchased soft#are that controls the format or function of the dis$+ contact the !endor
for instructions about ho# to use that soft#are #ith 3indo#s Ser!er 2004&
;& Chec$ the format of an% e@posed !olume or ?2& 3e recommend 2'.S for the
format (for the #itness dis$+ %ou must use 2'.S)&
Step 24 "nstall t#e failover !luster feature
*n this step+ %ou install the failo!er cluster feature& 'he ser!ers must be runnin" 3indo#s
Ser!er 2004&
02
To install t#e failover !luster feature on t#e servers
0& *f %ou recentl% installed 3indo#s Ser!er 2004+ the "nitial Configuration Tas,s
interface is displa%ed+ as sho#n in the follo#in" illustration&
"nitial Configuration Tas,s
*f this interface is displa%ed+ under Custo*i5e T#is Server+ clic$ dd features& 'hen
s$ip to step 5&
2& *f the "nitial Configuration Tas,s interface is not displa%ed and Ser!er Mana"er is
not runnin"+ clic$ Start+ clic$ d*inistrative Tools+ and then clic$ Server 0anager& (*f
the 'ser !!ount Control dialo" bo@ appears+ confirm that the action it displa%s is #hat
%ou #ant+ and then clic$ Continue&)
Server 0anager
05
*n Server 0anager+ under Features Su**ary+ clic$ dd Features&
5& *n the dd Features Wi5ard+ clic$ Failover Clustering+ and then clic$ "nstall&
=& .ollo# the instructions in the #i-ard to complete the installation of the feature& 3hen
the #i-ard finishes+ close it&
6& Repeat the process for each ser!er that %ou #ant to include in the cluster&
Step 64 7alidate t#e !luster !onfiguration
,efore creatin" a cluster+ #e stron"l% recommend that %ou !alidate %our confi"uration& <alidation
helps %ou confirm that the confi"uration of %our ser!ers+ net#or$+ and stora"e meets a set of
specific re8uirements for failo!er clusters&
To validate t#e failover !luster !onfiguration
0& 'o open the failo!er cluster snap/in+ clic$ Start+ clic$ d*inistrative Tools+ and then
clic$ Failover Cluster 0anage*ent& (*f the 'ser !!ount Control dialo" bo@ appears+
confirm that the action it displa%s is #hat %ou #ant+ and then clic$ Continue&)
Failover Cluster 0anage*ent snap-in
0=
2& Confirm that Failover Cluster 0anage*ent is selected and then+ in the center pane
under 0anage*ent+ clic$ 7alidate a Configuration&
7alidate a Configuration Wi5ard
06
5& .ollo# the instructions in the #i-ard to specif% the t#o ser!ers and the tests+ and then
run the tests& 'o full% !alidate %our confi"uration+ run all tests before creatin" a cluster&
=& 'he Su**ary pa"e appears after the tests run& 'o !ie# 9elp topics that #ill help %ou
interpret the results+ clic$ 0ore about !luster validation tests&
6& 3hile still on the Su**ary pa"e+ clic$ 7iew (eport and read the test results&
'o !ie# the results of the tests after %ou close the #i-ard+ see
#ystem!ootJClusterJReportsJ<alidation Report date and time&html
#here #ystem!oot is the folder in #hich the operatin" s%stem is installed (for e@ample+
C:J3indo#s)&
>& As necessar%+ ma$e chan"es in the confi"uration and rerun the tests&
7& 'o !ie# 9elp topics about cluster !alidation after %ou close the #i-ard+ in .ailo!er
Cluster Mana"ement+ clic$ +elp+ clic$ +elp Topi!s+ clic$ the Contents tab+ e@pand the
contents for the failo!er cluster 9elp+ and clic$ 7alidating a Failover Cluster
Configuration&
Step 84 Create t#e !luster
'o create a cluster+ %ou run the Create Cluster #i-ard&
0>
To run t#e Create Cluster wi5ard
0& 'o open the failo!er cluster snap/in+ clic$ Start+ clic$ d*inistrative Tools+ and then
clic$ Failover Cluster 0anage*ent& (*f the 'ser !!ount Control dialo" bo@ appears+
confirm that the action it displa%s is #hat %ou #ant+ and then clic$ Continue&)
2& Confirm that Failover Cluster 0anage*ent is selected and then+ in the center pane
under 0anage*ent+ clic$ Create a !luster&
Create Cluster Wi5ard
.ollo# the instructions in the #i-ard to specif%:
'he ser!ers to include in the cluster&
'he name of the cluster&
An% *P address information that is not automaticall% supplied b% %our :9CP
settin"s&
5& After the #i-ard runs and the Su**ary pa"e appears+ to !ie# a report of the tas$s
the #i-ard performed+ clic$ 7iew (eport&
Steps for !onfiguring a two-node print server
!luster
'o confi"ure a t#o/node print ser!er failo!er cluster+ follo# these steps:
07
To !onfigure a two-node print server failover !luster
0& 'o open the failo!er cluster snap/in+ clic$ Start+ clic$ d*inistrative Tools+ and then
clic$ Failover Cluster 0anage*ent& (*f the 'ser !!ount Control dialo" bo@ appears+
confirm that the action it displa%s is #hat %ou #ant+ and then clic$ Continue&)
2& *n the console tree+ if the cluster that %ou created is not displa%ed+ ri"ht/clic$ Failover
Cluster 0anage*ent+ clic$ 0anage a Cluster+ and then select the cluster %ou #ant to
confi"ure&
5& *n the console tree+ clic$ the plus si"n ne@t to the cluster that %ou created to e@pand
the items underneath it&
=& *f the clustered ser!ers are connected to a net#or$ that is not to be used for net#or$
communication in the cluster (for e@ample+ a net#or$ intended onl% for iSCS*)+ then under
Networ,s+ ri"ht/clic$ that net#or$+ clic$ Properties+ and then clic$ /o not allow t#e
!luster to use t#is networ,& Clic$ $9&
6& Clic$ Servi!es and ppli!ations& ?nder !tions (on the ri"ht)+ clic$ Configure a
Servi!e or ppli!ation&
+ig# vailability Wi5ard
>& Re!ie# the te@t on the first pa"e of the #i-ard+ and then clic$ Ne:t&
04
&ist of Servi!es and ppli!ations in t#e +ig# vailability Wi5ard
7& Clic$ Print Server+ and then clic$ Ne:t&
4& .ollo# the instructions in the #i-ard to specif% the follo#in" details:
A name for the clustered print ser!er
An% *P address information that is not automaticall% supplied b% %our :9CP
settin"sEfor e@ample+ a static *P!= address for this clustered print ser!er
'he stora"e !olume or !olumes that the clustered print ser!er should use
;& After the #i-ard runs and the Su**ary pa"e appears+ to !ie# a report of the tas$s
the #i-ard performed+ clic$ 7iew (eport&
00& 'o close the #i-ard+ clic$ Finis#&
00& *n the console tree+ ma$e sure Servi!es and ppli!ations is e@panded+ and then
select the clustered print ser!er that %ou Hust created&
02& ?nder !tions+ clic$ 0anage Printers&
An instance of the Failover Cluster 0anage*ent interface appears #ith Print
0anage*ent in the console tree&
05& ?nder Print 0anage*ent+ clic$ Print Servers and locate the clustered print ser!er
that %ou #ant to confi"ure&
Al#a%s perform mana"ement tas$s on the clustered print ser!er& :o not mana"e the
0;
dditional referen!es
'he follo#in" resources pro!ide additional information about failo!er clusters:
.or more information about iSCS*+ see the iSCS* .AG on the Microsoft 3eb site
(http:BB"o&microsoft&comBf#lin$BCin$*dD>0576)&
.or information about the impro!ements in failo!er clusters as compared to ser!er
clusters in 3indo#s Ser!er 2005+ see K3hatIs 2e# in .ailo!er ClustersK on the Microsoft
3eb site (http:BB"o&microsoft&comBf#lin$BCin$*dD>25>4)&
20