Or look for Running Concurrent Jobs http://www.bacula.org/5.2.x-manuals/es/problems/problems/Tips_Suggestions.html <http://www.bacula.org/5.2.x-manuals/es/problems/problems/Tips_Suggestions.html>
—Guy > On 29 Oct 2018, at 11:43, Uwe Schuerkamp <uwe.schuerk...@nionex.net> wrote: > > On Mon, Oct 29, 2018 at 11:31:33AM +0000, Philip Pemberton wrote: >> Hi, >> >> I'm using Bacula to back up a 6TB ZFS array onto LTO, with a fortnightly >> full backup and daily incrementals. >> >> The problem I have is that the full backup sometimes takes more than 24h to >> run. This means that Bacula starts the next backup while the Full is still >> running, creating two full backups, wasting time and filling the tapes. >> >> Is there some way I can avoid this? Either skipping an incremental (because >> the full backup is running) or delaying the incremental would be fine. >> >> I'm also going to be splitting the backup into multiple jobs - is there >> anything I need to do to the database when I modify the configuration? >> >> Thanks >> Phil > > > Hi Phil, > > take a look at the "cancel duplicate jobs" directive. > > All the best, > > Uwe > > > _______________________________________________ > Bacula-users mailing list > Bacula-users@lists.sourceforge.net <mailto:Bacula-users@lists.sourceforge.net> > https://lists.sourceforge.net/lists/listinfo/bacula-users > <https://lists.sourceforge.net/lists/listinfo/bacula-users>
signature.asc
Description: Message signed with OpenPGP
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
