Category Archives: System Center Data Protection Manager

DPM services fail to start following an upgrade to Windows Server 2016

I had SCDPM 2012 R2 running on Windows Server 2012 R2 with SQL Server 2012.  I followed the instructions here to upgrade to SCDPM 2016 UR 2 running on Windows Server 2016 with SQL Server 2016.

Everything was working fine until the final step to upgrade from Windows Server 2012 R2 to Windows Server 2016.  Following this the DPM services failed to start and the Event Log was full of errors like the below:

System.Exception: -2147023107

ATL Failure in Initializing Security of msdpm

Microsoft.Internal.EnterpriseStorage.Dls.Utils.DlsException: exception —> System.Runtime.InteropServices.COMException: Server execution failed (Exception from HRESULT: 0x80080005 (CO_E_SERVER_EXEC_FAILURE))

The resolution was to change the Netlogon service from Manual to Automatic.  Following this change and a reboot everything started working again.


Force A Tape To Be Free In System Center Data Protection Manager

If you need to force a tape to be free when you’re using System Center Data Protection Manager you can use the PowerShell script ForceFree-Tape.ps1.  The syntax of this command had me stuck for a while, so here’s a post to explain it.

  • Run the DPM Management Shell as an administrator.
  • Enter ForceFree-Tape.ps1.
  • Enter the DPM server name.
  • Enter the library name.  There’s no need to add speech marks for spaces in the name.
  • Here’s the bit that got me stuck.  Enter the location of the tape to be force free as slot-x, where x is the slot number of the tape you wish to erase.  Press enter and repeat the process for multiple slots.
  • When you’ve entered the location of the slots you wish to force free press Enter again.

DPM Tape Free





System Center Data Protection Manager 2012 R2 Operating System Support

As part of the planning stage for a System Center Data Protection Manager (SCDPM) 2012 R2 upgrade I found the support matrix for SCDPM 2012 R2.  The matrix shows that support for Windows Server 2003 and 2008 has been removed in the 2012 R2 release.

As I manage some SQL Servers that are running on Windows Server 2003 and 2008 I investigated the upgrade options.  Below is a short summary of the latest Windows OS version that is supported on various versions of SQL Server:

SQL Server 2005 supports up to Windows Server 2008 R2 as long as at least SQL 2005 SP3 is installed.

SQL Server 2008 supports Windows Server 2012 R2 as long as at least SQL 2008 SP3 is installed.

SQL Server 2008 R2 supports Windows Server 2012 R2 as long as at least SQL 2008 SP2 is installed.

SQL Server 2012 supports Windows Server 2012 R2 as long as at least SQL 2012 SP1 is installed.

Useful links:

Known issues installing SQL Server on Windows 7 or on Windows Server 2008 R2

Using SQL Server in Windows 8, Windows 8.1, Windows Server 2012 and Windows Server 2012 R2 environments

System Center Data Protection Manager 2012 – The device is not connected (0x8007048F)

I recently came across a problem with System Center Data Protection Manager 2012 (DPM) whereby backups were failing with the error “An unexpected error occurred while the job was running. (ID 104 Details: The device is not connected (0x8007048F))”

Unfortunately, I wasn’t able to resolve the problem without data loss, but these are the steps I followed to get DPM working again.

Firstly, go to Disk Management by opening Server Manager, then expand Storage.

DPM Error 1


I saw a large number of RAW volumes with 100% free space.  I had to delete each of these volumes, by right-clicking and choosing delete.

DPM Error 2

Once you’ve deleted all the RAW volumes, open the DPM Management Shell and run DPMSync – ReAllocateReplica.  This recreates the volumes for each item that’s protected by DPM where the volume is missing.

Open the DPM Management Console and start an consistency check of all data sources.  This ensures DPM has an up to date copy of all protected items and can resume backups.


Item Level Recovery Of SharePoint 2010 Using System Center Data Protection Manager 2010

In order to carry out item level recovery of SharePoint 2010 using System Center Data Protection Manager 2010 (DPM) you may need to update the DPM catalog.

I was testing SharePoint 2010 recovery using DPM and got a shock when a site and page I setup for the testing weren’t listed as being available for recovery despite the fact I’d just created a recovery point.  It turns out they had been backed up, but the DPM catalog was out of date.  The steps below detail how to update the catalog.

Open the DPM Management Shell and enter the commands below, substituting X for you DPM server name

$PG = Get-ProtectionGroup -DPMServerName X

Press Enter, type $PG and press Enter again and you should see a table with two columns.

Type $DS = Get-Datasource $PG[X] and press Enter.  Substitute X with the number of the datasource in the list above.  In my case I want to update the catalog for the “SharePoint 2010” datasource, which is third in the list, so I enter [2] as the list is zero based.   Type $DS and press Enter.

The output above shows the details for the selected datasource.  I want to update the catalog for the Sharepoint Farm, so type the command below and press Enter.  $DS[0] is the value of the datasource item within the list.  This list is also zero based.

Start-CreateCatalog -Datasource $DS[0]

Allow a few minutes for the catalog to update and the items will be available for recovery.



ID 30101 Details: The request could not be performed because of an I/O device error (0x8007045D)

On System Center Data Protection Manager (DPM) 2010 with March 2011 hotfix I got the following error when backing up to tape:

ID 30101 Details: The request could not be performed because of an I/O device error (0x8007045D)

This is an error that was originally fixed in DPM 2007 with a hotfix , but reappeared on my 2010 install.  It can occur with large tape backups that span more than one tape.  I fixed the error by adding the following registry key, a reboot wasn’t necessary:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Data Protection Manager\Agent]


I’ve had the same problem with DPM 2012 SP1 and the registry still fix worked.

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

[UPDATE – June 2013]

I’ve just encountered the same issue using Windows Server 2012, System Center Data Protection Manager 2012 SP1 and an Overland REO 4600 VTL.  As with DPM 2007, the fix is to change the tape drive driver to the generic Microsoft LTO tape driver.

I’ve used System Center Data Protection Manager (DPM) since the 2007 beta, primarily for SharePoint and SQL backups.  I have a primary DPM server which backs up to disk and a secondary server which backs up to disk and additionally to a Overland Storage REO 4500 iSCSI Virtual Tape Library (VTL) for long term protection.  Both servers have run Windows Server 2008 R2 with DPM 2010 since its release.

I’ve never had any major issues with DPM until I recently rebuilt the secondary server from scratch with a clean OS install of Windows Server 2008 R2 SP1 and DPM 2010.  What I found was that although DPM installed correctly it couldn’t see the tape drives in the VTL.  All the tape drives and the medium changer were visible in Device Manager and none were showing errors.  The medium changer and driver were automatically installed by Windows and the tape drive driver came from Windows Update.  The REO 4500 emulates an HP LTO2 tape drive and this is what was displayed in Device Manager.

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

Tape Library Overland Neo Series Medium Changers is not functioning efficiently for the following reason:

The drive information for Tape Library Overland Neo Series Medium Changers is incorrect and needs to be refreshed. (ID: 3302)

I followed the instructions to remap the drives here:  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: 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 16 tape drives were visible in the  DPM console.