I’m running into a problem where jobs are being canceled as duplicates of a job currently running. Trying to find the happy medium with correct number of volumes to keep the disk from filling up but it looks like the number of volumes being created is so high that jobs are waiting for appendable volumes to continue. Am I just saying that my client is trying to back up too much data to too little storage? Or is there some nuance I’m missing? Also wondering as I’m looking at the list of jobs in bconsole. Is jobbytes the number of bytes being backed up? Or the number of compressed bytes written by the job?
Thanks for input ya’ll. Jim
_______________________________________________ Bacula-users mailing list Baculafirstname.lastname@example.org https://lists.sourceforge.net/lists/listinfo/bacula-users