This article describes the issues in Microsoft System Center Data Protection Manager (DPM) 2010 that are fixed in the DPM 2010 hotfix rollup package version 3.0.7707.0 that has a publish date of March, 2011.
Note To determine the currently-installed version, click the Information icon that is located on the upper-right side of the Main menu bar in the DPM 2010 Administrator Console on the DPM Server.
This hotfix rollup resolves the following issues:
Note To determine the currently-installed version, click the Information icon that is located on the upper-right side of the Main menu bar in the DPM 2010 Administrator Console on the DPM Server.
This hotfix rollup resolves the following issues:
- 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 datasource 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.