My boss wants me to setup a 2nd Exchange 2010 box in our corporate office. he'd like me to set something up that will make Exchange highly available to our users even if our main site fails. Eventually we will have one exchange server on each remote site (2 in corporate office). We have three sites, a corporate office, remote sites New York and California.
The corporate site is where our datacenter is located and where I'm planning to have the second exchange server. The 2 sites are New york and California.
How can I setup Exchange 2010 on each site so that even if one of any sites go down email will still be accessible to both local (corporate office) Outlook users and remote site users and OWA/Blackberry users? I'm not sure where and how to start and go about making this all work across three sites.
DAGs use a subset of Windows Failover Clustering technologies, namely, the cluster heartbeat, cluster networks, and the cluster database (for storing data that changes or can change quickly).
Because DAGs rely on Windows Failover Clustering, they can only be created on Exchange 2010 Enterprise Edition Mailbox servers that are running Windows Server 2008 Enterprise or Windows Server 2008 Datacenter. In addition, each Mailbox server in the DAG must have at least two network interface cards in order to be supported.
When a DAG is formed, the failover cluster that is created will initially use the Node Majority quorum mode. When the second Mailbox server is added to the DAG, the cluster quorum is automatically changes to the Node and File Share Majority quorum model. When this change occurs, the DAG will begin using the specified UNC path and directory for the cluster quorum. If the specified UNC path and directory does not exist, the Add-DatabaseAvailbilityGroupServer cmdlet will automatically create them, and provision them with full control permissions for local administrators and the CNO computer account.
Because DAGs rely on Windows Failover Clustering, they can only be created on Exchange 2010 Enterprise Edition Mailbox servers that are running Windows Server 2008 Enterprise or Windows Server 2008 Datacenter.
This statement is wrong. The only difference between Exchange 2010 Standard and Enterprise is the number of Mailbox Databases it can host. Standard can host up to 5 databases whereas Enterprise can host up to as many as 100. So, is you want to use DAG functionality and can get by with 5 databases, Standard Edition of Exchange 2010 is fine.
< Message edited by Jesper Bernle -- 16.Nov.2011 10:29:33 AM >
_____________________________
Jesper Bernle | Microsoft Community Contributor 2011 Awardee
My boss wants me to setup a 2nd Exchange 2010 box in our corporate office. he'd like me to set something up that will make Exchange highly available to our users even if our main site fails. Eventually we will have one exchange server on each remote site (2 in corporate office). We have three sites, a corporate office, remote sites New York and California.
The corporate site is where our datacenter is located and where I'm planning to have the second exchange server. The 2 sites are New york and California.
How can I setup Exchange 2010 on each site so that even if one of any sites go down email will still be accessible to both local (corporate office) Outlook users and remote site users and OWA/Blackberry users? I'm not sure where and how to start and go about making this all work across three sites.
Any input would be greatly appreciated.
Thanks in advance!
Dennis
It is possible to achieve this but it takes both good knowledge of the inner workings of both DAGs and Load Balancing and some careful planning, so if your up to the challange fine, but my recommendation is to hire an Exchange Server consultant with good knowledge in designing High Availability in Exchange 2010.
_____________________________
Jesper Bernle | Microsoft Community Contributor 2011 Awardee
Because DAGs rely on Windows Failover Clustering, they can only be created on Exchange 2010 Enterprise Edition Mailbox servers that are running Windows Server 2008 Enterprise or Windows Server 2008 Datacenter.
To add to this all you need is Window server 2008 Enteprise Edition not Exchange 2010 Enterprise This statement is wrong. The only difference between Exchange 2010 Standard and Enterprise is the number of Mailbox Databases it can host. Standard can host up to 5 databases whereas Enterprise can host up to as many as 100. So, is you want to use DAG functionality and can get by with 5 databases, Standard Edition of Exchange 2010 is fine.
Because DAGs rely on Windows Failover Clustering, they can only be created on Exchange 2010 Enterprise Edition Mailbox servers that are running Windows Server 2008 Enterprise or Windows Server 2008 Datacenter.
This statement is wrong. The only difference between Exchange 2010 Standard and Enterprise is the number of Mailbox Databases it can host. Standard can host up to 5 databases whereas Enterprise can host up to as many as 100. So, is you want to use DAG functionality and can get by with 5 databases, Standard Edition of Exchange 2010 is fine.
To add to this all you need is Window server 2008 Enteprise Edition not Exchange 2010 Enterprise
I thought that was what I was saying.
_____________________________
Jesper Bernle | Microsoft Community Contributor 2011 Awardee
|
My Subscription |
My Forums |
Address Book |
Member List |
Search |
FAQ |
Ticket List |
Log Out
Printable Version
All Forums >> [Microsoft Exchange 2010] >> High Availability >> DAG in Exchange 2010 
DAG in Exchange 2010 - 
RE: DAG in Exchange 2010 - 
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
