Exchange Server 2010 prerequisites
Updated: May 13, 2016
Applies To: System Center 2012 SP1 - Data Protection Manager, System Center 2012 - Data Protection Manager, System Center 2012 R2 Data Protection Manager
Before you deploy DPM to protection Microsoft Exchange Server 2013 verify the deployment prerequisites:
Read about the Exchange versions that DPM 2012 can support in DPM protection support matrix.
Install the Exchange Server management tools on the DPM server.Ensure you install the management tools for the latest version of Microsoft Exchange that you are protecting.
Make sure the same versions of Eseutil.exe and Ese.dll are installed on both the Exchange Server and the DPM server. For example, if you’re using the 64-bit version of DPM, you must have the 64-bit version of eseutil.exe and ese.dll. If you update these files on the Exchange server you’ll need to update them on the DPM server too. The .ese and .eseutil files are usually in C:\Program Files\Microsoft\Exchange Server\V15\Bin folder.
To maintain up-to-date copies do the following:
At the command prompt, navigate to the <DPM installation folder>\Bin directory.
Type the fsutil command as follows to create a hard link for eseutil.exe: fsutil hardlink create <link> <target>
For example in a typical installation type: fsutil hardlink create “c:\program files\microsoft\dpm\bin\eseutil.exe” “c:\program files\microsoft\Exchange\bin\eseutil.exe”.
To protect an Exchange Server Database Availability Group (DAG) node, install the DPM protection agent on the node. Note that you can protect different DAG nodes from different DPM servers, only one node can be protected by one DPM server only.
You can protect up to 80 terabytes (TB) of data with a single DPM server. Therefore, you can protect DAGs that have up to 20 nodes with a single server or up to 10,000 mailboxes with a DPM server.
DPM functions with any database role. You can configure DPM to protect a server that hosts a collection of active or passive mailbox databases.
You should configure at least one full backup per day and a synchronization frequency to suit your requirements for Exchange log truncations When you protect more than one copy of an Exchange mailbox database (for example, when you are protecting multiple members of a DAG), you should configure one node for full backups and the rest for copy backups. Copy backups do not truncate log files.
Protect at least two copies of each mailbox database whether Exchange Server is implemented with inexpensive Serial ATA (Serial Advanced Technology Attachment or SATA) or several disks/drives (JBOD) disks.
Set the minimum frequency to greater than 15 minutes for mailbox synchronization. Start by setting up your current backup policy, and then gradually increase the number of recovery points. Performing one or two express full backups per day, in addition to a synchronization frequency of two hours, is a sound approach. For an optimal synchronization frequency consider the volume of your data, the performance impact, and the volume required to store the replicas.
As you maintain your Exchange data note the following:
Add mailbox databases to the server. If you create or add new mailbox databases to a protected storage group on an Exchange server, these databases are automatically added to the DPM replication and protection. You can add mailbox databases in incremental backups only after a full backup has finished.
Change mailbox database file paths. If you move a protected database or log files to a volume that contains data that is protected by DPM, protection continues. If you move a protected database or log files to a volume that is not protected by DPM, an alert appears, and the protection jobs fail. To resolve the alert, in the alert details, click the Modify protection job link, and then run a consistency check.
Dismount mailbox databases. If you dismount a protected mailbox database, the protection job for that particular database fails. The replica is marked inconsistent when DPM runs the next express full backup.
Rename mailbox databases. If you need to change the name of the mailbox database, stop protection, and protect the database again. Until you protect the database again, the backups continue to work but mailbox enumeration fails.