• RSS
  • Twitter
  • FaceBook

Exchange Server Forums

Forums | Register | Login | My Profile | Inbox | RSS RSS icon | My Subscription | My Forums | Address Book | Member List | Search | FAQ | Ticket List | Log Out

DAG Design

Users viewing this topic: none

Logged in as: Guest
  Printable Version
All Forums >> [Microsoft Exchange 2010] >> High Availability >> DAG Design Page: [1]
Login
Message << Older Topic   Newer Topic >>
DAG Design - 3.Jan.2012 7:25:10 PM   
huthmakerj

 

Posts: 27
Joined: 28.Dec.2011
Status: offline
I've been getting a ton of conflicting information, so I want to throw this design idea out here again. We are planning on upgrading our existing Exchange 2003 enviornment to Exchange 2010. One of the mandatory requirements my management has given me is that each satellite office will get its own Exchange server. If it wasnt for that, I would just build a nice DAG here at the Datacenter and load balance a CAS/Hub Array.

The second mandatory requirement is to be able to do all backup's here at the datacenter.

I know everyone has an opinion on why this set up is wrong, but this is the framework I MUST work within.

With that said, what would be the best solution. We are trying to minimize the amount of WAN traffic at each site.

My original idea; which I'm starting to reconsider; is to set up a behemoth server at the data center, and good servers at each remote location. I would make every server the member of the same DAG. I would then keep an active copy of each database on their respective site server, and a passive copy on the Datacenter server.

When I threw this idea out to begin with, everyone tore in to me. But I started asking questions about doing remote backups instead, and everyone asked me why I wasnt planning to use dags.

Our WAN links at each location is a minimum of a T1 MPLS. So the minimum bandwidth between any given location is at least 1.544mbps. Some locations have multiple T1's, and 2 have a T3.

I did do some pings from our Des Moines office, and saw most replies ~150ms. However I did have one reply hit 450ms.

We have 600 CAL's purchased for Exchange 2010. So my guess is that is proportional to the amount of users across the entire company. Most locations would have around 25-50 users.

Can someone please give me a solid answer on if this would work? If not, can someone please give me a better solution?
Post #: 1
RE: DAG Design - 4.Jan.2012 8:05:01 AM   
travis.sheldon

 

Posts: 356
Joined: 16.Sep.2010
Status: offline
Please run the mailbox role calculator so we can have a good understanding of the layout you're going for. You can't get wrapped up in the DAG and replication details before you have a solid understanding of your layout design..IE, how many databases? How many copies of each databases? How many users on average in each site? How much mail is typically sent each day? All these are items that you'll fill into the mailbox storage calculator and it'll give you and us a great idea of what your overall concept and layout is.

(in reply to huthmakerj)
Post #: 2
RE: DAG Design - 4.Jan.2012 9:47:31 AM   
huthmakerj

 

Posts: 27
Joined: 28.Dec.2011
Status: offline
Hey Travis,

I have populated the Mailbox Role Calculator spreadsheet. What information would you like to see? I can email it to you if you give me your email address.

Thanks,
John

(in reply to travis.sheldon)
Post #: 3

Page:   [1] << Older Topic    Newer Topic >>
All Forums >> [Microsoft Exchange 2010] >> High Availability >> DAG Design Page: [1]
Jump to:

New Messages No New Messages
Hot Topic w/ New Messages Hot Topic w/o New Messages
Locked w/ New Messages Locked w/o New Messages
 Post New Thread
 Reply to Message
 Post New Poll
 Submit Vote
 Delete My Own Post
 Delete My Own Thread
 Rate Posts


Follow TechGenix on Twitter