I think I may have figured this out. It is just a file share that can
actually be stored anywhere (san, nas, whatever) that the cluster service on
the mailbox servers update. Some kind log/journal--just a place to store
data to that be use to determine victor. If I am off base please let me
know.
If this is the case, can I create the file share witness on my DFS server so
it can be replicated between my sites? Or is this not recommended?
Thanks.
One thing you will want to consider is where do you place the file
share witness on your network. Remember, a MNS cluster requires a
majority of nodes to be available in order to come into service. If
your witness is a file share in your primary data center, if you lose
that data center, your secondary server in your DR site will not come
into service.
On the other hand, if your witness server is in the DR site, then a
loss of WAN connectivity to your DR site will result in a false
failover to the DR site, since your primary server would be a single
node and the majority would be in your DR site.
The best scenario is if you can place your witness server in a third
location with direct communications to both the primary and DR
site.That way your WAN link does not become a SPOF and your are
protected in the event of a complete site loss.
David A. Bermingham, MCSE, MCSA:Messaging
Senior Systems Engineer
www.steeleye.com
> I think I may have figured this out. It is just a file share that can
> actually be stored anywhere (san, nas, whatever) that the cluster service on
[quoted text clipped - 20 lines]
> >
> > Thanks in advance.
Neil Hobson [MVP] - 07 Dec 2006 16:22 GMT
> One thing you will want to consider is where do you place the file
> share witness on your network. Remember, a MNS cluster requires a
> majority of nodes to be available in order to come into service. If
> your witness is a file share in your primary data center, if you lose
> that data center, your secondary server in your DR site will not come
> into service.
It's my understanding that the MS best practice here is to have the FSW
located on the hub transport server within the cluster's 'preferred owner'
data center, i.e. the primary data center. Presumably this is because the
most likely failure will be the network between the two data centers rather
than losing an entire data center. Note the use of 'most likely'. :)
From what I remember at TechEd IT Forum, a failover of the primary data
center has some pre-provision requirements such as the creation of the FSW
share and relevant permissions on the hub transport server located within
the secondary data center so that they're ready to go if needed. You then
update DNS and use /forcequorum. There were some other things to do, but
you get the idea.
> On the other hand, if your witness server is in the DR site, then a
> loss of WAN connectivity to your DR site will result in a false
[quoted text clipped - 9 lines]
> Senior Systems Engineer
> www.steeleye.com

Signature
Neil Hobson
Exchange MVP
http://www.msexchange.org/Neil_Hobson/
http://www.msexchangeblog.com
daveberm - 07 Dec 2006 19:17 GMT
That makes sense, as long as the procedure is well documented and the
limitation is understood by management.
> > One thing you will want to consider is where do you place the file
> > share witness on your network. Remember, a MNS cluster requires a
[quoted text clipped - 35 lines]
> http://www.msexchange.org/Neil_Hobson/
> http://www.msexchangeblog.com