My guess based on those lines is something within the Hyper-V stack and since it is 2012 that could be part of the problem as well.  You might want to think about upgrading and since Veeam is completing at least you have backups.

I would also suggest testing the backups to ensure the server can be restored as a safety precaution.

Hi @selfhostr -

In looking through the HV Guide, it appears there may be a hardware limitation for HV VMs. So make sure your VM virtual h/w version meets the requirement:
https://helpcenter.veeam.com/docs/backup/hyperv/platform_support.html?ver=120#hyper-v-vms

Other than that...I see everything else you shared should be supported:
https://helpcenter.veeam.com/docs/backup/hyperv/platform_support.html?ver=120

We can’t really help much here regarding Linux errors you’re getting..only Veeam. As Chris shared, one option you could try is upgrade your HV environmnet to current. You could see if anyone on the Veeam Forums has experienced similar errors in a Ub Lnx VM, but they typically want a case ID over there. I don’t have any other suggestions.

Thanks for your responses everyone. I was afraid the bottom line would be that an upgrade is in order. I’m in the process of completely rebuilding the system from the ground up so that may eliminate any issues in the stack.

@coolsport00 It looks like the Hyper-V requirements all seem to be in line for what I have.

As far as a short-term fix, is it possible to completely disable the live backup functionality so that Veeam freezes the VM during the backup? I feel like these live backups may be adding some additional complication that I may want to avoid here.

@selfhostr - I’m not sure what you mean by “live” backups? Veeam uses Integration Services (IS) to quiesce the VM’s OS to keep apps on the VM at a app-consistent state. I don’t use HV, so not sure if IS works with Linux. If it does, then in theory, you shouldn’t be having app crashes. But I don’t have HV and thus not had to troubleshoot the issue you’re experiencing. If you disable the option to use IS in the Backup Job, then the backup is what’s called ‘crash-consistent’. You could try that if you haven’t already. Worth a shot. Otherwise, opening a case with Tech Support would be your best bet….which is allowed even for the CE version.

@coolsport00 I think you’ve got the gist of it! I’ve read a couple of different articles such as this one and this to better understand quiescence. There was a Veeam blog post I read several years ago which guided me towards writing some pre- and post- freeze scripts, and did a pretty good job of explaining the different types of quiescence that Hyper-V/Veeam can do, and I think I ended up going for the middle road, which was that it’s supposed to pause an app or two (MySQL I think it was) during the backup procedure, then resume it. I think the Integration Services are configured as well as can be (all components show in the MS Event Log as connected when the machine boots up, save for one complaining about being out of date which MS says is “fine”.) I can also see different HV components talking in the VM’s log during backup so it looks like there’s communication going on. I’m just starting to feel more and more that something isn’t working as expected and leading to these issues during the backup.

At this point, I’ve disabled the Backup Integration Service in Hyper-V which I assumed meant that the VM would be paused during the backup procedure, although I was still able to work in a remote terminal of the VM during the backup (and see some logs about VSS activating) so it seems what I was expecting didn’t really happen. I’ll try activating the crash-consistent option and see how that goes, thanks!

Edit: I’ve just realized that I didn’t have the crash-consistent option checked in the Hyper-V settings on the backup job, so I’m not quite sure what it was doing this last run. Didn’t seem to pause the VM either way.

The VM will only pause for a few seconds while the snapshot is taken and removed typically.  So that is as expected regardless of the crash-consistent being on/off.

Hi @selfhostr - no...the IS just pauses the I/O to the VM apps, not ‘freeze’ the VM itself. So, it works a bit different than what you thought (if I read your comment properly). So, during backup, you can use it like it wasn’t being backed up...ssh to it, etc. 

Keep us posted on things.

Veeam has just decided to “archive” my ticket due to low support staff availability. I understand de-prioritizing me due to my tier, but closing it just seems odd. Are they not offering free support anymore?

At any rate, I think I know what my mission is. I need to rebuild since the current system layers just aren’t cutting it on multiple levels. I think I’ve managed to configure Veeam such that it avoids using these sketchy Integration Services as much as possible to do what it needs, although I still seem to be having some instability. Probably just the way the VM is configured anyways and not the fault of Veeam.

Thank you all for your patience and help with my issues. I know it’s difficult to troubleshoot things from afar so I appreciate everything everyone has done here.

That is too bad and best of luck rebuilding.  Keep us posted on the outcome.

Ugh...sorry about that @selfhostr . Yeah...with free support tier, it’s best effort; then after a certain time period...if they’re load is too hefty, they close them out...from my undestanding.

Let us know how it all turns out. Would be curious to hear.

Best.

Thanks again for both of your responses!

Veeam has just pointed out to me that it’s problematic I installed B&R on the same host that’s running Hyper-V, saying “it could lead to erratic behavior and system instability”, although it’s not entirely clear to me to what extent this system instability goes. They offer that pre- and post- freeze scripts seem to be a sufficient work around, stating that these scripts could be used to “pause the VM”. I thought the scripts were supposed to run inside the VM so I’m not sure how that will work. I’ll continue to pursue this with the representative, although at this point I’m starting to think that it’s not Veeam causing these issues at all.

Ah, ok...wasn’t aware of that @selfhostr . Well, keep us posted if you get a resolution.

Best.