Re: Newbie: Tape doesn't eject?
I have just recently changed tape drives, so I was starting over again in my configuration, in essence. I did indeed force run amdump twice the same day since a level 0 of everything didn't fit on one tape and I wanted a full level 0 of everything on the new drive as soon as possible. Of course, nothing much went on from incrementals of the partitions/disks which had just had a full backup. -- Stephen Walton, Professor of Physics and Astronomy, California State University, Northridge [EMAIL PROTECTED] On Wed, 12 Dec 2001, KEVIN ZEMBOWER wrote: > I'm still left with one question. Is it permissible to run more than > one amdump in a day, even if tapes are changed between runs? Would this > do anything positive, like push forward a more extensive dump that might > be normally scheduled for the next day? Or, would amanda just see that > not much has changed in the hour or two since the last dump, and not do > much of anything?
Re: replacing full tapes?
On Wed, 2001-12-12 at 18:20, Michael Perry wrote: > I have sufficient tapes to handle up to a 14 tape tapecycle but some of > them are rather old I think and many are new so I am unsure about the > relative health of the tapes. > If you run amverify you should have a fair chance of discovering bad tapes. If you run an amverify *before* backup you will also discover tapes that have degraded while they've been stored. Amverify just checks if the tapes can be read and the data is valid. Regards, Ole Kaas
[no subject]
unsubscribe [EMAIL PROTECTED]
Re: tapecycle question
On Wed, 12 Dec 2001 at 9:22am, Richard B. Tilley (Brad) wrote > I'm new to amanda. I have succesfully compiled and installed the latest > version from amanda.org onto a RH7.2 machine. I have a Quantum DLT4000 > tape drive with 5 tapes. I would like to run amanda every weekend to do a > full weekly backup (no incrementals) of about 12 networked machines, but I > don't quiet understand how to set the dumpcycle, runcycle and tapecycyle > to do this. Could someone give me a brief example of how to setup these > cycles? dumpcycle 0 (forces full everytime) runspercycle 1 (doesn't really matter) tapecycle (you have 5 tapes) -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
tapecycle question
Hello Everyone, I'm new to amanda. I have succesfully compiled and installed the latest version from amanda.org onto a RH7.2 machine. I have a Quantum DLT4000 tape drive with 5 tapes. I would like to run amanda every weekend to do a full weekly backup (no incrementals) of about 12 networked machines, but I don't quiet understand how to set the dumpcycle, runcycle and tapecycyle to do this. Could someone give me a brief example of how to setup these cycles? Thanks for your time, Brad
Re: replacing full tapes?
Quoting Bort, Paul on Wed, Dec 12, 2001 at 10:49:31AM -0500: > You probably don't want to overwrite BUP2. IIRC, "active tape" means that > the most recent combination of a specific disk and level exists on that > tape. The amoverview command can show what levels were backed up on which > days, for starters. > > You might also want to look at your tapecycle, dumpcycle, and runspercycle > parameters. I usually try to keep dumpcycle at half (or less) of tapecycle, > so that I always have a complete set of tapes to restore from, and the set > I'm currently overwriting. > > Hi- Thanks for the pointer. I had neglected to take into account a few factors about using the settings like dumpcycle, tapecycle, runspercycle. My basic need I think is to backup 5 systems 3 times per week and have a 2 week latency of backups. This is not a huge network :) but I really enjoy the way amanda does the scheduling, planning, etc. Best I have ever found in some years of Linux work. What I am considering is how to build the correct settings for this and not have to buy a lot of very expensive ecrix tapes (almost $100 per tape). I have sufficient tapes to handle up to a 14 tape tapecycle but some of them are rather old I think and many are new so I am unsure about the relative health of the tapes. If I set the following variables, does this look close to my goal? BTW, the goal is to backup systems 3 times per week (Mon, Wed, Fri) and have two weeks of backups: dumpcycle 2 weeks tapecycle 8 tapes runspercycle 3 I am assuming with this setup that amanda will backup 3 times per week according to my crontab and check 3 times per week a bit earlier for the right tape. If I want 2 weeks of backups this would equal 6 tapes and then I would toss in a few extra to take care of any issues like failures, etc. I am backing up 5 systems here at home including a bsd firewall box which is exceedingly important to my sanity. Perhaps the other question is how other smaller LAN users schedule weekly backups or two week backups when doing dumps not every day but perhaps every other day and excluding weekends. Thanks for the answers to the questions everyone has sent. I should have provided all the information on my goals and approaches using amanda first time around. -- Michael Perry | "Do or do not; there is no try" Master Yoda [EMAIL PROTECTED] | http://www.lnxpowered.org
taper tunning to achieve tape streaming
Hi, Does anyone know how to modify the buffering ot the taper so that I can achive tape streaming. I'm using an dlt8000 tape on an enterprise e250 sun server. When write the same files to the tape using tar with blocking factor 126 or 256 the tape gets into full streaming. The tapebufs parameter seems to control the shared memory buffers to taper and not from taper to tape driver. Thanks for any help/ideas, Mihai.
Re: full backups all the time not working
yay it worked adding the reserve 0 field in solved the problem.. TVM -- Martin Joshua Baker-LePain wrote: > On Tue, 11 Dec 2001 at 9:29am, Martin Hepworth wrote > > >>nope still no luck. >> > > Somewhat random question -- there *is* a tape in the drive when you run > amdump, right? IOW, these aren't degraded mode dumps, right? > > >>here's my amanda.conf... >> >> > That all looks good. *sigh* How about sending an email from one of your > runs, as well as the amdump.n and the log.*. > >
RE: Newbie: Tape doesn't eject?
AMANDA does not automatically eject tapes after a backup. If you want to do this, there is an easy way: When you put your amcheck and amdump commands in cron, do something like this: 30 16 * * 1-5 /usr/sbin/amcheck -m DailySet1 0 4 * * 2-6 /usr/sbin/amdump DailySet1 && mt -f /dev/nst0 rewoffl Here's what it means: First line: "30 16": at 4:30 in the afternoon, " * * ": of any day of month or month of year, " 1-5 ": Monday through friday, "/usr/sbin/amcheck": Check to see if we're ready for backups "-m": and mail me any problems, "DailySet1": for configuration DailySet1 Second line: "0 4": at 4:00 in the morning, " * * ": of any day of the month or month of year, " 2-6 ": Tuesday through Saturday, "/usr/sbin/amdump": Run the backup, "DailySet1": for configuration DailySet1, " && ": and if that completes successfully, " mt ": send a tape command " -f /dev/nst0": to the first non-rewinding SCSI tape device " rewoffl ": to rewind and eject. (cron tells stories, they're just in shorthand.) And that's how you get an eject afterwards. Don't worry about using only 10% for now. you can tune that (indirectly) later by adjusting dumpcycle. > -Original Message- > From: KEVIN ZEMBOWER [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, December 11, 2001 5:27 PM > To: [EMAIL PROTECTED] > Subject: Newbie: Tape doesn't eject? > > > Just completed my first amanda backup successfully, mostly. However, I > got an error on three of my five hosts about "missing > results". Looking > this up in the searchable archives led me to the > /tmp/amanda/sendsize.*.debug file, and this showed that I had a > directory named /etc/amandates, instead of a file. I removed the > directory, touched the file, then chmod and chown it to amanda:disk > 0600. Should be fine, I think. > > However, when my backup finished, the report noted that the tape was > only 10% full, and it didn't eject. Is this normal amanda behavior, to > not eject a tape until it's full? I want to run amdump over > again right > away. Should I manually eject the tape (with mt) and insert a new one, > or just start amdump again with the same tape in the drive? > > Thanks, again, for all your help. > > -Kevin Zembower > > - > E. Kevin Zembower > Unix Administrator > Johns Hopkins University/Center for Communications Programs > 111 Market Place, Suite 310 > Baltimore, MD 21202 > 410-659-6139 >
RE: replacing full tapes?
You probably don't want to overwrite BUP2. IIRC, "active tape" means that the most recent combination of a specific disk and level exists on that tape. The amoverview command can show what levels were backed up on which days, for starters. You might also want to look at your tapecycle, dumpcycle, and runspercycle parameters. I usually try to keep dumpcycle at half (or less) of tapecycle, so that I always have a complete set of tapes to restore from, and the set I'm currently overwriting. > -Original Message- > From: Michael Perry [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, December 12, 2001 3:26 AM > To: [EMAIL PROTECTED] > Subject: replacing full tapes? > > > I have been busily backing up my home network which is about > 5 linux/bsd > systems onto an ecrix vxa tape drive. I finally got these errors this > evening on a bup tape: > > *** A TAPE ERROR OCCURRED: [cannot overwrite active tape BUP2]. > Some dumps may have been left in the holding disk. > Run amflush to flush them to tape. > The next tape Amanda expects to use is: BUP3. > > FAILURE AND STRANGE DUMP SUMMARY: > wwwhda2 lev 0 FAILED [disk hda2 offline on www?] > wwwhda1 lev 0 FAILED [disk hda1 offline on www?] > mperry hda2 lev 2 FAILED [no more holding disk space] > > I understand the issue with "www". I did not install dump on this > system before running the backup. How do I correct the tape > error above? > As far as holding disk space goes, I have a whole bunch left > and amcheck > reports that I have over 35g of space left which is plenty. > > I now have cycled to bup3 which is next in line for backup. > I corrected > the issue with 'www" and the lack of dump on that system. I > don't quite > understand how to deal with the tape error about overwriting > active tape > bup2 above. > > Thanks. > > > -- > Michael Perry | "Do or do not; there is no try" Master Yoda > [EMAIL PROTECTED] | http://www.lnxpowered.org >
Re: AmrecoverQuestion_Was Re: 2ndRequest_CreatingIndexFile_FromTape
On Wed, 12 Dec 2001 at 6:44am, ThomasRatliffDDS wrote > Thanks! Now I have valid index file I think. Now my problem is with > amrecover. > > indexfile is > /usr/adm/amanda/home/index/mac-pbG3.orthodontists.info/_/20010916_0.gz > > When I sit as root on the client machine mac-pbG3 and run > > ssh -1 buddies /usr/sbin/amrecover mac-pbG3_full No. amrecover expects to be run on the host you want the files for, not the tape server. It's going to be looking for the wrong index... > 200 Dump host set to buddies.orthodontists.info. See. Your dump host should be mac-pbG3.orthodontists.info, not buddies. If amrecover doesn't work on OSX, then you can just run it on buddies, but you need to do a 'sethost mac-pbG3.orthodontists.info'. > Any ideas what I need to stick in here please amrecover? I should have added the caveat that I'm not sure if just adding the index files will be enough to make amrecover happy, so there's no guarantee this will work. Do you absolutely *need* amrecover? There are other ways of getting the files off... -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
AmrecoverQuestion_Was Re: 2ndRequest_CreatingIndexFile_FromTape
Thanks! Now I have valid index file I think. Now my problem is with amrecover. indexfile is /usr/adm/amanda/home/index/mac-pbG3.orthodontists.info/_/20010916_0.gz When I sit as root on the client machine mac-pbG3 and run ssh -1 buddies /usr/sbin/amrecover mac-pbG3_full root@buddies's password: AMRECOVER Version 2.4.2p2. Contacting server on buddies.orthodontists.info ... 220 buddies AMANDA index server (2.4.2p2) ready. 200 Access OK Setting restore date to today (2001-12-12) 200 Working date set to 2001-12-12. 200 Config set to mac-pbG3_full. 200 Dump host set to buddies.orthodontists.info. $CWD '/root' is on disk '/' mounted at '/'. 200 Disk set to /. No index records for disk for specified date If date correct, notify system administrator Invalid directory - /root amrecover> and enter setdate 2001-09-16 setdate 2001-09-16 200 Working date set to 2001-09-16. No index records for cwd on new date Setting cwd to mount point amrecover> Any ideas what I need to stick in here please amrecover? On Wed, 12 Dec 2001, Joshua Baker-LePain wrote: > On Tue, 11 Dec 2001 at 1:37pm, ThomasRatliffDDS wrote > > > Is there any FAQ that describes how to Create an Index file from tape? > > > No, but I'll give it a shot. > > In indexdir (as specified in amanda.conf), there's a directory for each > host. In each host's directory, there's a directory for each disk > (subbing '_' for '/'). In each disk directory, there's a gzipped index > file named by the date of the amanda run and the level, e.g. this > morning's level one is 20011212_1.gz. The contents of that file are > generated on the fly by the backup program of choice. If, e.g., you use > tar, then it's a 'tar t'. Actually, the exact command (from > sendbackup*debug) is '/bin/gtar -tf - 2>/dev/null | sed -e 's/^\.//' . > > So, piping each backup image through 'tar t' (or the equivalent for > restore) should do it. Remember to skip over the first 32k of each image > on tape, as that's the amanda header. > > Good luck. > > -- > Joshua Baker-LePain > Department of Biomedical Engineering > Duke University >
Re: Newbie: Tape doesn't eject?
Thanks, Stephen, for sharing your experience with amanda with me. I'll add the eject to my crontab; that's a good idea. I suspect that what's confusing amanda in making my initial backup is the fact that I've still got running another, homebrew, backup system that's also writing to /etc/dumpdates. On the other hand, the report does say that the size of the backup of the two machines that worked is 3.5G, which might be close to a level 0 backup on these two machines. I'm still left with one question. Is it permissible to run more than one amdump in a day, even if tapes are changed between runs? Would this do anything positive, like push forward a more extensive dump that might be normally scheduled for the next day? Or, would amanda just see that not much has changed in the hour or two since the last dump, and not do much of anything? Thanks for your thoughts. -Kevin Zembower >>> Stephen Walton <[EMAIL PROTECTED]> 12/12/01 12:44AM >>> Hi, > /tmp/amanda/sendsize.*.debug file, and this showed that I had a > directory named /etc/amandates, instead of a file. I mad the same mistake. > However, when my backup finished, the report noted that the tape was > only 10% full, and it didn't eject. The 10% full number depends on timing of full dumps and so on. If you've set everything up right, then either amanda should have done a full dump of everything the first time out, or postponed some of them for later. I see everything from 10% to 99% full on my regular backups depending on how the mix of full & incrementals works out. amdump does not eject a tape. In my crontab I have something like: 5 12 * * * /opt/amanda/sbin/amdump daily && /bin/mt -t /dev/rmt/0m offl to get a tape eject when the backup is done. -- Stephen Walton, Professor of Physics and Astronomy, California State University, Northridge [EMAIL PROTECTED]
Re: 2ndRequest_CreatingIndexFile_FromTape
On Tue, 11 Dec 2001 at 1:37pm, ThomasRatliffDDS wrote > Is there any FAQ that describes how to Create an Index file from tape? > No, but I'll give it a shot. In indexdir (as specified in amanda.conf), there's a directory for each host. In each host's directory, there's a directory for each disk (subbing '_' for '/'). In each disk directory, there's a gzipped index file named by the date of the amanda run and the level, e.g. this morning's level one is 20011212_1.gz. The contents of that file are generated on the fly by the backup program of choice. If, e.g., you use tar, then it's a 'tar t'. Actually, the exact command (from sendbackup*debug) is '/bin/gtar -tf - 2>/dev/null | sed -e 's/^\.//' . So, piping each backup image through 'tar t' (or the equivalent for restore) should do it. Remember to skip over the first 32k of each image on tape, as that's the amanda header. Good luck. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
replacing full tapes?
I have been busily backing up my home network which is about 5 linux/bsd systems onto an ecrix vxa tape drive. I finally got these errors this evening on a bup tape: *** A TAPE ERROR OCCURRED: [cannot overwrite active tape BUP2]. Some dumps may have been left in the holding disk. Run amflush to flush them to tape. The next tape Amanda expects to use is: BUP3. FAILURE AND STRANGE DUMP SUMMARY: wwwhda2 lev 0 FAILED [disk hda2 offline on www?] wwwhda1 lev 0 FAILED [disk hda1 offline on www?] mperry hda2 lev 2 FAILED [no more holding disk space] I understand the issue with "www". I did not install dump on this system before running the backup. How do I correct the tape error above? As far as holding disk space goes, I have a whole bunch left and amcheck reports that I have over 35g of space left which is plenty. I now have cycled to bup3 which is next in line for backup. I corrected the issue with 'www" and the lack of dump on that system. I don't quite understand how to deal with the tape error about overwriting active tape bup2 above. Thanks. -- Michael Perry | "Do or do not; there is no try" Master Yoda [EMAIL PROTECTED] | http://www.lnxpowered.org
