>>>>> On Wed, 07 May 2008 16:43:43 -0700, Doug Breshears said:
> 
> Martin Simmons wrote:
> >>>>>> On Wed, 07 May 2008 09:25:10 -0700, Doug Breshears said:
> >>>>>>             
> >> Hi all,
> >>
> >> I have a Monthly Full backup that backs up to a DISK FILE, Then Migrate 
> >> to Tape. I then do a daily backup which should look at the last Full 
> >> backup. However the daily process is saying it cannot find a valid FULL 
> >> backup to compare to.
> >>
> >> I have included the pertinent sections from the log file to show the 
> >> progress of this one Job resource ("Full Set").
> >> I would appreciate any feedback here letting me know what I am doing wrong.
> >>
> >> --------------------------------------------------------------------------------------
> >> Time Frame:
> >>
> >>     I started the Full Backup Friday Eve (May 02),
> >>     I started Migration Monday Morn (May 05) (after setting volume
> >>     status to FULL),
> >>     Migration went all day and ended Tuesday,
> >>     Enabled regular daily backups Tuesday so it started Wednesday ~1am.
> >>     
> >
> > Looks like it might be a bug.
> >
> > What is the output of the following sql command for those jobs?
> >
> > select jobid, job, name, type, level, jobstatus from job where jobid in 
> > (4301,4300,4292);
> >
> > __Martin
> >   
> Interesting.. I will have to look at the DB more closely.
> Here is the data...
> 
> *sqlquery
> Automatically selected Catalog: MyCatalog
> Using Catalog "MyCatalog"
> Entering SQL query mode.
> Terminate each query with a semicolon.
> Terminate query mode with a blank line.
> Enter SQL query: select jobid, job, name, type, level, jobstatus from 
> job where jobid in (4301, 4300, 4292);
> +-------+-------------------------------------+-----------------+------+-------+-----------+
> | jobid | job                                 | name            | type | 
> level | jobstatus |
> +-------+-------------------------------------+-----------------+------+-------+-----------+
> | 4292  | Ex1.2008-05-02_17.36.37             | Ex1             | M    | F    
>  | T         |
> | 4300  | Migrate-Monthly.2008-05-05_08.18.01 | Migrate-Monthly | g    | F    
>  | T         |
> | 4301  | Ex1.2008-05-05_08.18.02             | Ex1             | B    | F    
>  | T         |
> +-------+-------------------------------------+-----------------+------+-------+-----------+
> Enter SQL query:

Ok, so the correct jobs are still in the catalog.  I think the
differential/incremental backups are suppose to find jobid 4301 after
migration.

The output of

select jobid, ClientId, FileSetId, StartTime from job where jobid in (4301, 
4292);

would be useful to check that the other important fields are correct.

The actual query used by Bacula will be

SELECT StartTime FROM Job WHERE JobStatus='T' AND Type='B'
       AND Level='F' AND Name='Ex1'
       AND ClientId=$TheClientId
       AND FileSetId=$TheFileSetId
       ORDER BY StartTime DESC LIMIT 1;

with $TheClientId and $TheFileSetId replaced by the appropriate numbers.  It
should find jobid 4301 after the migration.  Prior to the migration, it should
find jobid 4292.

__Martin

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users