Configure Exchange 2013 protection
Updated: May 13, 2016
DPM can back up Exchange 2013. You can back up Exchange data, and the Exchange server with a bare metal backup.
Before you start
Read through Prerequisitesbefore you set up protection.
Set up protection
Deploy DPM—Verify that DPM is installed and deployed correctly. If you haven’t see:
Set up storage—Check that you have storage set up. Read more about your options in:
Learn about short-term storage to disk and storage pools in Plan for disk backups
For storage to Azure with Azure Backup, see Plan for Azure backups
For long-term storage to tape, Plan for tape-based backups
Set up the DPM protection agent—The agent needs to be installed on the Exchange server. Read Plan for protection agent deployment, and then Set up the protection agent.
Set up a protection group—In the Select Group Members page of the Create New Protection Group wizard. You select all the DAGs that store data you want to protect. For each Exchange server you can also select to do a system state backup or full bare metal backup (which includes the system state. This in useful if you want the ability to recover your entire server and not just data.Read about protection groups and bare metal backup in:
Plan for protection group long-term and short-term protection
Back up and restore server system state and bare metal recovery (BMR)
Then follow the instructions in Create and manage protection groups. Note that when you run the New Protection Group Wizard you’ll be able to configure Exchange-specific settings the wizard.
After you create the protection group initial replication of the data occurs. Backup then takes place in line with the protection group settings.
Set up monitoring
After the protection group’s been created the initial replication occurs and DPM starts backing up and synchronizing the Exchange data. DPM monitors the initial synchronization and subsequent backups. You can monitor the Exchange data in a couple of ways:
Using default DPM monitoring can set up notifications for proactive monitoring. by publishing alerts and configuring notifications. You can send notifications by e-mail for critical, warning, or informational alerts, and for the status of instantiated recoveries.
If you use Operations Manager you can centrally publish alerts.
Set up monitoring notifications
In the DPM Administrator Console, click Monitoring > Action > Options.
Click SMTP Server, type the server name, port, and email address from which notifications will be sent. The address must be valid.
In Authenticated SMTP server , type a user name and password.The user name and password must be the domain account name of the person whose “From” address is described in the previous step; otherwise, notification delivery fails.
To test the SMTP server settings, click Send Test E-mail, type the e-mail address where you want DPM to send the test message, and then click OK. Click Options > Notifications and select the types of alerts about which recipients want to be notified. In Recipients type the e-mail address for each recipient to whom you want DPM to send copies of the notifications.
To test the SMTP server settings, click Send Test Notification > OK.
Publish alerts for Operations Manager
In the DPM Administrator Console, click Monitoring > Action > Options.
In Options click Alert Publishing > Publish Active Alerts.
After you enable Alert Publishing all existing DPM alerts that might require a user action are published to the DPM Alerts event log. The Operations Manager agent that is installed on the DPM server then publishes these alerts to the Operations Manager and continues to update the console as new alerts are generated.