MMS 2012

How to Migrate from DPM 2007 to DPM 2010

Written by Steve Buchanan on .

Original Article: http://www.packtpub.com/article/installing-data-protection-manager-2010 

With the DPM upgrade you will face some of the same issues as with the installation such as what are the prerequisites? is your operating system patched? and is DPM 2007 fully patched and ready for the upgrade? This article will walk you through each step of the DPM installation process during the first half and the DPM 2007 to DPM 2010 upgrade in the second half. After reading this article you should know what to look for when working through the prerequisites and requirements.

Migrating from DPM 2007 to DPM 2010

Microsoft has released an upgrade adviser tool for upgrading from DPM 2007 to DPM 2010. You will need to run this to see if your current DPM 2007 is ready for the upgrade. This is a tool that asks you a series of questions and it will give you the recommended steps to take in order to upgrade your DPM from 2007 to 2010. This tool is an excel file and can be downloaded at the following page:

Here are what the questions are and what the tool looks like:

Installing Data Protection Manager 2010

Here are the steps that the tool recommends after answering the series of questions:

  1. Upgrade to DPM 2007 SP1 (mandatory) and install the latest rollup package (optional).
  2. Close the DPM administrator console and DPM Management Shell if opened.
  3. Launch the DPM 2010 RTM retail setup and proceed by clicking on Install DPM.
  4. Complete the installation wizard and restart the computer to complete the upgrade.
  5. Upgrade agents on production servers.NOTE: If rollup KB976542 (version 2.0.8861.0) or the latter is installed, you can upgrade the agent from the DPM Administrator Console. If this rollup is not installed, you should upgrade the agents manually by running the DPMAgentInstaller.
  6. Run a consistency check for all the protected datasources.
  7. Uninstall DPM 2007 SQL instance (optional) if there are no issues after the upgrade. However, if you’re looking to downgrade then DPM 2007 DPMDB is required.

Depending on the state of your current DPM and the server it is installed on you may need to do some pre-work. You need to make sure your server, DPM, and SQL are fully patched and up-to-date before you can upgrade. You will need to check the following requirements and recommendations on your current DPM 2007 server before you can run the upgrade:

  1. You need to make sure your DPM 2007 server is service pack 1.
  2. To check your DPM service pack level, open the DPM administrator console and click on the icon in the upper-right hand corner, as shown:

alt

  1. On the DPM 2007 information page, check the version number is the same as in the following image. If this version number is 2.0.5820.0 or higher then service pack 1 is installed.

Installing Data Protection Manager 2010

  1. Install all of the latest hotfixes for DPM 2007 SP1. To get the latest updates and hotfixes for DPM go here.
  2. Make sure your DPM 2007 server is installed on Windows Server 2008 or Windows Server 2008 R2, either needs to be 64 bit.
  3. Make sure the disk on which DPM 2007 is installed and you plan to run the upgrade on has a minimum of 3 GB of free space.
  4. It is highly recommended that you back up your current DPM database (DPMDB) on external media.
  5. If you are using a local dedicated SQL instance, don’t worry, the DPM upgrade process will install SQL 2008 and place the new database here. If you are using a remote SQL instance on SQL 2005 it is recommended that you do a fresh install of SQL 2008. This can be SQL Standard or Enterprise editions. You will then point the DPM 2010 upgrade installation to this remote SQL instance.
The upgrade process

Now, let’s get into the upgrade process itself. This will be a step by step guide to completing the installation. The upgrade installation is somewhat similar to the DPM 2010 installation. You will need to complete the following steps:

  1. Launch the DPM 2010 installer.
  2. Click on Install Data Protection Manager:

Installing Data Protection Manager 2010

  1. Accept the licensing terms and click OK. DPM will copy the setup files just like the regular installation does:

Installing Data Protection Manager 2010

  1. The Welcome screen reminds you that all protection jobs need to be stopped during the upgrade process. You also need to update the DPM agents right after the upgrade on your protected servers.(Move the mouse over the image to enlarge it.)

alt

  1. Click on Next to go to the next screen.
  2. The installation then checks all the prerequisites.(Move the mouse over the image to enlarge it.)

alt

  1. Take care of any issues that the installation finds then click Check Again. Once everything is okay click on Next.
  2. The next screen is the DPM installation path and choice of SQL instance. You can chose a local dedicated or a remote SQL instance. Make your selections and click on Next.

alt

  1. If you selected a local SQL instance then fill in a password and click Next. If you chose remote SQL instances then input your SQL Server settings and click on Next. If you need instructions on this please refer to Installing DPM using a remote instance of SQL Server 2008 seen earlier.(Move the mouse over the image to enlarge it.)

alt

  1. Choose to use Microsoft updates and click Next. Select whether you want to send Microsoft feedback or not and click the Upgrade button to start the DPM upgrade.

Installing Data Protection Manager 2010

  1. If you see the following screen with all check marks, it means that the upgrade went smooth. Click on Close to complete it.

alt

  1. A window will pop up reminding you to reboot your server and to update the DPM agents on all of your protected servers:

Installing Data Protection Manager 2010

  1. You will now see DPM 2007 and DPM 2010 icons on your desktop:

Installing Data Protection Manager 2010

  1. Once you reboot, DPM 2007 will be completely removed.
The post-upgrade process

After successfully upgrading to DPM 2010, there are some tasks you need to complete to get the rest of your servers functioning properly with DPM 2010. These tasks are:

  • Upgrade all of the protection agents on protected servers. Upgrading the agents will not require a restart of the protected computer.
  • Once you upgrade the DPM server and the agents on the protected computers, all of your protected data will go into an inconsistent state. You will need to perform a consistency check on all of the protected data after the agents have been upgraded.
Upgrading a protection agent

The following are the steps to perform an agent upgrade by running the DPMAgentInstaller.exe:

  • In the root directory on your DPM 2010 disc, locate the agent’s folder, and then copy these two files: DPMAgentInstaller_x64.exe and DPMAgentInstaller_x86.exe to a share on your network or an external drive.
  • Now log on to your protected servers and either put in your external drive or navigate to your network share where you put the DPM agent installation files in. Now run the appropriate DPMAgentInstaller.exe file. You will either have a 32-bit or a 64-bit server.

Microsoft Data Protection Manager 2010

Microsoft Data Protection Manager 2010

A practical step-by-step guide to planning deployment, installation, configuration, and troubleshooting of Data Protection Manager 2010

Read more about this book

(For more resources on Microsoft, see here.)

MS CM Support Team

The Configuration Manager Support Team Blog

This is the Configuration Manager blog for the Microsoft support team. If you were looking for the SCCM 2007 blog then you are in the right place.
  • I recently came across an older, fairly common issue recently but I never see one of the potential workarounds mentioned so I thought I write it up here in case you run into it. With this issue, the System Center Configuration Manager 2007 (ConfigMgr 2007) Remote Tools and Remote Desktop tools fail to connect to client computers that have a NetBIOS name longer than 15 characters even though regular Windows Remote Desktop works fine.  When your try to start Configuration Manager 2007 Remote Tools you get following error: Unable to contact Host When you try to use the Configuration Manager 2007 Remote Desktop client you get this error: Remote Desktop can’t find the computer <client name>.This might mean that <Client name> does not belong to the specified Network. Verify the computer name and domain that you trying to connect to. When trying to ping the 15+ character NetBIOS name it works, but when we try to ping the truncated NetBIOS name it errors out with the below message: Ping Request could not find host client <truncated NetBIOS name> NOTE In DNS, a Host (A) record is created for the 15+ character NetBIOS name (e.g. Client-PC123456789) although in the Configuration Manager console and under Active Directory users and computers it shows the truncated name consisting of first 15 characters (e.g. Client-PC123456). Most people assume that if you have a NetBIOS name of more than 15 character (the standard, accepted limit), the only way to fix the issue is to shorten it.  While that’s definitely the preferred method, you might be able to get away by enabling "NetBIOS over TCP/IP" on the server and client.  If you have a server or client with an NetBIOS name longer than 15 characters and “NetBIOS over TCP/IP” is disabled then you’ll definitely get the errors mentioned above. To resolve this issue, ensure that both the Configuration Manager 2007 server and the client have NetBIOS over TCP/IP enabled. You can verify this by going to Network Connection -> TCP/IP properties -> Advanced -> WINS tab -> NetBIOS. Adeel Mohd Get the latest System Center news on Facebook and Twitter: App-V Team blog: http://blogs.technet.com/appv/ AVIcode Team blog: http://blogs.technet.com/b/avicode ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/ DPM Team blog: http://blogs.technet.com/dpm/ MED-V Team blog: http://blogs.technet.com/medv/ OOB Support Team blog: http://blogs.technet.com/oob/ Opalis Team blog: http://blogs.technet.com/opalis Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/ OpsMgr Support Team blog: http://blogs.technet.com/operationsmgr/ SCMDM Support Team blog: http://blogs.technet.com/mdm/ SCVMM Team blog: http://blogs.technet.com/scvmm Server App-V Team blog: http://blogs.technet.com/b/serverappv Service Manager Team blog: http://blogs.technet.com/b/servicemanager System Center Essentials Team blog: http://blogs.technet.com/b/systemcenteressentials WSUS Support Team blog: http://blogs.technet.com/sus/ The Forefront Server Protection blog: http://blogs.technet.com/b/fss/ The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/ The Forefront TMG blog: http://blogs.technet.com/b/isablog/ The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/

  • We recently discovered an issue that KB2509007 would not install properly if installed at the same time as either KB977203 or KB977384 via the PATCH= option in the " Setup Windows and ConfigMgr " task. We were able to reproduce the issue internally and...(read more)

MS CM Team Blog

System Center Configuration Manager Team Blog

The official blog of the Microsoft System Center Configuration Manager Product Group