Workaround: On the Secondary DPM Server, while Creating or Modifying a Protection Group, on the Group Members” Screen, select the Primary DPM Server and click “Select After this Consistency Check jobs will succeed. “Refresh”. Search for Files/Folders during Recovery Description: If you protect a file, folder, or volume using DPM 2016, and search for it in the recovery pane under and Folders”, you may not get the relevant results. “Files Workaround: Browse through the Recovery Points to find the file, folder, or volume. Protecting Hyper-V VMs with an ISO in DVD Drive Description: If you protect a VM with an ISO in DVD drive, backups may fail with the following messages: Initial Replica: DPM failed to communicate with [DPMServerName] because of a communication error with the protection agent. (ID 53 Details: Not implemented (0x80000001)) Subsequent Backups: An unexpected error occurred while the job was running. (ID 104 Details: Internal error code: 0x80990E54) Workaround: Eject the ISO and trigger backup again. Deleting Storage Volumes with backups Description: If the backups of a data-source are stored on a volume, and the volume is deleted, the PG goes into an state. Workaround: Stop Protection of the affected data-sources with Delete Data option and protect the data-source again. Concurrent Incremental and Tape Backups Description: If you create a Policy that triggers Synchronization jobs and tape backup jobs at the same time on the same data source, Tape backup may fail sometimes. Workaround: Retry the tape backup. To avoid this scenario, create the policy in such a way that incremental and tape backups don’t clash. BMR Protection Failures Description: If you try to protect BMR, it may fail with the message that the replica size is not sufficiently Workaround: Use PowerShell to increase the replica size: $dpm = Connect-DPMServer -DpmServerName <name of DPM>
Workaround: On the Secondary DPM Server, while Creating or Modifying a Protection Group, on the “Select Group Members” Screen, select the Primary DPM Server and click “Refresh”. After this Consistency Check jobs will succeed. Search for Files/Folders during Recovery Description: If you protect a file, folder, or volume using DPM 2016, and search for it in the recovery pane under “Files and Folders”, you may not get the relevant results. Workaround: Browse through the Recovery Points to find the file, folder, or volume. Protecting Hyper-V VMs with an ISO in DVD Drive Description: If you protect a VM with an ISO in DVD drive, backups may fail with the following messages: Initial Replica: DPM failed to communicate with [DPMServerName] because of a communication error with the protection agent. (ID 53 Details: Not implemented (0x80000001)) Subsequent Backups: An unexpected error occurred while the job was running. (ID 104 Details: Internal error code: 0x80990E54) Workaround: Eject the ISO and trigger backup again. Deleting Storage Volumes with backups Description: If the backups of a data-source are stored on a volume, and the volume is deleted, the PG goes into an state. Workaround: Stop Protection of the affected data-sources with Delete Data option and protect the data-source again. Concurrent Incremental and Tape Backups Description: If you create a Policy that triggers Synchronization jobs and tape backup jobs at the same time on the same data source, Tape backup may fail sometimes. Workaround: Retry the tape backup. To avoid this scenario, create the policy in such a way that incremental and tape backups don’t clash. BMR Protection Failures Description: If you try to protect BMR, it may fail with the message that the replica size is not sufficiently Workaround: Use PowerShell to increase the replica size: $dpm = Connect-DPMServer -DpmServerName <name of DPM>
DPM2016_VHDEVAL.docx