On Tuesday 03 April 2007 12:46, Kern Sibbald wrote: > On Monday 02 April 2007 22:28, Arno Lehmann wrote: > > Hi, > > > > On 4/2/2007 6:37 PM, Kern Sibbald wrote: > > > On Monday 02 April 2007 18:00, Xeos Laenor wrote: > > >> I've noticed a no strange behavior when i start a new job. > > >> Bacula verify if there is a Full backup in catalog when the job is add > to > > >> the queue but not when the job really start. > > >> It could be a problem if i have already an identical (full) backup in > > >> progress. In this case, when i add the new job in the queue, it doesn't > > >> detect the actually full backup and do another full backup for this job > (ok > > >> two equals jobs in queue, it's not often :p). I would prefer have a > > >> differential backup for the second job. > > >> > > >> So, maybe, you could move the test at the moment where the job really > > >> starts, no? > > > > > > This is a Feature Request item. See the web site for info about doing > Feature > > > Requests. > > > > Hm... wasn't this discussed some time ago? > > Yes, but I don't recall if we have a project or not. We have so many projects > that maybe I forgot ... > > > > > In any case, I agree with Franck - it would be good to move the upgrade > > to a later time, if that's possible. I just had to work around that > > problem myself :-) > > Almost everything is possible -- it just takes programmers. > > > > > > Looking through the projects, I don't find this one. > > OK, that confirms my feeling on this. > > > Looking through the list mail is too much work now :-) > > It isn't necessary. If it isn't in the projects list, it needs a new email > and some discussion on the list. > > > > > (Although technically this might be a feature request because the > > current behaviour is what has been working for a long while, and there > > is no documentation indicatng things should be different, the current > > behaviour is really very close to a bug, IMO.) > > > > Arno
Hello. I just ran into the same problem. One client does its 20 GB backup over internet and it takes a few days. Today I noticed Bacula had just completed the 2nd full backup and is now waiting for appendable volumes to do the 3rd one. On the 9th of april, 21:47 the 1st full backup was completed, the 2nd job's log: ===== 07-Apr 23:05 backup-dir: No prior Full backup Job record found. 07-Apr 23:05 backup-dir: No prior or suitable Full backup found in catalog. Doing FULL backup. 09-Apr 21:47 backup-dir: Start Backup JobId 5770, Job=serv1-userdata.2007-04-07_23.05.16 09-Apr 21:47 backup-dir: Recycled volume "serv1-userdata-full-0002" ... ===== I just cancelled the 3rd job, set "rerun failed levels = no" for that job and hope that tonight the incremental job is done. It seems a bug to me also - job should have decided its level on 9th of april upon starting, not on the 7th upon queuing (when there was the 1st full backup still running). Arno, how did you work around such a situation? Silver ------------------------------------------------------------------------- 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 [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/bacula-users
