DPM Error 30126 DPM could not find find a valid recovery point on disk Or ‘Replica Inconsistent’ showing against System State and Bare Metal Recovery on Protected Server

This error normally occurs due to one of the following two possible causes:

  • Not enough disk space is available on the protected machine to store a backup of the system state files
  • The Windows Server Backup feature is not installed on the protected machine (Windows 2008 or Windows 2008 R2)

Simply install the Windows Server Backup feature on to the protected machine from Server Manager. Installation of this feature doesn’t normally require a reboot.

If the protected machine doesn’t have enough disk space to store a backup of the system state files (you’ll need 10-12Gb free on the system drive by default to store these files) you’ll need to create some space on the system drive, or add another disk to the machine and modify the PSDataSourceConfig.xml file to allow DPM to use the new location.

The PSDataSourceConfig.xml file is normally located at %SystemDrive%\Program Files\Microsoft Data Protection Manager\DPM\DataSources. Modify the <FilesToProtect> section of the xml file to point to the new drive added. Maybe that you may need to remove protection for the machine from the DPM 2010 console and then re-enable protection to get DPM to read the new location for backup files from the PSDataSourceConfig.xml file.

Data Protection Manager 2010 error ID 30140 Details: Internal error code: 0x80990D11

I get the following error in DPM Management console on a SQL2000 server that is protected with DPM 2010

Affected area:           

Occurred since:          8/20/2011 4:01:13 AM

Description:    Recovery point creation jobs for SQL Server 2000 database ?????? on ???? have been failing. The number of failed recovery point creation jobs = 3.

If the datasource protected is SharePoint, then click on the Error Details to view the list of databases for which recovery point creation failed. (ID 3114)

DPM tried to do a SQL log backup, either as part of a backup job or a recovery to latest point in time job. The SQL log backup job has detected a discontinuity in the SQL log chain for  SQL Server 2000 database ???? since the last backup. All incremental backup jobs will fail until an express full backup runs. (ID 30140 Details: Internal error code: 0x80990D11)

More information

Recommended action:           If you see this failure as part of a backup job, then in the Protection task area, select the SQL Server database and click Create recovery point. Choose express full backup. Alternately, you can wait for the next scheduled express full backup to run.

If this failure occurs as part of a recovery job, then try to recover from another point in time.

Review the Application Event Viewer logs on the computer running SQL Server for more details.

Ensure that this database is not already protected by another backup application.

Create a recovery point…

Resolution:     To dismiss the alert, click below

Inactivate alert


DPM tried to do a SQL log backup, either as part of a backup job or a recovery to latest point in time job. The SQL log backup job has detected a discontinuity in the SQL log chain for SQL Server 2005 database database <name database> since the last backup. All incremental backup jobs will fail until an express full backup runs. (ID 30140 Details: Internal error code: 0x80990D11)

Resolution: It seemed that the problem was that there were also backups performed straight from the SQL Management Studio. Stopping these backups resolved the issue. See also http://support.microsoft.com/kb/970642

DPM 2010 System State of Bare Metal Recovery Fail on Windows 2008 R2 or Windows 7

When you check the event log of de server you see a event 517.

Name: Microsoft-Windows-Backup
Source: Microsoft-Windows-Backup
Date: date
Event ID: 5
Task Category: None
Level: Error
User: username
Computer: computer name
The backup operation that started at time has failed with following error code ‘2155347997’ (The operation ended before completion.). Please review the event details for a solution, and then rerun the backup operation once the issue is resolved


This a now Bug check KB2182466 you can download the hotfix here KBHotfix

DPM 2010 Data Protection Manager Error ID 316 on DPM Server or DPMRA Event id 85 on Workgroup Client

DPM 2010 Data Protection Manager Error ID: 316


or DPMRA Event id 85



On the protected server running the DPM agent

SetDpmServer.exe -dpmServerName YOURDPMSERVER -isNonDomainServer –updatePassword

On the DPM server


System Center Data Protection Manager 2010 Doesn’t Detect Tape Drives In Library

I’ve used System Center Data Protection Manager (DPM) since the 2007 beta, primarily for SharePoint and SQL backups & Exchange Backups.  At a customer they have one  DPM server which backs up to disk and additionally to a HP MSL2024 Tape Library for long term protection. The runs Windows Server 2008 R2 with DPM 2010 since its release.

After updating de DPM Server with SP1 for Windows 2008 R2 en updated the drivers. I had some issues with DPM. What I found was that although DPM installed correctly it couldn’t see  all the tape drives in the VTL. All the tape drives were visible in Device Manager and none were showing errors. I use the RECOMMENDED * HP StorageWorks Tape Drivers for Windows

In the DPM console under Management -> Libraries, the library was listed, but Total Drives was 0, rather than the expected 2. The DPM console showed the following error:


I followed the instructions to remap the drives here: http://technet.microsoft.com/en-us/library/bb795782.aspx. The DPMLA.xml file produced by the tool was correct, showing the correct SCSI IDs, serial numbers etc. but DPM still couldn’t see the drives.

I found the solution to the problem on the DPM forum here: http://social.technet.microsoft.com/Forums/en-US/dpmtapebackuprecovery/thread/1d599443-7bf6-437a-bf12-52847fa7c8e5/ What I did is update the tape drive driver to the Inbox LTO driver as described on the forum and below:

1) Open device manager
2) Locate the tape drive
3) Right-click and look at the properties.
3) Under the DRIVER tab, select UPDATE DRIVER
a) Select the Install from list or specific location (Advanvced) – next.
b) Select Don’t search. I will choose the driver to install. – next.
c) Uncheck the Show comtabile hardware checkbox.
d) Highlight LTO under the manufacturer.
e) Highlight the LTO tape drive under model – then next.
f) This should install the Microsoft ltotape.sys driver.
4) Rescan the tape library in the DPM console – try to take another backup.

After following the above steps, all the two tape drives were visible in the DPM console.

DPM 2010 Fix: Disk based recovery points are not deleted as per retention goals

When using System Center Data Protection Manager 2007 or 2010 (DPM) to backup your production servers, you might encounter a situation where the recovery point volumes for your protected data source keep running out of space and the number of days that DPM has recovery points for exceeds the desired retention range. If you run vssadmin list shadows, or run diskshadow.exe followed by list shadows all command, you can see that there are more shadow copies than there should be based on the desired retention goal. Also, if you manually run the DPM Power Shell pruneshadowcopies2010.ps1 script, no recovery points are removed, but there are no errors.

So what’s going on here? Most likely this is happening because the NetBIOS name of the DPM server is longer than 15 characters.


To resolve the problem perform the following to truncate the name to the 15 character limit.

1) Using notepad, open C:\Program Files\Microsoft DPM\DPM\bin\pruneshadowcopiesDpm2010.ps1 (For DPM2010) or pruneshadowcopies.ps1 (For DPM 2007).

2) Locate the following entry:

$dpmservername = &"hostname"

3) Replace the &"hostname" with the truncated 15 character NetBIOS name of the DPM server. For example, if the DPM Server’s host name is "Long-DPM-server-name" then modify the entry as follows:

$dpmservername = "ward-dpm01.wardvissers.local"

4) Save the modified script.

5) Either run the script manually, or wait for it to run at midnight – then verify the shadow copies are being pruned as expected.

Now I have nice Green Protection Groups

Special Thanks to J.C. Hornbeck

DPM 2010 Enabling/Disabling co-location of data on Tape

With this feature, you can achieve better tape utilization by co-locating data from multiple protection groups with similar retention range. This feature is disabled by default. You can use following PowerShell commands to enable and disable tape co-location.

Enable Tape co-location:

Set-DPMGlobalProperty -DpmServer <DPM Server Name> -OptimizeTapeUsage $true

After data co-location has been enabled, DPM will check for the following conditions before allocating a tape:

  1. The expiry date of the current dataset should fall in between the following dates:
    Upper bound: furthest expiry date among all the datasets on the tape – (furthest expiry date among all the datasets on the tape – current date) * TapeExpiryTolerance
    Lower Bound: furthest expiry date among all the datasets on the tape + (furthest expiry date among all the datasets on the tape – current date) * TapeExpiryTolerance.
  2. Current time should be less than first backup time of the dataset on the media + TapeWritePeriodRatio * RetentionRangeOfFirstDataset.

A dataset will be collocated only if both the above conditions are true.

When you add the value to the registry, set the DWORD to be the actual percentage in decimal. The Default is 17 percent if that value is not present. Most likely you need to increase that value to a higher percentage and in some cases you need to set it to 100 in order for tape co-location to work as desired.

TapeWritePeriodRatio – Indicates the number of days for which data can be written on to a tape as a fraction between 0 and 1. The default value is 0.15 – meaning by default, we will write to the same tape for 15% of the retension range period specified for each PG.

TapeWritePeriodRatio is not a registry. It is a global property for the DPM which needs to be set using DPM CLI command. Here is the command to set it:

Set-DPMGlobalProperty –DPMServerName <dpm server name> -TapeWritePeriodRatio <fraction>

EXAMPLE, to set the write period ratio to 50%, use the following command.

Set-DPMGlobalProperty –DPMServerName MY-DPMSEREVR -TapeWritePeriodRatio .50


System Center Data Protection Manager 2010 Monitoring Management Pack

The management pack monitors the health status of System Center Data Protection Manager 2010 and its components. It alerts the admin on critical health state and it provides certain break fix tasks to take corrective actions.

The following alerts are new in this release of the DPM 2010 Management Pack:

  • Backup metadata enumeration failed
  • Agent ownership required
  • Replica allocated and initial replication scheduled
  • Share path changed
  • Duplicate disks detected
  • VHD parent locator fix-up failed
  • Virtual machine metadata enumeration failed
  • VHD parent locator fix-up canceled
  • SharePoint Item Level Catalog failed
  • Backup without writer metadata
  • Customer Feedback opt-in
  • Backup SLA failed
  • Hyper-V Recovery Success
  • Global DPMDB Database Not Accessible alert notification
  • StagingAreaRestore in-progress
  • StagingAreaRestore success
  • StagingAreaRestore partial success
  • StagingAreaRestore failure
  • Auto Instance Protection failed
  • DPM Online Recovery Point creation failures
  • DPM Online Cache volume is missing
  • Partial Backup success
  • Library devices were disabled

You can download the System Center Data Protection Manager 2010 Monitoring Management Pack HERE

Storage Calculators for System Center Data Protection Manager 2010

Microsoft has released some new sizing calculators for DPM 2010.




Translate »