You are browsing the archive for 2009 August.

System Center Data Protection Manager 2007: New course and Exam

8:26 am in Uncategorized by mikeresseler

Hey All,

Just to let you know, now there is a new course for DPM available from Microsoft Learning:

Course 50213A – Implementing Data Protection Manager 2007

There is also now an exam on DPM

Exam 70-658: TS: System Center Data Protection Manager 2007, Configuring

More information can also be found on All Backed Up:



System Center Data Protection Manager 2007: Installation Part III: Patching, patching and patching

1:24 pm in Uncategorized by mikeresseler

Allright, here is part 3 of the installation of System Center Data Protection Manager.  This is the part where we are going to install a lot of hotfix rollups and hotfixes.

To have a good DPM installation, these hotfixes are needed or otherwise, you will have a lot of problems.  So here goes and here is the list of necessary hotfixes:


  • Description of the hotfix rollup package for System Center Data Protection Manager 2007: February
  • Description of the hotfix rollup package for System Center Data Protection Manager 2007: April
  • Description of the hotfix rollup package for System Center Data Protection Manager 2007: June
  • An Update is available for Windows Server 2008-based computers to address issues with backing up and restoring Hyper-V Virtual Machines
  • A replica may be listed as inconsistent after you install System Center Data Protection Manager 2007 Service Pack 1 on a computer that is running an x64-based version of Windows Server 2003
  • Availability of a Volume Shadow Copy Service (VSS) update rollup package for Windows Server 2003 to resolve some VSS snapshot issues


Now this looks like a lot of updates / hotfixes to install, but luckily, not all are necessary.  Because the Hotfix rollup package of June contains the previous ones (April and February) and also KB 9615012

So that leaves us with KB 970867, KB 959962 and KB 940349

KB 940349 is needed if your DPM server is running win2k03 (not in my case) but is also needed on EVERY windows 2003 server that will be protected by DPM.  Also note that this KB is best installed BEFORE you push an agent to that server.

KB 959962 is necessary when you want to protect virtual machines.  This update need to be installed on the Host Hyper-V systems and afterwards, you need to upgrade all the integration services on the virtual machines.

And the Hotfix rollup (KB 970867) will need to be installed on the DPM server.

Here’s how:

First, run the x64_DataProtectionManager2007-KB970867 (or the x86 variant)


Again, you get the same notifications as you received with the SP1 update.  Please also note that you will need to restart your DPM server if you didn’t installed the rollups before (As it is in my case) or when the DPM Console or Management Shell is open.


The license agreement


The installation


Again the question for the Microsoft Update (I really start to wonder here ;-))


And in the end he asks me to open the DPM console, and apparently I didn’t need to reboot after all.

Second part of the installation is the  SQLPrep package, unless you are running the dedicated instance on the DPM server as I do, so I don’t need to run this one.

Finally, you will need to run the Management Shell update on all computers where you have the Management Shell installed.

When that is all done, you need to start the DPM Management console and update the agents


Press the Update Available link for each agent.


Press Yes to continue.  The system tells you that you will need to run a consistency check afterwards.


Press the Update Agents button.


Now you need to fill in your credentials.  Make sure that you select the Manually restart the selected servers later because it is NOT necessary to restart the servers afterwards.


The system is upgrading the agent.



That’s it.  In the next posts we will be giving a further demonstration on how to configure DPM.

Till then,






System Center Data Protection Manager 2007: Installation Part II: The program and SP1

9:03 am in Uncategorized by mikeresseler

Hey All, here is part two of the installation manual for SCDPM.  In the previous part, we have prepared our environment and installed the prerequisites.  Now it is time to install the software itself and this part exists out of two steps:

Step 1: Installation of SCDPM RTM

After you start the installation, this is the first screen you get:


Choose Install Data Protection Manager.  Please note that this will automatically install the DPM Management Shell


As always, accept the License Terms


The Welcome screen, press next to continue


The installation wizard will now run a prerequisite check to verify if everything is ok.


Now the product registration


In this window, you need to select the SQL instance you want to use or create a new SQL installation which will be a dedicated one.  Note that DPM is only supported on a SQL 2005 environment.  In fact, you will not get past this screen if you try to install it on a SQL 2008 environment because the installer checks it.  In my case, I will go for the dedicated SQL installation which is the best solution in my opinion.  (After all, if your SQL server dies, you want to be able to restore it.  How are you going to start with it if you don’t have the DPM SQL anymore :-)


If you have chosen for the local dedicated installation, you need to choose a strong password for 2 local restricted accounts.  Make sure it is a strong one as these accounts their passwords don’t expire.  The accounts are:

  • MICROSOFT$DPM$Acct: This account runs the SQL Server service and the SQL Server Agent service
  • DPMR$<nameserver>: This account securely generates reports

Then press Next to continue


Here you can choose whether you want to use Microsoft Update or not.  Depending on the policies of your company you can choose to put this on or off.


Choose whether you want to make use of the Customer Experience Improvement Program


Finally you get the summary and we are ready for the installation.


This is a screen during the installation.  Notice that in my case the SQL Server installation is busy.


And finally, it is finished.  You get a link to get the latest updates for the product, but since we are going to install immediately Service Pack 1, I didn’t bother to visit the link :-)

Last but not least, you get this notification


I’ve tried to start the installation of SP1 without restarting but that doesn’t work :-)

Step 2: Installation of Service Pack 1


The first thing the installer did before starting with the installation was the installation of the Visual C++ 2008 Redistributable Setup


Of course you need to accept the license agreement.


This installation took a matter of seconds.


And now the upgrade of SP1 starts.  The first thing it does is inform you of possible issues that can arise during the upgrade:

  • Any jobs that are in progress or that are scheduled during the install will fail
  • The installation will backup the DPM database
  • The process can take a large amount of time if you protect a large or multiple large sharepoint farms.

These warnings are no problem for my installation as I don’t have any sharepoint farms or jobs for the moment since I am upgrading from a clean installation.


Again you need to accept the License Terms, and in the top bar you can see that this service pack is also known as KB 959605


No further configuration here, since it is an upgrade and the installation is busy


Again the question about the Microsoft Update (If you choose yes, you would get an additional screen for the update settings… but as I said, I prefer that this is arranged on organization level)


And the finish, notifying that you need to restart.


I’ve tried to start DPM without restarting but then you get this error:


After restarting, I was able to get into the DPM console


In the next part, I will discuss the various rollups and hotfixes that are necessary to install.



System Center Data Protection Manager 2007: Installation Part I: Prerequisites

9:02 am in Uncategorized by mikeresseler

Hey All,

In the next 3 posts, an installation guide for System Center Data Protection Manager 2007.  Let’s start with explaining the environment I’ve used and the prerequisites.

First, let’s look at the prerequisites as they are provided by Microsoft. (

First, the security requirements

1) Security Requirements

To install DPM you must be a local admin and logon to the computer where you want to install DPM.  OK, this can be arranged :-)

After the installation of DPM, you need to have a domain user with administrator access to use the DPM Administrator Console.  Basically, this means that when you need to be able to use the administrator console, you need to be a local administrator on the DPM server.

2) Network Requirements

According to Microsoft, you need to have a windows server 2003 or windows server 2008 active directory domain.  My testenvironment is a native windows server 2008 domain so no problems there.  You also need to have persistent connectivity with the servers and desktop computers it protects and if you are protecting data across a WAN, then you need to have a minimum network bandwidth of 512kbps.  So far so good

3) Hardware Requirements

Disks:  You should have a disk that contains the storage pool and one that is dedicated to system files, DPM installation files, prerequisite software and database files.  Basically, this means that you need an OS and program files just as any other server (you can divide it into multiple volumes) but the storage dedicated for the backups can’t be the same as above.  When DPM takes the storage, it allocates it and it is not usable for something else.

CPU: Minimum 1Ghz, Recommended 2.33 Ghz

Memory: Minimum 2 GB RAM, Recommended 4 GB Ram

Pagefile: 0.2 percent the size of all recovery point volumes combined, in addition to the recommended size (1.5 times the Memory)

Disk Space:

– Minimum: Program Files: 410 MB, Database: 900 MB, System Drive: 2650 MB

– Recommended: 2 till 3 GB of free space on the program files volume

Disk Space for storage pool: 1,5 Times the size of the protected data, recommended = 2 – 3 times the size of the protected data

LUNS: Maximum of 17 TB for GPT dynamic disks, 2 TB for MBR disks

32-bit servers: 150 data sources

64-bit servers: 300 data sources

Since this will be a test environment, there is no way I’m going to follow the complete requirements for DPM. :-)

4) Operating System Prerequisites

32-bit or 64-bit servers.  No ia64 bit is supported

The DPM server cannot be a management server for SCOM

The DPM server cannot be an application server or an DC server.

There is a VSS limitation on 32-bit servers.  It can’t outgrow 10 TB of protected data.  Preferred is 4 TB on a 32-bit server.

OS: Windows Server 2008 Standard and Enterprise Edition or Windows Server 2003 (R2) SP2 or later or Windows server 2003 Advanced server or Windows Server 2003 Storage server.

The management shell can also be run on windows XP SP2, Vista and Windows Server 2003 SP2 or later.


My Environment

I will run the server on a Hyper-V platform (Not yet R2) and I’ve created a virtual machine with the following specifications

CPU: 2 * 3.60 GHz Xeon

Memory: 2048 MB

Storage: C:\ 40 GB  (OS and application) D:\ 60 GB (Play storage for backup)

OS: Windows Server 2008 x64 SP2, Fully patched

Software Prerequisites

Before I started with the installation, I’ve installed following things first:

– IIS 7 with the following options on:

  • Common HTTP Features
    • Static Content
    • Default Document
    • Directory Browsing
    • HTTP Errors
    • HTTP Redirection
  • Application Development
    • ASP.NET
    • .NET Extensibility
    • ISAPI Extensions
    • ISAPI Filters
    • Server Side Includes
  • Health and Diagnostics
    • HTTP Logging
    • Request Monitor
  • Security
    • Windows Authentication
    • Request Filtering
  • Performance
    • Static Content Compression
  • Management Tools
    • IIS Management Console (not really a prerequisite but handy ;-))
    • IIS 6 Management Compatibility
      • IIS 6 Metabase Compatibility
      • IIS 6 WMI Compatibility
      • IIS 6 Scripting Tools
      • IIS 6 Management Console


– SIS (Single Instance Store)

To enable this, open a command prompt with administrator privileges and run the following command:

start /wait ocsetup.exe SIS-Limited /Quiet /norestart


After this is finished, restart the server.  To check if the SIS is enabled, open regedit and check the existence of the following key:



That’s it

In the next part, the installation of SCDPM 2007

Till then,



System Center Data Protection Manager: Powershell script

12:02 pm in Uncategorized by mikeresseler

Hey All,

Another interesting Powershell script:

Allow DPM to backup itself:

Set-DPMGlobalProperty -DPMServerName <servername> -AllowLocalDataProtection $true