Hello!
I've got a problem with my Amanda installation:
I am using Amanda version 2.4.2p2 on SuSE-Linux 6.3 (i386) - Kernel
2.2.19.
Amanda should always do only full backups daily (Mo to Fr), weekly
(every Sa)
and monthly (every 1st Day in month).
For that i have 3 configurations, and all have the same settings
(without configname
and no of tapes):
# general parameters
- dumpcycle 0 day # the number of days in the normal dump cycle
# dumptypes
define dumptype global {
strategy noinc
...
All was working well, but since a few weeks my weekly configuration is
trying to do
a level 2 backup of the disk /usr2. Last week i forced a full backup of
this disk via
amadmin, but the last backup failed again with
FAILURE AND STRANGE DUMP SUMMARY:
gretel /usr2 lev 0 FAILED [can't switch to incremental dump]
First this behaviour occured with Amanda 2.4.2b2, so i updated to
2.4.2p2 last week. But Amanda is trying to continue to do incrementals.
Because of the description in amanda.conf (2.4.2b2)
# "noinc" - do level 0 dumps every time.
# Unfortunately, this is not currently
# implemented. Use `dumpcycle 0'
# instead.
I commented out this command, but nothing changes.
I have nothing changed on the Amanda server, in the configurations or
something else. So why is Amanda trying to do incrementals since a
few weeks?
Please reply to me directly, because i'm not subscribed in the list
anymore.
I have attached the Amanda-email my amanda.conf.
Greetings,
Jens Krause
---------------------------------------------------------------------------------------------------------
Email:
Subject: woche AMANDA MAIL REPORT FOR May 13, 2001
X-AntiVirus: scanned for viruses by AMaViS 0.2.1 (http://amavis.org/)
*** A TAPE ERROR OCCURRED: [label Tagessicherung.Freitag doesn't match
labelstr "^Wochensicherung.Woche[1-5]"].
Some dumps may have been left in the holding disk.
Run amflush to flush them to tape.
The next tape Amanda expects to use is: Wochensicherung.Woche2.
FAILURE AND STRANGE DUMP SUMMARY:
gretel /usr2 lev 0 FAILED [can't switch to incremental dump]
STATISTICS:
Total Full Daily
-------- -------- --------
Estimate Time (hrs:min) 0:08
Run Time (hrs:min) 1:33
Dump Time (hrs:min) 1:25 1:25 0:00
Output Size (meg) 8437.5 8437.5 0.0
Original Size (meg) 8437.5 8437.5 0.0
Avg Compressed Size (%) -- -- --
Filesystems Dumped 6 6 0
Avg Dump Rate (k/s) 1696.0 1696.0 --
Tape Time (hrs:min) 0:00 0:00 0:00
Tape Size (meg) 0.0 0.0 0.0
Tape Used (%) 0.0 0.0 0.0
Filesystems Taped 0 0 0
Avg Tp Write Rate (k/s) -- -- --
NOTES:
planner: Forcing full dump of henko:/ as directed.
planner: Forcing full dump of henko:/opt as directed.
planner: Forcing full dump of gretel:/ as directed.
planner: Forcing full dump of gretel:/opt/informix as directed.
planner: Forcing full dump of gretel:/usr2 as directed.
planner: Forcing full dump of gretel:/usr5 as directed.
planner: Forcing full dump of focus:/ as directed.
DUMP SUMMARY:
DUMPER STATS TAPER STATS
HOSTNAME DISK L ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS
KB/s
-------------------------- ---------------------------------
------------
focus / 0 14600001460000 -- 60:17 403.7 N/A N/A
gretel / 0 28648322864832 -- 13:163599.8 N/A N/A
gretel -t/informix 0 65088 65088 -- 0:106199.8 N/A N/A
gretel /usr2 0 FAILED
---------------------------------------
gretel /usr5 0 38152003815200 -- 7:597961.3 N/A N/A
henko / 0 307040 307040 -- 2:252120.8 N/A N/A
henko /opt 0 127808 127808 -- 0:482685.1 N/A N/A
(brought to you by Amanda version 2.4.2p2)
---------------------------------------------------------------------------------------------------------
amanda.conf:
#
# amanda.conf - sample Amanda configuration file. This started off life
as
# the actual config file in use at CS.UMD.EDU.
#
# If your configuration is called, say, "csd", then this file normally
goes
# in @CONFIG_DIR@/csd/amanda.conf.
#
# general parameters
#
org "woche" # your organization name for reports
mailto "root" # space separated list of operators at your site
dumpuser "root" # the user to run dumps under
inparallel 5 # maximum dumpers that will run in parallel
netusage 1200 Kbps # maximum net bandwidth for Amanda, in KB per sec
dumpcycle 0 day # the number of days in the normal dump cycle
runspercycle 0 day # the number of amdump runs in dumpcycle days
tapecycle 4 tapes # the number of tapes in rotation
# 4 weeks (dumpcycle) times 5 tapes per week
(just
# the weekdays) plus a few to handle errors that
# need amflush and so we do not overwrite the
full
# backups performed at the beginning of the
previous
# cycle
### ### ###
# WARNING: don't use `inf' for tapecycle, it's broken!
### ### ###
bumpsize 20 Mb # minimum savings (threshold) to bump level 1 -> 2
bumpdays 1 # minimum days at each level
bumpmult 4 # threshold = bumpsize * bumpmult^(level-1)
etimeout 600 # seconds per filesystem for estimates
#etimeout -600 # total number of seconds for estimates.
# a positive number will be multiplied by the number of filesystems on
# each host; a negative number will be taken as an absolute total
time-out.
# The default is 5 minutes per filesystem.
# Specify tape device and/or tape changer. If you don't have a tape
# changer, and you don't want to use more than one tape per run of
# amdump, just comment out the definition of tpchanger.
# Some tape changers require tapedev to be defined; others will use
# their own tape device selection mechanism. Some use a separate tape
# changer device (changerdev), others will simply ignore this
# parameter. Some rely on a configuration file (changerfile) to
# obtain more information about tape devices, number of slots, etc;
# others just need to store some data in files, whose names will start
# with changerfile. For more information about individual tape
# changers, read docs/TAPE.CHANGERS.
# At most one changerfile entry must be defined; select the most
# appropriate one for your configuration. If you select man-changer,
# keep the first one; if you decide not to use a tape changer, you may
# comment them all out.
runtapes 1 # number of tapes to be used in a single run of amdump
tapedev "/dev/nst0" # the no-rewind tape device to be used
# rawtapedev "/dev/null" # the raw device to be used (ftape only)
# tpchanger "chg-manual" # the tape-changer glue script
# changerfile "/usr/adm/amanda/DailySet1/changer"
# changerfile "/usr/adm/amanda/DailySet1/changer-status"
# changerfile "/usr/local/etc/amanda/DailySet1/changer.conf"
# changerdev "/dev/null"
tapetype EXB-Mammoth # what kind of tape it is (see tapetypes below)
labelstr "^Wochensicherung.Woche[1-5]" # label constraint regex: all
tapes must match
# Specify holding disks. These are used as a temporary staging area for
# dumps before they are written to tape and are recommended for most
sites.
# The advantages include: tape drive is more likely to operate in
streaming
# mode (which reduces tape and drive wear, reduces total dump time);
multiple
# dumps can be done in parallel (which can dramatically reduce total
dump time.
# The main disadvantage is that dumps on the holding disk need to be
flushed
# (with amflush) to tape after an operating system crash or a tape
failure.
# If no holding disks are specified then all dumps will be written
directly
# to tape. If a dump is too big to fit on the holding disk than it will
be
# written directly to tape. If more than one holding disk is specified
then
# they will all be used round-robin.
holdingdisk hd1 {
comment "main holding disk"
directory "/workingdisk/workingdisk" # where the holding disk is
use 12660000KB # how much space can we use on it
# a negative value mean:
# use all space except that value
# chunksize -1 # size of chunk if you want big dump to be
# dumped on multiple files on holding disks
# N Kb/Mb/Gb split disks in chunks of size N
# 0 split disks in INT_MAX/1024 Kb
chunks
# -1 same as -INT_MAX/1024 (see below)
# -N Kb/Mb/Gb dont split, dump larger
# filesystems directly to tape
# (example: -2 Gb)
chunksize 1500 Mb
}
#holdingdisk hd2 {
# directory "/dumps2/amanda"
# use 1000 Mb
# }
#holdingdisk hd3 {
# directory "/mnt/disk4"
# use 1000 Mb
# }
# If amanda cannot find a tape on which to store backups, it will run
# as many backups as it can to the holding disks. In order to save
# space for unattended backups, by default, amanda will only perform
# incremental backups in this case, i.e., it will reserve 100% of the
# holding disk space for the so-called degraded mode backups.
# However, if you specify a different value for the `reserve'
# parameter, amanda will not degrade backups if they will fit in the
# non-reserved portion of the holding disk.
reserve 0 # percent
# This means save at least 30% of the holding disk space for degraded
# mode backups.
# 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. We use /usr/adm. Create an amanda
directory
# under there. You need a separate infofile and logfile for each
# configuration, so create subdirectories for each conf and put the
files
# there. Specify the filenames below.
infofile "/usr/local/var/amanda/woche/amanda.info" # database
filename
logfile "/usr/local/var/amanda/woche/amanda.log" # log filename
indexdir "/usr/local/var/amanda/woche/index" # index directory
# tapelist "/usr/adm/amanda/DailySet1/tapelist" # list of used tapes
# tapelist is stored, by default, in the directory that contains
amanda.conf
# 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.
#
# A filemark is the amount of wasted space every time a tape section
# ends. If you run `make tapetype' in tape-src, you'll get a program
# that generates tapetype entries, but it is slow as hell, use it only
# if you really must and, if you do, make sure you post the data to
# the amanda mailing list, so that others can use what you found out
# by searching the archives.
#
# There's a script by Icarus Sparry <[EMAIL PROTECTED]> that may help
# calculating the size of a tape. Get it from the URL
# http://www.amanda.org/amanda-users/users/Oct-Dec.1995/msg00208.html
#
# 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.
# If you want amanda to print postscript paper tape labels
# add a line after the comment in the tapetype of the form
# lbl-templ "/path/to/postscript/template/label.ps"
# if you want the label to go to a printer other than the default
# for your system, you can also add a line above for a different
# printer. (i usually add that line after the dumpuser specification)
# dumpuser "operator" # the user to run dumps under
# printer "mypostscript" # printer to print paper label on
# here is an example of my definition for an EXB-8500
# define tapetype EXB-8500 {
# ...
# lbl-templ "/usr/local/amanda/config/lbl.exabyte.ps"
# }
define tapetype HP-DAT {
comment "HP JetStore 5000"
length 2000 mbytes # these numbers are not accurate
filemark 100 kbytes # but you get the idea
speed 500 kbytes
}
define tapetype EXB-Mammoth {
comment "Exabyte Mammoth drive on local machine"
length 20000 mbytes
filemark 48 kbytes
speed 3 mbytes
}
# dumptypes
#
# These are referred to by the disklist file. The dumptype specifies
# certain parameters for dumping including:
# auth - authentication scheme to use between server and client.
# Valid values are "bsd" and "krb4". Default: [auth bsd]
# comment - just a comment string
# comprate - set default compression rate. Should be followed by one
or
# two numbers, optionally separated by a comma. The 1st is
# the full compression rate; the 2nd is the incremental rate.
# If the second is omitted, it is assumed equal to the first.
# The numbers represent the amount of the original file the
# compressed file is expected to take up.
# Default: [comprate 0.50, 0.50]
# compress - specify compression of the backed up data. Valid values
are:
# "none" - don't compress the dump output.
# "client best" - compress on the client using the best (and
# probably slowest) algorithm.
# "client fast" - compress on the client using fast algorithm.
# "server best" - compress on the tape host using the best (and
# probably slowest) algorithm.
# "server fast" - compress on the tape host using a fast
# algorithm. This may be useful when a fast
# tape host is backing up slow clients.
# Default: [compress client fast]
# dumpcycle - set the number of days in the dump cycle, ie, set how
often a
# full dump should be performed. Default: from DUMPCYCLE above
# exclude - specify files and directories to be excluded from the
dump.
# Useful with gnutar only; silently ignored by dump and
samba.
# Valid values are:
# "pattern" - a shell glob pattern defining which
files
# to exclude.
# gnutar gets --exclude="pattern"
# list "filename" - a file (on the client!) containing
patterns
# re's (1 per line) defining which
files to
# exclude.
# gnutar gets
--exclude-from="filename"
# Note that the `full pathname' of a file within its
# filesystem starts with `./', because of the way amanda
runs
# gnutar: `tar -C $mountpoint -cf - --lots-of-options .'
(note
# the final dot!) Thus, if you're backing up `/usr'
with a
# diskfile entry like ``host /usr gnutar-root', but you
don't
# want to backup /usr/tmp, your exclude list should
contain
# the pattern `./tmp', as this is relative to the `/usr'
above.
# Please refer to the man-page of gnutar for more
information.
# Default: include all files
# holdingdisk - should the holding disk be used for this dump. Useful
for
# dumping the holding disk itself. Default: [holdingdisk yes]
# ignore - do not back this filesystem up. Useful for sharing a
single
# disklist in several configurations.
# index - keep an index of the files backed up. Default: [index no]
# kencrypt - encrypt the data stream between the client and server.
# Default: [kencrypt no]
# maxdumps - max number of concurrent dumps to run on the client.
# Default: [maxdumps 1]
# priority - priority level of the dump. Valid levels are "low",
"medium"
# or "high". These are really only 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 at least dumped. Default: [priority medium]
# program - specify the dump system to use. Valid values are "DUMP"
and
# "GNUTAR". Default: [program "DUMP"].
# record - record the dump in /etc/dumpdates. Default: [record yes]
# 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.
# starttime - delay the start of the dump? Default: no delay
# strategy - set the dump strategy. Valid strategies are currently:
# "standard" - the standard one.
# "nofull" - do level 1 dumps every time. 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.
# "noinc" - do level 0 dumps every time.
# Unfortunately, this is not currently
# implemented. Use `dumpcycle 0'
# instead.
# "skip" - skip all dumps. Useful for sharing a single
# disklist in several configurations.
# Default: [strategy standard]
#
# Note that you may specify previously defined dumptypes as a shorthand
way
# of defining parameters.
define dumptype global {
comment "Global definitions"
# This is quite useful for setting global parameters, so you don't
have
# to type them everywhere. All dumptype definitions in this sample
file
# do include these definitions, either directly or indirectly.
# There's nothing special about the name `global'; if you create any
# dumptype that does not contain the word `global' or the name of
any
# other dumptype that contains it, these definitions won't apply.
# Note that these definitions may be overridden in other
# dumptypes, if the redefinitions appear *after* the `global'
# dumptype name.
# You may want to use this for globally enabling or disabling
# indexing, recording, etc. Some examples:
# record no
compress none
priority high
# strategy noinc
index yes
program "GNUTAR"
}
define dumptype henko {
comment "local host"
global
# holdingdisk no
# exclude "/workingdisk/workingdisk/*"
exclude list "/usr/local/var/amanda/exclude.henko"
}
define dumptype gretel {
comment "remote gretel"
global
exclude list "/usr/local/var/amanda/exclude.gretel"
}
#define dumptype rapunzel {
# comment "remote rapunzel"
# global
# exclude "./usr/database"
# exclude list "/usr/local/var/amanda/exclude.rapunzel"
#}
define dumptype focus {
comment "remote focus"
global
exclude list "/usr/local/var/amanda/exclude.focus"
# exclude "./usr/database"
}
#define dumptype toaster {
# comment "remote toaster"
# global
# exclude list "/usr/local/var/amanda/exclude.toaster"
#}
# network interfaces
#
# These are referred to by the disklist file. They define the
attributes
# of the network interface that the remote machine is accessed through.
# Notes: - netusage above defines the attributes that are used when the
# disklist entry doesn't specify otherwise.
# - the values below are only samples.
# - specifying an interface does not force the traffic to pass
# through that interface. Your OS routing tables do that.
This
# is just a mechanism to stop Amanda trashing your network.
# Attributes are:
# use - bandwidth above which amanda won't start
# backups using this interface. Note that if
# a single backup will take more than that,
# amanda won't try to make it run slower!
define interface local {
comment "a local disk"
use 1000 kbps
}
define interface le0 {
comment "100 Mbps ethernet"
use 400 kbps
}
# You may include other amanda configuration files, so you can share
# dumptypes, tapetypes and interface definitions among several
# configurations.
# includefile "/usr/local/amanda.conf.main"
