On Saturday 03 March 2007 11:44, Christian Nolte wrote:
> Hello!
>
> I use the following schedule:
>
> Schedule {
> Name = "WeeklyCycle"
> Run = Level=Full Pool=Full 1st sun at 23:05
> Run = Level=Differential Pool=Full 2nd-5th sat at 23:05
> Run = Level=Incremental Pool=Incremental sun-fri at 23:05
> }
>
> Let's say today is Wednesday and the first full backup will be scheduled
> at Sunday. Now on Wednesday when the incremental backup starts bacula
> finds no full backup and it will run a full backup instead of the
> scheduled incremental backup. The problem here is that bacula then
> writes the full backup to the 'Incremental' pool.
>
> Is it somehow possible to tell bacula to store the full backup which is
> run because no previous full backup has been made into the 'Full' pool
> and not the 'Incremental'?
This is probably a "bug" because if Bacula upgrades a job from Incremental to
Full, it *probably* re-calculate what pool it should go into. However, I
would say that it is probably not worth fixing since this situation in
principle should only arise the first time that you run a job, and it seems
to me one can probably do it manually the first time, or simply setup the
schedule correctly.
If someone find this to be a really onerous bug, perhaps he/she will send in a
patch.
>
> Best regards!
> Christian
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
