Export (0) Print
Expand All

Prepare the DPM database

Updated: August 13, 2014

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

Data Protection Manager (DPM) needs an instance of SQL Server for its database. You can use a remote instance of SQL Server, or a local instance of SQL Server running on the DPM server.

SQL Server for DPM 2012 or 2012 with SP1

DPM in System Center 2012 or 2012 with SP1 can use the following 64-bit versions of SQL Server as a database:

  • SQL Server 2012 (for DPM 2012 with SP1 only)

  • SQL Server 2008 R2 with SP1

  • SQL Server 2008 R2 (available on the DPM DVD)

During DPM setup you can select to use a local SQL Server instance collocated on the DPM server, or a remote instance of SQL Server that can be shared by multiple DPM servers.

  • If you want to use a remote instance you’ll need to have that up and running before you run DPM setup.

  • If you want to use a local instance you can either install one on the DPM server before you run setup, or DPM will automatically install a local instance of SQL Server 2008 R2.

  • With System Center 2012 licenses you can install and run SQL Server Standard edition instances to support System Center 2012 products. However, these instances may not be used for other workloads.

  • If DPM automatically installs a local version of SQL Server 2008 R2 it installs a number of programs that aren’t required for DPM. These won’t be removed if you uninstall DPM at some point:

    • Microsoft SQL Server Compact 3.5 SP1

    • Microsoft SQL Server Compact 3.5 SP1 Query Tools

    • Microsoft SQL Server 2008 R2 Native Client

    • Microsoft Visual Studio Tools for Applications 2.0

    • Microsoft Office 2003 Web ComponentsP1

Set up local version of SQL Server 2012

If you’re running System Center 2012 SP1 and you want to configure DPM to use a local instance of SQL Server 2012, do the following in SQL Server 2012 Setup before installing DPM:

    1. On the Setup Role tab select SQL Server Feature Installation.

    2. On the Feature Selection tab select Database Engine Services. Then in Instance Features, select Reporting Service - Native.

    3. On the Instance Configuration tab specify the name of the instance that will be used for DPM.

    4. On the Server Configuration tab, in Service Accounts specify the account that the SQL Server services should run under:

      • We recommend that you use a single, dedicated domain user account to run the SQL Server services SQL Server Agent, SQL Server Database Engine, and SQL Server Reporting Services.

      • When you create a domain user account give it the lowest possible privileges, assign it a strong password that does not expire. You can give any name to the account. But give it a name that’s easily identifiable, such as DPMSQLSvcsAcc.

    5. On the Database Engine Configuration tab, use Windows authentication mode as the authentication method. In Specify SQL Server administrators, add the account you specified to the administrators list.

    6. In the Reporting Service Configuration tab, in Reporting Services Native Mode, select Install and configure to perform a default installation of reporting

  1. Note the following if you want to run a remote instance of SQL Server:

SQL Server requirements for DPM in System Center 2012 R2

DPM in System Center 2012 or 2012 with SP1 can use the following 64-bit versions of SQL Server as a database:

  • SQL Server 2012 with SP1

  • SQL Server 2008 R2 with SP2

In DPM in System Center R2 you’ll need an instance of SQL Server available locally on the DPM server or remotely, before you run DPM setup. DPM doesn’t install an local instance of SQL Server as part of setup. Note the following:

  • You must install the local or remote instance of SQL Server before you install DPM.

  • Running the remote instance on a domain controller isn’t supported.

  • The computer running the remote instance of SQL Server must be located in the same domain and time zone as the DPM server.

  • When you install DPM and specify the remote SQL Server instance, Setup creates the DPMDBReaders$<DPM server name> and DPMDBAdministrators$<DPM server name> local groups on the computer that is running the remote instance of SQL Server. You must add DPM administrators to these groups for DPM to use the remote instance of SQL Server.

  • For the DPM server to access a remote instance of SQL Server through Windows Firewall, you must configure an incoming exception for sqservr.exe for the DPM instance of SQL Server, to allow TCP on port 80.

  • After SQL Server installation is complete, enable the TCP/IP protocol for the DPM instance of SQL Server.

  • Use the following SQL Server settings: default failure audit, and enable password policy checking.

  • Using an instance of SQL Server running in a cluster is supported.

  • You cannot use a SQL Server AlwaysOn deployment.

  • On the remote SQL Server you’ll need to install the DPM support files (SQLprep). To do this, on the SQL Server computer insert the DPM DVD and start setup.exe. On the DPM installation menu select DPM remote SQL prep, and follow the wizard steps to install Microsoft Visual C++ 2012 Redistributable. The DPM support files will be installed automatically.

  • For information about setting up a remote SQL Server of DPM, see Set up a remote SQL Server database for DPM.

-----
For additional resources, see Information and Support for System Center 2012.

Tip: Use this query to find online documentation in the TechNet Library for System Center 2012. For instructions and examples, see Search the System Center 2012 Documentation Library.
-----
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft