You are browsing the archive for 2011 March.

DPM 2012: The preview

6:25 pm in Uncategorized by mikeresseler

As MMS 2011 is going to the end, today was the most wanted session of the entire summit Winking smile


The session started with the overview of how DPM has changed over the years, starting with V1, V2 and so on… Now, with DPM 2010 (which is V3) gaining more momentum, the team released what the new stuff will be in V4, or DPM 2012

The nice thing is that they listened to all of us out there, and implemented the most requested features


So what can we expect for the next release:

Centralized Management

  • Centralized Monitoring
  • Remote administration
  • Remote recovery
  • Role Based management
  • Remote corrective actions
  • Scoped Troubleshooting
  • Push to Resume Backups
  • SLA based Alerting : Alert only when SLA violated
  • Consolidated Alerts ensure one ticket per root cause issue
  • Alert categorization (Ex: infra alerts versus backup failure alerts)
  • Allow admins to automate/extend the base functionality using PowerShell


I can’t show you screenshots of how it looks, because they did a live demo but I can guarantee you that the crowd in the room went wild.  The integration with OpsMgr is very neat and gives you real good tools to work on your DPM server(s) easy, straight to the point and last but not least… FAST.

Role-based management


You asked for it, you get it.  While you still need to be admin on the DPM box to be able to manage it, in the next version there will be different roles available for you to scope your DPM environment to the right people.  While the picture above will probably still be subject of change, I think it is clear that role-based administration is on the way, and that the combination of DPM role-based administration and OpsMgr integration…. Well, I think it speaks for itself Smile

Certificate Base Protection


DPM 2010 already has workgroup support… With DPM 2012, this will be done by certificates, which is much easier to manage in larger environments and from a security point of view will be much more appreciated by the security people.  Oh yeah, and there will be support for workgroup clustering protection.

Tape Media Co-location


In DPM 2012 you will have the possibility to co-locate multiple protection groups on one tape set… Yes, you have read that correctly Smile

SharePoint item-level recovery


In DPM 2010 and with SharePoint 2010 you already had easy Item-Level Recovery.  (It is also possible with SharePoint 2007 but then you need the recovery farm)  It can take a while to recover a single item, but it’s there.  In 2012, they will enhance that experience and recover much faster then before.

Virtual DPM Enhancements


You run DPM virtually?  (Which works well BTW) You can’t do item-level recovery of hyper-v because of this?  It’s coming now!

Generic Data Source Protection


For me, this is one of the most exciting features.  This will open up DPM to every Microsoft workload as long as the product team will adapt this.  And they will need to do that.  As example, we were shown how Virtual Machine Manager has already leveraged this to protect the VMM database.  In the future, they will extend that with the protection of the VMM library so that you can protect VMM the same way as SharePoint.  One-box, one-click, and of you go.

Want more?


Watch out for the future because more exciting things are coming.  Integration with Service Manager.  Powershell integration.

Should I wait to install DPM?

NO!  Start now by implementing DPM 2010 already.  The centralized management will be able to connect to your DPM 2010 boxes.  There is no need to wait because the product is ALREADY great, and with the upgrade track / side-by-side migrations and everything they will provide us with it will be easy to go to DPM 2012 when it is released.

If you have questions or want to know more about DPM, don’t hesitate to contact me through this blog or contact the Microsoft people.



Getting the non-administrator client recovery working in DPM 2010

8:47 am in Uncategorized by mikeresseler

As said in a previous post, with the latest QFE, it is now possible to give your end-users the possibility to recover data from the DPM server through the DPM Client UI, without them being local administrator on their machine.

This is a feature that many administrators wanted, and now it is finally there.

So after installing the QFE on my environment, I started to test this out.

Now here is the first catch…

There is a mistake in the documentation of the KB.  It states the following:

The administrator of a client computer has to set the name of non-admin users who have permissions to perform end-user recovery of protected data of a client computer.  To do this, the administrator must add the following registry key and value for each of those non-admin users

Registry Key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Data Protection Manager\Agent\ClientProtection and then create a new key called ClientOwner as REG_MULTI_SZ

So first thing is browse to that hive


Second thing was inserting the new registry key


When I couldn’t get it working, I wrote an email to the product team and also digged in to the log files.  There it clearly stood that the key needed to be ClientOwners with an S at the back.

PS: REG_MULTI_SZ = Multi-String Value


I changed that, but it still didn’t work as I expected.  Luckily, the product team replied very fast (thank you Venkat!) and gave me the naming convention to use for placing the non-admin users in that key. (which I had wrong also ofcourse…)

The convention is: DOMAIN\Username



And if you want multiple non-admin users in that registry, then you need to use DOMAIN\Username, DOMAIN\Username2


When that was done, I rebooted the windows computer, waited until a backup was taken and then it worked:



Next post will go deeper into the Client protection



Update: Thanks to Alex Smits, who saw I had the wrong QFE link…

DPM QFE installation

9:18 am in Uncategorized by mikeresseler

Our MMS presentation is in two weeks, and I have already started building servers a while ago, but now that the DPM product team has released a QFE I decided to install it on my demo environment.  Many of you will say that this a bad idea considering that MMS is so close and things could go wrong… but my trust in the DPM product team is high so I just went on with the installation :-)

As always, my advice is to read the entire knowledge base very well, to make sure that you understand how to install this.

On of the prerequisites of installing this is KB2223201 when DPM 2010 is installed on Windows Server 2008 R2 or KB2279787 when DPM 2010 is installed on Windows Server 2008.

Because I never installed the KB2223201 on that demo machine, I decided to have a look at what the issues could be…

The installer checks this however, and I don’t get the change of installing the update without the hotfix.


Make sure that you have this hotfix in front, because this one requires a reboot, and that is something you don’t want to do in the middle of the day.

Now that I got rid of the hotfix prerequisite, I could start the actual installation


Information about the jobs that will fail and that there will be taken a backup of the DPM database


Accept the license agreement


And that’s it, the installer is installing the update


Press Close to finish the installation.  I left the Open DPM 2010 administrator console checkbox on because I want to deploy the update to my agents asap, so that I could keep them protected


As you can see, every agent requires an update.  By selecting them (or doing it one by one) and clicking on the update available link, you can start the upgrade process


You will get a notification again that running jobs will fail, but then again, they would fail anyhow because you are not running the latest agent version Smile



And finally it is finished.

This was an installation for a single DPM server with the SQL dedicated on the same box.

If you have the SQL remotely installed, don’t forget to run the Sqlprep-KB2465832.msp (the x64 or x32 depending on your situation) BEFORE you start upgrading your agents.

If you have the DPM Management shell installed on a remote computer, then run the DPMManagementshell2007-KB2465832.msp

And if you have custom DPMRA ports then you need to do additional work after the installation (see the KB for information)

The same goes when you have IBM libraries, read the document carefully.

That’s it for today.

Next thing is testing the client protection with a non-admin user Smile



New QFE available for DPM 2010

2:55 pm in Uncategorized by mikeresseler

The DPM product team has just released a new QFE:

Things that got resolved:

  • When you change the ports that are used by the Data Protection Manager 2010 Remote Access service, recovery jobs may fail.
  • On some client computers, the System volume runs out of space when local shadow copies are created and when the shadow copy storage is set to UNBOUNDED.
  • When you try to use one Data Protection Manager 2010 server to protect more than 1,000 client computers, you receive a warning that states that you cannot protect more than 1,000 client computers by using Data Protection Manager 2010. You receive this message even though Data Protection Manager 2010 can protect up to 3,000 client computers.
  • When you try to use one Data Protection Manager 2010 server to protect more than 1,000 client datasources, you receive a warning that you cannot protect more than 1,000 datasources by using Data Protection Manager 2010. You receive this message even though Data Protection Manager 2010 can protect up to 3,000 client datasources.
  • Data Protection Manager 2010 does not support the IBM System Storage TS2900 Tape Autoloader backup, recovery, or detailed inventory operations. The tape is left behind in the drive after any of these operations.
  • When you use Data Protection Manager 2010 Replication Agent to protect a 1.2 terabyte SQL server that has lots of .ndf secondary data files, Data Protection Manager 2010 Replication Agent crashes.
  • If you are not the administrator on a client computer, you cannot perform an end-user recovery of protected data on the client computer.
  • When there are many client computers that trigger client back up or client recovery operations, corresponding jobs are not triggered on the Data Protection Manager 2010 server. When the Data Protection Manager 2010 server enters this state, any later client backup or client recovery operations are not triggered on the Data Protection Manager 2010 server.
  • Data Protection Manager 2010 experiences slower performance if you try to protect more than 300 client datasources on a secondary Data Protection Manager 2010 server.
  • Data Protection Manager 2010 does not keep a recovery point for a client datasouce that was not synchronized during the retention period.
  • If there are many list items within of a SharePoint List in a SharePoint Content Database, the generation of a SharePoint Item level catalog will fail continuously for the SharePoint Content Database.

When I look at the things that got fixed, there is one in particular that drew my attention…

If you are not the administrator on a client computer, you cannot perform an end-user recovery of protected data on the client computer…

That is something huge!  That is actually something we were asking for and while we always thought that they would give it to us in the next version or if we got lucky in a service pack, we already have it now.  Now every company that owns DPM should really look at the client protection!

Download link:

And as always, make sure that you follow the install guidelines correctly.

Have fun with this great release



DPM 2012

3:48 am in Uncategorized by mikeresseler

The MVP summit is over, had a great time over here meeting a lot of people, placing faces to people that I’ve worked and chatted with. 

But the most important thing about the MVP summit is the interaction with the product team.

And the guys of the DPM product team did a great job hosting this event for us.  We have discussed many things, and seen some great stuff.

And the cool thing that we learned is that the product team does listen to the customers and the it community.

Those of you who took the time and effort to fill-in the future survey that was available on the connect site can start getting curious.  I’ve seen the results of the survey, and I’ve already seen the response of the product team to that.

You want to know more?  Sorry, can’t tell you more… at least not just yet.

For those of you who go to the MMS summit, I definitely would recommend to go to the following session:

BB18: A first look at DPM 2012:

Hope to see you all there… It will be fantastic… You will cheer for it… You will love it… I promise