Export (0) Print
Expand All
1 out of 1 rated this helpful - Rate this topic

Installing a Remote Instance of SQL Server 2008

Updated: July 2, 2010

Applies To: System Center Data Protection Manager 2010

System Center Data Protection Manager (DPM) 2010 requires an instance of SQL Server 2008 SP1 for the DPM database. During setup, you can choose to have DPM Setup install a dedicated instance of SQL Server on the DPM server, or you can specify a remote instance of SQL Server. 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:

  • The remote instance of SQL Server must be running SQL Server 2008 with Service Pack 1 (SP1), Standard or Enterprise Edition.

  • The remote instance of SQL Server cannot be installed on a domain controller.

  • The computer running SQL Server must be located in the same domain as the DPM server.

  • When you install DPM and specify the remote instance of SQL Server, DPM 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 Named Pipes protocol for the specific instance that you use for the DPM database.

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

  • The default failure audit setting.

  • Enable password policy checking.

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

To install and configure a remote instance of SQL Server 2008 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.

    noteNote
    If you are installing SQL Server 2008 on Windows Server 2008 R2, you might receive a compatibility warning when you begin setup and again when you click Installation in the SQL Server Installation Center. In both cases, 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, click Show details, review the status of the support rules and correct any failures before proceeding with the installation. When all rules have passed, click OK.

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

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

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

    • Database Engine Services and both subfeatures, SQL Server Replication and Full-Text Search

    • Reporting Services

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

    • SQL Client Connectivity SDK

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

  8. Proceed to the Server Configuration page, and then use the following table to configure the SQL Server services.

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

    Create a domain user account with the lowest possible privileges, assign it a strong password that does not expire, and then add it to both the local Administrators group and to the SQL Server Sysadmin fixed server role in a later step.

    You can name this user account anything that you want; however, for the purposes of easily identifying the account’s purpose, you might want to give it a significant name, such as DPMSQLSvcsAcct.

     

    SQL Server service Configuration

    SQL Server Agent

    Enter the name and password of a domain account that you want this service to run under, and then set the Startup type to Automatic.

    SQL Server Database Engine

    Enter the name and password of a domain account that you want this service to run under. Do not change the default Startup type.

    SQL Server Reporting Services

    Enter the name and password of a domain account that you want this service to run under. Do not change the default Startup type.

    SQL Full-text Filter Daemon Launcher

    Do not change the default settings.

    SQL Server Browser

    Change the default Startup type to Automatic.

  9. On the Database Engine Configuration page, accept Windows authentication mode as the authentication mode, and then, in the Specify SQL Server administrators area, add to the SQL Server administrators group the user account that you will use to connect to the remote instance of SQL Server when you install DPM. To add your own user account, click Add Current User. You can add additional user accounts if needed.

    ImportantImportant
    Ensure that the user account you plan use to connect to the remote SQL Server when you install DPM is added to the SQL Server administrators group and to the local Administrators group.

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

    ImportantImportant
    If you are not installing SQL Server 2008 SP1from a slipstreamed installation source, before you run SQL Server for the first time, install SQL Server 2008 Service Pack 1 (SP1) or later. For more information, see How to identify your SQL Server version and edition (http://go.microsoft.com/fwlink/?LinkId=188814).

  11. Install the DPM support files on the SQL Server computer by performing the following steps:

    ImportantImportant
    If you are using this procedure to upgrade to DPM 2010 RTM from DPM 2010 RC, you must install the RTM version of the DPM support files.

    1. On the remote SQL Server computer, navigate to the SQLPrepInstaller folder on the root directory of the DPM product DVD or 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 to install Microsoft Visual C++ 2008 Redistributable.

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

    • If Windows Firewall is enabled on the SQL Server computer, you must configure an incoming exception for sqlservr.exe to allow use of the TCP protocol on port 80 for each specific instance that you use for a DPM database.

      1. In Control Panel, click Windows Firewall, click Advanced Settings, right-click Inbound Rules, and then click New Rule.

        The New Inbound Rule Wizard opens.

      2. On the Rule Type page, click Program, and then click Next.

      3. On the Program page, click This program path, click Browse, and then navigate to sqlservr.exe at the following location:

        <system drive>:\Program Files\Microsoft SQL Server\MSSQL10. <Instance Name>\MSSQL\Binn

      4. On the Action page, click Allow the connection, and then click Next.

      5. On the Profile page, clear the Private and Public check boxes, and then click Next.

      6. On the Name page, type a name and optionally a description for the rule, and then click Finish.

      7. In the Inbound Rules list, right-click the new rule, click Properties, and then click the Protocols and Ports tab.

      8. In the Protocols list, click TCP, and in the Local ports list, click Specific ports, type 80, and then click OK.


    • You must enable the Named Pipes protocol for the instance of SQL Server that you installed for the DPM database.

      Open SQL Server Configuration Manager, expand SQL Server Network Configuration, click Protocols for the specific instance that you will use for the DPM database, right-click Named Pipes, and then click Enable.

      ImportantImportant
      For this change to take effect, you must stop and restart the SQL Server service.

    • Ensure that the URLs for the instance of SQL Server are accessible.

      Click Start, click SQL Server 2008, click Configuration Tools, click Reporting Services Configuration Manager, connect to the local instance, and then in the Connect pane, click Report Manager URL and Web Service URL respectively, and then click each URL to ensure that both are accessible.

See Also

Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft. All rights reserved.