On Tue, 7 Jul 2026 at 16:23, Arno Lehmann via Bacula-users <[email protected]> wrote: > If you use several pools for first-tier, local backups, you can have > more fine-grained control over what will be copied without having to > create and maintain your own SQL queries. The price, of course, would be > more setup in Pools and Schedules. > > And as usual there are more options even -- tags both attached to jobs > and used for copy selection would allow similar results (I'm not sure > they are available in version 15, though, but I hope Eric reads this > while he goes through the list of things to add for v. 17 ;-) and can be > used to control operations with straightforward external tooling.
Hello Arno, hello everybody, Bacula tags are available in Bacula Community starting from version 13.0. No need to add it :-) To select jobids for copy job can also be used a job 'comment' property. It can be even a bit easier for SQL query selection method because it is in the same SQL job table and the query will be simpler. In bconsole we can add for example custom marker string to selected jobids by command: update jobid=XXXXX comment="add_to_copy" and in the SQL query used in copy job select jobids by this string and by mentioned here already PriorJobId. Worth mentioning that copy jobs also provide integrated selection types by client, job, volume and others that, if used, do not require preparing SQL queries because they are pre-defined in Bacula, but the SQL query method is the best way to have customized jobids selection. Best regards, Marcin Haba _______________________________________________ Bacula-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-users
