420GB is not the total amount per night. Something is bogging this down though and I don't know what. I am not using holding disks because the majority of data is being backed up from one set of disks to another on the same machine. This one machine has a set of RAID 10 disks. These disks are backed up by amanda and put onto a set of RAID 5 disks. As far as assigning spindle #s goes I don't quite understand why I would set that. I have inparallel set to 4 and then didn't define maxdumps, so I would assume that not more than 1 dumper would get started on a machine at once. Am I getting this right? Here is my email log from the backup this morning.
STATISTICS:
Total Full Daily
Estimate Time (hrs:min) 7:30
Run Time (hrs:min) 10:35
Dump Time (hrs:min) 2:52 0:29 2:23
Output Size (meg) 12163.2 9094.3 3068.9
Original Size (meg) 29068.4 19177.4 9891.0
Avg Compressed Size (%) 41.8 47.4 31.0 (level:#disks ...)
Filesystems Dumped 3 1 2 (1:1 5:1)
Avg Dump Rate (k/s) 1207.5 5366.4 366.3
Tape Time (hrs:min) 0:17 0:13 0:05
Tape Size (meg) 12163.3 9094.3 3069.0
Tape Used (%) 1.8 1.3 0.4 (level:#disks ...)
Filesystems Taped 3 1 2 (1:1 5:1)
Avg Tp Write Rate (k/s) 11980.6 12287.9 11153.9
\
NOTES:
driver: WARNING: /tmp: not 102400 KB free.
planner: Incremental of venus.:/home bumped to level 5.
planner: Full dump of bda1.:/home specially promoted from 13 days ahead.
taper: tape DailySet111 kb 12455232 fm 3 [OK]
DUMP SUMMARY:
DUMPER STATS TAPER STATS
HOSTNAME DISK L ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
-- -
bda1. /home 0 196376909312576 47.4 28:555366.4 12:3812287.9
bda2. /var/www 1 3210 480 15.0 0:01 364.4 0:0028399.0
venus. /home 5 101251603142176 31.0 142:59 366.3 4:4211152.8
On Mon, 2004-07-19 at 15:20, Frank Smith wrote:
--On Monday, July 19, 2004 14:07:40 -0700 Kris Vassallo [EMAIL PROTECTED] wrote:
I am looking for some assistance in tweaking the bumpsize, bumpdays,
and bumpmult items in amanda.conf. I am backing up 420GB + worth of home
directories to hard disks every night and the backup is taking about 11
hours. I just changed the backup of one 400GB home drive from client
compress best to client compress fast, which did seem to shave a bit of
time off the backup. The disks that are being backed up are on the same
RAID controller as the backup disks.
I really need to make the backup take a lot less time because the
network crawls when the developers come in to work in the morning
because the home directory server is blasting away with the backup. So,
with a filesystem this large, what would be some good settings for the
bump options. Also, are there any other things I can do to get this
backup done any faster without turning off disk compression all
together?
Are you actually writing 420GB per night, or is that just the total
amount to be backed up? If most of your data isn't changing daily
then breaking up your DLEs to not have a 400GB chunk could spread
the level 0s across more nights and shorten your nightly backup time.
Are you sure its the compression using up most of the time? You
probably need to add spindle numbers to your disklist to serialize
the accesses to the DLEs that share common disks. Using a holding
disk not on the same controller would speed things up also.
If your DLS and file backups share the same disks and not just
the same controller then the disks will waste quite a bit of time
seeking back and forth. You might also want to do some performance
testing on your RAID controller, perhaps it is the bottleneck as
the model of controller (and the RAID level) can have a big impact
on throughput.
Perhas posting your daily report and more details of the physical
layout would give us a better idea of where to start on suggestions
for improving your backup times.
Frank
