On Thu, 14 Dec 2006, Kern Sibbald wrote:

>> Kern, any ideas?
>
> 1. Probably you modified the Fileset.

All the jobs have "ignore fileset changes = yes"

> 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

%c ?

>   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

Presumably I got part of this wrong because I got no results.

> Note, any current job running will be considered a failed job.

That isn't a good idea:
   A 1Tb full backup may take several days to run, in LTO2 spool/despool
   time alone. Incrementals tend to run daily...

AB


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

Reply via email to