Hi andrea, all,
Am 07.07.2026 um 10:47 schrieb Andrea Venturoli:
On 7/4/26 17:49, Arno Lehmann via Bacula-users wrote:
Hello.
Keeping in mind that Pools are essentially for free, and Job
definitions too, what keeps you from using Copy Jobs with the
PoolUncopiedJobs selection scheme?
Thanks for pointing out an option that I didn't notice.
However, I have 12 months of local backups; as I'm adding cloud backups
now, wouldn't this directive suddenly copy *all* my jobs to the S3 storage?
Trick question ;-)
Not suddenly, as you can limit the number of copies spawned per copy job
invocation.
Eventually yes.
Mitigation here is, of course, another set of pools :-)
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.
Cheers,
Arno
bye & Thanks
av.
_______________________________________________
Bacula-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users
--
Arno Lehmann
IT-Service Lehmann
Sandstr. 6, 49080 Osnabrück
_______________________________________________
Bacula-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users
