Is there an option to have Bacula retry write operations without restarting the job? A search shows the last time this question was asked was in 2010 (the answer was no) and I'm hoping there is a
change since then. I have remote backups that can take days, if not a week plus and it is not uncommon to run into a network error where Bacula aborts the backup job altogether.
If Bacula does not have this capability, is there a workaround for the same such that the end result is that the remote backups are visible to Bacula directly.
I appreciate any suggestions.
Thanks,
Duane