Hello!
I really would like to use amanda, bu i have the following problem:
dumping works o.k. For example if i dump two partitions, i get
---
NOTES:
taper: tape Marsupilami01 kb 115360 fm 2 [OK]
---
And no errors. So now i would like to restore the data. I i rewind the Tape
and then restore the whole backup - no problem, i get the following messages:
--
[/mnt/cdimage/amanda] # mt -f /dev/st0 rewind
[/mnt/cdimage/amanda] # amrestore /dev/nst0 localhost
amrestore: 0: skipping start of tape: date 20010113 label Marsupilami01
amrestore: 1: restoring localhost._dev_sda5.20010113.0
amrestore: 2: restoring localhost._dev_sda8.20010113.0
amrestore: 3: reached end of tape: date 20010113
--
The files are back on disk. No problem restoring only /dev/sda5, but
i am unable to restore /dev/sda8 only.
It is not possible to use amrecover/amrestore on
any file except the first on tape. If i try, i get the message:
--
[/mnt/cdimage/amanda] # mt -f /dev/st0 rewind
[/mnt/cdimage/amanda] # amrestore /dev/nst0 localhost /dev/sda8
amrestore: 0: skipping start of tape: date 20010113 label Marsupilami01
amrestore: 1: skipping localhost._dev_sda5.20010113.0
amrestore: error reading file header: Eingabe-/Ausgabefehler
--
When i now do an mt -f /dev/nst0 bsf 1 and afterwards
amrestore /dev/nst0 localhost /dev/sda8
it works, too. So it seems, amanda skips one file to far?
So what goes wrong there? my amanda.conf is at the end of this message. It
would be great, if anyone could help me.
By the way, i am using a Seagate STT2800N SCSI Travan4 Tapedrive, amanda
2.4.1p1, debian Linux potato - what else do you need to know?
Bye, and Thanks
Frank
#
# amanda.conf - sample Amanda configuration file.
#
# If your configuration is called, say, "DailySet1", then this file
# normally goes in /etc/amanda/DailySet1/amanda.conf.
#
# for explanation of the parameters refer to amanda(8) and
# /usr/doc/amanda/WHATS.NEW.gz
org "Full" # your organization name for reports
mailto "haegar" # space separated list of operators at your site
dumpuser "backup" # the user to run dumps under
#
inparallel 2 # maximum dumpers that will run in parallel
netusage 600 # maximum net bandwidth for Amanda, in KB per sec
# a filesystem is due for a full backup once every <dumpcycle> days
dumpcycle 4 weeks # the number of days in the normal dump cycle
tapecycle 1 tapes # the number of tapes in rotation
bumpsize 0 MB # minimum savings (threshold) to bump level 1 -> 2
bumpdays 0 # minimum days at each level
bumpmult 4 # threshold = bumpsize * (level-1)**bumpmult
#runtapes 9 # explained in WHATS.NEW
#tpchanger "no-changer" # the tape-changer glue script, see TAPE.CHANGERS
tapedev "/dev/nst0" # Linux @ tuck, important: norewinding
# tapedev "/dev/nrst8" # or use the (no-rewind!) tape device directly
tapetype SeagateTR4 # what kind of tape it is (see tapetypes below)
labelstr "^Marsupilami[0-9][0-9]*$" # label constraint regex: all tapes must match
#diskdir "/space" # where the holding disk is
#disksize 290 MB # how much space can we use on it
#diskdir "/dumps/amanda/work" # additionaly holding disks can be specified
diskdir "/mnt/cdimage/amanda"
disksize 350 MB # they are used round-robin
# Amanda needs a few MB of diskspace for the log and debug files,
# as well as a database. This stuff can grow large, so the conf directory
# isn't usually appropriate.
infofile "/var/lib/amanda/Full/curinfo" # database filename
logfile "/var/log/amanda/Full/log" # log filename
# where the index files live
indexdir "/var/lib/amanda/Full/index"
# tapetypes
#
# Define the type of tape you use here, and use it in "tapetype" above.
# Some typical types of tapes are included here. The tapetype tells amanda
# how many MB will fit on the tape, how big the filemarks are, and how
# fast the tape device is.
#
# For completeness Amanda should calculate the inter-record gaps too, but it
# doesn't. For EXABYTE and DAT tapes this is ok. Anyone using 9 tracks for
# amanda and need IRG calculations? Drop me a note if so.
define tapetype STT8000A {
comment "just produced by tapetype program"
length 3850 mbytes
filemark 0 kbytes
speed 505 kps
}
define tapetype SeagateTR4 {
comment "Aus der Mailingliste"
length 4000 mbytes
filemark 8 kbytes
speed 551 kbytes
}
# dumptypes
#
# These are referred to by the disklist file. The dumptype specifies
# certain "options" for dumping including:
# index - keep an index of the files backed up
# compress-fast - (default) compress on the client using fast algorithm
# compress-best - compress using the best (and slowww) algorithm
# no-compress - don't compress the dump output
# srvcompress - Compress dumps on the tape host instead of client
# machines. This may be useful when a fast tape host
# is backing up slow clients.
# record - (default) record the dump in /etc/dumpdates
# no-record - don't record the dump, for testing
# no-hold - don't go to the holding disk, good for dumping
# the holding disk partition itself.
# skip-full - Skip the disk when a level 0 is due, to allow
# full backups outside Amanda, eg when the machine
# is in single-user mode.
# skip-incr - Skip the disk when the level 0 is NOT due. This
# is used in archive configurations, where only full
# dumps are done and the tapes saved.
# no-full - Do a level 1 every night. This can be used, for
# example, for small root filesystems that only change
# slightly relative to a site-wide prototype. Amanda
# then backs up just the changes.
#
# Also, the dumptype specifies the priority level, where "low", "medium" and
# "high" are the allowed levels. These are only really used when Amanda has
# no tape to write to because of some error. In that "degraded mode", as
# many incrementals as will fit on the holding disk are done, higher priority
# first, to insure the important disks are dumped first.
define dumptype mein-tar {
program "GNUTAR"
comment "partitions dumped with tar"
options no-compress, index, exclude-list "/etc/amanda/exclude.gtar"
priority high
dumpcycle 0
maxcycle 0
}
define dumptype mein-full {
comment "Full dump of this filesystem always"
options no-compress, index
priority high
dumpcycle 0
maxcycle 0
}
define dumptype always-full {
comment "Full dump of this filesystem always"
options no-compress
priority high
dumpcycle 0
maxcycle 0
}
define dumptype comp-user-tar {
program "GNUTAR"
comment "partitions dumped with tar"
options compress-fast, index, exclude-list "/etc/amanda/exclude.gtar"
priority medium
}
define dumptype comp-root-tar {
program "GNUTAR"
comment "Root partitions with compression"
options compress-fast, index, exclude-list "/etc/amanda/exclude.gtar"
priority low
}
define dumptype user-tar {
program "GNUTAR"
comment "partitions dumped with tar"
options no-compress, index, exclude-list "/etc/amanda/exclude.gtar"
priority medium
}
define dumptype high-tar {
program "GNUTAR"
comment "partitions dumped with tar"
options no-compress, index, exclude-list "/etc/amanda/exclude.gtar"
priority high
}
define dumptype root-tar {
program "GNUTAR"
comment "Root partitions dumped with tar"
options no-compress, index, exclude-list "/etc/amanda/exclude.gtar"
priority low
}
define dumptype comp-user {
comment "Non-root partitions on reasonably fast machines"
options compress-fast
priority medium
}
define dumptype nocomp-user {
comment "Non-root partitions on slow machines"
options no-compress
priority medium
}
define dumptype holding-disk {
comment "The master-host holding disk itself"
options no-hold
priority medium
}
define dumptype comp-root {
comment "Root partitions with compression"
options compress-fast
priority low
}
define dumptype nocomp-root {
comment "Root partitions without compression"
options no-compress
priority low
}
define dumptype comp-high {
comment "very important partitions on fast machines"
options compress-best
priority high
}
define dumptype nocomp-high {
comment "very important partitions on slow machines"
options no-compress
priority high
}
define dumptype nocomp-test {
comment "test dump without compression, no /etc/dumpdates recording"
options no-compress, no-record
priority medium
}
define dumptype comp-test {
comment "test dump with compression, no /etc/dumpdates recording"
options compress-fast, no-record
priority medium
}
