In Exchange Server 2007 RTM and SP1, the Exchange team has published guidance for using a CNAME record in DNS as part of the provisioning process for the file share witness (FSW) component of a Major...
Updated Jul 01, 2019
Version 2.0
Blog Post
6 MIN READ
New File Share Witness and Force Quorum Guidance for Exchange 2007 Clusters
Hi there,
Firstly, sorry for a long post. I think I'm getting confused (or confusing myself) and I'm pretty sure it's because I'm not fully understanding how MNS+FSW works (especially when using ForceQuorum). I have added comments on the steps I'm having troubles getting my head around. I would greatly appreciate if you can confirm my thoughts, or point out where I'm wrong:
Provisioning Site B:
2) Force quorum on NodeB in Datacenter B by adding the following registry value to the node:
HKLMSystemCurrentControlSetServicesClusSvcParameters
REG_SZ: ForceQuorum
Value: NodeB
- Does this tell the cluster service to start with a new quorum, and to start in a configuration so that NodeB is the only node in the Cluster?
4) Reconfigure the cluster quorum to use the FSW share on EXHUB2.
- Why do we need to do this step? If the Cluster service has started and the Clustered Mailbox Server is online (which I'm assuming it is, as the next step is to take it offline), couldn't we just run without a FSW until we re-activate SiteA?
5) Take the clustered mailbox server offline.
6) Remove the registry value, and then reboot NodeB.
7) Start the clustered mailbox server.
Re-Activating siteA
1) Provision a new share on EXHUB1 in Datacenter A.
Is this to ensure that the old share (containing the old quorum data) is not available to NodeA when it starts (and therefore can not form a majority with it)? Would it be possible to just delete the contents of the existing FSW Share, or is it a requiremnt to create a new share (new share name?)?
2) Bring NodeA online.
How does the cluster service start in this situation? Is it because it can still form majority because it can communicate with both itself and NodeB - Basically it just thinks that the EXHUB1 is down (as the Share was recreated or the contents were deleted in step 1)?
The rest of the steps seem fairly self explanatory. Any clarification or further explanation on the above would be most appreciated.
3) Reconfigure the cluster quorum to use the FSW share on EXHUB1.
4) Stop the clustered mailbox server.
5) Move the Cluster Group from NodeB to NodeA.
6) Move the clustered mailbox server from NodeB to NodeA.
7) Start the clustered mailbox server.
Many thanks,
Stephen.
Firstly, sorry for a long post. I think I'm getting confused (or confusing myself) and I'm pretty sure it's because I'm not fully understanding how MNS+FSW works (especially when using ForceQuorum). I have added comments on the steps I'm having troubles getting my head around. I would greatly appreciate if you can confirm my thoughts, or point out where I'm wrong:
Provisioning Site B:
2) Force quorum on NodeB in Datacenter B by adding the following registry value to the node:
HKLMSystemCurrentControlSetServicesClusSvcParameters
REG_SZ: ForceQuorum
Value: NodeB
- Does this tell the cluster service to start with a new quorum, and to start in a configuration so that NodeB is the only node in the Cluster?
4) Reconfigure the cluster quorum to use the FSW share on EXHUB2.
- Why do we need to do this step? If the Cluster service has started and the Clustered Mailbox Server is online (which I'm assuming it is, as the next step is to take it offline), couldn't we just run without a FSW until we re-activate SiteA?
5) Take the clustered mailbox server offline.
6) Remove the registry value, and then reboot NodeB.
7) Start the clustered mailbox server.
Re-Activating siteA
1) Provision a new share on EXHUB1 in Datacenter A.
Is this to ensure that the old share (containing the old quorum data) is not available to NodeA when it starts (and therefore can not form a majority with it)? Would it be possible to just delete the contents of the existing FSW Share, or is it a requiremnt to create a new share (new share name?)?
2) Bring NodeA online.
How does the cluster service start in this situation? Is it because it can still form majority because it can communicate with both itself and NodeB - Basically it just thinks that the EXHUB1 is down (as the Share was recreated or the contents were deleted in step 1)?
The rest of the steps seem fairly self explanatory. Any clarification or further explanation on the above would be most appreciated.
3) Reconfigure the cluster quorum to use the FSW share on EXHUB1.
4) Stop the clustered mailbox server.
5) Move the Cluster Group from NodeB to NodeA.
6) Move the clustered mailbox server from NodeB to NodeA.
7) Start the clustered mailbox server.
Many thanks,
Stephen.