System Center Data Protection Manager (DPM) 2010 requires a SQL Server 2008 SP1 instance for the DPM database. During setup, you can choose to have DPM Setup install a new, dedicated SQL Server 2008 instance on the DPM server, or you can specify a supported remote SQL Server 2008 instance. For detailed instructions for installing SQL Server 2008 on a remote computer, see Installing a Remote Instance of SQL Server 2008. For a list of supported versions of SQL Server 2008, see DPM Server Software Prerequisites.

When you use a remote instance of SQL Server for DPM, note the following:

When installing a new remote instance of SQL Server for use with DPM, we recommend that you use the following SQL Server settings:

The following procedure explains how to install and configure a remote SQL Server 2008 instance for use by DPM.

To install and configure a remote SQL Server 2008 instance for DPM

  1. On the product media or network share, double-click setup.exe, and then in the SQL Server Installation Center, click Installation in the navigation pane on the left.

    If you are installing SQL Server 2008 on Windows Server 2008 R2, you will receive a compatibility warning when you begin Setup and again when you click Installation in the SQL Server Installation Center. In both instances, click Run program to continue installing SQL Server 2008.
  2. On the Installation page, click New SQL Server stand-alone installation or add features to an existing installation.

    The SQL Server 2008 Setup Wizard opens.

  3. On the Setup Support Rules page, review the status of the support rules and correct any failures before proceeding with the installation.

  4. On the Setup Support Files page, click Install, and then click Next.

  5. On the Feature Selection page, select the following features:

    • Database Engine Services and both of its sub-features

    • Reporting Services

    • Management Tools – Basic (also enables the Management Tools- Complete feature)

    • SQL Client Connectivity SDK

  6. Proceed to the Instance Configuration page, click Named instance, enter a name for the SQL Server instance, and then click Next.

  7. Proceed to the Server Configuration page, and then do the following: enter an account name, password, and startup type for each SQL Server service, and then click Next.

    When configuring the service accounts, consider the following:

    • For the SQL Server Browser and SQL Server Agent services, set the Startup type to Automatic.

    • We recommend that you use a separate dedicated domain user account for each service. However, the SQL Reporting Services service can be configured to run under the Network Service account.

    • Use the least-privileged user account on the computer running SQL Server.

  8. On the Database Engine Configuration page, accept Windows authentication mode as the authentication mode, and then click Add Current User in the Specify SQL Server administrators area.

  9. Retain the default settings on all subsequent pages, and then on the Ready to Install page click Install.

    Before you run SQL Server, install SQL Server 2008 Service Pack 1 (SP1) or later.
  10. Install the DPM Support Files on the SQL Server by performing the following steps:

    1. On the remote SQL Server computer, navigate to the SQLPrepInstaller folder on the DPM product DVD or the directory on a network share.

    2. Depending on the operating system running on the computer, right-click either SQLPrepInstaller_x64 or SQLPrepInstaller_x86, and then click Run as administrator.

    3. Follow the steps in the wizard, which installs Microsoft Visual C++ 2008 Redistributable.

  11. After the installation of the SQL Server instance is complete, do the following:

    • Ensure that the SQL Server Browser service is started.

    • If Windows Firewall is enabled on the SQL Server, ensure that an exception for port 80 is created for SQLServer.exe.

    • Remote connections are enabled on the SQL Server instance.

    • Click Start, click SQL Server 2008, click Configuration Tools, click Reporting Services Configuration Manager, and then ensure that both the Report Manager URL and Web service URL are accessible.

See Also