> On 2016-01-04 at 09:01:44 Heitor Faria wrote: > >> > Em 4 de jan de 2016, pelo 08:10, pietersnld < >> > pieters...@users.sourceforge.net > escrito: >> >> >> pietersnld wrote >> >> >>> In the schedule resource the manual says: >> >>> <week-of-year-keyword> >> >>> = w00 | w01 | ... w52 | w53 >> >> >>> So why didn't my backup run in week 53? >> >>> (Still a lot of time to fix no week 53 until 2016.....) >> >> >>> Pieter >> >> >> Still not fixed after 6 years! (At least not in version 5.2.12 >> >> still need to build a new server to use version 7). >> >> Is the problem still there in version 7? >> >> Did anyone successfully ran a backup in week 53? (With w53 keyword >> >> in the schedule. If no restrictions are made the backup runs ok) >> >> >> Schedule is the same as it was 6 years ago: >> >> >> Schedule { >> >> Name = "WeeklyCycle" >> >> Run = Level=Full w01 w03 w05 w07 w09 w11 w13 w15 w17 w19 w21 w23 >> >> w25 w27 w29 w31 w33 w35 w37 w39 w41 w43 w45 w47 w49 w51 w53 on sun >> >> at 01:05 Run = Level=Differential w02 w04 w06 w08 w10 w12 w14 w16 >> >> w18 w20 w22 w24 w26 w28 w30 w32 w34 w36 w38 w40 w42 w44 w46 w48 >> >> w50 w52 on sun at 01:05 Run = Level=Incremental tue-fri at 01:05 >> >> } >> >> >> Schedule that works ok: >> >> >> Schedule { >> >> Name = "Mob-WeeklyCycle" >> >> Run = Level=Full fri at 19:05 >> >> } >> >> >> Marek Simon-2 wrote >> >> >>> Bacula follows the ISO 8601 specification. The first week of >> >>> years is the first week that has the first Thursday in this year. >> >>> The first weekend was not in the first week of the year. >> >>> More in Bacula Documentation, Section Schedule Resource. >> >>> Marek >> Yes, Marek seemed pretty accurate. >> Your backup will only run at sunday from the 53th week if it exists >> within a year. If not, the next year will consider weeks from the >> start again (w00). By the way: you must be missing the first week >> backup because your forgot to start counting by 0. The first week of >> the year is 0. Have a nice new year. > > Incorrect, first week of the year IS 1. Otherwise Bacula has made its > own rule.
Hello Érik: this is the way Bacula works and the manual is accurate. See the example: "*time Sat 02-Jan-2016 18:00:28 *show schedule Schedule: name=WeeklyCycle Schedule: name=WeeklyCycleAfterBackup --> Run Level=Incremental hour=20 mday=0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 month=0 1 2 3 4 5 6 7 8 9 10 11 wday=6 wom=0 1 2 3 4 5 woy=0 mins=0 *status schedule Scheduled Jobs: Level Type Pri Scheduled Job Name Schedule ===================================================================================== Incremental Backup 11 Sat 02-Jan 20:00 BackupCatalog WeeklyCycleAfterBackup ====" Regards, =========================================================================== Heitor Medrado de Faria - LPIC-III | ITIL-F | Bacula Systems Certified Administrator II Do you need Bacula training? http://bacula.us/video-classes/ +55 61 8268-4220 Site: http://bacula.us FB: heitor.faria =========================================================================== ------------------------------------------------------------------------------ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users