Dump too big for tape

Hi all -

Well, here I am again…same server different issue. My backups are still failing on that client with a timeout and I'm still searching to figure out why. But that's not why I'm here today. Running amanda 2.4.2p2 on a RH8 box with a seagate stand alone with 125m DDS3 12/24GB DAT tapes and hardware compression is turned off.

Report says:
These dumps were to tape isymmdaily01.
The next tape Amanda expects to use is: isymmdaily06.

FAILURE AND STRANGE DUMP SUMMARY:
www.iclear / lev 0 FAILED [mesg read: Connection timed out]

STATISTICS:
                          Total       Full      Daily
                        --------   --------   --------
Estimate Time (hrs:min)    0:02
Run Time (hrs:min)         3:57
Dump Time (hrs:min)        0:58       0:58       0:00
Output Size (meg)        5798.6     5787.0       11.7
Original Size (meg)      5798.6     5787.0       11.7
Avg Compressed Size (%)     --         --         --    (level:#disks ...)
Filesystems Dumped           10          9          1   (1:1)
Avg Dump Rate (k/s)      1717.8     1716.1     3433.8

Tape Time (hrs:min)        1:32       1:32       0:00
Tape Size (meg)          5798.9     5787.2       11.7
Tape Used (%)              50.1       50.0        0.1   (level:#disks ...)
Filesystems Taped            10          9          1   (1:1)
Avg Tp Write Rate (k/s) 1072.5     1072.4     1102.8

FAILED AND STRANGE DUMP DETAILS:

/-- www.iclear / lev 0 FAILED [mesg read: Connection timed out]
sendbackup: start [www.iclear.com:/ level 0]
sendbackup: info BACKUP=/usr/local/bin/tar
sendbackup: info RECOVER_CMD=/usr/local/bin/tar -f... -
sendbackup: info end
\--------

NOTES:
planner: Dump too big for tape: full dump of isymmdb:/var delayed.
taper: tape isymmdaily01 kb 5938112 fm 10 [OK]

DUMP SUMMARY:
                                      DUMPER STATS                TAPER STATS
HOSTNAME DISK          L   ORIG-KB   OUT-KB COMP% MMM:SS    KB/s MMM:SS    KB/s
------------------------ --------------------------------------- --------------
isymmdb /etc          0      2336     2336   --    0:04   618.6   0:01 1739.3
isymmdb /export       0     78560    78560   --    0:21 3803.3   1:25   922.7
isymmdb /opt          0    371488   371488   --    2:08 2911.2   5:51 1058.6
isymmdb -oracle/admin 0   2897184 2897184   --    9:27 5107.0 44:45 1079.1
isymmdb /usr          0    695872   695872   --    5:30 2106.8 10:45 1079.1
isymmdb /var          1     11936    11936   --    0:03 3432.9   0:11 1102.8
web.isym /etc          0      2688     2688   --    0:01 2700.6   0:03   809.1
web.isym /home         0     64576    64576   --    0:03 20024.3   1:01 1055.0
web.isym /var          0    229344   229344   --    0:17 13575.1   3:33 1078.4
www.icle /             0 FAILED -----------------------------------------------
xfer.icl /             0   1583808 1583808   --   39:42   664.8 24:42 1069.0

(brought to you by Amanda version 2.4.2p2)

The interesting part is that for tape size it says: 5798.9 while my estimate says 5798.6…and my entry in amanda.conf for this tape says:

define tapetype Verbatim-125m {
    comment "Verbatim 4mm-125m DAT"
    length 11576 mbytes
    filemark 0 kbytes
    speed 1077 kbytes
}

As I look back through my reports (2 days earlier my backup was 5950.2 and it says my tape size was 5950.5) I see that my tape size is always reading .3 over my estimated dump size.

First, is this normal that my tape size never displays what it actually is.
Should I chalk this up to a media problem? When my failing client was working, I was successfully backing up 10229.2.

Any input appreciated. THANKS.
rapc

Rebecca A. Crum
Systems Administrator
Unterberg & Associates, P.C.
(219) 736-5579 ext. 184