Disaster Recovery

Data Protection Manager 2010 QFE Rollup Package 2 installation tips

Microsoft has released the QFE Rollup Package 2 for System Center Data Protection Manager 2010. Scott Lowe discusses what the release fixes and shares tips on installing the QFE Rollup Package 2.

At Westminster College, we made the move to Data Protection Manager (DPM) 2010 last fall and, overall, we've been very pleased with the product. This week, I updated Westminster's DPM 2010 installation with the QFE Rollup Package 2 for System Center DPM 2010. The rollup corrects a number of issues, which includes the following:

  • When protecting more than 1,000 client data sources from a DPM 2010 system, you're told that you can't protect more than 1,000 sources --this is incorrect. DPM 2010 can protect up to 3,000 client data sources.
  • When you change the ports that are used by the DPM 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.
  • If you are not the administrator on a client computer, you cannot perform an end-user-recovery of protected data on the client computer.
  • If there are many list items within a SharePoint List in a SharePoint Content Database, then the generation of a SharePoint Item level catalog will fail continuously for the SharePoint Content Database.

There are also a number of client-based resolutions (such as i9n, the protected workload - protected desktops) that help bring DPM 2010 further into the realm of enterprise-grade protection software. With DPM, you need to be a pretty strong Microsoft shop; the QFE Rollup Package 2 does not add support for third-party platforms.

Visit the Microsoft site to find out all of the issues that are resolved with the QFE Rollup Package 2 for DPM 2010.

Installation tips

Depending on how DPM 2010 is configured in your environment, there are up to four files that you need to download in order to complete the installation of the QFE Rollup Package 2:

  • Required hotfix (a reboot may be required):
    • If the DPM 2010 server is running on Windows Server 2008, apply this hotfix before installing the QFE Rollup Package 2.
    • If the DPM 2010 server is running on Windows Server 2008 R2, apply this hotfix before installing the QFE Rollup Package 2.
  • On the DPM server:
    • Install the DPM 2010 QFE rollup 2 hotfix from the QFE rollup 2 download page. This file is named DataProtectionManager2010-KB2465832.exe. No restart is necessary.
  • On the SQL Server that holds your DPM database:
    • You can skip this step if you're using the DPMDB SQL Server instance on the DPM 2010 server. You only need to apply this step if you're not using the DPM 2010 default SQL configuration.
    • If the SQL Server is a 32-bit installation, install the file named SqlPrep-KB2465832_x86.msp.
    • If the SQL Server is a 64-bit installation, install the file named SqlPrep-KB2465832_amd64.msp.
  • On any systems used to manage the DPM server:
    • This is not required on the DPM server itself.
    • Install the file named DPMManagementShell2010-KB2465832.msp.
Once the server side of the equation is up-to-date, you need to turn your attention to the client side. Open the Data Protection Manager console, navigate to the Management zone, and choose the Agents tab. On the Agents tab, you will see that all of your agents are now in an OK status, but the Agent Updates column indicates that an update is available for these systems. In Figure A, you can see that most of the listed systems have an update available. I've already applied the update for some of the systems, so there is no longer an available update for these systems. Figure A

Updates are available for the DPM agent.
When you choose to perform an agent update by clicking the Update Available link, DPM will warn you that any running protection jobs will fail while the agent is being updated, and it may also cause the existing replicas to move into an inconsistent state; this is easily rectified by scheduling a consistency check once the upgrade is complete (Figure B). In my case, all of our protection groups are configured to automatically run a consistency check in the event that a replica becomes inconsistent, so I let DPM do the work for me. Bear in mind that a consistency check can put a strain on the DPM server and the protected item, so schedule it appropriately. Figure B

A consistency check can be an intensive operation.

Conclusion

DPM 2010 is far superior to earlier versions of the product, and I look forward to seeing what Microsoft adds in more substantial updates in the future.

About

Since 1994, Scott Lowe has been providing technology solutions to a variety of organizations. After spending 10 years in multiple CIO roles, Scott is now an independent consultant, blogger, author, owner of The 1610 Group, and a Senior IT Executive w...

0 comments

Editor's Picks