DPMRA not starting on the DPM Server

The following issue I encountered in our own DPM environment.

When checking the DPM console we found that all jobs were stuck. During investigation we found that the the DPMRA service on the DPM server keeps failing to start.The event log shows countless number of the following errors.

Log Name:      System Source:        Service Control Manager Event ID:      7009 Task Category: None Level:         Error Keywords:      Classic Description: A timeout was reached (30000 milliseconds) while waiting for the DPMRA service to connect.

Log Name: System Source: Application Popup Event ID: 26 Task Category: None Level: Informatio Keywords: Classic Description: Application popup: DPMRA.exe - Application Error : The exception unknown software exception (0x8007000e) occurred in the application at location 0xfd74bccd

There are no other event in the eventlog that indicate why the DPMRA service keeps failing. The DPMRA1.errlog logs gives us a better indication of the root cause.

2430 28D4 02/04 09:31:11.131 03 agentcfg.cpp(475) [0000000000A5CC20] NORMAL Cound not find configuration for DPMRA 2430 28D4 02/04 09:31:11.131 29 dpmra.cpp(125) [0000000000A594D0] NORMAL CDPMRA: destructor [0000000000A594D0]

With help of this Technet forum post we found that this error indicates that one of the registry keys for DPM is missing.

did a procmon trace, and found that the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Data Protection Manager\Agent\2.0\Configuration is missing ! Which would co-incide with the agent saying "Element not found"

We checked the registry and the key is indeed missing. As shown in the image below.

 

This is a complex key with a lot of unique information, therefor the best way to fix this issue is by restoring the key. In our case we have a System State back-up available of the server (created at the time the server was working fine).

The steps below show you how to restore the registry key from a System state back-up (VHD). This procedure uses Windows 2008 R2 server. Other OS versions involve different steps

DPM reporting fails (after server reinstall)

Reinstallation of DPM with the same server name and database. For instance in the case of hardware replacement. Could lead to failing reports on the DPM server.

Error

An error occurred during client rendering. An error has occurred during report processing. (rsProcessingAborted) Cannot create a connection to data source 'DLS'. (rsErrorOpeningConnection) Cannot open database "DPMDB" requested by the login. The login failed. Login failed for user ‘%servername%\DPMR$%servername%.

Cause
After recovery of the DPM server to new hardware. The account ‘%servername%\DPMR$%servername%. doesn’t have the correct mappings for the DPM database.

Solution

1. Connect to the MSDPM2010 instance using SQL management dtudio
2. Expand Security then expand Logins; right-click %servername%\DPMDBReaders$%servername% and select properties
3. Select User Mapping in the left pane; in the upper right pane, under "Users mapped to this login:" verify DPMDB is selected; In lower right pane, ensure db_datareader and public are both selected; click OK

An error has occurred during report processing. (rsProcessingAborted) Cannot impersonate user for data source 'DPMReporterDataSource'. (rsErrorImpersonatingUser) Log on failed. Ensure the user name and password are correct. (rsLogonFailed) Logon failure: the user has not been granted the requested logon type at this computer

To resolve this error, you must ensure that the DPMReport account has the Allow log on locally user right. To assign the Allow log on locally user right to the DPMReport account: In Administrative Tools, open Local Security Policy. Under Security Settings, expand Local Policies, and then click User Rights Management. In the details pane, right-click Allow log on locally and then right-click Properties. In the Allow log on locally Properties dialog box, click Add User or Group. In the Select Users, Computers, or Groups dialog box, click Locations, click the name of the DPM server, and then click OK. In the Select Users, Computers, or Groups dialog box, enter DPMReport, and then click OK. In the Allow log on locally Properties dialog box, click OK. In the details pane, right-click Deny log on locally and then right-click Properties. If the DPMReport account is listed, select DPMReport and then click Remove

DPM console crashes on Recovery Tap

One of our customers ran in to the problem that the DPM Console Kept on crashing when selecting the recovery Tab in the DPM console.

Error data

Description:AppName: mmc AppVer: xxxxx ModName: mmc.exe ModVer: 6.1.7600.16385 StackHash: F36A6DFE Problem signature: Problem Event Name: DPMException Application Name: mmc Application Version: xxxxxxxx Module Name: mmc.exe Module Version: 6.1.7600.16385 Exception Name: System.ArgumentException Exception Point: System.ThrowHelper.ThrowArgumentException Other: F36A6DFE OS Version: 6.1.7601.2.1.0.272.7 Locale ID: 1033

Check for duplicate servers in database
The error could be caused by duplicated names of Protected servers in Your DPM database.

Best way to check this is by running a query against the DPMDB.

The query: Select ServerName, Domainname from dbo.tbl_AM_Server
returns an overview of all protected servers in the database. It could be that servers are duplicate in the database with their NETBIOS and their FQDN.
If there are any duplicates you should stop protection for these servers and re-add them to DPM. This should resolve the issue with the crashing DPM console

DPM log error and event log error below

Self service Recovery for SQL Cluster

When enabling self service recovery for an Instance on a SQL Cluster you might run into the following error.

The specified SQL instance … is invalid or cannot be found (ID 32608). If a SQL instance exists with the specified name, use Get-Datasource –ProductionServer <ProductionServer> –Inquire cmdlet to refresh the information. Then retry the Operation.

Solution
SQL instances of a Cluster need to be added in a special way.
The convention is: FQDN of the Resource\SQLVirtualname\SQLInstance

Example
FQDN resource = (blackberry).c260.gp.wan
SQLVirtualname= C265
Instance name – BLACKBERRY

In the example above you need to specify the following SQL Server Instance: (Blackberry).c260.gp.wan\C265\BLACKBERRY

ID 7: Unable to connect to the Active Directory Domain Services

During the deployment or the attaching of agents you might run in to the error below.

Unable to connect to the Active Directory Domain Services database. Make sure that the DPM server is a member of a domain and that a domain controller is running. Also verify that there is network connectivity between the DPM server and the domain controller. ID: 7 Details: Unknown error (0x80005000) (0x80005000)

There is a knowledge database article for a issue like this:
http://support.microsoft.com/kb/978900

Resolution for Error ID: 7 To resolve this error, change the Authenticated Users group so that it has read permissions for the organizational unit that the target server is a member of. To do this, follow these steps: On the domain controller, open the Active Directory Users and Computers MMC. Right-click the organizational unit that contains the target server, and then click Properties. On the Security tab, add the Authenticated Users group and give them READ permissions. Redeploy the DPM protection agent to the protected server

Alternative cause to this issue

The error code Unknown error (0x80005000) (0x80005000) points to another cause.

In this case the issue was caused by a slash in the OU Name the  The target machine to install the DPM agent on was in an OU named "DR/ test Servers."  DPM doesn't understand special characters in active directory, so the / was what tripped it up.  When you rename the OU, you should be y able to install the agent.

Windows 2008 (R2) system state fails due FSCVSSWriter

In a previous post we discussed the Windows 2008 (R2) system state backup failures because of a FSCVSSwriter issue.

Log Name:      Application Source:        FSCVSSWriter Date:          2-11-2009 17:36:17 Event ID:      11003 Task Category: (11) Level:         Error Keywords:      Classic User:          N/A Computer:      <server_name> Description: Microsoft Forefront Protection VSS Writer failed when preparing for backup. Writer instance: FSCVSSWriter Error code: 0x00000000

The workaround in this post was to disable the FSCVSSWriter. With this workaround you will lose the functionality of the Microsoft Forefront Protection VSS Writer.

There is now a Hotfix Rollup 1 for Microsoft Forefront Protection for Exchange available that includes a fix for this issue. http://support.microsoft.com/kb/2181692
----------------More details---------------

A system state backup fails while attempting to perform anything other than a full backup on a server running Forefront Protection for Exchange Problem A system state backup fails while attempting to perform anything other than a full backup on a server running Forefront Protection for Exchange.

The following will be generated within the Application Log:

Error FSCVSSWriter 11003 Microsoft Forefront Protection VSS Writer failed when preparing for backup. Writer instance: FSCVSSWriter Error code: 0x00000000 Warning VSS 8229 A VSS writer has rejected an event with error 0x800423f0, The shadow-copy set only contains only a subset of the volumes needed to correctly backup the selected components of the writer. Changes that the writer made to the writer components while handling the event will not be available to the requester. Check the event log for related events from the application hosting the VSS writer.

The hotfix role up is available on request here

APPLIES TO: Microsoft Forefront Protection 2010 for Exchange Server

DPM cannot set up an e-mail subscription

In some cases (after a upgrade from RC to RTM for instance) the email subscription to reports is not working. Even when the SMTP Server settings are properly configured (on the SMTP server TAB under options) with a valid e-mail address. 

Test messages work fine and you receive warning and error alert messages. Still you receive the error below.

-------------------------
DPM cannot set up an e-mail subscription for this report. The information may be missing or incorrect. Click Options in the Actions pane, then click the SMTP Server tab, and provide the correct SMTP server name and e-mail address. ID: 3010
---------------------------------

 

Solution
You should check if the SMTP server settings is correct set on the report server.

To configure report server e-mail using the Reporting Services Configuration tool

1. Verify that the Report Server Windows service has Send As permissions on the SMTP server.

2. Start the Reporting Services Configuration tool and connect to the report server instance.

3. On the Email Settings page, enter the name of the SMTP server. This value can be an IP address, a UNC name of a computer on your corporate intranet, or a fully qualified domain name.

4. In Sender Address, enter the name an account that has permission to send e-mail from the SMTP server.

5. Click Apply.

 

SharePoint with multiple WFE servers

When starting protection of a SharePoint farm with multiple Web Front-End (WFE) servers, you need to perform additional step.
When you run the ConfigureSharePoint –EnableSharePointProtection command you might receive the following error in a environment with more then one WFE server.

Cannot start service SPWriter on computer '.'. An error occurred while trying to start the Sharepoint Vss Writer.

In this case you first need to run the command:
C:\program Files\Common Files\Microsoft Shared\Web Server extensions\12\bin\Stsadm.exe -o registerwsswriter

Note: The administrator credentials you provide for the Windows SharePoint Services farm must be a local administrator on the WFE server

More info: TechNet forum

Agent update failed

After installing the new Hotfix rollup package for DPM 2007 (KB979970) you have to update the agents. In my case this went fine for almost all agents.
Only the agents on the SharePoint servers had a nasty issue.

The (push) upgrade failed with the following error.

Agent Operation failed (ID 370)
The agent operation fauled because an error occurred wile running the installation program on <compter name> (ID 313). Details: The installation source for the product is not available. Verify that the source exits anf that you can access it (ox8007064c)
-----------------
The local agent installation shows a same kind of error:

DPMAgentInstaller failed with errorcode =8007064c, error says: The installation source for this product is not available.  Verify that the source exists and that you can access it.

Check log files in [WINDIR]Temp\MSDPM*.LOG
Press Enter key to close the window
-----------------
For this error messages it is not clear which installation files are missing.

The log MSDPMAgentPatchInstall.LOG (windir\temp) shows in more detail which files are required.
--------------------------
SI (s) (8C:D0) [13:27:58:789]: SOURCEMGMT: Source is invalid due to missing/inaccessible package.
MSI (s) (8C:D0) [13:27:58:789]: Note: 1: 1706 2: -2147483647 3: dpmra.msi
MSI (s) (8C:D0) [13:27:58:789]: SOURCEMGMT: Processing net source list.
MSI (s) (8C:D0) [13:27:59:810]: SOURCEMGMT: Now checking product {07CCDE6A-1D92-2C9C-D091-9E682643ABCC}
MSI (s) (8C:D0) [13:27:59:810]: SOURCEMGMT: Attempting to use LastUsedSource from source list.
MSI (s) (8C:D0) [13:27:59:810]: SOURCEMGMT: Trying source C:\WINDOWS\Microsoft Data Protection Manager\DPM\Agents\RA\2.0.8844.0\.
MSI (s) (8C:D0) [13:27:59:810]: Note: 1: 2203 2: C:\WINDOWS\Microsoft Data Protection Manager\DPM\Agents\RA\2.0.8844.0\dpmra.msi 3: -2147287037
MSI (s) (8C:D0) [13:27:59:810]: SOURCEMGMT: Source is invalid due to missing/inaccessible package.
MSI (s) (8C:D0) [13:27:59:810]: MainEngineThread is returning 1612
-----------------------------

The agent upgrade requires the file dpmra.msi from the directory C:\WINDOWS\Microsoft Data Protection Manager\DPM\Agents\RA\2.0.8844.0\.
This is actually the installation file from the current agent version (2.0.8844). The issue is that this directory does not exist on the server and the installation files are not in any other directory on the server.

Solution (workaround)
The only way I could get the required source files was installing the old agents files (2.0.8864) to (a temporary)machine. The source is available on the DPM server (\\dpmservername\c$\Program Files\Microsoft DPM\DPM\Agents\RA\2.0.8844.0).
When installing the agent a temporary directory is created on the machine (like: 4cf3806aac3ed28e02810670b5) copy during installation the files from this directory to temp directory.
Now you have a valid copy of the installation files. Copy these installations files to the server that fails to upgrade the agent (directory C:\WINDOWS\Microsoft Data Protection Manager\DPM\Agents\RA\2.0.8844.0\) and retry the agent upgrade

Not a very nice solution, but at least it worked for me…

SharePoint 2007 recovery point fails after Password change

There are many reasons why a SharePoint recovery point keeps failing. It also a good idea to check the logs on the Web front-end and SQL backend server.

In our case we found the following errors in the system log of the SharePoint Web front-end

Event Type: Error Event Source: DCOM Event Category: None Event ID: 10004 Date: 10-2-2010 Time: 16:10:49 User: N/A Computer: <server_name> Description: DCOM got error "Logon failure: unknown user name or bad password. " and was unable to logon <account_name> in order to run the server:{

Event Type: Error Event Source: DCOM Event Category: None Event ID: 10005 Date: 10-2-2010 Time: 18:14:55 User: N/A Computer: <server_name> Description:DCOM got error "The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. " attempting to start the service vds with arguments "" in order to run the server:

Reason / Cause
In our case this error was caused by a Password change of the account we used (a long time ago) to configure SharePoint protection.

Solution
After you change the password of the account you used for the ConfigureSharePointProtection, you need to run the commands again on the SharePoint Web Front-end machines.

ConfigureSharePoint –EnableSharePointProtection
ConfigureSharePoint –EnableSPSearchProtection
All available commands: http://technet.microsoft.com/en-us/library/dd441708.aspx

Sharepoint 2007 Protection error

When you try to add a SharePoint farm to a DPM protection group you may get the error below.

The operation failed because an error occurred while enumerating the data source for Virtual SSP Writer. Check to see that the data source specified in the error message is online and accessible. ID: 921 Details: The system cannot find the path specified (0x8007003)

You will receive this error when trying to expand the SharePoint Front-end server.

Resolution \ Cause:
The might be caused by a missing MTATempStore$ share on your SharePoint frontend server. Check if the directory %program files\Data Protection Manager\Temp is shared as MTATempStore$. The default permission is Everyone full control. This can be changed as long as the account you used for configuring the WssCmdletsWrapper has access to the Share.
Now you can retry to add the SharePoint farm to the Protection group

System State back-up fails – part x

The system state back-up fails on a Windows 2008 server with SQL 2005 installed.

The error message on the DPM server is a bit confusing

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)

There is enough free space available and the system state back-up worked before, this confirms that the Windows Server backup application is successful installed.

The first steps of troubleshooting are: kicking off the system state back-up locally on the protected server and checking the event log

Stating the system state backup locally should be done from the command line interface:
wbadmin start systemstatebackup -backuptarget:x
(x – should be replaced with the drive letter where you like to store the system state backup)

In our case this local back-up fails as well. Surprising is that; we did not select the SQL database to be included in the back-up but the application log is still full with SQL backup errors.

An overview of errors

Log Name: Application Source: SQLinstance Date: 5-2-2010 10:53:51 Event ID: 18210 Task Category: (2) Level: Error Keywords: Classic User: SYSTEM Computer: servername.domain.ad Description:BackupMedium::Report Error: write failure on backup device '{18C03E39-BD81-4166-8BE1-230C4343980F}6'. Operating system error 995(error not found).

Application error 1

Log Name: Application Source: SQLVDI Date: 5-2-2010 10:53:51 Event ID: 1 Task Category: None Level: Error Keywords: Classic User: N/A Computer: servername.domain.ad Description:SQLVDI: Loc=SVDS::CloseDevice. Desc=Abort detected. ErrorCode=(0). Process=3072. Thread=5916. Server. Instance=xxxxxxx. VD=Global\{18C03E39-BD81-4166-8BE1-230C4343980F}4_SQLVDIMemoryName_0.

Application error 2

Log Name: Application Source: SQLWRITER Date: 5-2-2010 10:53:51 Event ID: 24583 Task Category: None Level: Error Keywords: Classic User: N/A Computer: servername.domain.ad Description:Sqllib error: OLEDB Error encountered calling ICommandText::Execute. hr = 0x80040e14. SQLSTATE: 42000, Native Error: 3013 Error state: 1, Severity: 16 Source: Microsoft SQL Native Client Error message: BACKUP DATABASE is terminating abnormally. SQLSTATE: 42000, Native Error: 3202 Error state: 2, Severity: 16 Source: Microsoft SQL Native Client Error message: Write on "{18C03E39-BD81-4166-8BE1-230C4343980F}2" failed: 995(error not found)

Application error 3

Log Name: Application Source: SQLinstance Date: 5-2-2010 10:53:51 Event ID: 3041 Task Category: (6) Level: Error Keywords: Classic User: SYSTEM Computer: servername.domain.ad Description: BACKUP failed to complete the command BACKUP DATABASE <DATABASENAME>. Check the backup application log for detailed messages.

Application error 4

Log Name: Application Source: Microsoft-Windows-Backup Date: 5-2-2010 10:53:55 Event ID: 521 Task Category: None Level: Error Keywords: User: SYSTEM Computer: servername.domain.ad Description:Backup started at '5-2-2010 9:52:41' failed as Volume Shadow copy operation failed for backup volumes with following error code '2155348129'. Please rerun backup once issue is resolved.

Application error 5

The errors in the application log indicate that there is an issue with the SQL databases which causes the SQL VSS-writer to fail during the system state back-up.

This can be confirmed by stopping the SQL services and try the system state backup again. Now the back-up is successful.

One of the SQL database is causing the SQL VSS-writer to fail. Application error 4 shows which database is causing the issue.

In our case we contacted the SQL application error, who did his magic. (I do not have the details).

After this the System state back-up is successful

Enable End-User Recover in DPM fails

When you want to enable End-User Recovery on a DPM servers run Windows 2008, you will probably run into an error

To enable End_user recovery you should click on the recovery tab and then under actions  click on “Configure end-user recovery” and click Configure Active Directory"

This will result in an error: “Active Directory could not be configured because the Active Directory domain could not be found. Make sure that the domain name is properly constructed. The following example shows a properly constructed domain name: city.corp.company.com” 

The reason is the way the security of Windows 2008 is configured

The workaround is to use the DPMADSchemaExtension.exe tool, located in C:\program files\Microsoft DPM\DPM\End User Recovery. In order to run this tool logon to a domain controller map to the directory above and run DPMADSchemaExtension.exe.

1. Enter Data Protection Manager Computer Name –> Enter here the DPM server name : Note: this is not the FQDN name of the server, but just the server name.
2. Enter Data Protection Manager Server domain name –> Enter here your domain name. Note: This will be the FQDN domain name so if your domain is yourdomain.local enter yourdomain.local
3. Enter Protected Computer Domain Name –> This field can be left blank if the DPM server is in the same domain as the Domain Controller that owns the Schema master role.
4. Click OK on the next to Information screens
5. On the DPM server open the DPM 2007 Administrative Console, select the recovery tab and then under actions  click on “Configure end-user recovery”  Notice that the configure active directory button is grayed out and that you can place a check mark in the “Enable end-user recovery” check mark button.
6. You will get a warning telling you that you must wait for a synchronization to take place before the setting change takes effect. Click OK

 

The information in this post is taken from the source below (Keith Hill). I was only able to find the result in the Google cache therefore I recreated this document.

Source: http://209.85.229.132/search?q=cache:sOz_ZPThi7AJ:blogs.technet.com/askcore/archive/2008/06/29/dpm-how-to-enable-end-user-recovery-using-windows-2008-server.aspx+dpm+end+user+recovery+schema&cd=3&hl=en&ct=clnk&gl=nl

Windows 2008 (R2) system state fails due to . . .

I have been troubleshooting a issue with a failing System State backup on 2 Windows 2008 R2 servers. These two servers both run Exchange 2010.
The DAG backup with DPM 2010 works perfect, but the system State keeps failing with this error in the application log.
--------------------------------------------
Log Name:      Application
Source:        Microsoft-Windows-Backup
Date:          2-11-2009 17:36:18
Event ID:      521
Task Category: None
Level:         Error
Keywords:     
User:          SYSTEM
Computer:      <server_name>
Description:
Backup started at '2-11-2009 16:36:13' failed as Volume Shadow copy operation failed for backup volumes with following error code '2155348129'. Please rerun backup once issue is resolved.
--------------------------------------------

According to some Forum post the error code '2155348129' may be caused by the incorrect Active volume. (When a OEM Partition is the active partition instant of the system partition) 
http://social.technet.microsoft.com/forums/en-US/winserverfiles/thread/d5daada2-b78b-4935-bd9e-80726c26c4a8/ 

But this is not the case here.

A closer look in the application log shows a second error for the Forefront Vss writter:
--------------------------------------------
Log Name:      Application
Source:        FSCVSSWriter
Date:          2-11-2009 17:36:17
Event ID:      11003
Task Category: (11)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      <server_name>
Description:
Microsoft Forefront Protection VSS Writer failed when preparing for backup. Writer instance: FSCVSSWriter Error code: 0x00000000
Event Xml:
--------------------------------------------

Workaround:
I found a workaround With a little help of this post

-> Disable the Forefront Protection VSS Writer in the service Panel

In the same post is also an issue with the SQL VSS\Hyper-V writer mentioned as cause.

SharePoint protection failed

DPM can be used to protected Microsoft Office SharePoint 2007 or Windows SharePoint Services 3.0. DPM used the SharePoint VSS writer for this Protection. More details in the post SharePoint Protection with DPM

To provide the DPMRA agent with the necessary permissions to protect SharePoint, you need to run the ConfigureSharepoint.exe tool. This utility configures the WSS Writer service and any associated services with the correct credentials required to access the farm for backup and recovery purposes.

This works like a charm in most environments. However in some highly secured domains you can run in to issues. When a Group Policy overwrites the required permissions, the protection will fail.

In this case you will see errors like below.

Error on the DPM Server:
------------------------------------------------------------------------------------
Recovery point creation jobs for Shared Services Provider SSP_Database_server_name\Instance\database_name on SharePoint front-end_server_name  have been failing. The number of failed recovery point creation jobs = 4.
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)

An unexpected error occurred during job execution. (ID 104 Details: The server process could not be started because the configured identity is incorrect. Check the username and password (0x8000401A))
------------------------------------------------------------------------------------

Error in the application log of the WFE (SharePoint Front-end):

Event Type:    Error
Event Source:    DCOM
Event Category:    None
Event ID:    10004
Date:        29-10-2009
Time:        10:05:04
User:        N/A
Computer:    <WFE server>
Description: DCOM got error "Logon failure: the user has not been granted the requested logon type at this computer. " and was unable to logon <domain>\<configuration account> in order to run the server:
{E95EF0B1-D0E3-45D9-B699-8B37F068CF25}
------------------------------------------------------------------------------------

This can be related to Log on as a batch job permission that should be assigned to the account you specified when running the ConfigureSharePoint.exe command.

This right is set by the ConfigureSharepoint.exe –EnableSharePointProtection command. Make sure this right is not overwiten by your security (Group) policies.

Change the location of the system state backup file

As you might know, DPM stores the system state of a machine first locally on the protected machine before copying the data to the DPM server. DPM select the most suitable disk for the local copy of the system state when you run the backup for the first time. You might want to change this location when available disk space changes or when you add additional disk to your system.
This can be done by editing the configuration file on the protected computer. 

(Technet)
The backup file of system state is created at %systemdrive%\DPM_SYSTEM_STATE.

To change the location of the system state backup file

1.On the protected computer, open PSDatasourceConfig.xml in an XML or text editor. PSDatasourceConfig.xml is typically located at install path\Program Files\Microsoft Data Protection Manager\DPM\Datasources.

2.Change the <FilesToProtect> value from %systemdrive% to the desired location.

3.Save the file.

4.On the DPM server, if there is a protection group protecting the system state of the protected computer in step 1, run a consistency check.

5.The consistency check will fail and generate an alert. Perform the recommended actions in the alert as follows:

a.In the alert details, click the Modify protection group link, and then step through the wizard.

b.Perform a consistency check

-------------------------------------------------------------------

When you have issues with backing up the system state of the machine you should always check the logs on the local machine.

-Application log
-C:\Windows\Logs\WindowsServerBackup

FI: Backup started at ‘’ failed with following error code '2155348165' ( There was a failure in preparing the backup image of one of the volumes in the backup set. ). Please rerun backup once issue is resolved.

Fast inventory fails

Found that the fast inventory of the Tape library in DPM can fail or show the wrong results in some cases. According to a newsgroup post this can be caused (in certain types of libraries) by the press of a cleaning tape.

The post reports this for IBM 35XX series and HP 1/8 tape libraries. We have seen the same issue on the Dell TL2000 tape library which is actually an IBM Totalstorage 3573 Tape library.

The workaround is to remove the cleaning tape from the library.

The newsgroup threat also describes a fix setting a registry key. (I have not tried this yet)

The rekey fix is to handle some  unexpected behavior of tape library. The issue is when there is cleaner media present in some library element (slot/drive/transport ) the IOCTL_CHANGER_GET_ELEMENT_STATUS for that particular elment returns with ELEMENT_STATUS_EXCEPT set in CHANGER_ELEMENT_STATUS.Flags and CHANGER_ELEMENT_STATUS.ExceptionCode is set to ERROR_UNHANDLED_ERROR.  This is unexpected behavior as per WHQL and as a result of this you will see Fast  Inventory failing with "Hardware Issue". The workaround is added in DPM 2007 SP1 and we have seen this issue with only IBM 35XX series and HP 1/8 tape library

Thanks to Sachin

Link to full newsgroup threat

The DPMRA service terminated with service-specific error 10048

After maintenance on one of the Exchange CAS/HUB servers the DPM server could not contact the DPM agent anymore.

The Error Code:

Log Name:      System
Source:        Service Control Manager
Date:          17-7-2009 14:36:34
Event ID:      7024
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      servername.domain.local
Description:
The DPMRA service terminated with service-specific error 10048 (0x2740).

This article on Microsoft site tells that this could be caused by another service running on the ports used by DPMRA service. (port 5718 and 5719)

To find which service this is you can use the command netstat –oan, this returns the ports and the corresponding PID. With the command tasklist /svc  you find the service involved.

In this case the service MSExchangeFDS (Microsoft Exchange File Distribution) was running on both ports.

We used the following work around:

• Stop the Microsoft Exchange File Distribution service
• Set the DPMRA service from manual to automatically
• Start the DPMRA service
• Start the Microsoft Exchange File Distribution service

This work around fixed the issue for us.

…
Thanks to Karl

Downloaded PowerShell Scripts won’t run

When you download PowerShell scripts from the internet you might find that they do not work on your local (DPM) Server.
The reason is PowerShell is configured to run in the most secure mode by default. This mode is the "Restricted" execution policy, in which PowerShell operates as an interactive shell only.

Error message:

The file C:\downloaded_script.ps1 cannot be loaded. The execution of scripts is disabled on this system. Please see "Get-Help about_signing" for more details

You can change this behavior with Set-ExecutionPolicy command in PowerShell

Example:

• Set-ExecutionPolicy Allsigned (Runs only signed scripts)
• Set-ExecutionPolicy Unrestricted (Runs all scripts signed and unsigned)

More options and information at: http://www.hanselman.com/blog/SigningPowerShellScripts.aspx

Regional Settings

I Found some unexpected behavior on a DPM server that is configured with an English OS, but with the Dutch regional settings.

When using the command: set-dpmGlobalproperty –DPMserverName <servername> -TapewritePeriodRatio 0.2 (this command configures the DPM settings for marking tapes ready for offsite storage)

This command works and the settings seem to be update.

When you after that request the active settings with the command: get-dpmGlobalproperty –DPMserverName <servername> TapewritePeriodRatio. You get the value back in the Dutch regional format, which is 0,2. (see above)

The workaround is to configure the server with US regional settings at least for the decimal symbol and digit grouping symbol

Thanks to Peer for his help on this.