I make a special amanda config with a one tape tapelist to just dump this
one large filesystem on a remote network that didn't make the last backup
due to an interuption. After nearly 24 hours, it made it to the local
holding disk on the server, but had a tape error trying to get it to tape.
The DLT drive complained about needing to be cleaned, so I did that,
amlabeled another tape (not a new one, but one that should be fine) and
attempted to amflush thusly:
---- su-2.05b$ amflush ns1 ns1_0 Scanning/home/amanda/dumps...
20060914210742: found Amanda directory.
Today is: 20060915
Flushing dumps in 20060914210742 to tape drive "/dev/nsa0".
Expecting a new tape. (The last dumps were to tape ns1_0)
Are you sure you want to do this [yN]? y
Running in background, you can log off now.
You'll get mail when amflush is finished.
---
The tape drive starts to spin, but a few seconds later, I get the amanda
report saying:
NOTES:
taper: tape ns1_0 kb 0 fm 0 [OK]
?
DUMP SUMMARY:
DUMPER STATS TAPER STATS
HOSTNAME DISK L ORIG-kB OUT-kB COMP% MMM:SS KB/s MMM:SS KB/s
-------------------------- --------------------------------- ------------
host.name.net /dev/da0s1f NO FILE TO FLUSH ---------------------------
(brought to you by Amanda version 2.4.5)
With all the stats at zero. There are definitely several ~1GB files in
the under ~amanda/dumps/20060914210742/ and it seemed to find the
directory fine...
Any ideas?
James Smallacombe PlantageNet, Inc. CEO and Janitor
[EMAIL PROTECTED]
http://3.am
=========================================================================
