[prev in list] [next in list] [prev in thread] [next in thread] 

List:       bacula-devel
Subject:    [Bacula-devel] Making copy job messaging better
From:       Phil Stracchino <phils () caerllewys ! net>
Date:       2022-05-02 23:52:58
Message-ID: bff47bcf-97bb-fb57-c49e-cb6ee79496cb () caerllewys ! net
[Download RAW message or body]

Folks,
This is just a general thought and rumination about copy jobs and their 
messaging.

The basic issue here is that each Copy job generates two messages.  You 
end up with a set of notification messages a bit like this:

   37     May 02 Bacula          (3.9K) Epsilon3_Backup (Full) OK
   38     May 02 Bacula          (3.3K) Minbar_Backup (Full) OK
   39     May 02 Bacula          (3.8K) Babylon5_Backup (Full) OK
   40     May 02 Bacula          (3.3K) Narn_Backup (Full) OK
   41     May 02 Bacula          (2.7K) Netstore_Backup (Full) OK
   42     May 02 Bacula          (2.4K) MySQL_Backup_New (Full) OK
   43     May 02 Bacula          (2.2K) Archive_Copy (Full) OK
   44     May 02 Bacula          (1.0K) Babylon5_Backup (Full) OK
   45     May 02 Bacula          (2.2K) Archive_Copy (Full) OK
   46     May 02 Bacula          (0.4K) Epsilon3_Backup (Full) OK
   47     May 02 Bacula          (2.2K) Archive_Copy (Full) OK
   48     May 02 Bacula          (0.4K) Netstore_Backup (Full) OK
   49     May 02 Bacula          (2.2K) Archive_Copy (Full) OK
   50     May 02 Bacula          (0.4K) Minbar_Backup (Full) OK
   51     May 02 Bacula          (0.4K) Narn_Backup (Full) OK
   52     May 02 Bacula          (2.2K) Archive_Copy (Full) OK
   53     May 02 Bacula          (3.1K) Archive_Copy (Full) OK
   54     May 02 Bacula          (0.4K) MySQL_Backup_New (Full) OK

where the first six messages are the original backup jobs, and the last 
twelve are the copy jobs that archive them onto removable media.  So 
there are two new messages for each job copied.  This pair, for example:

   46     May 02 Bacula          (0.4K) Epsilon3_Backup (Full) OK
   47     May 02 Bacula          (2.2K) Archive_Copy (Full) OK

Now, of this pair, all the information actually ABOUT the job and what 
was copied where is in the *second* message, titled Archive_Copy (Full). 
  That message body is about 40 lines, and contains ALL of the important 
information about the job.  But there is nothing in the title that 
connects it to the job copied.

There is no actual useful information in the one titled Epsilon3_Backup 
(Full).  All that's in it is this:

02-May 14:29 minbar-dir JobId 1499: Using Device "ArchiveCopy" to write.
02-May 14:29 epsilon3-file JobId 1499: Volume "ARCHIVE-20220502-14:00" 
previously written, moving to end of data.
02-May 14:29 epsilon3-file JobId 1499: Ready to append to end of Volume 
"ARCHIVE-20220502-14:00" size=44,912,413,674
02-May 14:50 epsilon3-file JobId 1499: Elapsed time=00:21:35, Transfer 
rate=33.76 M Bytes/second

It's not worth keeping the "named job" messages, but if you keep the 
"Archive" messages, you have to hunt through them all to find the 
relevant one.


So what I'm pondering is, how can we make this better?  Is there 
something we can do to make the Archive_Copy (in this example) job get a 
useful title that conveys information about *what* job it copied? 
ideally each copy operation would produce one message, not two; 
containing all the useful information about the copy operation; and with 
a title that both makes clear that it was a Copy job, and WHICH job it 
was copying.

Anyone have any ideas to offer on this front?


-- 
   Phil Stracchino
   Babylon Communications
   phils@caerllewys.net
   phil@co.ordinate.org
   Landline: +1.603.293.8485
   Mobile:   +1.603.998.6958


_______________________________________________
Bacula-devel mailing list
Bacula-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-devel
[prev in list] [next in list] [prev in thread] [next in thread]