Backup Copy for AHV Failures Keep Running Every 30 Minutes - Even After Failure

[wa15]

This appears to be a bug, curious if anyone else is having this issue:

I Veeam Backup Copy for AHV configured to run every day at 12am. If the job fails due to insufficient disk space, the job keeps on restarting itself and fails, resulting in a notification email being sent every 30 minutes. I do not see this same behavior with vSphere Backup Copy jobs.

Anyone else experiencing this? Should I open a ticket with support?

[HannesK]

Hello,

Should I open a ticket with support?

yes, that's what is written in red letters when you created this topic

Please provide a case number and check with support. Otherwise the topic will be removed by moderators eventually.

Best regards,
Hannes

[wa15]

Sorry! Case #04486542 created and uploaded logs.

[KnB567]

Any update on this issue.
Have just started getting this behaviour, but is not space related.
Seems the target .vbm file shows multiple instances of the backup that do not currently exist and insisted all but one be renamed.
Have to disable job to prevent repeats.
Ray

[HannesK]

Hello,
in the case, I can only see that it was resolved. No details given.

I recommend that you also open a case and please post the case number for reference.

Best regards,
Hannes

[dpeach01]

I think that is by design. My copy jobs fail daily - again by design, because I use reverse incremental jobs. I just filter out failure emails now. There is no workaround available. If a job fails irrecoverably, I will get spammed every minute until I log in and disable the copy job. And I have to hurry before my entire team screams at me for spamming them. Really weak alerting options here.

[HannesK]

uhm, where do you use reverse incremental? AHV backup only supports forward incremental (not reverse incremental)