Quantcast
Channel: Exchange Server 2013 - General Discussion forum
Viewing all articles
Browse latest Browse all 13303

DAG across 2 Data Centers

$
0
0

Looking for pros and cons of 2 potential Exchange 2013 implementations.

  • ADSite1: 400 users
  • ADSite2: 100 users
  • ADSite3: 50 users

Implementation 1: (DAG across two Data Centers without DAC implemented)

  • ADSite1: ExchSrv1 (MBX/CAS) --- DAG (2 DB) --- ADSite2: ExchSrv2 (MBX/CAS)
  • ADSite3: FSW

Implementation 2: (DAG across two Data Centers with DAC implemented)

  • ADSite1: ExchSrv1 (MBX/CAS) ExchSrv2 (MBX/CAS)--- DAG (2 DB) --- ADSite2: ExchSrv3 (MBX/CAS)
  • Site3: FSW

1. Am I gaining any true benefit from Implementation 2 (additional server in Primary Site)? i.e. Implementation 1 covers me for HA and DR. Would it make sense to consolidate ADSite1 and ADsite2 into a single ADSite for Implementation 1?

2. In either case, is it ok the configure NLB for all the servers (for the CAS role). So, if a user on ADSite2 hits the CAS on ADSite1 they could then be proxied to either ADSite ExchSrv depending on where their MBX is.


3. If all the MBX DBs in ADSite2 are replicas and not active and a user hits the CAS on ADSite2, is this increasing network traffic to then allow ExchSrv3 (CAS) to have to proxy to the ExchSrv1 (MBX). If so, does it not make sense to have the ADSite2 server only hosting replicas?


Viewing all articles
Browse latest Browse all 13303

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>