In this article I describe one method for moving from a single Exchange Server 2010 server into a high availability topology with a CAS array and Database Availability Group.
This tutorial demonstrates the recovery process for removing a failed Mailbox server from a Database Availability Group, reinstalling the server, and returning the DAG to its original state.
When an Exchange Server 2010 Mailbox server that is a member of a Database Availability Group has failed, part of the recovery process is to remove it from DAG membership. In some scenarios this process may result in an error.
When Windows Server Backup is used to back up an Exchange Server 2010 Mailbox server that a a member of a Database Availability Group the backup result may report “Completed with warnings”.
When a mailbox database copy has failed in an Exchange Server 2010 Database Availability Group (DAG) it may be necessary to reseed the mailbox server with the failed database copy.
After an outage or maintenance to the Mailbox servers in a Database Availability Group you may find that the mailbox databases are no longer balanced across all of the DAG members.
Microsoft Exchange Server 2010 introduced a new high availability feature called the Database Availability Group (DAG). This tutorial describes how Database Availability Groups work in Exchange Server 2010, as well as demonstrating the steps for deploying a DAG using Exchange Server 2010 SP1 and Windows Server 2008 R2.
In this video I demonstrate the end user experience during different failure scenarios in a highly available Exchange Server 2010 environment.