Re: Amdump takes forever
Joshua Baker-LePain wrote: > > On Wed, 11 Jul 2001 at 10:44am, Gary Algier wrote > > > I have tried to read the amdump log, but I can't decode it. Are there > > any tools to help me figure out where the time is being used? > > 'man amstatus' Just what I needed! I missed that one. I guess somebody added it while I was not looking ;-). It shows: --- Using /var/amanda/Weekly/amdump from Fri Jul 6 19:45:00 EDT 2001 abel:/ 0 282225k wait for dumping abel:/home2 0 584393k wait for dumping abel:/home3 0 508214k wait for dumping abel:/home4 0 563139k wait for dumping angelica:/ 09341k wait for dumping angelica:/export/home0 166745k wait for dumping angelica:/opt0 28550k wait for dumping angelica:/usr0 72708k wait for dumping angelica:/usr/openwin0 85132k wait for dumping angelica:/var0 65571k wait for dumping bond:/ 0 15136k wait for dumping bond:/export/home0 1025601k wait for dumping bond:/usr0 652433k wait for dumping bond:/var0 15278k wait for dumping bruckner:/ 02223k wait for dumping bruckner:/home 0 318820k wait for dumping bruckner:/home1 0 499938k wait for dumping bruckner:/home2 0 839959k wait for dumping bruckner:/usr0 242340k wait for dumping bruckner:/var0 680k wait for dumping burn:/ 0 15132k wait for dumping burn:/usr0 363997k wait for dumping burn:/var01242k wait for dumping camelot:/0 304102k wait for dumping camelot:/home0 2263810k wait for dumping chuckie:/0 32320k finished (22:17:36) chuckie:/export/homea0 936672k finished (21:00:45) chuckie:/opt 0 233792k finished (22:16:46) chuckie:/usr 0 553792k finished (22:08:42) chuckie:/var 0 796096k finished (21:27:14) chuckie:/var/mail0 646752k finished (21:48:25) delilah:/0 340621k wait for dumping delilah:/home0 671364k wait for dumping delilah:/home1 0 995859k wait for dumping delilah:/home2 0 1445041k wait for dumping delilah:/home3 0 1745416k wait for dumping delilah:/home4 0 1271751k wait for dumping delilah:/home5 0 1043010k wait for dumping delilah:/home6 0 102k wait for dumping delilah:/home7 0 1227327k wait for dumping delilah:/home8 0 1481872k wait for dumping delilah:/home9 0 32k finished (20:25:37) delilah:/homea 0 3445192k wait for dumping delilah:/homeb 0 2637984k wait for dumping delilah:/homec 0 3688052k wait for dumping delilah:/homed 0 2737345k wait for dumping delilah:/homee 0 2585379k wait for dumping delilah:/opt 0 214049k wait for dumping dil:/0 10671k wait for dumping dil:/export 0 10463k wait for dumping dil:/export/homea0 183504k wait for dumping dil:/export/homeb0 519287k wait for dumping dil:/export/homec0 53k wait for dumping dil:/export/homed0 2620430k wait for dumping dil:/opt 0 254696k wait for dumping dil:/usr 0 484784k wait for dumping dil:/usr/news04694k wait for dumping dil:/usr/news/db 03558k wait for dumping dil:/var 0 60297k wait for dumping freeport:/ 08202k wait for dumping freeport:/export/home0 89100k wait for dumping freeport:/export/homea 0 1720854k wait for dumping freeport:/opt0 215813k wait for dumping freeport:/usr0 451879k wait for dumping freeport:/var0 44232k wait
Re: Amdump takes forever
On Wed, 11 Jul 2001 at 10:44am, Gary Algier wrote > I have tried to read the amdump log, but I can't decode it. Are there > any tools to help me figure out where the time is being used? 'man amstatus' > I can supply configs and logs upon request, but a little info may be helpful: Are you using software compression on slow clients? Are you using server software compression for several clients? Either of those could slow you down mightily. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Amdump takes forever
My amdump is suddenly running for days. I have a special configuration named "Weekly" that does a level 0 dump of all file systems (with no record) that I have been running every Friday night. This always took until some time on Sunday, but lately it has carried over to Wednesday or even Thursday. Yes, I have added more file systems to dump, but how do I figure out why adding 5% to the work to be done makes it run for 100% longer? I have tried to read the amdump log, but I can't decode it. Are there any tools to help me figure out where the time is being used? Also, how do I "tune" this thing? Should I allow more parallel dumps? Or is that self defeating? I have been a happy user for several years, but I am now getting heat from my users who can't get files restored because the system is too busy doing backups. I can supply configs and logs upon request, but a little info may be helpful: Server: Amanda 2.4.2 on Solaris 8 with 52Gbyte holding disk Tapes: DLT7000 on an Exabyte 230D usually uses 5 tapes / run Clients: 182 file system on 25 hosts with amanda 2.4.1p1 or 2.4.2 with Solaris, Unixware, Sinix, HPUX, AIX, FreeBSD Can someone please help me make this run faster? -- Gary Algier, WB2FWZ [EMAIL PROTECTED] +1 856 787 2758 Ulticom Inc., 1020 Briggs Rd, Mt. Laurel, NJ 08054 Fax:+1 856 866 2033 A self-addressed envelope would be addressed "envelope."
