You are browsing the archive for SCDPM 2007.

Backup VMWare virtual machines

6:02 pm in Uncategorized by mikeresseler

Hey All,

A question that is asked a lot, so I thought I write about it.  Can VMWare virtual machines be protected by DPM 2010 (and also with DPM 2007 by the way :-))?  The answer is YES. How cool is that?

Here is a how-to:

To achieve this, we need VDR backup.  In the current version (1.0.2) the backup repository must be in an ‘inactive’ state when it is copied to tape.  When is it in an active state? When the following conditions are met:

  • Performing a backup

  • Performing a restore

  • During housing keeping tasks such as integrity checks or pruning of old backup restore points

Because of that, we need to make sure that the VDR is in an inactive state before copying the data to tape, or with other words, shut down the VDR application.

This guide also assumes that you have already configured your VDR appliance and that the backups are scheduled and running.

Before I get to that, I’ll first explain what the prerequisites are on the DPM protected server!  What does this mean?  It has to be done on the server that holds the backup disk for the virtual machines.


So far the prerequisites.  Now it is time to create all the scripts to do the job.

Number on:

Create a bat file called ShutdownVDR.bat (as example, the name is free to chose)

In this example, all scripts will be placed under c:\dpmscripts

Type the folliowing in the bat file (note! This must be on 1 line…)

%systemdirectory%\windowspowershell\v1.0\powershell.exe -PSConsoleFile “%programfiles%\VMware\Infrastructure\VSphere PowerCLI\vim.psc1” -Command <scriptname>

Or, in my example:

C:\WINDOWS\system32\windowspowershell\v1.0\powershell.exe -PSConsoleFile “C:\Program Files\VMware\Infrastructure\VSphere PowerCLI\vim.psc1” -Command C:\DPMScripts\ShutdownVDR.ps1

The thorough reader has already seen that there is a .ps1 script that needs to be created… Here it is:

Connect-VIServer -Server <vCenterIPAddress> -Protocol https -User <adminUsername> -Password <password> shutdown-vmguest <VDRApplianceName> -Confirm:$False Disconnect-VIServer -Confirm:$False

or again according to my example

Connect-VIServer -Server -Protocol https -User svc_user -Password VerYDiffICultPasswd shutdown-vmguest MP-VDR01 -Confirm:$False Disconnect-VIServer -Confirm:$False

Enough? No, we now have our shutdown of VDR in place, now it is time to create the startup.


%systemdirectory%\windowspowershell\v1.0\powershell.exe -PSConsoleFile “%programfiles%\VMware\Infrastructure\VSphere PowerCLI\vim.psc1” -Command <scriptname>


Connect-VIServer -Server <vCenterIPAddress> -Protocol https -User <adminUsername> -Password <password> Start-VM <VDRApplianceName> Disconnect-VIServer -Confirm:$False

Configure the protected server

Now you need to configure the protected server so that it will execute pre and post scripts when it needs to perform a backup.

You do this by editing the Scriptingconfig.xml file on that protected server.  This can be found under the agent installation directory (%programfiles%\Microsoft Data Protection Manager\DPM\Scripting\)

<?xml version="1.0" encoding="utf-8"?>

<ScriptConfiguration xmlns:xsi="" xmlns:xsd="" xmlns="">

<DatasourceScriptConfig DataSourceName="<DataSource>">



<TimeOut>15 </DatasourceScriptConfig>


Change the path\script to the correct values.  In my case it is c:\dpmscripts\shutdownVDR.bat for prebackup and c:\dpmscripts\startupVDR.bat for postbackup

Now just create a protection group that protects the specific drive and off you go…

With a lot of thanks to my colleague Arne Peleman.




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



    Troubleshoot Sharepoint Recoveries

    7:30 am in Uncategorized by mikeresseler

    Hey All,

    Just saw a nice video about troubleshooting Sharepoint Recoveries with system center data protection manager 2007.

    The video is created by Shane Brasher who is a Senior DPM Support Escalation Engineer.

    You can find the video @

    In the Video, Shane demonstrates two common failures and how to find information about them.

    One of these errors is not enough disk space for the recovery.  It is indeed a fact that to recover something from sharepoint you need to recover the entire site.  And this is sometimes overlooked by administrators.  Both on the recovery farm as the production farm you need to have enough space to recover.

    The error you will receive is ID 2035 and can be found in the DPM UI, eventviewer and the MSDPMCurr.errlog

    And finally, it is also found back in the trace logs when you need to make them for Microsoft Support.

    The other error he explained is a little more difficult to understand.  What he did was recover a site but to an alternate site.

    The error shown now was ID 32005: The system cannot find the file specified.

    Again, this error is visible in the DPM UI, eventviewer and the MSDPMCurr.errorlog but just shows this cryptic notification.

    The log you need here is the WSSCmdLetsWrapperCurr.errlog where there is a much better answer about this error.

    It states that you are trying to restore a site to another location which has the wrong template so be aware.

    Anyway, a must seen video for all you DPM admins out there.



    DPM2007 system state backup error : ID 30214 Details: Internal error code: 0x809909FB

    1:00 pm in Uncategorized by mikeresseler

    DPM 2007 message:

    DPM failed to create the system state backup. If you are trying to create the system state of a Windows 2008 Server operating system, verify that the Windows Server Backup (WSB) is installed, and that there is enough free disk space on the protected server to store the system state. (ID 30214 Details: Internal error code: 0x809909FB)

    when going to the server that needs to backed up we have the following messages in the application eventlog:

    Log Name:      Application
    Source:        Microsoft-Windows-Backup
    Date:          30/10/2009 9:34:37
    Event ID:      517
    Task Category: None
    Level:         Error
    User:          SYSTEM
    Computer:      secretcomputer
    Backup started at '30/10/2009 8:34:31' failed with following error code '2155348226' (System writer is not found in the backup.). Please rerun backup once issue is resolved.

    systemwriter not found? huh ?

    lets do a vssadmin list writers then and indeed there is no system writer.


    after sending the above message through some searchengines i came across this post :

    which points to permission issues:

    i ran the script in the post and my system writer returned.

    Takeown /f %windir%\winsxs\filemaps\* /a

    icacls %windir%\winsxs\filemaps\*.* /grant "NT AUTHORITY\SYSTEM:(RX)"

    icacls %windir%\winsxs\filemaps\*.* /grant "NT Service\trustedinstaller:(F)"

    icacls %windir%\winsxs\filemaps\*.* /grant BUILTIN\Users:(RX)

    C:\Windows\system32>vssadmin list writers
    vssadmin 1.1 – Volume Shadow Copy Service administrative command-line tool
    (C) Copyright 2001-2005 Microsoft Corp.

    Writer name: 'System Writer'
       Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
       Writer Instance Id: {d0a010fd-a697-4cd0-9ee0-0807830bc73b}
       State: [1] Stable
       Last error: No error

    the problem returns on reboot apparently… so be aware…


    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



    Installation of DPM 2007 Sp1 went fine but did require a consistency check

    10:05 pm in Uncategorized by evilbart

    This post is written by Ilse Van Criekinge from

    Being anxious to get my hands on Service Pack 1 for System Center Data Protection Manager 2007, I was very happy to see it is available for download now @ Microsoft. After reading the installation guidelines, I went ahead and updated my test environment.
    Since I have one DPM server, and I’m running running the SQL DPMDB instance on the Data Protection Manager 2007 server itself, I only needed to download and run the DataProtectionManager2007-KB959605.exe on the DPM server.

    After double-clicking the exe file, the installation of Visual C++ Redistributable is launched.








    After finishing the installation of this Visual C++ redistributable, the setup of service pack 1 really kicks off:





    Setup does warn you that any jobs in progress or the ones that will start during the installation process will fail. The installation procedure will also backup the DPM database. The warning that the process may take several hours can be ignored by me since I’m only using this DPM server to backup my Exchange environment.
    I accept the License agreement:



    And start the installation:



    To finish the update process I will need to restart the DPM server, as stated clearly when the installation of Service Pack is done:




    After rebooting the DPM Server, it is clear that I don’t have any other choice than to update the agents on my protected Exchange servers as well.


    DPM warns you that updating the agent may cause the need to schedule a consistency check after the upgrade:






    And DPM shows that the agent status is now ok:



    But a look at the protection group soon reveals that a consistency check is needed:




    Which I manually initiated immediately:




    And after a few minutes of waiting, everything worked out fine:





    So, installation went fine (even though rebooting both the DPM server and the protected Exchange server was required), and I had to perform a consistency check after updating the agents, but everything looks good now :-) Time to test the protecting of a SCR target now, but that’s for a next post 😉
    Please note, we have been forced to disable the ability to post comments, due to comment spammers. If you have a comment about this post or any other, don’t hesitate to send me a mail @ ilse.vancriekinge[@]
    – Ilse


    This post is written by Ilse Van Criekinge from

    IPD Guides: Microsoft System Center Data Protection Manager 2007 SP1

    9:37 pm in Uncategorized by evilbart

    Infrastructure Planning and Design Guides-Release Announcement: Microsoft System Center Data Protection Manager 2007 SP1

    The Infrastructure Planning and Design team has released a new guide, Microsoft System Center Data Protection Manager 2007 SP1.
    Looking to protect your organization’s data but not quite sure how to do this? This guide leads the reader through the process of planning a Microsoft System Center Data Protection Manager (DPM) 2007 SP1 infrastructure. Work through the infrastructure design process in a logical, sequential order. This guide enables the reader to quickly identify what types of data will be protected, what the recovery goals are, and the protection strategy to achieve those goals. Other benefits of using this guide include best practice design guidance from the product group and an optimized infrastructure to best meet the business requirements.

    Download the guide



    Alexandre Verkinderen

    Prerequisites and Known Issues with Hyper-V Protection

    9:17 am in Uncategorized by evilbart

    SP1 for dataprotection 2007 is now available, but if there are some prerequisites and known issues with Hyper-V protection:



    Before protecting Hyper-V virtual machines with DPM, ensure that the following updates are installed on the target Hyper-V server:

    • The customer should be running Hyper-V RTM. The corresponding Windows update is KB950050 ( HyperV Manager version should be 6.0.6001.18016.
    • Install the following updates:
      • KB951308 ( on each cluster node for cluster deployment.
        Increased functionality and virtual machine control in the Windows Server 2008 Failover Cluster Management console for the Hyper-V role.
      • KB959962 ( on the Hyper-V host and the guest virtual machines. This update for Hyper-V writer is required for backing up Hyper-V VMs with DPM.
        KB959962 is scheduled to release in January 2009, it enables online protection of Hyper-V guest machines. Until the update is available, virtual machines can be protected by configuring them for offline backup within each machines’ Integration Components service settings. Open the Settings window for the virtual machine and select Integration Services in the left pane. Clear the check box for Backup (volume snapshot) service and click OK. If you have set the DWORD AllowOffline registry key under HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft Data Protection Manager\Agent make sure the value is not zero (0).



      • KB960038 ( on all Hyper-V hosts. This update for Windows Server 2008 fixes a crash of the Hyper-V host server which you may experience when backups are made using Hyper-V writer.
    • The version of Integration Components running inside the VM should be the same as the version of Hyper-V on the host. For Hyper-V RTM it is 6.0.6001.18016.
      You can confirm this in the Device Manager inside the guest VM. Under System Devices in Device Manager, right-click on the entry Hyper-V Volume Shadow Copy and choose Properties. Check the version under the Driver tab. If the version does not match, insert the integration services disk by choosing the option under the Action menu in the VM console. Install the integration components and reboot the VM.

    Known Issues:







    Hyper-V server stops working when DPM runs backups on the server.

    You may experience a Stop 0x7E when you backup a server that has the Hyper-V role installed.

    This is a problem in the volsnap.sys driver when interacting with the Hyper-V VSS writer.


    Download and install KB960038 on the Hyper-V host to solve this problem.

    We recommend that you deploy this in the next available downtime window on the Hyper-V host.

    Backup of Hyper-V virtual machine fails

    Hyper-V virtual machine backups (backups using child partition) fail with following error for multiple volume virtual machines: DPM encountered a retryable VSS error. (ID 30112 Details: Unknown error (0x800423f3) (0x800423F3)).
    On the Hyper-V host in the event log: VMMS Event log contains following entry:
    Failed to revert to VSS snapshot on one or more virtual hard disks of the virtual machine ‘%1′. (Virtual machine ID %2).


    Perform an offline backup of the virtual machine.

    Download and install KB959962 on the Hyper-V host to solve this problem.

    We recommend that you install this update on all Hyper-V hosts protected by DPM.

    Recovery of Hyper-V virtual machine fails

    The Hyper-V Virtual Machine Management service stops when you are restoring a virtual machine.

    This issue can occur if the virtual machine is configured to use a legacy network adapter.

    Restart the Hyper-V Virtual Machine Management service.

    Download and install KB959962 on the Hyper-V host to solve this problem. Then recover the data to an alternate location.

    We recommend that you deploy this update on all Hyper-V hosts protected by DPM.

    Backup of the Hyper-V virtual machine fails

    Hyper-V VSS writer is in a bad state and does not identify itself to VSS anymore. The VSS application writer or the VSS provider is in a bad state. Either it was already in a bad state or it entered a bad state during the current operation (ID 30111 Details: Unknown error (0x80042319) (0x80042319)). Please check that the Event Service and the VSS service are running, and check for errors associated with these services in the Application Event Log on the server Please allow 10 minutes for VSS to repair itself and then retry the operation.

    This is a problem in the Hyper-V writer in Windows Server 2008.

    To get the writer back to a stable state, restart the Hyper-V Virtual Machine Management service. Perform offline backups of the virtual machines to prevent the writer from going into a bad state.

    Download and install KB959962 on the Hyper-V host to solve this problem.

    We recommend that you deploy this update on all Hyper-V hosts protected by DPM.



    Alexandre Verkinderen

    Service Pack 1 for DPM 2007 now available

    9:13 am in Uncategorized by evilbart

    What’s new in SP1 for DataProtection Manager 2007:


    Service Pack 1 for Microsoft System Center Data Protection Manager (DPM) 2007 provides continuous data protection for Windows application and file servers using seamlessly integrated disk and tape media and includes the following expanded capabilities:

    • Protection of Hyper-V™ virtualization platforms, including both Windows Server 2008 Hyper-V and the Microsoft Hyper-V Server, has been added to the existing set of protected workloads, building on the virtualization protection originally delivered for Virtual Server 2005.

    • Enhanced SQL Server 2008 protection, including the addition of new protection capabilities for mirrored databases, support for parallel backups of databases within a single instance, and the ability to move data from SQL Server 2005 to SQL Server 2008 for migration scenarios.

    • Microsoft Office SharePoint Server 2007 and Windows SharePoint Services 3.0 receive index protection, significant catalog optimization, and support for mirrored content databases.

    • Added protection for Exchange Server 2007 Standby Cluster Replication (SCR), enabling a complete disaster recovery solution that leverages SCR failover alongside DPM point-in-time restores.

    In addition to enhancing the protection of each of the core Microsoft application workloads, additional capabilities have also been introduced with the release of DPM 2007 SP1, such as:

    • Local Data Source Protection enabling the DPM 2007 SP1 server to act as a branch office server offering self-protecting File Services and Virtualization hosting within one platform.

    • Cross-Forest Protection allowing large enterprise customers with multiple Active Directory® forests to now have even more flexibility in their DPM deployments.

    • Provision for a Client DPML answers customer demand for a more cost-effective way to protect Windows XP and Windows Vista clients using the same DPM 2007 infrastructure that protects their servers.

    • Disaster Recovery capabilities within DPM 2007 SP1 now include the ability to leverage a third-party vaulting partner via the cloud (SaaS).

    DPM 2007 SP1 x86

    DPM 2007 SP1 x64

    Management pack for DPM 2007:

    feature Bullet Summary:

    • Centrally monitor the health and state of data protection for multiple DPM servers and protected computers.
    • In State Views, view consolidated state for protection activities in DPM at a glance. For DPM servers, view the state of database and service health, performance, and other indicators. For protected computers, view the state of connectivity, data protection and recovery operations.
    • Monitor resource usage and performance trends on DPM servers.
    • Monitor actionable DPM alerts relating to protection and recovery.
    • Through MOM alerts, monitor the status of memory, CPU, and disk resources on DPM servers, and find out about database and service failures.
    • Read Product Knowledge to get comprehensive practical information for diagnosing and resolving alerts.
    • Use tasks to diagnose and resolve problems on remote DPM servers.


    Download MP here



    Alexandr Verkinderen

    Session recording A Technical Overview of System Center Data Protection Manager

    10:38 am in Uncategorized by evilbart

    Session recording of the DPM event of Octover 14th, 2008


    Subject: “In this session, we will provide an overview of DPM
    2007, and deep dive of how DPM protects Microsoft SQL Server, Microsoft
    Exchange, Office SharePoint Server, and Microsoft Hyper-V/Virtual
    Server-using both near continuous protection to disk and long term
    archival to tape.”


    Guest Speaker: Anand Karandeep (Senior Program Manager , Data Protection Manager)