none
Update Rollup 1 for DPM 2019 has been released! RRS feed

  • General discussion

  • The Update Rollup 1 for System Center 2019 Data Protection Manager is now available:
    Update Rollup 1 for System Center 2019 Data Protection Manager

    Introduction

    This article describes the issues that are fixed in Update Rollup 1 for Microsoft System Center 2019 Data Protection Manager. This article also contains the installation instructions for this update.

    Note: Existing Data Protection Manager to Microsoft Azure customers should upgrade to the latest Microsoft Azure Recovery Services (MARS) agent (version 2.0.9171.0 or later). If the latest agent is not installed, online backups might fail, and no Data Protection Manager to Microsoft Azure operation will work.

    Issues that are fixed
    This update fixes the following issues:

    • While running the attach agent wizard when you select a computer on trusted domain and add it, the selected computer does not get listed under Selected Computers.
    • When you select short term backup to tape and change the backup mode to full, the wizard shows incorrect backup schedule option and DPM console may crash on selection.
    • In a scenario you deleted the protection group retaining the recovery point for a VMware VM, which is no more available on the ESX server. If you recreate the new VM with the same name on the same ESX instance and protect again using DPM, the recovery pane creates multiple entries for this VM.
    • The DPM Console becomes unresponsive while loading Recoverable Items for a data source.
    • DPM Service might stop during DPM maintenance jobs.
    • In some scenarios, pruning job failures leading to storage bloat
    • In addition to these, all the issues fixed in SC DPM 2016 Update Rollup 8 are also fixed in SC DPM 2019 UR1.

    Other Improvements and Features

    • SCDPM 2019 UR1 also has additional new features introduced. For details on the new features refer to the documentation here.



    Blog: https://thesystemcenterblog.com LinkedIn:

    Tuesday, February 4, 2020 6:37 PM

All replies