Re: amrecover is kicking my butt......
Thanks Jean...your idea works great..why hasn't this been incorporated previously by chance Don Don Potter wrote: > Thanks I setup a cname for the interim which works well until I test > out the hacked amrecover. > > Looking at the diff..are you basically taking the extrapolation > portion for the disk_regex to setup host_regex, so basically redoing > the same procedure??? > > That is what I'm getting from this so far. > > Don > > Jean-Louis Martineau wrote: > >> Hi Don, >> >> Try this patch on the client, it makes a stricker pattern by enclosing >> it in ^$ >> >> Jean-Louis >> >> PS. The patch is untested. >> >> On Fri, Mar 15, 2002 at 10:35:34AM -0500, Don Potter wrote: >> >>> Being that I'm restricted to using only the name since the expresion >>> is ported to amrestore when I do the "sethost " is I >>> can setup a cname for that machine (can't change the machine name >>> since it is the mailhost) and adjust my disklist entry to reflect >>> the cname. And if I'm feeling really "randy" ( I always wanted to >>> use that term in a email)...I can see about adjusting the code of >>> amrecover to allow literal patterns as opposed to pattern matches >>> (at least for the host portion. >>> >>> Don >>> >>> Don Potter wrote: >>> >>>> Whoops .I forgot..but I think I have found the problem (not the >>>> solution). I've summized (sp???) that the amidxtaped is spawning >>>> an amrestore and the host portion does a pattern search as opposed >>>> to a literal search it fails (follow my thinking): >>>> >>>> The machine I'm restoring is chg and the filesystem is /var..and >>>> when I'm doing the amrecover it ouputs this: >>>> amrecover> add dpotter >>>> Added /mail/dpotter >>>> amrecover> extract >>>> Extracting files using tape drive /dev/rmt/0cn on host chgsfs. >>>> The following tapes are needed: Daily_10 >>>> >>>> Restoring files into directory /var/adm/amanda/sbin >>>> Continue? [Y/n]: Y >>>> >>>> Load tape Daily_10 now >>>> Continue? [Y/n]: Y >>>> ./mail/dpotter is not on volume >>>> set owner/mode for '.'? [yn] >>>> >>>> So at least I know that it is opening the correct index file. Now >>>> this is where it gets freaky, I'm only cuttin' and pastin'the tail >>>> portion of the amrecover (since amrecover is working): >>>> amrecover: stream_client: connected to 152.3.165.105.10083 >>>> amrecover: stream_client: our side is 0.0.0.0.750 >>>> amrecover: try_socksize: receive buffer size is 65536 >>>> Started amidxtaped with arguments "6 -h -p /dev/rmt/0cn chg ^/var$ >>>> 20020314" >>>> Exec'ing /usr/sbin/ufsrestore with arguments: >>>> restore >>>> xbf >>>> 2 >>>> - >>>> /mail/dpotter >>>> >>>> Which then spawns the amidxtaped and then seems to run correctly, >>>> but never gets past chgsfs (another machine) /var. >>>> >>>> more amidxtaped.20020315095725.debug >>>> amidxtaped: debug 1 pid 19244 ruid 9732 euid 9732 start time Fri >>>> Mar 15 09:57:25 >>>> 2002 >>>> amidxtaped: version 2.4.2p2 >>>> >>>>> SECURITY USER root >>>>> >>>> bsd security: remote host chgsfs.mc.duke.edu user root local user >>>> amanda >>>> amandahosts security check passed >>>> >>>>> 6 >>>>> >>>> amrestore_nargs=6 >>>> >>>>> -h >>>>> -p >>>>> /dev/rmt/0cn >>>>> chg >>>>> ^/var$ >>>>> 20020314 >>>>> >>>> Ready to execv amrestore with: >>>> path = /var/adm/amanda/sbin/amrestore >>>> argv[0] = "amrestore" >>>> argv[1] = "-h" >>>> argv[2] = "-p" >>>> argv[3] = "/dev/rmt/0cn" >>>> argv[4] = "chg" <=== Here is the kicker >>>> argv[5] = "^/var$" >>>> argv[6] = "20020314" >>>> amrestore: 0: skipping start of tape: date 20020314 label Daily_10 >>>> amrestore: 1: skipping primer._export.200
Schedule question.....
Okay..I know the virtues of amanda allowing it to do all of the backup scheduling itself (full and incremental), and I think that it is really kewl. BUT.when your client base is used to 1st of the month full-backups I have to adjust acordingly (so sayeth the boss man). That being said (and trying to apease the group that I support) could I do the following and obtain that same effect: dumpcycle 31 days runspercycle 31 days (daily backups.weekends included) tapecycle 31 tapes I have a 6 slot tapechanger so I will be changing the tapes at the end cycle and putting in new tapes. I can do a amadmin Daily force of all my hosts and filesystems initally and take those tapes out of rotation, and at the end of the tapecycle (I'm assuming I wouldn't need to do a amadmin Daily no-reuse since they won't be in the changer at all) and once the first of the month rolls around do the force again and once again pull those tapes out of rotation. The level 0 would be out of the rotation for basically forever. Does this sound viable? BTW...this is an inital implementation... Don
Planner question
Is there a way to determine what planner determines as the compressed backup size of tthe various filesystems in your disklist while doing the initial estimate. I know when the completion report is sent you get the average compression rate. I was just wondering if that is compiled initially during planning and saved any a file. Is this data located in the amdump log file Thanks, Don
Re: amandad keeps dying for some unknown reason......
Dan Wilder wrote: > This could be an inetd issue, if you have a whole lot > of disklist entries pointing to the server in question. > > Rate limiting is a common inetd feature. The idea is that > more than some number of requests per unit time means the > same request is coming in repeatedly, and the server isn't > satisfying it. > > As anybody who has ever tried to run even a moderatly busy SMTP > server over inetd has discovered, this feature, while preventing > machine meltdown due to overspawning a failing server, may also > bring about server failures under slightly different circumstances. > > Of course this was not unexpected, and inetd makes allowances > for this. See "man inetd". At least on Linux. I'd expect > similar allowance on Solaris, too. > > >From "man 5 inetd.conf", an entry like > > amanda dgram udp wait.100 amanda /usr/libexec/amandad amandad > > specifies that 100 server processes may be spawned in one minute. > > On Wed, Jan 02, 2002 at 12:18:01PM -0500, Don Potter wrote: > > I have Solaris 8 box using Amanda 2.4.2 (client). And when I run > > amcheck from the tape server I get the following errors on the console: > > > > Dec 31 09:54:18 oligo inetd[170]: [ID 858011 daemon.warning] > > /var/adm/amanda/libexec/amandad: Killed > > Dec 31 09:55:28 oligo inetd[170]: [ID 667328 daemon.error] amanda/udp > > server failing (looping), service terminated > > > > I thought it was an issue pertaining to the OS version only. But I > > have been able to use amanda on other 5.8 boxes. The only differance > > is that I used different GCC to compile the software. The failing box > > uses 3.0.2 and the working boxes utilize 2.8.1 of gcc (upgrading the > > compiler). > > > > Has anybody seen issues of this variety by chance. I'm not sure if > > this is even related to the gcc rev. > > > > Thanks for any advice. > > > > Don Potter > > > > > > -- > - > Dan Wilder <[EMAIL PROTECTED]> Technical Manager & Editor > SSC, Inc. P.O. Box 55549 Phone: 206-782-8808 > Seattle, WA 98155-0549URL http://embedded.linuxjournal.com/ > - This is a initial installation so there are only 3 total entries in the disklistI don't believe that there is an equivilant to increase a number of given server processes in Solaris as there is Linux by modifying the /etc/inetd.conf. I would assume that would be in the /etc/system, but it wouldn't be the first time that I'm wrong. I'm not sure on how to determine the max number of invocatiions of a given server process spawned by inetd. Does anybody else? Don
Re: Multi-tape question
It didn't complain (and if I'm incorrect in my assumption crowd..please
correct me) planner never takes into account the tape length so that is
why there wasn't any complaints
When taper started writing the dumps to tape and it was determined that
the filesystem exceeded the expected tape size (regardless of hardware
compression) the dumps would fail since the dumps aren't capable of
spanning tapes
You should use the compression device (/dev/rmt/0cn..depending unix
flavor) and adjust your length to be what you expect your compression to be.
Make sense??
If I recollect (had same problem myself) the tapetype doesn't prefer the
compression it gives you the raw length of the tape...so if you had a
tapetype length of 33000 mb (+ or -) then you could set your length to
65000 mb (if using hardware compression.
As a side note make sure that you aren't using software and hardware at
the same time (speaking from experience as an amanda "freshmen" myself)
Don
Eric Trager wrote:
>On Tue, 26 Feb 2002, Don Potter wrote:
>
>>What is the length of the tapetypeusing hardware compression you
>>will need to adjust the length to what you expect your actually
>>compression ratio to be..if you expect each tape to be about 70gb then
>>your length would be 7 mbytes.
>>
>
>Ah... so perhaps this is causing the issue?
>
>define tapetype DLTtapeIV {
>comment "DLTtape IV - 40 GB"
>length 33706 mbytes
>filemark 43 kbytes
>speed 1820 kps
>}
>
>That was what the tapetype run gave us. So I guess you're saying that
>using the cbn device rather than the bn or n device is creating a
>conflict?
>
>I'm just wondering why amanda would abandon partitions... it did seem to
>properly determine that it had ~70 Gb to work with...
>
>- Eric
>
>
Re: Amanda users does not get full access to files
Does bin have read access on the raw devices /dev/rdsk (or /dev/vx/)?? Toomas Aas wrote: >Hi David! > >On 8 Apr 02 at 10:57 you wrote: > >>I've just upgraded from 2.4.2p2 to 2.4.3b3, at the same time I've changed my >>amanda user from root to bin. I notice when I get the report at the end of a >>level 0 backup. It has backed up nowhere near all the data that exists. >> >>For example: >> >>/export/home/staff >> >>has 11.8GB but is only backing up 235MB. Now when I do a du -sk >>/export/home/staff as user bin it reports (Guess what) 235MB. >> > >I don't know about Solaris but in FreeBSD the user that Amanda runs as >needs to have read access to disk devices (in my casem, a subset of >/dev/da0s* and /dev/da1s*) >-- >Toomas Aas | [EMAIL PROTECTED] | http://www.raad.tartu.ee/~toomas/ >* No problem is so big that it can't be run away from. >
Re: Schedule question.....
John shed some light from a previous thread..I'll basically be required to maintain two seperate configs as to allow the Daily runs correctly and still maintain Full backups for off-site storage. My brain is fried now. Don Don Potter wrote: > Okay..I know the virtues of amanda allowing it to do all of the backup > scheduling itself (full and incremental), and I think that it is > really kewl. > > BUT.when your client base is used to 1st of the month full-backups > I have to adjust acordingly (so sayeth the boss man). > > That being said (and trying to apease the group that I support) could > I do the following and obtain that same effect: > > dumpcycle 31 days > runspercycle 31 days (daily backups.weekends included) > tapecycle 31 tapes > > I have a 6 slot tapechanger so I will be changing the tapes at the end > cycle and putting in new tapes. I can do a amadmin Daily force of all > my hosts and filesystems initally and take those tapes out of > rotation, and at the end of the tapecycle (I'm assuming I wouldn't > need to do a amadmin Daily no-reuse since they won't be in the changer > at all) and once the first of the month rolls around do the force > again and once again pull those tapes out of rotation. The level 0 > would be out of the rotation for basically forever. > > Does this sound viable? > > BTW...this is an inital implementation... > > Don > >
Re: Question in case of disaster
I have an rsync running to an alternate server so the index files are replicated to once the backup is completed. So I always have a fall back server. David Flood wrote: >>My interest is to know ow to restore an entire directory and all it's >>subdirectories and all their files content in the shortest time possible >>after an unwanted disaster may occur. >> > > To do this in the shortest time possible the answer must be back > up the amanda database files onto floppy disk on a regular basis, > also test the floppy regularly. If your DB files won't fit onto a floppy > consider CD or the tape your backing the other stuff on to. > Although may have complicatyions with this method because the > DB files will be open while amanda is running. In this scenario you > only have to dig through the tape for the DB files restore them then > restore as normal. > > This is the way we do it although touch wood we have not been > faced with such a situation to date. Now that I've said that I know > it's going to happen. > > > David Flood > Systems Administrator > -- _ Don Potter -- [EMAIL PROTECTED] Center for Human Genetics Duke University -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_ Never knock on Death's door. Ring the doorbell and run (he hates that)
Re: Using Multiple Tape Sizes
I would be willing to bet that you could use..them but since the config specifies the tape size, you would only be using the limits of the previous size. I would say add the tapes in your rotation and adjust your tape size to reflect the new tapes. And remove the the 8GB tapes from your rotation. My thoughts don't reflect the ideas of a rationale mind Brook Hurd wrote: > We currently use 20 8 gig tapes for our backup in > amanda. We have obtained some 20 gig tapes and we > would like to add these to the backup schedule. Do we > need to replace the 8 gig tapes with the 20's or can > we intermix them? > > Thanks, > > Brook > -- _____ Don Potter -- [EMAIL PROTECTED] Center for Human Genetics Duke University -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_ Security-wise, NT is a server with a "Kick me" sign taped to it. -- Peter Gutmann
Re: Amanda + solaris
Solaris 8 does. Thomas Hepper wrote: [EMAIL PROTECTED]"> Hi,On Tue, Apr 23, 2002 at 03:35:34PM +0200, Ryszard Kluza wrote: HelloI have Sun E250 with Solaris 7Tape library Adic FastStore22And amandaHow I have to configure amanda and solaris to work together,What kind of driver I need to instal on Solaris I'm not sure if solaris have already the sgen driver. If no check the docs directory and there the file TAPE.CHANGERS on what youneed for solaris without the sgen driver. In this doc you will findalso some notes on how to configure the sgen driver.Hope this helps for the first steps. Thomas -- _-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Don Potter -- [EMAIL PROTECTED] Center for Human Genetics Duke University -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_ Today's subliminal thought is:
Re: Amanda users does not get full access to files
Does bin have read access on the raw devices /dev/rdsk (or /dev/vx/)?? Toomas Aas wrote: >Hi David! > >On 8 Apr 02 at 10:57 you wrote: > >>I've just upgraded from 2.4.2p2 to 2.4.3b3, at the same time I've changed my >>amanda user from root to bin. I notice when I get the report at the end of a >>level 0 backup. It has backed up nowhere near all the data that exists. >> >>For example: >> >>/export/home/staff >> >>has 11.8GB but is only backing up 235MB. Now when I do a du -sk >>/export/home/staff as user bin it reports (Guess what) 235MB. >> > >I don't know about Solaris but in FreeBSD the user that Amanda runs as >needs to have read access to disk devices (in my casem, a subset of >/dev/da0s* and /dev/da1s*) >-- >Toomas Aas | [EMAIL PROTECTED] | http://www.raad.tartu.ee/~toomas/ >* No problem is so big that it can't be run away from. >
Re: amanda auth hosts problem
You are actually supposed to run amrecover as root...which makes sense being that would be the account that would be doing a restore or a recover typically. Don Tom Van de Wiele wrote: >Hello list > >I have a backupserver with two partitions on it that need to be backup'd >+ 2 clients. > >I have a .amandahosts in the amanda user's $HOME. It has this in it: > >[cut] >hostname.eduline.beamanda >[/cut] > >To make backups, this works fine. But when I want to amrecover files, I >get that amanda authhosts failed. When I change the user to "root" >instead of "amanda", then amrecover works. Is there a more sudle way >then to always change that user in that file? > >(BTW, I applied the stream_client patch, recompiled and amrecover works) > >Kind regards > >-- Tom > > >
Re: "I know this message..." help restore entire system
Good reference: http://www.backupcentral.com/amanda-23.html Don't forget to do a amadmin find to detemine what tape has your most current backups (Level 0 and 1 preferably) Good Luck Mr Igor Vertiletsky wrote: >Hi all; > >I am running RH 7.1 with an IDE hard drive. the system >is configured as amanda client and has only one >partition / (root). I've been getting some disk >read/write errors on this computer. To parafrase >Galaxy Quest: "I know this message... It is a bad >message!!!", . It looks like the IDE drive is about to >go. I am planning to run fsck, but it has an equal >chance of trashing the system. > >Anyway, my question is: how do I restore the entire >system (in case I need to rplace or rebuild hard >drive)? I have recent full dumps of the server. > >Thanks. > >igor. > >__ >Do You Yahoo!? >Yahoo! Tax Center - online filing with TurboTax >http://taxes.yahoo.com/ >
Re: Setting up an archival system...
I run two seperate configs (Daily vs. Monthly) with the same list of disklist entries and devices (holding disks, tape drive). But with the Monthly config I have record set to no and the dump type in the disklist set as always-full. I pick an arbitrary day (usually the first Monday of a month) and I will run the Monthly backup (for off-site storage) and then I will continue with the Daily config on all other days. With the Monthly record set to no the /etc/dumdpates is never touched and doesn't conflict with the Daily runs. Don Morse, Richard E. wrote: >Hi! I'd like to, in addition to my current backup setup, have a series of >archival snapshots that I take every other month or so. This is an issue, >because I was just asked to retrieve a file from 1998, which was (hopefully) >backed up under a previous sysadmin, in some form or other, but which I'm having >difficulty accessing. I'd like to prevent that from being an issue in the >future. > >I was wondering if there was a way to run an archival backup without disturbing >my current regular backup as well. One possibility that occured would be to >have amanda somehow keep the level 0 dump images on the holding disk and flush >them to disk during the day (the regular backup runs at night), when I could >have a separate set of tapes to insert. > >The reason for doing this is that I can't run the archival backup during the day >(the systems are in use), but I don't have a tape changer, and I don't want to >stop doing my standard backups during this period -- because if I'm doing a >level 0 of every disk, it will reset the last 'level 0 date' for the standard >backup as well, which might then not do a level 0 as frequently as I'd like for >the regular backup... > >Any suggestions? > >Thanks, >Ricky > >- >Richard MorseSystem Administrator >MGH Biostatistics Center 50 Staniford St. Rm 560 >[EMAIL PROTECTED] 617/724-9830 >
Adjusting runtapes
I'm decom' a server that was a tape hog. So consequently I'm able to adjust my runtapes. Has anybody experienced any adverse situations that would be derived from reducing the runtapes? Don
Re: help had to reconfig disks on a server
You could try copying the info file of the old name to the info file of the name. I'm not sure if you would need to adjust the /etc/dumpdates as well on the server though. Just a thought... Stott, Trevor wrote: > > > One of my servers suffered a failure yesterday and out of that I had > to move some disks around but now amanda is going to think they're new > disks. For example the old disk was /dev/vx/dsk/rootdg/Compuset and > it's now /dev/vx/dsk/sys_dg/Compuset. Basically changed from the > rootdg to the sys_dg which shouldn't be a big deal but now amanda > thinks they're new disks and will try to do 0 level dumps at the same > time on all of them. > > Any Ideas? > > Trevor. >
Does anybody purge old index files.....
Reading John's excellent chapter got me to thinking...I should purge old index files as well after I have completed my tape rotation. Since once that tape is overwritten that index in null and void. Can anybody contradict that thinking. Don
Re: question to the audience.....
That would be a good idea...something similar to the plugins that BigBrother has. Not endoresed by BigBrother but made availbale as user contributions. Matthew Boeckman wrote: > I think it's a great idea. Would it be possible to have a page at > amanda.org to post them instead of the list? I'd love to go to > www.amanda.org/scripts (or something) instead of searching for perl > regex'es in the amanda-users archive... > > > just a thought... > > > Don Potter wrote: > >> I'm sure we all have a selection of scripts that we use to make our >> backup lives that much easier. Would there be any objections posting >> any scripts that we find to be prudent to this mailer. Majority of >> mine are quick and nasty bourne scripts which can be pasted in, but >> they could prove to be useful out there. >> >> Just inquiring to see if there is a interest. >> Don >> >> > >
Re: Would this be considered erroneous???
Sorry if my lack of info sounds misleading..it is only amverify that fails John R. Jackson wrote: >>>What do you mean "restores are failing on that specific archive"? >>> >>That specific file (the archived image on tape)...I guess I selected a >>inappropriate termthanks John. >> > >What I meant (and I wasn't clear) was that you said *restores* are >failing. Did you mean amverify, or do you mean you are actually having >trouble doing a restore? > >If it's amverify, then this is just a ufsrestore annoyance. But if >you're having trouble doing a real restore, that might be something >completely different. > >>Don >> > >John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED] >
question to the audience.....
I'm sure we all have a selection of scripts that we use to make our backup lives that much easier. Would there be any objections posting any scripts that we find to be prudent to this mailer. Majority of mine are quick and nasty bourne scripts which can be pasted in, but they could prove to be useful out there. Just inquiring to see if there is a interest. Don
Re: Would this be considered erroneous???
That specific file (the archived image on tape)...I guess I selected a inappropriate termthanks John. John R. Jackson wrote: >>W hen I run an amverify I get the following: >>... >>Cannot find file dump list >> > >Solaris ufsrestore does this when the image is "empty", e.g. when >you do an incremental backup of a very static file system and nothing >gets dumped. I consider it a bug. > >You can ignore it (I do). > >>It is consistent to this one archive on all of the tapes.and restores are >>failing on that specific archive. ... >> > >What do you mean "restores are failing on that specific archive"? > >>Don >> > >John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED] >
Would this be considered erroneous???
W hen I run an amverify I get the following: ** Error detected (chgsfs._usr.20020321.1) amrestore: WARNING: not at start of tape, file numbers will be offset amrestore: 0: restoring chgsfs._usr.20020321.1 Cannot find file dump list 64+0 records in 64+0 records out It is consistent to this one archive on all of the tapes.and restores are failing on that specific archive. But I can DD the file off and do the ufsrestore myself. H The tape serve is a Solaris 8 box and I haven't been recieving any SCSI errors so I feel safe in the notion that the tape drive is good. Any ideas??? Don
Re: amrecover is kicking my butt......
Thanks Jean...your idea works great..why hasn't this been incorporated previously by chance Don Don Potter wrote: > Thanks I setup a cname for the interim which works well until I test > out the hacked amrecover. > > Looking at the diff..are you basically taking the extrapolation > portion for the disk_regex to setup host_regex, so basically redoing > the same procedure??? > > That is what I'm getting from this so far. > > Don > > Jean-Louis Martineau wrote: > >> Hi Don, >> >> Try this patch on the client, it makes a stricker pattern by enclosing >> it in ^$ >> >> Jean-Louis >> >> PS. The patch is untested. >> >> On Fri, Mar 15, 2002 at 10:35:34AM -0500, Don Potter wrote: >> >>> Being that I'm restricted to using only the name since the expresion >>> is ported to amrestore when I do the "sethost " is I >>> can setup a cname for that machine (can't change the machine name >>> since it is the mailhost) and adjust my disklist entry to reflect >>> the cname. And if I'm feeling really "randy" ( I always wanted to >>> use that term in a email)...I can see about adjusting the code of >>> amrecover to allow literal patterns as opposed to pattern matches >>> (at least for the host portion. >>> >>> Don >>> >>> Don Potter wrote: >>> >>>> Whoops .I forgot..but I think I have found the problem (not the >>>> solution). I've summized (sp???) that the amidxtaped is spawning >>>> an amrestore and the host portion does a pattern search as opposed >>>> to a literal search it fails (follow my thinking): >>>> >>>> The machine I'm restoring is chg and the filesystem is /var..and >>>> when I'm doing the amrecover it ouputs this: >>>> amrecover> add dpotter >>>> Added /mail/dpotter >>>> amrecover> extract >>>> Extracting files using tape drive /dev/rmt/0cn on host chgsfs. >>>> The following tapes are needed: Daily_10 >>>> >>>> Restoring files into directory /var/adm/amanda/sbin >>>> Continue? [Y/n]: Y >>>> >>>> Load tape Daily_10 now >>>> Continue? [Y/n]: Y >>>> ./mail/dpotter is not on volume >>>> set owner/mode for '.'? [yn] >>>> >>>> So at least I know that it is opening the correct index file. Now >>>> this is where it gets freaky, I'm only cuttin' and pastin'the tail >>>> portion of the amrecover (since amrecover is working): >>>> amrecover: stream_client: connected to 152.3.165.105.10083 >>>> amrecover: stream_client: our side is 0.0.0.0.750 >>>> amrecover: try_socksize: receive buffer size is 65536 >>>> Started amidxtaped with arguments "6 -h -p /dev/rmt/0cn chg ^/var$ >>>> 20020314" >>>> Exec'ing /usr/sbin/ufsrestore with arguments: >>>> restore >>>> xbf >>>> 2 >>>> - >>>> /mail/dpotter >>>> >>>> Which then spawns the amidxtaped and then seems to run correctly, >>>> but never gets past chgsfs (another machine) /var. >>>> >>>> more amidxtaped.20020315095725.debug >>>> amidxtaped: debug 1 pid 19244 ruid 9732 euid 9732 start time Fri >>>> Mar 15 09:57:25 >>>> 2002 >>>> amidxtaped: version 2.4.2p2 >>>> >>>>> SECURITY USER root >>>>> >>>> bsd security: remote host chgsfs.mc.duke.edu user root local user >>>> amanda >>>> amandahosts security check passed >>>> >>>>> 6 >>>>> >>>> amrestore_nargs=6 >>>> >>>>> -h >>>>> -p >>>>> /dev/rmt/0cn >>>>> chg >>>>> ^/var$ >>>>> 20020314 >>>>> >>>> Ready to execv amrestore with: >>>> path = /var/adm/amanda/sbin/amrestore >>>> argv[0] = "amrestore" >>>> argv[1] = "-h" >>>> argv[2] = "-p" >>>> argv[3] = "/dev/rmt/0cn" >>>> argv[4] = "chg" <=== Here is the kicker >>>> argv[5] = "^/var$" >>>> argv[6] = "20020314" >>>> amrestore: 0: skipping start of tape: date 20020314 label Daily_10 >>>> amrestore: 1: skipping primer._export.200
Re: amrecover is kicking my butt......
Thanks I setup a cname for the interim which works well until I test out the hacked amrecover. Looking at the diff..are you basically taking the extrapolation portion for the disk_regex to setup host_regex, so basically redoing the same procedure??? That is what I'm getting from this so far. Don Jean-Louis Martineau wrote: >Hi Don, > >Try this patch on the client, it makes a stricker pattern by enclosing >it in ^$ > >Jean-Louis > >PS. The patch is untested. > >On Fri, Mar 15, 2002 at 10:35:34AM -0500, Don Potter wrote: > >>Being that I'm restricted to using only the name since the expresion is >>ported to amrestore when I do the "sethost " is I can >>setup a cname for that machine (can't change the machine name since it >>is the mailhost) and adjust my disklist entry to reflect the cname. And >>if I'm feeling really "randy" ( I always wanted to use that term in a >>email)...I can see about adjusting the code of amrecover to allow >>literal patterns as opposed to pattern matches (at least for the host >>portion. >> >>Don >> >>Don Potter wrote: >> >>>Whoops .I forgot..but I think I have found the problem (not the >>>solution). I've summized (sp???) that the amidxtaped is spawning an >>>amrestore and the host portion does a pattern search as opposed to a >>>literal search it fails (follow my thinking): >>> >>>The machine I'm restoring is chg and the filesystem is /var..and when >>>I'm doing the amrecover it ouputs this: >>>amrecover> add dpotter >>>Added /mail/dpotter >>>amrecover> extract >>>Extracting files using tape drive /dev/rmt/0cn on host chgsfs. >>>The following tapes are needed: Daily_10 >>> >>>Restoring files into directory /var/adm/amanda/sbin >>>Continue? [Y/n]: Y >>> >>>Load tape Daily_10 now >>>Continue? [Y/n]: Y >>>./mail/dpotter is not on volume >>>set owner/mode for '.'? [yn] >>> >>>So at least I know that it is opening the correct index file. Now >>>this is where it gets freaky, I'm only cuttin' and pastin'the tail >>>portion of the amrecover (since amrecover is working): >>>amrecover: stream_client: connected to 152.3.165.105.10083 >>>amrecover: stream_client: our side is 0.0.0.0.750 >>>amrecover: try_socksize: receive buffer size is 65536 >>>Started amidxtaped with arguments "6 -h -p /dev/rmt/0cn chg ^/var$ >>>20020314" >>>Exec'ing /usr/sbin/ufsrestore with arguments: >>> restore >>> xbf >>> 2 >>> - >>> /mail/dpotter >>> >>>Which then spawns the amidxtaped and then seems to run correctly, but >>>never gets past chgsfs (another machine) /var. >>> >>>more amidxtaped.20020315095725.debug >>>amidxtaped: debug 1 pid 19244 ruid 9732 euid 9732 start time Fri Mar >>>15 09:57:25 >>>2002 >>>amidxtaped: version 2.4.2p2 >>> >>>>SECURITY USER root >>>> >>>bsd security: remote host chgsfs.mc.duke.edu user root local user amanda >>>amandahosts security check passed >>> >>>>6 >>>> >>>amrestore_nargs=6 >>> >>>>-h >>>>-p >>>>/dev/rmt/0cn >>>>chg >>>>^/var$ >>>>20020314 >>>> >>>Ready to execv amrestore with: >>>path = /var/adm/amanda/sbin/amrestore >>>argv[0] = "amrestore" >>>argv[1] = "-h" >>>argv[2] = "-p" >>>argv[3] = "/dev/rmt/0cn" >>>argv[4] = "chg" <=== Here is the kicker >>>argv[5] = "^/var$" >>>argv[6] = "20020314" >>>amrestore: 0: skipping start of tape: date 20020314 label Daily_10 >>>amrestore: 1: skipping primer._export.20020314.1 >>>amrestore: 2: skipping intron._intron2.20020314.1 >>>amrestore: 3: skipping sibpair._app_oracle_product_8.0.5a.20020314.1 >>>amrestore: 4: skipping dnadoc.c0t0d0s0.20020314.1 >>>amrestore: 5: skipping pcr._pcr2.20020314.1 >>>amrestore: 6: skipping marker._var.20020314.1 >>>amrestore: 7: skipping chgsfs.c0t0d0s0.20020314.1 >>>amrestore: 8: skipping primer._usr.20020314.1 >>>amrestore: 9: skipping mitosis._var.20020314.1 >>>amrestore: 10: skipping sibpair._sibpair3.20020314.1 >>>amrestore: 11: skipping pcr._var.20020314.1 >&g
Re: Amanda general question
Also if you have duplicate configs make sure to set "record no" in the global dumptype Joshua Baker-LePain wrote: >On Fri, 15 Mar 2002 at 1:35pm, Robert SHEN wrote > >>1) how amanda records how many runs performed in a dumpcycle? Let's say >>if dumpcycle=7 and runspercycle = 5 and what happens if I configure 6 >>cron jobs to run from monday to friday >> > >Then you'll get extra backups -- I don't think it'll confuse amanda too >much. Note that dumpcycle has units -- I'm assuming you mean 7 days. > >>2) what happens if runspercycle > dumpcycle? >> > >Then you're telling amanda that you plan on running it more than once a >day (again, assuming your units on dumpcycle is days), and you'd better do >so or amanda will get very unhappy. > >>3) if I want to apply the following strategy, what config should I put? >>Monday full backup for a directory /home/public >>Tuesday->Friday incremental backup of /home/public >> > >AGH! :) Why? This has been discussed *many* times. You *can* force >amanda into your schedule. But, unless you have a very good reason why, >then it really is best to let amanda set the schedule. It does a very >good job at it. > >If you must do it, the canonical method is via two configs, one which does >the full (via a dumpcycle=0 dumptype) and one which does only >incrementals. > >>4) What suggestion for disaster recovery? >> >A boot floppy/CD with, minimally, mt, dd, and tar/restore, and possibly >with the amanda tools. >
Re: amrecover is kicking my butt......
Being that I'm restricted to using only the name since the expresion is ported to amrestore when I do the "sethost " is I can setup a cname for that machine (can't change the machine name since it is the mailhost) and adjust my disklist entry to reflect the cname. And if I'm feeling really "randy" ( I always wanted to use that term in a email)...I can see about adjusting the code of amrecover to allow literal patterns as opposed to pattern matches (at least for the host portion. Don Don Potter wrote: > Whoops .I forgot..but I think I have found the problem (not the > solution). I've summized (sp???) that the amidxtaped is spawning an > amrestore and the host portion does a pattern search as opposed to a > literal search it fails (follow my thinking): > > The machine I'm restoring is chg and the filesystem is /var..and when > I'm doing the amrecover it ouputs this: > amrecover> add dpotter > Added /mail/dpotter > amrecover> extract > Extracting files using tape drive /dev/rmt/0cn on host chgsfs. > The following tapes are needed: Daily_10 > > Restoring files into directory /var/adm/amanda/sbin > Continue? [Y/n]: Y > > Load tape Daily_10 now > Continue? [Y/n]: Y > ./mail/dpotter is not on volume > set owner/mode for '.'? [yn] > > So at least I know that it is opening the correct index file. Now > this is where it gets freaky, I'm only cuttin' and pastin'the tail > portion of the amrecover (since amrecover is working): > amrecover: stream_client: connected to 152.3.165.105.10083 > amrecover: stream_client: our side is 0.0.0.0.750 > amrecover: try_socksize: receive buffer size is 65536 > Started amidxtaped with arguments "6 -h -p /dev/rmt/0cn chg ^/var$ > 20020314" > Exec'ing /usr/sbin/ufsrestore with arguments: >restore >xbf >2 >- >/mail/dpotter > > Which then spawns the amidxtaped and then seems to run correctly, but > never gets past chgsfs (another machine) /var. > > more amidxtaped.20020315095725.debug > amidxtaped: debug 1 pid 19244 ruid 9732 euid 9732 start time Fri Mar > 15 09:57:25 > 2002 > amidxtaped: version 2.4.2p2 > > SECURITY USER root > bsd security: remote host chgsfs.mc.duke.edu user root local user amanda > amandahosts security check passed > > 6 > amrestore_nargs=6 > > -h > > -p > > /dev/rmt/0cn > > chg > > ^/var$ > > 20020314 > Ready to execv amrestore with: > path = /var/adm/amanda/sbin/amrestore > argv[0] = "amrestore" > argv[1] = "-h" > argv[2] = "-p" > argv[3] = "/dev/rmt/0cn" > argv[4] = "chg" <=== Here is the kicker > argv[5] = "^/var$" > argv[6] = "20020314" > amrestore: 0: skipping start of tape: date 20020314 label Daily_10 > amrestore: 1: skipping primer._export.20020314.1 > amrestore: 2: skipping intron._intron2.20020314.1 > amrestore: 3: skipping sibpair._app_oracle_product_8.0.5a.20020314.1 > amrestore: 4: skipping dnadoc.c0t0d0s0.20020314.1 > amrestore: 5: skipping pcr._pcr2.20020314.1 > amrestore: 6: skipping marker._var.20020314.1 > amrestore: 7: skipping chgsfs.c0t0d0s0.20020314.1 > amrestore: 8: skipping primer._usr.20020314.1 > amrestore: 9: skipping mitosis._var.20020314.1 > amrestore: 10: skipping sibpair._sibpair3.20020314.1 > amrestore: 11: skipping pcr._var.20020314.1 > amrestore: 12: skipping linkage._var.20020314.1 > amrestore: 13: skipping sibpair._app_oracle_product_8.1.7.20020314.1 > amrestore: 14: skipping wwwchg._usr.20020314.1 > amrestore: 15: skipping wwwchg.c0t0d0s0.20020314.1 > amrestore: 16: skipping locus._var.20020314.1 > amrestore: 17: skipping theta._var.20020314.1 > amrestore: 18: skipping allele._var.20020314.1 > amrestore: 19: skipping hybrid._var.20020314.1 > amrestore: 20: skipping primer._var.20020314.1 > amrestore: 21: skipping diploid._var.20020314.1 > amrestore: 22: skipping haldane._var.20020314.1 > amrestore: 23: skipping exon._var.20020314.1 > amrestore: 24: skipping weinberg._var.20020314.1 > amrestore: 25: skipping chimera._var.20020314.1 > amrestore: 26: skipping ligate._var.20020314.1 > amrestore: 27: skipping ligate._export_home.20020314.1 > amrestore: 28: skipping peptide._var.20020314.0 > amrestore: 29: skipping annotate._var.20020314.0 > amrestore: 30: skipping hybrid._export.20020314.2 > amrestore: 31: restoring chgsfs._var.20020314.1 > > > amrestore is my failing point.. > > Does all that make sense > > Don > > > > > >
Re: amrecover is kicking my butt......
Whoops .I forgot..but I think I have found the problem (not the solution). I've summized (sp???) that the amidxtaped is spawning an amrestore and the host portion does a pattern search as opposed to a literal search it fails (follow my thinking): The machine I'm restoring is chg and the filesystem is /var..and when I'm doing the amrecover it ouputs this: amrecover> add dpotter Added /mail/dpotter amrecover> extract Extracting files using tape drive /dev/rmt/0cn on host chgsfs. The following tapes are needed: Daily_10 Restoring files into directory /var/adm/amanda/sbin Continue? [Y/n]: Y Load tape Daily_10 now Continue? [Y/n]: Y ./mail/dpotter is not on volume set owner/mode for '.'? [yn] So at least I know that it is opening the correct index file. Now this is where it gets freaky, I'm only cuttin' and pastin'the tail portion of the amrecover (since amrecover is working): amrecover: stream_client: connected to 152.3.165.105.10083 amrecover: stream_client: our side is 0.0.0.0.750 amrecover: try_socksize: receive buffer size is 65536 Started amidxtaped with arguments "6 -h -p /dev/rmt/0cn chg ^/var$ 20020314" Exec'ing /usr/sbin/ufsrestore with arguments: restore xbf 2 - /mail/dpotter Which then spawns the amidxtaped and then seems to run correctly, but never gets past chgsfs (another machine) /var. more amidxtaped.20020315095725.debug amidxtaped: debug 1 pid 19244 ruid 9732 euid 9732 start time Fri Mar 15 09:57:25 2002 amidxtaped: version 2.4.2p2 > SECURITY USER root bsd security: remote host chgsfs.mc.duke.edu user root local user amanda amandahosts security check passed > 6 amrestore_nargs=6 > -h > -p > /dev/rmt/0cn > chg > ^/var$ > 20020314 Ready to execv amrestore with: path = /var/adm/amanda/sbin/amrestore argv[0] = "amrestore" argv[1] = "-h" argv[2] = "-p" argv[3] = "/dev/rmt/0cn" argv[4] = "chg" <=== Here is the kicker argv[5] = "^/var$" argv[6] = "20020314" amrestore: 0: skipping start of tape: date 20020314 label Daily_10 amrestore: 1: skipping primer._export.20020314.1 amrestore: 2: skipping intron._intron2.20020314.1 amrestore: 3: skipping sibpair._app_oracle_product_8.0.5a.20020314.1 amrestore: 4: skipping dnadoc.c0t0d0s0.20020314.1 amrestore: 5: skipping pcr._pcr2.20020314.1 amrestore: 6: skipping marker._var.20020314.1 amrestore: 7: skipping chgsfs.c0t0d0s0.20020314.1 amrestore: 8: skipping primer._usr.20020314.1 amrestore: 9: skipping mitosis._var.20020314.1 amrestore: 10: skipping sibpair._sibpair3.20020314.1 amrestore: 11: skipping pcr._var.20020314.1 amrestore: 12: skipping linkage._var.20020314.1 amrestore: 13: skipping sibpair._app_oracle_product_8.1.7.20020314.1 amrestore: 14: skipping wwwchg._usr.20020314.1 amrestore: 15: skipping wwwchg.c0t0d0s0.20020314.1 amrestore: 16: skipping locus._var.20020314.1 amrestore: 17: skipping theta._var.20020314.1 amrestore: 18: skipping allele._var.20020314.1 amrestore: 19: skipping hybrid._var.20020314.1 amrestore: 20: skipping primer._var.20020314.1 amrestore: 21: skipping diploid._var.20020314.1 amrestore: 22: skipping haldane._var.20020314.1 amrestore: 23: skipping exon._var.20020314.1 amrestore: 24: skipping weinberg._var.20020314.1 amrestore: 25: skipping chimera._var.20020314.1 amrestore: 26: skipping ligate._var.20020314.1 amrestore: 27: skipping ligate._export_home.20020314.1 amrestore: 28: skipping peptide._var.20020314.0 amrestore: 29: skipping annotate._var.20020314.0 amrestore: 30: skipping hybrid._export.20020314.2 amrestore: 31: restoring chgsfs._var.20020314.1 amrestore is my failing point.. Does all that make sense Don
amrecover is kicking my butt......
Okay, this makes no sense whatsoever. This is only occuring on one
filesystem, and it is sporadic in occurances there. When ever I
attempt to do a amrecover of the directory on /var/mail I get the
following:
But I can dd the file from tape and extract it doing a straight
ufsrestore from that archived file, so it is on the volume. At first I
thought that index file was corrupted (since that is was amrecover
refers off of initially). And the files (or directories) are there in
my "dd'd" version. Amverify shows no issues whatsoever with the
filesystem in question:
Checked chg._var.20020313.0
And the sendbackup doesn't have any complaints either:
sendbackup: debug 1 pid 11165 ruid 9732 euid 9732 start time Wed Mar 13
22:10:45
2002
/var/adm/amanda/libexec/sendbackup: version 2.4.2p2
sendbackup: got input request: DUMP /var 0 1970:1:1:0:0:0 OPTIONS
|;bsd-auth;ind
ex;
parsed request as: program `DUMP'
disk `/var'
lev 0
since 1970:1:1:0:0:0
opt `|;bsd-auth;index;'
sendbackup: try_socksize: send buffer size is 65536
sendbackup: stream_server: waiting for connection: 0.0.0.0.48393
sendbackup: stream_server: waiting for connection: 0.0.0.0.48394
sendbackup: stream_server: waiting for connection: 0.0.0.0.48395
waiting for connect on 48393, then 48394, then 48395
sendbackup: stream_accept: connection from 152.3.165.105.47225
sendbackup: stream_accept: connection from 152.3.165.105.47226
sendbackup: stream_accept: connection from 152.3.165.105.47227
got all connections
sendbackup: started index creator: "/usr/sbin/ufsrestore -tvf - 2>&1 |
sed -e '
s/^leaf[]*[0-9]*[ ]*\.//
t
/^dir[ ]/ {
s/^dir[ ]*[0-9]*[ ]*\.//
s%$%/%
t
}
d
'"
sendbackup: spawning /usr/sbin/ufsdump in pipeline
sendbackup: argument list: dump 0usf 1048576 - /dev/rdsk/c0t0d0s3
sendbackup: index created successfully
sendbackup: pid 11165 finish time Wed Mar 13 23:04:32 2002
What is leading amrecover to believe that the file inquestion isn't on
the volume? I am out of ideas.
Don
Re: result of amcheck
It means that it is a unused tape ...if it had been previously used (meaning tape is referred to in the tapelist file) then there will be a reference to the tape. Look in your tapelist file and see if there is any reference to DailySet16 Don Zhen Liu wrote: >Hi, > >I am working on amanda with the Adic Fastor autoloader...Dlt7000... >on RH linux 7.1 os... > >When I run amcheck i got the following message: amcheck-server: slot0: >date X label DailySet16 (first labelstr match) > >So, anyone knows anything wrong with this? why the date shows X >instead of the actual date? pls help!!! > >Thanks, > >Zhen Liu >Via Webmail >[EMAIL PROTECTED] >
amrecover is actig really flaky.....
I backup the /var parttion of our mail server (solaris box) using straight ufsdump with hardware compresion. I'm able to amrecover anything on that particular filesystem except for /var/mail (kind of important). They are on the same partition so I'm not crossing devices. I get the statement that the file isn't on the volume. But I can dd the file from the tape and restore it with no problem. And access it as expected. It is almost as if the index maybe corrupted, but it is the same for every single backup. I was originally doing a comp-user in my disklist, and I adjusted it to always-full. The problem persists. Could it be some underlying permission issue. I use two seperate configs (Daily and Monthly) and I know the discussions that may raise. But I was able to pull the backup off of the monthly with no problem. The only differance betweeen the two configs is that Monthly doesn't update /etc/dumpdates and that the stratoegy for all partitions is always-full. Any advice would be greatly appreciated. This doesn't make sense to me at all. Don
Re: netusage, high or low?
If I remember corredctly the defined interfaces are only needed if you
are specifying that a given disklist entry is to backed up directly via
an specific interface (I.E. Private backup networks).
When you look at the report do you see any client contention (I'm sure
you do but is it substantial). I had an issue where the holding_area
was on a heavily utilized bus so the throughput was noticably slower.
So I spread the spindles across different buses (sp???)
What kind of traffic are you seeing when you do a netstat -i 5. You can
raise the netusage amount. But you will find that the hardware does all
of the required throttling needed.
Don
Brandon Moro wrote:
>Also, as to my original question, I am still wondering whether I should bump
>these numbers up or down in order to increase the amount of traffice (or
>numbers of running dumpers) that amanda will allow.
>
> netusage 4000 Kbps # maximum net bandwidth for Amanda, in KB per sec
>
> define interface le0 {
> comment "100 Mbps ethernet"
> use 4000 kbps
>
>
>I'm pretty sure I RAISE the netusage variable, but what do I do to the
>interface 'use' attribute?
>
>B
>
>-Original Message-
>From: Martin Hepworth [mailto:[EMAIL PROTECTED]]
>Sent: Thursday, March 07, 2002 9:32 AM
>To: [EMAIL PROTECTED]
>Cc: Brandon Moro
>Subject: Re: netusage, high or low?
>
>
>Brandon
>
>err you mention the le0 interface in the config.
>
>Is this correct 'cos the the le0 interface is a 10base system, not
>100base!..
>
>--
>Martin
>
>Brandon Moro wrote:
>
>>Hello all!
>>
>>I am having some troubles with my AMANDA backups running too long. They
>>often take 20+ hours,
>>sometimes even breaking the 24-hour mark. The average amount of data I
>>
>get
>
>>is only about 35GB.
>>
>>I am running my amanda-server on Solaris8, on a Sun Ultra5 400MHz with
>>
>256MB
>
>>RAM, on a 100mbps
>>connection. I have 2 DLT 7000 tape drives set up (though it very rarely
>>roles over).
>>
>>Recently, I put a larger holding disk on the server and found that my run
>>time was cut more than in half!
>>However, I notice that I am still only getting a total of about 3GB an
>>
>hour.
>
>>The data runs from the holding
>>disk to tape at more like 6MB/s.
>>
>>We have a couple of other backup systems running on almost identical
>>hardware that puts more than
>>twice as much data to tape in slightly less time. So I guess what I am
>>really asking is, am I missing
>>something in the configuration of AMANDA sthat will allow better usage of
>>the network connection?
>>
>>I found this in the amanda.conf file:
>>
>>netusage 4000 Kbps # maximum net bandwidth for Amanda, in KB per sec
>>(blah blah)
>>
>>network interfaces
>>
>>. Attributes are:
>>use - bandwidth above which amanda won't
>>start
>> backups using this interface.
>>Note that if
>> a single backup will take more
>>than that,
>> amanda won't try to make it run
>>slower!
>>
>>define interface local {
>>comment "a local disk"
>>use 1000 kbps
>>}
>>
>>define interface le0 {
>> comment "100 Mbps ethernet"
>> use 4000 kbps
>>
>>
>>So, does this mean that if my dumpers are using 4000kbps, amanda won't
>>
>allow
>
>>any more
>>dumpers to start (even if the maximum number of allowed dumpers has not
>>
>been
>
>>reached)?
>>
>>Can I improve performance by raising the netusage variable and "use"
>>attribute to something
>>more in line with the actual capacity of the amanda-server's network
>>connection?
>>
>>Also, the network interface on the amanda-server is actually "hme0". Are
>>the above simply
>>examples? Should I create a new interface definition?
>>
>>Thanks for your help!
>>
>>Brandon Moro
>>Systems Administration, Unify Corporation
>>[EMAIL PROTECTED]
>>-
>>>From meanness first this Portsmouth Yankey rose, And still to meanness all
>>his conduct flows.--Oppression, A poem by an American (Boston, 1765).
>>
>>
>>
>
Re: Question about amreport.....
I figured out the second question...it was dumping the postscript file in the log directory...big time goof...and aopon further reflection...I'm blowin smoke So ignore the idiot that resides in the Big Green Pickle Don Joshua Baker-LePain wrote: >On Tue, 5 Mar 2002 at 11:00am, Don Potter wrote > >>Since my backups span two tapes..I would of expected to seperate tape >>labels to be printed. Instead there was one label with the tape label >>divided by a comma. Is this correct >> > >It's certainly not desired behavior... > >>Second when I attempted to adjust the label type to a 8.5x11...I should >>of been able to do the following: >> >>amreport Monthly -l (logfile name) -p /var/adm/amanda/postscript/8.5x11.ps >> >>This should of taken the config from the amanda.conf for Monthly and >>printed out the adjusted label. No such liuck...it just sent tthe >>report to myself via e-mail. >> >Nope. From the amreport man page: > > -p postscriptfile > Send the postscript output to the file postscript > file instead of to the lpr(1) command. This option > has an effect only if the lbl-templ directive is > specified in amanda.conf. > >IOW, it redirected the postscript output (that is, the tape label that >would normally be printed) to the named file -- you just overwrote the >8.5x11 label template... > >You need to change lbl-templ in amanda.conf to change the type of label >that gets printed. >
Re: Question about amreport.....
BTW..it is defined in my amanda.conf as a label type Don Potter wrote: > I did a full backup for production and I'mn working on the estetics > right now. > > Since my backups span two tapes..I would of expected to seperate tape > labels to be printed. Instead there was one label with the tape > label divided by a comma. Is this correct > > > Second when I attempted to adjust the label type to a 8.5x11...I > should of been able to do the following: > > amreport Monthly -l (logfile name) -p > /var/adm/amanda/postscript/8.5x11.ps > > This should of taken the config from the amanda.conf for Monthly and > printed out the adjusted label. No such liuck...it just sent tthe > report to myself via e-mail. > > > Am I missing something??? > > Don
Question about amreport.....
I did a full backup for production and I'mn working on the estetics right now. Since my backups span two tapes..I would of expected to seperate tape labels to be printed. Instead there was one label with the tape label divided by a comma. Is this correct Second when I attempted to adjust the label type to a 8.5x11...I should of been able to do the following: amreport Monthly -l (logfile name) -p /var/adm/amanda/postscript/8.5x11.ps This should of taken the config from the amanda.conf for Monthly and printed out the adjusted label. No such liuck...it just sent tthe report to myself via e-mail. Am I missing something??? Don
amdump question
Doing a test I have a two filesystems (/var to be precise) on two differnet machines (pretty obvious there). And I did a backup and it was determined to be a level 1 (which is what I expected it to be since I did a full 2 days ago nad had little or no change. So for S and G's I put a 50 MB file into the /var filesystem and kicked off another amdump. I was expecting it to adjust the backup level to 2 since the bumpsize is set for 20 mb. Instead the amdump proceeded to do a level 1 on one files system and resort back to a level 0 on the other. Does this sound correct? Or am I misinterpeting wwhat the amanda.conf is telling me? Here is the info from the amanda.conf: dumpcycle 4 weeks runspercycle 31 tapecycle 31 tapes bumpsize 20 Mb bumpdays 1 bumpmult 4 Message from report: Don
Re: Schedule question.....
That is what I was thinking about doing initally..but I was concerned with introducing tapes into the rotation for my expected full backup (of the archive variety)I'm assuming that you don't add them arbitrairlly into your tapelist... I would guess that you add them before you do a full backup and once that backup is complete you mark them as no-reuse and removehave you ever had any issues about doing a restore from those tapes by chance Is that the approach that you follow??? Gotta ask the silly questions. Don Stephen Carville wrote: >I have to create both weekly and monthly archives that go offsite. I >just use amadmin to force a full backup on the appropiate day. I set >whatever tapes were used as no-reuse and, if necessary, add >replacements into the rotation. Because the monthly tapes never >rotate back in, every so often I go in and remove them from the >tapelist by hand. The weekly fulls rotate on a four week cycle so I >mark them as reuse when I put them back into the changer magazine. > >On Tue, 26 Feb 2002, Don Potter wrote: > >- Okay..I know the virtues of amanda allowing it to do all of the backup >- scheduling itself (full and incremental), and I think that it is really >- kewl. >- >- BUT.when your client base is used to 1st of the month full-backups I >- have to adjust acordingly (so sayeth the boss man). >- >- That being said (and trying to apease the group that I support) could I >- do the following and obtain that same effect: >- >- dumpcycle 31 days >- runspercycle 31 days (daily backups.weekends included) >- tapecycle 31 tapes >- >- I have a 6 slot tapechanger so I will be changing the tapes at the end >- cycle and putting in new tapes. I can do a amadmin Daily force of all >- my hosts and filesystems initally and take those tapes out of rotation, >- and at the end of the tapecycle (I'm assuming I wouldn't need to do a >- amadmin Daily no-reuse since they won't be in the changer at all) and >- once the first of the month rolls around do the force again and once >- again pull those tapes out of rotation. The level 0 would be out of the >- rotation for basically forever. >- >- Does this sound viable? >- >- BTW...this is an inital implementation... >- >- Don >- >- >- >- >
Re: Schedule question.....
John shed some light from a previous thread..I'll basically be required to maintain two seperate configs as to allow the Daily runs correctly and still maintain Full backups for off-site storage. My brain is fried now. Don Don Potter wrote: > Okay..I know the virtues of amanda allowing it to do all of the backup > scheduling itself (full and incremental), and I think that it is > really kewl. > > BUT.when your client base is used to 1st of the month full-backups > I have to adjust acordingly (so sayeth the boss man). > > That being said (and trying to apease the group that I support) could > I do the following and obtain that same effect: > > dumpcycle 31 days > runspercycle 31 days (daily backups.weekends included) > tapecycle 31 tapes > > I have a 6 slot tapechanger so I will be changing the tapes at the end > cycle and putting in new tapes. I can do a amadmin Daily force of all > my hosts and filesystems initally and take those tapes out of > rotation, and at the end of the tapecycle (I'm assuming I wouldn't > need to do a amadmin Daily no-reuse since they won't be in the changer > at all) and once the first of the month rolls around do the force > again and once again pull those tapes out of rotation. The level 0 > would be out of the rotation for basically forever. > > Does this sound viable? > > BTW...this is an inital implementation... > > Don > >
Schedule question.....
Okay..I know the virtues of amanda allowing it to do all of the backup scheduling itself (full and incremental), and I think that it is really kewl. BUT.when your client base is used to 1st of the month full-backups I have to adjust acordingly (so sayeth the boss man). That being said (and trying to apease the group that I support) could I do the following and obtain that same effect: dumpcycle 31 days runspercycle 31 days (daily backups.weekends included) tapecycle 31 tapes I have a 6 slot tapechanger so I will be changing the tapes at the end cycle and putting in new tapes. I can do a amadmin Daily force of all my hosts and filesystems initally and take those tapes out of rotation, and at the end of the tapecycle (I'm assuming I wouldn't need to do a amadmin Daily no-reuse since they won't be in the changer at all) and once the first of the month rolls around do the force again and once again pull those tapes out of rotation. The level 0 would be out of the rotation for basically forever. Does this sound viable? BTW...this is an inital implementation... Don
Re: Multi-tape question
I should of stated filesystem.bad Donno soup for me It will put as many filesystems on a tape as possibel (prvoding tape length is calc'd correctly) and then write the remainder on the next tape (if you have specified the dumps to use multiple tapes) Sorry for the confusion..I'll keep my mouth shut from now on Eric Trager wrote: > >On Tue, 26 Feb 2002, Don Potter wrote: > >>When taper started writing the dumps to tape and it was determined that >>the filesystem exceeded the expected tape size (regardless of hardware >>compression) the dumps would fail since the dumps aren't capable of >>spanning tapes >> > >Waitaminit... this I didn't know. Amanda can't run dumps across tapes? Why >is the runtapes entry even used at all? > >So if I use HW compression and set the length at 65 Gb, and I want to do a >"level 0" dump (say it's the first dump, for example) ... > >host /filesystem # 40 Gb FS >host /filesystem2# 20 Gb FS >host /filesystem3# 20 Gb FS > >... Amanda will continue to sense a problem and drop one of the >filesystems from the lineup? I thought that, using "runtapes 2", amanda >would put two of the filesystems on one tape, load the next tape, and >stick the leftover system on it... ? > >- Eric >
Re: Multi-tape question
It didn't complain (and if I'm incorrect in my assumption crowd..please
correct me) planner never takes into account the tape length so that is
why there wasn't any complaints
When taper started writing the dumps to tape and it was determined that
the filesystem exceeded the expected tape size (regardless of hardware
compression) the dumps would fail since the dumps aren't capable of
spanning tapes
You should use the compression device (/dev/rmt/0cn..depending unix
flavor) and adjust your length to be what you expect your compression to be.
Make sense??
If I recollect (had same problem myself) the tapetype doesn't prefer the
compression it gives you the raw length of the tape...so if you had a
tapetype length of 33000 mb (+ or -) then you could set your length to
65000 mb (if using hardware compression.
As a side note make sure that you aren't using software and hardware at
the same time (speaking from experience as an amanda "freshmen" myself)
Don
Eric Trager wrote:
>On Tue, 26 Feb 2002, Don Potter wrote:
>
>>What is the length of the tapetypeusing hardware compression you
>>will need to adjust the length to what you expect your actually
>>compression ratio to be..if you expect each tape to be about 70gb then
>>your length would be 7 mbytes.
>>
>
>Ah... so perhaps this is causing the issue?
>
>define tapetype DLTtapeIV {
>comment "DLTtape IV - 40 GB"
>length 33706 mbytes
>filemark 43 kbytes
>speed 1820 kps
>}
>
>That was what the tapetype run gave us. So I guess you're saying that
>using the cbn device rather than the bn or n device is creating a
>conflict?
>
>I'm just wondering why amanda would abandon partitions... it did seem to
>properly determine that it had ~70 Gb to work with...
>
>- Eric
>
>
Re: Multi-tape question
What is the length of the tapetypeusing hardware compression you will need to adjust the length to what you expect your actually compression ratio to be..if you expect each tape to be about 70gb then your length would be 7 mbytes. But I would suggest you not go to the limit of your expected compression. Don Eric Trager wrote: >Hi, all. I managed to get my changer working with Amanda using chg-scsi. >Today I started the first test dump to see what would happen. > >Using hardware compression, my DLT-IV tapes hold about 70 GB. I set up a >dump of several large and small partitions totalling ~88 GB. One was not >mounted for the dump so the total was actually 73 GB. I set runtapes to 2 >in the amanda.conf file thinking this would tell amanda to use two tapes, >but I see this in the amdump log: > >[snip] > >INITIAL SCHEDULE (size 73008621): > gorge /export/home pri 11747 lev 0 size 16340165 > gorge /usr/ pri 11747 lev 0 size 15425329 > gorge /usr/oracle2 pri 11747 lev 0 size 12874971 > gorge /usr/oracle pri 11747 lev 0 size 7166160 > gorge /usr/oracle5 pri 11747 lev 0 size 4502198 > gorge /usr/oracle3 pri 11747 lev 0 size 4348242 > gorge /usr/oracle4 pri 11747 lev 0 size 4143069 > gorge / pri 11747 lev 0 size 3541838 > gorge /public pri 11747 lev 0 size 982111 > gorge /var pri 11747 lev 0 size 818101 > gorge /export/gorge pri 11746 lev 0 size 2865347 > gorge /export/mada/yoga pri 11746 lev 0 size 40 > >DELAYING DUMPS IF NEEDED, total_size 73008621, tape length 69029888 mark >43 >planner: FAILED gorge /export/gorge 20020226 0 [dumps too big, but cannot >incremental dump new disk] >planner: FAILED gorge /var 20020226 0 [dumps too big, but cannot >incremental dump new disk] >planner: FAILED gorge /public 20020226 0 [dumps too big, but cannot >incremental dump new disk] > delay: Total size now 68342837. >[snip] > > > >So it dropped some small partitions until it got to a total it likes. I >thought, however, that runtapes tells Amanda to use the changer to fill >additional tapes as needed. Am I assuming the wrong thing? Does runtapes >mean something else? > >I have included some snips from my configs. Please shed some light on this >if you can. > >TIA, > >Eric > > > amanda.conf > >runtapes 2 # number of tapes to use in a single run of amdump >tpchanger "/usr//opt/amanda-2.4.3b2/etc/amanda/Othertest/chg-scsi" >tapedev "0" >changerfile >"/usr//opt/amanda-2.4.3b2/etc/amanda/Othertest/chg-scsi-solaris.conf" >labelstr "^CMAG-[0-9][0-9]*$" >dumpcycle 1#the number of days in the normal dump cycle >bumpdays 1 #minimum days at each level >bumpsize 20 Mb #minimum savings (threshold) to bump level 1 -> 2 >bumpmult 2 #threshold = bumpsize * bumpmult^(level-1) >runspercycle 1 # the number of amdump runs in dumpcycle days >tapecycle 4# the number of tapes in rotation > > chg-scsi-solaris.conf > >number_configs 1 >eject 1 # Tapedrives need an eject command >sleep 45 # Seconds to wait until the tape gets ready >cleanmax 1000# How many times could a cleaning tape get used >changerdev /dev/changer ># >config 0 >drivenum 0 >dev/dev/rmt/1cbn >startuse 0 # The slots associated with the drive 0 >enduse 14 # > >-- >
Re: planner fails, dumps too big
Regardless of the autoloader..you still must specify number of tapes per a backup...if the config resticts you to use 1 tape then so be it..I believe that if you specify two tapes in your config file and it only takes up one (depending if you are using hardware compression ) then the next tape would be loaded at he next invocation of a backup. Juanjo wrote: > Hello, > > Seems that only 4 out of 6 dumps are backed up. Two of them are > skipped giving error message: dumps too big > > What I see is that it starts estimating sizes of every disk, therefore > total size exceeds single tape size, but I'm using an autoloader, so > It should jump on to a new tape, shouldnt it? And send there the disks > that didnt fit on that prior tape. How? > > Here I paste a piece of amdump.log: > > >- > > > got result for host srvc disk /data1: 0 -> 32149300K, -1 -> -1K, -1 -> > -1K > got result for host srvc disk /data0: 0 -> 20482410K, -1 -> -1K, -1 -> > -1K > got result for host srvb disk /data1: 0 -> 35674680K, -1 -> -1K, -1 -> > -1K > got result for host srvb disk /data0: 0 -> 21510210K, -1 -> -1K, -1 -> > -1K > getting estimates took 266.671 secs > FAILED QUEUE: empty > DONE QUEUE: > 0: srva /data1 > 1: srva /data0 > 2: srvc /data1 > 3: srvc /data0 > 4: srvb /data1 > 5: srvb /data0 > > ANALYZING ESTIMATES... > pondering srva:/data1... next_level0 -11737 last_level -1 (due for > level 0) (new disk, can't switch to degraded mode) > curr level 0 size 27650 total size 27770 total_lev0 27650 > balanced-lev0size 4608 > pondering srva:/data0... next_level0 -11737 last_level -1 (due for > level 0) (new disk, can't switch to degraded mode) > curr level 0 size 423860 total size 451670 total_lev0 451510 > balanced-lev0size 75251 > pondering srvc:/data1... next_level0 -11737 last_level -1 (due for > level 0) (new disk, can't switch to degraded mode) > curr level 0 size 32149300 total size 32601010 total_lev0 32600810 > balanced-lev0size 5433467 > pondering srvc:/data0... next_level0 -11737 last_level -1 (due for > level 0) (new disk, can't switch to degraded mode) > curr level 0 size 20482410 total size 53083460 total_lev0 53083220 > balanced-lev0size 8847202 > pondering srvb:/data1... next_level0 -11737 last_level -1 (due for > level 0) (new disk, can't switch to degraded mode) > curr level 0 size 35674680 total size 88758180 total_lev0 88757900 > balanced-lev0size 14792982 > pondering srvb:/data0... next_level0 -11737 last_level -1 (due for > level 0) (new disk, can't switch to degraded mode) > curr level 0 size 21510210 total size 110268430 total_lev0 110268110 > balanced-lev0size 18378017 > INITIAL SCHEDULE (size 110268430): > srvb /data1 pri 11738 lev 0 size 35674680 > srvc /data1 pri 11738 lev 0 size 32149300 > srvb /data0 pri 11738 lev 0 size 21510210 > srvc /data0 pri 11738 lev 0 size 20482410 > srva /data0 pri 11738 lev 0 size 423860 srva /data1 pri 11738 lev 0 > size 27650 > DELAYING DUMPS IF NEEDED, total_size 110268430, tape length 7168 > mark 8 > planner: FAILED srvc /data0 0 [dumps too big, but cannot incremental > dump new disk] > planner: FAILED srvb /data0 0 [dumps too big, but cannot incremental > dump new disk] > delay: Total size now 68275730. > > PROMOTING DUMPS IF NEEDED, total_lev0 68275490, balanced_size 18378017... > analysis took 0.000 secs > > GENERATING SCHEDULE: > > srvb /data1 11738 0 1970:1:1:0:0:0 35674680 1189156 > srvc /data1 11738 0 1970:1:1:0:0:0 32149300 1071643 > srva /data0 11738 0 1970:1:1:0:0:0 423860 14128 > srva /data1 11738 0 1970:1:1:0:0:0 27650 921 > >- > > > > Tape size is DLT1 40/80 btw. > > Thanks. > >
Re: chg-zd-mtx
It means that you haven't given the correct variables is the config script ...add a -x to the first line of the chg-zd-mtx script and you can see what variable is needed.. Mark Lin wrote: >I'm using mtx in solaris to work with amanda. mtx command to the changer >all works fine. But when I tried it with "chg-zd-mtx -info" or use it in >changer glue script in amanda.conf then use amcheck, I get the same error >messag: >/usr/local/libexec/chg-zd-mtx: test: argument expected > >can someone help? >I've tried "truss" in solaris, but I just wasn't worthy to understand its >output. :( > >Mark >
Re: amandad keeps dying for some unknown reason......
Dan Wilder wrote: > This could be an inetd issue, if you have a whole lot > of disklist entries pointing to the server in question. > > Rate limiting is a common inetd feature. The idea is that > more than some number of requests per unit time means the > same request is coming in repeatedly, and the server isn't > satisfying it. > > As anybody who has ever tried to run even a moderatly busy SMTP > server over inetd has discovered, this feature, while preventing > machine meltdown due to overspawning a failing server, may also > bring about server failures under slightly different circumstances. > > Of course this was not unexpected, and inetd makes allowances > for this. See "man inetd". At least on Linux. I'd expect > similar allowance on Solaris, too. > > >From "man 5 inetd.conf", an entry like > > amanda dgram udp wait.100 amanda /usr/libexec/amandad amandad > > specifies that 100 server processes may be spawned in one minute. > > On Wed, Jan 02, 2002 at 12:18:01PM -0500, Don Potter wrote: > > I have Solaris 8 box using Amanda 2.4.2 (client). And when I run > > amcheck from the tape server I get the following errors on the console: > > > > Dec 31 09:54:18 oligo inetd[170]: [ID 858011 daemon.warning] > > /var/adm/amanda/libexec/amandad: Killed > > Dec 31 09:55:28 oligo inetd[170]: [ID 667328 daemon.error] amanda/udp > > server failing (looping), service terminated > > > > I thought it was an issue pertaining to the OS version only. But I > > have been able to use amanda on other 5.8 boxes. The only differance > > is that I used different GCC to compile the software. The failing box > > uses 3.0.2 and the working boxes utilize 2.8.1 of gcc (upgrading the > > compiler). > > > > Has anybody seen issues of this variety by chance. I'm not sure if > > this is even related to the gcc rev. > > > > Thanks for any advice. > > > > Don Potter > > > > > > -- > - > Dan Wilder <[EMAIL PROTECTED]> Technical Manager & Editor > SSC, Inc. P.O. Box 55549 Phone: 206-782-8808 > Seattle, WA 98155-0549URL http://embedded.linuxjournal.com/ > - This is a initial installation so there are only 3 total entries in the disklistI don't believe that there is an equivilant to increase a number of given server processes in Solaris as there is Linux by modifying the /etc/inetd.conf. I would assume that would be in the /etc/system, but it wouldn't be the first time that I'm wrong. I'm not sure on how to determine the max number of invocatiions of a given server process spawned by inetd. Does anybody else? Don
amandad keeps dying for some unknown reason......
I have Solaris 8 box using Amanda 2.4.2 (client). And when I run amcheck from the tape server I get the following errors on the console: Dec 31 09:54:18 oligo inetd[170]: [ID 858011 daemon.warning] /var/adm/amanda/libexec/amandad: Killed Dec 31 09:55:28 oligo inetd[170]: [ID 667328 daemon.error] amanda/udp server failing (looping), service terminated I thought it was an issue pertaining to the OS version only. But I have been able to use amanda on other 5.8 boxes. The only differance is that I used different GCC to compile the software. The failing box uses 3.0.2 and the working boxes utilize 2.8.1 of gcc (upgrading the compiler). Has anybody seen issues of this variety by chance. I'm not sure if this is even related to the gcc rev. Thanks for any advice. Don Potter
Re: next tape and tapelist
If you don't wish to preserve that data you could remove the tapelist fileswhich would be recreated during backup Juanjo wrote: >After doing some checks, I'm gonna let amanda do a first backup, about 180 >Gigs of data. >Well, after those checks, the pointer is at tape 3, how can I tell amanda >to start with tape 1? > >I've tried launching: >amrmtape confname tapelabel > >but it says something about preserving original database, and after >running amcheck, next due tape is 3 still... > >Tnx. >
inparallell option in amanda.conf
I'm trying this outI have more than enough holding are and network bandwidth..so I was wondering how many users actually adjust this value.I have been up to 8 but I have usually become involved with spindle contention. Is there anybody that has opted to increase to anything near what the max value is. Or is it the consensus of the group to remain at the default. Thanks for any input. Don
Re: follow up
I believe that you will need to do a amrmtape the tape from the database trhen you could do a amlabel and re-label the disk.and then you will need to reintroduce it back into the rotation Don [EMAIL PROTECTED] wrote: >ok so the problem is that it thinks I have no new tapes, I'd like to just >write over tape 1 - how to I tell it to just write over it? > >
Re: before I recreate the wheel.....
never mind the nieve nature of the question...I have the chg-zd-mtx working (minus all of the req. for a cleaning tape which I removed) Don Don Potter wrote: > Does anybody have a changer.conf for an Sun StorEdge L280...I'm using > MTX (1.2.15) on a Solaris 8 box. > > I haven't seen one in the arcchive by chance. > > Thanks, > Don >
before I recreate the wheel.....
Does anybody have a changer.conf for an Sun StorEdge L280...I'm using MTX (1.2.15) on a Solaris 8 box. I haven't seen one in the arcchive by chance. Thanks, Don
Planner question
Is there a way to determine what planner determines as the compressed backup size of tthe various filesystems in your disklist while doing the initial estimate. I know when the completion report is sent you get the average compression rate. I was just wondering if that is compiled initially during planning and saved any a file. Is this data located in the amdump log file Thanks, Don
Re: netusage.......
So basically if I have determined that 8 dumper are the max. number of to run in parralell. And after the inital calculation (assumed that this is done by planner) the estimated amount of bandwidth needed per dump from each client. Those dumps will be initiated and the total number of dumps being accepted by the tape server will no equate to more that 600kbps. And if a dumper is in "standby" waiting to accept a connection from another host, that dumper will not begin if the transfer will go over the pre-determined limit in the amanda.conf. Correct???
Re: I have some douts.
Did you run the amcheck first (assuming inital installation)? Check that dumper is owned by root and the setuid bit is set for the usr (chmod u+s dumper) should look something like this: -rwsr-x--- 1 root sys 909112 Jan 8 10:23 dumper amcheck should tell you if the daemons are talkin' to one another (thanks to the wise "John" for this insite) v Fabio de Oliveira wrote: >Hi, > >Sorry about my english. > >I have some douts about the messages that I'd got after run amdump > >This is the e-mail that the user amanda received: > >--- >THESE DUMPS WERE TO DISK. Flush them onto a new tape. >Tonight's dumps should go onto 1 tape: a new tape. > >FAILURE AND STRANGE DUMP SUMMARY: > dumper: FATAL must be run setuid root to communicate correctly > dumper: FATAL must be run setuid root to communicate correctly > xxx.xx.xxx /PATH/. lev 0 FAILED [Request to xxx.xx.x.xx timed out.] > yy.yyy //x/. lev 0 FAILED [Request to yy.y.yyy timed out.] > > >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) -- -- -- > >? >NOTES: > planner: Adding new disk xxx.xx.x.xxx:/PATH/.. > planner: Adding new disk yyy.y.yyy:/PATH2/.. > driver: WARNING: got empty schedule from planner > >? >DUMP SUMMARY: > DUMPER STATS TAPER >STATS >HOSTNAME DISK L ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s >-- >xxx.xx.xx -o/PATH/. 0 FAILED >yy.y ///. 0 FAILED > >(brought to you by Amanda version 2.4.1p1) > >--- >The tape is not ready yet, but I wanted to simulate a amflush. > >The host xxx.xx.x.xxx is the server tape > >The holdingdisk is in the server tape. > >Would anybody answer me: > > >Why all de "dumpers" failed ? > >Why the Request to server tape failed ? > > >Thank you for anyone. >___ > >Fabio de Oliveira. >Network Administrator. >
netusage.......
I'd like the opinion of the crowd. What is the frequency that the netusage is adjusted from the default. I understand there are some locations that have less than desirable connections so I was just wondering. I'm attempting to determine if I'm saturating our link while doing the initial level 0 backup. And I would think that wouldn't be the case with the default of 600kbps value. All opinions would be greatly appreciated. Thanks, Don
Re: amcheck ...again (but on a different machine)
It appears that the HUP was giving erroneous infoI bounced the box and it is content now... Thans for the advice John R. Jackson wrote: >>I'm not as slow as my questions indicate >> > >:-) :-) > >The things you're running into are among the most common initial >problems. Don't despair. > >Since they are so common, they are even documented in the FAQ :-). >Have you read and tried all the steps documented here: > > http://amanda.sourceforge.net/fom-serve/cache/16.html > http://amanda.sourceforge.net/fom-serve/cache/140.html > >In addition to the above, have you tried all the tricks we talked >about yesterday (the shell script and truss)? > >>I would understand if it was a external box, but this is the same box. >> > >There is no difference as far as Amanda is concerned. It still makes a >network connection (even though it's through the local host interface). >In particular this means inetd has to be set up right, which is the most >common source of trouble. > >>Don Potter >> > >John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED] >
Re: amcheck ...again (but on a different machine)
That's a relief...I was feeling rather inadequate I digress. No amandad debug file (since the access time hasn't changed that would be expectedright???) and nothing in /var/adm/messages as well I was concerened with the issue of access problems (from a previoous thread) and tried running amandad as root...same outcome.. I can invoke the amandad by hand it timesout after 30 seconds (as expected) and it creates the debug file with the expected contents of a happy daemon. Joshua Baker-LePain wrote: >On Wed, 30 Jan 2002 at 3:05pm, Don Potter wrote > >>I'm not as slow as my questions indicate >> > >Amanda is a rather nice system that can take a fair bit of elbow grease to >get going. It also tweaks all sorts of things in the underlying OS setup >and can often indicate problems there. In short, don't sweat it. > >>Scenario: >>Starting up the production tape server have installed 2.4.2. Disklist >>has partitions on the tape server only (initial population). Ran >>amcheck and it fails saying that the host is down. The client >>and the tape server are one in the same. >> >>1. ) netstat -a shows that the port is being listened >>2.) parameters in /etc/inetd.conf and /etc/services are the settings >>that patch-system appends (index, tape, and amanda daemon) >>3. ) ls -lu shows that the access time on the amandad doesn't change >>since install time (which means that the daemons aren't talkin' to each >>other) >>4.) debug is created in the tmp space and indicates that it was local >> and an attempt was made (see pasted) >> >>amcheck: debug 1 pid 16456 ruid 9732 euid 0 start time Wed Jan 30 >>14:55:13 2002 >>amcheck: dgram_bind: socket bound to 0.0.0.0.1001 >>amcheck: pid 16456 finish time Wed Jan 30 14:55:43 2002 >> > >amcheck*debug is from the amcheck process, i.e. its a server side program. >What you really need to check for is the client side stuff. Is an >amandad*debug file is getting created when you run amcheck. If so, what >are its conents? Any messages in the system logs? > >>I would understand if it was a external box, but this is the same box. >> > >Amanda treats all clients the same, so it really doesn't matter that the >client is the server (or vice versa). >
amcheck ...again (but on a different machine)
I'm not as slow as my questions indicate Scenario: Starting up the production tape server have installed 2.4.2. Disklist has partitions on the tape server only (initial population). Ran amcheck and it fails saying that the host is down. The client and the tape server are one in the same. 1. ) netstat -a shows that the port is being listened 2.) parameters in /etc/inetd.conf and /etc/services are the settings that patch-system appends (index, tape, and amanda daemon) 3. ) ls -lu shows that the access time on the amandad doesn't change since install time (which means that the daemons aren't talkin' to each other) 4.) debug is created in the tmp space and indicates that it was local and an attempt was made (see pasted) amcheck: debug 1 pid 16456 ruid 9732 euid 0 start time Wed Jan 30 14:55:13 2002 amcheck: dgram_bind: socket bound to 0.0.0.0.1001 amcheck: pid 16456 finish time Wed Jan 30 14:55:43 2002 I would understand if it was a external box, but this is the same box. Any ideas Don Potter
Re: selfcheck request timed out. Host down?
Launching the daemon as root works just fine.I didn't even think about the library issue. the access time never changed on amandad until I changed the daemon owner...now comes the fun part ot figure out which library has a permission issue.. But I should be able to discern that by he truss..at least I believe that should work... Don John R. Jackson wrote: >>Jan 29 13:48:18 helix inetd[189]: [ID 858011 daemon.warning] >>/usr/bin/truss: Hangup >>... >>Jan 29 13:50:28 helix inetd[189]: [ID 858011 daemon.warning] >>/tmp/amanda_test: Hangup >> > >Something is seriously wonky about your system if you can't run these >things. Try one more test without Amanda in the loop at all: > > amandadgram udp wait amanda /bin/sleep sleep 4 > >If that also does the Hangup (amcheck will fail, but that's not important >at this point), then I have no clue. Well, maybe one ... > >>I can truss the amandad with no problem as well as determine what >>arguments and exit status by running from the command line >> > >When you run things by hand, they have a different environment (in many >ways) than when inetd runs them. It can be a real pain figuring out >what the difference is. > >When you ran things by hand, did you run them a "amanda"? In >particular, did you do something like this: > > su - amanda -c "/var/adm/amanda/libexec/amandad" > >The leading '-' tells "su" to set up the environment as though the >user had logged in (i.e. it does not inherit whatever you have). >And specifying the full path makes sure $PATH isn't getting you a >different version of the program. > >If that's not it, and the sleep also fails, try using sleep again but >change "amanda" to "root". > >If that also fails, there is something wrong with the way your system >is set up, but without looking at it myself I wouldn't have the faintest >idea where to start. > >If root works but amanda fails, you've may have some kind of permissions >problem. Since amandad (et al) are dieing right at the start, I'd guess >a shared library. > >One other thing you could try is truss (-f) inetd itself to watch >the amanda service (I'd still use sleep at this point) get started. >The problem could easily be that the forked inetd child is having the >problem and never even getting to the other program (sleep, amandad, >truss, etc). > >Speaking of which, did you check the access time on amandad after trying >amcheck? If it's not getting updated, that also means it's probably >the inetd child failing before it can exec the real program. > >John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED] >
Re: selfcheck request timed out. Host down?
dum fails as well (should of specified )..running the test that you specified I recieved the following in the /var/adm/messages: Jan 29 13:48:18 helix inetd[189]: [ID 858011 daemon.warning] /usr/bin/truss: Hangup Jan 29 13:48:26 helix last message repeated 38 times Jan 29 13:48:26 helix inetd[189]: [ID 667328 daemon.error] amanda/udp server failing (looping), service terminated Jan 29 13:50:28 helix inetd[189]: [ID 858011 daemon.warning] /tmp/amanda_test: Hangup I can truss the amandad with no problem as well as determine what arguments and exit status by running from the command line John R. Jackson wrote: >>it only croaks on the amcheck... >> > >Huh??? It **doesn't** fail for amdump? > >>the amandad will Hangup before providing any output.. >> > >Huh??? > >Did you try either of the other "debug tricks" I sent? > >John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED] >
Re: selfcheck request timed out. Host down?
Cut and paste ...
it only croaks on the amcheck...
no security packs. at all:
the amandad will Hangup before providing any output..
John R. Jackson wrote:
>>amandadgram udp wait amanda /var/adm/amanda/libexec/amandad
>>amandad
>>amandaidx stream tcp nowait amanda /var/adm/amanda/libexec/amindexd
>>amindexd
>>amidxtape stream tcp nowait amanda /var/adm/amanda/libexec/amidxtaped
>>amidxtaped
>>
>
>The lines came across in the E-mail broken as shown above. Is that
>real or is it just a cut/paste artifact?
>
>The important part is that there be one, and only one, arg to each of
>the lines (after the path to the executable). If the arg (e.g. "amanda")
>is missing, the server will try to reference argv[0] and die.
>
>What you have above is OK if there are actually three lines and not six.
>
>Did inetd whine into /var/adm/messages when you HUP'd it?
>
>Do you have (I think it's called) BSM installed (some kind of enhanced
>security package)? I recall problems with it, but don't remember the
>details.
>
>If none of that helps, here are the next things I do (from my inetd.conf):
>
>#JJ First debug trick -- create this shell script (chmod +x /tmp/amandad.test):
>#JJ #!/bin/ksh
>#JJ exec > /tmp/amandad.out.$$ 2>&1
>#JJ echo "$(/bin/date): starting amandad ($#): " "$@"
>#JJ /opt/amanda/libexec/amandad "$@"
>#JJ status=$?
>#JJ echo "$(/bin/date): amandad done: status is $status"
>#JJ exit $status
>#JJ
>#JJ amanda dgram udp waitbackup /tmp/amandad.test amandad
>#JJ
>#JJ Next debug trick -- run amandad under truss:
>#JJ
>#JJ amanda dgram udp waitbackup /bin/truss amandad -fo
>/tmp/amandad.truss /opt/amanda/libexec/amandad
>
>Note that the user name ("backup" vs. "amanda") and paths to the binaries
>on your system will be different.
>
>John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
>
Re: selfcheck request timed out. Host down?
Here ya' go.basiclly the config appeneeded when you use patch-system /etc/services amanda 10080/udp amandaidx 10082/tcp amidxtape 10083/tcp /etc/inetd.conf amandadgram udp wait amanda /var/adm/amanda/libexec/amandad amandad amandaidx stream tcp nowait amanda /var/adm/amanda/libexec/amindexd amindexd amidxtape stream tcp nowait amanda /var/adm/amanda/libexec/amidxtaped amidxtaped John R. Jackson wrote: >>... Ran the amcheck again and the amanda ports would be shut >>down with the following message in the /var/adm/message file: >> >>Jan 29 10:50:54 svr1 inetd[189]: [ID 858011 daemon.warning] /var/adm/amanda/li >>bexec/amandad: Hangup >>... >> > >What's your inetd.conf line look like? > >>Don Potter >> > >John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED] >
selfcheck request timed out. Host down?
Scenario: Solaris 2.7 and 2.8 Amanda 2.4.2p2 Ran amcheck of backup config (total of 28 hosts) and initially 10 hosts failed so I HUP'd the inetd on all of the hosts again and then only 2 failed. Ran a "netstat -a|grep amanda" and saw that the ports are "listening". Ran the amcheck again and the amanda ports would be shut down with the following message in the /var/adm/message file: Jan 29 10:50:54 svr1 inetd[189]: [ID 858011 daemon.warning] /var/adm/amanda/libexec/amandad: Hangup Jan 29 10:51:33 svr1 last message repeated 38 times Jan 29 10:51:34 svr1 inetd[189]: [ID 667328 daemon.error] amanda/udp server failing (looping), service terminated I'm capable of invoking the amandad daemon from the command line and letting it timeout on its own (see end of mail for contents of /tmp/amanda/amandad.). Any ideas as why the timeout persists. The /tmp/amanda dir is never created when running the amcheck so the daemons aren't talking to each other. Do I have to many hosts in the disklist? Looking at the archives, I don't think that is the issue. Any suggestions would be greatly appreciated. Don Potter amandad: debug 1 pid 4130 ruid 9732 euid 9732 start time Tue Jan 29 10:57:32 200 2 amandad: version 2.4.2p2 amandad: build: VERSION="Amanda-2.4.2p2" amandad:BUILT_DATE="Thu Jan 24 14:49:15 EST 2002" amandad:BUILT_MACH="SunOS chgsfs 5.8 Generic_108528-12 sun4u sparc SUNW, Ultra-60" amandad:CC="gcc" amandad: paths: bindir="/var/adm/amanda/bin" amandad:sbindir="/var/adm/amanda/sbin" amandad:libexecdir="/var/adm/amanda/libexec" amandad:mandir="/var/adm/amanda/man" AMANDA_TMPDIR="/tmp/amanda" amandad:AMANDA_DBGDIR="/tmp/amanda" amandad:CONFIG_DIR="/var/adm/amanda/etc/amanda" amandad:DEV_PREFIX="/dev/dsk/" RDEV_PREFIX="/dev/rdsk/" amandad:DUMP="/usr/sbin/ufsdump" RESTORE="/usr/sbin/ufsrestore" amandad:GNUTAR="/usr/local/bin/tar" amandad:COMPRESS_PATH="/usr/local/bin/gzip" amandad:UNCOMPRESS_PATH="/usr/local/bin/gzip" amandad:MAILER="/usr/ucb/Mail" amandad:listed_incr_dir="/var/adm/amanda/var/amanda/gnutar-lists" amandad: defs: DEFAULT_SERVER="weinberg" DEFAULT_CONFIG="DailySet1" amandad:DEFAULT_TAPE_SERVER="weinberg" amandad:DEFAULT_TAPE_DEVICE="/dev/rmt/0bn" HAVE_MMAP HAVE_SYSVSHM amandad:LOCKING=POSIX_FCNTL SETPGRP_VOID DEBUG_CODE amandad:AMANDA_DEBUG_DAYS=4 BSD_SECURITY USE_AMANDAHOSTS amandad:CLIENT_LOGIN="amanda" FORCE_USERID HAVE_GZIP amandad:COMPRESS_SUFFIX=".gz" COMPRESS_FAST_OPT="--fast" amandad:COMPRESS_BEST_OPT="--best" UNCOMPRESS_OPT="-dc" amandad: dgram_recv: timeout after 30 seconds amandad: error receiving message: timeout error receiving message: timeout amandad: pid 4130 finish time Tue Jan 29 10:58:02 2002
Re: Tapetype when utilizing hardware compression
Thank You all for all your input...you have enlightened me immensely
.became so used to using commercial applications that due the
thinking for you.
Don
Gene Heskett wrote:
>On Thursday 17 January 2002 09:10 am, Don Potter wrote:
>
>>I ran the tapetype test to our tapedrive (ADIC DS9400D) using
>>DLTTAPE IV. I frontpaneled the compression so I expected at
>>least 40 GB when the tapetype was completed. But I only got
>>about 17GB:
>>
>>Command: tapetype -d /dev/rmt/0n
>>
>>define tapetype unknown-tapetype {
>> comment "just produced by tapetype program"
>> length 17587 mbytes
>> filemark 13 kbytes
>> speed 1011 kps
>>}
>>
>>Then I ran it with software compression (/dev/rmt/0cn) and I
>>only got 20 GB:
>>
>>Command: tapetype -d /dev/rmt/0cn
>>
>>define tapetype unknown-tapetype {
>> comment "just produced by tapetype program"
>> length 19565 mbytes
>> filemark 4 kbytes
>> speed 1101 kps
>>}
>>
>>Both ways I would of expected close to double the native writes.
>> Any ideas why the compression would not of increased.
>>
>>Any suggestions would be appreciated.
>>
>>Don Potter
>>
>
>First Don, be aware that tapetype uses /dev/urandom as a data
>source, and /dev/urandom prides itself on being as truely random
>as it can be. It takes repeatable, predictable data to be able
>to compress it by any great amount.. The output of urandom wil
>typically drive a hardware compressor to make a file bigger, not
>smaller.
>
>What it boils down to is that the values you get from tapetype
>will be truely the absolute worst case values. Typical hardware
>compression will gain 2/1 on text and such sparse files, while a
>really good software algorythm can easily double that again.
>However, the hardware compression can be easily defeated by
>preceeding it with a good software compressor so that the copy on
>the tape might be 10 or more percent larger on tape than the
>actual compressed file is.
>
>If you have the cpu horspower, always use software only, with the
>hardware compression in the drive disabled.
>
Tapetype when utilizing hardware compression
I ran the tapetype test to our tapedrive (ADIC DS9400D) using DLTTAPE IV.
I frontpaneled the compression so I expected at least 40 GB when the tapetype
was completed. But I only got about 17GB:
Command: tapetype -d /dev/rmt/0ndefine tapetype unknown-tapetype {
comment "just produced by tapetype program"
length 17587 mbytes
filemark 13 kbytes
speed 1011 kps
}Then I ran it with software compression (/dev/rmt/0cn) and I only got 20 GB:Command: tapetype -d /dev/rmt/0cn
define tapetype unknown-tapetype {
comment "just produced by tapetype program"
length 19565 mbytes
filemark 4 kbytes
speed 1101 kps
}Both ways I would of expected close to double the native writes. Any ideas why the compression would not of increased.Any suggestions would be appreciated.Don Potter
Dump to holding area only
I'm presently testing amanda out before I proceed with actually implementation. I' m just sending dumps to the holding area to see speed and so forth. My holding area is 34GB and I have the reserve set for 50%. The dumps aren't saved since I have the tapedev set for /dev/null. I have two file systems that will no dump to holding_area statin g that they are too large: chgsfs /home5 lev 0 FAILED [dump larger than tape, but cannot incremental dump new disk] exon /export/home/bioproj00 lev 0 FAILED [dump larger than tape, but cannot incremental dump new disk] the filesystem derived from exon is about 10GB so I can't rationalize why the cojmplaint about lack of space when that isn't really the case. Anybody have any insight as to why this would fail?? Thanks, Don Potter
Re: amandad keeps dying for some unknown reason......
Dan Wilder wrote: > This could be an inetd issue, if you have a whole lot > of disklist entries pointing to the server in question. > > Rate limiting is a common inetd feature. The idea is that > more than some number of requests per unit time means the > same request is coming in repeatedly, and the server isn't > satisfying it. > > As anybody who has ever tried to run even a moderatly busy SMTP > server over inetd has discovered, this feature, while preventing > machine meltdown due to overspawning a failing server, may also > bring about server failures under slightly different circumstances. > > Of course this was not unexpected, and inetd makes allowances > for this. See "man inetd". At least on Linux. I'd expect > similar allowance on Solaris, too. > > >From "man 5 inetd.conf", an entry like > > amanda dgram udp wait.100 amanda /usr/libexec/amandad amandad > > specifies that 100 server processes may be spawned in one minute. > > On Wed, Jan 02, 2002 at 12:18:01PM -0500, Don Potter wrote: > > I have Solaris 8 box using Amanda 2.4.2 (client). And when I run > > amcheck from the tape server I get the following errors on the console: > > > > Dec 31 09:54:18 oligo inetd[170]: [ID 858011 daemon.warning] > > /var/adm/amanda/libexec/amandad: Killed > > Dec 31 09:55:28 oligo inetd[170]: [ID 667328 daemon.error] amanda/udp > > server failing (looping), service terminated > > > > I thought it was an issue pertaining to the OS version only. But I > > have been able to use amanda on other 5.8 boxes. The only differance > > is that I used different GCC to compile the software. The failing box > > uses 3.0.2 and the working boxes utilize 2.8.1 of gcc (upgrading the > > compiler). > > > > Has anybody seen issues of this variety by chance. I'm not sure if > > this is even related to the gcc rev. > > > > Thanks for any advice. > > > > Don Potter > > > > > > -- > - > Dan Wilder <[EMAIL PROTECTED]> Technical Manager & Editor > SSC, Inc. P.O. Box 55549 Phone: 206-782-8808 > Seattle, WA 98155-0549URL http://embedded.linuxjournal.com/ > - This is a initial installation so there are only 3 total entries in the disklistI don't believe that there is an equivilant to increase a number of given server processes in Solaris as there is Linux by modifying the /etc/inetd.conf. I would assume that would be in the /etc/system, but it wouldn't be the first time that I'm wrong. I'm not sure on how to determine the max number of invocatiions of a given server process spawned by inetd. Does anybody else? Don
amandad keeps dying for some unknown reason......
I have Solaris 8 box using Amanda 2.4.2 (client). And when I run amcheck from the tape server I get the following errors on the console: Dec 31 09:54:18 oligo inetd[170]: [ID 858011 daemon.warning] /var/adm/amanda/libexec/amandad: Killed Dec 31 09:55:28 oligo inetd[170]: [ID 667328 daemon.error] amanda/udp server failing (looping), service terminated I thought it was an issue pertaining to the OS version only. But I have been able to use amanda on other 5.8 boxes. The only differance is that I used different GCC to compile the software. The failing box uses 3.0.2 and the working boxes utilize 2.8.1 of gcc (upgrading the compiler). Has anybody seen issues of this variety by chance. I'm not sure if this is even related to the gcc rev. Thanks for any advice. Don Potter
