Hi All, [if this is more appropriate for hackers, please inform me]
I've been struggling with an OnStream ADR 50 drive (Not the SC-50) for the last two weeks. Everytime it seems to work with a small (test) backup, and it consistently fails for backup the real (big) data. I now understand that this is caused by a firmware bug in the ADR50. (Amanda closes the file upon starting the write of the next file, which might not occur before the drive timeouts, resulting in unreadble tapes) As a workaround, it has been suggested to dump to harddisk, and flush lateron. This means that there are no timeouts, as all data is readily available on the holding disk. This seems to work, but is a kludge. Now I have a few questions: 1) How can I configure amanda to flush to tape only after all dumps are done? Except for not inserting a tape untill the following morning. Would removing the write permission for amanda on the drive work (and running amflush as root?) and running it as follows (as root) dump.sh su -c amanda amdump DailySet1 amflush DailySet1 amverify DaiySet1 mt -f /dev/nst0 offline 2) I also would like to keep the files on disk (for quicker restores). How can I configure amanda not to delete these files after flushing, or only those that have a certain age? 3) Question to the hackers: Is it possible to change amada behaviour so that after a file is written to tape, it is closed immediately? Or does that interfere with normal amanda behaviour? Adminstrativa: I'm using RedHat 7.2 on a PIII 800MHz, with an Onstream ADR 50 SCSI LVD drive, firmware 2.39.
