Posted by: scdpm2010 | December 29, 2010

undo suspect tapes

osql -E -S localhost\MS$DPM2007$ -d DPMDB -Q “UPDATE tbl_MM_ArchiveMedia SET IsSuspect = 0″

Posted by: scdpm2010 | December 27, 2010

ReSchedule library inventory

Get-MaintenanceJobStartTime -DPMServerName XXXX -MaintenanceJob LibraryInventory

Set-MaintenanceJobStartTime -DPMServerName XXXX -MaintenanceJob LibraryInventory -StartTime 20:00

Posted by: scdpm2010 | December 27, 2010

Enable Caching on DPM server

When you are protecting a large number (over 200 virtual machines) of virtual machines using cluster shared volumes (CSV), it may take a long time (>15 min) to populate the inquiry screen in the Create New Protection Group Wizard. You can avoid this by enabling caching on the primary DPM server. After you enable caching, when you expand the data source on the inquiry screen, DPM will refresh the resource groups under that node, but the virtual machines under each resource group will be populated from the cache. The default time-out for the cache is 48 hours. You can change this by editing the registry.

To enable caching, create a new registry key called CacheInquiryResults at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Data Protection Manager\Configuration. Under this key, create the DWORD InquiryResultsTimeoutInterval.

After you create the registry key, you will see the Clear Cache button on the inquiry page of the Create New Protection Group Wizard. Click this button when you want to force DPM to refresh the list of virtual machines.

Posted by: scdpm2010 | December 3, 2010

DPM Version overview

name Vesion number Related article   Release date
DPM 2007 RTM 2.0.5820.0     9-2007
Featurepack 2.0.8107.0 KB949779   18-7-2008
Hotfix rollup 2.0.8111.0 KB954641   31-10-2008
SP1 2.0.8793.0 KB959605   19-12-2008
Hotfix 2.0.8811.0 KB961502 X64 16-1-2009
Hotfix package 2.0.8824.0 KB963102   1-2-2009
Hotfix package 2.0.8836.0 KB968579   14-4-2009
Hotfix package 2.0.8844.0 KB970867   1-6-2009
Hotfix Package 2.0.8851.0 KB970868   15-9-2009
Hotfix Package 2.0.8861.0 KB976542   5-11-2009
DPM 2010 Beta 3.0.7336.0      
DPM 2010 CTP3 3.0.7475.0      
DPM 2010 RC 3.0.7558.0     8-2-2010
DPM 2010 RTM 3.0.7696.0      
Hotfix package 3.0.7706.0 KB2250444   10-11-2010
Hotfix package 3.0.7707.0 kb2465832   3-3-2011
Posted by: scdpm2010 | December 3, 2010

Agent upgrade question

Question: When i upgrade a dpm 2007 agent to dpm 2010 do i lose customizations i made in PSdatasourceconfig.xml?

Answer: No, the upgrade process will modify the file but will leave your customizations in place

This hotfix rollup resolves the following issues:

  • You cannot protect the Microsoft Exchange Database Availability Group (DAG) on a secondary DPM 2010 server.
  • You are prompted to restart a client computer after you install an agent on the client.
  • DPM services crash, and you receive the error, “Unable to connect to the database because of a fatal database error.”
  • MSDPM crashes, and event ID 945 is logged in the event log.
  • When you change a Protection Group, add a very large database, change the disk allocation, and then commit the Protection Group, DPM 2010 does not honor the user intent, and instead, DPM 2010 sets the sizes of replica and shadow copy volumes to the default sizes.
  • The Management tab does not link to information about the latest Microsoft Knowledge Base article for DPM 2010.
  • You receive the message, “Computers not synchronized,” when you try to replicate DPM 2010 databases to a System Center Operations Manager. 

Installation instructions

// This Data Protection Manager 2010 rollup package consists of three separate updates. To install each update, follow these steps:  

  1. Install the rollup package on the server that is running Data Protection Manager 2010. To do this, run the DataProtectionManager2010-KB2250444.exe file on the server. 

    Note You must restart the Data Protection Manager server after you install this rollup package.

  2. Update the remote Microsoft SQL Server installation that is hosting the DPMDB database. To do this, run the SqlPrep-KB2250444.msp file on the computer that is running SQL Server. 

    Note This step is not required if you are running a SQL Server DPMDB instance on the Data Protection Manager 2010 server.

  3. In the DPM Administrator Console, update the protection agents. To do this, use one of the following methods.

    Method 1: Update the protection agents from the DPM Administrator Console

    1. Open the DPM Administrator Console.
    2. Click the Management tab, and then click the Agents tab.
    3. In the Protected Computer list, select a computer, and then click Update on the Action pane.
    4. Click Yes, and then click Update Agents.
    5. In the Enter Credentials and Reboot option dialog box that is displayed, enter your credentials, select the Manually restart the selected servers later option, and then click OK.

      Note You do not have to restart the computer to update the agent. This is why the Manually restart the selected servers later option was selected.

    Method 2: Update the protection agents on the protected computers

    1. Obtain the update protection agent package from the “Data Protection Manager installation location\DPM\Agents\RA\3.0.7706.00” directory on the Data Protection Manager 2010 server.
      • For x86-based updates: i386\1033\DPMAgentInstaller_KB2250444.exe
      • For x64-based updates: amd64\1033\DPMAgentInstaller_KB2250444_AMD64.exe

      Note The DPMAgentInstaller.exe package applies to all languages.

    2. Run the appropriate DPMAgentInstaller.exe package on each protected computer.
    3. Open the DPM Administrator Console on the Data Protection Manager 2010 server. 
    4. Click the Management tab, and then click the Agents tab.
    5. Select the protected computers, and then verify that the agent version is listed as 3.0.7706.00.
  4. Run the DPMManagementShell2007-KB2250444.msp file.

    Note This step is not required if you are running the Data Protection Manager Management Shell on the Data Protection Manager 2010 server.

Restart information

// If the DPM Management Shell is open when you install the hotfix rollup package, you must restart the computer. Otherwise, a restart is not required.

« Newer Posts