It was released as a post - Windows
2003 SP1 download in kb921181. It is included in Service Pack 2 for Windows 2003. The FSW quorum
allows the cluster nodes to share a file share outside of the cluster to add an additional vote for cluster
status. As long as any two resources are available, the cluster nodes know which node is active. If two
resources go offline, the entire cluster shuts down because it is not possible for a node to know if it is
active or passive.
The recommended location for the FSW is on a CAS or Hub server. Another recommendation is to use a
DNS CName record for the server name hosting the FSW. This makes changing the server that has the
replacement FSW easier because the cluster configuration does not have to change, only the DNS record
needs to be updated. If the DNS alias is not used, an administrator would have to go through the steps
in this section again to create the new FSW. This process is more time consuming than a simple record
update.
1. First set the parameters needed for the FSW creation:
??‘ User is the cluster service account
??‘ Cluster_Name is the name of the cluster
??‘ User_Perm is the full permission for the cluster service account
??‘ Share_Path is the full path for the file share
??‘ DirPath is the full path the shared directory
??‘ CMS_Name is the name of the Clustered Mailbox Server
$Cluster_Name (reused from the initial configuration above)
$User_Perm=$User+???:F???
$Share_Path=???\\MBFSW\MNS_FSW_MBCCR???
$Share_Name=???MNS_FSW_MBCCR???
$Dir_Path=???C:\FSWMB100CCR???
$CMS_Name=???MB100CCR???
$Share_DNS_Name=???MBFSW???
$FSW_Server_Name=???CA100.
Pages:
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482