System Center
United States (English) Sign in
Home 2012 Previous Versions Library Forums Gallery
1 out of 2 rated this helpful - Rate this topic

Setting up the DPM database

Updated: January 15, 2013

Data Protection Manager (DPM) requires an instance of SQL Server to host the DPM database. You can use SQL Server 2012, SQL Server 2008 R2 (available on the System Center 2012 SP1 DVD) or SQL Server 2008 R2 with SP1. The setup wizard allows you to setup and configure an instance of SQL Server for use by DPM or you can use an existing instance to host the DPM database. In either case, DPM allows you to either have a local instance of the database for each installation of DPM or a shared instance which is used by multiple DPM servers.

On the prerequisites page of the DPM setup wizards you can choose how you want to setup your database.

Use the dedicated instance of SQL Server: Use this option to install or connect to a local instance of SQL Server to host the DPM database. If you want to use a new instance of SQL Server, DPM allows you to install SQL Server 2008 R2 from the System Center 2012 SP1 DVD and host the DPM database on this instance. On the other hand, if you want to use an existing local instance of SQL Server on the computer that you are installing DPM, you can use that instance to host the DPM database.

Use an existing instance of SQL Server: Use this option to connect to a remote instance of SQL Server that is being shared across multiple DPM servers.

ImportantImportant
When using a remote instance of SQL Server, you must make sure of the following:

  • Enable remote procedure calls (RPC) on the computer on which SQL Server is installed.

  • The remote instance of SQL Server is not on a domain controller.

  • The computer running SQL Server is in the same domain as the DPM server.

  • When you install DPM and specify the remote instance of SQL Server, Setup creates the DPMDBReaders$<DPM server name> and DPMDBAdministrators$<DPM server name> local groups on the computer where the remote instance of SQL Server is installed.

  • For the DPM server to access a remote instance of SQL Server through Windows Firewall, on the remote computer, you must configure an incoming exception for sqlservr.exe for the specific instance that you use for the DPM database to allow use of the TCP protocol on port 80.

  • After the installation of SQL Server is complete, enable the TCP/IP protocol for the specific instance that you use for the DPM database.

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

To install DPM using a local SQL Server instance

  1. Log on to the computer that will be your DPM server using a domain user account that is a member of the local Administrators group.

  2. Start Setup.

  3. In the SQL server settings section, click Use an existing instance of SQL Server, and then click Check and Install.

  4. On the Security Settings page, specify and confirm a strong password for the restricted MICROSOFT$DPM$Acct and DPMR$<computer name> local user accounts, and then click Next.

    To enhance security, setup creates the following low-privileged local user accounts:

    • MICROSOFT$DPM$Acct to run the SQL Server and SQL Server Agent services.

    • DPMR$<computer name> to generate DPM reports by using SQL Server Reporting Services.

    A strong password is typically defined as a password that is at least six characters long, does not contain all or part of the user’s account name, and contains at least three of the following four categories of characters: uppercase characters, lowercase characters, base 10 digits, and symbols (such as !, @, #).

    noteNote
    The password that you specify for these accounts does not expire.

To install DPM using a remote instance of SQL Server

  1. Log on to the DPM server with a domain user account that is a member of all the following:

    • The local Administrators group on the DPM server

    • The SQL Server Sysadmin fixed server role on the computer running the remote instance of SQL Server

    noteNote
    After setup is complete, you can remove the user account from the local Administrators group on the computer running the remote instance of SQL Server.

  2. Start setup.

  3. On the System Center 2012 – Data Protection Manager (DPM) screen, click Install Data Protection Manager.

  4. On the Prerequisite Checks page, in the Instance of SQL Server box, type the name of the remote SQL Server instance as <Computer Name>\<Instance Name>, and then type the credentials for a domain user account that is a member of both the local Administrators group and the SQL Server Sysadmin fixed server role on the computer where the remote instance is installed.

    noteNote
    After setup is complete, you can remove the user account from the local Administrators group.

noteNote
A restart is necessary to start the volume filter that DPM uses to track and transfer block-level changes between DPM and the computers it protects, or between the primary and secondary DPM servers.

After installation, your DPM database will be named DPMDB_<DPMServername> or DPMDB_<DPMServername><GUID>.

After you install DPM, you must perform some required configuration tasks before you can start protecting your data. For more information, see Required Configuration Tasks

ImportantImportant
Do not use localized characters in the computer name if you want to install DPM using SQL Server remotely.

-----
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.
-----
Did you find this helpful?
(1500 characters remaining)
© 2013 Microsoft. All rights reserved.