Please reach our support team regarding Update 2 and the mentioned error. Most likely this issue is not related to your target, so investigation is required. Thanks.
I've setup Veeam for the first time to test and got exactly the same error while trying to backup Windows 10 machine.
Marc, have you made any progress in getting it resolved?
I did some troubleshooting together with the VEEAM Support and at the end I was told that this is a VSS error not caused by Veeam. The recommendation was to open a ticket with Microsoft. As this was only a test machine I did not do that. I also do not have any other machine on which I tried it. Sorry for not being a help....
Hey Jay,
In this specific case of above, Marc closed the case with us and should open a case with Microsoft but he posted here that he wasn't going to do this.
You can create a support call with Microsoft but mostly, in this case, best you can do is to check the states of your VSS writers first. One or more could be in a bad state causing the backups to fail.
Actually that's what i thought, but after removing the CBT Driver i had no issues with this backups...so i'm running them now. Complicated server setup in that they are XEN Hypervisor hosted vm's...complicated as in who uses XEN!
Thats correct, interestingly when i installed the driver the vms took a over 30 minutes to reboot (directly after install) when normally its a minute max.
CBT Driver should not affect the process of VSS snapshot creation. I'd still recommend to get in touch with our support team as debug log analysis is required.
Just my two penneth, VSS writers can fail for many reasons I found sometimes that a lack of resources after installation of the agent prevents it working.
If you check using admin cmd with "vssadmin list writers" this will show which vss provider has failed and usually a reboot is the only way to resolve these failures.