Heitor Faria wrote
>> On 2016-01-04 at 10:46:46 Heitor Faria wrote:
>> 
>>> > On 2016-01-04 at 09:01:44 Heitor Faria wrote:
>>> > 
>>> >> > Em 4 de jan de 2016, pelo 08:10, pietersnld <
>>> >> > 

> pietersnld@.sourceforge

>  > 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 ===="
>> 
>> OK, so Bacula does not use ISO rules. See:
>> http://www.epochconverter.com/date-and-time/weeknumbers-by-year.php
> 
> Hello again Erik, please read this manual paragraph:
> 
> "Note, the Week of Year specification wnn follows the ISO standard
> definition of the week of the year, where Week 1 is the week in which the
> first Thursday of the year occurs, or alternatively, the week which
> contains the 4th of January. Weeks are numbered w01 to w53. w00 for Bacula
> is the week that precedes the first ISO week (i.e. has the first few days
> of the year if any occur before Thursday). w00 is not defined by the ISO
> specification. A week starts with Monday and ends with Sunday."
> [http://www.bacula.org/5.2.x-manuals/en/main/main/Configuring_Director.html#SECTION001460000000000000000]
> 
> I would say that Bacula complies to the ISO standard expect for the leap
> week thing:
> 
> "An ISO week-numbering year (also called ISO year informally) has 52 or 53
> full weeks. That is 364 or 371 days instead of the usual 365 or 366 days.
> The extra week is referred to here as a leap week, although ISO 8601 does
> not use this term. Weeks start with Monday. The first week of a year is
> the week that contains the first Thursday of the year (and, hence, always
> contains 4 January). ISO week year numbering therefore slightly deviates
> from the Gregorian for some days close to 1 January."
> [https://en.wikipedia.org/wiki/ISO_week_date]

Found the same in the source code (7.2)

/*
 * Given a Unix date return the week of the year.
 * The returned value can be 0-53.  Officially
 * the weeks are numbered from 1 to 53 where week1
 * is the week in which the first Thursday of the
 * year occurs (alternatively, the week which contains
 * the 4th of January).  We return 0, if the week of the
 * year does not fall in the current year.
 */
int tm_woy(time_t stime)
{

Think i have to accept an extra differential backup in "week 0". Thanks for
pointing me to the manual just didn't read the whole part :-(
(Next time I will check twice if bacula has some exceptions to the
standards)

Pieter




--
View this message in context: 
http://bacula.10910.n7.nabble.com/No-Full-backup-in-first-weekend-of-january-tp11342p82947.html
Sent from the Bacula - Users mailing list archive at Nabble.com.

------------------------------------------------------------------------------
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to