Author: jalil1408 <bacula-forum AT backupcentral DOT com>
Date: Tue, 28 Jul 2015 07:22:00 -0700
I have Job1 : Client1 Storage1 Schedule1 (Tue at 21:00) Pool1 (Volume1) Fileset1 Full Job2 : Client1 Storage1 Schedule2 (Wed at 22:00) Pool2 (Volume2) Fileset1 Incremental I run Job1 manually success
Author: jalil1408 <bacula-forum AT backupcentral DOT com>
Date: Tue, 28 Jul 2015 07:44:21 -0700
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
Author: Christoph Litauer <litauer AT uni-koblenz DOT de>
Date: Tue, 28 Jul 2015 16:56:44 +0200
Just define one Schedule with different levels and different pools: Schedule { Name = "Schedule1" Run = Level=Full Pool=Pool1 Tue at 21:00 Run = Level=Incremental Pool=Pool2 Wed at 22:00 } -- Kind re
Author: Josip Deanovic <djosip+news AT linuxpages DOT net>
Date: Tue, 28 Jul 2015 20:23:45 +0200
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 j
Author: Radosaw Korzeniewski <radoslaw AT korzeniewski DOT net>
Date: Wed, 29 Jul 2015 08:41:59 +0200
Hello, 2015-07-28 20:23 GMT+02:00 Josip Deanovic <djosip+news AT linuxpages DOT net>: Also, since you can't have multiple jobs with the same name and different Client or FileSet Which is not perfectl