First backup went fine, but amanda seems to get trouble with the large filesystems. One of them /var is about
actually /usr from the report below
70 Gig, but only 4% of it about 2.5 GB, are filled with data. What ist amanda calculating to determine whether a backup fits on the tape.
Calculates it the overall size of the Partition or the actual amount of data on that partition ?
The actual amount of data on the disk. It this by running dump and breaking off as soon as dump gives an estimate or running gnutar with the option --file /dev/null. Especially the latter can take some time if there are many small files on disk. But this is not your problem as your estimate took only 2 minutes.
I include an exerpt from the error mail amanda sent me:
FAILURE AND STRANGE DUMP SUMMARY:
_www.XXXXX_ <http://www.duisbu/> /usr lev 1 FAILED [dump larger than tape, -1 KB, skipping incremental]
Actually it got a reply back "-1 Kb" but in unsigned arithmetic this is larger than tape.
The message actually means that there was a problem with the estimate. Delve in the /tmp/amanda/*debug files on that client to find out what is happening.
(Still on my todo list: find out where amanda makes the mistake of taking -1 as "too large".)
STATISTICS: Total Full Daily -------- -------- -------- Estimate Time (hrs:min) 0:02 Run Time (hrs:min) 6:20 Dump Time (hrs:min) 6:14 0:07 6:07 Output Size (meg) 3395.1 1701.8 1693.3 Original Size (meg) 4813.9 2500.1 2313.8 Avg Compressed Size (%) 62.7 68.1 52.2 (level:#disks ....) Filesystems Dumped 4 1 3 (1:3) Avg Dump Rate (k/s) 154.8 3884.7 78.8
Tape Time (hrs:min) 0:11 0:06 0:05 Tape Size (meg) 3395.1 1701.8 1693.3 Tape Used (%) 8.9 4.5 4.4 (level:#disks ...) Filesystems Taped 4 1 3 (1:3) Avg Tp Write Rate (k/s) 5240.3 4589.4 6111.4
USAGE BY TAPE: Label Time Size % Nb tape02 0:11 3395.1 8.9 4
NOTES: planner: Full dump of _www.xxxxxxx.xx:/var promoted from 6 days ahead. taper: tape tape02 kb 3476736 fm 4 [OK]
DUMP SUMMARY: DUMPER STATS TAPER STATS HOSTNAME DISK L ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s -------------------------- --------------------------------- ------------ lx18027 hda3 1 981520 981520 -- 344:37 47.5 2:05 7840.0 lx18027 hda5 1 57990 57990 -- 20:18 47.6 0:08 7351.2 __www.xxxx_ / 1 1329790 694396 52.2 1:565 968.6 2:31 4609.8 __www.xxxx_ /usr 1 FAILED --------------------------------------- __www.xxxx_ /var 0 2560100 1742633 68.1 7:29 3884.7 6:20 4589.4
(brought to you by Amanda version 2.4.4p1)
First I have added some whitespace between the numbers above. There is an amanda directive "colspec" for this. It makes your reports much more readable.
Maybe not related, but is it normal that lx18027 is so incredibly slow? It could be 486 with 8 Mbyte RAM indeed, or it could be mismatch with full/half duplux on your 100Mbit switch?
-- Paul Bijnens, Xplanation Tel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUM Fax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *********************************************************************** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... * * ... "Are you sure?" ... YES ... Phew ... I'm out * ***********************************************************************
