I encountered an error when trying to recover a Hyper-V virtual machine from DPM 2012 R2. The recovery job would recover the complete amount of data for that virtual machine, but then the recovery job would fail right after. The error says “The VSS application writer or the VSS provider is in a bad state. Either it was already in a bad state or it entered a bad state during the current operation. (ID 30111)”.
I tried recovering to different drives within the same Hyper-V host and even to a different Hyper-V host, but it gave the same error. It turns out, the issue was because of the file path it was recovering to, was too deep. DPM also adds date and time stamps as part of the recovery folder. The file path shouldn’t exceed 260 characters according to Microsoft.
“In the Windows API (with some exceptions discussed in the following paragraphs), the maximum length for a path is MAX_PATH, which is defined as 260 characters.” – see link below.
In order to fix this issue, I had to restore the individual disks and recreate the virtual machine by attaching the individually recovered disks and reconfiguring the virtual machine settings (Ex. Network settings).