Not sure if this is the right place to post this one I think I have an issue with the interaction between a 2012.R2 host Hyper-V VSS writer and the VM VSS components on an SBS2008 based VM.
I have a Windows 2012.R2 Hyper-V host running three VMs. VM OS are one SBS2008, one 2008 Server with SQLExpress instances, one 2012.R2. Veeam is our current backup solution and is configured to run application aware backups. The Veeam backup completes without error reports (Veaam uses Hyper-V VSS to request VMs to prepare snapshops). However, in the SBS2008 VM, there are many Event ID1 Source SQLVDI, EventID 24583 Source SQLWRITER and EventIDs 3041 and 18210 sourced from each SQL instances. All the VSS writers involved in the backup are left in State [9] failed with Last error: No error. The 2008 and 2012.R2 OS VMs have no event log errors.
A Windows Server Backup (Full VSS) run within the SBS2008VM completes successfully with no event log errors in the VM
An online Windows Server Backup (Full VSS) from the Hyper-V host of the SBS2008VM completes successfully, but with an even more extensive set of errors as per the Veeam backup.
The hosts are Domain joined, the Hyper-V host is not on the domain. All integration tools are 2012.R2 level. I've spent several days trying to apply various solutions for the SQLVDI errors as suggested in various MS and other sources on the web.
Would appreciate any guidance in what further troubleshooting I can do.
Thanks