Cluster Configuration W2k3

Guide to Creating and Configuring a Server Cluster
under Windows Server 2003

By Elden Christensen
Microsoft Corporation
Published: November 11, 200
Abstract
This guide provides step-by-step instructions for creating and configuring a typical single quoru
device ulti-node server cluster using a shared dis! on servers running the "icrosoft# Windows#
Server 2003 $nterprise $dition and Windows Server 2003 %atacenter $dition operating systes&
Microsoft! "indo#s! $erver 200 "hite Paper
%his is a preliminary document and may be chan&ed substantially prior to
final commercial release of the soft#are described herein'
%he information contained in this document represents the current vie# of
Microsoft Corporation on the issues discussed as of the date of
publication' Because Microsoft must respond to chan&in& mar(et
conditions, it should not be interpreted to be a commitment on the part of
Microsoft, and Microsoft cannot &uarantee the accuracy of any
information presented after the date of publication'
%his document is for informational purposes only' M)C*+$+,% M-.E$
N+ "-**-N%)E$, E/P*E$$ +* )MP0)E1, -$ %+ %2E )N,+*M-%)+N
)N %2)$ 1+C3MEN%'
Complyin& #ith all applicable copyri&ht la#s is the responsibility of the
user' "ithout limitin& the ri&hts under copyri&ht, 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 4electronic, mechanical,
photocopyin&, recordin&, or other#ise5, or for any purpose, #ithout the
e6press #ritten permission of Microsoft Corporation'
Microsoft may have patents, patent applications, trademar(s, copyri&hts,
or other intellectual property ri&hts coverin& sub7ect matter in this
document' E6cept as e6pressly provided in any #ritten license a&reement
from Microsoft, the furnishin& of this document does not &ive you any
license to these patents, trademar(s, copyri&hts, or other intellectual
property'
8 200 Microsoft Corporation' -ll ri&hts reserved'
Microsoft, "indo#s, the "indo#s lo&o, "indo#s N%, and "indo#s
$erver are either re&istered trademar(s or trademar(s of Microsoft
Corporation in the 3nited $tates and9or other countries'
%he names of actual companies and products mentioned herein may be
the trademar(s of their respective o#ners'
Contents
Introduction............................................................................................................................................ 1
Checklists for Server Cluster Configuration:....................................................................................... 2
Software 'equireents&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& 2
(ardware 'equireents&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& 2
)etwor! 'equireents&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& 2
Shared %is! 'equireents*&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& 3
Cluster Installation................................................................................................................................. 5
+nstallation ,verview&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& -
+nstalling the Windows Server 2003 ,perating Syste&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&.
Setting /p )etwor!s&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& .
General )etwor! Configuration*&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& 0
Configuring the 1rivate )etwor! 2dapter&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& 3
Configuring the 1ublic )etwor! 2dapter&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& 42
5erifying Connectivity and )ae 'esolution&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& 42
5erifying %oain "ebership&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& 42
Setting /p a Cluster /ser 2ccount&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& 43
Setting up Shared %is!s&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& 4-
2bout the 6uoru %is!&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& 4-
Configuring the Cluster Service.......................................................................................................... 19
5alidating the Cluster +nstallation&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& 20
Configuring the Second )ode&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& 27
Post-Installation Configuration........................................................................................................... !
(eartbeat Configuration&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& 30
(eartbeat 2dapter 1rioriti8ation&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& 32
Configuring Cluster %is!s&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& 32
6uoru %is! Configuration&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& 33
Creating a 9oot %elay&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& 3:
"est Installation.................................................................................................................................... 5
Test ;ailover&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& 3-
iii
A##endi$............................................................................................................................................... %
2dvanced Testing&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& 30
SCS+ %rive +nstallations&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& 37
Configuring the SCS+ %evices&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& 37
Terinating the Shared SCS+ 9us&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& 37
Storage 2rea )etwor! Considerations&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& :0
/sing S2)s with Server Clusters&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& :4
&elated 'inks........................................................................................................................................ ()
iv
Introduction
2 server cluster is a group of independent servers wor!ing collectively and running the "icrosoft Cluster
Service <"SCS=& Server clusters provide high availability> failbac!> scalability> and anageability for
resources and applications
Server clusters allow client access to applications and resources in the event of failures and planned
outages& +f one of the servers in the cluster is unavailable because of a failure or aintenance
requireents> resources and applications ove to other available cluster nodes&
;or Windows Clustering solutions> the ter ?high availability@ is used rather than ?fault tolerant&@ ;ault-
tolerant technology offers a higher level of resilience and recovery& ;ault-tolerant servers typically use a
high degree of hardware redundancy plus speciali8ed software to provide near-instantaneous recovery fro
any single hardware or software fault& These solutions cost significantly ore than a Windows Clustering
solution because organi8ations ust pay for redundant hardware that waits in an idle state for a fault&
Server clusters do not guarantee non-stop operation> but they do provide sufficient availability for ost
ission-critical applications& The cluster service can onitor applications and resources and autoatically
recogni8e and recover fro any failure conditions& This provides fleAibility in anaging the wor!load
within a cluster& +t also iproves overall syste availability&
Cluster service benefits include*
*igh Availabilit+* With server clusters> ownership of resources such as dis! drives and +nternet
protocol <+1= addresses is autoatically transferred fro a failed server to a surviving server& When
a syste or application in the cluster fails> the cluster software restarts the failed application on a
surviving server> or disperses the wor! fro the failed node to the reaining nodes& 2s a result>
users eAperience only a oentary pause in service&
,ailback* The Cluster service will autoatically re-assign the wor!load in a cluster when a failed
server coes bac! online to its predeterined preferred owner& This feature can be configured> but
is disabled by default&
-anageabilit+* Bou can use the Cluster 2dinistrator tool <Clu2din&eAe= to anage a cluster as
a single syste and to anage applications as if they were running on a single server& Bou can
ove applications to different servers within the cluster& Cluster 2dinistrator can be used to
anually balance server wor!loads and to free servers for planned aintenance& Bou can also
onitor the status of the cluster> all nodes> and resources fro anywhere on the networ!&
Scalabilit+* Cluster services can grow to eet increased deand& When the overall load for a
cluster-aware application eAceeds the clusterCs capabilities> additional nodes can be added&
This docuent provides instructions for creating and configuring a server cluster with servers connected to
a shared cluster storage device and running Windows Server 2003 $nterprise $dition or Windows Server
2003 %atacenter $dition& +ntended to guide you through the process of installing a typical cluster> this
docuent does not eAplain how to install clustered applications& Windows Clustering solutions that
ipleent non-traditional quoru odels> such as "aDority )ode Set <")S= clusters and geographically
dispersed clusters> also are not discussed& ;or additional inforation about server cluster concepts as well
as installation and configuration procedures> see the Windows Server 2003 ,nline (elp&
Guide to Creating and Configuring a Server Cluster in Windows Server 2003 4
Checklists for Server Cluster Configuration:
This chec!list helps you prepare for installation& Step-by-step instructions begin after the chec!list&
Soft.are &e/uire0ents
"icrosoft Windows Server 2003 $nterprise $dition or Windows Server 2003 %atacenter $dition
installed on all coputers in the cluster&
2 nae resolution ethod such as %oain )ae Syste <%)S=> DNS dynamic update protocol>
Windows +nternet )ae Service <W+)S=> (,STS> and so on&
2n eAisting doain odel&
2ll nodes ust be ebers of the sae doain&
2 doain-level account that is a eber of the local adinistrators group on each node& 2 dedicated
account is recoended&
*ard.are &e/uire0ents
Clustering hardware ust be on the cluster service (ardware Copatibility Eist <(CE=& To find the latest
version of the cluster service (CE> go to the Windows (ardware Copatibility Eist at
http*FFwww&icrosoft&coFhclF> and then search for cluster& The entire solution ust be certified on the
(CE> not Dust the individual coponents& ;or additional inforation> see the following article in the
"icrosoft Gnowledge 9ase*
30333- The "icrosoft Support 1olicy for Server Clusters and the (ardware
1ote: +f you are installing this cluster on a storage area networ! <S2)= and plan to have ultiple devices
and clusters sharing the S2) with a cluster> the solution ust also be on the ?ClusterF"ulti-Cluster %evice@
(ardware Copatibility Eist& ;or additional inforation> see the following article in the "icrosoft Gnowledge
9ase*
30::4- Support for "ultiple Clusters 2ttached to the Sae S2) %evice
Two ass storage device controllersHSall Coputer Syste +nterface <SCS+= or ;ibre Channel& 2
local syste dis! for the operating syste <,S= to be installed on one controller& 2 separate peripheral
coponent interconnect <1C+= storage controller for the shared dis!s&
Two 1C+ networ! adapters on each node in the cluster&
Storage cables to attach the shared storage device to all coputers& 'efer to the anufacturers
instructions for configuring storage devices& See the appendiA that accopanies this article for additional
inforation on specific configuration needs when using SCS+ or ;ibre Channel&
2ll hardware should be identical> slot for slot> card for card> 9+,S> firware revisions> and so on> for all
nodes& This a!es configuration easier and eliinates copatibility probles&
1et.ork &e/uire0ents
2 unique )et9+,S nae&
Static +1 addresses for all networ! interfaces on each node&
1ote: Server Clustering does not support the use of +1 addresses assigned fro %ynaic (ost
Configuration 1rotocol <%(C1= servers&
2ccess to a doain controller& +f the cluster service is unable to authenticate the user account used to
start the service> it could cause the cluster to fail& +t is recoended that you have a doain controller
on the sae local area networ! <E2)= as the cluster is on to ensure availability&
$ach node ust have at least two networ! adaptersHone for connection to the client public networ!
and the other for the node-to-node private cluster networ!& 2 dedicated private networ! adapter is
required for (CE certification&
2ll nodes ust have two physically independent E2)s or virtual E2)s for public and private
counication&
+f you are using fault-tolerant networ! cards or networ! adapter teaing> verify that you are using the
ost recent firware and drivers& Chec! with your networ! adapter anufacturer for cluster
copatibility&
Shared 2isk &e/uire0ents:
2n (CE-approved eAternal dis! storage unit connected to all coputers& This will be used as the
clustered shared dis!& Soe type of a hardware redundant array of independent dis!s <'2+%= is
recoended&
2ll shared dis!s> including the quoru dis!> ust be physically attached to a shared bus&
1ote* The requireent above does not hold true for "aDority )ode Set <")S= clusters> which are not
covered in this guide&
Shared dis!s ust be on a different controller then the one used by the syste drive&
Creating ultiple logical drives at the hardware level in the '2+% configuration is recoended rather
than using a single logical dis! that is then divided into ultiple partitions at the operating syste level&
This is different fro the configuration coonly used for stand-alone servers& (owever> it enables you
to have ultiple dis! resources and to do 2ctiveF2ctive configurations and anual load balancing
across the nodes in the cluster&
2 dedicated dis! with a iniu si8e of -0 egabytes <"9= to use as the quoru device& 2 partition of
at least -00 "9 is recoended for optial )T;S file syste perforance&
5erify that dis!s attached to the shared bus can be seen fro all nodes& This can be chec!ed at the
host adapter setup level& 'efer to the anufacturerCs docuentation for adapter-specific instructions&
SCS+ devices ust be assigned unique SCS+ identification nubers and properly terinated according
to the anufacturerCs instructions& See the appendiA with this article for inforation on installing and
terinating SCS+ devices&
2ll shared dis!s ust be configured as basic dis!s& ;or additional inforation> see the following article
in the "icrosoft Gnowledge 9ase*
2307-3 %ynaic %is! Configuration /navailable for Server Cluster %is! 'esources
Software fault tolerance is not natively supported on cluster shared dis!s&
2ll shared dis!s ust be configured as aster boot record <"9'= dis!s on systes running the .:-bit
versions of Windows Server 2003&
2ll partitions on the clustered dis!s ust be foratted as )T;S&
(ardware fault-tolerant '2+% configurations are recoended for all dis!s&
2 iniu of two logical shared drives is recoended&
Guide to Creating and Configuring a Server Cluster in Windows Server 2003 :
Cluster Installation
Installation 3vervie.
%uring the installation process> soe nodes will be shut down while others are being installed& This step
helps guarantee that data on dis!s attached to the shared bus is not lost or corrupted& This can happen
when ultiple nodes siultaneously try to write to a dis! that is not protected by the cluster software& The
default behavior of how new dis!s are ounted has been changed in Windows 2003 Server fro the
behavior in the "icrosoft# Windows# 2000 operating syste& +n Windows 2003> logical dis!s that are not
on the sae bus as the boot partition will not be autoatically ounted and assigned a drive letter& This
helps ensure that the server will not ount drives that could possibly belong to another server in a copleA
S2) environent& 2lthough the drives will not be ounted> it is still recoended that you follow the
procedures below to be certain the shared dis!s will not becoe corrupted&
/se the table below to deterine which nodes and storage devices should be turned on during each step&
The steps in this guide are for a two-node cluster& (owever> if you are installing a cluster with ore than two
nodes> the )ode 2 colun lists the required state of all other nodes&
Ste#
Node
1
Node
2
Storage Comments
Setting up
networ!s
,n ,n ,ff
5erify that all storage devices on the shared
bus are turned off& Turn on all nodes&
Setting up shared
dis!s
,n ,ff ,n
Shutdown all nodes& Turn on the shared
storage> then turn on the first node&
5erifying dis!
configuration
,ff ,n ,n
Turn on the first node> turn on second node&
'epeat for nodes 3 and : if necessary&
Configuring the
first node
,n ,ff ,n Turn off all nodesI turn on the first node&
Configuring the
second node
,n ,n ,n
Turn on the second node after the first node is
successfully configured& 'epeat for nodes 3
and : as necessary&
1ost-installation ,n ,n ,n 2ll nodes should be on&
Several steps ust be ta!en before configuring the Cluster service software& These steps are*
+nstalling Windows Server 2003 $nterprise $dition or Windows Server 2003 %atacenter $dition
operating syste on each node&
Setting up networ!s&
Setting up dis!s&
1erfor these steps on each cluster node before proceeding with the installation of cluster service on the
first node&
Guide to Creating and Configuring a Server Cluster in Windows Server 2003 -
To configure the cluster service> you ust be logged on with an account that has adinistrative perissions
to all nodes& $ach node ust be a eber of the sae doain& +f you choose to a!e one of the nodes a
doain controller> have another doain controller available on the sae subnet to eliinate a single point
of failure and enable aintenance on that node&
Installing the 4indo.s Server 2!! 3#erating S+ste0
'efer to the docuentation you received with the Windows Server 2003 operating syste pac!age to install
the syste on each node in the cluster&
9efore configuring the cluster service> you ust be logged on locally with a doain account that is a
eber of the local adinistrators group&
1ote* The installation will fail if you attept to Doin a node to a cluster that has a blan! password for the
local adinistrator account& ;or security reasons> Windows Server 2003 prohibits blan! adinistrator
passwords&
Setting 5# 1et.orks
$ach cluster node requires at least two networ! adapters with two or ore independent networ!s> to avoid
a single point of failure& ,ne is to connect to a public networ!> and one is to connect to a private networ!
consisting of cluster nodes only& Servers with ultiple networ! adapters are referred to as ?ulti-hoed&@
9ecause ulti-hoed servers can be probleatic> it is critical that you follow the networ! configuration
recoendations outlined in this docuent&
"icrosoft requires that you have two 1eripheral Coponent +nterconnect (1C+= networ! adapters in each
node to be certified on the (ardware Copatibility Eist <(CE= and supported by "icrosoft 1roduct Support
Services& Configure one of the networ! adapters on your production networ! with a static +1 address> and
configure the other networ! adapter on a separate networ! with another static +1 address on a different
subnet for private cluster counication&
Counication between server cluster nodes is critical for sooth cluster operations& Therefore> you ust
configure the networ!s that you use for cluster counication are configured optially and follow all
hardware copatibility list requireents&
The private networ! adapter is used for node-to-node counication> cluster status inforation> and cluster
anageent& $ach nodeCs public networ! adapter connects the cluster to the public networ! where clients
reside and should be configured as a bac!up route for internal cluster counication& To do so> configure
the roles of these networ!s as either JInternal Cluster Co00unications 3nl+J or JAll Co00unicationsJ
for the Cluster service&
2dditionally> each cluster networ! ust fail independently of all other cluster networ!s& This eans that two
cluster networ!s ust not have a coponent in coon that can cause both to fail siultaneously& ;or
eAaple> the use of a ultiport networ! adapter to attach a node to two cluster networ!s would not satisfy
this requireent in ost cases because the ports are not independent&
To eliinate possible counication issues> reove all unnecessary networ! traffic fro the networ!
adapter that is set to Internal Cluster co00unications onl+ <this adapter is also !nown as the heartbeat
or private networ! adapter=&
To verify that all networ! connections are correct> private networ! adapters ust be on a networ! that is on
a different logical networ! fro the public adapters& This can be accoplished by using a cross-over cable
Guide to Creating and Configuring a Server Cluster in Windows Server 2003 .
in a two-node configuration or a dedicated dub hub in a configuration of ore than two nodes& %o not use
a switch> sart hub> or any other routing device for the heartbeat networ!&
1ote* Cluster heartbeats cannot be forwarded through a routing device because their Tie to Eive <TTE= is
set to 4& The public networ! adapters ust be only connected to the public networ!& +f you have a virtual
E2)> then the latency between the nodes ust be less then -00 illiseconds <s=& 2lso> in Windows Server
2003> heartbeats in Server Clustering have been changed to ulticastI therefore> you ay want to a!e a
"adcap server available to assign the ulticast addresses& ;or additional inforation> see the following
article in the "icrosoft Gnowledge 9ase*
3003.2 "ulticast Support $nabled for the Cluster (eartbeat
Figure 1 below outlines a four-node cluster configuration.

,i&ure 1' Connections for a four:node cluster'
6eneral 1et.ork Configuration:
1ote* This guide assues that you are running the default Start enu& The steps ay be slightly different if
you are running the Classic Start enu& 2lso> which networ! adapter is private and which is public depends
upon your wiring& ;or the purposes of this white paper> the first networ! adapter <Eocal 2rea Connection= is
connected to the public networ!> and the second networ! adapter <Eocal 2rea Connection 2= is connected
to the private cluster networ!& Bour networ! ay be different&

To rename the local area network icons
+t is recoended that you change the naes of the networ! connections for clarity& ;or eAaple> you
ight want to change the nae of 0ocal -rea Connection 2 to soething li!e Private& 'enaing will help
you identify a networ! and correctly assign its role&
1.Clic! Start> point to Control Panel> right-clic! 1et.ork Connections> and then clic! 3#en
2.'ight-clic! the 'ocal Area Connection 2 icon&
3.Clic! &ena0e&
4.Type Private in the teAtboA> and then press $)T$'&
5.'epeat steps 4 through 3> and then renae the public networ! adapter as Public&
,i&ure 2' *enamed icons in the Net#or( Connections #indo#'
6.The renaed icons should loo! li!e those in ;igure 2 above& Close the )etwor! Connections window&
The new connection naes will appear in Cluster 2dinistrator and autoatically replicate to all
other cluster nodes as they are brought online&
To configure the binding order networks on all nodes
1.Clic! Start> point to Control Panel> right-clic! 1et.ork Connections> and then clic! 3#en
2.,n the Advanced enu> clic! Advanced Settings&
3.+n the Connections boA> a!e sure that your bindings are in the following order> and then clic! 37*
a= 1ublic
b= 1rivate
c= 'eote 2ccess Connections

Configuring the Private 1et.ork Ada#ter
1. 'ight-clic! the networ! connection for your heartbeat adapter> and then clic! Pro#erties&
2. ,n the 6eneral tab> a!e sure that only the Internet Protocol 8"CP9IP: chec! boA is selected> as
shown in ;igure 3 below& Clic! to clear the chec! boAes for all other clients> services> and protocols&
,i&ure ' Clic( to select only the Internet Protocol chec( bo6 in the Private Properties dialo& bo6'
. +f you have a networ! adapter that is capable of transitting at ultiple speeds> you should
anually specify a speed and dupleA ode& %o not use an auto-select setting for speed>
because soe adapters ay drop pac!ets while deterining the speed& The speed for the
networ! adapters ust be hard set <anually set= to be the sae on all nodes according to the
card anufacturerKs specification& +f you are not sure of the supported speed of your card and
connecting devices> "icrosoft recoends you set all devices on that path to 1! 0egab+tes
#er second <"bps= and *alf 2u#le$> as shown in ;igure : below& The aount of inforation
that is traveling across the heartbeat networ! is sall> but latency is critical for counication&
This configuration will provide enough bandwidth for reliable counication& 2ll networ!
adapters in a cluster attached to the sae networ! ust be configured identically to use the
sae 2u#le$ -ode> 'ink S#eed; ,lo. Control> and so on& Contact your adapterKs
anufacturer for specific inforation about appropriate speed and dupleA settings for your
networ! adapters&

,i&ure ;' $ettin& the speed and duple6 for all adaptors
1ote* "icrosoft does not recoended that you use any type of fault-tolerant adapter or JTeaingJ for the
heartbeat& +f you require redundancy for your heartbeat connection> use ultiple networ! adapters set to
+nternal Counication ,nly and define their networ! priority in the Cluster configuration& +ssues seen with
early ulti-ported networ! adapters> verify that your firware and driver are at the ost current revision if
you use this technology&
Contact your networ! adapter anufacturer for inforation about copatibility on a server cluster& ;or
additional inforation> see the following article in the "icrosoft Gnowledge 9ase*
2-:404 )etwor! 2dapter Teaing and Server Clustering
(. Clic! Internet Protocol 8"CP9IP:> and then clic! Pro#erties&
5. ,n the 6eneral tab> verify that you have selected a static +1 address that is not on the sae
subnet or networ! as any other public networ! adapter& +t is recoended that you put the
private networ! adapter in one of the following private networ! ranges*
40&0&0&0 through 40&2--&2--&2-- <Class 2=
402&4.&0&0 through 402&34&2--&2-- <Class 9=
432&4.7&0&0 through 432&4.7&2--&2-- <Class C=
2n eAaple of a good +1 address to use for the private adapters is 40&40&40&40 on node 4 and
40&40&40&44 on node 2 with a subnet as! of 2--&0&0&0> as shown in ;igure - below& 9e sure that
this is a copletely different +1 address schee then the one used for the public networ!&
1ote* ;or additional inforation about valid +1 addressing for a private networ!> see the following article in
the "icrosoft Gnowledge 9ase*
4:27.3 5alid +1 2ddressing for a 1rivate )etwor!
,i&ure <' -n e6ample of an )P address to use for private adapters'
). 5erify that there are no values defined in the 2efault 6ate.a+ boA or under 5se the
,ollo.ing 21S server addresses&
%. Clic! the Advanced button&
<. ,n the 21S tab> verify that no values are defined& "a!e sure that the &egister this
connection=s addresses in 21S and 5se this connection=s 21S suffi$ in 21S registration
chec! boAes are cleared&
9. ,n the 4I1S tab> verify that there are no values defined& Clic! 2isable 1et>I3S over "CP9IP
as shown in ;igure . on the neAt page&
,i&ure =' >erify that no values are defined on the ")N$ tab'
1!. When you close the dialog boA> you ay receive the following propt* ?%his connection has an
empty primary ")N$ address' 1o you #ant to continue?@ +f you receive this propt> clic! ?es
11. Coplete steps 4 through 40 on all other nodes in the cluster with different static +1 addresses&
Configuring the Public 1et.ork Ada#ter
1ote* +f +1 addresses are obtained via %(C1> access to cluster nodes ay be unavailable if the %(C1
server is inaccessible& ;or this reason> static +1 addresses are required for all interfaces on a server cluster&
Geep in ind that cluster service will only recogni8e one networ! interface per subnet& +f you need
assistance with TC1F+1 addressing in Windows Server 2003> please see the ,nline (elp&
@erif+ing Connectivit+ and 1a0e &esolution
To verify that the private and public networ!s are counicating properly> ping all +1 addresses fro each
node& Bou should be able to ping all +1 addresses> locally and on the reote nodes&
To verify nae resolution> ping each node fro a client using the nodeCs achine nae instead of its +1
address& +t should only return the +1 address for the public networ!& Bou ay also want to try a PI16 Aa
coand to do a reverse loo!up on the +1 2ddresses&
@erif+ing 2o0ain -e0bershi#
2ll nodes in the cluster ust be ebers of the sae doain and be able to access a doain controller
and a %)S server& They can be configured as eber servers or doain controllers& Bou should have at
least one doain controller on the sae networ! segent as the cluster& ;or high availability& another
doain controller should also be available to reove a single point of failure& +n this guide> all nodes are
configured as eber servers&
There are instances where the nodes ay be deployed in an environent where there are no pre-eAisting
"icrosoft# Windows )T# :&0 doain controllers or Windows Server 2003 doain controllers& This
scenario requires at least one of the cluster nodes to be configured as a doain controller& (owever> in a
two-node server cluster> if one node is a doain controller> then the other node also ust be a doain
controller& +n a four-node cluster ipleentation> it is not necessary to configure all four nodes as doain
controllers& (owever> when following a ?best practices@ odel and having at least one bac!up doain
controller> at least one of the reaining three nodes should be configured as a doain controller& 2 cluster
node ust be prooted to a doain controller by using the %C1roo tool before the cluster service is
configured&
The dependence in Windows Server 2003 on the %)S further requires that every node that is a doain
controller also ust be a %)S server if another %)S server that supports dynaic updates andFor S'5
records is not available <2ctive directory integrated 8ones recoended=&
The following issues should be considered when deploying cluster nodes as doain controllers*
+f one cluster node in a two-node cluster is a doain controller> the other node ust be a doain
controller
There is overhead associated with running a doain controller& 2n idle doain controller can use
anywhere between 430 and 4:0 "9 of '2"> which includes having the Clustering service running&
There is also increased networ! traffic fro replication> because these doain controllers have to
replicate with other doain controllers in the doain and across doains&
+f the cluster nodes are the only doain controllers> then each ust be a %)S server as well& They
should point to each other for priary %)S resolution and to theselves for secondary resolution&
The first doain controller in the forestFdoain will ta!e on all ,perations "aster 'oles& Bou can
redistribute these roles to any node& (owever> if a node fails> the ,perations "aster 'oles assued by
that node will be unavailable& Therefore> it is recoended that you do not run ,perations "aster
'oles on any cluster node& This includes Schee "aster> %oain )aing "aster> 'elative +% "aster>
1%C $ulator> and +nfrastructure "aster& These functions cannot be clustered for high availability with
failover&
Clustering other applications such as "icrosoft# S6E Server L or "icrosoft# $Achange Server in a
scenario where the nodes are also doain controllers ay not be optial due to resource constraints&
This configuration should be thoroughly tested in a lab environent before deployent
9ecause of the copleAity and overhead involved in a!ing cluster-nodes doain controllers> it is
recoended that all nodes should be eber servers&
Setting 5# a Cluster 5ser Account
The Cluster service requires a doain user account that is a eber of the Eocal 2dinistrators group on
each node> under which the Cluster service can run& 9ecause setup requires a user nae and password>
this user account ust be created before configuring the Cluster service& This user account should be
dedicated only to running the Cluster service> and should not belong to an individual&
1ote* The cluster service account does not need to be a eber of the %oain 2dinistrators group& ;or
security reasons> granting doain adinistrator rights to the cluster service account is not recoended&
The cluster service account requires the following rights to function properly on all nodes in the cluster& The
Cluster Configuration Wi8ard grants the following rights autoatically*
2ct as part of the operating syste
2dDust eory quotas for a process
9ac! up files and directories
+ncrease scheduling priority
Eog on as a service
'estore files and directories
;or additional inforation> see the following article in the "icrosoft Gnowledge 9ase*
2.3223 (ow to "anually 'e-Create the Cluster Service 2ccount
To set up a cluster user account
1.Clic! Start> point to All Progra0s> point to Ad0inistrative "ools> and then clic! Active 2irector+
5sers and Co0#uters&
2.Clic! the plus sign <M= to eApand the doain if it is not already eApanded&
3.'ight-clic! 5sers> point to 1e.> and then clic! 5ser&
4.Type the cluster nae> as shown in ;igure 0 below> and then clic! 1e$t&
,i&ure @' %ype the cluster name'
Guide to Creating and Configuring a Server Cluster in Windows Server 2003 4:
5.Set the password settings to 5ser Cannot Change Pass.ord and Pass.ord 1ever B$#ires& Clic!
1e$t; and then clic! ,inish to create this user&
1ote* +f your adinistrative security policy does not allow the use of passwords that never eApire> you ust
renew the password and update the cluster service configuration on each node before password eApiration&
30-743 (ow to Change the Cluster Service 2ccount 1assword
6.'ight-clic! Cluster in the left pane of the 2ctive %irectory /sers and Coputers snap-in> and then
clic! Pro#erties on the shortcut enu&
7.Clic! Add -e0bers to a 6rou#&
8.Clic! Ad0inistrators; and then clic! 37& This gives the new user account adinistrative privileges
on this coputer&
9.6uit the 2ctive %irectory /sers and Coputers snap-in&
Setting u# Shared 2isks
4arning* To avoid corrupting the cluster dis!s> a!e sure that Windows Server 2003 and the Cluster
service are installed> configured> and running on at least one node before you start an operating syste on
another node& +t is critical to never have ore then one node on until the Cluster service is configured&
To proceed> turn off all nodes& Turn on the shared storage devices> and then turn on node 4&
About the Cuoru0 2isk
The quoru dis! is used to store cluster configuration database chec!points and log files that help anage
the cluster and aintain consistency& The following quoru dis! procedures are recoended*
Create a logical drive with a iniu si8e of -0 "9 to be used as a quoru dis!> -00 "9 is optial for
)T;S&
%edicate a separate dis! as a quoru resource&
I0#ortant* 2 quoru dis! failure could cause the entire cluster to failI therefore> it is strongly recoended
that you use a volue on a hardware '2+% array& %o not use the quoru dis! for anything other than
cluster anageent&
The quoru resource plays a crucial role in the operation of the cluster& +n every cluster> a single resource is
designated as the quoru resource& 2 quoru resource can be any 1hysical %is! resource with the
following functionality*
+t replicates the cluster registry to all other nodes in the server cluster& 9y default> the cluster
registry is stored in the following location on each node* A$ystem*ootABClusterBClusdb& The
cluster registry is then replicated to the M$C$BCh(666'tmp file on the quoru drive& These files are
eAact copies of each other& The M$C$BCuolo&'lo& file is a transaction log that aintains a record of
all changes to the chec!point file& This eans that nodes that were offline can have these changes
appended when they reDoin the cluster&
Guide to Creating and Configuring a Server Cluster in Windows Server 2003 4-
+f there is a loss of counication between cluster nodes> the challenge response protocol is
initiated to prevent a Jsplit brainJ scenario& +n this situation> the owner of the quoru dis! resource
becoes the only owner of the cluster and all the resources& The owner then a!es the resources
available for clients& When the node that owns the quoru dis! functions incorrectly> the surviving
nodes arbitrate to ta!e ownership of the device& ;or additional inforation> see the following article
in the "icrosoft Gnowledge 9ase*
30347. (ow the Cluster Service Ta!es ,wnership of a %is! on the Shared 9us
%uring the cluster service installation> you ust provide the drive letter for the quoru dis!& The letter C is
coonly used as a standard> and 6 is used in the eAaple&
To configure shared disks
1."a!e sure that only one node is turned on&
2.'ight clic! -+ Co0#uter> clic! -anage> and then eApand Storage&
3.%ouble-clic! 2isk -anage0ent&
4.+f you connect a new drive> then it autoatically starts the Write Signature and /pgrade %is! Wi8ard&
+f this happens> clic! 1e$t to step through the wi8ard&
1ote* The wi8ard autoatically sets the dis! to dynaic& To reset the dis! to basic> right-clic! 2isk n <where
n specifies the dis! that you are wor!ing with=> and then clic! &evert to >asic 2isk&
5. 'ight-clic! unallocated disk s#ace&
6. Clic! 1e. Partition&
7. The )ew 1artition Wi8ard begins& Clic! 1e$t&
8. Select the Pri0ar+ Partition partition type& Clic! 1e$t&
9. The default is set to aAiu si8e for the partition si8e& Clic! 1e$t& <"ultiple logical dis!s are
recoended over ultiple partitions on one dis!&=
10. /se the drop-down boA to change the drive letter& /se a drive letter that is farther down the
alphabet than the default enuerated letters& Coonly> the drive letter C is used for the quoru
dis!> then '> S>and so on for the data dis!s& ;or additional inforation> see the following article in
the "icrosoft Gnowledge 9ase*
347-3: 9est 1ractices for %rive-Eetter 2ssignents on a Server Cluster
1ote* +f you are planning on using volue ount points> do not assign a drive letter to the dis!& ;or
additional inforation> see the following article in the "icrosoft Gnowledge 9ase*
270230 (ow to Configure 5olue "ount 1oints on a Clustered Server
11. ;orat the partition using )T;S& +n the @olu0e 'abel boA> type a nae for the dis!& ;or eAaple>
2rive C> as shown in ;igure 7 below& +t is critical to assign drive labels for shared dis!s> because
this can draatically reduce troubleshooting tie in the event of a dis! recovery situation&
Guide to Creating and Configuring a Server Cluster in Windows Server 2003 4.
,i&ure D' )t is critical to assi&n drive labels for shared dis(s'
+f you are installing a .:-bit version of Windows Server 2003> verify that all dis!s are foratted as "9'&
Global 1artition Table <G1T= dis!s are not supported as clustered dis!s& ;or additional inforation> see the
following article in the "icrosoft Gnowledge 9ase*
27:43: Server Clusters %o )ot Support G1T Shared %is!s
5erify that all shared dis!s are foratted as )T;S and designated as "9' 9asic&

To verify disk access and functionality
1.Start Windows $Aplorer&
2.'ight-clic! one of the shared dis!s <such as 2rive C:D=> clic! 1e.; and then clic! "e$t 2ocu0ent&
3.5erify that you can successfully write to the dis! and that the file was created&
4.Select the file> and then press the 2el !ey to delete it fro the clustered dis!&
5.'epeat steps 4 through : for all clustered dis!s to verify they can be correctly accessed fro the first
node&
6.Turn off the first node> turn on the second node> and repeat steps 4 through : to verify dis! access and
functionality& 2ssign drive letters to atch the corresponding drive labels& 'epeat again for any
additional nodes& 5erify that all nodes can read and write fro the dis!s> turn off all nodes eAcept the
first one> and then continue with this white paper&
Configuring the Cluster Service
Bou ust supply all initial cluster configuration inforation in the first installation phase& This is
accoplished using the Cluster Configuration Wi8ard&
2s seen in the flow chart> the for <Create a new Cluster= and the Noin <2dd nodes= ta!e a couple different
paths> but they have a few of the sae pages& )aely> Credential Eogin> 2naly8e> and 'e-2naly8e and
Start Service are the sae& There are inor differences in the following pages* Welcoe> Select Coputer>
and Cluster Service 2ccount& +n the neAt two sections of this lesson> you will step through the wi8ard pages
presented on each of these configuration paths& +n the third section> after you follow the step-through
sections> this white paper describes in detail the 2naly8e> >'e-2naly8e and Start Service pages> and what
the inforation provided in these screens eans&
1ote* %uring Cluster service configuration on node 4> you ust turn off all other nodes& 2ll shared storage
devices should be turned on&
To configure the first node
1.Clic! Start> clic! All Progra0s> clic! Ad0inistrative "ools> and then clic! Cluster Ad0inistrator&
2.When propted by the ,pen Connection to Cluster Wi8ard> clic! Create ne. cluster in the Action
drop-down list> as shown in ;igure 3 below&
,i&ure E' %he Action drop:do#n list'
3.5erify that you have the necessary prerequisites to configure the cluster> as shown in ;igure 40
below& Clic! 1e$t&
,i&ure 10' - list of prereFuisites is part of the Ne# $erver Cluster "iGard "elcome pa&e'

4.Type a unique )et9+,S nae for the cluster <up to 4- characters=> and then clic! 1e$t& +n the
eAaple shown in ;igure 44 below> the cluster is naed -+Cluster&= 2dherence to %)S naing
rules is recoended& ;or additional inforation> see the following articles in the "icrosoft
Gnowledge 9ase*
4.3:03 )et9+,S SuffiAes <4.th Character of the )et9+,S )ae=
2-:.70 %)S )aespace 1lanning
,i&ure 11' -dherence to 1N$ namin& rules is recommended #hen namin& the cluster'
5.+f you are logged on locally with an account that is not a 2o0ain Account .ith 'ocal
Ad0inistrative #rivileges> the wi8ard will propt you to specify an account& This is not the
account the Cluster service will use to start&
1ote* +f you have appropriate credentials> the propt entioned in step - and shown in ;igure 42 below
ay not appear&

,i&ure 12' %he Ne# $erver Cluster "iGard prompts you to specify an account'
6.9ecause it is possible to configure clusters reotely> you ust verify or type the nae of the server
that is going to be used as the first node to create the cluster> as shown in ;igure 43 below& Clic!
1e$t&
,i&ure 1' $elect the name of the computer that #ill be the first node in the cluster'

1ote* The +nstall wi8ard verifies that all nodes can see the shared dis!s the sae& +n a copleA storage
area networ! the target identifiers <T+%s= for the dis!s ay soeties be different> and the Setup progra
ay incorrectly detect that the dis! configuration is not valid for Setup& To wor! around this issue you can
clic! the Advanced button> and then clic! Advanced 80ini0u0: configuration& ;or additional
inforation> see the following article in the "icrosoft Gnowledge 9ase*
334704 Cluster Setup "ay )ot Wor! When Bou 2dd )odes
7.;igure 4: below illustrates that the Setup process will now analy8e the node for possible hardware or
software probles that ay cause probles with the installation& 'eview any warnings or error
essages& Bou can also clic! the 2etails button to get detailed inforation about each one&
,i&ure 1;' %he $etup process analyGes the node for possible hard#are or soft#are problems'

8.Type the unique cluster +1 address <in this eAaple 402&2.&20:&40=> and then clic! 1e$t&
2s shown in ;igure 4- below> the )ew Server Cluster Wi8ard autoatically associates the cluster +1
address with one of the public networ!s by using the subnet as! to select the correct networ!& The cluster
+1 address should be used for adinistrative purposes only> and not for client connections&
,i&ure 1<' %he Ne# $erver Cluster "iGard automatically associates the cluster )P address #ith one of the
public net#or(s'
9.Type the user na0e and #ass.ord of the cluster service account that was created during pre-
installation& <+n the eAaple in ;igure 4. below> the user nae is ?Cluster@=& Select the doain
nae in the 2o0ain drop-down list> and then clic! 1e$t&
2t this point> the Cluster Configuration Wi8ard validates the user account and password&

,i&ure 1=' %he #iGard prompts you to provide the account that #as created durin& pre:installation'
10. 'eview the Su00ar+ page> shown in ;igure 40 below> to verify that all the inforation that is about
to be used to create the cluster is correct& +f desired> you can use the quoru button to change the
quoru dis! designation fro the default auto-selected dis!&
The suary inforation displayed on this screen can be used to reconfigure the cluster in the event of
a disaster recovery situation& +t is recoended that you save and print a hard copy to !eep with the
change anageent log at the server&
1ote* The Cuoru0 button can also be used to specify a "aDority )ode Set <")S= quoru odel& This is
one of the aDor configuration differences when you create an ")S cluster

,i&ure 1@' %he Proposed Cluster Confi&uration pa&e'
11. 'eview any warnings or errors encountered during cluster creation& To do this> clic! the plus signs
to see ore> and then clic! 1e$t& Warnings and errors appear in the Creating the Cluster page as
shown in ;igure 47&
,i&ure 1D' "arnin&s and errors appear on the Creatin& the Cluster pa&e'

12. Clic! ,inish to coplete the installation& ;igure 43 below illustrates the final step&
,i&ure 1E' %he final step in settin& up a ne# server cluster'
1ote* To view a detailed suary> clic! the @ie. 'og button or view the teAt file stored in the following
location*
%SystemRoot%\System32\LogFiles\Cluster\ClCfgSrv.Log

@alidating the Cluster Installation
/se the Cluster 2dinistrator <Clu2din&eAe= to validate the cluster service installation on node 4&
To validate the cluster installation
1.Clic! Start> clic! Progra0s> clic! Ad0inistrative "ools> and then clic! Cluster Ad0inistrator&
2.5erify that all resources cae online successfully> as shown in ;igure 20 below&

,i&ure 20' %he Cluster -dminister verifies that all resources came online successfully'
1ote 2s general rules> do not put anything in the cluster group> do not ta!e anything out of the cluster
group> and do not use anything in the cluster group for anything other than cluster adinistration&
Configuring the Second 1ode
+nstalling the cluster service on the other nodes requires less tie than on the first node& Setup configures
the cluster service networ! settings on the second node based on the configuration of the first node& Bou
can also add ultiple nodes to the cluster at the sae tie> and reotely&
1ote* ;or this section> leave node 4 and all shared dis!s turned on& Then turn on all other nodes& The
cluster service will control access to the shared dis!s at this point to eliinate any chance of corrupting the
volue&
1.,pen Cluster Ad0inistrator on )ode 4&
2.Clic! ,ile> clic! 1e.> and then clic! 1ode&
3.The 2dd Cluster Coputers Wi8ard will start& Clic! 1e$t&
4.+f you are not logged on with appropriate credentials> you will be as!ed to specify a doain account
that has adinistrative rights over all nodes in the cluster&
5.$nter the achine nae for the node you want to add to the cluster& Clic! Add& 'epeat this step>
shown in ;igure 24 below> to add all other nodes that you want& When you have added all nodes>
clic! 1e$t&

,i&ure 21' -ddin& nodes to the cluster'
6.The Setup wi8ard will perfor an analysis of all the nodes to verify that they are configured properly&
7.Type the password for the account used to start the cluster service&
8.'eview the suary inforation that is displayed for accuracy& The suary inforation will be
used to configure the other nodes when they Doin the cluster&
9.'eview any warnings or errors encountered during cluster creation> and then clic! 1e$t&
10. Clic! ,inish to coplete the installation&

Post-Installation Configuration
*eartbeat Configuration
)ow that the networ!s have been configured correctly on each node and the Cluster service has been
configured> you need to configure the networ! roles to define their functionality within the cluster& (ere is a
list of the networ! configuration options in Cluster 2dinistrator*
Bnable for cluster use* +f this chec! boA is selected> the cluster service uses this networ!& This chec!
boA is selected by default for all networ!s&
Client access onl+ 8#ublic net.ork:* Select this option if you want the cluster service to use this
networ! adapter only for eAternal counication with other clients& )o node-to-node counication
will ta!e place on this networ! adapter&
Internal cluster co00unications onl+ 8#rivate net.ork:* Select this option if you want the cluster
service to use this networ! only for node-to-node counication&
All co00unications 80i$ed net.ork:* Select this option if you want the cluster service to use the
networ! adapter for node-to-node counication and for counication with eAternal clients& This
option is selected by default for all networ!s&
This white paper assues that only two networ!s are in use& +t eAplains how to configure these networ!s as
one iAed networ! and one private networ!& This is the ost coon configuration& +f you have available
resources> two dedicated redundant networ!s for internal-only cluster counication are recoended&
To configure the heartbeat
1.Start Cluster 2dinistrator&
2.+n the left pane> clic! Cluster Configuration; clic! 1et.orks> right-clic! Private; and then clic!
Pro#erties&
3.Clic! Internal cluster co00unications onl+ 8#rivate net.ork:> as shown in ;igure 22 on the neAt
page&
,i&ure 22' 3sin& Cluster -dministrator to confi&ure the heartbeat'
4.Clic! 37&
5.'ight-clic! Public; and then clic! Pro#erties <shown in ;igure 23 below=&
6.Clic! to select the Bnable this net.ork for cluster use chec! boA&
7.Clic! the All co00unications 80i$ed net.ork: option> and then clic! 37&
,i&ure 2' %he Public Properties dialo& bo6'

*eartbeat Ada#ter PrioritiEation
2fter configuring the role of how the cluster service will use the networ! adapters> the neAt step is to
prioriti8e the order in which they will be used for intra-cluster counication& This is applicable only if two or
ore networ!s were configured for node-to-node counication& 1riority arrows on the right side of the
screen specify the order in which the cluster service will use the networ! adapters for counication
between nodes& The cluster service always attepts to use the first networ! adapter listed for reote
procedure call <'1C= counication between the nodes& Cluster service uses the neAt networ! adapter in
the list only if it cannot counicate by using the first networ! adapter&
1.Start Cluster 2dinistrator&
2.+n the left pane> right-clic! the cluster nae <in the upper left corner=> and then clic! Pro#erties&
3.Clic! the 1et.ork Priorit+ tab> as shown in ;igure 2: below&
,i&ure 2;' %he Network Priority tab in Cluster -dministrator'
4.5erify that the Private networ! is listed at the top& /se the -ove 5# or -ove 2o.n buttons to
change the priority order&
5.Clic! 37&
Configuring Cluster 2isks
Start Cluster 2dinistrator> right-clic! any dis!s that you want to reove fro the cluster> and then
clic! 2elete&
1ote* 9y default> all dis!s not residing on the sae bus as the syste dis! will have 1hysical %is!
'esources created for the> and will be clustered& Therefore> if the node has ultiple buses> soe dis!s
ay be listed that will not be used as shared storage> for eAaple> an internal SCS+ drive& Such dis!s

should be reoved fro the cluster configuration& +f you plan to ipleent 5olue "ount points for soe
dis!s> you ay want to delete the current dis! resources for those dis!s> delete the drive letters> and then
create a new dis! resource without a drive letter assignent&
Cuoru0 2isk Configuration
The Cluster Configuration Wi8ard autoatically selects the drive that is to be used as the quoru device& +t
will use the sallest partition that is larger then -0 "9& Bou ay want to change the autoatically selected
dis! to a dedicated dis! that you have designated for use as the quoru&
To configure the quorum disk
1.Start Cluster 2dinistrator <Clu2din&eAe=&
2.'ight-clic! the cluster nae in the upper-left corner> and then clic! Pro#erties&
3.Clic! the Cuoru0 tab&
4.+n the Cuoru0 resource list boA> select a different dis! resource& +n ;igure 2- below> %is! 6 is
selected in the Cuoru0 resource list boA&
,i&ure 2<' %he Quorum resource list bo6'
5.+f the dis! has ore than one partition> clic! the partition where you want the cluster-specific data to
be !ept> and then clic! 37&
62703-3 (ow to Change 6uoru %is! %esignation

Creating a >oot 2ela+
+n a situation where all the cluster nodes boot up and attept to attach to the quoru resource at the sae
tie> the Cluster service ay fail to start& ;or eAaple> this ay occur when power is restored to all nodes
at the eAact sae tie after a power failure& To avoid such a situation> increase or decrease the "i0e to
2is#la+ list of o#erating s+ste0s setting& To find this setting> clic! Start> point to -+ Co0#uter> right-
clic! -+ Co0#uter> and then clic! Pro#erties& Clic! the Advanced tab> and then clic! Settings under
Startu# And &ecover+&
"est Installation
There are several ethods for verifying a cluster service installation after the Setup process is coplete&
These include*
Cluster Ad0inistrator: +f installation was copleted only on node 4> start Cluster 2dinistrator> and
then attept to connect to the cluster& +f a second node was installed> start Cluster 2dinistrator on
either node> connect to the cluster> and then verify that the second node is listed&
Services A##let: /se the services snap-in to verify that the cluster service is listed and started&
Bvent 'og: /se the $vent 5iewer to chec! for ClusSvc entries in the syste log& Bou should see
entries confiring that the cluster service successfully fored or Doined a cluster&
Cluster service registr+ entries: 5erify that the cluster service installation process wrote the correct
entries to the registry& Bou can find any of the registry settings under HKEY_LOCAL_ACH!"E\Cluster
Clic! Start> clic! &un> and then type the 5irtual Server nae& 5erify that you can connect and see
resources&
"est ,ailover
To verify that resources will failover
1.Clic! Start> clic! Progra0s> clic! Ad0inistrative "ools> and then clic! Cluster Ad0inistrator> as
shown in ;igure 2. below&
,i&ure 2=' %he Cluster -dministrator #indo#'
2.'ight-clic! the 2isk 6rou# 1 group> and then clic! -ove 6rou#& The group and all its resources will
be oved to another node& 2fter a short period of tie> the 2isk ,: 6: will be brought online on the
second node& Watch the window to see this shift& 6uit Cluster 2dinistrator&

CongratulationsO Bou have copleted the configuration of the cluster service on all nodes& The server
cluster is fully operational& Bou are now ready to install cluster resources such as file shares> printer
spoolers> cluster aware services li!e %istributed Transaction Coordinator> %(C1> W+)S> or cluster-aware
progras such as $Achange Server or S6E Server&
A##endi$
Advanced "esting
)ow that you have configured your cluster and verified basic functionality and failover> you ay want to
conduct a series of failure scenario tests that will deonstrate eApected results and ensure the cluster will
respond correctly when a failure occurs& This level of testing is not required for every ipleentation> but
ay be insightful if you are new to clustering technology and are unfailiar how the cluster will respond or if
you are ipleenting a new hardware platfor in your environent& The eApected results listed are for a
clean configuration of the cluster with default settings> this does not ta!e into consideration any user
custoi8ation of the failover logic& This is not a coplete list of all tests> nor should successfully copleting
these tests be considered ?certified@ or ready for production& This is siply a saple list of soe tests that
can be conducted& ;or additional inforation> see the following article in the "icrosoft Gnowledge 9ase*
4300:0 ;ailoverF;ailbac! 1olicies on "icrosoft Cluster Server
Test: Start Cluster 2dinistrator> right-clic! a resource> and then clic! ?Initiate ,ailure@& The resource
should go into an failed state> and then it will be restarted and brought bac! into an online state on that
node&
E6pected *esult: 'esources should coe bac! online on the sae node
Test: Conduct the above ?Initiate ,ailure@ test three ore ties on that sae resource& ,n the fourth
failure> the resources should all failover to another node in the cluster&
E6pected *esult: 'esources should failover to another node in the cluster
Test: "ove all resources to one node& Start Coputer "anageent> and then clic! Services under
Services and A##lications& Stop the Cluster service& Start Cluster 2dinistrator on another node and
verify that all resources failover and coe online on another node correctly&
Test: "ove all resources to one node& ,n that node> clic! Start; and then clic! Shutdo.n& This will
turn off that node& Start Cluster 2dinistrator on another node> and then verify that all resources
failover and coe online on another node correctly&
Test: "ove all resources to one node> and then press the power button on the front of that server to
turn it off& +f you have an 2C1+ copliant server> the server will perfor an ?$ergency Shutdown@ and
turn off the server& Start Cluster 2dinistrator on another node and verify that all resources failover and
coe online on another node correctly& ;or additional inforation about an $ergency Shutdown> see
the following articles in the "icrosoft Gnowledge 9ase*
32-3:3 (,W T,* 1erfor an $ergency Shutdown in Windows Server 2003
2304-0 1ower 9utton on 2C1+ Coputer "ay ;orce an $ergency Shutdown
4arning* 1erforing the $ergency Shutdown test ay cause data corruption and data loss& %o not
conduct this test on a production server
Test: "ove all resources to one node> and then pull the power cables fro that server to siulate a
hard failure& Start Cluster 2dinistrator on another node> and then verify that all resources failover and
coe online on another node correctly
4arning* 1erforing the hard failure test ay cause data corruption and data loss& This is an eAtree test&
"a!e sure you have a bac!up of all critical data> and then conduct the test at your own ris!& %o not conduct
this test on a production server
Test: "ove all resources to one node> and then reove the public networ! cable fro that node& The
+1 2ddress resources should fail> and the groups will all failover to another node in the cluster& ;or
additional inforation > see the following articles in the "icrosoft Gnowledge 9ase*
27.3:2 )etwor! ;ailure %etection and 'ecovery in Windows Server 2003 Clusters
Test: 'eove the networ! cable for the 1rivate heartbeat networ!& The heartbeat traffic will failover to
the public networ!> and no failover should occur& +f failover occurs> please see the ?Configuring the
1rivate )etwor! 2daptor@ section in earlier in this docuent
E6pected *esult: There should be no failures or resource failovers
SCSI 2rive Installations
This appendiA is provided as a generic set of instructions for SCS+ drive installations& +f the SCS+ hard dis!
vendorCs instructions conflict with the instructions here> always follow the instructions supplied by the
vendor&
The SCS+ bus listed in the hardware requireents ust be configured prior to cluster service installation&
Configuration applies to*
The SCS+ devices&
The SCS+ controllers and the hard dis!s so that they wor! properly on a shared SCS+ bus&
1roperly terinating the bus& The shared SCS+ bus ust have a terinator at each end of the bus& +t is
possible to have ultiple shared SCS+ buses between the nodes of a cluster&
+n addition to the inforation on the following pages> refer to docuentation fro the anufacturer of your
SCS+ device or to the SCS+ specifications> which can be ordered fro the 2erican )ational Standards
+nstitute <2)S+=& The 2)S+ Web site includes a catalog that can be searched for the SCS+ specifications&
Configuring the SCSI 2evices
$ach device on the shared SCS+ bus ust have a unique SCS+ identification nuber& 9ecause ost SCS+
controllers default to SCS+ +% 0> configuring the shared SCS+ bus includes changing the SCS+ +% nuber on
one controller to a different nuber> such as SCS+ +% .& +f there is ore than one dis! that will be on the
shared SCS+ bus> each dis! ust have a unique SCS+ +% nuber&
"er0inating the Shared SCSI >us
There are several ethods for terinating the shared SCS+ bus& They include*
SCSI controllers
SCS+ controllers have internal soft terination that can be used to terinate the bus> however this ethod
is not recoended with the cluster server& +f a node is turned off with this configuration> the SCS+ bus will
be terinated iproperly and will not operate correctly&
Storage enclosures
Storage enclosures also have internal terination> which can be used to terinate the SCS+ bus if the
enclosure is at the end of the SCS+ bus& This should be turned off&
? cables
B cables can be connected to devices if the device is at the end of the SCS+ bus& 2n eAternal active
terinator can then be attached to one branch of the B cable in order to terinate the SCS+ bus& This
ethod of terination requires either disabling or reoving any internal terinators that the device ay
have&
;igure 20 outlines how a SCS+ cluster should be physically connected&
,i&ure 2@' - dia&ram of a $C$) cluster hard#are confi&uration'

1ote: 2ny devices that are not at the end of the shared bus ust have their internal terination disabled& B
cables and active terinator connectors are the recoended terination ethods because they will
provide terination even when a node is not online&
Storage Area 1et.ork Considerations
There are two supported ethods of ;ibre Channel-based storage in a Windows Server 2003 server
cluster* arbitrated loops and switched fabric&
I0#ortant* When evaluating both types of ;ibre Channel ipleentation> read the vendorCs docuentation
and be sure you understand the specific features and restrictions of each&
2lthough the ter ,ibre Channel iplies the use of fiber-optic technology> copper coaAial cable is also
allowed for interconnects&
Arbitrated 'oo#s 8,C-A':
2 ;ibre Channel arbitrated loop <;C-2E= is a set of nodes and devices connected into a single loop& ;C-2E
provides a cost-effective way to connect up to 42. devices into a single networ!& 2s with SCS+> a aAiu
of two nodes is supported in an ;C-2E server cluster configured with a hub& 2n ;C-2E is illustrated in
;igure&
Figure Error# Refere$%e sour%e $ot fou$&.' FC(AL Co$$e%tio$
;C-2Es provide a solution for two nodes and a sall nuber of devices in relatively static configurations& 2ll
devices on the loop share the edia> and any pac!et traveling fro one device to another ust pass
through all interediate devices&
+f your high-availability needs can be et with a two-node server cluster> an ;C-2E deployent has several
advantages*
The cost is relatively low&
Eoops can be eApanded to add storage <although nodes cannot be added=&
Eoops are easy for ;ibre Channel vendors to develop&
Guide to Creating and Configuring a Server Cluster in Windows Server 2003 :0
The disadvantage is that loops can be difficult to deploy in an organi8ation& 9ecause every device on the
loop shares the edia> overall bandwidth in the cluster is lowered& Soe organi8ations ight also be
unduly restricted by the 42.-device liit&
S.itched ,abric 8,C-S4:
;or any cluster larger than two nodes> a switched ;ibre Channel switched fabric <;C-SW= is the only
supported storage technology& +n an ;C-SW> devices are connected in a any-to-any topology using
;ibre Channel switches <illustrated in ;igure $rror* 'eference source not found&2=&
Figure Error# Refere$%e sour%e $ot fou$&.2 FC(S) Co$$e%tio$
When a node or device counicates with another node or device in an ;C-SW> the source and target set
up a point-to-point connection <siilar to a virtual circuit= and counicate directly with each other& The
fabric itself routes data fro the source to the target& +n an ;C-SW> the edia is not shared& 2ny device can
counicate with any other device> and counication occurs at full bus speed& This is a fully scalable
enterprise solution and> as such> is highly recoended for deployent with server clusters&
;C-SW is the priary technology eployed in S2)s& ,ther advantages of ;C-SW include ease of
deployent> the ability to support illions of devices> and switches that provide fault isolation and rerouting&
2lso> there is no shared edia as there is in ;C-2E> allowing for faster counication& (owever> be aware
that ;C-SWs can be difficult for vendors to develop> and the switches can be eApensive& 5endors also have
to account for interoperability issues between coponents fro different vendors or anufacturers&
5sing SA1s .ith Server Clusters
;or any large-scale cluster deployent> it is recoended that you use a S2) for data storage& Saller
SCS+ and stand-alone ;ibre Channel storage devices wor! with server clusters> but S2)s provide superior
fault tolerance&
2 S2) is a set of interconnected devices <such as dis!s and tapes= and servers that are connected to a
coon counication and data transfer infrastructure <;C-SW> in the case of Windows Server 2003
clusters=& 2 S2) allows ultiple server access to a pool of storage in which any server can potentially
access any storage unit&
The inforation in this section provides an overview of using S2) technology with your Windows
Server 2003 clusters& ;or additional inforation about deploying server clusters on S2)s> see the Windows
Clustering* Storage 2rea )etwor!s lin! on the Web 'esources page at
http*FFwww&icrosoft&coFwindowsFres!itsFwebresources&
1ote* 5endors that provide S2) fabric coponents and software anageent tools have a wide range of
tools for setting up> configuring> onitoring> and anaging the S2) fabric& Contact your S2) vendor for
details about your particular S2) solution&
SCSI &esets
$arlier versions of Windows server clusters presued that all counications to the shared dis! should be
treated as an isolated SCS+ bus& This behavior ay be soewhat disruptive> and it does not ta!e
advantage of the ore advanced features of ;ibre Channel to both iprove arbitration perforance and
reduce disruption&
,ne !ey enhanceent in Windows Server 2003 is that the Cluster service issues a coand to brea! a
'$S$'52T+,)> and the Stor1ort driver can do a targeted or device reset for dis!s that are on a ;ibre
Channel topology& +n Windows 2000 server clusters> an entire bus-wide SCS+ '$S$T is issued& This causes
all devices on the bus to be disconnected& When a SCS+ '$S$T is issued> a lot of tie is spent resetting
devices that ay not need to be reset> such as dis!s that the C(2EE$)G$' node ay already own&
'esets in Windows 2003 occur in the following order*
4& Targeted logical unit nuber <E/)=
2& Targeted SCS+ +%
3& $ntire bus-wide SCS+ '$S$T
Targeted resets require functionality in the host bus adapter <(92= drivers& The driver ust be written
for Stor1ort and not SCS+1ort& %rivers that use SCS+1ort will use the Challenge and %efense the sae
as it is currently in Windows 2000& Contact the anufacturer of the (92 to deterine if it supports
Stor1ort&
SCSI Commands
*he Cluster service uses the following SCS+ coands*
SCS+ reserve* This coand is issued by a host bus adapter or controller to aintain
ownership of a SCS+ device& 2 device that is reserved refuses all coands fro all other host
bus adapters eAcept the one that initially reserved it> the initiator& +f a bus-wide SCS+ reset
coand is issued> loss of reservation occurs&
SCS+ release* This coand is issued by the owning host bus adapterI it frees a SCS+ device
for another host bus adapter to reserve&
SCS+ reset* This coand brea!s the reservation on a target device& This coand is
soeties referred to globally as a Jbus reset&J
The sae control codes are used for ;ibre Channel as well& These paraeters are defined in this partner
article*
30347. (ow the Cluster Service Ta!es ,wnership of a %is! on the Shared 9us
3404.2 Supported ;ibre Channel Configurations
The following sections provide an overview of S2) concepts that directly affect a server cluster deployent&
1ote
H!s
(ost bus adapters <(92s= are the interface cards that connect a cluster node to a S2)> siilar to the way
that a networ! adapter connects a server to a typical $thernet networ!& (92s> however> are ore difficult to
configure than networ! adapters <unless the (92s are preconfigured by the S2) vendor=& 2ll (92s in all
nodes should be identical and be at the sae driver and firware revision
"oning and #$N %asking
Poning and E/) as!ing are fundaental to S2) deployents> particularly as they relate to a Windows
Server 2003 cluster deployent&
Zoning
"any devices and nodes can be attached to a S2)& With data stored in a single cloud> or storage entity> it
is iportant to control which hosts have access to specific devices& Poning allows adinistrators to partition
devices in logical volues and thereby reserve the devices in a volue for a server cluster& That eans
that all interactions between cluster nodes and devices in the logical storage volues are isolated within the
boundaries of the 8oneI other noncluster ebers of the S2) are not affected by cluster activity&
;igure $rror* 'eference source not found&3 is a logical depiction of two S2) 8ones <Pone 2 and Pone 9=>
each containing a storage controller <S4and S2> respectively=&
Figure Error# Refere$%e sour%e $ot fou$&.3 +o$i$g
+n this ipleentation> )ode 2 and )ode 9 can access data fro the storage controller S4> but )ode C
cannot& )ode C can access data fro storage controller S2&
Poning needs to be ipleented at the hardware level <with the controller or switch= and not through
software& The priary reason is that 8oning is also a security echanis for a S2)-based cluster> because
unauthori8ed servers cannot access devices inside the 8one <access control is ipleented by the
switches in the fabric> so a host adapter cannot gain access to a device for which it has not been
configured=& With software 8oning> the cluster would be left unsecured if the software coponent failed&
+n addition to providing cluster security> 8oning also liits the traffic flow within a given S2) environent&
Traffic between ports is routed only to segents of the fabric that are in the sae 8one&
!N "asking
2 E/) is a logical dis! defined within a S2)& Server clusters see E/)s and thin! they are physical dis!s&
E/) as!ing> perfored at the controller level> allows you to define relationships between E/)s and
cluster nodes& Storage controllers usually provide the eans for creating E/)-level access controls that
allow access to a given E/) to one or ore hosts& 9y providing this access control at the storage controller>
the controller itself can enforce access policies to the devices&
E/) as!ing provides ore granular security than 8oning> because E/)s provide a eans for 8oning at
the port level& ;or eAaple> any S2) switches allow overlapping 8ones> which enable a storage controller
to reside in ultiple 8ones& "ultiple clusters in ultiple 8ones can share the data on those controllers&
;igure $rror* 'eference source not found&: illustrates such a scenario&
Figure Error# Refere$%e sour%e $ot fou$&., Stor-ge Co$troller i$ ulti.le +o$es
E/)s used by Cluster 2 can be as!ed> or hidden> fro Cluster 9 so that only authori8ed users can access
data on a shared storage controller&
&equirements for 'eploying S!Ns with (indows Server 2))* Clusters
The following list highlights the deployent requireents you need to follow when using a S2) storage
solution with your server cluster& ;or a white paper that provides ore coplete inforation about using
S2)s with server clusters> see the Windows Clustering* Storage 2rea )etwor!s lin! on the Web 'esources
page at http*FFwww&icrosoft&coFwindowsFres!itsFwebresources&
Guide to Creating and Configuring a Server Cluster in Windows Server 2003 ::
$ach cluster on a S2) ust be deployed in its own 8one& The echanis the cluster uses to protect
access to the dis!s can have an adverse effect on other clusters that are in the sae 8one& 9y using 8oning
to separate the cluster traffic fro other cluster or noncluster traffic> there is no chance of interference&
2ll (92s in a single cluster ust be the sae type and have the sae firware version& "any storage and
switch vendors require that all (92s on the sae 8oneHand> in soe cases> the sae fabricHshare these
characteristics&
2ll storage device drivers and (92 device drivers in a cluster ust have the sae software version&
)ever allow ultiple nodes access to the sae storage devices unless they are in the sae cluster&
)ever put tape devices into the sae 8one as cluster dis! storage devices& 2 tape device could isinterpret
a bus rest and rewind at inappropriate ties> such as during a large bac!up&
+uidelines for 'eploying S!Ns with (indows Server 2))* Server Clusters
+n addition to the S2) requireents discussed in the previous section> the following practices are highly
recoended for server cluster deployent*
+n a highly available storage fabric> you need to deploy clustered servers with ultiple (92s& +n these
cases> always load the ultipath driver software& +f the +F, subsyste sees two (92s> it assues they are
different buses and enuerates all the devices as though they were different devices on each bus& The
host> eanwhile> is seeing ultiple paths to the sae dis!s& ;ailure to load the ultipath driver will disable
the second device because the operating syste sees what it thin!s are two independent dis!s with the
sae signature&
%o not eApose a hardware snapshot of a clustered dis! bac! to a node in the sae cluster& (ardware
snapshots ust go to a server outside the server cluster& "any controllers provide snapshots at the
controller level that can be eAposed to the cluster as a copletely separate E/)& Cluster perforance is
degraded when ultiple devices have the sae signature& +f the snapshot is eAposed bac! to the node with
the original dis! online> the +F, subsyste attepts to rewrite the signature& (owever> if the snapshot is
eAposed to another node in the cluster> the Cluster service does not recogni8e it as a different dis! and the
result could be data corruption& 2lthough this is not specifically a S2) issue> the controllers that provide this
functionality are typically deployed in a S2) environent&
;or additional inforation> see the following articles in the "icrosoft Gnowledge 9ase*
304.:0 Cluster Service +proveents for Storage 2rea )etwor!s
30::4- Support for "ultiple Clusters 2ttached to the Sae S2) %evice
2700:3 Windows Clustering and Geographically Separate Sites
Guide to Creating and Configuring a Server Cluster in Windows Server 2003 :-
&elated 'inks
See the following resources for further inforation*
"icrosoft Cluster Service +nstallation 'esources
at http*FFsupport&icrosoft&coFQidR2-32.0
6uoru %rive Configuration +nforation
at http*FFsupport&icrosoft&coFQidR2703:-
'ecoended 1rivate J(eartbeatJ Configuration on Cluster Server
at http*FFsupport&icrosoft&coFQidR2-70-0
)etwor! ;ailure %etection and 'ecovery in a Server Cluster
at http*FFsupport&icrosoft&coFQidR2:2.00
(ow to Change 6uoru %is! %esignation
at http*FFsupport&icrosoft&coFQidR2703-3
"icrosoft Windows Clustering* Storage 2rea )etwor!s
at http*FFwww&icrosoft&coFwindows&netserverFtechinfoFoverviewFsan&spA
Geographically %ispersed Clusters in Windows Server 2003
at http*FFwww&icrosoft&coFwindows&netserverFtechinfoFoverviewFclustergeo&spA
Server Cluster )etwor! 'equireents and 9est 1ractices
at http*FFwww&icrosoft&coFtechnetFtreeviewFdefault&aspQ
urlRFtechnetFprodtechnolFwindowsserver2003FaintainFoperateFclstntbp&asp
;or the latest inforation about Windows Server 2003> see the Windows 2003 Server Web site at
http*FFwww&icrosoft&coFwindowsserver2003Fdefault&spA
Guide to Creating and Configuring a Server Cluster in Windows Server 2003 :.

Cluster Configuration W2k3

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Cluster Configuration W2k3

Hochgeladen von

Copyright:

Verfügbare Formate

Guide to Creating and Configuring a Server Cluster

under Windows Server 2003

Das könnte Ihnen auch gefallen