DPM 2019: Error 40002 – The VHD containing the replica or one of its snapshots could not be mounted or unmounted
This error was fixed for DPM 2016 in Update Rollup 7. Please fix this for DPM 2019 now, and not make us wait for Update Rollup 1 (Q3 '19 on the roadmap). Neither host nor client has anything to do with VHD's and this error still occurs daily.
How about that UR1? As many others have stated we are dealing with this daily as well.
We are facing these issues as well. Can we get some update about the hotfix that can help in sorting out this issue?
We are in Q4 and still no fix for this bug
Stephen Cooper commented
DPM 2019 is little short of catastrophic. The VHD/WMI issue, the services recycling, awful performance. Modern Storage isn't all its made out to be, that's for sure.
I don't understand Microsoft's bug fix release policy. We have several bugs (including this one) that we are encountering with Microsoft server products that make them unusable (because they cause data loss), but they seem to want to wait for a cumulative update cycle to push them out. In the past, there were releases to solve this issues between service packs. This is a much better approach for these critical problems. They don't understand the seriousness of these type problems and the impact on users and their ability to accomplish their tasks.
Marco Veiga commented
Hi, i was living this nightmare(DPM 2019: Error 40002) when i install the update KB3186568 and KB4103720 on the DPM Server with windows server 2016 v.1607, after that he start to make the recovery successfull. I really don't know who was the guilty for my smile, but i hope this post can make you smile too.
Kent Spencer commented
We have had this issue with 3 of our DPM servers, it is a pain to have to reboot our DPM servers during day time hours just to fix this issue, especially since that kills any/all current jobs then we have to re-do them all over again.
Lots of time spent to fix this.
Jose Cruz commented
Microsoft please this issue asap. I spend time every day re-creating my backups. This is not acceptable.
This just started happening to us. Found there is no fix while trying to find a fix! Please fix!
100% agree. This is now affecting three of our DPM servers. I also tried the memory fixes suggested in the DPM forum's announcement but that didn't do anything.
As everyone else says, the only way to fix it is to restart the server, which is a pain.
BTW, when you're fixing this bug, please fix the misspelling of "its". There's no apostrophe in its as in this context it's not a contraction of "it is" or "it has".
It's absolutely a pain to deal with this issue, the only way to recover from the error is to reboot the DPM server, so yes, the hotfix should be released intermediate.
David Goh commented
Q3 '19 is a bit too long. Please expedite.
With this 40002 error fix released for DPM 2016 UR7, surely MS cannot release a patch for DPM2019 instead of waiting until Q3 for Update Rollup 1?
We need the fix now!