why is SureBackup so moody?

[mcz]

Dear PM's,

some guys from support told me a while ago that SureBackup is the feature which has plenty of tickets and also plenty of reasons why it could fail. Now when I take a look at "my statistics", my jobs failed by 30 % the last month - which is way too much. Now of course, some reasons are fine, like 'backup is locked' or things like that, but for instance today I had:

Error: Results: unable to perform Domain Controller restore from a crash-consistent backup. Be sure application-aware processing is enabled in the backup job settings

on the first vm (maybe even before it started). The thing is, whenever there's a good reason why the job would fail and you fix it, everything is allright. But when the last job failed (even on the first vm) and you start it (from the same restore point) again and it succeeds, that's not understandable to me and I had this many times before. Also, the errormessages sometimes do not correlate with the "real reasons" - like in this case the message about the aap - if I take a look at the backup-job, it is and was always enabled. Of course, I could create a ticket and let the support guys take a look but I wannted to know if this topic is known and if there are some fixes in the pipeline for future releases.

Thanks!

[Gostev]

In general, this kind of inconsistency is typically caused by limited backup storage performance, which results in instantly recovered SureBackup VMs I/O timing out affecting applications inside VMs. It's not something we can fix in software. You should probably look at upgrading your backup storage to something faster, if you want reliable and predictable SureBackup.

[dasfliege]

We do have similar problems with a sure backup job which includes domain controller. We also receive the error "unable to perform Domain Controller restore from a crash-consistent backup" even tough AAP is enabled ans is working perfectly fine, as i am able to perform Active-Directory application item restores on these VM without any problems. Also sure backup is taking forever to execute the ping tests even tough the VM is running fine and i am able to login and ping it manually without any issue. Our storage should not be the problem, as it is pretty fast (48x SAS). Also i wonder why such errors as described above should have anything to do with storage performance. The error clearly suggests that there is something wrong with veeam recognizing the backups correctly.

i will open a ticket and check what is wrong in our particular case.