>-i don't manage to make incremental backup of many
>disk :(
>into one tape (it seems to make a full backup each
>amdump)
That's correct. Every time you run Amanda (amdump or amflush), it will
start a new tape. That's just the way it is (for now).
If you want to conserve tapes, and you are sure you understand the
danger of leaving things in the holding disk without a copy on tape,
you can just not load a tape in the drive and amdump will leave things
in the holding disk. When you have enough there to make it worth while,
run amflush and write it all out to tape.
>Actually i suppose when amanda reuse a tape, it
>simply erase it, amanda does this if tape contains
>other disks for an another configuration (ex:
>DailySet2)???
When Amanda reuses a tape, it just starts writing again at the
beginning.
If you have multiple configurations, you should use labelstr and amlabel
to make sure each configuration has a unique label. This will protect
you from accidentally using the wrong tape in the wrong configuration.
For instance, our Research Computing Division (RCD) has a configuration
and the Instructional Computing Division (ICD) has a different one.
The tape labels are "nnnnnn/RCD" and "nnnnnn/ICD" to make sure they
cannot get mixed up.
>Beside, i reaffirm a little bug with amrecover:
>>EOF, check amidxtaped.debug file on localhost.
>>...
>and little : 'mt rewind' is adviced before OR retry a
>2nd extract with amrecover -> that's works well.
Could you explain this some more? Normally amidxtaped (used by amrecover)
rewinds the tape after each request. I don't know why you would need
to explicitly do it.
>I didn't found into amanda commands for deleting a
>disk into a tapes(not into the database definitely),
>is it possible with amanda or other command???
Not sure I understand. If you want Amanda to forget about a particular
disk that has been backed up before, you can use the "delete" subcommand
of "amadmin" to remove it from the database.
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
