Backup Server 2016 - Source Server 2012R2

[bcscholl]

I thought I've fixed this before but need a refresher. Backup up Hyper-V VMs [Server 2016] with Veeam 9.5.4.2866. Source server [ Server 2012R2]. Even if the VMs are powered down they get an error:

Failed to create VM recovery checkpoint (mode: Crash consistent) Details: Not supported in Windows Server 2012 R2

Do I need to re-install Server 2012R2 on the Veeam server?

[Dima P.]

Hello bcscholl,

To clarify: you have Veeam B&R installed on top of Hyper-V 2016 and Hyper-V 2012R2 server is added as additional source host? Thanks!

[bcscholl]

Veeam B&R is installed on bare metal Server 2016 (With Hyper-V Installed), source VMs are on another Host (Server 2012R2).

Works as expected Installing Veeam on 2012R2, then uses Microsoft Software Shadow Copy provider 1.0. Backup is successful (Crash Consistent). Guess I don't get to use Fast Clone on 2016 REFS

[bcscholl]

Uninstalled Hyper-V on the Veeam backup server. Now it works, using MS Shadow copy provider.

[Dima P.]

Hello Brian,

Thanks for the updates and glad you found a workaround. I've passed your feedback to QA folks and they will review the described case to make sure everything works correctly. Cheers!

[bcscholl]

Restart was only a temporary fix, eventually the jobs will error out again. When reviewing the source server managed volumes it has a volume listed from itself (Backup server) Which doesn't exist on the source server. I found if we re-scan the Hyper-V Standalone host (source server) this volume disappears and then the jobs will run successfully. The source server was the original backup server, we exported and imported the configuration onto the new backup server, not sure if that is causing the issue somehow.

[bcscholl]

New fix, re-add source server using only machine name, not FQDN. Re-added all VMs to jobs and now working as expected (so far). Veeam support found it was trying to use RDMA as well as it thought it was attached via Failover cluster vs stand alone Hyper-V. Crossing fingers...

[aich365]

As an FYI
We have been working with Veeam support and Microsoft on Hyper-V host 2016 and one VM W2012.
We cannot create Production Checkpoints and it looks like the issue is related to IntegratedServices and Rapid Recovery.
On Servers where RR was uninstalled CPs could be created OK but one Server still has an issue
In Server 2012 integration service updates had to be downloaded and installed manually, they are now delivered through the normal Windows Update process in Server 2016/2019.
We have discovered the 2012 server IntegratedServices are well out of date so are in the process of updating.