Josip:
That is obviously the problem, but I'm not sure why it has occurred, or
how to correct it. These are standard LTO2 tapes, that were previously
used in a different setting. I used an mt command, mt -f /dev/nst0 weof
to write an end of file mark at the begining so I could use bacula to
re-label them. All of the tapes are marked with a maxvolbytes of
53,687,091,200. volbytes is set to 64512 in each of them. I guess
something was changed significantly between the 5.X version of bacula
and 9.6, but it also might be the upgrade of Slackware. I also don't
recall the shoeshine parameter being enabled in the prior release. In my
current setup, which I will probably have to re-create, my spool files
grow quite large.
Thank you for pointing my search to a satisfactory solution.
Alan
On 3/8/22 11:31, Josip Deanovic wrote:
On 2022-03-08 15:23, Alan Polinsky wrote:
I have recently moved from an old version of Bacula FROM THE 5.X
series to 9.6, along with my move from Slackware 14.2 to Slackware 15,
along with a change to Mariadb 10.5. (I would first like to thank Phil
Stracchino for his help in getting things configured properly.) I am
backing up to LTO2 tapes which should have a minimum of about 200 gigs
of storage. I seem to be getting requests to mount a new tape after
about 80 gigs. Initially I thought that perhaps a tape had some sort
of defect, but that was disproved when I put in a previously unused
tape. Perhaps I have not configured some parameter properly. Can
someone suggest what parameter I might be able to change or add to
assure more complete tape utilization? (I should mention that the tape
drive wrote complete tapes under the old release.)
Hi Alan
I would suggest to use the bconsole command llist to check the
current media parameters.
Specifically, check for variables like maxvolbytes, maxvolfiles and
maxvoljobs.
Regards!
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
