nmdange wrote:If you enable Hyper-V Native Guest Quiescence, then the Hyper-V integration services will initiate a VSS snapshot in the guest as long as "Backup (Volume Snapshot)" is enabled in the integration services, so it will still be application consistent. If the issue is with VSS in the guest, then it will most likely fail using native quiescence as well, but it's worth trying to see if there is a difference.
Mike Resseler wrote:That will depend. What workloads are those VMs running. The SBS 2008 I'm a bit scared off because it most probably runs exchange and AD and a crash consistent backup might be not the best idea when you need to restore.
BCT-Tech wrote:Are you talking about enabling Hyper-V Native Guest Quiescence, but not crash consistent backup?
nmdange wrote:The setting "Take crash consistent backup instead of suspending VMs" in Veeam is really only applicable to Windows Server 2012 R1 and earlier, which used to suspend VMs that could not do online backups. As long as you have "Backup (Volume Snapshot)" enabled in the properties of the VM in Hyper-V, it will do an in-guess VSS snapshot and if that fails, the backup will fail with a VSS error, it does not fall back to crash-consistent. To do that you have to disable that integration services setting on the VM in Hyper-V.
nmdange wrote:No that behavior is only applicable to Windows Server 2012 R1 and earlier. 2012 R2 and later do not pause VMs during backup. https://blogs.msdn.microsoft.com/virtua ... s-anymore/
Users browsing this forum: Bing [Bot] and 1 guest