Re: [Bacula-users] No Full backup in first weekend of january

[Dan Langille]

> On Jan 5, 2016, at 9:23 AM, Erik P. Olsen  wrote:
> 
> On 2016-01-05 at 15:01:11 Kern Sibbald wrote:
> 
>> There is always the possibility of a bug in Bacula, but no one has
>> reported one.  It "sounds" like you are saying that something is a
>> bug, but I am not sure.
>> 
>> I based the Bacula algorithm on the ISO definition as it existed in
>> 2000, and I never remember seeing anything about a year being more
>> than 365 days.  This is why I came with week 0. If I missed that or
>> the ISO definition has changed, that might be worthwhile reporting.
>> However, always take what some web site says is an ISO implementation
>> with a grain of salt.  It takes a good amount of time to ensure that
>> an algorithm is correct.
>> 
>> Best regards,
>> Kern
> 
> Please read https://en.wikipedia.org/wiki/ISO_8601

Keep in mind that wikipedia is a reference, not the ISO itself.

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

Re: [Bacula-users] No Full backup in first weekend of january

[Josh Fisher]

On 1/5/2016 9:01 AM, Kern Sibbald wrote:
There is always the possibility of a bug in Bacula, but no one has 
reported one.  It "sounds" like you are saying that something is a 
bug, but I am not sure.


I based the Bacula algorithm on the ISO definition as it existed in 
2000, and I never remember seeing anything about a year being more 
than 365 days.  This is why I came with week 0. If I missed that or 
the ISO definition has changed, that might be worthwhile reporting.  
However, always take what some web site says is an ISO implementation 
with a grain of salt.  It takes a good amount of time to ensure that 
an algorithm is correct.


The current (and third) version of ISO 8601 was published in 2004.

I think the confusion is that ISO 8601 does not mention a week 0, rather 
what tm_woy() is naming week 0 would be named week 52 or week 53 of the 
preceding year. In other words, in those years where the first few days 
of January would fall in week w52 or w53 of the preceding year, tm_woy() 
is returning 0. The problem is that scheduling a job for the first 
Thursday of week w01 will always work as expected, whereas the first 
Wednesday of w01 will sometimes not. This is neither a bug nor a 
misinterpretation of ISO 8601. It is simply not a good way to specify 
the first Wednesday of the year. Rather than "the Wednesday in the first 
week of the year", one would instead specify the "the first Wednesday in 
January".





Best regards,
Kern

On 01/05/2016 01:30 PM, pietersnld wrote:


Peter Keller wrote

On 01/04/2016 09:00 AM, pietersnld wrote:

> 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)

Curiously, how does that "alternatively" clause work on Jan 2026?
Is Jan 1 - 3 indeed week 0?

 January 2026
Su Mo Tu We Th Fr Sa
  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 31


Later,
-pete

No, ISO weeks start on monday so i reformated your calendar of 
january 2026.

 January 2026
Mo Tu We Th Fr Sa Su
   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 31
First thursday in January is week 1. So january 1st is in week 1. 
Week1 is December 29th 2025 - January 4th 2026 But it gets even 
stranger. When using bacula's routine the following occurs:

Time : Thu Dec 25 14:13:24 2025
Week : 52

Time : Fri Dec 26 14:13:24 2025
Week : 52

Time : Sat Dec 27 14:13:24 2025
Week : 52

Time : Sun Dec 28 14:13:24 2025
Week : 52

Time : Mon Dec 29 14:13:24 2025
Week : 53

Time : Tue Dec 30 14:13:24 2025
Week : 53

Time : Wed Dec 31 14:13:24 2025
Week : 53

Time : Thu Jan  1 14:13:24 2026
Week : 1

Time : Fri Jan  2 14:13:24 2026
Week : 1

Time : Sat Jan  3 14:13:24 2026
Week : 1

Time : Sun Jan  4 14:13:24 2026
Week : 1

Time : Mon Jan  5 14:13:24 2026
Week : 2

Time : Tue Jan  6 14:13:24 2026
Week : 2

Something to keep in mind! If the last part of the year is actually 
in the new year bacula will calcutate it as week 53!


Pieter


View this message in context: Re: No Full backup in first weekend of 
january 

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




--


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


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

Re: [Bacula-users] No Full backup in first weekend of january

[Kern Sibbald]

  
  
There is always the possibility of a
  bug in Bacula, but no one has reported one.  It "sounds" like you
  are saying that something is a bug, but I am not sure. 
  
  I based the Bacula algorithm on the ISO definition as it existed
  in 2000, and I never remember seeing anything about a year being
  more than 365 days.  This is why I came with week 0. If I missed
  that or the ISO definition has changed, that might be worthwhile
  reporting.  However, always take what some web site says is an ISO
  implementation with a grain of salt.  It takes a good amount of
  time to ensure that an algorithm is correct.
  
  Best regards,
  Kern
  
  On 01/05/2016 01:30 PM, pietersnld wrote:


  

  Peter
Keller wrote
  

On 01/04/2016 09:00 AM, pietersnld wrote:

> 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)

Curiously, how does that "alternatively" clause work on Jan
2026?
Is Jan 1 - 3 indeed week 0?

January 2026
Su Mo Tu We Th Fr Sa
 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 31


Later,
-pete
  

  
  No, ISO weeks start on monday so i reformated your calendar of
  january 2026.
  January 2026
Mo Tu We Th Fr Sa Su
  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 31

  First thursday in January is week 1. So january 1st is in week 1.
  Week1 is December 29th 2025 - January 4th 2026
  But it gets even stranger. When using bacula's routine the
  following occurs:
  Time : Thu Dec 25 14:13:24 2025
Week : 52

Time : Fri Dec 26 14:13:24 2025
Week : 52

Time : Sat Dec 27 14:13:24 2025
Week : 52

Time : Sun Dec 28 14:13:24 2025
Week : 52

Time : Mon Dec 29 14:13:24 2025
Week : 53

Time : Tue Dec 30 14:13:24 2025
Week : 53

Time : Wed Dec 31 14:13:24 2025
Week : 53

Time : Thu Jan  1 14:13:24 2026
Week : 1

Time : Fri Jan  2 14:13:24 2026
Week : 1

Time : Sat Jan  3 14:13:24 2026
Week : 1

Time : Sun Jan  4 14:13:24 2026
Week : 1

Time : Mon Jan  5 14:13:24 2026
Week : 2

Time : Tue Jan  6 14:13:24 2026
Week : 2

  
  Something to keep in mind! If the last part of the year is
  actually in the new year bacula will calcutate it as week 53!
  
  Pieter
  
  
  View this message in context: Re:
No Full backup in first weekend of january
  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



  


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

Re: [Bacula-users] No Full backup in first weekend of january

[Kern Sibbald]

It seems to me that there is no Sunday in week 53 of 2015.

Best regards,
Kern

On 01/04/2016 10:03 AM, pietersnld wrote:
> pietersnld wrote
>> In the schedule resource the manual says:
>> 
>>  = 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
>>
>> Fahrer, Julian napsal(a):
>>> I ve seen the same thing at a customers site using 3.0.3
>>>
>>> Mit freundlichem Gruß
>>>
>>> Julian Fahrer
>>>
>>>
>>> - Originalnachricht -
>>> Von: Pieter (NL) pieters...@users.sourceforge.net
>>> An: bacula-users@lists.sourceforge.net
>>> bacula-users@lists.sourceforge.net
>>> Gesendet: Sat Jan 09 20:17:12 2010
>>> Betreff: [Bacula-users]  No Full backup in first weekend of january
>>>
>>>
>>> Hi,
>>>
>>> I noticed something stange. In the first week of january no Full backup
>>> was
>>> made on my server(s). I have the following schedule:
>>>
>>> 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
>>> }
>>>
>>> I know this weekend was in week 53 is this a missing week in bacula?
>>>
>>> Greetings,
>>> Pieter
>>>
>>>
>>>
>>> 
>>>
>>> --
>>> This SF.Net email is sponsored by the Verizon Developer Community
>>> Take advantage of Verizon's best-in-class app development support
>>> A streamlined, 14 day to market process makes app distribution fast and
>>> easy
>>> Join now and get one step closer to millions of Verizon customers
>>> http://p.sf.net/sfu/verizon-dev2dev 
>>>
>>>
>>> 
>>>
>>> ___
>>> Bacula-users mailing list
>>> Bacula-users@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/bacula-users
>>
>> --
>> This SF.Net email is sponsored by the Verizon Developer Community
>> Take advantage of Verizon's best-in-class app development support
>> A streamlined, 14 day to market process makes app distribution fast and
>> easy
>> Join now and get one step closer to millions of Verizon customers
>> http://p.sf.net/sfu/verizon-dev2dev 
>> ___
>> Bacula-users mailing list
>> Bacula-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/bacula-users
>
>
>
>
> --
> View this message in context: 
> http://bacula.10910.n7.nabble.com/No-Full-backup-in-first-weekend-of-january-tp11342p82938.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


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

Re: [Bacula-users] No Full backup in first weekend of january

[Erik P. Olsen]

On 2016-01-05 at 15:01:11 Kern Sibbald wrote:

> There is always the possibility of a bug in Bacula, but no one has
> reported one.  It "sounds" like you are saying that something is a
> bug, but I am not sure.
> 
> I based the Bacula algorithm on the ISO definition as it existed in
> 2000, and I never remember seeing anything about a year being more
> than 365 days.  This is why I came with week 0. If I missed that or
> the ISO definition has changed, that might be worthwhile reporting.
> However, always take what some web site says is an ISO implementation
> with a grain of salt.  It takes a good amount of time to ensure that
> an algorithm is correct.
> 
> Best regards,
> Kern

Please read https://en.wikipedia.org/wiki/ISO_8601

-- 
Erik

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

Re: [Bacula-users] No Full backup in first weekend of january

[Erik P. Olsen]

On 2016-01-05 at 12:12:26 Dan Langille wrote:

> > On Jan 5, 2016, at 9:23 AM, Erik P. Olsen  wrote:
> > 
> > On 2016-01-05 at 15:01:11 Kern Sibbald wrote:
> >   
> >> There is always the possibility of a bug in Bacula, but no one has
> >> reported one.  It "sounds" like you are saying that something is a
> >> bug, but I am not sure.
> >> 
> >> I based the Bacula algorithm on the ISO definition as it existed in
> >> 2000, and I never remember seeing anything about a year being more
> >> than 365 days.  This is why I came with week 0. If I missed that or
> >> the ISO definition has changed, that might be worthwhile reporting.
> >> However, always take what some web site says is an ISO
> >> implementation with a grain of salt.  It takes a good amount of
> >> time to ensure that an algorithm is correct.
> >> 
> >> Best regards,
> >> Kern  
> > 
> > Please read https://en.wikipedia.org/wiki/ISO_8601  
> 
> Keep in mind that wikipedia is a reference, not the ISO itself.

I do. But if you debate the correctness of this wikipedia reference you
can verify it by buying the full standard from the ISO store:
http://www.iso.org/iso/home/store.htm

-- 
Erik

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

Re: [Bacula-users] No Full backup in first weekend of january

[pietersnld]

Peter Keller wrote
> 
> On 01/04/2016 09:00 AM, pietersnld wrote:
> 
>> 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)
> 
> Curiously, how does that "alternatively" clause work on Jan 2026?
> Is Jan 1 - 3 indeed week 0?
> 

> January 2026Su Mo Tu We Th Fr Sa 1  2  3 4  5  6  7  8  9
> 1011 12 13 14 15 16 1718 19 20 21 22 23 2425 26 27 28 29 30 31

> 
> Later,
> -pete

No, ISO weeks start on monday so i reformated your calendar of january 2026.
January 2026Mo Tu We Th Fr Sa Su  1  2  3  4 5  6  7  8  9 10
1112 13 14 15 16 17 1819 20 21 22 23 24 2526 27 28 29 30 31
First thursday in January is week 1. So january 1st is in week 1. Week1 is
December 29th 2025 - January 4th 2026But it gets even stranger. When using
bacula's routine the following occurs: 
Time : Thu Dec 25 14:13:24 2025Week : 52Time : Fri Dec 26 14:13:24 2025Week
: 52Time : Sat Dec 27 14:13:24 2025Week : 52Time : Sun Dec 28 14:13:24
2025Week : 52Time : Mon Dec 29 14:13:24 2025Week : 53Time : Tue Dec 30
14:13:24 2025Week : 53Time : Wed Dec 31 14:13:24 2025Week : 53Time : Thu Jan 
1 14:13:24 2026Week : 1Time : Fri Jan  2 14:13:24 2026Week : 1Time : Sat Jan 
3 14:13:24 2026Week : 1Time : Sun Jan  4 14:13:24 2026Week : 1Time : Mon Jan 
5 14:13:24 2026Week : 2Time : Tue Jan  6 14:13:24 2026Week : 2

Something to keep in mind! If the last part of the year is actually in the
new year bacula will calcutate it as week 53!

Pieter




--
View this message in context: 
http://bacula.10910.n7.nabble.com/No-Full-backup-in-first-weekend-of-january-tp11342p82955.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

Re: [Bacula-users] No Full backup in first weekend of january

[Heitor Faria]

> Em 4 de jan de 2016, pelo 08:10, pietersnld < 
> pieters...@users.sourceforge.net >
> escrito:

>> pietersnld wrote

>>> In the schedule resource the manual says:
>>> 
>>> = 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. 

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

Re: [Bacula-users] No Full backup in first weekend of january

[pietersnld]

pietersnld wrote
> In the schedule resource the manual says:
> 
>  = 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
> 
> Fahrer, Julian napsal(a):
>> I ve seen the same thing at a customers site using 3.0.3
>> 
>> Mit freundlichem Gruß
>> 
>> Julian Fahrer
>> 
>> 
>> - Originalnachricht -
>> Von: Pieter (NL) pieters...@users.sourceforge.net
>> An: bacula-users@lists.sourceforge.net
>> bacula-users@lists.sourceforge.net
>> Gesendet: Sat Jan 09 20:17:12 2010
>> Betreff: [Bacula-users]  No Full backup in first weekend of january
>> 
>> 
>> Hi,
>> 
>> I noticed something stange. In the first week of january no Full backup
>> was
>> made on my server(s). I have the following schedule:
>> 
>> 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
>> }
>> 
>> I know this weekend was in week 53 is this a missing week in bacula?
>> 
>> Greetings,
>> Pieter
>> 
>> 
>> 
>> 
>> 
>> --
>> This SF.Net email is sponsored by the Verizon Developer Community
>> Take advantage of Verizon's best-in-class app development support
>> A streamlined, 14 day to market process makes app distribution fast and
>> easy
>> Join now and get one step closer to millions of Verizon customers
>> http://p.sf.net/sfu/verizon-dev2dev 
>> 
>> 
>> 
>> 
>> ___
>> Bacula-users mailing list
>> Bacula-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/bacula-users
> 
> 
> --
> This SF.Net email is sponsored by the Verizon Developer Community
> Take advantage of Verizon's best-in-class app development support
> A streamlined, 14 day to market process makes app distribution fast and
> easy
> Join now and get one step closer to millions of Verizon customers
> http://p.sf.net/sfu/verizon-dev2dev 
> ___
> Bacula-users mailing list
> Bacula-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bacula-users





--
View this message in context: 
http://bacula.10910.n7.nabble.com/No-Full-backup-in-first-weekend-of-january-tp11342p82938.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

Re: [Bacula-users] No Full backup in first weekend of january

[Erik P. Olsen]

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:
> >>> 
> >>> = 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.

-- 
Erik


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

Re: [Bacula-users] No Full backup in first weekend of january

[Heitor Faria]

> 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 <
>> >> > pieters...@users.sourceforge.net > escrito:
>> >> 
>> >> >> pietersnld wrote
>> >> 
>> >> >>> In the schedule resource the manual says:
>> >> >>> 
>> >> >>> = 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
>> =
>> IncrementalBackup11  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#SECTION00146]

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]

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 
===

--

Re: [Bacula-users] No Full backup in first weekend of january

[Erik P. Olsen]

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 <
> >> > pieters...@users.sourceforge.net > escrito:
> >> 
> >> >> pietersnld wrote
> >> 
> >> >>> In the schedule resource the manual says:
> >> >>> 
> >> >>> = 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
> =
> IncrementalBackup11  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

-- 
Erik

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

Re: [Bacula-users] No Full backup in first weekend of january

[Heitor Faria]

> 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:
>> >>> 
>> >>> = 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
=
IncrementalBackup11  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

Re: [Bacula-users] No Full backup in first weekend of january

[pietersnld]

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:
>>> >> >>> 
> 
>>> >> >>> = 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
>>> =
>>> IncrementalBackup11  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#SECTION00146]
> 
> 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 

Re: [Bacula-users] No Full backup in first weekend of january

[Peter Keller]

On 01/04/2016 09:00 AM, pietersnld wrote:

> 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)

Curiously, how does that "alternatively" clause work on Jan 2026?
Is Jan 1 - 3 indeed week 0?

January 2026
Su Mo Tu We Th Fr Sa
 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 31

Later,
-pete

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

Re: [Bacula-users] No Full backup in first weekend of january

[Marek Simon]

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

Fahrer, Julian napsal(a):
 I ve seen the same thing at a customers site using 3.0.3
 
 Mit freundlichem Gruß
 
 Julian Fahrer
 
 
 - Originalnachricht -
 Von: Pieter (NL) pieters...@users.sourceforge.net
 An: bacula-users@lists.sourceforge.net bacula-users@lists.sourceforge.net
 Gesendet: Sat Jan 09 20:17:12 2010
 Betreff: [Bacula-users]  No Full backup in first weekend of january
 
 
 Hi,
 
 I noticed something stange. In the first week of january no Full backup was
 made on my server(s). I have the following schedule:
 
 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
 }
 
 I know this weekend was in week 53 is this a missing week in bacula?
 
 Greetings,
 Pieter
 
 
 
 
 
 --
 This SF.Net email is sponsored by the Verizon Developer Community
 Take advantage of Verizon's best-in-class app development support
 A streamlined, 14 day to market process makes app distribution fast and easy
 Join now and get one step closer to millions of Verizon customers
 http://p.sf.net/sfu/verizon-dev2dev 
 
 
 
 
 ___
 Bacula-users mailing list
 Bacula-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/bacula-users


--
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] No Full backup in first weekend of january

[Fahrer, Julian]

Yes, but shouldn't backups ran in week 53???

-Ursprüngliche Nachricht-
Von: Marek Simon [mailto:marek.si...@trustica.cz] 
Gesendet: Montag, 11. Januar 2010 14:35
Cc: bacula-users@lists.sourceforge.net
Betreff: Re: [Bacula-users] No Full backup in first weekend of january

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

Fahrer, Julian napsal(a):
 I ve seen the same thing at a customers site using 3.0.3
 
 Mit freundlichem Gruß
 
 Julian Fahrer
 
 
 - Originalnachricht -
 Von: Pieter (NL) pieters...@users.sourceforge.net
 An: bacula-users@lists.sourceforge.net bacula-users@lists.sourceforge.net
 Gesendet: Sat Jan 09 20:17:12 2010
 Betreff: [Bacula-users]  No Full backup in first weekend of january
 
 
 Hi,
 
 I noticed something stange. In the first week of january no Full backup was
 made on my server(s). I have the following schedule:
 
 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
 }
 
 I know this weekend was in week 53 is this a missing week in bacula?
 
 Greetings,
 Pieter
 
 
 
 
 
 --
 This SF.Net email is sponsored by the Verizon Developer Community
 Take advantage of Verizon's best-in-class app development support
 A streamlined, 14 day to market process makes app distribution fast and easy
 Join now and get one step closer to millions of Verizon customers
 http://p.sf.net/sfu/verizon-dev2dev 
 
 
 
 
 ___
 Bacula-users mailing list
 Bacula-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/bacula-users


--
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
--
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] No Full backup in first weekend of january

[Pieter (NL)]

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



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
 
 Fahrer, Julian napsal(a):
 I ve seen the same thing at a customers site using 3.0.3
 
 Mit freundlichem Gruß
 
 Julian Fahrer
 
 
 - Originalnachricht -
 Von: Pieter (NL) pieters...@users.sourceforge.net
 An: bacula-users@lists.sourceforge.net
 bacula-users@lists.sourceforge.net
 Gesendet: Sat Jan 09 20:17:12 2010
 Betreff: [Bacula-users]  No Full backup in first weekend of january
 
 
 Hi,
 
 I noticed something stange. In the first week of january no Full backup
 was
 made on my server(s). I have the following schedule:
 
 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
 }
 
 I know this weekend was in week 53 is this a missing week in bacula?
 
 Greetings,
 Pieter
 
 
 
 
 
 --
 This SF.Net email is sponsored by the Verizon Developer Community
 Take advantage of Verizon's best-in-class app development support
 A streamlined, 14 day to market process makes app distribution fast and
 easy
 Join now and get one step closer to millions of Verizon customers
 http://p.sf.net/sfu/verizon-dev2dev 
 
 
 
 
 ___
 Bacula-users mailing list
 Bacula-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/bacula-users
 
 
 --
 This SF.Net email is sponsored by the Verizon Developer Community
 Take advantage of Verizon's best-in-class app development support
 A streamlined, 14 day to market process makes app distribution fast and
 easy
 Join now and get one step closer to millions of Verizon customers
 http://p.sf.net/sfu/verizon-dev2dev 
 ___
 Bacula-users mailing list
 Bacula-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/bacula-users
 
 

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


--
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] No Full backup in first weekend of january

[Fahrer, Julian]

I ve seen the same thing at a customers site using 3.0.3

Mit freundlichem Gruß

Julian Fahrer


- Originalnachricht -
Von: Pieter (NL) pieters...@users.sourceforge.net
An: bacula-users@lists.sourceforge.net bacula-users@lists.sourceforge.net
Gesendet: Sat Jan 09 20:17:12 2010
Betreff: [Bacula-users]  No Full backup in first weekend of january


Hi,

I noticed something stange. In the first week of january no Full backup was
made on my server(s). I have the following schedule:

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
}

I know this weekend was in week 53 is this a missing week in bacula?

Greetings,
Pieter

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


--
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
--
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev ___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

[Bacula-users] No Full backup in first weekend of january

[Pieter (NL)]

Hi,

I noticed something stange. In the first week of january no Full backup was
made on my server(s). I have the following schedule:

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
}

I know this weekend was in week 53 is this a missing week in bacula?

Greetings,
Pieter

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


--
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users