You are browsing the archive for QFE.

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

Screenshot13

Second thing was inserting the new registry key

Screenshot01

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

Screenshot15

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

Screenshot16

 

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

Screenshot17

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

Screenshot11

Screenshot12

Next post will go deeper into the Client protection

Cheers,

Mike

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.

Screenshot03

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

Screenshot05

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

Screenshot06

Accept the license agreement

Screenshot07

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

Screenshot08

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

Screenshot09

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

Screenshot10

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

Screenshot11

Screenshot12

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

Cheers,

Mike

New QFE available for DPM 2010

2:55 pm in Uncategorized by mikeresseler

The DPM product team has just released a new QFE: http://support.microsoft.com/kb/2465832

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: http://www.microsoft.com/downloads/en/details.aspx?FamilyID=d3fabb18-1adb-4c87-a95d-d3c3826d5bfb&displaylang=en

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

Have fun with this great release

Cheers,

Mike