Upgrade to DPM 2012 fails if you use a manually installed instance of SQL Server 2008 R2
Important Make sure that you have the DPM 2010 installation media and license key (if applicable) before you proceed.
Step 1: Update and replace the DPM 2010 installation
- Download and install hotfix 2751231 that contains DPM agent version 3.0.8180, if you are not already running this version.You will also reinstall this hotfix in a later step. To obtain the file, click the following article number to go to the article in the following Microsoft Knowledge Base:2751231 Description of hotfix rollup package 7 for System Center Data Protection Manager 2010
- Cancel all scheduled jobs for the next two hours so that they do not interfere with the upgrade. Wait for all currently running jobs to finish.
- Make a backup of the current DPMDB database in the C:\Temp folder by running the following command:
C:\Users\Administrator.SCSDPM>dpmbackup -db -instancename (LOCAL) -targetlocation c:\temp
- Make sure that the Dpmdb.bak file exists. Then, rename it to Dpmdb8195.bak. To do this, run the following command in the C:\Users\Administrator.SCSDPM folder:
ren c:\temp\dpmdb.bak dpmdb8195.bak
- In the Programs and Features item in Control Panel, uninstall DPM 2010. When you are prompted to retain or delete the protected data, click Retain.
- After DPM 2010 is removed, reinstall the program. When you are prompted by the SQL Server selection screen, select the first option to let DPM install its own SQL Server instance that is named MSDPM2010.
Note If you receive an error message that states that the database already exists, start SQL Server Management Studio, and then connect the local instance and delete the DPMDB database. This deletes the database files from the C:\Program Files\Microsoft DPM\DPM\DPMDB folder.
- Complete the DPM 2010 installation process.
- Open the DPM 2010 console to make sure that it works correctly, and then close it.
- Install the hotfix 2751231 file that you downloaded in step 1.
Important You must perform this step to update the database schema to version 3.0.8195.
- Restart the DPM server.
- Restore the 3.0.8195 DPM database from the C:\Dpm8195.bak file by running the following commands at an administrative command prompt:Note The DPM role configuration of this server will also be rolled back during this operation.
C:\>Dpmsync –restoredb –dbloc c:\temp\dpmdb8195.bakC:\Users\Administrator.SCSDPM>dpmsync -restoredb -dbloc c:\temp\dpmdb8180.bakDpmSync 2.0 - DPM database synchronization command-line tool
- Run the following command to synchronize the database:Notes
- This command confirms the status of the mount points and shadow copies.
- All recovery points will be retained.
- After you run this command, you receive the following message:DPM Synchronization completed.
Your tape library status may have changed.
Recommendation: Go to the Library tab in the Management Task Area of the DPM Administration Console and choose the Inventory Library action.
Step 2: Upgrade to DPM 2012
- Start SQL Server Management Studio, and then connect to the MSDPM2012 instance.
- Delete the DPM database so that the upgrade process can re-create it.
- Start the DPM upgrade process. Make sure that you resolve any prerequisite checks, such as for the accounts that are used in the DPM 2012 instance. (During this check, use same accounts that are used in the DPM 2010 instance.)
- Install hotfix 2751230. To obtain the file, see Update Rollup 3 for System Center Data Protection Manager 2012.
- Open the DPM console, upgrade the agents, and then run the consistency checks until all the data sources are displayed as green.
Step 3: Repair the DPM database and SQL Server log fileA small regression was introduced in Update Rollup 3 for Microsoft System Center 2012 in which Windows SharePoint catalog jobs caused the DPM database and SQL Server log file to become bloated. To repair the database and log file, follow these steps:
- Back up the DPM database again by running the following command:
dpmbackup -db -instancename (LOCAL) -targetlocation c:\temp
- Start SQL Server Enterprise Manager, and then connect to the MSDPM2012 instance.
- Run the following SQL Server query to update the DPM stored procedure that is causing the problem.
USE [DPMDB] GO /****** Object: StoredProcedure [dbo].[prc_PRM_SharePointRecoverableObject_Update] Script Date: 11/03/2012 01:36:08 ******/SET ANSI_NULLS ON GO SET QUOTED_IDENTIFIER ON GO ALTER PROCEDURE [dbo].[prc_PRM_SharePointRecoverableObject_Update] ( @Caption nvarchar(40), @ComponentType nvarchar(16), @RecoverableObjectId BIGINT ) AS DECLARE @error INT, @rowCount INT SET @error = 0 SET NOCOUNT ON -- UPDATE tbl_RM_SharePointRecoverableObject SET Caption = @Caption UPDATE tbl_RM_SharePointRecoverableObject SET Caption = @Caption, ComponentType = @ComponentType WHERE RecoverableObjectId = @RecoverableObjectId SELECT @error = dbo.udf_DPS_CheckRowCount(1) SET NOCOUNT OFF RETURN @error
Article ID: 2795977 - Last Review: 11/08/2013 23:51:00 - Revision: 4.0
- kbprb kbsurveynew kbexpertiseadvanced kbexpertiseinter KB2795977