"Andrew" == <[EMAIL PROTECTED]> on Mon, 30 Apr 2001 15:00:43 -0500
"John" == John R Jackson <[EMAIL PROTECTED]> on Mon, 30 Apr 2001 15:41:23 -0500
Andrew> 1) When I run an amflush I notice that the dump are put on
Andrew> tape starting with the smallest and working its way up to
Andrew> the largest last. Why is this?
John> I suspect the theory is to get as many images safely out to tape
John> as quickly as possible.
John> Would you prefer it was done some other way? Why?
I've thought that the reverse behavior (largest images first) would
result in better usage of tapes in a multiple tape configuration. Our
offsite backups run to multiple tapes, and Amanda always finds the end
of a tape by writing off the end of it:
INFO taper tape offsite-009 kb 19799936 fm 56 writing file: No space left on device
which results in the large image being written to the next tape.
Now, perhaps my Amanda configuration is screwed up, but if so I don't
know how. I'm writing to DDS-4 tapes, with a tapetype definition of
19,500 mbytes and a filemark of 0 bytes. My most recent log has
17,863,648 KB being written to the first tape, and then trying to
write an additional 5,899,168 KB, which would result in putting a
whopping 23,762,816 KB on the tape, far in excess of the tapetype
definition.
It struck me that doing the largest backups at the front of the tape
would make this work better.
But perhaps I have something messed up someplace. :)
