Bill Moran wrote:
"Erik P. Olsen" <[EMAIL PROTECTED]> wrote:
I am infrequently getting tape full conditions at times when I did not expect
it. My tapes are DDS-4 tapes and they are considered "Full" by bacula at various
capacities, for exampel:
21,112,841,569
6,445,884,582
17,477,850,063
15,855,178,172
After the last volume ran "full" and mounting of the next empty volume it
appended only 3,710,244,549 to it, an amount which I had thought could easily be
squeezed into the "full" volume.
I don't understand what triggers the "Full" condition especially the 6GB volume
is wierd since it shouldn't be full before approx. 20GB of data has been written
to it.
Bytes written isn't the only criteria that Bacula uses to determine when
a tape is full. Check to see if you have pool settings such as the
maximum number of jobs per volume set.
I know about the three pool settings which may influence the tape full criteria
but I have none of them active.
--
Regards,
Erik P. Olsen.
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
