Features implemented in this update rollup
- Automatically repair DPM Filter corruptions without requiring a consistency check for file server backups
- No production server restart is required when you upgrade from DPM 2012 R2 Update Rollup 6 or later versions
- Removing the Offline/Online tag from Hyper-V VM name in the DPM UI
Issues that are fixed in this update rollup
- When you perform a recovery for an external data source from an imported tape, and if you try to run a search on the recovery tab, DPM UI may crash.
- If you try to perform an original location recovery from an inactive cloud protection (such as when you remove cloud protection but retain cloud recovery points), the recovery may fail. An alternative location recovery will work in this case.
- If you are protecting client data sources, alternative location recovery may fail. An original location recovery still works in this situation.
- Item level recovery for SharePoint may fail after you upgrade to DPM 2012 R2 Update Rollup 6, 7, or 8.
- If you are already protecting a stand-alone SQL database by using DPM, and then you try to create a mirror database and protect it with DPM, DPM Self Service Recovery Tool does not display the mirror database. However, the DPM recovery wizard shows the mirror database.
- DPM may display the following redundant messages in the event log if End-User Recovery is enabled for any data source and at the same time you configure BMR:
Failed to update permissions used for end-user recovery on DPM_FQDN. Permissions update failed for the following reason: (ID: 3123)
- The DPM console may crash when you open DPM canned reports.