Sebastian, Thank you for that clarification. Having parameters in the documentation that aren't really used is quite frustrating.
Here's an example of the documentation that I would find useful to have in a single place. Some of the terms I'm using may not be appropriate, but I expect you'll get the idea. # Creating a Virtual Full backup This backup type creates a new Full backup by walking the backup chain (Full, Differential, Incremental) for a Job that contains all changes since the previous Full backup. This is useful for creating long term backups such as off-site backups without needing to go back to the backup client to create the backup. It can be used with both a standard backup scheme and the always incremental backup scheme. The source is determined by the jobs in the backup chain used to create a full backup. This can span multiple volumes and media types depending on how the backup chain (Full, Differential, Incremental) is setup. There is no specific configuration parameter to specify the source. The destination is specified by the Next Pool parameter. This parameter is first checked in the run line, then the Job Resource (or JobDefs Resource) and finally the Pool Resource. The "Pool" parameter for the job is used to find the "Next Pool" parameter, otherwise it is not used. Link to any existing documentation about Virtual Full backups # Creating a standard backup scheme This backup type uses Full, Differential and Incremental backups. A Full backup contains all data from the host at the specified time. The Differential contains all changes since the previous Full backup. The Incremental contains all changes since the previous Incremental or Differential or Full backup, whichever is most recent. The source is the backup client. The destination is the determined by the Pool parameter. This parameter is first checked in the run line, then the Job Resource (or JobDefs Resource). Link to any existing documentation about standard backups # Creating an Always Incremental backup scheme See the existing documentation for Always Incremental backups # Creating a Copy backup ... documentation about why this would be used and what the source and destination are # Creating a Migration backup ... documentation about why this would be used and what the source and destination are On Thursday, January 23, 2025 at 7:22:06 AM UTC-6 Sebastian Sura wrote: > If i recall correctly, both `Pool->NextPool` as well as `Job->NextPool` > are being used as the destination. Normally what you write in the `run` > command has the highest priority, then comes your Job configuration and > then the place where it is normally configured. > > So if you write `run ... NextPool=xyz` then the job will use `xyz` as > the next pool; otherwise it will use `Job->NextPool` if that is defined > and lastly it will use `Pool->NextPool`. > > `Job->VirtualFullBackupPool` is currently not used, but the idea is that > it will take precedence over your next pool configuration if set. > > Am 23.01.25 um 14:05 schrieb Jon Schewe: > > > > - What pool is used for the destination of the Virtual Full backup? > > - Pool -> Next Pool? > > - Job -> Next Pool? > > - Job -> Virtual Full Backup Pool? > > Regarding your other question: Iirc a virtual full backup will first > build a backup chain for the used job, and then simply read from all > volumes that are used in that backup chain. It still has a pool defined > but this is mostly used for the `Pool->NextPool` configuration, etc. > > -- > Sebastian Sura [email protected] > Bareos GmbH & Co. KG Phone: +49 221 630693-0 > https://www.bareos.com > Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646 > Komplementär: Bareos Verwaltungs-GmbH > Geschäftsführer: Stephan Dühr, Jörg Steffens, Philipp Storz > > -- 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 [email protected]. To view this discussion visit https://groups.google.com/d/msgid/bareos-users/c66ef8b6-3e7c-45bb-90ae-a5536b4ee16an%40googlegroups.com.
