--On Wednesday, February 05, 2003 18:20:42 -0500 Geoff Gowey <ggowey AT rxhope DOT
com> wrote:
Not sure if I have this config correctly and would be extremely thankful if
anyone could point my in the right direction. What I need to do is back up
multiple boxes at once. The setup is what I outlined in my last post:
Linux (2.4.20 kernel)
ADIC Scalar 100 - 4x Quantum DLT7000 Drives
- the picker has a barcode scanner
120 DLT IV's
- all have bar codes
Adaptec 2944UW controller
I think chg-scsi is most appropriate due to the fact I want to be using more
than one drive at once. Also, the unit has a reader and all cartridges are
tagged making what I think is an ideal application for chg-scsi. Thanks in
advance.
Geoff
Amanda only uses one drive (unless you use the RAIT device driver to stripe or
mirror
the data, which doesn't seem to be the case in your config). Otherwise you
would need
multiple configs running simultaneously, each with its own config specifying
its own
drive(s). There was recently a thread on the list on how do that, check the
archives.
Other comments on your amanda config file:
org "DailySet1" # your organization name for reports
mailto "bin" # space separated list of operators at your site
dumpuser "bin" # the user to run dumps under
inparallel 4 # maximum dumpers that will run in parallel (max 63)
# this maximum can be increased at compile-time,
# modifying MAX_DUMPERS in server-src/driverio.h
netusage 100000 mbps # maximum net bandwidth for Amanda, in KB per sec
dumpcycle 4 weeks # the number of days in the normal dump cycle
Are you sure you want this? It means that each disklist entry (DLE) will only
be gauranteed a full backup every 4 weeks. IT also means that if you need to
restore it you have to use up to 20 tapes to do it (since your running 5
days/week)
runspercycle 20 # the number of amdump runs in dumpcycle days
# (4 weeks * 5 amdump runs per week -- just weekdays)
tapecycle 120 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
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.
Might be too small if you have large filesystems with many small files
# 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.
dtimeout 1800 # number of idle seconds before a dump is aborted.
ctimeout 30 # maximum number of seconds that amcheck waits
# for each client host
tapebufs 20
# A positive integer telling taper how many 32k buffers to allocate.
# WARNING! If this is set too high, taper will not be able to allocate
# the memory and will die. The default is 20 (640k).
runtapes 1 # number of tapes to be used in a single run of amdump
Only one tape will be used each night. Will it fit? If not, set it to the
maximum
number of tapes you want to use each night (6 is the most you could use with
your
current config (120 tapes/20 runs, but 4 would allow for occasional problems).
tpchanger "chg-scsi" # the tape-changer glue script
tapedev "0" # the no-rewind tape device to be used
changerfile "/usr/local/etc/amanda/DailySet1/chg-scsi.conf"
tapetype DLT7000-IV # what kind of tape it is (see tapetypes below)
labelstr "^DailySet1[0-9][0-9]*$" # label constraint regex: all tapes must
match
holdingdisk hd1 {
comment "main holding disk"
directory "/dumps/amanda" # where the holding disk is
use 290 Mb # how much space can we use on it
# a non-positive value means:
# use all space but that value
If your DLEs are larger than this number then it won't do you any good,
Amanda only writes chunks to the holding disk if they'll all fit, since it
doesn't start writing a DLE to tape until the last chunk is written to disk.
If your DLEs are larger than the holding disk they will get written directly
to tape, which is much slower if your client and network can't stream the
data as fast as your drive needs it (causing it to repeated stop and reposition
itself, wasting time and tape).
chunksize 1Gb # size of chunk if you want big dump to be
# dumped on multiple files on holding disks
# N Kb/Mb/Gb split images in chunks of size N
# The maximum value should be
# (MAX_FILE_SIZE - 1Mb)
# 0 same as INT_MAX bytes
}
# 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 defaults to 0, so you may want to increase it if some of your DLEs
will fit in the 290M you specified above.
Frank
# This means save at least 30% of the holding disk space for degraded
# mode backups.
infofile "/usr/adm/amanda/DailySet1/curinfo" # database DIRECTORY
logdir "/usr/adm/amanda/DailySet1" # log directory
indexdir "/usr/adm/amanda/DailySet1/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 tapetype QIC-60 {
comment "Archive Viper"
length 60 mbytes
filemark 100 kbytes # don't know a better value
speed 100 kbytes # dito
}
define tapetype DEC-DLT2000 {
comment "DEC Differential Digital Linear Tape 2000"
length 15000 mbytes
filemark 8 kbytes
speed 1250 kbytes
}
# goluboff AT butch.Colorado DOT EDU
# in amanda-users (Thu Dec 26 01:55:38 MEZ 1996)
define tapetype DLT {
comment "DLT tape drives"
length 20000 mbytes # 20 Gig tapes
filemark 2000 kbytes # I don't know what this means
speed 1536 kbytes # 1.5 Mb/s
}
define tapetype SURESTORE-1200E {
comment "HP AutoLoader"
length 3900 mbytes
filemark 100 kbytes
speed 500 kbytes
}
define tapetype EXB-8500 {
comment "Exabyte EXB-8500 drive on decent machine"
length 4200 mbytes
filemark 48 kbytes
speed 474 kbytes
}
define tapetype EXB-8200 {
comment "Exabyte EXB-8200 drive on decent machine"
length 2200 mbytes
filemark 2130 kbytes
speed 240 kbytes
}
define tapetype HP-DAT {
comment "DAT tape drives"
# data provided by Rob Browning <rlb AT cs.utexas DOT edu>
length 1930 mbytes
filemark 111 kbytes
speed 468 kbytes
}
define tapetype DAT {
comment "DAT tape drives"
length 1000 mbytes # these numbers are not accurate
filemark 100 kbytes # but you get the idea
speed 100 kbytes
}
define tapetype MIMSY-MEGATAPE {
comment "Megatape (Exabyte based) drive through Emulex on Vax 8600"
length 2200 mbytes
filemark 2130 kbytes
speed 170 kbytes # limited by the Emulex bus interface, ugh
}
define tapetype DLT7000-IV {
comment "DLT7000 with DLTtape IV uncompressed"
length 35000 mbytes
filemark 8 kbytes
speed 5000 kbytes
}
# dumptypes
define dumptype global {
comment "Global definitions"
}
define dumptype always-full {
global
comment "Full dump of this filesystem always"
compress none
priority high
dumpcycle 0
}
define dumptype root-tar {
global
program "GNUTAR"
comment "root partitions dumped with tar"
compress none
index
exclude list "/usr/local/lib/amanda/exclude.gtar"
priority low
}
define dumptype user-tar {
root-tar
comment "user partitions dumped with tar"
priority medium
}
define dumptype high-tar {
root-tar
comment "partitions dumped with tar"
priority high
}
define dumptype comp-root-tar {
root-tar
comment "Root partitions with compression"
compress client fast
}
define dumptype comp-user-tar {
user-tar
compress client fast
}
define dumptype holding-disk {
global
comment "The master-host holding disk itself"
holdingdisk no # do not use the holding disk
priority medium
}
define dumptype comp-user {
global
comment "Non-root partitions on reasonably fast machines"
compress client fast
priority medium
}
define dumptype nocomp-user {
comp-user
comment "Non-root partitions on slow machines"
compress none
}
define dumptype comp-root {
global
comment "Root partitions with compression"
compress client fast
priority low
}
define dumptype nocomp-root {
comp-root
comment "Root partitions without compression"
compress none
}
define dumptype comp-high {
global
comment "very important partitions on fast machines"
compress client best
priority high
}
define dumptype nocomp-high {
comp-high
comment "very important partitions on slow machines"
compress none
}
define dumptype nocomp-test {
global
comment "test dump without compression, no /etc/dumpdates recording"
compress none
record no
priority medium
}
define dumptype comp-test {
nocomp-test
comment "test dump with compression, no /etc/dumpdates recording"
compress client fast
}
# 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 "10 Mbps ethernet"
use 400 kbps
}
--
Frank Smith fsmith AT hoovers DOT
com
Systems Administrator Voice: 512-374-4673
Hoover's Online Fax: 512-374-4501
| 