scheduling question.
Hello, It is my understanding that amanda will run a level 0 dump when it meets certian thresholds based upon definitions in the amanda.conf. It is also my understanding that amanda is not desigined to run a level 0 on some day and some time. Friday two of my hosts had a lvl 0 dump. This morning when I checked the status of the backups over the weekend I noticed that those same two hosts ran a lvl 0 again today. I am curious as to why amanda would run two level 0 dumps in three days. One last note. Last week on wednesday I had to force level 0's on everything with amadmin. Could this be the cause? Thanks in advance. Andrew
Re: Suggestions on how to proceed ...
Malcolm Herbert wrote: The first question is how to easily stagger 0-level dumps across a dump cycle where some disks need to be backed up at different frequency to others. You can use different dump types for different disks. In these special dumptypes set the desired dumpcycle for that disk. I used to do that and it worked fine. I like a short dumpcycle (fewer tapes for restores) but I had a 36Gb disk that was fairly static. I upped the dumpcycle for just that one disk. -- [EMAIL PROTECTED] - HMC UNIX Systems Manager My opinions are my own and probably don't represent anything anyway.
Re: taper: FATAL cannot allocate shared memory
++ 07/01/02 09:36 -0800 - Frank Wojcik: FAILURE AND STRANGE DUMP SUMMARY: taper: FATAL cannot allocate shared memory amflush: ERROR Cannot flush without tape. Try again. I use a 7 day dump/tapecycle with 8 tapes. The OS is FreeBSD 4.5-PRERELEASE and the Amanda-source is from a cvs-checkout last friday (4th of january). The OS of the clients is all FreeBSD ranging from 4.2-STABLE to 4.5-PRERELEASE. I see this problem on FreeBSD and Solaris. What has happened is that either a) some taper processes are hanging around (check ps), or, more likely, b) some shared memory segments are hanging around. You can check this out by making SURE that no Amanda processes are running, and running the command: 'ipcs -m'. If you see a line like: m 196609 0 --rwa-- operator operator (operator being my, and I suspect your, Amanda user), then you need to clear out these memory segments using 'ipcrm'. Also make sure not to delete any segments being used by root. Okay, thanks. It's working fine again now. However, I needed to decrease the tapebufs in amanda.conf in order to stop it from complaining about it in every status mail. Is this normal on FreeBSD-systems? -- Med venlig hilsen / Kind Regards, Tommy Eriksen E-Consult http://www.econsult.dk/ [EMAIL PROTECTED]
Re: Dump to holding area only
On Mon, 7 Jan 2002 at 3:05pm, Don Potter wrote 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 don't recall if amanda will even put dumps on holding disk with such a tapedev. The canonical way to fool amanda into doing this is to use something like /dev/nosuchdevice. 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. Amanda is still going to use your tapetype to determine if things will fit on tape. So if your tapetype is set to, e.g., something 7GB big, then Amanda is going to complain as above. Remember, a single filesystem can't be bigger than a tape. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Error with sense Data?
Hello, i'm using Amanda with a Seagate IDE Tape Streamer using IDE-SCSI Module for accesing the drive. When Amanda starts reading or writing to tape, the following error message appears on the console: st0: Error with sense Data: Current st09:00: Sense Key Illegal request Additional sense indicates Invalid command operation code The drive seems to work correctly. What does this message mean? Bye, Harald.
Re: Dump to holding area only
On Mon, 7 Jan 2002, Don Potter wrote: 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?? If you have just started the cycle these messages will persist until all disks have received their first level 0 dump. It's expected behavior. You cannot incremental dump something which has no level 0 on tape. Thus, amanda does level 0s of as many filesystems as possible per day until everything is on tape. Give it some time to get through your disklist. Brandon D. Valentine -- Iam mens praetrepidans avet vagari. - G. Valerius Catullus, Carmina, XLVI
Amanda and Win2k backups
I currently have amanda backing up several linux servers that I have used to restore data from using amrestore. Now that I have amanda working properly I would like it to back up my win2k machines as well. Can someone point me to or explain what is needed to make this happen. It seems I have read something about samba? but I cannot find it now. If you could reference me to a how-to or some kind of doc's that would be great! Thanks for your time. Lewis Watson
Re: Amanda and Win2k backups
On Mon, 7 Jan 2002 at 3:09pm, Lewis Watson wrote I currently have amanda backing up several linux servers that I have used to restore data from using amrestore. Now that I have amanda working properly I would like it to back up my win2k machines as well. Can someone point me to or explain what is needed to make this happen. It seems I have read something about samba? but I cannot find it now. If you could reference me to a how-to or some kind of doc's that would be great! Thanks for your time. more $AMANDA-SRC-DIR/docs/SAMBA -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
amandahostauth failed
Running amcheck results it the following: ERROR: localhost.localdomain: [access as amandauser not allowed from [EMAIL PROTECTED]] amandahostsauth failed I have created a .amandahosts file with the following entry: localhost.localdomain amandauser Help? thanks, --charlie -- Charles Farinella Appropriate Solutions, Inc. www.AppropriateSolutions.com[EMAIL PROTECTED] 603.924.6079(v) 603.924.8668(f)
Re: amandahostauth failed
On Mon, 7 Jan 2002 at 5:08pm, Charles Farinella wrote ERROR: localhost.localdomain: [access as amandauser not allowed from [EMAIL PROTECTED]] amandahostsauth failed I have created a .amandahosts file with the following entry: localhost.localdomain amandauser You've got some DNS oddness going on. The canonical answer is to always use fully qualified hostnames with AMANDA -- don't use localhost. It *will* eventually bite you. Also, make sure that your .amandahosts file is in the right place (the $HOME of amandauser) and is readable by amandauser (duh). -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
