Hi Andrea, all, Am 07.07.2026 um 10:57 schrieb Andrea Venturoli: ...
Sorry, I sent the message before it was finished...
Convenient to keep topics in mail threads separated ;-)
Where does Bacula store the fact that a jobs was already copied?
This gets derived from the fact that some Jobs may have a PriorJobId value>0 in the catalog.
Is there a way (some query?) to trick it into thinking the older jobs where already copied?
What I could imagine to be reasonable might be to just move those Jobs into a different Pool. Of course this may be a bit messy if your Volumes contain a mixture of Jobs, in which case just updating Volumes to be members of another Pool may not be feasible. You would then have to either run local migration Jobs first, or get back to "cheating" -- which would more or less be the same effort and risk you have when using SQL queries for Copy Jobs.
Personally, I think that just having more Pools and maintaining a bit more complex Schedules is less problematic than all the near-magic hackery you could do with direct Catalog interaction. On the other hand, sometimes, and in particular if I know I'm not making anybody else's life harder, a bit of fun is also nice. And I'm glad I can chose with Bacula, for that matter.
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
