On Wed, 17 Jan 2007 [EMAIL PROTECTED] wrote: > => Your fix works for me, but shows up a lack of Job.Name in the output. > > Hmmm... I'm not sure about the benefit to having the Job.Name...
Some of my multi-Tb SAN-attached clients may run anywhere up to 40 jobs. > => - SELECT DISTINCT Job.JobId,Client.Name AS > Client,StartTime,JobFiles,JobBytes, > => + SELECT DISTINCT Job.JobId,Job.Name,StartTime,JobFiles,JobBytes, > > Yes, I can see how having the Job.Name would be useful (especially for the > bacula-dir server, as the catalog backup is considered a "Full" backup). That too.... > => IMO There's not much point showing the client name as it's just been > => explicitly specified and you can't script "query" commands. > > Huh? I script query commands all the time--in fact, as part of the > post-catalog > backup, I've got shell and perl scripts that run about 5 queries nightly, Oops. I meant you can't just say "query 17 blah" > reporting on things like what tapes need to be changed, what tapes are > available to load, etc. I could certainly see scripting reports that query the > most recent backups for a long list of servers, such as: > > foreach $client (alpha-fd, beta-fd, gamma-fd) > do > echo "query\n3\n$client\nquit\n" | bconsole -f > /etc/bconsole.conf | \ > grep "^|" > done > > in which case, I would want the client name on each line of the output. > => > => YMMV YMMV = "Your Milage May Vary". In such a case you would want that output :) AB ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Bacula-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-users
