On Tuesday 2015-07-28 07:44:21 jalil1408 wrote:
> Got it!
> 
> The incremental backup is based on the full backup executed with:
> 
> - The same Job name. (in my case I have different jobs: Job1 and Job2)
> - The same Client name.
> - The same FileSet (any change to the definition of the FileSet such as
> adding or deleting a file in the Include or Exclude sections
> constitutes a different FileSet.
> 
> Why isn't it based only on the same Client and the same Fileset only?

In short, job helps you to keep track of the combination of different
options that define a job, including a Client and FileSet.

Among other options, Client and FileSet are parameters that define a job.
When you want to perform a backup you run some job. When you want to
restore something from the backup you are first looking for an appropriate
job (everything else might be of a secondary importance).
You might look at a job as an essential collection of options needed to
manage a backup and keep backed up data in a consistent state.

Also, since you can't have multiple jobs with the same name and different
Client or FileSet, it might look like it would suffice to say that
incremental backup is based on the full backup executed with the same
job name.
However, during the time it is possible that Client or FileSet for the job
get changed which would naturally lead to the inconsistent data with full
and incremental backups performed on different clients or file sets.

-- 
Josip Deanovic

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