DPM error messages.
Please update error messages so they can be understood in english of what they mean. Error messages are almost always vague and require a lot of troubleshooting. Please just tell us the problem. We don't have time to trouble shoot dpm issues that take several days.
I am agreeing with Jochen Wezel.
Jochen Wezel commented
Currently, DPM doesn't tell error Messages most of the time - it tells the result and nothing more. This is very time consuming to always fish somewhere in the deep deep log/event forest of Windows (hopefully you search on the right Windows machine - it might be either the backup server machine or the remote Server machine), doing Manual tests if Windows backup can create e.g. the system state backup without Problems while DPM might not do it, do further Analysis, Review VSS writers and Providers lists for potential Errors related to our current Problem, Review remote Problems with volume System (ReFS vs. NTFS vs. Cluster volume vs. ...), recreate disk IDs with diskpart and more. Finally, some Hyper-V machines can't be backupped for whatever reason, so we have to work around this issue by installing the Agent in the virtual machine.
All in all, I spent days and weeks for getting our DPM 2012 R2 backing up all Exchange databases, SQL Server databases, volumes, hyper-V online/offline machines - always searching for the secret hint in logs or discussion Forums.
Then you Change a few Servers to use ReFS volume instead of NTFS and wonder why many items don't backup any more. With luck you can detect the Event which lead to your next backup Problems again. Otherwise have fun with searching for the next hint for hours or days :-(
This has to be stopped! Please stop wasting the DPM admin's time ASAP. Provide reasonable error Messages by collecting error Messages from DPM Server and DPM Client System, and collect error Messages and not just error codes. Collect error Messages from all relevant and required Sub Systems.