Amanda-Users

amdump ok amrestore not!

2003-05-22 12:02:31
Subject: amdump ok amrestore not!
From: "Ryan Moreton" <ryan.moreton AT edge-logic DOT com>
To: <amanda-users AT amanda DOT org>
Date: Thu, 22 May 2003 16:57:25 +0100
Hi all,

I am having a few problems with my Amanda setup and was wondering if anybody
has experienced similar problems to what I am encountering:

System Setup
Amanda Server Hostname  : ELLWDB02
Operating System                : Redhat 7.3
Amanda                  : Version 2.4.2p2
Tape Drive                      : OnStream ADR2 120
Tapes                   : ADR 30 Gig (60 Gig compressed) x 7

I have created a configuration called normal and have configured the
amanda.conf and disklist files to back up one directory and all it's
contents locally and one directory and all it's contents from another
machine on the same network. My backup will be run once every day (one disk
for every day and remove the old contents on the disk on a rotation basis)
and have amended the amanda.conf file for these requirements.

I have configured the /etc/hosts file on both machines so they know about
each other and gone through the Amanda FAQ's when I encountered some earlier
problems. Both machines can now communicate successfully between each other
and when I run amdump it sends me a e-mail stating that everything is ok. I
have to label the disks using amlabel to ensure that amdump works correctly
as follows:

#/usr/sbin/amlabel /normal EdgeLogic1

Output of email is as follows:
These dumps were to tape EdgeLogic1.
The next tape Amanda expects to use is: a new tape.

STATISTICS:
                          Total       Full      Daily
                        --------   --------   --------
Estimate Time (hrs:min)    0:00
Run Time (hrs:min)         0:01
Dump Time (hrs:min)        0:00       0:00       0:00
Output Size (meg)           0.2        0.0        0.2
Original Size (meg)         1.8        0.0        1.8
Avg Compressed Size (%)    10.2        --        10.2   (level:#disks ...)
Filesystems Dumped            3          0          3   (1:3)
Avg Dump Rate (k/s)       474.1        --       474.1

Tape Time (hrs:min)        0:01       0:00       0:01
Tape Size (meg)             0.3        0.0        0.3
Tape Used (%)               0.2        0.0        0.2   (level:#disks ...)
Filesystems Taped             3          0          3   (1:3)
Avg Tp Write Rate (k/s)     7.5        --         7.5


NOTES:
  taper: tape EdgeLogic1 kb 288 fm 3 [OK]


DUMP SUMMARY:
                                     DUMPER STATS            TAPER STATS
HOSTNAME     DISK        L ORIG-KB OUT-KB COMP% MMM:SS  KB/s MMM:SS  KB/s
-------------------------- --------------------------------- ------------
localhost    /var/opt    1      10     32 320.0   0:001551.4   0:24   2.6
mogador      /etc/httpd  1      10     32 320.0   0:00 524.8   0:07   9.0
mogador      -mcat-4.0.6 1    1870    128   6.8   0:00 393.3   0:07  22.5

(brought to you by Amanda version 2.4.2p2)

However I cannot restore the files once they have been backed up on the
disk. When I attempt a amrestore /dev/nst0 I get the following message:

amrestore:   0: skipping start of tape: date 20030521 label EdgeLogic1
amrestore: strange amanda header: "AMANDA: FILE 20030521 localhost /var/opt
lev 0 comp(.g~ program$/bin/tar"

Sometimes I get a different header and sometimes I the header isn't being
displayed correctly.

I think it has something to do with the tapetype in the amanda.conf file:
define tapetype ADR {
    comment "OnStream ADR tape drives"
    length 30000 mbytes        # 30 Gig tapes
    filemark 32 kbytes           # I don't know what this means
    speed 1579 kbytes          # 1.5 Mb/s
}

Please find attached configuration files (amanda.conf & disklist) for more
detail.

Has anybody seen this problem before? Any help would be hugely appreciated.

Kind Regards,

Ryan Moreton
ryan.moreton AT edge-logic DOT com












Attachment: disklist
Description: Binary data

Attachment: amanda.conf
Description: Binary data

<Prev in Thread] Current Thread [Next in Thread>