Description of Update Rollup 6 for System Center 2012 – Virtual Machine Manager Server

For those who haven’t been able to upgrade System Center 2012 to SP1 Microsoft still provides support. Update Rollup 6 is available and it is only for Virtual Machine Manager and fixes only one issue:

  • When VMWare vSphere 4.1 is updated, the Virtual Machine Manager Service may stop.

If you are experiencing this issue you can find more information and download link here.

QFE Rollup Package 6 for System Center Data Protection Manager 2010 is released

Microsoft released a new hotfix for SCDPM 2010. This hotfix resolves several issues:

  • DPM backup fails for a Microsoft SharePoint farm together with a mirrored content database if the mirrored server name starts with the same name as the principal server name. For example, this issue occurs if the principal server name is "MachineName," the mirrored server name is "MachineName1," and the content database is on a nondefault instance of Microsoft SQL Server. 
    Additionally, you 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)

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

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

  • Tapes are not reusable until the day after the day of expiry. This is true because DPM waits until midnight to run the reclamation job that marks tapes as reusable. If a user wants a tape to be reusable on the same day on which it expires, the user should follow these steps: 
    1. Create the following registry key:

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

    2. Create the ExpireDatasetOnDayStart 32-bit DWORD value, and then set its value data to 1.
  • DPM does not enable browsing of protected folders on a protected server that has an invalid created date and time.
  • A tape backup of millions of files fails, and you receive the following error message: 

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

  • Tape colocation that has a high expiry tolerance mixes retention ranges. This causes tapes to expire earlier than expected.
    Full information and instructions for implementing about this hotfix can be found here.
    The update itself can be downloaded from here.