High availability solution in exchange 2010

HIGH AVAILABILITY SOLUTION IN EXCHANGE 2010

Mailbox databases and the data they contain are one of the most critical components (if not the most critical component) of any Microsoft Exchange organization. In Microsoft Exchange Server 2010, you can protect mailbox databases and the data they contain by configuring your mailbox databases for high availability and site resilience. Exchange 2010 reduces the cost and complexity of deploying a highly available and site resilient messaging solution while providing higher levels of end-to-end availability and supporting large mailboxes. Building on the native replication capabilities introduced in Microsoft Exchange Server 2007, the new high availability architecture in Exchange 2010 provides a simplified, unified framework for high availability and site resilience. Exchange 2010 integrates high availability into the core architecture of Exchange, enabling customers of all sizes and in all segments to be able to economically deploy a messaging continuity service in their organization.

  Key Terminology

A high availability solution is a solution that provides service availability, data availability, and automatic recovery from failures that affect the service or data (such as a network, storage or server failure).

Disaster recovery is any process used to manually recover from a failure. This can be a failure that affects a single item, or it can be a failure that affects an entire physical location.

Site resilience is a manual disaster recovery process that used to recover from a complete site failure. Using Exchange 2010, you can configure your messaging solution for high availability and enable site resilience using the built-in features and functionality described in this content area.

*over (pronounced "star-over") is short for switchovers and failovers. A switchover is a manual activation of one or more databases. A failover is an automatic activation of one or more databases after a failure.

Mailbox Resiliency is the name of unified high Availability and site resilience solution in Exchange 2010.

Database Mobility is the ability of a single Exchange 2010 mailbox database to be replicated to and mounted on other Exchange 2010 Mailbox servers.

Incremental Deployment is the ability to deploy high availability /site resilience after Exchange 2010 is installed.

The Exchange Third Party Replication API is an Exchange-provided API that enables use of third-party synchronous replication for a DAG in lieu of continuous replication.

A Database Availability Group is a group of up to 16 Exchange 2010 Mailbox servers that host a set of replicated databases.

A Mailbox Database Copy is a mailbox database (.edb file and logs) that is either active or passive.

A Lagged Mailbox Database Copy is a passive mailbox database copy that has a log replay lag time greater than zero.

The RPC Client Access service is a new service that provides a MAPI endpoint for Outlook clients.

Shadow Redundancy is a transport server feature that provides redundancy for messages for the entire time they are in transit.