Priorities ?
I have a bunch of disks Im amanda-dumping 4 18G disks, a couple od smaller disks and a 420G RAID5 array Now obviously even a level 3 dump of the 420G dsk array is going to take longer than a 0 dump of the smalles disks. Therefore, I'd like ot tell amanda to start work on the 420G disk array first. So I gave the 420G disk a priority of high, and all the other disks a priority of medium. This does not work. I then tried making the disk the first entry in the disklist, didn't work either. So my question is: 1) How does amanda decide which disks to dump first ? 2) How can I influence this ? (apart from rewriting planner.c) Gerhard, @jasongeo.com == The Acoustic Motorbiker == -- __O Some say the end is near. =`\, Some say we'll see armageddon soon (=)/(=) I certainly hope we will I could use a vacation
Questions and Answers and Thanks
Hmm,
Favor #1: can the reply to adress on the digests be set to @amanda.org ;)
* [EMAIL PROTECTED] [EMAIL PROTECTED] (Fri, Jan 19, 2001 at 06:34:02AM
-)
First off, thanks to all who answered my priorities question. ;)
Second.
I noticed when looking through the logs that the *dumper* performance is
around the 1Kps (or less) on my system ,
whereas the *taper* gets a performance of about 7 Kps.
So apparently it's not the speedn of my tapedrive that's the bottleneck,
but soemthing within amanda.
I have now turned compression off and im hoping this will imporve matters.
Are there any other ways to tweak amanda.conf to improve dumper performance
(I've set the bandwith parameters to large values since it's on local disks
and I've specified local in my disklist.
define interface local {
comment "a local disk"
use 40 Mbps
}
define interface le0 {
comment "100 Mbps ethernet"
use 4000 kbps
}
Also, from yestersdays digest
lsof:
We tried to get lsof installed on our solaris box 2 months ago but it
failed to run after the install - we got a 32/64 bit error message.
I assume you then contacted the author (who happens to be my boss) and
he got it fixed for you, right? That program runs on bajillions of OS's
and versions. It would be truly amazing if it does not work at your site.
I have lsof running on Sol 2.6 7 and 8 and it rules,
now if only your boss would decide to port it to Irix 6.5 .
One of my biggest frustrations with Irix .. I cannot get lsof to compile
and work on it ;) )
Message: 22
Date: Fri, 19 Jan 2001 11:20:44 +1100 (EST)
From: Ben Elliston [EMAIL PROTECTED]
Subject: HP-DAT.ps
I want to use this template for labels. I just tried printing the template
(through Ghostscript) and get an empty PCL output file. Is there something
weird with this PostScript file that I should know about?
yeah,
it's not a full postscript file, but it's part of it (the beginning)
the rest will be attached by amanda when it runs amreport.
Most notably, there is now (showpage) at the end which means it will not
work on all PS devices.
(showpage) is what tells a PS device to actually display what it has built
sofar.
Ghostscript immediately displays (at least in X11 mode) what it gets, hence
the differences.
If you wanna print it, use amreport .
On a related note, I managed to hack some logos in the postscript label
templates (well most of the code is already there).
If anyone is interested Ill see if I can work the hack into a small perl
script ;)
Kind regards,
--
Gerhard den Hollander Phone +31-10.280.1515
Technical Support Jason Geosystems BV Fax +31-10.280.1511
(When calling please note: we are in GMT+1)
[EMAIL PROTECTED] POBox 1573
visit us at http://www.jasongeo.com 3000 BN Rotterdam
JASON...#1 in Reservoir CharacterizationThe Netherlands
This e-mail and any attachment is/are intended solely for the named
addressee(s) and may contain information that is confidential and privileged.
If you are not the intended recipient, we request that you do not
disseminate, forward, distribute or copy this e-mail message.
If you have received this e-mail message in error, please notify us
immediately by telephone and destroy the original message.
Priorities, amanda speed
More on the same story .. Im getting there :) Seems that the bottleneck indeed was the gzip process .. I've changed my disklist/amanda.conf to no longer compress the images, and instead rely on the hardware compression in the LTO drive (trading tape space for speed ;) ), and the results are rather dramatic. A normal amanda session with compression takes between 10 and 15 hours, running whitout compression finished in 3.5 hours . I still noticed that the dumper process is the bottleneck, but dumper now gets a performance of about 3 - 4 Kbps (iso sometimes down to 250bps). Kind regards, -- Gerhard den Hollander Phone +31-10.280.1515 Technical Support Jason Geosystems BV Fax +31-10.280.1511 (When calling please note: we are in GMT+1) [EMAIL PROTECTED] POBox 1573 visit us at http://www.jasongeo.com 3000 BN Rotterdam JASON...#1 in Reservoir CharacterizationThe Netherlands This e-mail and any attachment is/are intended solely for the named addressee(s) and may contain information that is confidential and privileged. If you are not the intended recipient, we request that you do not disseminate, forward, distribute or copy this e-mail message. If you have received this e-mail message in error, please notify us immediately by telephone and destroy the original message.
Re: A question about tapecycles and 0 dumps
* Christoph Scheeder [EMAIL PROTECTED] (Mon, Jan 22, 2001 at 10:31:14AM +0100) It looks like amanda tries to squeeze exactly 1 0 dump for each filesystem in a dumpcycle. This is bad (just imagine a diskcrash just as the disk is being 0dumped to the tape that had the last 0dump on it). No, that is the intended way amanda works. Okay Is there any way to get amanda to do 2 0dumps per filesystem in each dumpcycle (apart form specifying a dumpcycle of N/2 days ) ? No other way. Dumpcycle is exactly ment for this purpose. To give the time after that every filesystem has to be dumped at least once with a level 0 dump. Okay Or am I misunderstanding things here ? Yes. Okay, that explains it ;) if you specify a dumpcycle of 7 days, with runspercycle set to 5 and tapecycle set to 10, amanda will only accept tape T1 when it has written to tape T10 before. dumpcyle tels amanda how often to do level 0's and tapecycle tells her how many tapes she should use before recycling them. Hope it helps Yup, sure does. Rereading the manpages, I see that that's exactly what's written there, I guess that'll teach me not to read manpages on sunday evenings ;) ) Kind regards, -- Gerhard den Hollander Phone +31-10.280.1515 Technical Support Jason Geosystems BV Fax +31-10.280.1511 (When calling please note: we are in GMT+1) [EMAIL PROTECTED] POBox 1573 visit us at http://www.jasongeo.com 3000 BN Rotterdam JASON...#1 in Reservoir CharacterizationThe Netherlands This e-mail and any attachment is/are intended solely for the named addressee(s) and may contain information that is confidential and privileged. If you are not the intended recipient, we request that you do not disseminate, forward, distribute or copy this e-mail message. If you have received this e-mail message in error, please notify us immediately by telephone and destroy the original message.
Re: Reiser
* Joshua E Warchol [EMAIL PROTECTED] (Tue, Jan 23, 2001 at 09:02:36AM -0500) Has anyone successfully backed up larger reiserfs partitions? One of my co- Depending on what you mean by larger ... My own linux box has 2 reiser partitions, the OS (which doesn't get backed up) and my personal data (which does ;) [~ 8G ]). And we've got a number crucnher that has 2 reiser partitions (6 and 18G) and they back up just fine. Of course, you have to use tar to make a backup, since there is no dump for reiser. ^^ workers has setup a new Linux workstation with reiserfs for everything but /boot. Boy, am I glad he did that :-( Well, I for one am very happy with it. 1) it actually *is* fatser than ext2 2) never having to fsck an 18G partition after a hard crash (and yes, I know, linux boxes shouldn';t hard crash, but then, you shouldn't be playing with alpha and beta level kernel drivers ;) ) Gerhard, @jasongeo.com == The Acoustic Motorbiker == -- __O Standing above the crowd, he had a voice so strong and loud =`\, we'll miss him (=)/(=) Ranting and pointing his finger, At everything but his heart we'll miss him
Re: Using LTO drives with amanda? (oops, lto.ps)
* Chris Stoddart [EMAIL PROTECTED] (Tue, Jan 23, 2001 at 03:55:46PM +) Oops. I noticed the lto.ps has a logo included with it, you proabbly don't want the logo in there if you use it , so you have to hack it out of the postscript again ;) Gerhard, @jasongeo.com == The Acoustic Motorbiker == -- __O Some say the end is near. =`\, Some say we'll see armageddon soon (=)/(=) I certainly hope we will I could use a vacation
Re: Q: tape drives beyond DLT or SLR
* Bernhard R. Erdmann [EMAIL PROTECTED] (Tue, Jan 23, 2001 at 10:34:35PM +0100) Work on multitapebackup is (apparently) underway for Amanda NG _This_ is good news indeed. So one possible solution would be to go for a library instead of an autoloader, start with 1 tape of 50 or 100 GB capacity now - and hope AmandaNG will be available when we need it ;-)) What is "Amanda NG"? Amanda Next Generation? Sorry, Ny bad, Amanda Ng is simply my abbreviation for whatever the next version of amamnda is going to be (2.4.2p1, 2.4.3, 2.5, 3.0 ) when I wrote the above I remembred a posting from someone sayign he was working on a multitape patch for Amanda. Gerhard, @jasongeo.com == The Acoustic Motorbiker == -- __O For prosimian fun, you can bugger a lemur =`\, To bolster your name as a pervert and schemer (=)/(=) The lemurs cry "Frink!" as a coy mating call But the hedgepod can never be buggered at all.
Re: self check request timed out
* John R. Jackson [EMAIL PROTECTED] (Wed, Jan 24, 2001 at 06:50:46PM -0500) The only things I can think of to try at this point are a complete rebuild of Amanda (blow away all traces of the build area you used before), or upgrading to the latest gcc and building that for the specific host, or making sure you have all the latest Solaris patches. That was the first thing I thought of when I saw these weird errors. It looks liek parts of the code are compiled with different compiler settings/defines or somesuch ... Either that or there is something weird with Sol 7 What could also be is that the Sol 7 code is being compiled with 64bit integers, and some of the supporting libraries you're linking against are expecting ints to be 32bits. Do you have a Sol 2.6 box around ? If so, try building amanda on the 2.6 box. 2.6 Amanda works nice and shiny on a Sol 7 box (at least it should, I haven't actually tried it yet ;) ) Kind regards, -- Gerhard den Hollander Phone +31-10.280.1515 Technical Support Jason Geosystems BV Fax +31-10.280.1511 (When calling please note: we are in GMT+1) [EMAIL PROTECTED] POBox 1573 visit us at http://www.jasongeo.com 3000 BN Rotterdam JASON...#1 in Reservoir CharacterizationThe Netherlands This e-mail and any attachment is/are intended solely for the named addressee(s) and may contain information that is confidential and privileged. If you are not the intended recipient, we request that you do not disseminate, forward, distribute or copy this e-mail message. If you have received this e-mail message in error, please notify us immediately by telephone and destroy the original message.
Re: Can't read Travan dump tape
* Mack Earnhardt [EMAIL PROTECTED] (Thu, Jan 25, 2001 at 09:28:31AM -0500) Had you rewound the tape? Amrecover does not do so (or anything else), so if it was at the end (or someplace in the middle), bad things will happen. It gives exactly the same messages (including amidxtaped.debug) whether amrecover is preceeded by 'mt rewind' or 'mt fsf'. Seems to make no difference. Many people have said amrecover doesn't rewind, but the tape drive sure sounds like it does. Ehm, this may be a stupid question, but are you sure you are using the no-rewind tapedevice ? usually called /dev/ntape /dev/nrtape or somesuch. Please check your OS documentation Kind regards, -- Gerhard den Hollander Phone +31-10.280.1515 Technical Support Jason Geosystems BV Fax +31-10.280.1511 (When calling please note: we are in GMT+1) [EMAIL PROTECTED] POBox 1573 visit us at http://www.jasongeo.com 3000 BN Rotterdam JASON...#1 in Reservoir CharacterizationThe Netherlands This e-mail and any attachment is/are intended solely for the named addressee(s) and may contain information that is confidential and privileged. If you are not the intended recipient, we request that you do not disseminate, forward, distribute or copy this e-mail message. If you have received this e-mail message in error, please notify us immediately by telephone and destroy the original message.
Re: gtar large filesystem times out.
* Alexandre Oliva [EMAIL PROTECTED] (Fri, Jan 26, 2001 at 12:58:59AM -0200) I don't understand. If the CPU usage dropped that much, it implies the GNU tar might have been done. Did you do a "ps" to see what was going on? Yeah, the gtar process was the one taking up 70% of the CPU, then after 20 minutes it was only using 0.4%. It never finished, I just killed it so I could run a manual dump command. strace would have told you what it was doing. You may want to try tar 1.13.19, that uses a hashtable instead of linear searches in file lists (compliments to Jean-Louis Martineau). Where can I get tar 1.13.19 ? The latest I can find on pub.gnu.org is 1.13. Gerhard, @jasongeo.com == The Acoustic Motorbiker == -- __O If your watch is wound, wound to run, it will =`\, If your time is due, due to come, it will (=)/(=) Living this life, is like trying to learn latin in a chines firedrill
Re: Time outs .. but why
* Alexandre Oliva [EMAIL PROTECTED] (Fri, Jan 26, 2001 at 08:17:56AM -0200) On Jan 26, 2001, Gerhard den Hollander [EMAIL PROTECTED] wrote: My nightly dump failed with an estimate time-out, How long is your etimeout? It must be longer than 3 hours: amandad: debug 1 pid 4135 ruid 0 euid 0 start time Thu Jan 25 19:00:02 2001 ^^ [...] amandad: waiting for ack: timeout, giving up! amandad: pid 4135 finish time Thu Jan 25 22:06:42 2001 ^^ Aaarggh ... My etimeout is exactly 3 hours .. fooled by 6 minutes ;( I've did the followign: - downloaded, compiled and installed tar 1.13.19 (as per suggestion here, which should be faster than normal tar .. will keep you posted) - upped my etimeout from -10800 to -15000 Thanks for the help, will keep you posted. (BTW, totally off-topic, but did anyone here ever manage to hookup an MGE - UPS to an UE450 box ?) Kind regards, -- Gerhard den Hollander Phone +31-10.280.1515 Technical Support Jason Geosystems BV Fax +31-10.280.1511 (When calling please note: we are in GMT+1) [EMAIL PROTECTED] POBox 1573 visit us at http://www.jasongeo.com 3000 BN Rotterdam JASON...#1 in Reservoir CharacterizationThe Netherlands This e-mail and any attachment is/are intended solely for the named addressee(s) and may contain information that is confidential and privileged. If you are not the intended recipient, we request that you do not disseminate, forward, distribute or copy this e-mail message. If you have received this e-mail message in error, please notify us immediately by telephone and destroy the original message.
Re: Amrecover, Invalid directory error
* John R. Jackson [EMAIL PROTECTED] (Fri, Jan 26, 2001 at 01:05:47PM -0500) Sure enough, GNU tar 1.13. Will version 1.11.8, or 1.12 work? I don't think 1.11.* will work. 1.12 will work if you apply the patches from www.amanda.org. 1.13.19 is reported to work. Could this be added to the docs, please ? Will 1.13.17 work ? Kind regards, -- Gerhard den Hollander Phone +31-10.280.1515 Technical Support Jason Geosystems BV Fax +31-10.280.1511 (When calling please note: we are in GMT+1) [EMAIL PROTECTED] POBox 1573 visit us at http://www.jasongeo.com 3000 BN Rotterdam JASON...#1 in Reservoir CharacterizationThe Netherlands This e-mail and any attachment is/are intended solely for the named addressee(s) and may contain information that is confidential and privileged. If you are not the intended recipient, we request that you do not disseminate, forward, distribute or copy this e-mail message. If you have received this e-mail message in error, please notify us immediately by telephone and destroy the original message.
Re: Amrecover, Invalid directory error
* Alexandre Oliva [EMAIL PROTECTED] (Mon, Jan 29, 2001 at 11:07:59AM -0200) Ehm, docs INSTALL sais, use 1.12 w/ patches. I assumed (incorrectly) that 1.13 would work as well. It's fixed in 2.4.2p1. So I noticed ;) Will 1.13.17 work ? Yep, but there's a (rare?) bug in 1.13.17 that may cause it to crash. I just tested it ()I know, why ask, if you can test it yourself) and 1.13.17 works fine (the one that comes with Suse 7.0) Which doesn't mean it wouldn't crash for you at certain obscure conditions. Jean-Louis Martineau posted a message about the problem (with patch) it a while ago. His patch made it to 1.13.19. As well as his improvements for GNU tar to use hash tables instead of linear searches for filenames, which should make it significantly faster. OK, I will install 1.13.19 on the linux boxen as well. However, it doesn;t give me a huge performance boost .. it still takes well over 3 hours to get an estimate ;) Gerhard, @jasongeo.com == The Acoustic Motorbiker == -- __O Some say the end is near. =`\, Some say we'll see armageddon soon (=)/(=) I certainly hope we will I could use a vacation
Re: why | ufsrestore?
* John R. Jackson [EMAIL PROTECTED] (Sun, Jan 28, 2001 at 08:20:30PM -0500) I have always wondered .. why does amanda pipe ufsdump output to ufsrestore before sending it to the tape device? It's collecting the index data. The dump (or tar) output pipeline is rather complicated. The image data goes back to sendbackup who in turn tee's it to the restore program to gather the index information (if indexing is enabled) as well as sending the raw data (possibly through a compression program) back on the network to a dumper process on the server side. The restore program also feeds its results back through sendbackup to be sent to the dumper on a different socket (as I recall). So sendbackup is multiplexing five data streams: * reading the dump image coming in from the backup program * writing the image out to the index (restore) process * writing the image out the socket connected to dumper on the server or to a compression program * reading the output of the index process * writing the index data to another socket back to dumper Allright, that explains a lot. Thanks very much. If I ufsdump direct to tape, eg. ufsdump 0f /dev/rmt/0n / I consistently achieve 3mb/second (Exabyte mammoth). If amanda is dumping direct to tape (file systems that are bigger than the holding disk), I'm lucky if i get 1mb/second. If it's going from the holding disk to tape, I get 3mb/second, as expected. But you're comparing apples and oranges. As you've noted, going from disk to tape on the same machine gets 3 MBytes/s whether you are using ufsdump or Amanda is using taper to copy a holding disk image. But that's not what happens when Amanda is dumping a client direct to tape. The data has to go across the network (even if it's all on the local machine it still goes through the kernel network stack). And, probably even more important, Amanda does compression when dumping, not when writing to tape. Even with compression disabled, amanda is much slower. Dumper gets between .5 and 3kbps (disk and tape all on server ). Taper gets 7-8Kbps [see below for more detailed report] So a dump to holding disk would be "slow" but the corresponding holding disk to tape operation would be "fast". But a direct to tape backup would pay the penalty and show the speed loss due to compression even though the tape I/O portion is going as fast as it is given data. It's not the compression (or at leat not only the compression) that gives the penalty, but more likely the 5 way split .. As long as Im doing incrementals it isn't too bad, since those dump to disk, and from disk to tape is fast. When doing a 0dump of a 100+G tar directory it becomes painfull ;) You didn't mention what kind of dump rates Amanda reports. Those should more or less match your direct to tape numbers for large enough images to get a good sample and with similar clients. Note that I'm not saying something isn't wrong in Amanda. Just that we need to narrow down the list of culprits. Using the atatched script, I got the following out of my latest amdump file (all disks are local to the amanda server all disks are wide scsi (80Mbps ) or better (LVD) ) (usage, getbps.pl amdumpfile ) DUMPER: 17.7 TAPER: 55.6 DUMPER: 8.7 TAPER: 47.7 DUMPER: 565.9 TAPER: 2886.3 DUMPER: 1431.6 TAPER: 9620.7 DUMPER: 294.6 TAPER: 6414.0 DUMPER: 3061.4 DUMPER: 2249.5 TAPER: 9787.8 TAPER: 2884.3 DUMPER: 1027.1 TAPER: 7059.3 DUMPER: 2077.8 TAPER: 6033.7 DUMPER: 1869.2 TAPER: 5516.5 DUMPER: 2913.1 TAPER: 7524.7 DUMPER: 1671.4 TAPER: 8072.4 DUMPER: 1423.8 TAPER: 6464.1 DUMPER: 1216.9 DUMPER: 2204.8 TAPER: 7347.8 TAPER: 6818.4 DUMPER: 1796.7 TAPER: 6793.8 DUMPER: 1584.8 TAPER: 7249.1 DUMPER: 2673.5 TAPER: 11384.8 DUMPER: 4331.9 TAPER: 4330.9 DUMPER: 2742.2 TAPER: 2742.1 Averages Dumper 1758.13 Taper 5951.7 The same script run over the last 10orso amdump files I had still on disk (output stripped to only show the averages) gives Averages Dumper 1124.84210526316 Taper 4952.77368421053 Averages Dumper 1198.96 Taper 4038.22 Averages Dumper 1762.467 Taper 7299.05 Averages Dumper 1758.13 Taper 5951.7 Averages Dumper 1523.978 Taper 5017.5 Averages Dumper 899.25 Taper 4525.7625 Averages Dumper 1771.47 Taper 5564.87 Averages Dumper 1658.56 Taper 6897.71 Averages Dumper 82.1 Taper 3085.6 Averages Dumper 95.81 Taper 3129.7 Kind regards, -- Gerhard den Hollander Phone +31-10.280.1515 Technical Support Jason Geosystems BV Fax +31-10.280.1511 (When calling please note: we are in GMT+1) [EMAIL PROTECTED] POBox 1573 visit us at http://www.jasongeo.com 3000 BN Rotterdam JASON...#1 in Reservoir CharacterizationThe Netherlands This e-mail and any attachment is/are intended solely for the named addressee(s) and may
|ufsrestore .. also for tar ?
sidenote: since egroups went yahoo, I haven';t eben able to access the searchable archives .. Is this just Konqueror, or is it broken ? Anyway, When dumping with ufsdump, amanda pipes through ufsrestore to get an index .. fair enough However, when dumping via tar, we dont need this, right ? doing a tar cvf .. should give you a full list of everything being backed up ? (well, maybe we need a grep -v excluded pipe or something smart like that ) So is amanda doing that ? Or does she do a tar cf - . | tar tvf - ?? Kind regards, -- Gerhard den Hollander Phone +31-10.280.1515 Technical Support Jason Geosystems BV Fax +31-10.280.1511 (When calling please note: we are in GMT+1) [EMAIL PROTECTED] POBox 1573 visit us at http://www.jasongeo.com 3000 BN Rotterdam JASON...#1 in Reservoir CharacterizationThe Netherlands This e-mail and any attachment is/are intended solely for the named addressee(s) and may contain information that is confidential and privileged. If you are not the intended recipient, we request that you do not disseminate, forward, distribute or copy this e-mail message. If you have received this e-mail message in error, please notify us immediately by telephone and destroy the original message.
Re: |ufsrestore .. also for tar ?
* Jean-Louis Martineau [EMAIL PROTECTED] (Mon, Jan 29, 2001 at 03:45:03PM -0500) It will require to much work to the sendbackup process. It will be possible to do it with the DUMPER-API, is you have time, you should work on the DUMPER-API. Time, yeah, heard about that .. seems to be very useful to have around ;) ... (or, sorry, but Im afraid I don';t really ahve the time to spare, though who knows ;) ) Kind regards, -- Gerhard den Hollander Phone +31-10.280.1515 Technical Support Jason Geosystems BV Fax +31-10.280.1511 (When calling please note: we are in GMT+1) [EMAIL PROTECTED] POBox 1573 visit us at http://www.jasongeo.com 3000 BN Rotterdam JASON...#1 in Reservoir CharacterizationThe Netherlands This e-mail and any attachment is/are intended solely for the named addressee(s) and may contain information that is confidential and privileged. If you are not the intended recipient, we request that you do not disseminate, forward, distribute or copy this e-mail message. If you have received this e-mail message in error, please notify us immediately by telephone and destroy the original message.
Re: Error msg interpretation
* Ben Elliston [EMAIL PROTECTED] (Tue, Jan 30, 2001 at 10:10:15AM +1000) jrj wrote: Is this 2.4.2? If so, I think you're not the only one who's mentioned this. Sigh. Yes, it is. Interestingly, I think this is the first partition of mine to receive a level 3 dump. Are you using tar to dump ? Level 3 dumps might take a long while to start receiving data when using tar. tar is slow .. It takes currently well over 4 hours for tar to give me an estimate of my disks [rant, rant, fume fume ;) ] more on this in a later post ;) Gerhard, @jasongeo.com == The Acoustic Motorbiker == -- __O Remember that two wrongs never make a right, =`\, But that three do. (=)/(=)
Re: amrecover: cannot connect to host (connection refused)
* Sebastian Frankfurt [EMAIL PROTECTED] (Tue, Jan 30, 2001 at 10:27:41AM +0100) Mack Earnhardt wrote: I was getting connection refused on amrecover for a while. The ..amandahosts file allowed access to root@localhost, but amrecover would use root@servername and fail. My solution was to use the server name explicitly in both .amandahosts and disklist. Hope this help one of your problems. :) Well thanx for the tip, but it doesn't matter, what I put into the .amandahosts because the error I get is: AMRECOVER Version 2.4.1p1. Contacting server on localhost ... amrecover: Unexpected server end of file Did you check the files in /tmp/amanda (on server and client) ? Kind regards, -- Gerhard den Hollander Phone +31-10.280.1515 Technical Support Jason Geosystems BV Fax +31-10.280.1511 (When calling please note: we are in GMT+1) [EMAIL PROTECTED] POBox 1573 visit us at http://www.jasongeo.com 3000 BN Rotterdam JASON...#1 in Reservoir CharacterizationThe Netherlands This e-mail and any attachment is/are intended solely for the named addressee(s) and may contain information that is confidential and privileged. If you are not the intended recipient, we request that you do not disseminate, forward, distribute or copy this e-mail message. If you have received this e-mail message in error, please notify us immediately by telephone and destroy the original message.
Getting estimates ..
getting estimates with gnuatr takes forever and then some. Amanda also comes with a little tool called calcsizes that 1) seems to be fatser than gnutar 2) can do mutlipel estimates in one run. Currently getting an estimate on the big disk takes 3 -4 hours and that's mainly because for every levbel, a new gnutar is being run. So to get estimates for a level 0, 1 and 2 run I see amanda doing get gnutar estimate for level 0 (this takes over an hour) when this has finished get gnutar estimate for level 1 (this takes over an hour) when this has finished get gnutar estimate for level 2 (this takes over an hour) total time, close to 4 hours. using calcsize, I should be able to do something like calcsize GNUTAR lto /whopper/home 0 0 1 980801273 2 980851273 and get the estimates for level 0 1 and 2 all at once. So my question is, How do I tell amanda to use calcsize ? I didn't find anything in docs/* man/* or config/* %grep calcsize docs/* man/* config/* docs/WHATS.NEW:"calcsize" and "runtar" therefore must be installed setuid root. I've made If this is not possible, can this please be taken as a serious wishlist for Amanda 2.5 ? Also, if this is not possible, does anyone have any other suggestions on getting a speedup on the estimates ? The sendsize.c file menations a maxdumps= variable .. How can this be set ? Kind regards, -- Gerhard den Hollander Phone +31-10.280.1515 Technical Support Jason Geosystems BV Fax +31-10.280.1511 (When calling please note: we are in GMT+1) [EMAIL PROTECTED] POBox 1573 visit us at http://www.jasongeo.com 3000 BN Rotterdam JASON...#1 in Reservoir CharacterizationThe Netherlands This e-mail and any attachment is/are intended solely for the named addressee(s) and may contain information that is confidential and privileged. If you are not the intended recipient, we request that you do not disseminate, forward, distribute or copy this e-mail message. If you have received this e-mail message in error, please notify us immediately by telephone and destroy the original message.
Re: amdump and eject
* Luc Lalonde [EMAIL PROTECTED] (Tue, Jan 30, 2001 at 08:55:29AM -0500) Hey folks, Is this safe to put in the Amanda crontab? /usr/sbin/amdump Daily; /usr/bin/mt -f /dev/nst0 eject I have it in mine. I'm just wondering if "amdump" spawns other jobs that need to be executed before quitting and then ejecting the Not that I have noticed. PS: Amanda is really great. I've only one complaint though. I can't seem to get estimates from Solaris 2.7. "sensize" takes forever with "tar". tar takes forever. I've hacked sendsize to use calcsize instead (which Im testing now on my linux box , where I can afford to screw up the backup process once or twice). using the hack below the estimate fase takes 16 minutes iso 45 - 60 minutes. It's currently backing up , Im curious to see how it pans out. on my big disk gnutar takes 3 times 75 minutes to ghet level 0, 1 and 2 estimates of a 110G dir-tree calcsize takes 35 minutes (and does all 3 levels in one go) Note, the hack below is not fully functional yet, and will *always* use calcsize, even if you're using ufsdump !!. In sendsize.c, change the bit from line 370 onward into /* Now in the child process */ #ifndef USE_GENERIC_CALCSIZE if(strcmp(est-program, "DUMP") == 0) dump_calc_estimates(est); else # ifdef SAMBA_CLIENT if (strcmp(est-program, "GNUTAR") == 0 est-amname[0] == '/' est-amname[1] == '/') smbtar_calc_estimates(est); else # endif # ifdef GNUTAR if (strcmp(est-program, "GNUTAR") == 0) gnutar_calc_estimates(est); else # endif #endif generic_calc_estimates(est); if (maxdumps 1) exit(0); } and #define USE_GENERIC_CALCSIZE (e.g. in config/config.h) I eventually have to kill it. I just bypass the problem and use "ufsdump". Is this one of the bugs that is fixed in 2.4.2p1? No. Gerhard, @jasongeo.com == The Acoustic Motorbiker == -- __O "Bipedalism--an unrecognized disease affecting over 99% of the =`\, population. Symptoms include lack of traffic sense, slow rate of (=)/(=) travel, and the classic, easily recognized behavior known as cycling."
Calcsize vs gnutar to do estimates
I just hacked sendsize.c to use calcsize iso gnutar to estimate dumpsizes.
The speed difference is enorm.
Whereas gnutar took well over 4 hours to get the estimates using calcsize
gives results within 45 minutes.
Now my question is:
1) Why is gnutar used in stead of calcsize ?
2) Are there any dangers in running calcsize ?
I gather from readiong the source, the changelog, and some searching on the
egroups list that calcsize should give the same numbers as gnutar .
At any rate,
Attached below my (small) hack to sendsize.c
(basically I moved the #ifndef USE_GENERIC_CALCSIZE 3 lines lower).
Im not sure if this is the intedned behaviour
(as it is now, it still uses DUMP to get dump estimates, and calcsize for
everything else. I noticed dump on SGI returning within seconds with a
correct estimate, and calcsize isn;t going to beat that ;) )
May I suggest the following changes for Amanda 2.5 (or whatever :) )
1) change USE_GENERIC_CALCSIZE into USE_CALCSIZE_FOR_GNUTAR
(or something like that ;) )
2) add an option to ./configure to set this as a #define in config.h
(heck, I'd happily do so myself, but I do not know what the procedure is ).
void calc_estimates(est)
disk_estimates_t *est;
{
dbprintf(("calculating for amname '%s', dirname '%s'\n", est-amname,
est-dirname));
if (maxdumps 1) {
while(dumpsrunning = maxdumps) {
wait(NULL);
--dumpsrunning;
}
++dumpsrunning;
switch(fork()) {
case 0:
break;
case -1:
error("calc_estimates: fork returned: %s", strerror(errno));
default:
return;
}
}
/* Now in the child process */
if(strcmp(est-program, "DUMP") == 0)
dump_calc_estimates(est);
else
#ifndef USE_GENERIC_CALCSIZE
# ifdef SAMBA_CLIENT
if (strcmp(est-program, "GNUTAR") == 0
est-amname[0] == '/' est-amname[1] == '/')
smbtar_calc_estimates(est);
else
# endif
# ifdef GNUTAR
if (strcmp(est-program, "GNUTAR") == 0)
gnutar_calc_estimates(est);
else
# endif
#endif
generic_calc_estimates(est);
if (maxdumps 1)
exit(0);
}
gerhard, @jasongeo.com == The Acoustic Motorbiker ==
--
__O "Hello. Welcome to Hell. I am, of course, the Devil. Now, we'll start be
=`\, separating you all into lots. First, the Germans. You knew that was
(=)/(=) coming, didn't you? Over here. Next, the French. You can go stand by
the Germans. Atheists over here. I bet you feel bloody stupid right now
eh? Christians, over here. What? Oh, I'm sorry, but it turns out the
Jews were right...
Re: dumps (barely) too big
* Chris Jones [EMAIL PROTECTED] (Tue, Jan 30, 2001 at 01:27:43PM -0700) I'm using amanda-2.4.2, and I've got one filesystem that's (after compression) 500MB too big for my tape. :( I'd rather not use gtar, due to previous bad experiences with it. What were thos ebad experiences ? Kind regards, -- Gerhard den Hollander Phone +31-10.280.1515 Technical Support Jason Geosystems BV Fax +31-10.280.1511 (When calling please note: we are in GMT+1) [EMAIL PROTECTED] POBox 1573 visit us at http://www.jasongeo.com 3000 BN Rotterdam JASON...#1 in Reservoir CharacterizationThe Netherlands This e-mail and any attachment is/are intended solely for the named addressee(s) and may contain information that is confidential and privileged. If you are not the intended recipient, we request that you do not disseminate, forward, distribute or copy this e-mail message. If you have received this e-mail message in error, please notify us immediately by telephone and destroy the original message.
Re: Calcsize vs gnutar to do estimates
* John R. Jackson [EMAIL PROTECTED] (Tue, Jan 30, 2001 at 11:41:53PM -0500) 1) Why is gnutar used in stead of calcsize ? For one thing, it knows about exclusion lists. For another, it knows about incrementals. Actually, we might be wrong on both counts. I took a very quick look at the source and there is at least some support for exclusions. According to the amanda-hackers archive at egroups calcsize uses the exclusion code from gnutar. And yes, calcsize knows about incrementals. And I think it can handle incrementals because it is given multiple timestamps to compare against and appears to add up sizes between the values, which would amount to an incremental. True. I think. I've tried it on 3 backup runs and the results were accurate enough for me. Kind regards, -- Gerhard den Hollander Phone +31-10.280.1515 Technical Support Jason Geosystems BV Fax +31-10.280.1511 (When calling please note: we are in GMT+1) [EMAIL PROTECTED] POBox 1573 visit us at http://www.jasongeo.com 3000 BN Rotterdam JASON...#1 in Reservoir CharacterizationThe Netherlands This e-mail and any attachment is/are intended solely for the named addressee(s) and may contain information that is confidential and privileged. If you are not the intended recipient, we request that you do not disseminate, forward, distribute or copy this e-mail message. If you have received this e-mail message in error, please notify us immediately by telephone and destroy the original message.
Re: Getting estimates ..
* John R. Jackson [EMAIL PROTECTED] (Tue, Jan 30, 2001 at 07:21:05PM -0500) The sendsize.c file menations a maxdumps= variable .. How can this be set ? With "maxdumps" in amanda.conf. It will cause more than one estimate (on D'Oh ;) separate disks) to be done at the same time, just like during dumping. Note that it will not run multiple estimate levels of the same disk at the same time (I don't think) since that would normally beat on the disk too hard. See my previous posts. calcsize rules in this respect it will simply go over the disk in one go, and keeps track on which files will be dumped at which levbel, and simply gives the results at the end in one go. So running an estimate for 9 levels with calsize will be just as quick (and beat the disk just as hard) as doing an estimate for a level 0 only Gerhard, @jasongeo.com == The Acoustic Motorbiker == -- __O If your watch is wound, wound to run, it will =`\, If your time is due, due to come, it will (=)/(=) Living this life, is like trying to learn latin in a chines firedrill
Re: Fwd: mammoth1 AMANDA MAIL REPORT FOR January 30, 2001
* Alexandre Oliva [EMAIL PROTECTED] (Wed, Jan 31, 2001 at 08:44:05AM -0200)
On Jan 31, 2001, Gerhard den Hollander [EMAIL PROTECTED] wrote:
So it looks like it did a 0 dump
Why does it say it bumped to level 3 ?
It initially planned to bump it to level 3, but then realized it was
time for a full backup and run it. amreport should probably be
enhanced to discard such overridden notes.
OK,
thanks for clarifying that.
Well, actually simply a statement following the bump saying
Doing scheduled full backup would alleviate some confusion ;)
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicampoliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist*Please* write to mailing lists, not to me
Gerhard, @jasongeo.com == The Acoustic Motorbiker ==
--
__O Van zwart haar moet ik huilen
=`\, van blond krijg ik't benauwd
(=)/(=) Ach! Vind je't erg als jij vannacht
je bromfietshelm ophoudt. -- Levi Weemoedt
Client constrained ?
I am checking amstatus and notice that amdump is only doing 2 dumps at the same time (client constrained she tells me). Can anyone tell me how I can tell amanda to use more dumpers at once ? (It's probably something really trivial ;) ) Using /volume/amanda/share/amanda/lto/amdump from Wed Jan 31 20:00:02 MET 2001 james:/dev/md/dsk/d101 47776k finished (20:50:14) james:/whopper/big 16304k finished (20:47:36) james:/whopper/charybdis 1 832k finished (20:44:59) james:/whopper/data 020761156k dumping 4237632k ( 20.41%) (20:56:22) james:/whopper/distrib 1 512k finished (20:44:43) james:/whopper/home 0116906568k wait for dumping james:/whopper/pd1 1 128k finished (20:44:14) james:/whopper/rap 12240k finished (20:44:38) james:/whopper/scylla12144k finished (20:44:09) james:/whopper/thea 1 288k finished (20:43:02) james:/whopper/ts11920k finished (20:43:32) james:/whopper/volume11056k finished (20:42:53) james:c0t0d0s0 1 14592k finished (20:46:10) james:c0t0d0s3 1 1170656k finished (20:58:44) james:c0t0d0s5 1 160k finished (20:45:06) james:c0t0d0s6 19344k finished (20:46:31) james:c2t1d0s2 1 23488k finished (20:45:52) james:c2t3d0s0 1 62816k finished (20:54:02) james:c2t3d0s1 1 3169018k dumping 2508928k ( 79.17%) (20:53:49) SUMMARY part real estimated size size partition : 19 estimated : 19 142168791k failed : 0 0k ( 0.00%) wait for dumping: 1 116906568k ( 82.23%) dumping to tape : 0 0k ( 0.00%) dumping : 2 6746560k 23930174k ( 28.19%) ( 4.75%) dumped : 16 1344256k 1332049k (100.92%) ( 0.95%) wait for writing: 00k0k ( 0.00%) ( 0.00%) writing to tape : 00k0k ( 0.00%) ( 0.00%) failed to tape : 00k0k ( 0.00%) ( 0.00%) taped : 16 1344256k 1332049k (100.92%) ( 0.95%) 22 dumpers idle : client-constrained taper idle network free kps: 120890 holding space : 240202576k ( 90.94%) dumper0 busy : 0:15:46 ( 96.22%) dumper1 busy : 0:15:42 ( 95.77%) taper busy : 0:03:32 ( 21.60%) 0 dumpers busy : 0:00:02 ( 0.30%) start-wait: 0:00:02 (100.00%) 1 dumper busy : 0:01:10 ( 7.14%) start-wait: 0:01:10 (100.00%) 2 dumpers busy : 0:15:10 ( 92.55%) client-constrained: 0:11:53 ( 78.33%) start-wait: 0:03:17 ( 21.67%) Gerhard, @jasongeo.com == The Acoustic Motorbiker == -- __O Standing above the crowd, he had a voice so strong and loud =`\, we'll miss him (=)/(=) Ranting and pointing his finger, At everything but his heart we'll miss him
Re: Client constrained ?
* Alexandre Oliva [EMAIL PROTECTED] (Wed, Jan 31, 2001 at 08:23:27PM -0200) On Jan 31, 2001, Gerhard den Hollander [EMAIL PROTECTED] wrote: (client constrained she tells me). Can anyone tell me how I can tell amanda to use more dumpers at once ? Increase maxdumps in some dumptype of that host. Thats' what I like about this list, rapid turn artound time, and to the ppoint answers that correctly solve the problem ;) Try finding that level of support for a commercial product ;) Gerhard, @jasongeo.com == The Acoustic Motorbiker == -- __O Standing above the crowd, he had a voice so strong and loud =`\, we'll miss him (=)/(=) Ranting and pointing his finger, At everything but his heart we'll miss him
Re: Speeding up the dumpprocess ?
* Mitch Collinsworth [EMAIL PROTECTED] (Thu, Feb 01, 2001 at 09:31:52AM -0500) The avg dump rate is listed as 2M/s The avg tape rate is listed as 10M/s ... is there any way to speed up the dump process ? If you take a closer look at the numbers you'll see these are actually averages over the individual file systems' dump rates, without taking into account amount of data dumped for each data point in the average. Put more plainly, these numbers are really bogus. To really know how fast your dumps are going, look down the KB/s column. Your numbers look pretty good to me. You've got better than 1 MB/s on all your big dumps. True. The point is though that 2.3M/s (which Im getting at the 0 dump of the biggest one) translates to about 10G/hr, which means it takes 11 hours to dump the largest slice. Dumping the results from that from holding disk to tape takes less than 3 hours. In other words, it's fast, but I'd like it even faster ;). I guess splitting that slice into a bunch of smaller slices would help Gerhard, @jasongeo.com == The Acoustic Motorbiker == -- __O I'm preparing to fly, under my own steam =`\, I'm preparing to fly, into the dream (=)/(=) I'm back in the saddle, I'm out in the clear I've got no regrets, I've got no fear
Re: Speeding up the dumpprocess ?
Thanskl for all who delivered suggestions for this: To really know how fast your dumps are going, look down the KB/s column. Your numbers look pretty good to me. You've got better than 1 MB/s on all your big dumps. True. The point is though that 2.3M/s (which Im getting at the 0 dump of the biggest one) translates to about 10G/hr, which means it takes 11 hours to dump the largest slice. Wow, that's one big partition. You _could_ cut it up into smaller partitions or use the GNU tar top level directory trick but you probably have your reasons why those solutions won't work for you. OK, maybe a description of th setup might help. We've got 1 (one) big server (sun UE450) it's got 2 scsi ontrollers, and we stuck in an additional 2 dual scsi cards giving us 6 scsi channels. They're all ultra LVD (that's 160 Mbaud unles Im deeply mistaken ) Controller 0 - 4 internal 4 G disk 1 disk split up into different slices other 3 disks striped to a 12 Gb disk Controller 1 - CDrom drive - Mammoth tape drive - Mammoth tapedrive Controller 2 - empty Controller 3 - 2 18G disks - 1 36G disk partitioned into 2 18G disks Controller 4 - LTO tapedrive Controller 5 - Zero downtime RAID array (420 G) [this puppy rules, see below for rant ;) ] For the 420G raid array I use gnutar (and a patched sendsize to use calcsize to calculate the estimates, see my previous posts on this) to backup the toplevel subdirs. The RAID array is raid 5 (w/ hotspare). The holding disk is on that same raid array (and on the same partition) I've checked, and it's not the scsi controller bandwidth that's the limiting factor. [that is, if amdump is dumping to holding disk, I can start moving data to and from that disk, whitout the amdump performance dropping noticably] * Johannes Niess [EMAIL PROTECTED] (Thu, Feb 01, 2001 at 08:01:39PM +0100) Let's do the math: We need 10 M/s sustained transfer rate from holding disk to the tape and 10 M/s from data disk to holding disk. A 80 M/s SCSI bus should be able to do that. 20 M/s with a lot of seeks are quite a load for a single holding disk. Depending on you holding disk hardware I'd guestimate 3 M/s a reasonable throughput under these circumstances. Im getting 7 M/s to tape, while the simultaneous write to the holding disk is around 3 M/s Even if there are 2 dumpers dumping (giving 6 M/s - holding disk) I easily get 7 M/s to tape. I upped maxdumpers to 4 and rearranged the toplevel dir layout on the big disk (i split the 110G dir into 2 dirs of ~ 55G each). Let's see how weel that performs .. If upping maxdumpers to 4 is indeed bottlenecking the disk (which i can easily see if the dumper speed average is dropping instead of staying more or less the same) I can lower the number again. Nobody asked about seek problems on your data disks. It definitely kills performance to dump two partitions of the same disk at the same time. Amanda's default value of the spindle parameter is not at an intuitive value: Been there, tried that, sent the postcard ;) dumping a single disk at once gives me roughly the sme performance as dumping 2 disks simultaneously, even to the same holding disk. Johannes Niess P.S: Feel free to make a faq-o-matic section on performace out of this. What about a weekly post of the FAQ to this list? I am actually keeping notes on this, and I plan to put it all together into some larger document. Im proobaly gonna stick it on my webpage (along with all the other useful hints and tips I've found about amanda sofar). Ill happily make it into a faq-o-matic or write it up a bit more detailed for inclusion with the amdna docs. Whatever is most appropriate. (but currently i's not yet finished , and im still experimenting. Gerhard, @jasongeo.com == The Acoustic Motorbiker == -- __O Standing above the crowd, he had a voice so strong and loud =`\, we'll miss him (=)/(=) Ranting and pointing his finger, At everything but his heart we'll miss him
Re: Missing e-mail reports
* Victor R. Cain [EMAIL PROTECTED] (Fri, Feb 02, 2001 at 10:36:20AM -0500) The beginning of my configuration file looks like: # /etc/amanda/Config1/amanda.conf org "Config1" # your organization name for reports mailto "[EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED]" # list of message recipients dumpuser "backup" # the user to run dumps under Amcheck reports no errors, and the runs appear to be happening, but I'm getting no e-mail reports. Is there something wrong with my "mailto" line? It tries to send email to "[EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED]"@whatever.your.default.domain.is try mailto [EMAIL PROTECTED],[EMAIL PROTECTED],[EMAIL PROTECTED] Kind regards, -- Gerhard den Hollander Phone +31-10.280.1515 Technical Support Jason Geosystems BV Fax +31-10.280.1511 (When calling please note: we are in GMT+1) [EMAIL PROTECTED] POBox 1573 visit us at http://www.jasongeo.com 3000 BN Rotterdam JASON...#1 in Reservoir CharacterizationThe Netherlands This e-mail and any attachment is/are intended solely for the named addressee(s) and may contain information that is confidential and privileged. If you are not the intended recipient, we request that you do not disseminate, forward, distribute or copy this e-mail message. If you have received this e-mail message in error, please notify us immediately by telephone and destroy the original message.
Re: Missing e-mail reports
* John R. Jackson [EMAIL PROTECTED] (Mon, Feb 05, 2001 at 01:30:50PM -0500) but this means the man-pages are wrong. You mean you actually read them??? :-) yes, actually I did, and as I noticed, not good enough, quite a lot of stuff asked here is actually answered in the manpages or in the FAQ (if you know where to look ;) ) [like my question about dumpcycle/tapecycle from a few weeks back] Gerhard, @jasongeo.com == The Acoustic Motorbiker == -- __O Standing above the crowd, he had a voice so strong and loud =`\, we'll miss him (=)/(=) Ranting and pointing his finger, At everything but his heart we'll miss him
Re: Can I use only one tape for backing up all the week?
* Adolfo Pachn [EMAIL PROTECTED] (Tue, Feb 06, 2001 at 03:07:35PM +0100) Christoph Scheeder has told me that I can't use only one tape for backing up all the days of the week. Can anybody suggest me a solution? By the moment, I cant pay more tapes. if you're data is important enough to back it up, it's also important enough to buy a few more tapes. With 1 single tape, you have a single point of failure (that tape). Kind regards, -- Gerhard den Hollander Phone +31-10.280.1515 Technical Support Jason Geosystems BV Fax +31-10.280.1511 (When calling please note: we are in GMT+1) [EMAIL PROTECTED] POBox 1573 visit us at http://www.jasongeo.com 3000 BN Rotterdam JASON...#1 in Reservoir CharacterizationThe Netherlands This e-mail and any attachment is/are intended solely for the named addressee(s) and may contain information that is confidential and privileged. If you are not the intended recipient, we request that you do not disseminate, forward, distribute or copy this e-mail message. If you have received this e-mail message in error, please notify us immediately by telephone and destroy the original message.
Re: Request to nachine timed out.
* tomas morhac [EMAIL PROTECTED] (Tue, Feb 06, 2001 at 04:30:00PM +0100) You are using gnutar. It's slow (es. an incremental with gzip compression) Make sure you have set your timeout to something large I have dtimeout set to 1800 . Also, did you check /tmp/amanda on the client for debug files (sendbackup.*.debug ) ? If so, what's in the last (timewise) sendbackup.*.debug files ? There should be one for sdc1 and one for sda2. Kind regards, -- Gerhard den Hollander Phone +31-10.280.1515 Technical Support Jason Geosystems BV Fax +31-10.280.1511 I tried with dtimeout to 1800 but it's same. FAILURE AND STRANGE DUMP SUMMARY: machinesdc1 lev 0 FAILED [Request to machine timed out.] and in the /tmp/amanda (client) is no sendbackup.debug, gnutar-file, machnesdc1_0.new is empty. What is there in /tmp/amanda ? There must be at least one sendbackup.*.debug for the dump that succeeded . Kind regards, -- Gerhard den Hollander Phone +31-10.280.1515 Technical Support Jason Geosystems BV Fax +31-10.280.1511 (When calling please note: we are in GMT+1) [EMAIL PROTECTED] POBox 1573 visit us at http://www.jasongeo.com 3000 BN Rotterdam JASON...#1 in Reservoir CharacterizationThe Netherlands This e-mail and any attachment is/are intended solely for the named addressee(s) and may contain information that is confidential and privileged. If you are not the intended recipient, we request that you do not disseminate, forward, distribute or copy this e-mail message. If you have received this e-mail message in error, please notify us immediately by telephone and destroy the original message.
Re: Request to nachine timed out.
* [EMAIL PROTECTED] [EMAIL PROTECTED] (Tue, Feb 06, 2001 at 10:41:19AM +0100) Hi all I've got the problem with this: FAILURE AND STRANGE DUMP SUMMARY: machinesda2 lev 0 FAILED [Request to machine timed out.] machinesdc1 lev 0 FAILED [Request to machine timed out.] It's a linux machine where sda2 is / directory and sdc1 is raid. On the sda2 is only system, so there is about 400M but on the sdc1 is data and there is about 17G. When I comment machine sdc1 in the disklist, amdump is running properly. I also tried create machinesdc1_0.new file manually on that machine but unsuccessful. /bin/gtar --create --directory /raid --listed-incremental /usr/local/amanda242/var/amanda/gnutar-lists/machinesdc1_0.new --sparse --one-file-system --ignore-failed-read --totals --file /dev/null --exclude-from /usr/local/lib/amanda/exclude.gtar . machinesdc1_0.new has always zero size. You are using gnutar. It's slow (es. an incremental with gzip compression) Make sure you have set your timeout to something large I have dtimeout set to 1800 . Also, did you check /tmp/amanda on the client for debug files (sendbackup.*.debug ) ? If so, what's in the last (timewise) sendbackup.*.debug files ? There should be one for sdc1 and one for sda2. Kind regards, -- Gerhard den Hollander Phone +31-10.280.1515 Technical Support Jason Geosystems BV Fax +31-10.280.1511 (When calling please note: we are in GMT+1) [EMAIL PROTECTED] POBox 1573 visit us at http://www.jasongeo.com 3000 BN Rotterdam JASON...#1 in Reservoir CharacterizationThe Netherlands This e-mail and any attachment is/are intended solely for the named addressee(s) and may contain information that is confidential and privileged. If you are not the intended recipient, we request that you do not disseminate, forward, distribute or copy this e-mail message. If you have received this e-mail message in error, please notify us immediately by telephone and destroy the original message.
Re: Potential problem ... ? file system too big for tape?
* The Hermit Hacker [EMAIL PROTECTED] (Tue, Feb 06, 2001 at 10:26:09PM -0400) If i have a file system that is, when compressed, larger then my tape size, what happens? from what I read, it can't span a file system across two tapes, but I might be mis-remembering what I read ... If you're lucky, (and your holdingdisk is big enough) amanda will dump to the holding disk instead. Then dump from holding disk to new tape. (which will only work if you have a tape somewhere that's big enough. Otherwise, use gnutar (and a modified sendsize [1] ) to back up the big disk in smaller blocks. (iso /bigdiskcomp-user specify /bigdisk/dir1 comp-user-tar /bigdisk/dir2 comp-user-tar /bigdisk/dir3 comp-user-tar /bigdisk/dir4 comp-user-tar /bigdisk/dirN comp-user-tar in your disklist. [1] gnutar takes forever to estimate , I hacked sendsize to use the calcsize executable (the patch can be found on the egroups searchable archive) Gerhard, @jasongeo.com == The Acoustic Motorbiker == -- __O Some say the end is near. =`\, Some say we'll see armageddon soon (=)/(=) I certainly hope we will I could use a vacation
Re: Can I use only one tape for backing up all the week?
* John R. Jackson [EMAIL PROTECTED] (Wed, Feb 07, 2001 at 09:14:26PM -0500) Now, am not 100% certain on how taper does write the files to tape ... Very quick review: Rewind Read the label and verify Rewind Write a new label and tapemark Write a header, image and tapemark Write a header, image and tapemark ... Write the trailing label, tapemark and quit (leaving the tape where it is) ... Why not [save] the last one in tapelist, and/or amount of tape used? That's the plan. Why not go one step further, and write this information in the tapelabel. Of course, this breaks if fsf is broken ... so, now you are effectively doing an 'mt fsf last field' to get to end of tape ... True. The problem is that the drive may screw up. You may tell it to skip 37 files and it skips 36 (or 38, or 10, or 100 ...). So you have to Is this still the case with newer tape drives ? I cannot remeber ever having this probelm with exabyte , mammoth or LTO tapes. Come to think of it, I cannot even remeber it ahppening in the huge reel-to-reel tapedrive we used way back when, and that was a pretty bad piece of work ;) Gerhard, (@jasongeo.com) == The Acoustic Motorbiker == -- __0 Oh my God, the bomb has just dropped =`\, And everybody climbed right on top (=)/(=) Singing,"What a beautifull country
Re: Can I use only one tape for backing up all the week?
* Simon Mayr [EMAIL PROTECTED] (Thu, Feb 08, 2001 at 01:20:52PM +0100)
What would it take to have some sort of config option that did exactly
that? ...
Nothing. It's already there. Just leave the tape out of the drive and
make as many runs as you want into the holding disk.
eg
crontab:
15 0 * * * /path/to/smartscript
smartscript:
if holdingdisk space is to small
/path/to/amdump to_tape_config \
mt offline ( send extra big mail to the guy who changes the tape:)
else
/path/to/amdump to_holding_config
How about
As abovem 2 configs, each identical exept for allowed tapestring;
if(holdingdisk space is full){
amflush totape mt rewoffl alert-person-to-change-tape
}
amdump todiskconfig
also, finetune this so that if a holdingdisk is more full than fits a
single tape, you amflush oldest partitions first until tapefull
(e.g. by moving the latest dumps to a different dir, amflush nd move back).
Again:
See the note above and have in mind that this can only be usefull for
poeple whose backup device capacity is much more higher than the backup
load from a couple of days.
And for people who can afford to loose a couple of days worth of backups if
the holdingdisk crashes.
Q: what to do if "all" is to big, you have more than 26 areas and the
one you really want to flush is to new to be listed?
Whats the deal with the 26 areas ?
Cannot amflush flush more than 26 areas to tape ?
What do you mean with area ?
Gerhard, [@jasongeo.com] == The Acoustic Motorbiker ==
--
__O I spoke about wings ... You just flew
=`\, I wondered, I guessed and I tried ... You just knew
(=)/(=) I sighed ... And you swooned
I saw the crescent ... You saw the whole of the moon
Re: Can I use only one tape for backing up all the week?
* Simon Mayr [EMAIL PROTECTED] (Thu, Feb 08, 2001 at 03:28:07PM +0100) how do you non-interactivly amflush ? echo "all" | amflush -f whatever-your-config-is (I think , I haven't tried it ) at my site, we do something like that, but instead of flushing (as it should be) we leave the incrementals on disk and delete them together with their index files, if the holding disk space is running low B ;) Cannot amflush flush more than 26 areas to tape ? As amflush presents you a list with the directorys in the holding disk all with a indicating letter (A-Z) there is a maximum of 26 visible holding "areas". they are sorted by age (or alphabetically whats the same in this case). So cou can't *see* the 27th area and therefore can not flush it. (I DONT know if it WOULD be flushed when you select all) OK, I never realized that . BTW I checked the source, and it looks like ALL will indeed dump all, so something like echo "all" | amflush -f whatever-your-config-is should do the trick (well actually, you have to type Y as well I think., Maybe you need to do something with expect ;) Gerhard, @jasongeo.com == The Acoustic Motorbiker == -- __O Some say the end is near. =`\, Some say we'll see armageddon soon (=)/(=) I certainly hope we will I could use a vacation
Re: Can I use only one tape for backing up all the week?
* Simon Mayr [EMAIL PROTECTED] (Thu, Feb 08, 2001 at 04:14:39PM +0100) something like echo -en "A\nY\n" | /path/to/amflush -f config is working. ( Arrrgh again! ;) Allright ... What about the amanda database if i set up a "flush to nirvana" config with /dev/null. Would it do any better or other than erase the images, the index files and the log files. dunno , according to the manpages it will ``update the databases, and send email similar to amreport'' It also makes a ncie printout if you have a label specified (though it's rather silly to stick a printout label to /dev/null ) I think I read somewhere that the behavior of amanda has changed about the meaning of /dev/null. Amanda didn't let me use the /dev/null device, ioctl error or something, cannot rewind, wrong tape etc., so I came up with the simply-delete-the-stuff solution ... Dunno, Solaris gives no tape loaded errors if you try to do mt commands on /dev/null , which is reasonable ;) (well actually, you have to type Y as well I think., Maybe you need to do something with expect ;) what's "expect" ? expect is a ltittle tool that lets you automate interactive programs expects sits there, reads the utput from the program, and feeds it the required input. e.g. UUCP uses it to talk to the dialout device Gerhard, @jasongeo.com == The Acoustic Motorbiker == -- __O If your watch is wound, wound to run, it will =`\, If your time is due, due to come, it will (=)/(=) Living this life, is like trying to learn latin in a chines firedrill
more than one tape reusable
This is probably something trivial. in my amanda.conf I have dumpcycle 1 week# the number of days in the normal dump cycle runspercycle 5 # the number of amdump runs in dumpcycle days # (4 weeks * 5 amdump runs per week -- just # weekdays) tapecycle 25 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 runtapes1 I have indeed 25 tapes in my tapelist. Now when I do an amadmin myconfig tape it tells me The next Amanda run should go onto tape LTO020 or a new tape. Meaning there's only one specific tape amanda will overwrite. Im lazy, and Id like to have a list of 5 tapes (so that I can take the tapes for a whole week, stack them, next to the tapedrive, and use them in whatever order I please. What is the trick to get this done ? Gerhard, (@jasongeo.com) == The Acoustic Motorbiker == -- __O This parrot wouldn't voom if I put 4000 volts through it. It's bleeding =`\, demised. This parrot is no more. It has ceased to be. It's expired (=)/(=) gone to meet it's maker. This is a late parrot. It's a stiff. Bereft of life, it rests in peace. It's rung down the curtain joined the choir invisible. This is an EX-parrot.
Re: more than one tape reusable
* Alexandre Oliva [EMAIL PROTECTED] (Tue, Feb 13, 2001 at 08:39:21AM -0200) On Feb 13, 2001, Gerhard den Hollander [EMAIL PROTECTED] wrote: I have indeed 25 tapes in my tapelist. Im lazy, and Id like to have a list of 5 tapes (so that I can take the tapes for a whole week, stack them, next to the tapedrive, and use them in whatever order I please. What is the trick to get this done ? Set tapecycle to 21. Then, any of the 5 oldest tapes will be overwritable. I just did that, and then I get this: # amadmin lto tape The next Amanda run should go onto tape LTO020 or a new tape. Am I missing something ? My tapelist file counts 25 tapes (LTO001 to LTO025) Gerhard, @jasongeo.com == The Acoustic Motorbiker == -- __O Standing above the crowd, he had a voice so strong and loud =`\, we'll miss him (=)/(=) Ranting and pointing his finger, At everything but his heart we'll miss him
Webbased backup overview
Please find attached a small perl script I wrote today. It parses the output of amadmin config find and generates an html page out of the result listing for the last 7 days the dump results for all disks that amadmin find is able to locate. It uses the Date::Calc perl module available from CPAN (or your linux distro ;) ). It's decidedly *NOT* fancy but it fulfills a need . (the only fancy thing it does is mark level 0 dumps as bold, and failed dumps in red, so that you can see in one glimps whether there was a 0dump in your last dump cycle. Usage: amadmin config find | backupstart.pl output.html konqueror output.html (or netscape or ...) Gerhard, @jasongeo.com == The Acoustic Motorbiker == -- __O With judicious application of shaving foam water =`\, and scraping with a razor of it's prickly hind quarters (=)/(=) Whether it wriggles like fury, or curls up in a ball That blasted hedgepod can be buggered for sure. backupstats.pl
Re: access as amanda not allowed from amanda@foo.sys.si.tlan] amandahostsauth failed
* David Klasinc [EMAIL PROTECTED] (Thu, Feb 15, 2001 at 08:53:33AM +0100) Banzai! I get the above message when trying to backup one specific host. Client and You get a message saying Banzai ! Did you install the WWII - japanese slang add-on to Amanda ? [Just kidding] server are bot v2.4.2 and if I do amcheck as root then everything works fine, if I do it as user amanda, then it fails. I have users root and amanda in ..amandahosts. Any ideas what could be wrong? Ehm do you have the .amandahosts in user amandas homedir ? or only in roots homedir ? The amanda FAQ (docs/FAQ in the source tree) sez this Q: Why does `amcheck' say `access as username not allowed...' A: There must be something wrong with .amandahosts configuration (or .rhosts, if you have configured --without-amandahosts). First, if the username is not what you expect (i.e., not what you have specified in the --with-user flag, at configure time), check the inetd configuration file: you must have specified the wrong username there. Make sure you specify the names exactly as they appear in the error message after the `@' sign in .amandahosts/.rhosts. You'll need a fully-qualified domain name or not, depending on how your client resolves IP addresses to host names. HTH Gerhard, @jasongeo.com == The Acoustic Motorbiker == -- __O Also by the time I'm 60, I want to get better at the art of living. =`\, And still be riding an acoustic motorbike. (=)/(=) -- not exactly Mark Knopfler
Re: amcheck: access as........
* Jrn Hildebrandt [EMAIL PROTECTED] (Thu, Feb 15, 2001 at 11:44:28AM +0100) Amanda Backup Client Hosts Check ERROR: saturn.systemelektronik.de: [access as amanda not allowed from [EMAIL PROTECTED]] Client check: 1 host checked in 0.019 seconds, 1 problem found. (brought to you by Amanda 2.4.1p1) i am little bit astonished as new linux-user about "access as amanda not allowed." because i'm running this command as root. Yes, but the client tries to run amanda as amanda (check the docs in /usr/share/doc/packages/amanda) BTW suse 7.0 ships with amanda-2.4.1p1-157 you might wanna upgrade to 2.4.2p2. Kind regards, -- Gerhard den Hollander Phone +31-10.280.1515 Technical Support Jason Geosystems BV Fax +31-10.280.1511 (When calling please note: we are in GMT+1) [EMAIL PROTECTED] POBox 1573 visit us at http://www.jasongeo.com 3000 BN Rotterdam JASON...#1 in Reservoir CharacterizationThe Netherlands This e-mail and any attachment is/are intended solely for the named addressee(s) and may contain information that is confidential and privileged. If you are not the intended recipient, we request that you do not disseminate, forward, distribute or copy this e-mail message. If you have received this e-mail message in error, please notify us immediately by telephone and destroy the original message.
Re: amlabel + rack of tapes question
* Joseph Del Corso [EMAIL PROTECTED] (Thu, Feb 15, 2001 at 11:03:16AM -0500) Is it possible to amlabel an entire rack of tapes without doing it manually for each tape? Specifically I have roughly 35 tapes that I'd like to label in some kind of automated fashion all at once. Besides writing my own script (which would take time and more than likely a HECK of a lot of debugging) is there an easier way to do this? How about #!/bin/sh for i in mylabel01 mylabel02 mylabel35 do amlabel myconfig $i amtape slot next done (assuming you have a tapechanger capable of holding 35 tapes ) Gerhard, (@jasongeo.com) == The Acoustic Motorbiker == -- __0 Time has a way of taking time =`\, Loneliness is not only felt be fools (=)/(=) Alone I call to ease the pain
Re: Questions and Answers and Thanks
* Chris Marble [EMAIL PROTECTED] (Sat, Feb 17, 2001 at 07:59:17PM -0800) Gerhard den Hollander wrote: I noticed when looking through the logs that the *dumper* performance is around the 1Kps (or less) on my system , whereas the *taper* gets a performance of about 7 Kps. So apparently it's not the speedn of my tapedrive that's the bottleneck, but soemthing within amanda. I have now turned compression off and im hoping this will imporve matters. Are there any other ways to tweak amanda.conf to improve dumper performance Best of luck finding your current bottleneck. I did some experiments (I still need to write this out and stick it on a proper website or somesuch :) ) Anyway, the bottleneck is (In my case) the mutli pipe that amanda does tar cvf - +--- holdingdisk | +--- | tar tvf - -- index daemon Sticking gzip in there makes things even worse. What I did is: - Make sure I have a big holding disk - Patch/Hack sendsize to use the calcsize executable iso gnutar to calculate estimates (estimate generation went down frm well over 4 hours to 45 minutes) - set maxdumps to 4 (having 4 dumps in paralel to holding disk) - dump everything from holding disk to tape. With this I get upto 11K performance to tape And while the avergae performance of a backup to dumper has dropped to ~ 2.5 Ks (was 3K whitout compression, 1K with) I have 4 of them inparalel giving approx 10Ks I never got the bandwidth setting corect on my setup so I have a LOT of different dump-types with different maxdumps and dumpcycle settings. I've got 36Gb of holding disk and a single 50Gb AIT-2 drive. One of the 18 machines I'm backing up has a 36Gb drive with 30Gb of already gzipped data on it. I work to keep the full backups of that drive confined to weekends. Or use guntar, and split the big disk in smaller gnutarrable slices. That's what I did with the 420G disk, I've made a bunch of slices all of which are 50G and I have 50+ G of holding disk space (on that same disk). My backup host is a Dell Precision 610 with 2 SCSI cards. I'm going to move the tape drive to the internal controlled since my holding disks are one the external one. Maybe I'll pick up some speed there. The holding disk is 4 9Gb drives striped with software RAID. I formatted for large block sizes and few inodes to improve large file performance. I'm running RedHat Linux 6.2 with kernel 2.2.16-8. Machine's got a single 500MHz Xeon CPU and 256Mb RAM. I know a faster CPU will help during the gzip phase. Will more RAM? Depends on what else you are running. I noticed that a 500Mhz can give rather excellent theoughput with gzip -fast. Since it's a linux box , you may want to look into using reiserFS. I found that file access with Reiser is faster than ext2 (although nothing shocking) esp. when going through a lot of smaller files in one swoop. Gerhard, @jasongeo.com == The Acoustic Motorbiker == -- and family | |Oo. __O__0 |__/-=`\, =`\, (*) (=)/(=)(=)/(=)
Re: tweaking the schedule
* John R. Jackson [EMAIL PROTECTED] (Tue, Feb 20, 2001 at 07:53:20PM -0500) Next we need to examine the driver algorithm in more detail. Some of the base information is in the usenix paper on the ftp.amanda.org site. [8] If inparallel is set to three (or less), you don't have any "big" dumpers and all the processing will happen from the front of the list. If inparallel is set to four, three dumpers will be picking off the little entries at the head of the list and one dumper will start at the end of the list and work its way backward. Hey, that explains exactly what Im seeing ... Now that I've upped maxdumpers to 4 it is indeed picking the biggest dump first (as well as some smaller ones) and giving a reduced dumptime . Time to get that useni paper ;) Gerhard, @jasongeo.com == The Acoustic Motorbiker == -- __O Aristotle, Aristotle was a bugger for the bottle, =`\, and Hobbes was fond of his Dram. (=)/(=) And Rene Descartes was a drunken fart: "I drink, therefore I am."
Re: questions on DLT7?
* Denyce Berg [EMAIL PROTECTED] (Wed, Feb 21, 2001 at 08:18:46AM -0700) Thinking about purchasing one want to make sure it will work before spending the large amount of money. Buy an LTO .. 100G uncompressed for roughly the same price Gerhard, (@jasongeo.com) == The Acoustic Motorbiker == -- __0 Oh where are you now pussy willow that smiled on this leaf? =`\, When I was alone you promised the stone from your heart (=)/(=) my head kissed the ground I was half the way down, treading the sand please, please, lift a hand
Re: Questions and Answers and Thanks
* Chris Marble [EMAIL PROTECTED] (Wed, Feb 21, 2001 at 09:51:32PM -0800) Gerhard den Hollander wrote: Since it's a linux box , you may want to look into using reiserFS. I found that file access with Reiser is faster than ext2 (although nothing shocking) esp. when going through a lot of smaller files in one swoop. I formatted up the holding disk with a large blocksize and small inode count. It's never going to have over 100 files on it so I doubt ReiserFS is worth the hassle. I guess not, Reiser comes prepackaged with Suse, so in my case it wasn't a hassle at all . But my suggestion was making the disk to be backed up use reiser iso the holding disk. I do all my backups with dump, ufsdump or xfsdump now. I'd just as soon avoid adding in gnu tar too. Well, amanda handles it all transparently for you. Except that getting estimates with gnutar takes forever and then some. Gerhard, @jasongeo.com == The Acoustic Motorbiker == -- __O You are a fluke of the universe ... =`\, You have no right to be here. (=)/(=) Whether you can hear it or not, the universe Is laughing behind your back.
Re: system crash
* Monserrat Seisdedos Nuez [EMAIL PROTECTED] (Thu, Feb 22, 2001 at 10:13:06AM +0100) Hello everybody: I'm wondering, if my entire system crash, and i have to built it again, just with a clean disk., i could do it from my last system amanda backup??? 0) Don't panic 1) reinstall OS 2) reinstall your amanda binaries (hint burn a CD with your amanda binaries) 3) Locate your last level 0,1 , c dumps (hint, always label your tapes, always keep a printout of which dump is on which tapeimage) 4) Use amrestore to read your tapeimages back (mt -f fsf XXX /norrewindtapedev; cd /disktoberestored ; amrestore -p | restore -ivbf 2 -) Gerhard, @jasongeo.com == The Acoustic Motorbiker == -- __O Some say the end is near. =`\, Some say we'll see armageddon soon (=)/(=) I certainly hope we will I could use a vacation
Re: forcing level 0 backups
* Ben Elliston [EMAIL PROTECTED] (Thu, Feb 22, 2001 at 11:17:58PM +1100) Is there any easy way to force a level 0 backup of every disk in the disklist? amadmin config force hostname repeat for each hostname Gerhard, @jasongeo.com == The Acoustic Motorbiker == -- __O I have a spelling checker. It came with my PC. =`\, It plane lee marks four my revue miss steaks aye can knot see. (=)/(=) To rite with care is quite a feet Of witch won should be proud, And wee mussed dew the best wee can, Sew flaws are knot aloud
Re: printout of dump says 0Kb
* Ross Macintyre [EMAIL PROTECTED] (Fri, Feb 23, 2001 at 10:57:54AM +)
I wonder if someone can help me here?
I'm still tyring to get someone else's setup of amanda running and I
feel I'm nearly there. But I'm confused by this:
2 night's worth of dumps failed (because I hadn't the correct tape in)
and I put in the right tape and ran 'diskflush tape1'. This seemed to
work fine but the printout of the dump says:
Total size 0.0MB
Tape Used 29.2%
Compression Ratio --%
Filesystems dumped 0
It then goes on to list lots of Filesystems that I think were dumped.
I did the flush manually and it certainly wrote a lot to tape, and the
2 logs(amflush.1 and log.20010222.0) look ok. The end of the log says:
-
SUCCESS taper hennion /dev/dsk/c0t0d0s3 20010222 1 [sec 0.059 kb 160 kps 2694.6
{wr: writers 5 rdwait 0.000 wrwait 0.038 filemark 0.018}]
INFO taper tape Tape1_125 kb 5956064 fm 146 [OK]
FINISH amflush date 20010222 time 4164.489
-
Does the 5956064 represent the Kb written to tape?
Yes,
It looks like you wrote 146 fileimages to tape, totalling 5956064 kb
If you want to be really sure
run the attached perl script to get a table of contents of your tape
(also included here sicne atatchement apaprently don';t work in digest mode
?)
#!/usr/bin/perl
$device = shift || die "Please specify full tapedevice\n";
$dd = "/bin/dd";
$mt = "/bin/mt";
print "Rewinding\n";
system("$mt -f $device rewind");
$tapeheader = `$dd if=$device bs=32k count=1`;
die "Amanda Label not found!\n$tapeheader\n" unless $tapeheader =~
/TAPESTART/;
print $tapeheader;
push(@stuff,$tapeheader);
while ( ! $ierr ){
$foo = `$dd if=$device bs=32k count=1 | head -3`;
if ($foo =~ /TAPEEND/) {
print $foo;
last;
} elsif ($foo =~ /FILE/) {
print $foo;
} else {
$foo =~ tr/A-Za-z0-9 \t\r\n/ /cs;
print "Unexpected thing: $foo\n";
}
$ierr = $?;
}
print "Rewinding\n";
system("$mt -f $device rewind");
Currently listening to: 02_JerkOff
Gerhard, [@jasongeo.com] == The Acoustic Motorbiker ==
--
__O Hypocrites and Zealots
=`\, are struggling for the throne,
(=)/(=) Kings and queens and presidents
All younger then the Stones
amanda.toc.pl
Re: Amrecover 2.4.2p1 Problem (2nd)
* Patrick LIN [EMAIL PROTECTED] (Fri, Feb 23, 2001 at 07:53:53AM -0500) hi, the directory spoon exist and the directory c1t5d0s0 too but something is strange some file is empty . 20010215_0 is empty but 20010215_0.gz is ther too and not empty strange been there, done that, bought the tshirt. rm 20010215_0 and your'e set. Im not sure what goes wrong, but amanda tries to uncompress the gzip files but this failes if there already is a file (with the same name, but no gzip extension). if the resulting file is empty, amanda cannot get any info. This happens either is you ^C out of amrecover or if there is a disk-full condition when amrecover tries to gunzip the .gz file). So to solve 1) rm the file(s) whitout the .gz extension (20010215_0) 2) make sure there is enough diskspace (or keeop an eye on your syslog, and if you get any disk full messages, make more diskspace and start again at step 1) Currently listening to: 10_youlied Gerhard, @jasongeo.com == The Acoustic Motorbiker == -- __O If your watch is wound, wound to run, it will =`\, If your time is due, due to come, it will (=)/(=) Living this life, is like trying to learn latin in a chines firedrill
Re: New question on disaster recovery with amanda
* John R. Jackson [EMAIL PROTECTED] (Sat, Feb 24, 2001 at 12:14:38PM -0500) The list of tapes needed may be maintained several ways: * You could set up lbl-templ in amanda.conf to (e.g.) 3hole.ps and save the paper copies Amanda will generate after every run. The exa,dat,LTO .ps files only list host, filesystem and dumplevel. They do not list which tapeimage is which, *and the listing is sorted alphabetically, not per dumpimage*. 3hole does list them though. Currently listening to: 05-PlanetTelex Gerhard, @jasongeo.com == The Acoustic Motorbiker == -- __O Some say the end is near. =`\, Some say we'll see armageddon soon (=)/(=) I certainly hope we will I could use a vacation
Re: sednsize problem
* Alexandre Oliva [EMAIL PROTECTED] (Tue, Feb 27, 2001 at 10:36:20PM -0300)
On Feb 27, 2001, Gerhard den Hollander [EMAIL PROTECTED] wrote:
What is the easiest way to debug sendsize ?
Get the request from amandad.debug and feed it to sendsize's stdin.
OK, full output of the amandad.debug is attached ..
Not sure where I can find the input to sendsize
but I suspect it's the lines that say
GNUTAR sda6 0 1970:1:1:0:0:0 -1 exclude-list=/usr/local/lib/amanda/exclude.gtar
GNUTAR sda6 0 1970:1:1:0:0:0 -1 exclude-list=/usr/local/lib/amanda/exclude.gtar
Which I take to ask (twice ?) for a level 0 dump
Sendsize obliges and returns the results of the level 0 dump only.
(which i can see if I run amstatus before the dump starts, there is a level
0 estimate listed for sda6)
Planner than decided to do a level 1 dump and since it didn't get an
estimate errors out with a No Estimate error.
Any clue ?
I've forced a level 0 dump of this disk for tonight, maybe that will help.
===
amandad: debug 1 pid 18824 ruid 0 euid 0 start time Tue Feb 27 20:00:04
2001
amandad: version 2.4.2p1
amandad: build: VERSION="Amanda-2.4.2p1"
amandad:BUILT_DATE="Mon Jan 29 11:24:48 CET 2001"
amandad:BUILT_MACH="Linux zeus 2.2.16 #3 Thu Nov 9 09:57:31 CET
2000 i686 unknown"
amandad:CC="gcc"
amandad: paths: bindir="/volume/amanda/bin" sbindir="/volume/amanda/sbin"
amandad:libexecdir="/volume/bin" mandir="/volume/amanda/man"
amandad:AMANDA_TMPDIR="/tmp/amanda" AMANDA_DBGDIR="/tmp/amanda"
amandad:CONFIG_DIR="/volume/amanda/etc/amanda" DEV_PREFIX="/dev/"
amandad:RDEV_PREFIX="/dev/" DUMP="/sbin/dump"
amandad:RESTORE="/sbin/restore" SAMBA_CLIENT="/usr/bin/smbclient"
amandad:GNUTAR="/bin/gtar" COMPRESS_PATH="/bin/gzip"
amandad:UNCOMPRESS_PATH="/bin/gzip" MAILER="/usr/bin/Mail"
amandad:listed_incr_dir="/usr/local/var/amanda/gnutar-lists"
amandad: defs: DEFAULT_SERVER="zeus" DEFAULT_CONFIG="DailySet1"
amandad:DEFAULT_TAPE_SERVER="zeus"
amandad:DEFAULT_TAPE_DEVICE="/dev/rmt/3hn" HAVE_MMAP HAVE_SYSVSHM
amandad:LOCKING=POSIX_FCNTL SETPGRP_VOID DEBUG_CODE
amandad:DEBUG_FILE_WITH_PID BSD_SECURITY USE_AMANDAHOSTS
amandad:CLIENT_LOGIN="root" FORCE_USERID HAVE_GZIP
amandad:COMPRESS_SUFFIX=".gz" COMPRESS_FAST_OPT="--fast"
amandad:COMPRESS_BEST_OPT="--best" UNCOMPRESS_OPT="-dc"
got packet:
Amanda 2.4 REQ HANDLE 000-0006E898 SEQ 983300403
SECURITY USER root
SERVICE sendsize
OPTIONS maxdumps=2;hostname=zeus;
GNUTAR sda6 0 1970:1:1:0:0:0 -1 exclude-list=/usr/local/lib/amanda/exclude.gtar
GNUTAR sda6 0 1970:1:1:0:0:0 -1 exclude-list=/usr/local/lib/amanda/exclude.gtar
sending ack:
Amanda 2.4 ACK HANDLE 000-0006E898 SEQ 983300403
bsd security: remote host james.jason.nl user root local user root
amandahosts security check passed
amandad: running service "/volume/bin/sendsize"
amandad: sending REP packet:
Amanda 2.4 REP HANDLE 000-0006E898 SEQ 983300403
OPTIONS maxdumps=2;
sda6 0 SIZE 4611708
amandad: got packet:
Amanda 2.4 ACK HANDLE 000-0006E898 SEQ 983300403
amandad: pid 18824 finish time Tue Feb 27 20:01:20 2001
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicampoliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist*Please* write to mailing lists, not to me
Currently listening to: the Smashing Pumpkins - Cash Car Star (Friends Enemies of
Modern Mu)
Gerhard, @jasongeo.com == The Acoustic Motorbiker ==
--
__O Soon I discovered that this rock thing was true
=`\, Jerry Lee Lewis was the devil
(=)/(=) Jesus was an architect previous to his career as a prophet
All of a sudden, I found myself in love with the world
So there was only one thing that I could do
To ding a ding dang my dang a long ling long
Re: sednsize problem
* Alexandre Oliva [EMAIL PROTECTED] (Wed, Feb 28, 2001 at 09:22:10AM -0300) On Feb 28, 2001, Gerhard den Hollander [EMAIL PROTECTED] wrote: GNUTAR sda6 0 1970:1:1:0:0:0 -1 exclude-list=/usr/local/lib/amanda/exclude.gtar GNUTAR sda6 0 1970:1:1:0:0:0 -1 exclude-list=/usr/local/lib/amanda/exclude.gtar Which I take to ask (twice ?) for a level 0 dump Yep. Which is totally unexpected to me. It points to some problem in planner, on the server. Are you using any unusual dumptype options for this disk? No, not really (and it has been working fine for weeks. I did ^C a test amdump for this config during the estimate phase. Could it be that amandates is corrupt ? It looks OK to me. Planner runs on the server right ? How does planner figure out which levels to ask for ? /tmp/amanda/* on the server doesn't offer anything if I grep on it. the share/config/hostname/diskname/info file for this disk looks like version: 0 command: 5 full-rate: 516.00 584.00 506.00 full-comp: 0.693692 0.663403 0.537524 incr-rate: 610.00 184.00 505.00 incr-comp: 0.806327 0.200776 0.725205 stats: 0 4861780 3372576 6527 982954990 13 MAM0127 last_level: 0 1 // The 2 disks that give this weird problem both have a command: 5 all other disks have a command: 0 What is the impact if I remove the info file for the 2 offending disks ? Currently listening to: the Smashing Pumpkins - Blue Skies Bring Tears (heavy (Friends Enemies of Modern Mu) Gerhard, @jasongeo.com == The Acoustic Motorbiker == -- __O Some say the end is near. =`\, Some say we'll see armageddon soon (=)/(=) I certainly hope we will I could use a vacation
Re: amanda reports BogusMonth 0, 0
* Aleksandr Vladimirskiy [EMAIL PROTECTED] (Wed, Feb 28, 2001 at 09:36:12AM -0500)
I am getting a results missing message from amanda as well as the date
is being reported to be "BogusMonth 0, 0". I ran amcheck and it went
through fine. I am including the report amdump generates in the hopes
someone might suggest a way to troubleshoot. Thanks in advance...
Well, apparently the file amreport uses to geenrate the report from is
empty, since it didn;t find a proper month, it gives you bogusmonth as a
result.
check the log directory under wehrever you isnatleld amanda, and feed the
file log/log.20010227.0 (or something like it) to amreport -l
BTW,
I see duplicate entries in the below list.
*** THE DUMPS DID NOT FINISH PROPERLY!
These dumps were to tapes .
Tonight's dumps should go onto 1 tape: a new tape.
FAILURE AND STRANGE DUMP SUMMARY:
host /dev/dsk/c0t0d0s0 RESULTS MISSING
host /dev/dsk/c0t1d0s0 RESULTS MISSING
host /dev/md/dsk/d0 RESULTS MISSING
host /dev/md/dsk/d0 RESULTS MISSING
host /dev/md/dsk/d6 RESULTS MISSING
STATISTICS:
Total Full Daily
Dump Time (hrs:min)0:00 0:00 0:00 (0:00 start)
Output Size (meg) 0.00.00.0
Original Size (meg) 0.00.00.0
Avg Compressed Size (%) -- -- --
Tape Used (%) 0.00.00.0
Filesystems Dumped0 0 0
Avg Dump Rate (k/s) -- -- --
Avg Tp Write Rate (k/s) -- -- --
DUMP SUMMARY:
DUMPER STATS
TAPER STATS
HOSTNAME DISK L ORIG-KB OUT-KB COMP% MMM:SS KB/s
MMM:SS KB/s
-- --
--
host -/dsk/c0t0d0s0MISSING
host -/dsk/c0t1d0s0MISSING
host /dev/md/dsk/d0MISSING
host /dev/md/dsk/d6MISSING
host /dev/md/dsk/d0MISSING
(brought to you by Amanda version 2.4.1p1)
Kind regards,
--
Gerhard den Hollander Phone +31-10.280.1515
Technical Support Jason Geosystems BV Fax +31-10.280.1511
(When calling please note: we are in GMT+1)
[EMAIL PROTECTED] POBox 1573
visit us at http://www.jasongeo.com 3000 BN Rotterdam
JASON...#1 in Reservoir CharacterizationThe Netherlands
This e-mail and any attachment is/are intended solely for the named
addressee(s) and may contain information that is confidential and privileged.
If you are not the intended recipient, we request that you do not
disseminate, forward, distribute or copy this e-mail message.
If you have received this e-mail message in error, please notify us
immediately by telephone and destroy the original message.
Re: holding disk/taper semantics?
* Carey Jung [EMAIL PROTECTED] (Fri, Mar 02, 2001 at 07:06:26AM -0600) Could someone please clarify the holding disk/taper semantics? It appears that amanda deletes files from the holding disk as they are taped off, rather than after they are ALL successfully taped off. We noticed this when we had a tape problem. When we put a good tape in and tried to re-flush the files, they had disappeared from the holding disk. Watching the behavior since then seems to confirm this. What amanda does (or should do) is: Dumper dumps mutliple file(systems) to holding disk taper writes them one by one to tape, and after a susccesful write, removes them from disk. so say holdingdisk holds A,B,C taper tapes A to tape. taper reports succesfull write of A now A gets deleted from holding disk leaving B,C In my case, I am dumping to LTO tapes, which hold upto 150G I don;t have a 150G holding disk so if taper should only throw away *after* dumping everything to tape, I would run out of holding disk space, whihc is seriously bad as it severly degrades performance. Regards, Carey Currently listening to: artist - Track 08 (title) Gerhard, @jasongeo.com == The Acoustic Motorbiker == -- __O If your watch is wound, wound to run, it will =`\, If your time is due, due to come, it will (=)/(=) Living this life, is like trying to learn latin in a chines firedrill
Re: ((((( hard or soft )))))
* Chris Marble [EMAIL PROTECTED] (Fri, Mar 02, 2001 at 07:56:00AM -0800) radar wrote: i have a (hp c1537a dds3 125m 4mm) tapedrive that can hold 12 gig uncompressed and says that it can compress up to 24. i think you know it all. my thougts was, hey, let the hardware do the compression so your system is not under such a heavy load. I was going that way for a while - tape drive doing the compression. But I have one computer with 30Gb of data that's mostly already been gzipped. The choice you make is between extra load on your server/clients or let the hardware do the job. For our big box (~ 500G of data [1] ) I have to let the LTO drive do the compression, if I use software compression on that box, the load becomes so high, the backup isn;t finished within 24 hours ;). [1] spread out over serveral disks and tar-slices, so it's not backing all ~500G every time ;) Currently listening to: 8-Cocaine Decisions Gerhard, @jasongeo.com == The Acoustic Motorbiker == -- __O Standing above the crowd, he had a voice so strong and loud =`\, we'll miss him (=)/(=) Ranting and pointing his finger, At everything but his heart we'll miss him
Re: Backup tape issue
* John R. Jackson [EMAIL PROTECTED] (Sat, Mar 03, 2001 at 10:31:14AM -0500) With that all said, he would like to be able to put ANY tape in the drive and have it succeed, basicly ignoring the tape lables. ... Then I assume you're not going to be using incrementals but doing a full dump of everything every day, right? Because this won't work if there are incrementals. You'll end up clobbering something you need for a restore. In the extreme case, your boss wants to be able to use the same tape every day. To do that with Amanda, set dumpcycle to 0 and tapecycle to 1. You may have more tapes listed in tapelist (via amlabel) and, as I understand it, Amanda will accept any of them. But you are seriously fucked if you have only one tape, and the disk you're backing up dies while writing the current backup over the previous one. I suggest a (smart-)moneky proof system, simply labelling the tapes *MONDAY* *TUESDAY* .. *FRIDAY* and go with that. Setting dumpcycle to 0 and tapecycle to 1 will ensure that it will write on whatever tape is in the drive. But clearly labelling them, and training people to put thet tape with the current day in the tapedrive should minimize the risk of the above scenario. Richard G. Duvall John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED] Currently listening to: Godspeed you black emperor - Levez vos skinny fists.. CD1-2 Gerhard, @jasongeo.com == The Acoustic Motorbiker == -- __O Get one man to ride his bycicle =`\, and there is hope for the human race (=)/(=) A.A.M. van Gulik
Re: Backup time
* Olivier Collet [EMAIL PROTECTED] (Wed, Mar 07, 2001 at 10:39:21AM +0100) Hello, First I would like to thanks everybody in this mailing list. I have a doubt. I launched the backup yesterday at 18:00 and today it is 10:35 and it is still not done! I have put 'only' three servers in this backup as a test. Is it normal it is so slow ? How can I tell the backup is still going on ? The Bandwith I put in the amanda config is 5000 kbitsec, the network is 100 Mbits. What also is strange is I run snmp deamon on amanda server, and I read the info in cricket, and it shows me it uses not more than 2 Mbit/sec.Is this normal or am I missing something ? Thanks what does amstatus yourconfig tell you (on the server) ? regards Olivier Collet Currently listening to: 09 - The Nile Song Gerhard, @jasongeo.com == The Acoustic Motorbiker == -- __O If your watch is wound, wound to run, it will =`\, If your time is due, due to come, it will (=)/(=) Living this life, is like trying to learn latin in a chines firedrill
Re: two dumps in one day
* John R. Jackson [EMAIL PROTECTED] (Tue, Mar 27, 2001 at 04:01:42PM -0500) Or you could just "know" that amrecover lies and whatever tape it tells you to load, go back to your reports and load the "right" tape. The amrestore than amidxtaped calls searches for the image by name anyway. It doesn't check that you loaded the tape amrecover told you to. So if the morning tape has the disk I need as file image 3 and the evening tape (that amrecover expects) has the disk as file image 94 it will simply fsf until it finds the named image (image 3 in this case) in stead of blindly fsf-ing to image 94 ? Now that is a handy feature .. Kind regards, -- Gerhard den Hollander Phone +31-10.280.1515 Technical Support Jason Geosystems BV Fax +31-10.280.1511 (When calling please note: we are in GMT+1) [EMAIL PROTECTED] POBox 1573 visit us at http://www.jasongeo.com 3000 BN Rotterdam JASON...#1 in Reservoir CharacterizationThe Netherlands This e-mail and any attachment is/are intended solely for the named addressee(s) and may contain information that is confidential and privileged. If you are not the intended recipient, we request that you do not disseminate, forward, distribute or copy this e-mail message. If you have received this e-mail message in error, please notify us immediately by telephone and destroy the original message.
Re: Amanda with two tape devices
* Miguel Nuno de Almeida Vasconcelos Ribeiro [EMAIL PROTECTED] (Thu, Apr 05, 2001 at 09:46:35AM +0100) Can it be done ? Yes Can amanda use who tape devices to perform a single backup? No What can I expect of it? Good performance Where can I find Info ? Here. Basically what you do (or what I did) is to set up different configurations (differtn disklists/tapelists) for each tapedevice, and work from there. Half your diskspace for tape1, the other ahlf for tape2 (or if you have different capaicty tapedrives, simply use more for one than the other) Currently listening to: Phish - Layla (11-29-98) Gerhard, @jasongeo.com == The Acoustic Motorbiker == -- __O Standing above the crowd, he had a voice so strong and loud =`\, we'll miss him (=)/(=) Ranting and pointing his finger, At everything but his heart we'll miss him
Re: large filesystem problems
* Jeff Heckart [EMAIL PROTECTED] (Thu, Apr 05, 2001 at 09:42:50AM -0400) Hello. I have recently added a disk that is roughly 60gb in size. One of the partitions is about 51gb. This particular machine is running bsdi4.2. This and the tapeserver are running amanda 2.4.2. My tape server is a redhat 6.1 machine, and is successfully backing up three other systems. I am using dump, no compression, and level 0. When I run amdump, everything appears to be ok, but I use amcheck and it tells me that it is "getting estimate", on both the large 51gb part, and the smaller 50mb part. When I try to backup only the 50mb part, it runs perfectly fine. This has all started by introducing this large partition. I have spent a couple of hours looking through the mailing list and found people with similiar problems, but they all seemed to be using tar. I am not. Same problem. The getting estimate takes forever and then some, so you may have to change your etime to someting larger (7200 for 2 hours). (and yes, i wouldn;t be surprrised if it indeed takes 2 hours to ewstimate a latrge disk, esp if it's full and you need to get 3 estimate (level 0, current incremental level, current incremental level +1). Alternatively you can patch client-src/sendsize.c as below, define USE_GENERIC_CALCSIZE and recompile sendsize /* Now in the child process */ if(strcmp(est-program, "DUMP") == 0) dump_calc_estimates(est); else #ifndef USE_GENERIC_CALCSIZE # ifdef SAMBA_CLIENT if (strcmp(est-program, "GNUTAR") == 0 est-amname[0] == '/' est-amname[1] == '/') smbtar_calc_estimates(est); else # endif # ifdef GNUTAR if (strcmp(est-program, "GNUTAR") == 0) gnutar_calc_estimates(est); else # endif #endif generic_calc_estimates(est); Kind regards, -- Gerhard den Hollander Phone +31-10.280.1515 Technical Support Jason Geosystems BV Fax +31-10.280.1511 (When calling please note: we are in GMT+1) [EMAIL PROTECTED] POBox 1573 visit us at http://www.jasongeo.com 3000 BN Rotterdam JASON...#1 in Reservoir CharacterizationThe Netherlands This e-mail and any attachment is/are intended solely for the named addressee(s) and may contain information that is confidential and privileged. If you are not the intended recipient, we request that you do not disseminate, forward, distribute or copy this e-mail message. If you have received this e-mail message in error, please notify us immediately by telephone and destroy the original message.
Re: linux kernel-2.4.2 issue
* John Palkovic [EMAIL PROTECTED] (Thu, Apr 05, 2001 at 12:08:23PM -0500) My amanda backup server runs Debian GNU/linux. I've had it running kernel version 2.2.16 for months and it has been working great, backing up a small network of ten machines. Kudos to the Amanda team. I recently compiled a 2.4.2 kernel for the backup server. If I boot this kernel, then one of my clients (coredump) fails consistently to backup. The amanda mail report says "FAILED [nak error:amandad busy]". All partitions on coredump fail with this error. Further investigation shows that the backups for coredump fail in the estimation phase. Coredump is also a debian system, kernel 2.4.3-pre8. If I revert to kernel version 2.2.16 on the amanda server, then coredump backs up with no errors. Obviously I'm staying with linux kernel 2.2.16 on the server for now. I can provide more detailed information if anyone is interested. Hmm, This 2.4 kernel, does this also imply glibc2.2 ? I have a couple of suse 7.1 boxes (kernel 2.4.X, glibc2.2) and amanda works fine. I did however reinstall the cvorrect tar version (1.13.19) and I use the sendisze hack (see prebious post about large file systems). So, maybe you need to check if you are using the ciorrect tar version. Kind regards, -- Gerhard den Hollander Phone +31-10.280.1515 Technical Support Jason Geosystems BV Fax +31-10.280.1511 (When calling please note: we are in GMT+1) [EMAIL PROTECTED] POBox 1573 visit us at http://www.jasongeo.com 3000 BN Rotterdam JASON...#1 in Reservoir CharacterizationThe Netherlands This e-mail and any attachment is/are intended solely for the named addressee(s) and may contain information that is confidential and privileged. If you are not the intended recipient, we request that you do not disseminate, forward, distribute or copy this e-mail message. If you have received this e-mail message in error, please notify us immediately by telephone and destroy the original message.
Re: linux kernel-2.4.2 issue
* John Palkovic [EMAIL PROTECTED] (Thu, Apr 05, 2001 at 02:04:07PM -0500) Tar is coredump:/tmp tar --version tar (GNU tar) 1.12 on both server and client. The amanda patches were applied to this tar. OK, I remember going to 1.13.19 after someone here suggested that this was better than (even_ 1.12 w/ amanda patches because under some strange circumstances it could coredump. When I upped my boxes to suse 7.1/2.4/glibc2.2 I also got a new tar (1.13.whatever0 and noticed it dump core everytime. When I went and copied my 1.13.19 over the current tar things started functioning again. I never tried booting back to 2.2.18 and see what happened then. It woudln't surprise me if there is something in the combo 2.4kernel/glibc2.2/amanda2.4.2 that causes a coredump in the 1.12 So, maybe you need to check if you are using the ciorrect tar version. If I do nothing but boot a kernel 2.4.2 on the server, the backups fail. If I revert to 2.2.16 on the server, everything is fine. Well, checking a new tar version is a small effort. If you want I can send you my binary, so you can drop it in and see if the dumops work again. Currently listening to: Porcupine Tree - Untitled Gerhard, [@jasongeo.com] == The Acoustic Motorbiker == -- __O Hypocrites and Zealots =`\, are struggling for the throne, (=)/(=) Kings and queens and presidents All younger then the Stones
Holding Disk Question
Im currently using a single (big) holding disk. I have 2 smaller disks, that I'd like to use as holding disks. But the samller disks will not be able to hold the big 0 dumps. According to the docs, the holding disks are used in a round-robin way (dump 1 to HD1, dump 2 - HD 2, dump3 - HD3, dump4 - HD1 c c ) What happens if my dump is supposed to go to HD1, but is way too big for HD1, but would easily fit on HD3 ? Will amanda use the big Holding disk ? Currently listening to: Flying Frog Brigade - Here's to the Man (August 29 - New York City) Gerhard, @jasongeo.com == The Acoustic Motorbiker == -- __O Some say the end is near. =`\, Some say we'll see armageddon soon (=)/(=) I certainly hope we will I could use a vacation
Re: Holding Disk Question
* Alexandre Oliva [EMAIL PROTECTED] (Thu, Apr 12, 2001 at 07:45:31AM -0300) What happens if my dump is supposed to go to HD1, but is way too big for HD1, but would easily fit on HD3 ? Will amanda use the big Holding disk ? I suppose so. Now that's what I call a honest and fair answer ;) Kind regards, -- Gerhard den Hollander Phone +31-10.280.1515 Technical Support Jason Geosystems BV Fax +31-10.280.1511 (When calling please note: we are in GMT+1) [EMAIL PROTECTED] POBox 1573 visit us at http://www.jasongeo.com 3000 BN Rotterdam JASON...#1 in Reservoir CharacterizationThe Netherlands This e-mail and any attachment is/are intended solely for the named addressee(s) and may contain information that is confidential and privileged. If you are not the intended recipient, we request that you do not disseminate, forward, distribute or copy this e-mail message. If you have received this e-mail message in error, please notify us immediately by telephone and destroy the original message.
Re: Holding Disk Question
* John R. Jackson [EMAIL PROTECTED] (Thu, Apr 12, 2001 at 11:28:03AM -0500) Im currently using a single (big) holding disk. I have 2 smaller disks, that I'd like to use as holding disks. But the samller disks will not be able to hold the big 0 dumps. According to the docs, the holding disks are used in a round-robin way (dump 1 to HD1, dump 2 - HD 2, dump3 - HD3, dump4 - HD1 c c ) According to the code (you actually read and believed the docs? :-): Oddly enough, yes ;) It's in the comments in the example amanda.conf. /* find the holdingdisk with the fewest active dumpers and among * those the one with the biggest free space So you should not have any trouble using all three as a "pool". It might work even better if you set the holding disk chunksize down so they can be split up into pieces and scattered around. Will that work ? If I specify a chunksize of 1G, and dump a 9G backup, will it stick 3 chunks on each of the 3 hilding disks ? That would be really impressive ... What "docs" did you find the round-robin described? I seem to remember seeing that, too, but can't find it now and would like to get it updated. Line 82 and on in example/amanda.conf in the source tree # Specify holding disks. These are used as a temporary staging area for # dumps before they are written to tape and are recommended for most sites. # The advantages include: tape drive is more likely to operate in streaming # mode (which reduces tape and drive wear, reduces total dump time); multiple # dumps can be done in parallel (which can dramatically reduce total dump time. # The main disadvantage is that dumps on the holding disk need to be flushed # (with amflush) to tape after an operating system crash or a tape failure. # If no holding disks are specified then all dumps will be written directly # to tape. If a dump is too big to fit on the holding disk than it will be # written directly to tape. If more than one holding disk is specified then # they will all be used round-robin. ^ Thanks, Gerhard John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED] Currently listening to: Pearl Jam - 11 Off He Goes (VA Beach 8_3_00) Gerhard, @jasongeo.com == The Acoustic Motorbiker == -- __O i hurt myself today to see if i still feel =`\, i focus on the pain the only thing that's real (=)/(=) the needle tears a hole the old familiar sting try to kill it all away but i remember everything
Re: Holding Disk Question
* John R. Jackson [EMAIL PROTECTED] (Fri, Apr 13, 2001 at 07:06:20AM -0500) Will that work ? No. I'm planning on getting a job in sales, so I'm just making all this up. :-) Good ;) If I specify a chunksize of 1G, and dump a 9G backup, will it stick 3 chunks on each of the 3 hilding disks ? Not necessarily. Note that it takes both the number of active dumpers (how busy) each holding disk has and the amount of free space. So there are dynamics involved that cannot be known until runtime. But based on that one comment and a quick glance at the code, I would expect it to do more or less "the right thing". Good. BTW, does the chunksize have any performance benefiot/penalty ? Or is it more a convenience (as in this case where picking the right chunksize will have the load indeed split over multiple disks) That would be really impressive ... It's Amanda. What did you expect? :-) Miracles Gerhard, @jasongeo.com == The Acoustic Motorbiker == -- __O Some say the end is near. =`\, Some say we'll see armageddon soon (=)/(=) I certainly hope we will I could use a vacation
Re: Holding Disk Question
* John R. Jackson [EMAIL PROTECTED] (Fri, Apr 13, 2001 at 07:44:09AM -0500) Or is it more a convenience (as in this case where picking the right chunksize will have the load indeed split over multiple disks) The original intent was to support file systems that cannot handle files larger than 32 KBytes (e.g. ext2 on Linux). But, as with all good ideas larger than 2G I assume ;) :-), it turns out to have some other nice benefits, such as what you're trying to do. Well, it's all in the amanda.conf now, We'll see tonight how it goes Currently listening to: The Radio (http://www.arrow.nl/specials/GVGVplaylist.htm) Gerhard, @jasongeo.com == The Acoustic Motorbiker == -- __O If your watch is wound, wound to run, it will =`\, If your time is due, due to come, it will (=)/(=) Living this life, is like trying to learn latin in a chines firedrill
Holding disks getting full ..
I've set amanda.conf to use all of the holding disk, minus 1Gb
holdingdisk hd2 {
comment "smaller holding disk"
directory "/eighteen1/amanda/lto"
use -1Gb
chunksize 250Mb
}
However, I am getting diskfull errors on that disk when amanda is backing
up ..
Now I know there is another job running on that disk, that uses up quite
some diskspace, but that job stops when the freediskspace is less than 500M
and continues after that.
(i checked ;) )
However, amanda happily continues dumping until the disk is full, thena
borts the dump, and retries later on.
Any clue ?
Currently listening to: The Tea Party - Live - Egyptian Prayer - Halcyon Days (New
Years Eve Buffalo)
Gerhard, @jasongeo.com == The Acoustic Motorbiker ==
--
__O If your watch is wound, wound to run, it will
=`\, If your time is due, due to come, it will
(=)/(=) Living this life, is like trying to learn latin
in a chines firedrill
Re: Holding disks getting full ..
* Gerhard den Hollander [EMAIL PROTECTED] (Fri, Apr 20, 2001 at 09:54:04AM +0200)
I've set amanda.conf to use all of the holding disk, minus 1Gb
holdingdisk hd2 {
comment "smaller holding disk"
directory "/eighteen1/amanda/lto"
use -1Gb
chunksize 250Mb
}
However, I am getting diskfull errors on that disk when amanda is backing
up ..
Now I know there is another job running on that disk, that uses up quite
some diskspace, but that job stops when the freediskspace is less than 500M
and continues after that.
(i checked ;) )
However, amanda happily continues dumping until the disk is full, thena
borts the dump, and retries later on.
Any clue ?
To be slightly more exact.
the sequence of events is:
amdump starts dumping [disk space 3G ]
[dump is estimated to be 2G]
amdump dumps some parts [disk space 2G ]
other program starts filling the disk, while amanda is dumping
[diskspace is now 500M, other program waits till enough free
diskspace]
amdump continues dumping
disk full ..
So it looks like amdump checks if there is enough space on the holding disk
before it starts dumping,
and then simply continues dumping whitout checking if the holding disk
becomes full, until it runs in a diskfull error and aborts the dump.
The right thing (imo) would be to check every time a new chunk is written,
and if the chunk to be written would fail the holding disk free space
criteria, it should abort the dump.
Thoughts ?
Currently listening to: Gone-JJJ live
Gerhard, @jasongeo.com == The Acoustic Motorbiker ==
--
__O Got no religion, don't need no friends
=`\, Got all I want and I got no need to pretend
(=)/(=) Don't try to reach me, 'cause I'd tear up your mind
I've seen the future and I leave it all behind
Re: Ultrium LTO tape drive
Have you done (are you doing) backups with different programs (Arkeia, taper, tar etc) or other OSes than linux? No. Yes. :) yes, yes If yes, what is your experience about backup speed? Amanda is slow, compared to ufsdump/tar straight to tape, because amanda does a lot more. If using a holding disk, and having 2 - 4 fumpers dump to holding disk, and from holding disk to tape, you can get approx 11/12 Kbps (4 dumps at 2 -3 Kbps to hodling disk and from HD to tape at 11/12 Kbps) LTO rules ;) Kind regards, -- Gerhard den Hollander Phone +31-10.280.1515 Technical Support Jason Geosystems BV Fax +31-10.280.1511 (When calling please note: we are in GMT+1) [EMAIL PROTECTED] POBox 1573 visit us at http://www.jasongeo.com 3000 BN Rotterdam JASON...#1 in Reservoir CharacterizationThe Netherlands This e-mail and any attachment is/are intended solely for the named addressee(s) and may contain information that is confidential and privileged. If you are not the intended recipient, we request that you do not disseminate, forward, distribute or copy this e-mail message. If you have received this e-mail message in error, please notify us immediately by telephone and destroy the original message.
Re: Holding disks getting full ..
* Alexandre Oliva [EMAIL PROTECTED] (Fri, Apr 20, 2001 at 11:08:36AM -0300) So it looks like amdump checks if there is enough space on the holding disk before it starts dumping, Yep. and then simply continues dumping whitout checking if the holding disk becomes full, until it runs in a diskfull error and aborts the dump. It would fall over to another holding disk, if you had one. The right thing (imo) would be to check every time a new chunk is written, and if the chunk to be written would fail the holding disk free space criteria, it should abort the dump. And end up aborting the dump anyway? What's the advantage? 1) it's quicker Aborting a dump after 3 G has been written to disk, or aborting after 4G has been written does make a difference. 2) It prevents diskfulls from happening, some other programs are suign the disk for (very small) scratch space, and they fall over if the disk is full (yes, I know, fix those programs ;) ) ... 3) The Right Thing (tm) if you have multiple hodling disks is t check before starting to write the chunk whether you're below the watermark, and if the next chunk would bring you below the watermark, switch to the enxt holding disk. No errors, no errors in the syslog. Kind regards, -- Gerhard den Hollander Phone +31-10.280.1515 Technical Support Jason Geosystems BV Fax +31-10.280.1511 (When calling please note: we are in GMT+1) [EMAIL PROTECTED] POBox 1573 visit us at http://www.jasongeo.com 3000 BN Rotterdam JASON...#1 in Reservoir CharacterizationThe Netherlands This e-mail and any attachment is/are intended solely for the named addressee(s) and may contain information that is confidential and privileged. If you are not the intended recipient, we request that you do not disseminate, forward, distribute or copy this e-mail message. If you have received this e-mail message in error, please notify us immediately by telephone and destroy the original message.
Re: Backup of large disk arrays with AMANDA?????
* Hartmann, O. [EMAIL PROTECTED] (Mon, Apr 23, 2001 at 10:48:00AM +0200) Well, I would like to ask for some hints or simply a fact-statement: Is AMANDA capable of spreading a large volume over several tapes with gtar like gtar does this using the multivolume mechanism? How to configure No (or Not yet, take your pick) this ability if possible? Please be aware of the following fact: I definitely can not split this array into smaller pieces because it is not possible to split them due the high data fluctuation. I have the same porblem (a 450G diskarray) I use gtar to split the disk in smaller pieces. I still have one 450G partition, but I have a whole slew of toplevel directories, and simply specify each of them as a target for tar. (some of those are too big even then, so I repeat the trick for the second level dirs). And yes, this sometimes mean I have to add or remove some entries from disklist. I can live with that ;). My disklist looks something like host/bigdisk/a high-tar host/bigdisk/b high-tar host/bigdisk/c high-tar host/bigdisk/d high-tar host/bigdisk/e high-tar host/bigdisk/e/1high-tar host/bigdisk/e/2high-tar host/bigdisk/e/3high-tar host/bigdisk/e/4high-tar host/bigdisk/e/5high-tar host/bigdisk/f high-tar host/bigdisk/g high-tar c c .. (where a..g are replaced with the names of my toplevel dirs and 1..5 replaced with the secondlevel dirs .. you get the picture) Kind regards, -- Gerhard den Hollander Phone +31-10.280.1515 Technical Support Jason Geosystems BV Fax +31-10.280.1511 (When calling please note: we are in GMT+1) [EMAIL PROTECTED] POBox 1573 visit us at http://www.jasongeo.com 3000 BN Rotterdam JASON...#1 in Reservoir CharacterizationThe Netherlands This e-mail and any attachment is/are intended solely for the named addressee(s) and may contain information that is confidential and privileged. If you are not the intended recipient, we request that you do not disseminate, forward, distribute or copy this e-mail message. If you have received this e-mail message in error, please notify us immediately by telephone and destroy the original message.
Re: STRANGE DUMP SUMMARY
* [EMAIL PROTECTED] [EMAIL PROTECTED] (Thu, Apr 26, 2001 at 04:36:29AM -0700) HI, I got the following, and was wondering what the Strange meant, and what I could do about the File too large failures : File too large: _ your dumping a 2G file to your linux holding disk, Either upgrade your linux kernel to 2.4 (e.g. suse 7.1) or set the chunksize for your holding disk to something less than 2G. As for the error messages on pipe10's /dev/hda1 either you were dumping a disk that had activity (lot of deleting of files from the looks of it (e.g. an overnight make job) or your disk is dying. Kind regards, -- Gerhard den Hollander Phone +31-10.280.1515 Technical Support Jason Geosystems BV Fax +31-10.280.1511 (When calling please note: we are in GMT+1) [EMAIL PROTECTED] POBox 1573 visit us at http://www.jasongeo.com 3000 BN Rotterdam JASON...#1 in Reservoir CharacterizationThe Netherlands This e-mail and any attachment is/are intended solely for the named addressee(s) and may contain information that is confidential and privileged. If you are not the intended recipient, we request that you do not disseminate, forward, distribute or copy this e-mail message. If you have received this e-mail message in error, please notify us immediately by telephone and destroy the original message.
Re: Linus Torvald's opinion on Dump.
* Daniel David Benson [EMAIL PROTECTED] (Fri, Apr 27, 2001 at 06:27:11PM -0700)
Why not? Have you seen/had problems with recent versions of gnu tar, or
Sun's bundled tar? I have seen problems with versions of tars
Unless gnutar is the latest (1.13.19 I think.
Chances ae it will screw you over backward (that is SEGV) whern you really
need it to read stuff back from tape.
Sun tar has other porblems (try using suntar on the latest qt snapshot).
Havoing said that,
since i use reiserfs, I have to use tar, and have never had problems with
it.
Configuring amanada to use tar iso dump is a matter of changing the key in
your dumplist.
As for tar being twice as slow as dump,
just use the modified sendsize.c which uses calcsize iso tar to estimate
dumpsizes.
It cuts 4 - 5 hours of my dumptimes.
Kind regards,
--
Gerhard den Hollander Phone +31-10.280.1515
Technical Support Jason Geosystems BV Fax +31-10.280.1511
(When calling please note: we are in GMT+1)
[EMAIL PROTECTED] POBox 1573
visit us at http://www.jasongeo.com 3000 BN Rotterdam
JASON...#1 in Reservoir CharacterizationThe Netherlands
This e-mail and any attachment is/are intended solely for the named
addressee(s) and may contain information that is confidential and privileged.
If you are not the intended recipient, we request that you do not
disseminate, forward, distribute or copy this e-mail message.
If you have received this e-mail message in error, please notify us
immediately by telephone and destroy the original message.
/*
* Amanda, The Advanced Maryland Automatic Network Disk Archiver
* Copyright (c) 1991-1998 University of Maryland at College Park
* All Rights Reserved.
*
* Permission to use, copy, modify, distribute, and sell this software and its
* documentation for any purpose is hereby granted without fee, provided that
* the above copyright notice appear in all copies and that both that
* copyright notice and this permission notice appear in supporting
* documentation, and that the name of U.M. not be used in advertising or
* publicity pertaining to distribution of the software without specific,
* written prior permission. U.M. makes no representations about the
* suitability of this software for any purpose. It is provided as is
* without express or implied warranty.
*
* U.M. DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL
* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL U.M.
* BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
* WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION
* OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN
* CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
*
* Authors: the Amanda Development Team. Its members are listed in a
* file named AUTHORS, in the root directory of this distribution.
*/
/*
* $Id: sendsize.c,v 1.97.2.13 2000/10/11 02:08:26 martinea Exp $
*
* send estimated backup sizes using dump
*/
#include amanda.h
#include pipespawn.h
#include amandates.h
#include getfsent.h
#include version.h
#ifdef SAMBA_CLIENT
#include findpass.h
#endif
#ifdef HAVE_SETPGID
# define SETPGRP setpgid(getpid(), getpid())
# define SETPGRP_FAILED() do { \
dbprintf((setpgid(%ld,%ld) failed: %s\n, \
(long)getpid(), (long)getpid(), strerror(errno)));\
} while(0)
#else /* () line 0 */
#if defined(SETPGRP_VOID)
# define SETPGRP setpgrp()
# define SETPGRP_FAILED() do { \
dbprintf((setpgrp() failed: %s\n, strerror(errno))); \
} while(0)
#else
# define SETPGRP setpgrp(0, getpid())
# define SETPGRP_FAILED() do { \
dbprintf((setpgrp(0,%ld) failed: %s\n,\
(long)getpid(), strerror(errno)));\
} while(0)
#endif
#endif
typedef struct level_estimates_s {
time_t dumpsince;
int estsize;
int needestimate;
} level_estimate_t;
typedef struct disk_estimates_s {
struct disk_estimates_s *next;
char *amname;
char *dirname;
char *exclude;
char *program;
int spindle;
level_estimate_t est[DUMP_LEVELS];
} disk_estimates_t;
disk_estimates_t *est_list;
#define MAXMAXDUMPS 16
int maxdumps = 1, dumpsrunning = 0;
char *host; /* my hostname from the server */
/* local functions */
int main P((int argc, char **argv));
void add_diskest P((char *disk, int level, char *exclude, int spindle, char *prog));
void calc_estimates P((disk_estimates_t *est));
void free_estimates P((disk_estimates_t *est));
void dump_calc_estimates P((disk_estimates_t *));
void smbtar_calc_estimates P
Re: Linus Torvald's opinion on Dump.
* Jamie Bowden [EMAIL PROTECTED] (Sat, Apr 28, 2001 at 12:20:58PM -0700) On Sat, 28 Apr 2001, Gerhard den Hollander wrote: :* Daniel David Benson [EMAIL PROTECTED] (Fri, Apr 27, 2001 at 06:27:11PM -0700) : : Why not? Have you seen/had problems with recent versions of gnu tar, or : Sun's bundled tar? I have seen problems with versions of tars : :Unless gnutar is the latest (1.13.19 I think. :Chances ae it will screw you over backward (that is SEGV) whern you really :need it to read stuff back from tape. Any version of tar works above the filesystem level, which is slow and problematic in it's own ways many others here have already brought up. True. OTOH tar allows you to back up a 450G partition on 150G capcity tapes w/ amamnda, by splitting it into a (large) number of subslices There's also another issue I'll bring up in response to your next comment. :Sun tar has other porblems (try using suntar on the latest qt snapshot). As others pointed out this is a combo of gnutar vs sun tar. I thankfully don't deal with Solaris anymore. Irix's xfsdump is fast, if a little odd for those not used to it. That's putting it politely ;) .. It took some time for Amanda to correctly work with xfsdump/xfsrestore. And before amanda I had xfsdump SEGV on me when called from a shell script forked from cron (and oddly enough worked fine when started from the command line). I won;t go into a Solaris vs Irix (or Solaris vs SGI) here. Im using both, they both have their strengths, and they both have their weaknesses (Solaris OpenGL excels in hardlocking my machines to name just one) , but fortunately they all dump/tar happily ever after . Kind regards, -- Gerhard den Hollander Phone +31-10.280.1515 Technical Support Jason Geosystems BV Fax +31-10.280.1511 (When calling please note: we are in GMT+1) [EMAIL PROTECTED] POBox 1573 visit us at http://www.jasongeo.com 3000 BN Rotterdam JASON...#1 in Reservoir CharacterizationThe Netherlands This e-mail and any attachment is/are intended solely for the named addressee(s) and may contain information that is confidential and privileged. If you are not the intended recipient, we request that you do not disseminate, forward, distribute or copy this e-mail message. If you have received this e-mail message in error, please notify us immediately by telephone and destroy the original message.
Re: Estimate request timed out - FAILED QUEUE - planner: FAILED
* John R. Jackson [EMAIL PROTECTED] (Wed, May 02, 2001 at 03:52:46PM -0500)
sendsize: debug 1 pid 377632 ruid 5 euid 5 start time Fri Apr 13 20:45:54 2001
...
sendsize: pid 377632 finish time Sat Apr 14 01:39:08 2001
Notice the duration was almost three hours. Amanda gave it 60 minutes
(two disks times 30 minutes per disk). It didn't answer within that
period, so Amanda thought it was dead.
You need to crank up etimeout in amanda.conf.
Or you need to use the modified sendsize that uses calcsize to calculate
the sizes ..
calcsize can do estimates at about 500G per hour (and that's full dump,
incremantal current level and incremental next level).
Tar does about 150G per hour, but that's only for one level .. so it has to
do it 3 times.
So doing 500G estimate with tar takes well over 9 hours.
with calcsize it's done in an hour ..
Attached my modified sendsize.c
Kind regards,
--
Gerhard den Hollander Phone +31-10.280.1515
Technical Support Jason Geosystems BV Fax +31-10.280.1511
(When calling please note: we are in GMT+1)
[EMAIL PROTECTED] POBox 1573
visit us at http://www.jasongeo.com 3000 BN Rotterdam
JASON...#1 in Reservoir CharacterizationThe Netherlands
This e-mail and any attachment is/are intended solely for the named
addressee(s) and may contain information that is confidential and privileged.
If you are not the intended recipient, we request that you do not
disseminate, forward, distribute or copy this e-mail message.
If you have received this e-mail message in error, please notify us
immediately by telephone and destroy the original message.
/*
* Amanda, The Advanced Maryland Automatic Network Disk Archiver
* Copyright (c) 1991-1998 University of Maryland at College Park
* All Rights Reserved.
*
* Permission to use, copy, modify, distribute, and sell this software and its
* documentation for any purpose is hereby granted without fee, provided that
* the above copyright notice appear in all copies and that both that
* copyright notice and this permission notice appear in supporting
* documentation, and that the name of U.M. not be used in advertising or
* publicity pertaining to distribution of the software without specific,
* written prior permission. U.M. makes no representations about the
* suitability of this software for any purpose. It is provided as is
* without express or implied warranty.
*
* U.M. DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL
* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL U.M.
* BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
* WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION
* OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN
* CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
*
* Authors: the Amanda Development Team. Its members are listed in a
* file named AUTHORS, in the root directory of this distribution.
*/
/*
* $Id: sendsize.c,v 1.97.2.13 2000/10/11 02:08:26 martinea Exp $
*
* send estimated backup sizes using dump
*/
#include amanda.h
#include pipespawn.h
#include amandates.h
#include getfsent.h
#include version.h
#ifdef SAMBA_CLIENT
#include findpass.h
#endif
#ifdef HAVE_SETPGID
# define SETPGRP setpgid(getpid(), getpid())
# define SETPGRP_FAILED() do { \
dbprintf((setpgid(%ld,%ld) failed: %s\n, \
(long)getpid(), (long)getpid(), strerror(errno)));\
} while(0)
#else /* () line 0 */
#if defined(SETPGRP_VOID)
# define SETPGRP setpgrp()
# define SETPGRP_FAILED() do { \
dbprintf((setpgrp() failed: %s\n, strerror(errno))); \
} while(0)
#else
# define SETPGRP setpgrp(0, getpid())
# define SETPGRP_FAILED() do { \
dbprintf((setpgrp(0,%ld) failed: %s\n,\
(long)getpid(), strerror(errno)));\
} while(0)
#endif
#endif
typedef struct level_estimates_s {
time_t dumpsince;
int estsize;
int needestimate;
} level_estimate_t;
typedef struct disk_estimates_s {
struct disk_estimates_s *next;
char *amname;
char *dirname;
char *exclude;
char *program;
int spindle;
level_estimate_t est[DUMP_LEVELS];
} disk_estimates_t;
disk_estimates_t *est_list;
#define MAXMAXDUMPS 16
int maxdumps = 1, dumpsrunning = 0;
char *host; /* my hostname from the server */
/* local functions */
int main P((int argc, char **argv));
void add_diskest P((char *disk, int level, char *exclude, int spindle, char *prog));
void calc_estimates P((disk_estimates_t *est));
void free_estimates P((disk_estimates_t *est
Re: Estimate request timed out - FAILED QUEUE - planner: FAILED
* Bernhard R. Erdmann [EMAIL PROTECTED] (Thu, May 03, 2001 at 07:34:01PM +0200) Or you need to use the modified sendsize that uses calcsize to calculate the sizes .. calcsize can do estimates at about 500G per hour (and that's full dump, incremantal current level and incremental next level). Gerhard, what is calcsize? Is it a part of Amanda? calcsize is amandas alternative way of calculating dumpestimates. Im not sure what the status of it is (I think it's no longer officially supported) but it rules. John, Alexandre Is there any chance of getting calcsize actively supprted in 2.5 ? With a configure option to determine whether you want to: - always use dump/tar - use dump for dump estimates, calcsize for tar estimates - use tar for tar estimates, calcsize for dump estimates - always use calcsize Im using calcsize for a couple of months (half a year ? longer ?) and never had any problem with it (Solaris ufsdump and tar, linux tar only). SGI's xfsdump is incredibly fast, so Im using that iso calcsize. I only have one SunOS box, and that has so little disk to backup taht calcsize would be a few minutes faster than dump so I didn;t bother with that. I did some extensive testign way back when, and found that calcsize wa within 1% of the estimates given by ufsdump/tar (on quiet filesystems) on busy filesystems the difference between calcsizes estimate and dump was the same as ebtween two succesive dumpestimates. The moment a ufsdump/tar estimate takes more than 3 hours, the estimated size will not refelct the actual size anyway. Currently listening to: the hum of my computer Gerhard, @jasongeo.com == The Acoustic Motorbiker == -- __O Standing above the crowd, he had a voice so strong and loud =`\, we'll miss him (=)/(=) Ranting and pointing his finger, At everything but his heart we'll miss him
holding space estimates
I've set amanda's holding space to be ``all of the disk, but leave XXX
free''
(
holdingdisk hd1 {
comment main holding disk
directory /whopper/amanda/lto # where the holding disk is
use -10 Gb # how much space can we use on it
# a non-positive value means:
#use all space but that value
}
It looks like amanda treats this as:
Upon startup, check how much free diskspace is there, subtract 10G from
that, and use that as the disksize.
My amanda dumps take all night (well over 12 hours) and the disks are
active, meaning that the amount of free diskspace is fluctuating.
However amanda does *NOT* adapt her idea of how much disksapce is
available.
She simply calculates at startup how much she can use, and uses that number
for the rest of the night.
Ideally amanda should look every time a chunk is written to disk how much
space ios free, but at least she should check at the start of each new
dump/tar how much diskspace is free.
% amstatus lto
Using /volume/amanda/share/amanda/lto/amdump from Thu May 3 18:00:01 MET
DST 2001
[snipped]
james:/whopper/data/autotest 033409192k wait for dumping
[snipped]
james:/whopper/newhome2 038438112k writing to tape (7:59:55)
All the other dumps are finished.
SUMMARY part real estimated
size size
partition : 27
estimated : 27 125219454k
failed : 12860734k ( 2.28%)
wait for dumping: 1 33409192k ( 26.68%)
dumping to tape : 0 0k ( 0.00%)
dumping : 00k0k ( 0.00%) ( 0.00%)
dumped : 25 85863904k 88949528k ( 96.53%) ( 68.57%)
wait for writing: 00k0k ( 0.00%) ( 0.00%)
writing to tape : 1 38438112k 38678328k ( 99.38%) ( 30.70%)
failed to tape : 00k0k ( 0.00%) ( 0.00%)
taped : 24 47425792k 50271200k ( 94.34%) ( 37.87%)
6 dumpers idle : no-diskspace
taper writing, tapeq: 0
network free kps: 126880
holding space : 4672463k ( 10.84%)
dumper0 busy : 12:37:57 ( 96.85%)
dumper1 busy : 7:37:54 ( 58.51%)
dumper2 busy : 8:24:40 ( 64.49%)
dumper3 busy : 9:06:01 ( 69.77%)
taper busy : 2:39:11 ( 20.34%)
0 dumpers busy : 0:23:56 ( 3.06%)no-diskspace: 0:23:56 (100.00%)
1 dumper busy : 3:31:44 ( 27.06%)no-diskspace: 3:31:13 ( 99.76%)
start-wait: 0:00:31 ( 0.24%)
2 dumpers busy : 0:41:29 ( 5.30%)no-diskspace: 0:41:00 ( 98.86%)
start-wait: 0:00:28 ( 1.14%)
3 dumpers busy : 0:47:51 ( 6.11%)no-diskspace: 0:47:16 ( 98.79%)
start-wait: 0:00:34 ( 1.21%)
4 dumpers busy : 7:37:35 ( 58.47%)no-diskspace: 7:32:38 ( 98.92%)
start-wait: 0:04:56 ( 1.08%)
james:/home/netscradd/Mail # df -k /whopper
Filesystemkbytesused avail capacity Mounted on
/dev/md/dsk/d99 433727332 391286116 3810394392%/whopper
Note that holding space sais it has only 4 G free
Whereas the df shows that the holding disk should have approx 28G free
Kind regards,
--
Gerhard den Hollander Phone +31-10.280.1515
Technical Support Jason Geosystems BV Fax +31-10.280.1511
(When calling please note: we are in GMT+1)
[EMAIL PROTECTED] POBox 1573
visit us at http://www.jasongeo.com 3000 BN Rotterdam
JASON...#1 in Reservoir CharacterizationThe Netherlands
This e-mail and any attachment is/are intended solely for the named
addressee(s) and may contain information that is confidential and privileged.
If you are not the intended recipient, we request that you do not
disseminate, forward, distribute or copy this e-mail message.
If you have received this e-mail message in error, please notify us
immediately by telephone and destroy the original message.
Re: holding space estimates
* John R. Jackson [EMAIL PROTECTED] (Fri, May 04, 2001 at 08:39:24PM -0500) Ideally amanda should look every time a chunk is written to disk how much space ios free ... That's probably a good idea. I've added it to the TODO list. thanks
Re: Linux and dump
* John R. Jackson [EMAIL PROTECTED] (Thu, May 17, 2001 at 04:02:19PM -0500) I was going to stay out of yet another round of dump vs tar, but what the hell. Here's a little eye-opener for all you tar folks ... $ gtar --version tar (GNU tar) 1.13.19 Not to panic you or anything, of course. Have a nice day. :-) As more people have shown, if you have compiled gnutar with Suns cc compiler (usually a piece of crap, but in this case it works ;) ) gnutar works fine. For those who need a version of gnutar (Sol 2.6 or better, will likely not work on 2.5.1 or earlier) I've uploaded my copy to http://gdenhollander.cjb.net/gnutar.1.13.19 Currently listening to: David Gilmour - In Concert (VCD) Gerhard, @jasongeo.com == The Acoustic Motorbiker == -- __O Some say the end is near. =`\, Some say we'll see armageddon soon (=)/(=) I certainly hope we will I could use a vacation
Re: make failed
* Skinner, Reed [EMAIL PROTECTED] (Mon, May 21, 2001 at 03:01:32PM -0400) Hi all, I'm not exactly sure what this error message means. Could someone help me understand what is causing this? cat patch-system.sh patch-system Looks like there already is a file/dir called patch-system and you do not have permission to overwrite. Kind regards, -- Gerhard den Hollander Phone +31-10.280.1515 Global Technical SupportFax +31-10.280.1511 Jason Geosystems BV (When calling please note: we are in GMT+1) [EMAIL PROTECTED] POBox 1573 visit us at http://www.jasongeo.com 3000 BN Rotterdam JASON...#1 in Reservoir CharacterizationThe Netherlands This e-mail and any attachment is/are intended solely for the named addressee(s) and may contain information that is confidential and privileged. If you are not the intended recipient, we request that you do not disseminate, forward, distribute or copy this e-mail message. If you have received this e-mail message in error, please notify us immediately by telephone and destroy the original message.
Re: dds3 or dds4?
* Jonathan Dill [EMAIL PROTECTED] (Wed, Jun 27, 2001 at 08:43:16AM -0400) We're on the verge of ordering a DDS drive (this week). It'll probably be an HP Surestore - but the question is DDS3 or DDS4? There's the where now some people are getting 75 GB and 180 GB disk drives, and with new instruments the data sets are increasing in size rapidly. Even the DDS4 isn't big enough anymore, so I'm having to look into getting a tapedrive with higher capacity (or using GNUTAR to split up dumps, or partitioning the drives into smaller chunks, both of which are kind of messy solutions). If things are different in whatever business you are in, maybe the DDS3 would be adequate, but it's something to think about. GNUTAR works surprisingly well in practice. As for bigger capacity drives, LTO is the wave of the future. Even DLT4 doesn't get beyond 35/70 whereas LTO comes in 100/200 (and it's only step 1 out of 4 on the roadmap. I think LTO4 (or maybe LTO3) is supposed to be able to handle 1T tapes. Currently listening to: Skinny Puppy - Smothered Hope (Demo) (Back And Forth Series Two) Gerhard, @jasongeo.com == The Acoustic Motorbiker == -- __O Standing above the crowd, he had a voice so strong and loud =`\, we'll miss him (=)/(=) Ranting and pointing his finger, At everything but his heart we'll miss him
Re: Compression with /dev/rmt/0n?
* Drew Raines [EMAIL PROTECTED] (Mon, Jul 02, 2001 at 11:26:30PM -0500) This might be a question better suited for sunmanagers, but I'll try it here. I'm running Solaris 2.7 on an E450, with a DDS-3 changer. amanda's been calling my tape drive by /dev/rmt/0n, which is the OS default. From the st(7D) manpage, it looks like by not specifying a `u' or a `c' in my device name that hardware compression has not been used (contrary to popular opinion). The `n' simply means non-rewinding. So does Solaris default to using compression or not? Do I need to specify a `l' flag (low density) like so? /dev/rmt/0ln Everything in the /kernel/drv/st.conf file is set to default (all commented). i's been awhile since Iv'e read these things, but the entry for the dds3 looks like this HP_DAT_3 = 1,0x34,0,0x9639,4,0x00,0x8c,0x8c,0x8c,1; but the 4 gives the number of densities, and the 4 hex numbers after that (0x00 0x8c 0x8c 0x8c) give the 4 different density modes. IIRC the first one (0x00 is for /dev/rmt/Xl) the other for Xc Xh and one other I forgot). So, yes, /dev/rmt/0l should give different characteristics. Currently listening to: Phish - La Grange () Gerhard, @jasongeo.com == The Acoustic Motorbiker == -- __O If your watch is wound, wound to run, it will =`\, If your time is due, due to come, it will (=)/(=) Living this life, is like trying to learn latin in a chines firedrill
Re: amdump taking a long time
* John R. Jackson [EMAIL PROTECTED] (Thu, Jul 19, 2001 at 10:53:03PM -0500) The Apollo fails to return an estimate and fails to backup. The estimates are taking about 6hrs to complete. ... Ick. I'm sure that's because GNU tar does not perform estimates as fast as ufsdump can. One possibility, if you're bound and determined to switch :-), would be to get GNU tar 1.13.19 from alpha.gnu.org. That seems to be a stable version and may perform the estimates better. But not by much, gnutar has to run the estimates 3 times (level 0, current level, cunnrent level + 1). with over 500G disk that's easy 6 hours There is also the calcsize approach, but let's leave that for the moment. calcsize does all 3 estimates in one go, is more than 2ce as fast per estimate then gtar. Doing estimates on 600+G witch calcsize takes a bit less than 45 minutes on a Sun UE450, the gtar stuff took well over 4 hours for just 2 levels (level 0 and level 1, since current level was also level 0). At that point I broke down, hacked the amanda source a bit and switched to calcsize. How do I speed the size estimation up ... Don't use GNU tar. Or use calcsize ;) Currently listening to: CD Audio Track 07 Gerhard, @jasongeo.com == The Acoustic Motorbiker == -- __O Some say the end is near. =`\, Some say we'll see armageddon soon (=)/(=) I certainly hope we will I could use a vacation
Re: amdump taking a long time
* John R. Jackson [EMAIL PROTECTED] (Fri, Jul 20, 2001 at 11:40:12AM -0500) calcsize does all 3 estimates in one go ... But it does not support exclusion patterns. That's the one major thing holding me back from supporting it. It doesn't ? If you compile with -DBUILTIN_EXCLUDE_SUPPORT it should. (OK, on second thought, I see it doesn't. most of the hooks are there though .. Hmm, linking it with libtar.a from tar.1.13.19 almost fixes this. ) Now if someone wants to figure out how to link calcsize with the GNU tar pattern matching code ... :-) OK, Time to put my coding where my mouth is ;) If I get it working, would you include it ? We would need to link against the libtar.a from tar 1.13.19 alpha though. Would that be a problem ? Currently listening to: Tool - Disposition (Lateralus) Gerhard, @jasongeo.com == The Acoustic Motorbiker == -- __O Standing above the crowd, he had a voice so strong and loud =`\, we'll miss him (=)/(=) Ranting and pointing his finger, At everything but his heart we'll miss him
Re: amdump taking a long time
* John R. Jackson [EMAIL PROTECTED] (Mon, Jul 23, 2001 at 01:30:37PM -0500) If I get it working, would you include it ? Absolutely. Great. We would need to link against the libtar.a from tar 1.13.19 alpha though. Would that be a problem ? Not if it's done right :-). I'd suggest something like this: * Add library tests to configure.in ala the readline ones to see if libtar is available (I can help if you've never had the joy of working with autoconf). I haven't, but it should not be too hard (famous last words ;0 ) [8] * Finally, I think a dumptype option should be added to control whether calcsize is used (calcsize boolean, default is no). I'm not sure what should happen if program is not GNUTAR, or if it appears to be a Samba entry. Calcsize works fine for ufsdump, xfsdump and the dump on Sunos 4.1. (though xfsdump is faster [when I tested it (a year ago orso)]) It will likely give more or less correct answers for Linux dump as well though I don;t have any linux boxes with an ext2 filesystem (except for the /boot ). More or less correct as in, the estimates are within a few % of the final reported dumpsize, and the differences between the reported size and the dumped size can easily be caused by the fact that the filesystem was life. Currently listening to: The Tea Party - One () Gerhard, (@jasongeo.com) == The Acoustic Motorbiker == -- __O Wake up in the morning,when the sun starts to shine =`\, My heads still aching and my lips taste of wine (=)/(=) Trying to remember, what we both did last night.
Re: amdump taking a long time
* John R. Jackson [EMAIL PROTECTED] (Tue, Jul 24, 2001 at 03:15:42PM -0500) And remember that when you need to make mods to a Makefile, they need to be to Makefile.am (which is only in the CVS), not Makefile.in. Which, in turn, means you need to be conversant with automake (another of life's adventures :-). Which means it's probably a good idea if I get everything out of CVS and try to amke it wokr with the CVs version. So how do I get the CVS version (2.4.2 preferably) ? (I know how to use CVS, I just dont know how to get into amanda CVS) Kind regards, -- Gerhard den Hollander Phone +31-10.280.1515 Global Technical SupportFax +31-10.280.1511 Jason Geosystems BV (When calling please note: we are in GMT+1) [EMAIL PROTECTED] POBox 1573 visit us at http://www.jasongeo.com 3000 BN Rotterdam JASON...#1 in Reservoir CharacterizationThe Netherlands This e-mail and any attachment is/are intended solely for the named addressee(s) and may contain information that is confidential and privileged. If you are not the intended recipient, we request that you do not disseminate, forward, distribute or copy this e-mail message. If you have received this e-mail message in error, please notify us immediately by telephone and destroy the original message.
Tape drive recommendation
Dear all, Our houston office is going to drastically expand their disksusage (they're aiming to have betwen 1.5T and 2T (~ 2000 Gigabytes ;) ) of diskspace before the end of the year. I'd like to use amanda for their setup as well (makes administrating a lot easier if all remote offices are suing the same backup system ;) and besides, Amanda rocks). But the main concern I have at this point is: What kind of backup -hardware should I recommend. Im coinsidering an LTO tape for evry 500 G of diskspace, but that would mean buying 4 LTO tapedrives (and 4 * 20 tapes ;) ). An alternative would be to get a jukebox like setup (e.g the quantum atl http://www.atlp.com/products/M1500/index.html there's also an lto version) Does anyone know if that puppy is supported by amanda ? Does anyone have any recommendations for backing up this amound of data ? [PS, I know I promised to spent time on the calcsize thingy, but the Houston thing was taking up a lot more of my time than I had hoped ] Currently listening to: CD Audio Track 09 Gerhard, @jasongeo.com == The Acoustic Motorbiker == -- __O Screwing a cow while she goes moo-moo =`\, Will be entertaining to both her and you (=)/(=) Or you might try a tiger, if you have enough gall But the hedgepod can never be buggered at all.
Re: Tape drive recommendation
* John R. Jackson [EMAIL PROTECTED] (Mon, Jul 30, 2001 at 05:04:47PM -0500) Does anyone know if that puppy is supported by amanda ? If it's SCSI, Amanda can do it (or it should be able to so we'll make it). It is, the thing is that it's a taperobot/tapechanger, and I remember reading discussions that getting that to work is not always a trivial issue. And Ill likely only have a week to set it all up (and do a whole lot more) so I'd prefer not to have to spent too much time tinkering with the scsi changer configs ;) Does anyone have any recommendations for backing up this amound of data ? Just a couple of general theories: * Make sure no one disk (disklist entry) gets out of line. Ignoring the tape overflow issue, it would still be a bad thing to have 1.9 TBytes of your 2.0 TBytes in one file system. The day Amanda decides to do that full dump during the dumpcycle is going to be bad every time it rolls around (we have one config like that here and it's a nuisance). Hence gnutar and calcsize ;) seriously, it's gonna be a bunch of linux boxes each with 100 - 150G of diskspace (2 IDE drives of 50 - 75G) * Extend your dumpcycle so Amanda can spread the full dumps out. Yes, that means more tapes. * Run in parallel (yes, more drives and more tapes). We backup up well over 2 TBytes and this (plus a 28 day dumpcycle) is how we survive. What kind of tapedrives do you use ? If you don't have enough clients (i.e. they are silly enough to put the whole 2 TBytes on a single server), I have a minor patch to let more than one amandad run at a time so you can have multiple tape servers working at the same time. Do you need a patch for that ? Im running 3 amandads on the same machine every night (all 3 to different tapedrives ), and each client is running multiple clients (or at least can run ) at the same time. * Do the math :-). You're familiar with Amanda and know how it behaves. Write up some scenarios for splitting up the data and do rough estimates of the timing. Then play with the variables (dumpcycle, holding disk space, number of configs, drive speed, etc). Yes, I'll have to do that anyway Ill need to make a cost/benefit analysis of the various scenarios . Gerhard, @jasongeo.com == The Acoustic Motorbiker == -- __O If your watch is wound, wound to run, it will =`\, If your time is due, due to come, it will (=)/(=) Living this life, is like trying to learn latin in a chines firedrill
Re: not an amanda tape???
* [EMAIL PROTECTED] [EMAIL PROTECTED] (Tue, Jul 31, 2001 at 03:09:24PM +0200) Hello there, I figure my last mail was less than informative - usually not my style and I apologize. ERROR: /dev/sa0: not an amanda tape. (expecting a new tape) I might be wrong here, but isn't /dev/sa0 the rewind device ? Try /dev/nsa0 (or whatever is the NON-rewind device in *BSD). Currently listening to: The Pleasure Elite-Aunt Flow Gerhard, @jasongeo.com == The Acoustic Motorbiker == -- __O Some say the end is near. =`\, Some say we'll see armageddon soon (=)/(=) I certainly hope we will I could use a vacation
Re: Tape drive recommendation
* John R. Jackson [EMAIL PROTECTED] (Tue, Jul 31, 2001 at 12:44:19PM -0500) the thing is that it's a taperobot/tapechanger, and I remember reading discussions that getting that to work is not always a trivial issue. That's going to be true no matter what. Any time software comes in contact with reality (hardware), bad things happen :-). Ain't that the truth. What kind of tapedrives do you use ? DLT7000 and I use hardware compression. OK, what I didn;'t mention, the machines to be backed up are being used to do seismic/geoscientific processing (those who are really curious could take a peak at http://www.jasongeo.com to see the cutting edge in seismic inversion, stochastic inversion all in a marketing friendly format ;) [1] ) Which means that there might be more than 100G of data geenrated in a day (seismic data these days is huge. We recently received a set of 9 DLT4 tapes to be loaded on our system. Amanda is still trying to recover ;) ) And you cannot hardware compress seismic data, even gzip doesn't get much better than 95% .. ... I have a minor patch to let more than one amandad run at a time so you can have multiple tape servers working at the same time. Do you need a patch for that ? Yes. If two Amanda servers try to contact a single client at the same time, only one will make it in and the other will fail. My patch allows you to have multiple amandad inetd/xinetd entries on a client and tell the server which one to talk to (basically a run time change to the hard coded default 10080 port number). and each client is running multiple clients (or at least can run ) at the same time. But each client is only in one disklist, right? The change I'm talking about allows a client to be in multiple disklists at the same time. Now that's pretty neat .. What would be really neat (bordering on total perfection) is if you could have a single disklist, and have it shared over multiple tapedrives. But I guess you're gonna tell me that that will be in 2.4.2p3 ;) Gerhard, @jasongeo.com == The Acoustic Motorbiker == -- __O Standing above the crowd, he had a voice so strong and loud =`\, we'll miss him (=)/(=) Ranting and pointing his finger, At everything but his heart we'll miss him
Re: DLT8000, IRIX, Indy
* Brian Cuttler [EMAIL PROTECTED] (Thu, Aug 02, 2001 at 11:13:44AM -0400) Gerhard, In order to run the DLT8000 on irix (pre-6.5.12) I did modify the device tables, changed the device recognition string but didn't mess with the parameters so the DLT8000 was treated as a 7000. Mods where to the /var/sysgen/master.d/scsi file. SGI suggested I might do this under 6.5.12 rather than using the new TS drivers. Will have to see what they come up with. Surprised to hear that they may not support the DLT8000 on the older hardware, thought it was an across the board thing and the vendor that sold us the drive certainly claimed... well, salesmen. ;-) Well, it might be supported (in fact Im still hugely surprised it's not) but the docs I have, give no clue as to how to do it ;( Ah well, a 2 week holliday coming up in about 5 hours ... ;) Kind regards, -- Gerhard den Hollander Phone +31-10.280.1515 Global Technical SupportFax +31-10.280.1511 Jason Geosystems BV (When calling please note: we are in GMT+1) [EMAIL PROTECTED] POBox 1573 visit us at http://www.jasongeo.com 3000 BN Rotterdam JASON...#1 in Reservoir CharacterizationThe Netherlands This e-mail and any attachment is/are intended solely for the named addressee(s) and may contain information that is confidential and privileged. If you are not the intended recipient, we request that you do not disseminate, forward, distribute or copy this e-mail message. If you have received this e-mail message in error, please notify us immediately by telephone and destroy the original message.
Re: DLT8000, IRIX, Indy
I said I'd check this in the docs that came wth out DLT8000. There's a couple of pages about hooking up a DLT to an IRIX box, but upon closer reading the book only offers instructions for DLT devices upto a DLT7000 not for a DLT8000 ... ;( Kind regards, -- Gerhard den Hollander Phone +31-10.280.1515 Global Technical SupportFax +31-10.280.1511 Jason Geosystems BV (When calling please note: we are in GMT+1) [EMAIL PROTECTED] POBox 1573 visit us at http://www.jasongeo.com 3000 BN Rotterdam JASON...#1 in Reservoir CharacterizationThe Netherlands This e-mail and any attachment is/are intended solely for the named addressee(s) and may contain information that is confidential and privileged. If you are not the intended recipient, we request that you do not disseminate, forward, distribute or copy this e-mail message. If you have received this e-mail message in error, please notify us immediately by telephone and destroy the original message.
Re: Solaris 2.6 CPU Utilization goes to 100% when Amanda runs
* Decker, Carla Heiner (DX3) [EMAIL PROTECTED] (Tue, Aug 21, 2001 at 07:38:05AM -0400) We're having a problem with Amanda running on a Solaris 2.6 installation with LDAP services. Whenever Amanda starts, the CPU utilization goes to 100% and within a short period of time other system resources are used up and the system crashes. Has anyone else had this experience? What is causing the CPU usage to go to 100% (that is, which process) if you run top , which processes are using up all the CPU ? what is in the /tmp/amanda logfiles ? What is in your syslog ? Currently listening to: The Tea Party - Live - Egyptian Prayer - Halcyon Days (New Years Eve Buffalo) Gerhard, @jasongeo.com == The Acoustic Motorbiker == -- __O (-; a saying about Russian emigrants to Israel: ;-) =`\, (-; If someone goes from the plane Moscow-Tel Aviv ;-) (=)/(=) (-; without a violin case, then (s)he is a pianist ;-)
Re: amrecover
* Brandon Amundson [EMAIL PROTECTED] (Fri, Aug 17, 2001 at 02:58:11PM -0400) First I want to say thanks to all of you who respond to email like mine. I am trying to test amrecover. when I run amrecover daily, I get the following error. AMRECOVER Version 2.4.2p2. Contacting server on mail.daml.org ... amrecover: Unexpected server end of file I've had that happen once .. what happened was the compressed index files get expanded to /var/tmp (or somewhere like that) to get sorted (I think amrecover does a zcat indexfile.gz | sort | something else) and /var/tmp does not have enough space for this. I hacked around that problem by making sort always sort to /tmp iso /var/tmp (sort is a shell script that does exec /bin/sort.exe -T /tmp/ $@ ) Note, this most be done on the index host, not on the client Gerhard, @jasongeo.com == The Acoustic Motorbiker == -- __O If your watch is wound, wound to run, it will =`\, If your time is due, due to come, it will (=)/(=) Living this life, is like trying to learn latin in a chines firedrill
Re: Solaris 8 Server hangs during backup
* Eva Freer [EMAIL PROTECTED] (Mon, Aug 13, 2001 at 11:52:48AM -0400) Amanda Users: We have a highly subnetted configuration of Solaris 8 and 2.6 boxes, mostly E220R's. The subnets are connected via firewalls. Each subnet has its own Amanda server with an Exabyte Mammoth tape drive. We use hardware compression only. The Amanda is 2.4.2p1 on most nodes. [snip] The usual concerns apply: 1) did you check the scsi chains on all machines to ensure proper termination, proper cables c c 2) What is in the syslog on the hanging machine 3) You say the machine gets slower and slower (which means it's progressive). Did you try running top (or similar) on the machine to see what was happening (e.g. was the machine running out of memory ? out of swap space ?) Was there anything special in the /tmp/amanda logfiles ? [you will have to make sure /tmp/amanda is not mounted on tmpfs 4) Are you using software compression ? but the problem persists. Messages in the logs (not from amanda) indicate that the system is very busy (e.g. sendmail won't run the queue because the load average is too high.) Amanda is the only thing really happening other than the usual OS stuff. Could you run top/ps -ef or whatever to see what exactly is runnig, and what is hogging the CPU ? Are you using ufsdump or tar dump ? Kind regards, -- Gerhard den Hollander Phone +31-10.280.1515 Global Technical SupportFax +31-10.280.1511 Jason Geosystems BV (When calling please note: we are in GMT+1) [EMAIL PROTECTED] POBox 1573 visit us at http://www.jasongeo.com 3000 BN Rotterdam JASON...#1 in Reservoir CharacterizationThe Netherlands This e-mail and any attachment is/are intended solely for the named addressee(s) and may contain information that is confidential and privileged. If you are not the intended recipient, we request that you do not disseminate, forward, distribute or copy this e-mail message. If you have received this e-mail message in error, please notify us immediately by telephone and destroy the original message.
