Hello,

I am using amanda 2.4.4 and the amanda host (running RedHat 9) has a gigabit connection to the network. Yet it seems to utilize only a fraction of the available bandwidth. How do I force it to run at 100% capacity? Here are the statistics from my last backup and below you can see my amanda.conf file. Thanks in advance.

Ashwin Bijur.

STATISTICS:
                         Total       Full      Daily
                       --------   --------   --------
Estimate Time (hrs:min)    2:16
Run Time (hrs:min)         8:58
Dump Time (hrs:min)        3:54       0:01       3:53
Output Size (meg)       53243.0       56.2    53186.7
Original Size (meg)     53243.0       56.2    53186.7
Avg Compressed Size (%)     --         --         --    (level:#disks ...)
Filesystems Dumped           29          4         25   (1:16 2:3 3:3 4:1 5:2)
Avg Dump Rate (k/s)      3881.6     1484.3     3888.2

Tape Time (hrs:min)        1:17       0:00       1:17
Tape Size (meg)         53243.5       56.3    53187.2
Tape Used (%)              62.7        0.1       62.6   (level:#disks ...)
Filesystems Taped            29          4         25   (1:16 2:3 3:3 4:1 5:2)
Avg Tp Write Rate (k/s) 11842.3     6114.8    11854.0



Amanda.conf:

org "Monthly"           # your organization name for reports
mailto "amanda"  # space separated list of operators at your site
dumpuser "amanda"       # the user to run dumps under

inparallel 10 # maximum dumpers that will run in parallel
netusage 100000000 Kbps # maximum net bandwidth for Amanda, in KB per sec


dumpcycle 4 days # the number of days in the normal dump cycle
runspercycle 4 # the number of amdump runs in dumpcycle days
# (4 weeks * 5 amdump runs per week -- just weekdays)
tapecycle 10 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 600 # number of seconds per filesystem for estimates.
#etimeout -600 # total number of seconds for estimates.
runtapes 1 # number of tapes to be used in a single run of amdump
tpchanger "/usr/local/etc/libexec/chg-scsi"
tapedev "0"
rawtapedev "/dev/null" # the raw device to be used (ftape only)
changerfile "/usr/local/etc/amanda/Monthly/chg-scsi.conf"
changerdev "/dev/sg0"


tapetype AME_225_SmartClean # what kind of tape it is (see tapetypes below)
labelstr "^Monthly_.*$" # label constraint regex: all tapes must match
holdingdisk hd1 {
comment "main holding disk"
directory "/dump" # where the holding disk is
use 30000 Mb # how much space can we use on it
#use 290 Mb # 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 10define tapetype AME_225_SmartClean {
comment "just produced by tapetype program"
length 90000 mbytes
filemark 1245 kbytes
speed 11051 kbytes Mb
}


define interface local {
   comment "a local disk"
   use 100 kbps
}

define interface eth0 {
   comment "100 Mbps ethernet"
   use 100 kbps
}

define interface eth1 {
   comment "100 Mbps ethernet"
   use 10000 kbps
}






Reply via email to