Upgrading to DPM 2010 from DPM 2007 When Using a Remote Instance of SQL Server

  • Article

Applies To: System Center Data Protection Manager 2010

Use the procedures in this topic to upgrade to System Center Data Protection Manager (DPM) 2010 from DPM 2007 SP1 when using a remote instance of SQL Server 2008.

To upgrade to DPM 2010, we recommend that you install a new instance of SQL Server 2008 SP1, Standard or Enterprise Edition, instead of upgrading an existing instance of SQL Server 2005. For information about how to install a remote instance of SQL Server 2008, see Installing a Remote Instance of SQL Server 2008.

Important

Before you upgrade DPM, we strongly recommend that you back up your DPM 2007 database and store the backup file in a secure location. If your upgrade to DPM 2010 does not complete successfully, or if you need to go back to DPM 2007 SP1, you can roll back the upgrade without losing the benefit of protection that you previously had.

Use the following procedures to back up your DPM 2007 database and to restore it to the DPM 2010 database.

To back up the DPM 2007 database

  1. Log on to the computer where the remote instance of SQL Server 2005 is installed with a domain account that is a member of the local Administrators group and the SQL Server Sysadmin fixed server role.

  2. Open an elevated Command Prompt window, and then run the following commands:

    • cd <system drive> :\Program Files\Microsoft Data Protection Manager\DPM2010\SQLPrep

    • DPMBackup.exe –db –instanceName <instance name>

      where <instanceName> is the name of the instance of SQL Server for the DPM database.

      Note

      Do not include the computer name in the parameter <instanceName>.

    The DPM 2007 database backup file DPMDB.bak is located at <system drive>:\<instanceName>\DPMBackup.

  3. Store the backup file in a secure location. If you have to roll back your upgrade, you can restore your DPM 2007 SP1 database. For more information, see Rolling Back a DPM 2010 Upgrade.

  4. If you are installing SQL Server 2008 SP1 for the DPM 2010 database on a different computer, copy the DPM 2007 database backup file to that computer.

To restore the DPM 2007 database to the DPM 2010 database

  1. Install and configure a new instance of SQL Server 2008 SP1, Standard or Enterprise Edition, on the remote computer. For step-by-step instructions about how to install a remote instance of SQL Server 2008, see Installing a Remote Instance of SQL Server 2008.

  2. If you installed SQL Server 2008 SP1 on a different computer than SQL Server 2005, copy the DPM 2007 database backup file to that computer.

  3. On the computer on which you installed a new instance of SQL Server 2008 SP1, click Start, click All Programs, click Microsoft SQL Server 2008, right-click SQL Server Management Studio, and then click Run as administrator.

  4. In the Connect to Server dialog box, in the Server name box, type the computer name and instance name in the following format <Computer Name\Instance Name>, and then click Connect.

  5. Right-click the Databases folder, and then click Restore Database.

  6. In the Restore Database dialog box, do the following:

    1. In the Destination for restore area, in the To database box, type DPMDB.

    2. In the Source for restore area, click From device, and then click the ellipsis (...) button.

    3. In the Specify Backup dialog box, click Add, browse to the location of the DPM 2007 database backup file, and then click OK two times.

    4. In the Restore Database dialog box, in the Select the backup sets to restore list, select the Restore check box, and then click OK.

  7. After you have restored the database, you must synchronize the database. To synchronize the database, in DPM Management Shell or an elevated Command Prompt window, run the following command:
    dpmsync –sync

Preparing to Upgrade to DPM 2010 from DPM 2007 When Using a Remote Instance of SQL Server

Before you upgrade DPM, do the following:

  • If you are sharing a tape library across multiple servers that are running System Center Data Protection Manager (DPM) 2010, you must remove library sharing before you upgrade DPM. For step-by-step instructions for removing library sharing, see Removing Library Sharing.

  • Ensure that the domain user account you will use to install DPM 2010 is a member of all the following:

    • The local Administrators group on the DPM server

    • The local Administrators group on the computer on which you have installed the remote instance of SQL Server 2008 SP1

    • The SQL Server Sysadmin fixed server role on the computer on which you have installed the remote instance of SQL Server 2008 SP1

      Note

      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.

  • Verify the following:

Upgrading a 32-bit DPM Server that uses a Remote Instance of SQL Server

DPM 2010 requires a 64-bit computer; therefore, you cannot perform an in-place upgrade of DPM 2007 on a 32-bit computer. Use the following procedure to move DPM 2007 to a 64-bit computer.

After you have moved DPM 2007 to a 64-bit computer, follow the steps later in this topic to upgrade to DPM 2007 on the 64-bit computer to DPM 2010.

To move a 32-bit DPM server using a remote instance of SQL Server to a 64-bit computer

  1. Remove the 32-bit DPM server from the network.

  2. Install Windows Server 2008 R2 or Windows Server 2008 on a 64-bit computer that meets the hardware requirements for DPM 2010. For information about the DPM 2010 hardware requirements, see Hardware Requirements.

  3. Rename the 64-bit computer with the exact same name as the 32-bit DPM server that you removed from the network.

  4. Install DPM 2007 on the 64-bit computer.

    Note

    The DPM 2010 installation location should be the same as the DPM 2007 location on the 32-bit computer.

  5. To upgrade DPM 2007 to DPM 2010, follow the steps provided in "Upgrading a 64-bit DPM Server That Uses a Remote Instance of SQL Server" in the following section.

Upgrading a 64-bit DPM Server That Uses a Remote Instance of SQL Server

Use the following procedure to upgrade a 64-bit DPM server that uses a remote instance of SQL Server.

To upgrade a 64-bit DPM server that uses a remote instance of SQL Server

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

    • The local Administrators group on the DPM server

    • The local Administrators group on the computer running the remote instance of SQL Server

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

    Note

    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. Insert the DPM 2010 product DVD in the DVD-ROM drive. If the DPM Setup Wizard does not start automatically, double-click setup.exe in the root folder of the DVD.

    –Or–

    If you are installing DPM from a network share, navigate to the installation share, and then double-click setup.exe in the root folder of the share.

    Important

    If you use a network share to install DPM, you should apply the appropriate security to the share to ensure that no unauthorized or unauthenticated users can access or alter the contents of the share.

  3. On the Microsoft System Center Data Protection Manager 2010 screen, click Install Data Protection Manager.

  4. On the Microsoft Software License Terms page, review the license agreement. If you accept the terms, click I accept the license terms and conditions, and then click OK.

    Note

    After you click OK, DPM installs the Visual C++ Redistributable 2008 package and Microsoft .NET Framework 3.5 SP1 if they have not already been installed.

  5. On the Welcome page, click Next.

    DPM begins a prerequisites check for all required hardware and software.

  6. On the Prerequisites Check page, wait while DPM Setup checks the system to verify that it meets the software and hardware requirements.

    If all required components are present, DPM Setup displays a confirmation. Click Next to continue.

    If one or more required or recommended components are missing or noncompliant, Setup displays a warning or error message.

    Note

    On the Prerequisites Installation page, DPM Setup installs any prerequisite software required for setup. The DPM Setup Wizard will indicate if a restart is required to complete the installation. If a restart is required, restart the DPM server, and then run DPM Setup again.

  7. On the Product Registration page, enter a user name, company name, and a valid product key, and then in the Protection agent licenses area, do the following:

    1. In the Standard licenses box, type the number of licenses that you have purchased to authorize protection of file resources and system state.

    2. In the Enterprise licenses box, type the number of licenses that you have purchased to authorize protection of both file and application resources.

    3. In the Client licenses box, type the number of licenses that you have purchased to authorize protection of client computers (portable computers and desktop computers).

    Note

    If you purchase additional licenses after you set up DPM or reallocate licenses from one DPM server to another, you can update the number of available licenses for each DPM server in DPM Administrator Console. For information about updating your protection agent licenses, in DPM 2010 Help, see How to Update DPM License Information (https://go.microsoft.com/fwlink/?LinkId=196896).

  8. On the Installation Settings page, in the DPM Program Files section, the installation location defaults to the installation location of DPM 2007. You cannot change this location.

    In the SQL Server settings section, because DPM 2007 is using a remote instance of SQL Server, this setting cannot be changed.

  9. On the SQL Settings 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.

    Note

    After setup is complete, you can remove the user account from the local Administrators group on the computer where the remote instance is installed.

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

  11. On the Microsoft Update Opt-In page, specify if you want to sign up for the Microsoft Update service, and then click Next.

  12. On the Customer Experience Improvement Program page, specify if you want to enlist in the Customer Experience Improvement Program (CEIP), and then click Upgrade.

    You can change your CEIP settings at any time by using DPM Administrator Console. In the Selected Items area of any task area, click Options, click the Customer Feedback tab, and then select an option.

  13. After the installation is complete, the Installation page displays the installation status.

  14. Click Close, and then restart the computer.

    Important

    You must restart the computer to incorporate all of the DPM Setup changes.

  15. After you restart the DPM 2010 server, note the following:

    • Ensure that you save the backup of the DPM 2007 database backup file (DPMDB) in a secure location.

    • You can uninstall the MS$DPM2007$ instance of SQL Server because it is not required for DPM 2010.

  16. Complete the post-installation tasks described in After Upgrading to DPM 2010.

See Also

Concepts

After Upgrading to DPM 2010
Upgrading to DPM 2010 from DPM 2007
Upgrading to DPM 2010 from DPM 2007 When Using a Local Instance of SQL Server
Retrying a Failed DPM 2010 Upgrade
Rolling Back a DPM 2010 Upgrade

Other Resources

Upgrading to DPM 2010