Amanda-Users

Super Slow full dump.

2004-01-30 16:40:58
Subject: Super Slow full dump.
From: Tavis Gustafson <tavis AT hq.dreamhost DOT com>
To: amanda-users AT amanda DOT org
Date: Fri, 30 Jan 2004 13:37:28 -0800 (PST)
I just ran a test dump of a Netapp F760 Filer.  The volume is 200GB total
broken down into "dataglobs".  Each dataglob has its own disklist entry
about (50 or so).
The backup runs over nfs via tar.  Amanda has a 200GB IDE spool disk.
The drive is a Sony AIX-700C (40GB/hr) inside a automatic tape changer.

This backup took 50 hours to complete.  Anyone know of any obvious things
I can do to speed this process up?

Thank, TAvis

--Sample of disklist :

localhost /mnt/netapp/squishy/postal/acetate always-full
localhost /mnt/netapp/squishy/postal/cadelle always-full
localhost /mnt/netapp/squishy/postal/cadence always-full


--Below is amanda.conf :


#
# 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 "vaultapp-squishy"          # your organization name for reports
mailto "root"           # space separated list of operators at your site
dumpuser "backup"       # the user to run dumps under
#
inparallel 4            # maximum dumpers that will run in parallel
netusage  60000         # 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
runspercycle 1
tapecycle 16 tapes      # the number of tapes in rotation

bumpsize 20 MB          # minimum savings (threshold) to bump level 1 -> 2
bumpdays     1          # minimum days at each level
bumpmult     4          # threshold = bumpsize * (level-1)**bumpmult

runtapes     3         # explained in WHATS.NEW
tpchanger "chg-zd-mtx" # the tape-changer glue script, see TAPE.CHANGERS
changerfile "/usr/local/dh/etc/amanda/vaultapp-squishy/changer"
changerdev "/dev/sg1"
#tapedev        "/dev/st0"      # Linux @ tuck, important: norewinding
tapedev "/dev/nst0"     # or use the (no-rewind!) tape device directly

tapetype SDX3-100C              # what kind of tape it is (see tapetypes
below)
labelstr "^ANX.*$"      # label constraint regex: all tapes must match

diskdir "/mnt/stage"            # where the holding disk is
disksize 200000 MB                      # how much space can we use on it
#diskdir "/dumps/amanda/work"   # additionaly holding disks can be specified
#diskdir "/mnt/disk4"
#disksize 1000 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/vaultapp-squishy/curinfo"     # database
filename
logfile  "/var/log/amanda/vaultapp-squishy/log" # log filename

# where the index files live
indexdir "/var/lib/amanda/vaultapp-squishy/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 SDX3-100C {
        comment "produced by tapetype"
        # length 97797 mbytes
        length 96000 mbytes
        filemark 5577 kbytes
        speed 11379 kps
}








<Prev in Thread] Current Thread [Next in Thread>