Hi,
My amanda configurations is:
- DailySetPS - Fraiday weekly to tape (Full dump PS and servers)
00 0 * * 5 root /etc/amanda/amdumpPS.cron
- DailySetL - Workday nightly (5 days) to holding disk (incremental dump
PS and servers with Mandrake Linux PC)
30 1 * * 0-4 root /etc/amanda/amdump00.cron
- DailySetTP - Monday weekly to tape (Full dump notebooks)
/etc/amanda/amdumpTP.cron
- DailySetY - Thuesday weekly to tape (Full dump boss notebooks)
00 10 * * 0-4 root /etc/amanda/amdump10.cron
- DailySetE - Wednesday nightly to tape (Full dump Mandrake Linux PC)
00 20 * * 3 root /etc/amanda/amdumpPE.cron
- DailySet2 - Workday (3 times X 5 days) to holding disk
(12:00,15:00,18:00 incremental dump notebooks)
00 12 * * 0-4 root /etc/amanda/amdump12.cron
00 15 * * 0-4 root /etc/amanda/amdump15.cron
00 18 * * 0-3 root /etc/amanda/amdump18.cron
- DailySetY - Workday (1 time X 5 days) to holding disk (10:00
incremental dump boss notebook)
00 10 * * 0-4 root /etc/amanda/amdump10.cron
- DailySetF - Workday nightly (5 days) flush from holding disk to tape
00 20 * * 0-4 root /etc/amanda/amflush.cron
Attached: 1. /etc/amanda/DailySet2/amanda.conf
2. /home/amanda/amd/ logfile
Jon LaBadie wrote:
On Thu, Jun 23, 2005 at 02:10:55PM +0300, Leonid Shulov wrote:
Hi,
I upgraded my amanda to 2.4.5 version, and after that sometimes amanda
do backup with lev0 without any tape to holding disk. This broke all my
work order. Before I do full PC dump once a week at Saturday nightly,
incremental PC dump nightly in working days to holding disk. Daily
incremental Notebook dump I do to holding disk.
And now I don't know what to do, amanda dumping salad of levels: 0,1....n
The behavior you describe, a mixture of levels, is the 'normal'
behavior for amanda. That amanda was behaving differently before
suggests you had some aspect of your configuration set to
force amanda to your desireed scheme. I'm surprised that a
version change in the amanda executables would change its
behavior with respect to an existing configuration.
Let us know how your configuration tries to force amanda into
the non-standard behavior you want. Maybe we will be able to
notice something that is now apparent from what your posted.
#
# 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 /etc/amanda/csd/amanda.conf.
#
org "DailySet2" # your organization name for reports
mailto "root" # space separated list of operators at your
siteDailySet1
dumpuser "backup" # the user to run dumps under
inparallel 4 # maximum dumpers that will run in parallel
netusage 1000 Kbps # maximum net bandwidth for Amanda, in KB per sec
dumpcycle 7 days # the number of days in the normal dump cycle
runspercycle 15 # the number of amdump runs in dumpcycle days
tapecycle 17 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
### ### ###
# WANING: 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 300 # number of 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 rewaind tape device to be use
#rawtapedev "/dev/st0" # the raw device to be used (ftape only)
#changerfile "/var/lib/amanda/DailySet1/changer"
#changerfile "/var/lib/amanda/DailySet1/changer-status"
#changerfile "/etc/amanda/DailySet1/changer.conf"
#changerdev "/dev/null"
tapetype VXA-2 # what kind of tape it is (see tapetypes below)
labelstr "^DailySet1[0-9][0-9]*$" # label constraint regex: all tapes
must match
holdingdisk Raid {
comment "main holding disk"
directory "/home/amanda/tmp" # where the holding disk is
use -20 Gb #how much space can we use on it
# a negative value mean:
# use all space except that value
chunksize 2 Gb # 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
# -N Kb/Mb/Gb dont split, dump larger
# filesystems directly to tape
# (example: -2 Gb)
}
# 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 30 # 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. Some sites use /usr/local/var and some /usr/adm.
# Create an amanda directory under there. You need a separate infofile and
# logdir for each configuration, so create subdirectories for each conf and
# put the files there. Specify the locations below.
infofile "/home/amanda/adm/curinfo" # database filename
logdir "/home/amanda/adm" # log directory
indexdir "/home/amanda/adm/index" # index directory
tapelist "/home/amanda/adm/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.
# 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 VXA-2 {
comment "Exabyte VXA-2 drive on asraid01"
length 160000 mbytes
filemark 2300 kbytes
speed 12000 kbytes
}
# 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 yes #- 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 yes #- 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]_dev_hd1
# 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:
program "GNUTAR"
index yes
# record no
}
define dumptype TP-user {
global
comment "Full dump of TP-users"
priority low
dumpcycle 1 weeks
index yes
compress server best
exclude append "./yuli/tmp"
}
define dumptype TP-vadim {
global
comment "Full dump of TP-vadim"
priority low
dumpcycle 1 weeks
index yes
compress server best
exclude append "./daniel"
exclude append "./tftpboot"
exclude append "./vadim/.mozilla"
exclude append "./vadim/tftpboot"
exclude append "./vadim/tmp"
exclude append "./vadim/downloads"
exclude append "./vadim/misc"
exclude append "./vadim/evolution"
exclude append "./vadim/host"
exclude append "./vadim/games"
}
START driver date 20050626
DISK planner astp0002 /dev/hda10
DISK planner astp0002 /dev/hda5
DISK planner astp0002 /dev/hda11
DISK planner astp0002 /dev/hda12
DISK planner astp0002 /dev/hda7
DISK planner astp0002 /dev/hda8
DISK planner astp0002 /dev/hda9
DISK planner astp0003 /
DISK planner astp0003 /var
DISK planner astp0003 /opt
DISK planner astp0003 /usr
DISK planner astp0003 /usr/local
DISK planner astp0003 /home
START planner date 20050626
STATS driver startup time 0.047
ERROR taper no-tape [tape_rdlabel: tape open: /dev/nst0: Input/output error]
INFO planner Full dump of astp0002:/dev/hda11 promoted from 4 days ahead.
INFO planner Full dump of astp0003:/var promoted from 4 days ahead.
INFO planner Full dump of astp0003:/ promoted from 4 days ahead.
INFO planner Full dump of astp0002:/dev/hda10 promoted from 4 days ahead.
INFO planner Full dump of astp0002:/dev/hda7 promoted from 4 days ahead.
FINISH planner date 20050626 time 1755.888
SUCCESS dumper astp0002 /dev/hda5 20050626 1 [sec 0.498 kb 0 kps 0.0 orig-kb 10]
SUCCESS dumper astp0003 /usr/local 20050626 1 [sec 6.864 kb 69 kps 10.1 orig-kb
1130]
SUCCESS dumper astp0003 /opt 20050626 1 [sec 4.602 kb 69 kps 15.0 orig-kb 730]
SUCCESS dumper astp0002 /dev/hda8 20050626 1 [sec 9.560 kb 29 kps 3.0 orig-kb
510]
SUCCESS dumper astp0003 / 20050626 0 [sec 119.412 kb 99203 kps 830.8 orig-kb
200590]
SUCCESS dumper astp0003 /var 20050626 0 [sec 133.904 kb 75493 kps 563.8 orig-kb
266830]
SUCCESS dumper astp0002 /dev/hda9 20050626 1 [sec 296.935 kb 16632 kps 56.0
orig-kb 45480]
SUCCESS dumper astp0002 /dev/hda10 20050626 0 [sec 141.279 kb 60249 kps 426.5
orig-kb 192780]
SUCCESS dumper astp0003 /usr 20050626 1 [sec 226.607 kb 612 kps 2.7 orig-kb
9000]
SUCCESS dumper astp0002 /dev/hda11 20050626 0 [sec 245.382 kb 186374 kps 759.5
orig-kb 426000]
SUCCESS dumper astp0002 /dev/hda7 20050626 0 [sec 365.292 kb 324530 kps 888.4
orig-kb 889140]
SUCCESS dumper astp0002 /dev/hda12 20050626 2 [sec 398.007 kb 6682 kps 16.8
orig-kb 36310]
SUCCESS dumper astp0003 /home 20050626 4 [sec 650.254 kb 498940 kps 767.3
orig-kb 878600]
FINISH driver date 20050626 time 3487.963
|
