VXA Tape V17

2000-12-28 Thread Bradley Glonka
Anyone using Ecrix VXA V17 tapes? I found this config in the faq-omatic I have a question: This drive is supposed to write 66gb with hardware compression. This config only reflects "length 30609 mbytes" about half of that. define tapetype VXA { comment "Ecrix VXA-1 V17"

Re: VXA Tape V17

2000-12-28 Thread C. Chan
Also Sprach Bradley Glonka: Anyone using Ecrix VXA V17 tapes? I found this config in the faq-omatic I have a question: This drive is supposed to write 66gb with hardware compression. This config only reflects "length 30609 mbytes" about half of that. define tapetype VXA {

Re: VXA Tape V17

2000-12-28 Thread John R. Jackson
This drive is supposed to write 66gb with hardware compression. This config only reflects "length 30609 mbytes" about half of that. Which is pretty close to correct, then. Manufactures reports twice the "native" density when giving the number for compression. I ran the tapetype utility with

Re: VXA Tape V17

2000-12-28 Thread C. Chan
Also Sprach John R. Jackson: - how do I take advantage of hardware compression? You fudge the length up from what you think it will do native based on the amount of compression you expect to get. And here's a tip -- **nobody** gets double :-). I typically see 20-35%. brad John R.

Re: VXA Tape V17

2000-12-28 Thread C. Chan
Also Sprach C. Chan: You fudge the length up from what you think it will do native based on the amount of compression you expect to get. And here's a tip -- **nobody** gets double :-). I typically see 20-35%. brad John R. Jackson, Technical Software Specialist, [EMAIL

Re: VXA Tape V17

2000-12-28 Thread John R. Jackson
... I think Amanda with software compression is smart enough not to compress if it means an increase in size ... I don't think so. Compression is always done in a pipeline so there is no chance to recover the original data if at the end it looks like it was a bad idea. C. Chan John R.