On 7/7/26 04:57, Andrea Venturoli wrote:
On 7/7/26 10:47, Andrea Venturoli wrote:
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?
bye & Thanks
av.
Sorry, I sent the message before it was finished...
Where does Bacula store the fact that a jobs was already copied?
Is there a way (some query?) to trick it into thinking the older jobs
where already copied?
Bacula knows that a job was already copied if an instance of the Copy
job has a Prior Job field pointing to the Job it was copied from. You
can see that mechanism at work in the query I showed you; that part of
it is fundamentally the mechanism underlying PoolUncopiedJobs.
You probably COULD, with some work, "trick it" into thinking that older
jobs had already been copied, but it is probably wiser to simply set a
horizon on how far back you look (which you will also see in my example;
it only considers jobs within the past seven days).
--
Phil Stracchino
Fenian House Publishing
[email protected]
[email protected]
Landline: +1.603.293.8485
Mobile: +1.603.998.6958
_______________________________________________
Bacula-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users
