Compression is often a CPU bottleneck, did you check for cpu usage? You
can try to use pigz instead of gzip if you have available core.
How many dump are you doing in parallel? You can try to increase
inparallel, netusage and/or maxdumps.
You can use amplot and amstatus to check amanda performance.
Jean-Louis
On 03/13/2013 10:44 PM, Amit Karpe wrote:
Hi all,
I am using Amanda to take backup weekly & monthly. For monthly backup
which is 2.5 to 2.7TB in size after backup with compression, it take
4-5 days. (Total size is around 6-7 TB, and there 52 entries DLEs,
from 10 different host in network. I am backuping on NAS, where I have
19T total space.)
Off course there are various parameter we have to consider to claim
whether it is slow process or not.
Could you please let me know how should I check and compare whether my
backup process is slow or not ?
Which are main parameter which affect Amanda Performance ?
Which tool I should use to check Amanda Performance ?
Currently I am using following steps:
1. I have started monthly backup.
2. Using bandwidth monitoring tools i.e. ntop, bmon I am checking
Backup Server to NAS bandwidth usage & trafic status.
3. Using iotop I am checking status / speed of io operation.
4. There are other few tools, which may help to understand io, had
disk usage. But as my backup directory is not a local device, (I have
mounted as nfs directory) I can't run hdparm or iostat directly.
5. Monitoring NAS's admin interface for its bandwidth usage.
6. Currently I am checking for some spastics, which help to compare
with my current setup.
Still I can't understand whether I going right way or not !
It will be if you help me here.
--
Regards
Amit Karpe.
http://www.amitkarpe.com/
http://news.karpe.net.in/
