Here is a updated amanda.conf file that is having the same problem.
[root@stanger root]# more /etc/amanda/DailySet1/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 /etc/amanda/csd/amanda.conf.
#
org "DailySet1" # your organization name for reports
mailto "admins AT interlinc DOT net" # space separated list of operators at
your
site
dumpuser "amanda" # the user to run dumps under
inparallel 4 # maximum dumpers that will run in parallel
netusage 600 Kbps # maximum net bandwidth for Amanda, in KB per sec
#dumpcycle 1 weeks # AMANDA_WEBMIN
runspercycle 1 # AMANDA_WEBMIN
tapecycle 7 tapes # AMANDA_WEBMIN
# 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 # AMANDA_WEBMIN
bumpdays 1 # AMANDA_WEBMIN
bumpmult 4 # AMANDA_WEBMIN
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 # AMANDA_WEBMIN
tpchanger "chg-zd-mtx" # the tape-changer glue script
tapedev "/dev/nst0" # the no-rewind tape device to be used
#rawtapedev "/dev/null" # 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"
changerdev "/dev/sg1"
tapetype unknown-tapetype # AMANDA_WEBMIN
labelstr "^DailySet1[0-9][0-9]*$" # AMANDA_WEBMIN
# 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 "/var/tmp" # where the holding disk is
use 100 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)
}
#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 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 "/var/lib/amanda/DailySet1/curinfo" # database filename
logdir "/var/lib/amanda/DailySet1" # log directory
indexdir "/var/lib/amanda/DailySet1/index" # index directory
#tapelist "/var/lib/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.
# 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"
# }
# goluboff AT butch.Colorado DOT EDU
# in amanda-users (Thu Dec 26 01:55:38 MEZ 1996)
define tapetype unknown-tapetype {
comment "just produced by tapetype program"
length 40000 mbytes
filemark 10 kbytes
speed 1291 kps
}
# 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.
# 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:
# index yes
# record no
define dumptype always-full {
comment "Full dump of this filesystem always"
index yes
compress none
priority high
dumpcycle 1 days # AMANDA_WEBMIN
}
# 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 eth0 {
comment "10 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"
[root@stanger root]#
> From: Jon LaBadie <jon AT jgcomp DOT com>
> Reply-To: <amanda-users AT amanda DOT org>
> Date: Wed, 22 Sep 2004 18:15:34 -0400
> To: <amanda-users AT amanda DOT org>
> Subject: Re: Amdump keeps running
>
> On Wed, Sep 22, 2004 at 04:37:28PM -0500, Jason Miller wrote:
>> Hello all, I am new to the amanda world and have setup a redhat 9.0 box
>> with Amanda from PRM. I have a Dell Powervault 122T. When I run a amdump it
>> estimates the size correctly, which is 23Gigs it hits 100% then keeps going
>> instead of backing it up to the tape. Anyone have any ideas what could be
>> causing the problem? I am pasting my configs for your review. As I said I am
>> green on this product and I am sure I missed something along the way but am
>> way too stupid to figure it out.
>>
>>
>> [root@stanger root]# more /proc/scsi/scsi
>> Attached devices:
>> Host: scsi1 Channel: 00 Id: 01 Lun: 00
>> Vendor: BNCHMARK Model: VS640 Rev: 5639
>> Type: Sequential-Access ANSI SCSI revision: 02
>> Host: scsi1 Channel: 00 Id: 01 Lun: 01
>> Vendor: BNCHMARK Model: VS640 Rev: 5639
>> Type: Medium Changer ANSI SCSI revision: 02
>
> VS640 sounds like 8 tapes of VS80 type, about 40GB uncompressed.
>
>> tapetype pv120T-dds4 # AMANDA_WEBMIN
>
> dds4 sounds like a DAT 4, about 20GB uncompressed
>
>> # goluboff AT butch.Colorado DOT EDU
>> # in amanda-users (Thu Dec 26 01:55:38 MEZ 1996)
>> define tapetype pv120T-dds4 {
>> comment "Dell PowerVault 122T DLT 8 tape autoloader"
>
> Well, now is it VS80, DDS4, or DLT8???
>
>
>> length 80000 mbytes
>>
>
> In any event, I don't think the actual capacity, uncompressed, is 80GB.
>>
>>
>> [root@stanger root]# more /etc/amanda/DailySet1/disklist
>> stanger.interlinc.net /dev/hda2 always-full -1 local
>> [root@stanger root]#
>>
>> [root@stanger root]# more /var/lib/amanda/DailySet1/log.20040922.5
>> DISK planner stanger.interlinc.net /dev/hda2
>> START planner date 20040922
>> INFO planner Adding new disk stanger.interlinc.net:/dev/hda2.
>> START driver date 20040922
>> START taper datestamp 20040922 label DailySet13 tape 0
>> FINISH planner date 20040922
>> STATS driver startup time 70.775
>> INFO taper tape DailySet13 kb 448 fm 1 writing file: Input/output error
>
> It wrote 1 file (fm 1) and about 448KB "successfully". That file was the
> amanda tape header, not a backup dump. Then it hit an error.
>
>> FAIL taper stanger.interlinc.net /dev/hda2 20040922 0 [out of tape]
>> ERROR taper no-tape [[writing file: Input/output error]]
>
> It says "out of tape", but consider other possibilities.
> Amanda gets an "error" from the system that often means one of
> several possibilities. Amanda then lists a likely reason.
>
> --
> Jon H. LaBadie jon AT jgcomp DOT com
> JG Computing
> 4455 Province Line Road (609) 252-0159
> Princeton, NJ 08540-4322 (609) 683-7220 (fax)
|
