Feature suggestion: Disable automatic job disablement due to too many failures

[vmcust]

We occasionally have to restart our proxy servers or lose connectivity to sites and the backup jobs running or about to run during when those servers are down fail to connect to the storage. Jobs fail and get automatically disabled due to too many errors. Error details show up like such:

Additional Details: Error: Cannot proceed with the job: existing backup meta file 'Backup_Copy_xxxx.vbm' on repository 'Windows Repository' is not synchronized with the DB. To resolve this, run repository rescan. The job has been automatically disabled due to too many failures. Please fix all...

There should be an option to prevent automatic job disablement due to too many failures. We tend to disable jobs when servers are decommissioned and leave them disabled for some time before we delete the backups and the disable jobs. In this last round of connectivity issues, several jobs were automatically disabled and was caught up in the mix of disabled jobs. These did not get noticed for some time and they were important jobs. If there was an option to prevent jobs from automatically being disabled, we would have these backups. We have only noticed backup copy jobs getting automatically disabled due to too many errors.

Thanks!

[foggy]

We tend to disable jobs when servers are decommissioned and leave them disabled for some time before we delete the backups and the disable jobs.

Could you please clarify the reasoning behind this, so we could think of possible ways to change this approach?

[vmcust]

We have some backup copy jobs for regulatory compliance servers and often see they get automatically disabled from not being able to reach a repository, usually due to network loss connectivity or rebooting the Veeam server with jobs still running or copy jobs that are doing their pre-checks. We also have jobs we have disabled due to server decommissions and when jobs get automatically disabled they become lost in the mix in the console view. Managing all these backup jobs take a considerable amount of time rather than just being something to set it and forget it. We have quarterly audits and backups are audited. We typically do not discover the automatically disabled jobs for days later and this has been affecting our compliance. It has gotten to the point where it is difficult to do any maintenance on the Veeam servers. It would also be nice if there was a maintenance mode to enable that stops all the jobs and restarts them instead of having to do it manually or rely on powershell scripts and wait. We have over 300 jobs.

[powersjo]

Did you get an email notification about the failed backup copy job? I have had the same situation but I also got a failed backup copy job email. I was able to address the repository issue the next day. Manual, but not having the job disable and notify me of something was wrong would make it so it would still be running now.