Re: Q: Where does a job of type "Copy" store the volume information?

Bill Arlofski via Bacula-users <[email protected]> Wed, 20 Nov 2024 19:06:41 +0000

Newsgroups	gmane.comp.bacula.user
Message-ID	<[email protected]>

Hello Justin,


It's more simple than you think.


When Bacula prunes a Backup job which has a copy of itself, it promotes the Copy to a Backup job as you know.

But, all that happens is the 'jobtype' field in the Job table for this Copy Job is changed from a 'C' to a 'B', and so then 
it is now a Backup job, and this 'B'ackup job is now the default job which bacula will select when performing a restore.


Now for some fun and possibly confusing stuff:

P.S. Since the word "Copy" and "Copy Job" is used confusingly and interchangeably I have decided to call the Copy Job which 
gets called to select jobs to copy a "Copy Control Job", and the resulting copy of the backup is simply a "Copy Job"

When working with Copy and Migration control jobs in my baculabackupreport.py script, I had to adopt some standard naming 
convention to help keep my sanity. :)

Next thing to know: When a Copy or Migration Control job finds more than one Backup job to copy, the Copy/Migration control 
job triggers n-1 new Copy/Migration Control jobs of itself, each to work on one backup job, and the original Copy Control Job 
takes the final Backup job in the list and performs the Copy/Migration itself.

Fun stuff. 😬


Hope this helps,
Bill

-- 
Bill Arlofski
[email protected]

_______________________________________________
Bacula-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users

signature.asc (application/pgp-signature, 509 B)