Considerations for Exchange Server 2010

Topics | Support

Overview

Support Information

Installation

Configuration

Feature Support

Overview

This section provides information about installing, configuring and using Exchange Agents for Exchange Server 2010. In general, Exchange Agents installed for Exchange Server 2010 behave the same as for Exchange Agents installed for other Exchange Server versions, with any differences noted in the following sections.

Support Information

See Considerations for Exchange Server 2010 - Support for information on the components supported with Exchange Server 2010.

Installation

Consider the following prior to deploying agents for Exchange Server 2010:

Exchange Database iDataAgent

The Exchange Database iDataAgent for Exchange Server 2010 must be installed on a 64-bit computer that hosts the Exchange Server 2010 application with the Exchange 2010 Mailbox Server role. To install this iDataAgent, follow the procedure to Install the Exchange iDataAgents and select the iDA for Exchange 2010 Database option on the Select Platforms dialog during the installation.

DAG Configurations

For DAG configurations, the Exchange Database iDataAgent must be installed on each physical node of the DAG group.

In a configuration where a CAS server (or another proxy configuration) will be used to back up multiple DAG nodes, the CAS server should be used to configure the Exchange profile information during install. After the installation is complete, configure the multiple exchange server names separated by semi colons in the Exchange iDataAgent's Agent properties.

Other Exchange-Based Agents

The following Exchange Agents must be installed as 32-bit components on a Microsoft Windows x64 platform. See Install 32-bit Exchange Agents on a Windows x64 Platform for step-by-step instructions.

• Exchange Mailbox iDataAgent
• Exchange Compliance Archiver Agent
• Exchange Mailbox Archiver Agent

Follow the steps provided below to install the Exchange Server 2010 Agents on a 32-bit off-host proxy computer. These steps apply to all Exchange-based agents for Exchange Server 2010 except the Exchange Database iDataAgent .

1. Add the remote computer to the same Domain in which the Exchange Server 2010 resides.
2. Install the appropriate Exchange Server Agent using the steps outlined in the following procedures:
   • Install the Exchange Agents for Exchange Server 2007/2010 on 32-bit Off-host Proxy
   • Install the Exchange Agents on Exchange Server 2007/2010 or 64-bit Off-host Proxy

Configuration

Consider the following configuration details for Exchange Server agents using Exchange Server 2010:

General

The Exchange Agent can be installed on the Client Access Role server or on a proxy server. In either case, Outlook 2007 or higher is required.

DAG Configurations

• For all other components, DAG is supported by adding each DAG server name separated by a semi-colon (;) in the Agent-level Properties dialog.
• In environments where the mailbox role is on a different server from the Client Access Role, use the sCASServerName registry key with a STRING value of <Client_Access_Role_Server_Hostname> to allow for profile recreation following a data protection job.

Feature Support

• The Exchange Mailbox iDataAgent and Exchange Mailbox Archiver Agent, for Exchange Server 2010, do not support auto-discovery by storage group affinity.

DAG Configurations

Backup

• Backups are supported only from the DAG active database copy. Backups from the DAG passive database copy are not supported.
• If a failover occurs, a full backup must be performed on the active node.

Restore

• Two restore options are available for DAG configurations:
  1. Restore the active database copy. Then, reseed the active database copy for all passive database copies.
  2. Restore the active database copy and all passive database copies from the same backup data set.
• The mailbox database copy must be suspended manually prior to performing a restore to a passive DAG database copy.
• Restores to an alternate database, including other Exchange servers, are supported.
• When restoring a passive copy to an active copy, an out-of-place restore destination is not required. Only the destination client must be selected.

Back to Top