Amanda-Users

performance of backup process

2008-11-17 03:09:23
Subject: performance of backup process
From: Mister Olli <mister.olli AT googlemail DOT com>
To: AMANDA users <amanda-users AT amanda DOT org>
Date: Mon, 17 Nov 2008 09:02:35 +0100
hi list,

I'm running amanda for some time now, and it really rocks. It's a
totally stable and easy to use backup solution with high reliability.
great work..

since my data volume is increasing, I'm wondering how to speed up the
backup process.
My network includes about 20 clients (mostly *NIX) machines, and one
amanda server which tapes to hard-drives.
I'm wondering how to tune amanda in this scenario? are there any general
hints and tips (beside tuning HD perfomance ;-))

right now I'm looking at the 'amstatus' of my daily backup job, which
gives me the following output
====================================================
Using /var/log/amanda/daily/amdump from Mon Nov 17 08:31:51 CET 2008

172.31.2.10:/daten/business 0    11085m dumping     4380m ( 39.52%)
(8:38:25)
172.31.2.10:/daten/company  1       16m finished (8:38:25)
172.31.2.10:/daten/intern   0    24001m wait for dumping
172.31.2.10:/daten/software 1   242107m wait for dumping
172.31.6.10:/daten/blub     0     1623m finished (8:40:33)
172.31.6.10:/daten/business 1        0m finished (8:37:14)
172.31.6.10:/daten/doku     0     5413m finished (8:45:19)

SUMMARY          part      real  estimated
                           size       size
partition       :   7
estimated       :   7               284248m
flush           :   0         0m
failed          :   0                    0m           (  0.00%)
wait for dumping:   2               266108m           ( 93.62%)
dumping to tape :   0                    0m           (  0.00%)
dumping         :   1      4380m     11085m ( 39.52%) (  1.54%)
dumped          :   4      7054m      7054m (100.00%) (  2.48%)
wait for writing:   0         0m         0m (  0.00%) (  0.00%)
wait to flush   :   0         0m         0m (100.00%) (  0.00%)
writing to tape :   0         0m         0m (  0.00%) (  0.00%)
failed to tape  :   0         0m         0m (  0.00%) (  0.00%)
taped           :   4      7054m      7054m (100.00%) (  2.48%)
  tape 1        :   4      7054m      7054m (  3.44%) ERNW-daily02
9 dumpers idle  : client-constrained
taper writing, tapeq: 0
network free kps:    248976
holding space   :    408372m ( 96.12%)
chunker0 busy   :  0:00:00  (  0.00%)
chunker1 busy   :  0:00:00  (  0.00%)
 dumper0 busy   :  0:05:25  ( 40.25%)
 dumper1 busy   :  0:08:04  ( 60.00%)
   taper busy   :  0:04:12  ( 31.21%)
 0 dumpers busy :  0:05:23  ( 40.04%)            not-idle:  0:05:23
(100.00%)
 1 dumper busy  :  0:03:36  ( 26.79%)  client-constrained:  0:02:25
( 67.29%)
                                               start-wait:  0:01:10
( 32.71%)
 2 dumpers busy :  0:04:27  ( 33.15%)  client-constrained:  0:04:27
(100.00%)
====================================================
from my understanding amanda is dumping (writing to holding disk) and
taping (writing from holding disk to virtual tapes) at the same time.
Doesn't this reduce speed on the dumper caused by the head-seeks on the
holding disc? Is there a way to prevent this scenario (as long as the
holding disc is big enough for all data that belongs to the job)?

greetz
olli


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