You are browsing the archive for 2009 December.

System Center Data Protection Manager 2007: TCP Chimney and Bandwidth throttling

3:22 pm in Uncategorized by mikeresseler

Hey All,

I’ve seen a number of cases where the backup of hyper-v guests is failing and also where the backup is extremely slow.  Almost every time, some small adjustments need to be made to fix them, but if you are not the network administrator or hardware administrator, this can cause a lot of discussions.

Suppose you have a DPM server with all the latest patches till date, a hyper-v host and some virtual machines.  You are of course also backing up other stuff from other servers.  You notice that your hyper-v guests are failing (the consistency check is running but never ends, file backups take a lot of time and so on…)

For the hyper-v guests backup, make sure that you check the TCP Chimney Offloading in windows.  When this is enabled on the host drive, it doesn’t always work.  I don’t know why but when I disabled it (both on the DPM server and on the hyper-v host) the backup ran without any problems.

The command to do that is netsh int tcp set global chimney=disabled

Now that the backups are running, the speed isn’t still optimal.  I read somewhere (but I can’t remember where and can’t find it back) that you sometimes need to enable bandwidth throttling.  I did that, gave it a huge number (it was off after all…) and after that we saw a huge increase in backup speed.

One doesn’t always have to do with the other but when you are experiencing failed backups or slow backups, it is certainly worth the try by disabling the TCP Chimney Offloading and enable the bandwidth throttling.  It might save your day :-)



PS: If you want more information on TCP Chimney, visit


System Center Data Protection Manager: Cool script

7:51 pm in Uncategorized by

Hey All,

One of my colleagues is managing a rather large environment on a daily base.  He has to manage two backup solutions (HP Data Protector and SCDPM) that share one tape library.  From time to time, he need to set a tape not free in that library (Otherwise SCDPM will use that tape while it is needed for the HP solution).  To do his work faster, he created a small powershell script where he has to give the name of the slot in order to mark that tape as not free.

So here it is:

$LIB = Get-DPMLibrary -DPMServerName "<servernaam>"

$TP1 = Get-Tape -DPMLibrary $LIB

$TapeLocationList = Read-Host "Tape location (Slot-x) "

foreach ($media in $TP1)


if ($TapeLocationList -contains $media.Location)


Set-Tape -Tape $media -NotFree

Echo "Tape in $($media.Location) marked as NOT FREE."




Echo "Tape in location $($media.Location) is not in requested slot."







PS: Thanks to Steven Van der Taelen for writing this script

System Center Data Protection Manager 2007 SP1: Bare Metal Recovery of Windows Server 2008

8:54 am in Uncategorized by mikeresseler

Hey All,

Microsoft has updated its whitepaper Bare Metal Recovery of Windows Server 2008 with System Center Data Protection Manager 2007 SP1

It can be found at

Important to know is that the DPM SRT (System Recovery Tool) that is used for recovering windows 2003 and windows XP has been completely replaced by the built-in backup utility of Windows server 2008, the WSB (Windows Server Backup) utility.

In the white-paper, they give a step-by-step instruction on how to enable bare metal recovery of a windows server 2008

Except for the fact that you need to do some additional work, this procedure certainly has some possibilities for the BMR of a physical windows server 2008. 

Still, I believe more in the procedure of working with the offline P2V which was discussed two weeks ago.  Since Matthijs Vreeken has responded on my questions I’m gonna keep working on this procedure and test it out.



System Center Data Protection Manager 2010 – SQL End-user Recovery

8:57 am in Uncategorized by mikeresseler

Hey All,

While reading up on the different blogs I follow, I found this interesting post from Anders Bengtsson, Microsoft MVP.

It’s all about SQL End-user Recovery.   In DPM 2010, it is possible to give SQL Administrators the rights to recover their databases without the need for a backup administrator.

See the article for the technical specifications (

The end-user recovery drew my attention for the following reasons:

– End-user recovery makes the live of a backup administrator more easy.  In 2007, when we implement the end-user recovery for files for users, we notice every time again, that the backup administrators are having less work

– Doing this for SQL administrators gives you an additional advantage.  Imagine that you have a test environment at your site.  This test environment is a virtualized “copy” of your production environment.  The programmers team is doing different things there and testing new features and so on.  They need a refresh of the database very often.  Now the SQL team can do this instead of the backup administrator.  How cool is that.  You as a backup administrator have less work, the programmers team will be helped more quickly, it’s a win win situation :-)


Now I am wondering if Microsoft would pull this further? What if we could delegate end-user recovery tasks for exchange, sharepoint and so on…

For the moment this is not possible, or at least I don’t have no documentation about this yet, but when I see the power of the SQL end-user recovery, I’m quite sure that this will be a much requested feature for the future



System Center Data Protection Manager 2007 SP1: Sharepoint issues

8:28 am in Uncategorized by mikeresseler

Hey All,

One of our engineers was having a big issue with the protection of a sharepoint farm.  In DPM, he could not resolve the following error:

The replica of SSPComponent_SSP Intranet on servername is inconsistent with the protected data source. All protection activities for data source will fail until the replica is synchronized with consistency check.

He has searched a lot on the problem but finally found that the problem was not with the DPM program but with the Sharepoint configuration.

The problem was that some service accounts tried to do a remote log-on to the server.  These service accounts are used for the timer / search server functions and had the appropriate rights locally but did not had the rights to do this remotely.

After adding the service account the rights to “logon as a batch” and “logon as a service” it suddenly started to work again.