[Bacula-users] Full/Incremental on Copy Jobs? Why?

Hello once again list.

I'd like to know if the "Level" option on a Copy Job makes any difference at all for the job. Since my Copy Job looks at "JobID" to copy (using an SQL Statement), it won't know that that JobID was Full or Incremental, right?

For example:

Job {
    Name = job.copy.full
    Type = Copy
    Level = Full
    Client = client.ptibacula-dir
    Write Bootstrap = "/var/spool/bacula/jobs/bootstrap.copy.full.%c.%n.bsr"
    FileSet = fs.default
    Messages = msg.default
    Max Start Delay = 48h
    Spool Data = "">    Pool = pool.full
    Schedule = sch.copy.full
    Allow Duplicate Jobs = yes
    Allow Higher Duplicates = no
    Selection Type = SQL Query
    Selection Pattern = "

    SELECT
        MAX(Job.JobId)
    FROM
        Job, Pool
    WHERE
        Job.Level = 'F'
        and Job.Type = 'B'
        and Job.JobStatus = 'T'
        and Pool.Name = 'pool.full'
        and Job.PoolId = Pool.PoolId
    GROUP BY
        Job.Name
    ORDER BY
        MAX(Job.JobId);
    "
}

In this Copy Job I'm selecting all previous Full Backups JobID using the SQL Statement, but I could very well change it to select all the previous Incremental Backups, hence the "Level = Full" makes no difference, right?

Thanks!

------------------------------------------------------------------------------
Doing More with Less: The Next Generation Virtual Desktop 
What are the key obstacles that have prevented many mid-market businesses
from deploying virtual desktops?   How do next-generation virtual desktops
provide companies an easier-to-deploy, easier-to-manage and more affordable
virtual desktop model.http://www.accelacomm.com/jaw/sfnl/114/51426474/

_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users