On Thursday 14 December 2006 16:51, Alan Brown wrote:
> On Wed, 13 Dec 2006, Alan Brown wrote:
>
> >
> > Can anyone else confirm this?
> >
> > ====
> >
> > Rerun Failed Levels = yes
> >
> > If an incremental job is scheduled to start before a full or differential
> > job has completed (ie, still running): When the incremental job starts the
> > previous (still running) job is detected as "failed" and the incremental
> > is upgraded to full or differential.
> >
> > ====
> >
> > It seems repeatable here but I'd like confirmation from someone else
> > before filing it as a genuine bug.
> >
>
> There's definitely something strange here:
>
> [query.sql entry]
>
> :List all backups for a particular Job
> *Enter JobName:
> SELECT DISTINCT Job.JobId,Job.Name,Job.Level AS L,Job.JobStatus as S,
> StartTime,JobBytes/1024/1024/1024 as Gb FROM Client,Job,JobMedia,Media
> WHERE Client.ClientId=Job.ClientId
> AND JobMedia.JobId=Job.JobId AND JobMedia.MediaId=Media.MediaId
> AND Job.Name='%1'
> ORDER BY Job.Name,Job.StartTime
>
> [snip]
>
> | 19,029 | Low-churn-peace10 | I | T | 2006-12-01 01:05:00 | 19.906394 |
> | 19,282 | Low-churn-peace10 | F | f | 2006-12-06 01:18:45 | 0.000000 |
> | 19,536 | Low-churn-peace10 | F | T | 2006-12-11 15:01:48 | 321.869721 |
>
> There are no instances of Low-churn-peace10 running, yet when I kicked off
> another job, it decided to upgrade to Full:
>
> 14-Dec 15:41 msslay-dir: Prior failed job found. Upgrading to Full.
> 14-Dec 15:41 msslay-dir: Start Backup JobId 19693,
Job=Low-churn-peace10.2006-12-14_15.41.48
>
> There _have_ been a couple of incremental jobs cancelled because their
> maximum wait time had exceeded, but surely a missed incremental shouldn't
> cause an upgrade of the next one?
>
> Kern, any ideas?
1. Probably you modified the Fileset.
2. You could try running the following SQL where you fill in the missing
pieces:
SELECT Level FROM Job WHERE JobStatus!='T' AND Type='%c' AND
Level IN ('F','D') AND Name='%1' AND ClientId=%2
AND FileSetId=%3 AND StartTime>'%4'
ORDER BY StartTime DESC LIMIT 1;
%1 = Jobname of current Job
%2 = ClientId of current Job
%3 = FileSetId of current Job
%4 = The time the last valid backup started
Note, any current job running will be considered a failed job.
>
>
> -------------------------------------------------------------------------
> 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
>
-------------------------------------------------------------------------
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
