How to provide a High Availably solution for two Exchange 2010 servers with DAG (Database Availability Groups)

Monday, May 28, 2012

A while ago I had a meeting with some IT senior consult that said to me that he use a workaround to provide High Availably solution for environment with two Exchange 2010 servers that hosting DAG (Database Availability Groups). His workaround was to point a A DNS record to the DAG Cluster name, and then assign it to the CAS Array name. However, this workaround isn't supported and may lead to unexpected downtime. To make things easier,  we can draw the following scenario: Exchange 2010 SP2 Servers: Server1 – MBX, HUB, CAS Server2 – MBX, HUB, CAS DAG Name:...

Exchange 2010 Database Availability Groups (DAGs) and Witness Server location – Design Considerations

Saturday, May 19, 2012

Exchange 2010 Database Availability Groups (DAGs) is an excellent solutions for customers that require to provide a high availability solution for the Exchange system.  However, some customers skip important design steps during Exchange 2010 Database Availability Groups (DAGs) deployment. The first common issue, is the Witness Server location. In most of the cases, the Witness Server should be reside near the Mailbox server that provide service to the local users. For example, in case that most of the users reside in New York, the Witness Server should be deployed in New York. The second common issue, is the amount...

Exchange 2010 DAG (Database Availability Group) Performance Optimization

Thursday, June 30, 2011

The following article provides a few tips and tricks to optimize Exchange 2010 DAG (Database Availability Group) performance. General 1. Use the latest Exchange 2010 Service Pack/Rollup, if it applicable. 2. Depend on the server hardware and drivers, you may need to disable the following settings: netsh int tcp set global chimney=disabled netsh int tcp set global rss=disabled 3. Use Microsoft recommendation for antivirus deployment in Exchange 2010 servers. CAS and DAG Optimization 1. Please remember that Exchange DAG wouldn't be useful without operational CAS server. So,...