Hi,

No problem doing amlabel ISR006 right now, amanda will let you do the backup in 
ISR005 or ISR006, it is up to you.

I don't know which kind of tape you have, but in scsi tapes you cat do "mt -f 
/dev/nst0 compression 0" to turn hw comp off.

Cheers,

--
Inaki Sanchez

Rodrigo Ventura wrote:
> Hi. I have a couple of questions about amanda's behavior:
> 
> The first one is, amadmin CONF tape says, in my case, something like
> "The next Amanda run should go onto tape ISR005 or a new tape." If I
> add a new tape, say label ISR006, I guess it is automatically added to
> the amanda tape list, right? My question is, in this case, the next
> tape to be used in amdump is ISR005 or ISR006?
> 
> I'd like to not disrupt the tape sequence, i.e. I prefer
> ISR001 -> ISR002 -> ... -> ISR004 -> ISR005 -> ISR006 -> ISR001 -> ...
> rather than
> ISR001 -> ISR002 -> ... -> ISR004 -> ISR006 -> ISR005 -> ISR001 -> ...
> 
> In order to make this happen, do I have to wait until ISR005 get
> dumped (tonight), and only amlabel the new tape afterwards?
> 
> The second question is, I'd like to make sure compression is off for
> the new tape, but amtapetype -o -c -f /dev/tape refuses to work:
> 
> "amtapetype: /dev/tape: reading label: Input/output error"
> 
> Do I have to amlabel it? However, I'd like to do so only after being
> sure ISR006 is used next to the ISR005 one.
> 
> And a final question: anyone thinking about re-doing an amanda survey?
> I noticed the last one was done circa 2003, so it's a bit old... (I
> guess I wasn't using amanda back then yet...)
> 
> Cheers,
> 
> Rodrigo Ventura
>