[Bacula-users] full and diff backups to differnt storages

2011-02-03 Thread Ronny Seffner
Hi list, I've a machine containig 2 different devices which I'ld like to use for backup. An RDX drive for full backups and an LTO drive for the differntials. So I defined: Jobs : full_Job and diff_Job FileSets : only one for both jobs togehter called data_FileSet Schedules : data_full_Schedule

Re: [Bacula-users] full and diff backups to differnt storages

2011-02-03 Thread Christian Manal
Am 03.02.2011 12:04, schrieb Ronny Seffner: Hi list, I've a machine containig 2 different devices which I'ld like to use for backup. An RDX drive for full backups and an LTO drive for the differntials. So I defined: Jobs : full_Job and diff_Job FileSets : only one for both jobs togehter

Re: [Bacula-users] full and diff backups to differnt storages

2011-02-03 Thread Ronny Seffner
To add some more; I saw parameters like Full Backup Pool and Differntial Backup Pool for Job definition and also Run = Full ... or Run = Differential ... for scheduling. But how to difference the Storage-Device and RunBefore/AfterJob parameters in such an

Re: [Bacula-users] full and diff backups to differnt storages

2011-02-03 Thread Dan Langille
On 2/3/2011 6:56 AM, Ronny Seffner wrote: To add some more; I saw parameters like Full Backup Pool and Differntial Backup Pool for Job definition and also Run = Full ... or Run = Differential ... for scheduling. Yes: Full Backup Pool = FullFile Differential Backup Pool =

Re: [Bacula-users] full and diff backups to differnt storages

2011-02-03 Thread Ronny Seffner
Just use the (Full|Differential|Incremental) Backup Pool options in a *single* job definition to tell Bacula to put each level into a different pool, then set the storage to use in the pool definitions. I found the same thing the same time. I've postet new matching quesitions the samt time you

Re: [Bacula-users] full and diff backups to differnt storages

2011-02-03 Thread Dan Langille
On 2/3/2011 6:56 AM, Ronny Seffner wrote: To add some more; I saw parameters like Full Backup Pool and Differntial Backup Pool for Job definition and also Run = Full ... or Run = Differential ... for scheduling. But how to difference the Storage-Device and RunBefore/AfterJob parameters in

Re: [Bacula-users] full and diff backups to differnt storages

2011-02-03 Thread Dan Langille
On 2/3/2011 7:09 AM, Ronny Seffner wrote: Just use the (Full|Differential|Incremental) Backup Pool options in a *single* job definition to tell Bacula to put each level into a different pool, then set the storage to use in the pool definitions. I found the same thing the same time. I've

Re: [Bacula-users] full and diff backups to differnt storages

2011-02-03 Thread Ronny Seffner
Yes, please read the documentation on scripts. :) I'll do so. Please provide an link because I can't find anything at bacula.org or /usr/share/doc describing variables like %c or %l (I guess %c = client name, %l = backup level). Mit freundlichen Grüßen / With kind regards      Ronny Seffner --

Re: [Bacula-users] full and diff backups to differnt storages

2011-02-03 Thread Phil Stracchino
On 02/03/11 06:56, Ronny Seffner wrote: To add some more; I saw parameters like Full Backup Pool and Differntial Backup Pool for Job definition and also Run = Full ... or Run = Differential ... for scheduling. Don't use Pool overrides in the Schedule. They are deprecated because they cannot

Re: [Bacula-users] full and diff backups to differnt storages

2011-02-03 Thread Dan Langille
On Thu, February 3, 2011 7:40 am, Ronny Seffner wrote: Yes, please read the documentation on scripts. :) I'll do so. Please provide an link because I can't find anything at bacula.org or /usr/share/doc describing variables like %c or %l (I guess %c = client name, %l = backup level). Rather

Re: [Bacula-users] full and diff backups to differnt storages

2011-02-03 Thread Martin Simmons
On Thu, 03 Feb 2011 07:52:10 -0500, Phil Stracchino said: Don't use Pool overrides in the Schedule. They are deprecated because they cannot be made to work properly in all cases. That's true, but I hope the functionality is never removed. It is still needed to make Full backups use