SQL cluster Backup

[itpfp]

Hi,

we have two VM's running 2012R2 with SQL 2014 running in a cluster. This is running our Skype for Business backend using SQL always on, using a cluster with a witness disk.

We upgraded the Hyper-V host to 2016 and since this upgrade, Veeam simply refuses to backup both vm's.

Initially we got:

26-3-2017 06:22:17 :: Error: Processing VMs with shared VHDX disks is not supported, please change shared disk format to VHDS

Ok, fair enough, since the hyper-v create shared disk wizard stated the minimum required OS version is Windows 10, I specifically excluded the witness disk from the backup (why would I even want to backup this disk is beyond me to be honest).

Yet Veaam is consistent. same error message..

So I decided to bite the bullet and change the witness disk to VHDS.

Maybe just maybe it would proceed to actually do what the software package has been paid to do, simply backup the data. Wrong, new error message:
26-3-2017 12:47:29 :: Failed to create VM recovery checkpoint (mode: Veeam application-aware processing) Details: Job failed ('Failed to create checkpoint on collection 'Hyper-V Collection' (CA8AE943-4693-4102-AE12-3DC3EBE0317A).

The operation failed.

Guest cluster validation on VM group 'Hyper-V Collection' (CA8AE943-4693-4102-AE12-3DC3EBE0317A) failed for checkpoint creation.

Size of the VM group 'Hyper-V Collection' (CA8AE943-4693-4102-AE12-3DC3EBE0317A) is not same with the size of the guest cluster.'). Error code:

Oh, me as a simple user is now utterly confused, we are talking about a witness disk, just a witness disk, meanwhile the whole purpose of my backup (to saveguard the SQL database on those hosts) is not met.

Ok ok, so I try to disable application aware processing alltogether. At the very least it would make a crash consistent VHDX backup, pretty please ? No you guessed it, no dice:

26-3-2017 13:41:40 :: Failed to create VM recovery checkpoint (mode: Hyper-V child partition snapshot) Details: Job failed ('Failed to create checkpoint on collection 'Hyper-V Collection' (2EA3F17B-0726-49DC-9286-AE91A29814CB).

The operation failed.'). Error code: '32768'.
Failed to create collection recovery checkpoint.


Can someone please tell me how I can backup two vm's that before the upgrade to 2016 backed up each and every day without fail ?

I am certain Veeam claimed their latest 9.5 was fully 2016 compatible. Yet I seem to be utterly unable to backup a critical SQL database, just because whatever reason..

Do I need to simply copy the VHDX's using powershell, or would I actually be able to use the software for the purpose it claims to fulfill ?

[Shestakov]

Please provide a support case number as required by the forum`s rules when asking about technical errors.
Thank you!

[itpfp]

Hi, I just logged a support case:

02110999

[adruet]

According to our experience, backup of a Windows 2016 cluster running on top of a 2016 hyper-V cluster is not yet possible due to Microsoft shipping products with features not yet implemented thoroughly:

microsoft-hyper-v-f25/backing-up-a-wind ... ml#p236554