Your previous post was removed because it reported a technical issue with the product without including support case ID, as requested when you click New Topic
. There are multiple reasons why this requirement is in place, and it is really easy to open a support case. Please, be sure to submit full logs to our support, and include support case ID in this topic if you'd like to pursue this issue further.
nbarsotti wrote:I believe this is a bug in the vss writer deployed by veeam, something that was never fully tested by veeam before they released support.
One thing for sure, Veeam does NOT deploy VSS writers, or any other VSS components for that matter, to guest. You are probably confusing us with other backup solutions which do deploy VSS providers. In fact, first thing you should do with VSS issues is make sure you do not have those 3rd party VSS modules installed on the system, as they are known to cause such issues to VSS framework.
With Veeam, what is pushed to guest in runtime is small coordination process that requests Microsoft VSS framework to prepare system for hot backup with generic VSS API call. VSS framework then performs applications and OS freeze, and if something does not work, reports any errors encountered back to us. The error that you see is the system error from VSS framework.
Out of curiosity, why would you use EFI in a VM. This is certainly the first time I encounter this. Does it provide certain benefits?