All about Windows 10 these days. And so lots of our customers heading for upgrading or deploying System Center Configuration Manager 1511. And while deploying and plannung all this….some of them also have other products related to ConfigMgr in use. For example the SCCM Connector in System Center 2012 R2 Service Manager… Issue: If you…
With Update Rollup 5 for System Center 2012 R2 Data Protection Manager there are lots of changes and fixes:
The following features have been added or improved:
- Protect SharePoint with SQL Always on Configuration
- Protect SharePoint Server, Exchange Server, and Windows Client workloads to Microsoft Azure by using Data Protection Manager
- Support for multiple retention ranges for long-term backup on Microsoft Azure
- Ability to transfer initial backup copy offline to Azure
- Support for protecting Microsoft workloads that are hosted in VMware
- Display missed SLA alerts on the Data Protection Manager console
- Enhanced reporting with Data Protection Manager central console
There are 11 fixes in this update rollup…see more information in KB
- The Data Protection Manager UI crashes intermittently when a backup to tape is performed.
- Backup job for dedupe-enabled volume on Windows 2012 R2 fails. For example, Data Protection Manager backup might fail for following setup:
Data Protection Manager2012 R2 is installed on Windows Server 2012.
Data Protection Manager is protecting a dedupe-enabled volume on Windows Server 2012 R2.
- Before you install this update, make a backup of the Data Protection Manager database.
- Install this rollup package on the server that is running System Center 2012 R2 Data Protection Manager. To do this, run Microsoft Update on the server.
- In the Data Protection Manager Administrator Console, update the protection agents. To do this, use one of the following methods.
- Restart protected computers
You have to restart the protected computer after you apply the Data Protection Manager Agent update for Update Rollup 5. Some backup jobs might fail if you don’t restart the protected computer.
Existing Data Protection Manager to Windows Azure customers should upgrade to the latest agent (version 2.0.8703.0 or a later version). If the latest agent is not installed, online backups will fail, and no Data Protection Manager to Windows Azure operation will work correctly.
Dieser Post ist auch verfügbar auf: German