Configure SQL Server protection
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
This topic provides the information that you should consider when you’re planning to protect a Microsoft SQL Server database by using Data Protection Manager (DPM).
Which SQL Server versions and functionality does DPM support?
SQL Server 2005
SQL Server 2008
SQL Server 2008 R2
SQL Server 2012
SQL Server 2014
In a SQL Server clustering deployment that is protected by a DPM server, when the instance of SQL Server fails over to another node, the DPM server will continue to protect the primary node of the SQL Server cluster without intervention from backup administrators.
DPM is cluster aware when it is protecting a SQL cluster. DPM is aware of the cluster’s identity in addition to the nodes in the cluster. In a SQL clustering scenario, if the instance of SQL Server is changed to a different node, DPM will continue to protect the SQL cluster without any intervention from backup administrators.
When a DPM server is protecting a SQL Server database that is mirrored, the DPM server is aware of the mirrored database and correctly protects the shared dataset.
SQL log shipping
In scenarios in which SQL Server log shipping is being used, DPM will automatically discover that log shipping is being used and will auto-configure itself to coexist. This makes sure of correct SQL protection.
When DPM is protecting SQL AlwaysOn, it will automatically detect availability groups. It will also detect a failover occurrence and will continue to protect the database.
For more information about SQL protection prerequisites, go to this page Prerequisites. We recommend that you read through the SQL Server prerequisites page before you set up your SQL protection.
Prepare DPM before you configure SQL Server protection
Before you set up SQL Server protection, you should make sure that you follow these steps:
Deploy DPM—Verify that DPM is installed and deployed correctly. If you do not have DPM deployed, go to the following links for guidance:
Set up storage—Check that you have storage set up. Read more about your options in the following articles:
Set up a protection group for the instance of SQL Server
In the DPM console click Protection
Click New to start the Create New Protection Group wizard.
On the Select Group Members page of the Create New Protection Group wizard, under Available members, expand your instance of SQL Server.
The instances of SQL Server on that server will be shown. You have the option of selecting protection at the instance level or protection of individual databases. Continue through the rest of the wizard to complete the setup of your SQL protection.
More information about creating protection groups can be found in this article Create and manage protection groups.
Note: When you are protecting at the instance level, any database that is added to that instance of SQL Server will automatically be added to DPM protection. See the following screen shot for an example of auto-protection at the instance level and of individual database protection.
Note: If you are using SQL Server AlwaysOn availability groups, you can create a protection group that contains the availability groups. The DPM server detects the availability groups and will display them under Cluster Group. Select the whole group to protect it so that any databases that you add to the group are protected automatically. You can also select individual databases instead of the whole group.
For each instance of SQL Server, you can also run a system state backup or full bare metal backup (this includes the system state). This in useful if you want to be able to recover your whole server and not just data. More information about protection groups and bare metal backup can be found in the following articles:
Then follow the instructions in Create and manage protection groups
After you create the protection group, initial replication of the data occurs. Backup then occurs in line with the protection group settings.
After the protection groups are created, the initial replication occurs, and DPM starts backing up and synchronizing the SQL Server data. You can use DPM to monitor the initial synchronization and successive backups in the following ways:
Using default DPM monitoring can set up notifications for proactive monitoring by publishing alerts and configuring notifications. You can send notifications by email for critical, warning, or informational alerts, and for the status of instantiated recoveries.
If you have System Center Operations Manager (SCOM) deployed in the organization, you can use SCOM for deeper DPM monitoring and management. DPM monitoring and management in SCOM is sufficient in meeting your SQL protection monitoring needs. For more information, see this article: Manage and Monitor DPM.
Set up monitoring notifications
In the DPM Administrator Console, click Monitoring > Action > Options.
Click SMTP Server, and then 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 email address to which you want DPM to send the test message, and then click OK.
Click Options > Notifications, and then select the kinds of alerts about which recipients want to be notified. In Recipients, type the email address of each recipient to whom you want DPM to send copies of the notifications.
To test the SMTP server settings, click Send Test Notification > OK.