Hi Jon

For example in your AI you should have a full/consolidate pool with is the 
target of where incremental are stored.
You extend that pool with next pool -> pointing to your tapes archives pool 
(that one need to have its storage definition)

Here is how I use it @home to export once a month my ai_jobs

ai consoliated pool

Pool {
  Name = "ai_consolidated"
  Description = "AI consolidated"
  ActionOnPurge = Truncate
  MaximumVolumes = 48
  MaximumVolumeJobs = 8
  VolumeRetention = 3 months
  VolumeUseDuration = 23 hours
 * NextPool = "vf_archives"*
  Storage = "ai_storage"
  RecyclePool = "scratch-ai"
  ScratchPool = "scratch-ai"
  FileRetention = 3 months
  JobRetention = 3 months
}

*show pool=vf_archives
Pool {
  Name = "vf_archives"
  Description = "VF Archives Virtual Fulls"
  LabelFormat = "vf_archives-"
  MaximumVolumes = 16
  MaximumVolumeBytes = 1 t 776 g
  VolumeRetention = 3 months 2 weeks 1 days
  VolumeUseDuration = 1 days
  *Storage = "vf_archives"*
  FileRetention = 4 months
  JobRetention = 4 months
}

One of my VF job looks like 
*show job=vf_month
Job {
  Name = "vf_month"
  Type = Backup
  Level = VirtualFull
  Messages = "standard"
  Pool = "ai_consolidated"
  VirtualFullBackupPool = "vf_archives"
  Client = "client-fd"
  FileSet = "fileset"
  Schedule = "vf_archives_month"
  JobDefs = "default_jobdef"
  Priority = 12
  RunScript {
    Console = "update jobid=%i jobtype=A"
    RunsWhen = "after"
  }
  Accurate = Yes
  AllowDuplicateJobs = No
  CancelLowerLevelDuplicates = Yes
  CancelQueuedDuplicates = Yes
}

Which is scheduled by a normal schedule first sunday at 3am.

Hope this will help you to glue the last bytes of your configuration.

On Wednesday, 22 January 2025 at 21:05:10 UTC+1 Jon Schewe wrote:

> Well, I made changes to my configuration before last weekend to use "job 
> -> Virtual Full Backup Pool" to specify the destination for virtual full 
> backups and got errors that the pool resource didn't have "next pool" set, 
> so the backups failed. What's the correct configuration for setting up an 
> archive job from a set of onsite jobs?
>
> My onsite jobs consist of 3 patterns:
> 1. Always Incremental to file
> 2. Standard Full, Differential, Incremental to file
> 3. Standard Full, Differential, Incremental to tape
>
> For each of these I'd like to do a Virtual Full backup every 2 weeks to a 
> pool of tapes that will go offsite. I know how to automatically mark the 
> offsite jobs as archive jobs using RunScript so that they aren't considered 
> for standard restores or as sources of the Virtual Full backups. The 
> question is what are the right parameters to use for these jobs? I had 
> thought that the Virtual Full backup would not need a source pool directive 
> because they just find all Backup jobs for the specified job and 
> consolidate them into a full backup. Given that I would have expected to 
> only need to specify Virtual Full Backup Pool. However as I pointed out 
> above, this isn't working. 
>
> On Friday, January 17, 2025 at 2:57:37 PM UTC-6 Jon Schewe wrote:
>
>> I've been using bareos for quite some time, mostly with the standard 
>> Full, Differential, Incremental backup scheme. The parameters used for this 
>> scheme seem to be fairly clear. 
>>
>> Recently I have had a need to use the Always Incremental scheme and 
>> Virtual Full backups for offsite storage. It seems that the parameters used 
>> for these are sometimes the same as the standard scheme and sometimes 
>> aren't. It also appears that new parameters have been added in the past few 
>> years to help with these new schemes, however it hasn't been very clear to 
>> me which parameters matter. Is there a good guide somewhere of what 
>> parameters are used for each scheme?
>>
>> I found the documentation of the Always Incremental scheme helpful. That 
>> seems pretty good. I find the most trouble with Virtual Full backups for 
>> offsites.
>>
>> My questions are:
>> - What pool is used for the source of a Virtual Full backup? Or is that a 
>> pointless question because bareos doesn't source from a pool for such a 
>> backup, but rather considers all backup jobs for the particular client that 
>> aren't archive jobs and uses whatever pool those volumes are in.
>>
>> - What pool is used for the destination of the Virtual Full backup?
>>   - Pool -> Next Pool?
>>   - Job -> Next Pool?
>>   - Job -> Virtual Full Backup Pool? This one appears to have been added 
>> since I first looked at Virtual Full backups about 5 years ago and is 
>> perhaps the correct one to use.
>>
>> I have not used Copy or Migration jobs, although feel like I would have 
>> similar questions for those jobs as I do for Virtual Full backups.
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to bareos-users+unsubscr...@googlegroups.com.
To view this discussion visit 
https://groups.google.com/d/msgid/bareos-users/85ddab95-4a74-4421-af94-58971990f2c7n%40googlegroups.com.

Reply via email to