Upgrade prerequisites

 

Updated: May 13, 2016

This topic summarizes prerequisites for upgrading to DPM in System Center 2012 R2 Preview:

  • If you are planning to upgrade two or more System Center components, it is imperative that you first consult the guide Upgrade Sequencing for System Center 2012 SP1. The order in which you perform component upgrades is important. Failure to follow the correct upgrade sequence might result in component failure for which no recovery options exist. The affected System Center components are Orchestrator; Service Manager; Data Protection Manager (DPM); Operations Manager; Configuration Manager; Virtual Machine Manager; and App Controller.

  • Ensure that the hard disk on which DPM is installed has at least 4.5 gigabytes (GB) of free disk space.

  • Install the latest DPM updates on the DPM server and protected computers.

  • You must back up the DPM database and save the backup file in a secure location.

  • If you are upgrading your instance of SQL Server to SQL Server 2012, we recommend installing a new instance of SQL Server 2012 before proceeding with the upgrade. For step-by-step instructions for installing a remote instance of SQL Server, see Setting up the DPM database. Then migrate your database using the steps outlined in Upgrade remote to remote.

  • Upgrade will require upgrading the DPM protection agents, which might force a restart of your protected computer.

  • After upgrade, DPM will mark all replicas as inconsistent. You must run a manual consistency check after upgrade.

  • If a protected computer is running Windows Server 2003 SP2, Windows Server 2008 or Windows Vista, you should download and install the following update, KB 975759.

  • If you are sharing a tape library across multiple servers running System Center 2012 – Data Protection Manager (DPM), you must remove library sharing before you upgrade to System Center 2012 SP1DPM.

  • If you have library sharing enabled, disable it and then backup your DPM dataset. You can enable tape library sharing after installing DPM successfully. Remove library sharing as follows:

    To remove library sharing

    1. On each library client computer, open an elevated command prompt, and then run the following commands:

cd <system drive> :\Program Files\Microsoft DPM\DPM\Setup

    **SetSharedDPMDatabase.exe –RemoveDatabaseSharing**
    
    **AddLibraryServerForDPM.exe –DPMServerWithLibrary** *\<FQDN of the library server\>* **-remove**
    
    where *\<FQDN of library server\>* is the fully qualified domain name of the library server.

2.  Upgrade DPM on the library client computers.

3.  Repeat steps 1 and 2 for all library client computers.

4.  After you have removed library sharing and upgraded DPM on all library clients, on the library server, open an elevated command prompt, and then run the following commands one time for each library client:
    

cd <system drive> :\Program Files\Microsoft DPM\DPM\Setup

    For each library client, run:
    
    **AddLibraryServerForDpm.exe – ShareLibraryWithDpm**  

**<FQDN of library client>* -remove*

    where *\<FQDN of library client\>* is the fully qualified domain name of the library client.
    
    Then run the following command one time:
    
    **SetSharedDPMDatabase.exe -RemoveDatabaseSharing**

5.  Upgrade DPM on the library server.

6.  After you have upgraded DPM on the library server, reconfigure tape library sharing. For step-by-step instructions about how to configure library sharing, see [Setting up Tape Library Sharing](https://go.microsoft.com/fwlink/p/?linkid=241592).