Update Rollup 2 for System Center 2012

Update Rollup 2 for System Center 2012 was released today. This rollup has fixes for App Controller, SCOM, SCORH, SCSM, SCVMM, and DPM. SCORH, SCSM, SCVMM, and DPM. This rollup is packed with updates for DPM. Here is the list:

Data Protection Manager (KB2706783)

Issue 1
After you upgrade from System Center Data Protection Manager 2010, Microsoft SharePoint backups fail if the SharePoint database has a nondefault collation.
Issue 2
A backup of encrypted files fails silently when the self-signed certificate Group Policy Object is disabled.
Issue 3
In the About Microsoft Data Protection Manager dialog box, the Version label is displayed. However, the version number is not displayed.
Issue 4
On the Action menu, the Help command is displayed two times. This issue occurs because you can now access Help for DPM by using the DPM Help command. The Help item on the Action menu refers to Microsoft Management Console (MMC) help.
Issue 5
In the DPM console view menu, the Expand All and Collapse All menu commands are displayed multiple times.
Issue 6
The Windows PowerShell cmdlet to query licenses that are being used is added.
Issue 7
A DPM backup may fail for a SharePoint farm with a mirrored content database whose mirrored server name starts with the principal server name. For example, this issue may occur when the principal server name is "MachineName," the mirrored server name is "MachineName1," and the content database resides on a nondefault instance of Microsoft SQL Server.
This issue may occur when a consolidated backup failure warning is raised for all the mirrored databases that satisfy the previous conditions.
When this failure occurs, you may receive the following error message:

Prepare for backup operation for SQL Server database CONTENT_DB_NAME (mirrored between – SQL PRINCIPAL and SQL MIRROR ) on SQL-PRINCIPAL.FQDN has been stopped because this operation depended on another backup operation which failed or was cancelled. (ID 30200)

Issue 8
Expiry dates for valid datasets that are already written to tape are changed when the retention range is changed during a protection group modification.
For example, a protection group is configured for long-term tape recovery points with custom long-term recovery goals. Recovery Goal 1 has a smaller retention range than other recovery goals. In this configuration, if a protection group is changed to remove Recovery Goal 1 and to keep other recovery goals, the datasets that were created by using Recovery Goal 1 have their retention range changed to the retention range of the other recovery goals.
To work around this problem, create the IsDatasetExpiryDateChangeInModifyPgAllowed DWORD under the following subkey, and then set its value to 0:

HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft Data Protection Manager\Configuration\MediaManager

Issue 9
Tapes are marked as reusable on the next day after the date of expiry as DPM runs a reclamation job only at midnight. If you want the tape to be reusable on the same date as it is expired, create the ExpireDatasetOnDayStart 32- bit DWORD, and set its value to 1 under the following registry key:

HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft Data Protection Manager\Configuration\MediaManager

Issue 10
DPM does not enable browsing of a protected folder on a protected server that has an invalid created date and time.
Issue 11
A tape backup of millions of files fails, and you receive the following error message:

ID 998
Details: The parameter is incorrect (0x80070057).

The rollup can be downloaded here: http://support.microsoft.com/kb/2706783

Print Friendly, PDF & Email

Leave a Reply