On 2025/12/08 15:17, Rob Gerber wrote:
Glad you got it working!
Not sure I have though, in that nothing seems to have happened, messages-wise, in quite some time.
The 2 jobs is easy to explain: The MigrateDCIM-to-Tape job could more reasonably be called a "Copy Control" job. It's task is to orchestrate the work done by the job it launches (job ID 8 in the most recent instance from your email). JID8 is a clone of JID4 in almost every way (down to the joblog), except for details that must differ, like storage resource used. Bacula is making a true copy of JID4 in JID8, which could stand in for JID4 if it were impossible to use for recovery.
I see where that thinking is heading, but, if it's making a copy of JobId 4, and that was an Incremental that ran as "first time Full", does that mean that there's now NOTHING that has changed, and hence both displaying 0 Files/Bytes,
JobId Type Level Files Bytes Name Status ====================================================================== 7 Copy Full 0 0 MigrateDCIM-to-Tape is running 8 Back Full 0 0 BackupDCIM-to-FileCP is running
rather than the actual payload from JobId 4?
JobId Level Files Bytes Status Finished Name 4 Full 3,514 152.7 M OK 04-Dec-25 16:25 ...
then again, if it really was "Copy-ing" 0 Files/Bytes, both Jobs would have ended by now, no? Kevin Buckley _______________________________________________ Bacula-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-users
