Lee Fedor ([EMAIL PROTECTED]):
>>
>> I am using an Exabyte 10h changer with an 8505XL drive. I have been
>> using the existing tapetype for EXB-8505, but those are only 5GB
>> tapes. The XL drive have 7GB tapes and we need all the space we can
>> get (took 7 dumps to get 10 servers).
>>
>> So I ran the tapetype program and it produced this (with my own
>> comments, of course):
>>
>> define tapetype EXB-8505XL {
>> comment "Exabyte 8505XL tapes (works with Exabyte 10h changer)"
>> length 9584 mbytes
>> filemark 917280 kbytes
>> speed 667 kps
>> }
>>
>> 1] I'm fairly certain these are 7GB tapes (and even gave -e 7g to
>> tapetype when I ran it). Why does tapetype come back saying they are
>> 9.5GB?
> it getting 9.5 with software compression. which is reasonable.
Hmm.. That make sense. I guess I need to figure out how to turn off
hardware compressions the, since software compression should be better
and faster.
>> 2] When I run Amanda with the new tape type, it dumps about 2GB on
>> each tape, not 5GB or 7GB or 9GB. Could this be because there was
>> already 5GB of data on the tape and now it's filling in the last two?
>> This is the second dump cycle on these tapes. Do I have to erase or
>> rewind the tapes or something between dump cycles to get it to use the
>> whole tape or does this mean that Amanda is having some other problem
>> with the tape or drive?
>>
> You do need to rewind the tape everytime.
> amanda will assume it is at the beginning.
So I need to have a cron-job like this?
(su -c '/usr/local/amdump daily; mt -f /dev/nst0 rewind' tape)
Why not have Amanda automatically rewind the tape when it's done. Or
when it starts? That just seems to make sense since all the operations
would expect the tape to be rewound.
--
Jeremy Wadsack
Wadsack-Allen Digital Group
