DPM and the 100 failed file limit

Regular readers and viewers will know that I use Microsoft’s Data Protection Manager (DPM) a lot, and I’m a fan of the product, despite some serious issues with recent updates (see other DPM posts for the details)…

One thing that I never could never get my head around, though, is the fact that if you’re doing a file system backup, DPM will abort the job and mark it as a failure if it encounters more than 100 files that it can’t back up.

This is design madness in a backup product. Sure, log the failed files and tell us about them, but for the sake of all that’s holy don’t just abandon the job! That is not data protection…

Thankfully, there is a way you get around this if you have a server where this is an issue. On the server you’re having issues backing up, open the registry editor and navigate to:

HKLM\Software\Microsoft\Microsoft Data Protection Manager\Agent

Create a new key called ContinueOnFailure and a DWORD value inside it called MaxFailedFiles and leave it with a value of zero (0) to turn this feature off. If you use DPM to back up your entire environment, it may be worth looking at using a Group Policy to create this registry key on all your domain-joined machines to avoid having to deal with this issue in a reactive manner.

Share and Enjoy:
  • Digg
  • StumbleUpon
  • Technorati
  • del.icio.us
  • Twitter
  • blogmarks
  • HackerNews
  • Tumblr
  • Posterous
  • email
Bookmark the permalink. Follow any comments here with the RSS feed for this post.
Post a comment or leave a trackback: Trackback URL.

Leave a Reply

Your email address will not be published. Required fields are marked *

This blog is kept spam free by WP-SpamFree.