You are browsing the archive for hotfix.

Protecting a Virtual Machine and also inside a guest

1:18 pm in Uncategorized by mikeresseler

Working on the Microsoft System Center Data Protection Manager booth the last few days got myself quite some insight in what customers want from DPM.  It also brought up a few “issues” that actually are non-issues but where you need to do a few steps to get the issue out of the way.

The DPM BoothMe and Hypervbear courtesy by @hypervbear


This is the scenario.  People want to protect the entire virtual machine once a day, a week, a … depending on their needs.  At the same time, they want to add a DPM agent inside the guest to enjoy the “every 15 minutes backup” for SQL or Exchange or so.

This scenario provides two great things:

1. You have a Disaster Recovery plan

You can recover your entire virtual machine, from x-days old.  Start the box, and then recover the latest data in the guest

2. You have a restore test scenario

Recover the virtual machine to an alternate hyper-v host.  And then do the recovery inside the guest again.

So you get real value for this scenario.  But here’s the catch.  When you are protecting the hyper-v machine, it will also go inside the guest to get a consistent state and truncate logs.  But you have also a guest backup that also will truncate logs… Houston, we have a problem here…

Luckily there is an answer to this problem.

The issue is described in this KB article:

Issue 3
The application backup operation in the virtual machine (VM) is incorrectly affected by the VM backup operation on the server that is running Hyper-V.

However, in some cases, this doesn’t solve the problem.  Don’t panic… Here is what you need to do:

You can apply the following registry entry in a virtual machine to fix "Issue 3" for that virtual machine:

Location: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Virtualization\VssRequestor
Name: BackupType
Value: 0 or 1

If this registry entry is created and its value is set to 1 , application backup will not be affected by the virtual machine backup operation on the server that is running Hyper-V. If this registry entry does not exist, or if its value is 0 , the "Issue 3" occurs.



DPM 2010 QFE Rollup available

10:55 am in Uncategorized by mikeresseler

Microsoft has just released a DPM 2010 QFE Rollup.

This, much awaited hotfix rollup, fixes 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. 

The information for the KB can be found here:

The download can be found here:



New hotfix rollup package for DPM 2007

8:02 am in Uncategorized by mikeresseler

Hey All,

A new hotfix rollup package is out for DPM 2007.

You can find the details here:

And the download can be found here:

The hotfix resolves following issues:

  • You may experience a crash in the Data Protection Manager engine when you run a tape job from a protected server.
  • When you use the Data Protection Manager Management Console to browse Microsoft SharePoint Server recovery points or when you back up a SharePoint point to tape from disk, you receive the following error message:

    PrmDatasetDatasourceMismatchForArchiveOfSC (=30132)

  • A SharePoint recovery point in a secondary Data Protection Manager has a different set of datasets than the corresponding recovery point in the primary Data Protection Manager.
  • Alerts for standby continuous replication (SCR) servers are not displayed in Microsoft Operations Manager.
  • Default disk allocations may grow unexpectedly for system state protection.
  • When you restore a SharePoint site that contains a WEB host header to an alternate location, the site is restored to the default site.
  • Shared Services Provider (SSP) database protection is blocked when one or more SSP names begin with the same SSP name.
  • The server is slow, and time-out errors may occur, when you run a backup-to-tape job.
  • Data Protection Manager-owned tapes are marked as unrecognized.
  • Data Protection Manager cannot retrieve SharePoint catalog information. Therefore, item-level recovery is not possible for some content databases. Additionally, you may receive the following error code:


  • You receive the following protection agent error code when bulk tape jobs cannot be completed successfully:


  • You may experience a Data Protection Manager engine crash during backup to tape.
  • The Data Protection Manager Management Console does not display recovery points before the year 2010 in some scenarios.

    As usual, the hotfix contains all previous hotfix rollups.

    Make sure you read the knowledgebase article well because after the hotfix, there could be an issue

    Also make sure you have the correct prerequisites (SP1 and KB962975)


    During the installation, make sure that you select Manually restart the selected servers because it is not necessary to restart the servers



    System Center Data Protection Manager 2007: Important Hotfix Rollup Package

    9:30 am in Uncategorized by mikeresseler

    Hey All,

    Microsoft has released a hotfix rollup package for SCDPM 2007 SP1.  This package resolves a lot of issues with this product:

    Issue 1
    If you enable library sharing, you cannot delete a protection group, and you receive the following error message:

    Cannot promote the transaction to a distributed transaction because there is an active save point in this transaction.

    Issue 2
    The SharePoint backup process fails if DPM 2007 cannot back up a content database. If you install this update, the SharePoint backup process will finish. However, an alert will be raised if DPM 2007 cannot back up a content database.

    Issue 3
    DPM 2007 jobs randomly fail. In the administrator console, you see error code 0x800706BA if you check the detailed information about the failed job.

    Issue 4
    DPM 2007 does not delete directories that are no longer being protected from the replica volume.

    Issue 5
    When you restore a Microsoft SharePoint site that is configured to use a host header, the incorrect SharePoint site is restored.

    Issue 6
    DPM 2007 performs a Volume Shadow Copy Service (VSS) full backup. Because the transaction logs are deleted when the DPM 2007 backup job is completed, this backup may interfere with other applications that are backing up transactional applications such as Microsoft SQL Server or Microsoft Exchange.
    After you install this update rollup, you can configure DPM 2007 to perform VSS copy backup. This means that the application transaction logs will not be deleted when the DPM 2007 backup job is finished.

    Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:

    322756 ( ) How to back up and restore the registry in Windows

    To configure DPM 2007 to perform VSS copy backup, add the following CopyBackupEnabled registry value under the following registry subkey:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Data Protection Manager\Agent\2.0

    Registry value: CopyBackupEnabled
    Type: REG_DWORD
    Value Data: 1

    Issue 7
    Reconciling a VSS shadow copy causes the DPM 2007 service to crash.

    Issue 8
    The DPM 2007 service crashes if a tape backup job is canceled during the CheckConcurrencyBlock operation.

    Issue 9
    The Pruneshadowcopies.ps1 script cannot delete expired recovery points.

    Issue 10
    If a parent backup job of a SharePoint farm fails, but the child backup succeeds, the DPM 2007 service crashes.
    This hotfix also includes the following previously released rollups for Data Protection Manager 2007 Service Pack 1:

    961502 ( ) A replica may be listed as inconsistent after you install System Center Data Protection Manager 2007 Service Pack 1 on a computer that is running an x64-based version of Windows Server 2003

    963102 ( ) Description of the hotfix rollup package for System Center Data Protection Manager 2007: February 16, 2009

    968579 ( ) Description of the hotfix rollup package for System Center Data Protection Manager 2007: April 14, 2009

    Make sure you install this one on all of your DPM installations:;EN-US;970867