Plan the DPM database
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
DPM needs a SQL Server database running any of the following 64-bit versions of SQL Server:
SQL Server 2012 with SP1 Standard or Enterprise
SQL Server 2012 Standard or Enterprise
SQL Server 2008 R2 with SP2 Standard or Enterprise
SQL Server 2008 R2 with SP1 2012 Standard or Enterprise
You can use either of the following:
Local SQL Server—You can run SQL Server collocated on the DPM server.
If you’re deploying DPM 2012 R2 you’ll need to install SQL Server on the DPM server before you run DPM setup.
If you deploy DPM 2012 or DPM 2012 with SP1 you have the option of installing SQL Server on the DPM server before you run DPM setup, or you can use the instance of SQL Server 2008 R2 that comes as part of the DPM installation files. If you want to use this option you don’t need to set anything up before you start DPM setup.
Remote SQL Server—If you want to use a remote instance of SQL Server you’ll need to set it up before you start DPM setup. Note that:
The server running SQL Server and the DPM server should be located in the same domain.
Enable RPC on the remote SQL Server.
The remote instance of SQL should not be running on a domain controller.
The remote instance of SQL Server should be running the following components only:
SQL Server Database Engine
Reporting Services
The remote instance of SQL Server should not run as Local System.
If you’re running DPM deployed as an Azure virtual machine (supported from DPM 2012 R2 Update 3 onwards) you can use an Azure virtual machine running SQL Server as the remote SQL Server database. You can’t use an on-premises SQL Server, and currently Azure SQL Database isn’t supported.
Next steps