Upgrade the DPM Database

 

Updated: May 13, 2016

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

An important step in the DPM upgrade is to update the System Center 2012 – Data Protection Manager (DPM) database (DPMDB).

DPM 2012 consolidates the database for all DPM servers to one SQL Server instance. You can upgrade the SQL Server instance as follows:

  • Upgrade local to local— Use this option if you want to continue to have DPMDB on the same computer as DPM after the upgrade.

  • Upgrade local to remote— Use this option if you want to use a remote instance of SQL Server instead of a local instance after the upgrade. When SQL Server is deployed remotely it can host the databases of multiple DPM servers.

  • Upgrade remote to remote— Use this option to continue to use a remote instance of SQL after the upgrade. One instance of SQL Server can host the databases of multiple DPM servers.

    Note that using a SQL Server that is deployed in a cluster is only supported from DPM in System Center 2012 R2.

Before you start, note the following:

  • Remember to back up the existing database before upgrading.

  • Upgrade the DPM servers sequentially. Parallel upgrades may lead to errors.

  • If you are using an existing instance of SQL Server, you must run the DPM Remote SQL Prep tool from the Setup splash screen on the instance of SQL Server you are going to use. All the DPM databases on this instance must be upgraded.

    The remote SQL Server can have only one version of SQL Prep tool on it. You can’t upgrade the tool for selected databases only.

  • You can’t share an instance of SQL Server that’s installed by DPM. We recommend you use it only for DPM databases. Note that DPM doesn’t install SQL Server in DPM in System Center 2012 R2 onwards.

  • TCP/IP must be enabled on SQL Server and TCP/IP client protocol on DPM server.

  • When you set up tape library sharing, provide the complete name as <servername>\<instancename>\<databasename>.

  • The naming conventions for DPM database installed by DPM were changed in System Center 2012. Check the name of the database using the Information button in the Administrator Console.

Upgrade local to local

  1. Backup DPMDB. Setup will upgrade the SQL Server instance to SQL Server 2008 R2 SP2.

  2. Launch System Center 2012 SP1System Center 2012 – Data Protection Manager (DPM) installation. This will start setup in upgrade mode.

Upgrade local to remote

  1. Verify that the domain user account you’ll use for DPM 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 on which you have installed the remote instance of SQL Server 2008 R2 or SQL Server 2012.

  2. 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.

  3. Backup DPMDB.

  4. Restore the DPMDB backup to a remote instance of SQL Server 2008 R2 or SQL Server 2012 where you plan to use to host databases of multiple DPM servers. The name of the restored database should be DPMDB.

  5. Ensure that TCP/IP protocol is enabled for this instance of SQL Server.

  6. Install SQL Prep Tool on the remote computer running SQL Server. You can find this on the Setup page.

  7. Launch DPM installation. This will start setup in upgrade mode.

    Select Existing instance of SQL Server as your database.

Upgrade remote to remote

  1. Ensure that the domain user account you will use to install DPM 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 R2.

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

  2. 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.

  3. Backup the DPM database.

  4. Restore the DPM database backup to a remote instance of SQL Server that you plan to use to host databases of multiple DPM servers. The name of the restored database should be the same as the DPM database you backed up.

  5. Ensure that TCP/IP protocol is enabled for this instance of SQL Server.

  6. Install SQL Prep Tool on the remote instance of SQL Server.

  7. Launch DPM installation. This will start setup in upgrade mode.

Use the above steps in case you are moving from one remote SQL Server instance to another. If you are going to use an existing remote instance then simply provide that instance’s credentials.