Solved

Exchange 2010 File Share Witness design, 2 sites

Posted on 2011-03-17
2
436 Views
Last Modified: 2012-05-11
Hi all,

I am currently performing a transition from Exchange 2003 to 2010, and so far so good.

I have now come to the point where I need to start building the resilience into the new system to allow for system failures.

We are located in site A. site B is the datacentre, and all exchange kit and DCs are located there.

I wanted to build (presumably) a DAG with 2 servers at the DC, so in case 1 fails, the other will take over with a live up to date copy of the database. Can I build an Exchange server at our office (Site A) as the copy and if the link to the DC goes the local server kicks in?

The issue here is the FSW. In both scenarios above, if I have the FSW at the DC then how will the local server at site A kick in? Or shall I put the FSW at site A instead, so if the link to the DC is lost, the local exchange server kicks in?

I assume the exchange mailbox servers can replicate all database traffic between them and stay synchronised and up to date in case the non-master has to assume control?

Our CAS servers are at the DC (site B).

Any help would be appreciated!

Thanks

Andoni
0
Comment
Question by:schneiderit
2 Comments
 
LVL 49

Accepted Solution

by:
Akhater earned 500 total points
ID: 35155951
When you say DC you mean Data Center right or Domain Controller ?


1. I wanted to build (presumably) a DAG with 2 servers at the DC, so in case 1 fails, the other will take over with a live up to date copy of the database. Can I build an Exchange server at our office (Site A) as the copy and if the link to the DC goes the local server kicks in?

Nop you cannot, DAG does not take into account link failures if the link fails  the datacenter without FSW will fail
0
 

Author Closing Comment

by:schneiderit
ID: 35156841
Thanks!

I meant datacentre.

Taking into account the FSW and link state in case of failure, there would be no point isolating the mailbox server at the office (Site A) as the CAS servers are at the DC, rendering exchange usage useless anyway. We do not have an internet line at site A, it is all at the datacentre.

Researching this further it seems unnecessary to have 1 mailbox server at each site. So I have opted for 2 mailbox servers in a DAG at the datacentre, and if the link goes (which is unlikely, 2 x 40 gig links), it goes, nothing I can do about it.

Thanks again

Andoni
0

Featured Post

Find Ransomware Secrets With All-Source Analysis

Ransomware has become a major concern for organizations; its prevalence has grown due to past successes achieved by threat actors. While each ransomware variant is different, we’ve seen some common tactics and trends used among the authors of the malware.

Join & Write a Comment

Marketers need statistics and metrics like everybody else needs oxygen. In this article we explain how to enable marketing campaign statistics for Microsoft Exchange mail.
Following basic email etiquette rules will help you write a professional email and achieve a good, lasting impression with your contacts.
In this video we show how to create an email address policy in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.:  First we need to log into the Exchange Admin Center. Navigate to the Mail Flow…
In this video we show how to create a mailbox database in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Servers >> Data…

707 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

20 Experts available now in Live!

Get 1:1 Help Now