Configuring Exchange Server 2010 DAG

Microsoft Professional Advisory Services is a support option that provides short-term, proactive, consultative support beyond break-fix product maintenance needs. This includes working with the same technician for assistance with issues like product migration, code review, or new program development and is a remote, phone-based support option. This service is typically used for shorter engagements, and is designed for developers and IT professionals who do not require the traditional onsite consulting or sustained account management services that are available from other Microsoft support options.

For additional information on Microsoft Advisory Services, including on how to engage, refer to this Microsoft web page:

http://support.microsoft.com/gp/AdvisoryService

Assists customers with setup of Exchange Server 2010 Database Availability Group(s) (DAG).The purpose of this document is to assist the Pro-Advisory Support Engineer in scoping a case in which a customer is planning to deploy Exchange Server 2010 Database Availability Group(s) (DAG).

Configuration will involve the following phases:� Planning, Deployment, and Finalizing.

• Planning: understanding the environment and suggesting the requirements for high availability.
• Deployment: setup of the DAG and adding the member node.
• Finalization: test if the DAG is successfully running.

This document will help in better understanding the environment and defining the course of action.

Assumptions

• The current Exchange Server environment is configured properly per the Exchange Pre-Deployment Analyzer (ExPDA), and is healthy as determined by a full Exchange Best Practice Analyzer (ExBPA) health check and is ready for deploying Exchange Server 2010. If this is the first Exchange Server 2010 deployment then it is assumed that all the pre-requisite are taken care as determined by the Exchange 2010 Deployment Assistant.
• The server environment meets the requirement as per the Planning for Exchange 2010 TechNet article. Any other issues need to be resolved via separate break/fix incidents. It is highly recommended that the customer perform the ExBPA health check and resolve any issues prior to beginning work on the advisory case scope. If any unexpected break/fix issues arise while working on the scoped issue, a maximum of thirty (30) minutes will be spent troubleshooting the other issues. This will be billed to the current advisory case. If the issue is not resolved in thirty (30) minutes the customer must open a new break/fix support case, at additional cost, to address the problem.� The Professional Advisory Support Engineer may work that break/fix support case at their discretion.
• The current environment meets all prerequisites for installing Exchange Server 2010 as per the Exchange 2010 Prerequisites TechNet article. This includes all Active Directory & DNS configuration requirements as per the Planning Active Directory TechNet article.
• The scenarios where disjoint namespace are supported for Exchange Server 2010 are as per the Understanding Disjoint Namespace Scenarios TechNet article.
• The storage architecture and configuration should be as per these TechNet articles: Understanding Storage Configuration, Mailbox Server Processor Capacity Planning, Exchange 2010 Mailbox Server Role Requirements Calculator and Updates to the Exchange 2010 Mailbox Server Role Requirements Calculator.

Scoping Questions

1. Topology documentation:

• How many AD sites, domains, and DC/GC�s are present in the environment (list names)?
• How the AD sites are connected (network topology) (list names)?
• Are any servers in a perimeter network (DMZ)?� Note: Exchange Server 2010 does not support CAS, HUB or MBX server roles in a perimeter network.� The only server role supported in a perimeter network is the EDGE role.
• How is the storage architecture designed?

2. How do you want to configure DAG?� Refer to these TechNet articles:

• Installation Guide Template - DAG Member
• High Availability and Site Resilience Note: DAG with Site Resilience configurations are not covered under Professional Advisory support scenarios.
• Database Availability Group Design Examples
  
  o�� Two-member DAG in single datacenter/Active Directory site - Both members are in the same datacenter.
  
  o�� Four-member DAG in a single datacenter/Active Directory site - All four-members are in the same datacenter.
  
  o�� Four-member DAG in two datacenters/Active Directory sites - Two members in the primary datacenter and two in the second datacenter.

Guidance Questions

There are many different design dimensions that have to be considered when designing for high availability with Exchange Server 2010. Due to these new sizing factors, additional steps are required to size mailbox servers when configured for Mailbox Resiliency.

• The locality of the users will ultimately determine the DAG architecture
  
  a.������ Are users primarily located in one datacenter?
  
  b.����� Are users located in multiple datacenters?
  
  c.������ Is there a requirement to maintain user population in a particular datacenter?
  
• What kind of a solution are you looking for?
  
  a.������ Mailbox Resiliency or stand alone?�
  
  b.����� Site resiliency?
  
• Database Availability Group design
  
  a.������ How many DAGs should I deploy?
  
  b.����� How many members should be in a DAG?
  
  c.������ How many database copies you plan to activate on a per server basis when configured for Mailbox Resiliency?
  
  d.����� What types of database copies do you want to deploy? HA database copies or Lagged database copies.

You can use the information in the Mailbox Server Processor Capacity Planning TechNet article to better understand the design guidance for sizing mailbox servers when configured for mailbox resiliency.

DAG design examples are listed in the Database Availability Group Design Examples TechNet article and here:

• Two-member DAG in single datacenter/Active Directory site - Both members are in the same datacenter.
• Four-member DAG in a single datacenter/Active Directory site - All four-members are in the same datacenter.
• Four-member DAG in two datacenters/Active Directory sites - Two members in the primary datacenter and two in the second datacenter.

Note: DAG with Site Resilience configurations are not covered under Professional Advisory support scenarios.

1. Verify the operating system prerequisites for Mailbox Servers are installed.
   
   • Microsoft .NET Framework 3.5 Service Pack 1 �
     
   • Update for the .NET Framework 3.5 Service Pack 1 �
     
   • Windows Management Framework
     ��
   • On servers that will host the Hub Transport or Mailbox server role, install the Microsoft Filter Pack 2007 Office System Converter: Microsoft Filter Pack
2. Configure the NIC for both the MAPI network and Replication network. It is recommended that each DAG have at least 2 networks � one for MAPI and one for the Replication network.
   
   a.������ Configuring Network Protocols and Components
   
   b.����� Modify the Protocol Bindings Order�
   
   c.������ Planning for High Availability and Site Resilience
   
3. Configure the DAG Witness Server and the Witness Directory:
   
   ��������� Create the witness directory and share on the Witness Server
   
   ��������� A Witness Server must not be the member of DAG
   
   ��������� The Witness Server can be any Windows Server operating system and need not be same as the DAG members
   
   Note: If the witness server you specify isn't an Exchange 2010 server, you must add the Exchange Trusted Subsystem universal security group to the local Administrators group on the Witness Server. These security permissions are necessary to ensure that Exchange can create a directory and share on the Witness Server as needed: Create a Database Availability Group.
   
4. Deploy & configure DAG:
   
   a.������ Pre-stage the Cluster Network Object for a Database Availability Group
   
   b.����� Understanding Database Availability Groups
   
   c.������ Create a Database Availability Group.�
   
5. Configure DAG properties and add members� to the DAG: Configure Database Availability Group Properties
   
6. Create DAG network: Create a Database Availability Group Network
   
7. Configure/verify DAG network properties: Configure Database Availability Group Network Properties
   
8. Add mailbox database copy: Managing Mailbox Database Copies
   
9. Configure mailbox database copies: Configure Mailbox Database Copy Properties
   
10. Verify the solution:
    
    ��������� Monitoring High Availability and Site Resilience
    
    ��������� Managing High Availability and Site Resilience

Below is a list of self-help resources or this scenario. These resources may also be used by Microsoft Support Engineers during an Advisory Services engagement.

Planning

Understanding Database Availability Groups

High Availability in Exchange Server 2010

Database Availability Group Design Examples

Understanding Active Manager

Understanding Mailbox Database Copies

Mailbox Server Storage Design

Planning for High Availability and Site Resilience

Understanding Datacenter Activation Coordination Mode


Deployment

Create a Database Availability Group

Manage Database Availability Group Membership

Configure Database Availability Group Properties

Understanding Datacenter Activation Coordination Mode

Configure Database Availability Group Network Properties

Add a Mailbox Database Copy

Deploying High Availability and Site Resilience


Finalization

Managing Database Availability Groups

Monitoring High Availability and Site Resilience

Monitoring Exchange 2010

Switchovers and Failovers

Activate a Mailbox Database Copy

Perform a Server Switchover

Installing Update Rollups on Database Availability Group Members

Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use for other considerations.