Bacula Enterprise has this feature where a job can be restarted. There is no
work around other than breaking up the jobs into smaller chunks.
Patti Clark
Linux System Administrator
R&D Systems Support Oak Ridge National Laboratory
From: Duane Webber <duane.web...@comcast.net<mailto:duane.web...@comcast.net>>
Date: Thursday, February 25, 2016 at 11:58 AM
To:
"bacula-users@lists.sourceforge.net<mailto:bacula-users@lists.sourceforge.net>"
<bacula-users@lists.sourceforge.net<mailto:bacula-users@lists.sourceforge.net>>
Subject: [Bacula-users] Write Retry on Network Error without Restarting the Job
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
------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
