Was this page helpful?
Additional feedback?
1500 characters remaining
Export (0) Print
Expand All

Configure SQL Server protection


Applies To: System Center 2012 SP1 - Data Protection Manager, System Center 2012 - Data Protection Manager, System Center 2012 R2 Data Protection Manager

This topic provides important information that you should consider when planning to protect SQL Server data with System Center 2012 – Data Protection Manager (DPM), or DPM 2012 R2.

Read through SQL Server prerequisites before you set up protection.

  1. Deploy DPM—Verify that DPM is installed and deployed correctly. If you haven’t see:

  2. Set up storage—Check that you have storage set up. Read more about your options in:

  3. Set up the DPM protection agent—The agent needs to be installed on the SQL Server. Read Plan for protection agent deployment, and then Set up the protection agent.

  4. Set up a protection group—In the Select Group Members page of the Create New Protection Group wizard. You can create protection groups that contain Availability Groups. DPM shows the Availability Groups under Cluster Group. Select the whole group to protect it so that any databases you add to the group are protected automatically. To protect the selected databases in a group, expand the group name and select the individual databases that you want to protect. For each SQL 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:

  5. After you create the protection group initial replication of the data occurs. Backup then takes place in line with the protection group settings.

After the protection group’s been created the initial replication occurs and DPM starts backing up and synchronizing the SQL Server data. DPM monitors the initial synchronization and subsequent backups. You can monitor the SQL Server 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

  1. In the DPM Administrator Console, click MonitoringActionOptions.

  2. Click SMTP Server, type the server name, port, and email address from which notifications will be sent. The address must be valid.

  3. 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.

  4. 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.

  5. To test the SMTP server settings, click Send Test NotificationOK.

Publish alerts for Operations Manager

  1. In the DPM Administrator Console, click MonitoringActionOptions.

  2. In Options click Alert PublishingPublish Active Alerts.

  3. 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.

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
© 2015 Microsoft