El miércoles, 3 de diciembre de 2014 11:56:35 UTC+1, IP escribió: > W dniu 2014-12-03 o 11:06, Daniel Carrasco Marín pisze: > > El lunes, 1 de diciembre de 2014 20:12:38 UTC+1, Ireneusz Piasecki > > escribió: > >> W dniu 01.12.2014 o 16:15, Daniel Carrasco Marín pisze: > >>> El lunes, 1 de diciembre de 2014 07:33:25 UTC+1, IP escribió: > >>>> Hi. > >>>> > >>>> I have schedules: 1 day of every month bareos doing a full backup, then > >>>> every day from mon to sat bareos doing Incremental backup - all at 6:00 > >>>> at morning. Sun is for differentail jobs. > >>>> > >>>> And today, 01.12.2014 bareos doing full backup and after this job did > >>>> Incremental backup. Exactly like in teh schedule. Is there any settings > >>>> to instruct bareos to not to duplicate job ? Incremental job should run > >>>> in this case in the next day. > >>>> > >>>> I.Piasecki > >>> Hi,first, sorry for my english. > >>> > >>> Just now i'm configuring a bareos backup system and i've found two > >>> options that maybe is what you want: > >>> > >>> https://www.bareos.org/files/misc/bacula.org.bandwidth.2013-11-26.pdf > >>> > >>> In page 14 (at end) and followings, you will see some info about what you > >>> want. Must add in Job definition something like: > >>> Allow Duplicate Jobs = no > >>> Cancel Lower Level Duplicates = yes > >>> Cancel Queued Duplicates = yes > >>> > >>> I've not tested yet, but should work. > >>> > >>> Greetings!! > >> Hi. > >> > >> Thx for Your reply. I think, that this option are true, when my first > >> job were ran to long, and the same job sholud start, but first job is > >> still running. In my case on the same hour the same job is starting, one > >> is Full, and second is Incremental - casue my schedule type. I slight > >> modified schedules like in bareos tutorials, so this sytuation never > >> happens. Very clever indeed. > >> > >> Best regards, > >> I.Piasecki > > I'm glad I helped. > > > > I had no tested that situation, but just yesterday i had similar situation > > (Incremental backup with full running), and all worked perfect ;) > > > > 02-dic 00:01 backup-director JobId 29: Fatal error: JobId 20 already > > running. Duplicate job not allowed. > > 02-dic 00:01 backup-director JobId 29: Bareos backup-director 13.2.3 > > (11Mar14): > > Build OS: x86_64-pc-linux-gnu debian Debian GNU/Linux 7.0 > > (wheezy) > > JobId: 29 > > Job: ovh_srv1m3_mails.2014-12-02_00.01.01_49 > > Backup Level: Full (upgraded from Incremental) > > Client: "ovh_srv1m3" 5.2.6 (21Feb12) > > x86_64-pc-linux-gnu,debian,7.0 > > FileSet: "ovh_srv1m3_mails.fs" 2014-12-01 13:17:42 > > Pool: "ovh_srv1m3_mails.po" (From Job resource) > > Catalog: "ovh_servers.ca" (From Client resource) > > Storage: "roma_file_auto.st" (From Pool resource) > > Scheduled time: 02-dic-2014 00:01:01 > > Start time: 02-dic-2014 00:01:01 > > End time: 02-dic-2014 00:01:01 > > Elapsed time: 0 secs > > Priority: 10 > > FD Files Written: 0 > > SD Files Written: 0 > > FD Bytes Written: 0 (0 B) > > SD Bytes Written: 0 (0 B) > > Rate: 0.0 KB/s > > Software Compression: None > > VSS: no > > Encryption: no > > Accurate: no > > Volume name(s): > > Volume Session Id: 0 > > Volume Session Time: 0 > > Last Volume Bytes: 0 (0 B) > > Non-fatal FD errors: 1 > > SD Errors: 0 > > FD termination status: > > SD termination status: > > Termination: Backup Canceled > But these jobs ran at the same time date, hour, minute, seconds ? If > yes, this can be a solution. > > Thx. > > I.Piasecki
Not really the same time, because i've started full backup manully after configure the backup, but don't allow to duplicate the same job and that's what you want ¿right?. Date/time don't care, if job is the same then the second job will be canceled. Greetings! -- You received this message because you are subscribed to the Google Groups "bareos-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. For more options, visit https://groups.google.com/d/optout.
