Wednesday, September 30, 2009

Home /3.0.7336.0 /DPM 2007 to DPM 2010 Upgrade /DPM 2010 /MSDPMV3BETA1EVA / DPM 2007 to DPM 2010 Upgrade

DPM 2007 to DPM 2010 Upgrade

1 comment

I have started testing the DPM 2010 installation and DPM 2007 to DPM 2010 upgrade scenarios in my lab. I have successfully upgraded my DPM 2007 to DPM 2010. Here are my observations during the upgrade process:

Lab setup: SQL 2005 64 bit and DPM 2007 64 Bit running on a Windows 2008 64 bit Server

  • You need to uninstall the Windows Poweshell 1.0 and install Poweshell 2.0 before you can install DPM 2010.
  • During the upgrade process, DPM 2010 will install a new SQL 2008 instance called MSDPMV3BETA1EVAL.

image

  • DPM 2010 process will automatically copy the DPM base from DPM 2007 to DPM 2010.
  • After the installation you will see DPM 2007 and DPM 2010 in the program menu. But after you restart the server, you will see only the DPM 2010 components.
  • But you will have two versions of the SQL servers. SQL 2005 and SQL 2008. You need to manually uninstall the SQL 2005.

image

  • After the complete installation you have to perform the following tasks:
    • Upgrade the agent with the latest version (3.0.7336.0). I had a little trouble with upgrading the agent. I ended up using the DPMAgentInstaller file located in the AMD folder. It is for 64 bit OSs. By default, 32 bit agent installation file is located in Program Files\Microsoft DPM\DPM\ProtectionAgents\RA\3.0.7336.0\i386 folder and 64 bit is in AM64.
    • You need to perform the consistency check after the agent upgrade
  • All protection groups, recovery groups etc were intact after the upgrade.

Anyway, I have a working DPM 2010 environment now and I am still testing different scenarios. So guys check back again for more updates.

Filed under
Share X LinkedIn Facebook Email
SS

Santhosh Sivarajan

Microsoft MVP · Identity & Cybersecurity Architect

Santhosh has 30+ years of hands-on enterprise experience in Identity and Access Management, Microsoft Entra ID, Active Directory, Microsoft 365 and Zero Trust architecture. He is the author of two books on Windows Server and security, and leads consulting, assessments and training at SAG Business Group.

SAG Business Group LinkedIn Publications Work with Santhosh

1 comments:

If rollup KB976542 (version 2.0.8861.0) or later 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

Post a Comment

Popular Posts
Workstation Trust Relationship Issue Issue: You receive the following error message, when you try to login to the domain.  The security database on the server does not have ... ADMT Service Account - Permission and Configuration The ADMT service account needs to have proper permission in source and target domains.  You don’t need to use 2 separate accounts.  You can ... My First Peek into Microsoft Exchange 2010 By Santhosh Sivarajan Before I really dive into Exchange 2010, I thought I would install and play with it first. I took some screen shots and notes during the ins... ObjectSID and Active Directory What is an objectSID in Active Directory? When a new object is created in Active Directory, Domain Controller assigns a unique value used ... AD Group Report - List Group Members in Active Directory–PowerShell Script Updated Script - http://portal.sivarajan.com/2011/10/search-ad-collect-local-admin-group.html Script #1 This script... Add Users to a Group–PowerShell Script Purpose – Add users to a group from an input file – PowerShell V2 Script.  Input file – Input file (Users.csv) contains samAccountName in... User Account Migration and Merging – Part I (ADMT) Part I - User Account Migration and Merging Using ADMT Part II - User Account Migration and Merging Using QMM pre-creating user account ... User Account Migration and Merging – Part II (Quest Migration Manager) Part I - User Account Migration and Merging Using ADMT Part II - User Account Migration and Merging Using QMM Pre-creating user account in... Delete Stale or Inactive Computer Accounts from Active Directory Here is an easy way to identify and delete inactive or stale computers in an Active Directory environment.  Using the dsquery command you c... Converting PowerShell (PS1) to EXE / Standalone Application As we know, there many applications available to convert a PowerShell file to a standalone executable file.  Based on my experience, PowerSh...