Re: [Bacula-users] feature request

[Josh Fisher]

Alexander Kolesnik wrote: It would be nice to have keywords: Full Backup Storage Incremental Backup Storage Differential Backup Storage If I understand the request correctly, this feature already exists with Run storage overrides. If I understand this correctly - no :) Imagine, that you set in Job resource to store all your full backups onto Storage1 and all incr. backups onto Storage2. Then, for a client your full backup fails for some reason (all other clients were backed up OK). The next backup level is incremental, but for that failed client it will be upgraded to full. But now - it's time for incremental backups so that full backup will be stored onto Storage2 instead of Storage1. Hope you've got what I meant :) I have noticed that too. Whatever storage device is specified in the Run directive is always used for that run, even when that run's level gets upgraded for whatever reason. In the example below, the first Run directive will always use the  "full_pool" pool and write to the "AITTape" storage device. Under normal circumstances, the second Run directive will use the "inc_pool" pool and write to the "Disk1" storage device. If the second (incremental) Run should be upgraded to level=full for some reason, however, it will then use the "full_pool" pool but will still write to the "Disk1" storage device. Job {   Name = "nas1"   Client = s1-fd   JobDefs = "DefaultJob"   FileSet = "nas1-files"   Schedule = "nas1-schedule"   Storage = "AITtape"   Pool = full_pool   FullPool = full_pool   IncrementalPool = incl_pool   Write Bootstrap = "/var/bacula/nas1.bsr" } Schedule {   Name = "nas1-schedule"   Run = Level=Full  thu at 22:01   Run = Level=Incremental Storage=Disk1 fri-wed at 22:01 } --- Josh Fisher