Re: Help, Strange Error !!
Hi, have you tried it with a brand new tape? or only with tapes the old drive failed on? I had a sdt-9000 die similar, producing write-errors with medium-errors. the Tapes wreer unusable even in a new drive until i took a big magnet and wiped every bit on these tapes. after that they started working again. The defective drive must have written such a mess at the header peace of the tape(s), so no other drive's would write to them until they where bulk erased. Christoph Roberto Samarone Araújo (RSA) schrieb: Hi, I have an Amanda Backup that was working fine now, when I try to use: su -c "/usr/sbin/amlabel Daily1 DAILY1-01" backup, the system return me: st0: Error with sense data: Current st09:00: sense key Medium Error Additional sense indicates Write error If I try: mt erase /dev/st0, it return me: st0: Error with sense data: Current st09:00: sense key Medium Error Additional sense indicates Write error mt: /dev/tape: Input/Output error I change my SDT-9000 tape to a new one and the problem persist. I saw on the logs the messages: st0: Block limits 1 - 16777215 bytes st0: Error with sense data: Current st09:00 sense key Medium Error Additional sense indicates Write error Does anyone could help me please ? When a try to recover a backup it worked fine. Roberto Samarone Araujo
(광고)아직도 부진한 매출에 고민만 하고 계십니까?? @
팝업서비스-신청즉시 매출이 쑥쑥!! 고정 방문객 1만명 절대 꿈이 아닙니다. 메일맨Pro을 이용하시면 3,000만 네티즌이 나의 고객!! 이제 마케팅 끝~~ 사이트 홍보, 상품 광고는 이제 Mail Man 하나로 자동으로 끝내세요~ 자동 이메일 추출, 대량 메일 발송을 하나로 통합한 솔루션 자동 페이지 검색 방식으로 사이트와 게시판에서 이메일을 자동으로 수집합니다. 최대 200개를 동시 발송하여 시간당 5만개 이상 발송이 가능합니다. 정통부 이메일 법규 완벽준수!! 뛰어난 기능과 저렴한 가격!! 고객님에 홍보 솔루션은 메일맨이 도와드리겠습니다. 메일맨을 선택하신 고객님은 벌써 성공자 이십니다. [홈페이지 바로가기] 메일맨프로의 이메일 추출기 메일맨프로의 이메일 발송기 MailMan Pro의 기능과 특징 [홈페이지 바로가기] 1. 통합형 : 이메일 수집 + 이메일 발송 + 수신거부자 관리 + 수신확인 2. 검색어를 통한 사이트의 모든 페이지와 게시판에서 일괄추출 기능 3. 이메일 수집경로 표시와 수집거부 사이트에서의 수집금지 기능 4. 자체 메일 서버 탑제 : 메일서버 없이 대량 발송 5. SMTP를 설정하면 한메일등 모든 메일 발송가능 6. 그룹관리 : 수집된 이메일을 그룹별, 메일발송일 별로 관리 7. 쉬운사용법 : 초보자도 쉽게 사용 8. 간편한 수신거부자 관리및 수신자확인 기능 9. 백업기능 : 추출이메일을 백업 보관 및 기존 이메일 불러오기 가능 10. HTML 지원 : HTML미리보기, HTML 메일 발송 11. 뛰어난 기능에도 파격적인 저렴한 가격! 직접 평가판을 다운받아 사용해 보시고 기능및 가격을 비교해 주세요. [MailMan Pro 평가판 다운로드] ⊙ 그밖의 인터넷 마케팅 프로그램 ⊙ [홈페이지 바로가기] ◈ 게시판 추출 글등록기 ◈ 바탕화면 아이콘 생성기 ◈ IP변환 프로그램등... If you don't want this type of information or e-mail, please click the 'refuse' button. 정보를 더 이상 원치 않으시면 [수신거부]를 눌러 주세요. 인터넷마케팅전문사이트ㅣE_mailㅣ☏ 011-642-6236.ㅣCopyright ⓒ 2001 Hidream All Rights Reserved [수집URL] http://daily.daemonnews.org/view_story.php3?story_id8
Re: [UPDATE] How to control which tape is next?
On Wednesday 22 October 2003 21:19, Matt Hyclak wrote: >On Wed, Oct 22, 2003 at 08:54:52PM -0400, Gene Heskett enlightened us: >> >> Q: Does this automaticly set the ownerships and perms in the >> >> built rpm? Amanda should be built by a non-priviledged user, >> >> then installed by root. Otherwise the perms get fubared. I >> >> ask because I've never done it this way to test. >> > >> >Yes, it goes through after the files are built and sets the >> > appropriate ownership and permissions correctly. It assumes the >> > user will be called amanda, which is the "right way" to do it on >> > a RH system. >> >> Great Matt. And that pretty much takes care of my first >> objection. Even better if the installer actually setup that user, >> and made that user a member of the needed group too. > >From the .spec: > >%pre >useradd -M -n -g disk -o -r -d /var/lib/amanda -s /bin/bash \ > >-c "Amanda user" -u 33 amanda >/dev/null 2>&1 || : >:-) >: Well, like Howard Cosell, I never played the game myself :) >> The second would be taken care of if the building of the src to an >> rpm it was trained to barf voluminously and exit if the config >> (the spec file) still says 'localhost' anyplace in it. A bit >> arbitrary maybe, but for gnubies, a "barked knuckle" the first >> time sure beats no recovery when the gnubie needs it 6 months on >> down the log. > >Hmmm, an interesting idea. I'll take that up with Jay tomorrow if I > get a chance. The use of localhost is a sleeping dog that offers little or no long term good. Its nice to be able to use it to get started, but its long term useage is like a 3 pack a day habit, hard on ones health and well being on the long run. It really should be nipped in the first days build, hard enough to draw mental blood IMO. Make them look up the manpages if they have them, or read the comments in the .spec file, and fix it right up front the first time. >> >Which is why I've only posted the src.rpm and encouraged people >> > to rebuild it using the correct settings for their site. The >> > problem is in distributing it on a large scale (i.e. part of a >> > distro), but there really is no good solution to that. If there >> > is interest in the src.rpm, I'll be sure to post it as it gets >> > updated (assuming Jay doesn't beat me to it). >> > >> >Matt >> >> I think Jay needs the help. Not because he is doing a bad job, he >> isn't, but when one is that busy, stuff starts falling thru the >> cracks... Maybe you could take over the amanda rpm maintainance >> for those distros that use rpms, says he, donning the kevlar >> underwear. >> >> :-) > >I'm more than happy to give him a hand, but I don't think RedHat > would like it too much if I became the official maintainer :-) > Besides, he has access to all the test equipment, not me. I'll be > sure to keep feeding him fixes/updates/patches, etc. If there are > any requests for features, speak up on the list (that goes for > everyone). I'm not sure I want to get into rpm-ing snapshots at > this point, but if there's enough yelling for that, I can look into > doing that. > >(I did talk with Jay briefly today, and he has been busy with other > things, but has some time now to return to the state of the amanda > packages). Sounds good to me! >Matt -- Cheers, Gene AMD [EMAIL PROTECTED] 320M [EMAIL PROTECTED] 512M 99.21% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attornies please note, additions to this message by Gene Heskett are: Copyright 2003 by Maurice Eugene Heskett, all rights reserved.
Re: [UPDATE] How to control which tape is next?
On Wed, Oct 22, 2003 at 08:54:52PM -0400, Gene Heskett enlightened us: > >> Q: Does this automaticly set the ownerships and perms in the built > >> rpm? Amanda should be built by a non-priviledged user, then > >> installed by root. Otherwise the perms get fubared. I ask > >> because I've never done it this way to test. > > > >Yes, it goes through after the files are built and sets the > > appropriate ownership and permissions correctly. It assumes the > > user will be called amanda, which is the "right way" to do it on a > > RH system. > > Great Matt. And that pretty much takes care of my first objection. > Even better if the installer actually setup that user, and made that > user a member of the needed group too. > >From the .spec: %pre useradd -M -n -g disk -o -r -d /var/lib/amanda -s /bin/bash \ -c "Amanda user" -u 33 amanda >/dev/null 2>&1 || : :-) > The second would be taken care of if the building of the src to an rpm > it was trained to barf voluminously and exit if the config (the spec > file) still says 'localhost' anyplace in it. A bit arbitrary maybe, > but for gnubies, a "barked knuckle" the first time sure beats no > recovery when the gnubie needs it 6 months on down the log. > Hmmm, an interesting idea. I'll take that up with Jay tomorrow if I get a chance. > >Which is why I've only posted the src.rpm and encouraged people to > > rebuild it using the correct settings for their site. The problem > > is in distributing it on a large scale (i.e. part of a distro), but > > there really is no good solution to that. If there is interest in > > the src.rpm, I'll be sure to post it as it gets updated (assuming > > Jay doesn't beat me to it). > > > >Matt > > I think Jay needs the help. Not because he is doing a bad job, he > isn't, but when one is that busy, stuff starts falling thru the > cracks... Maybe you could take over the amanda rpm maintainance for > those distros that use rpms, says he, donning the kevlar underwear. > :-) > I'm more than happy to give him a hand, but I don't think RedHat would like it too much if I became the official maintainer :-) Besides, he has access to all the test equipment, not me. I'll be sure to keep feeding him fixes/updates/patches, etc. If there are any requests for features, speak up on the list (that goes for everyone). I'm not sure I want to get into rpm-ing snapshots at this point, but if there's enough yelling for that, I can look into doing that. (I did talk with Jay briefly today, and he has been busy with other things, but has some time now to return to the state of the amanda packages). Matt -- Matt Hyclak Department of Mathematics Department of Social Work Ohio University (740) 593-1263
Re: [UPDATE] How to control which tape is next?
On Wednesday 22 October 2003 14:45, Matt Hyclak wrote: >On Wed, Oct 22, 2003 at 11:07:17AM -0400, Gene Heskett enlightened us: >> >FWIW, I have made packages of 2.4.4-p1 that are pretty much the >> > RH packages with a couple tweaks to the .spec file. Namely, >> > there are 2 variables at the top of the .spec to define your >> > tapeserver and your config name. The problem with packaging >> > binary files for amanda is that you have to resort to using >> > localhost where a hostname is required so the thing will at >> > least mostly work. Because of this, I put the variable at the >> > top of the spec file and recommend people rebuild the source rpm >> > after making the appropriate changes to the .spec. >> > >> >If anyone is interested in this, you can get it from (sorry it >> > wraps): >> > http://www.math.ohiou.edu/mirror/casit/contrib/9/SRPMS/amanda-2. >> >4.4 p1-2mrh3.src.rpm >> > >> >To install it "correctly" goes something like this: >> > >> >$ rpm -i amanda-2.4.4p1-2mrh3.src.rpm >> >edit the .spec file (in /usr/src/redhat/SPECS if you build as >> > root) >> >> Q: Does this automaticly set the ownerships and perms in the built >> rpm? Amanda should be built by a non-priviledged user, then >> installed by root. Otherwise the perms get fubared. I ask >> because I've never done it this way to test. > >Yes, it goes through after the files are built and sets the > appropriate ownership and permissions correctly. It assumes the > user will be called amanda, which is the "right way" to do it on a > RH system. Great Matt. And that pretty much takes care of my first objection. Even better if the installer actually setup that user, and made that user a member of the needed group too. The second would be taken care of if the building of the src to an rpm it was trained to barf voluminously and exit if the config (the spec file) still says 'localhost' anyplace in it. A bit arbitrary maybe, but for gnubies, a "barked knuckle" the first time sure beats no recovery when the gnubie needs it 6 months on down the log. >> >$ rpmbuild -ba amanda.spec >> ># rpm -Uvh amanda-2.4.4p1-2mrh3.i386.rpm ... >> > (in /usr/src/redhat/RPMS/i386 if you build as root) >> > >> >You don't have to build amanda as root from the rpm (and I >> > recommend that you don't just on principle). I've fed these >> > changes up to Jay and he's created bugzilla entries (or at least >> > was going to. If he hasn't, maybe this can be his poke in the >> > ribs...) to make it a little easier to build amanda for your >> > location and still have the package be managed instead of >> > resorting to *cringe* tarballs. ;-) >> > >> >Matt >> >> Just out of curiosity, why the cring at the thought of tarballs? > >In general because you often have little control over what a 'make > install' does. Many applications out there ignore PREFIX settings > and the like and you end up with files barfed all over your system. > I don't think amanda is that way, but I don't want to take that > chance :-) Nah, amanda is clean in that regard. That "make install" has been tweaked, then the tweaks have been tweaked until its as solid as any long term project should be. In my lingo, thats the equivalent of "10 foot tall and bulletproof". :-) But you are right too, many otherwise great projects fail because the Makefile.in was just an afterthought, not always valid for oddball hardware etc. >> There are good and valid reasons to use the rpms and have a >> managed install. In amanda's case, where the correct perms and >> such are required for proper overall functionality, and which may >> vary according to the users whims, something the rpms don't seem >> to handle right, I've found the tarballs to be much the easier way >> to maintain amanda. And I've learned the hard way to never, ever, >> let the up2date utility anywhere near your amanda install. One >> early version, if not the first one released, must have been a bit >> buggy though. I did not check anything amanda related, but it did >> it anyway. Took me 2 days to clean up the mess that made. > >Yes, amanda is one thing I make sure yum ignores since I upgrade > that by hand myself. > >> We also spend about 25% of our support efforts here on this list >> trying to convince gnubies that they cannot run it reliably using >> localhost. Most probably have acquired the localhost habit from >> an rpm install. The README etc in the tarballs carry warnings, >> but theres no good place in the rpms for such advisories. After a >> while some of us can get downright bored, even growly about it. >> My apologies in that case :) > >Which is why I've only posted the src.rpm and encouraged people to > rebuild it using the correct settings for their site. The problem > is in distributing it on a large scale (i.e. part of a distro), but > there really is no good solution to that. If there is interest in > the src.rpm, I'll be sure to post it as it gets updated (assuming > Jay doesn't beat me to it). >
amanda build problem
There aren't pre-compiled binaries around with port restrictions already in place, are there ? >From my amanda config.log $ ./configure --with-tcpportrange=10084,10100 --with-udpportrange=932,948 --with-group=sys --with-user=amanda >From my build [newton] /tmp/amanda-build/common-src 27> make source='alloc.c' object='alloc.lo' libtool=yes \ depfile='.deps/alloc.Plo' tmpdepfile='.deps/alloc.TPlo' \ depmode=none /bin/ksh ../config/depcomp \ /bin/ksh ../libtool --mode=compile /opt/SUNWspro/bin/cc -DHAVE_CONFIG_H -I. -I. -I../config -I./../regex-src -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -g -c -o alloc.lo `test -f 'alloc.c' || echo './'`alloc.c mkdir .libs /opt/SUNWspro/bin/cc -DHAVE_CONFIG_H -I. -I. -I../config -I./../regex-src -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -g -c alloc.c -KPIC -DPIC -o alloc.o "/usr/include/sys/model.h", line 35: syntax error before or at: / cc: acomp failed for alloc.c *** Error code 1 make: Fatal error: Command failed for target `alloc.lo' Oh well - will attach a DDS drive to the box tomorrow, then the FW will not matter. thanks
Mixing backups to disk and tape?
Since the list has been pretty quiet lately: Is there a (relatively) easy way of backing up to both disk and tape from a single config? I was thinking of using the file driver to do backups to disk (for faster recoveries) while also using tapes (for archiving and offsite purposes). Options I've considered: Just using the file driver and then dd'ing those to tape later. But since I couldn't keep as many file 'tapes' around as I would keep tapes, how would I handle recoveries of older data? Just delete the file 'tapes' as needed, and to do a restore, first dd the tape back to the properly named file? Using the RAIT driver (does it still exist?) to mirror a backup between disk and file? How would a restore work in this case; would Amanda expect both tape and file to be present? Could a changer script handle the two diferent mediums? Two configs. It would double the backup window and I"m soaking some WAN links too long already. Something else? My idea is to somehow use the file driver to keep a couple of dumpcycle's worth of backups on disk, but to also have a tapecycle's worth of tapes (which is many times dumpcycle). Anybody tried anything similar? Frank -- Frank Smith [EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
port range
...realized this might be an amanada-hackers thing. I've got a fairly old system Solaris 2.6, that I've just pushed into a DMZ and in order to reach the previous amanda server I've been asked to recompile so that we can restrict the port ranges. Possible in future releases that amanda can be made more restrictive at run time (than it was at compile time) by specifying things like port-range in amanda.conf or perhaps in this case some server client-specific config file ? I seem to be activating the dump utility though the dump is not being returned to the server, I'm hoping that I don't also need to recompile the server - there are multiple clients of various architictures and OS versions, up through Solaris 9 and Irix. thanks, Brian --- Brian R Cuttler [EMAIL PROTECTED] Computer Systems Support(v) 518 486-1697 Wadsworth Center(f) 518 473-6384 NYS Department of HealthHelp Desk 518 473-0773
Re: How to handle archival runs (again)?
On Wed, Oct 22, 2003 at 05:35:38PM +0200, Toralf Lund wrote: > Reviewing the amanda config again in conjunction with a tape format > update... > I forget (and list search doesn't return anything conclusive): How do > you people recommend handling archival runs? There are two obvious ways: > > 1. Via a special config. > 2. Using the normal config, but special labels and "amadmin ... no-reuse" > > What are the pros and cons of each of these? > > Note: I know that one argument against 2) is that you normally want > different behaviour with regard to incrementals, but that doesn't really > apply in my case as there are no incrementals in any case (in the main > config; I have a separate one for incrementals as they are written to a > different medium.) > I backup only a couple of systems. But I use separate archive configs. Note the plural, I use 3. One archive config is for system DLE's (root, var, usr, ...) and the second for user data DLE's(ArchSys & ArchUser). However the config dirs for these two configs only have two files, amanda.conf and disklist. Both configs are setup to use the third config, Archive, for all the common things. Like the index, logs, changer info, tapelist, ... (they both use the same tape sequence). I split them into sys and user for several reasons: - Shorten the time to make an archive of one or the other. Then I can do an ArchUser this Sunday (no DailySet run from Sat -> Sunday) and an ArchSys next weekend. - I don't do the sys as often as the user - I wanted the ability to do a system backup before things like OS upgrades which would have no effect on the user data. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: amrecover: Why does it use disklist and log files
Jean-Louis Martineau wrote: Hi Toralf, On Wed, Oct 22, 2003 at 10:09:56AM +0200, Toralf Lund wrote: As far as I can't tell, amrecover won't work unless 1. Log file from the backup you are trying to recover is still present The log are needed to find which dump are on which tape and where on that tape. Isn't that information in the index and/or "curinfo"? 2. DLE is still in the disklist That's what amanda use, but for some command (eg, amrecover, amadmin find, ...) it should build its disklist dynamicaly from the log file? That will help a lot if you remove an entry from your disklist. Quite. Why? Shouldn't amrecover work from the index alone? Having an index doesn't mean that the dump is somewhere. And having the logfile does? Seems more logical to me to view the amanda *database* as the authoritative information, and logfiles as purely informative data that may be removed at the user's discretion - Toralf
Re: How to handle archival runs (again)?
I use a separate config for Archives. I find it easy to maintain and easy to think about. The disklist looks the same for both. And the amanda.conf looks the same for both (with the exception of the config name). I do monthly archives. So I set up the amanda.conf for two years worth of tapes (24 tapes). When it's time for me to make an archive, I do the following: - find a new tape and label it with amlabel - force a full dump of all filesystems with "amadmin force" command Surely you don't need that, as long as the dumpcycle is correctly configured? - run the amdump - verify I can restore from the tape by grabbing random files and directories off the archive and comparing them to what's on the filesystem (for static files at least) BTW, I was thinking that a separate config might be a bit of a hassle as it isn't practically possible to run a normal dump *and* the archive one on the same day. Then it struck me that I might schedule the archival for the weekend, now that we have a tape changer... - Toralf
Re: [UPDATE] How to control which tape is next?
On Wed, Oct 22, 2003 at 11:07:17AM -0400, Gene Heskett enlightened us: > >FWIW, I have made packages of 2.4.4-p1 that are pretty much the RH > > packages with a couple tweaks to the .spec file. Namely, there are > > 2 variables at the top of the .spec to define your tapeserver and > > your config name. The problem with packaging binary files for > > amanda is that you have to resort to using localhost where a > > hostname is required so the thing will at least mostly work. > > Because of this, I put the variable at the top of the spec file and > > recommend people rebuild the source rpm after making the > > appropriate changes to the .spec. > > > >If anyone is interested in this, you can get it from (sorry it > > wraps): > > http://www.math.ohiou.edu/mirror/casit/contrib/9/SRPMS/amanda-2.4.4 > >p1-2mrh3.src.rpm > > > >To install it "correctly" goes something like this: > > > >$ rpm -i amanda-2.4.4p1-2mrh3.src.rpm > >edit the .spec file (in /usr/src/redhat/SPECS if you build as root) > > Q: Does this automaticly set the ownerships and perms in the built > rpm? Amanda should be built by a non-priviledged user, then > installed by root. Otherwise the perms get fubared. I ask because > I've never done it this way to test. > Yes, it goes through after the files are built and sets the appropriate ownership and permissions correctly. It assumes the user will be called amanda, which is the "right way" to do it on a RH system. > >$ rpmbuild -ba amanda.spec > ># rpm -Uvh amanda-2.4.4p1-2mrh3.i386.rpm ... > > (in /usr/src/redhat/RPMS/i386 if you build as root) > > > >You don't have to build amanda as root from the rpm (and I recommend > > that you don't just on principle). I've fed these changes up to Jay > > and he's created bugzilla entries (or at least was going to. If he > > hasn't, maybe this can be his poke in the ribs...) to make it a > > little easier to build amanda for your location and still have the > > package be managed instead of resorting to *cringe* tarballs. ;-) > > > >Matt > > Just out of curiosity, why the cring at the thought of tarballs? > In general because you often have little control over what a 'make install' does. Many applications out there ignore PREFIX settings and the like and you end up with files barfed all over your system. I don't think amanda is that way, but I don't want to take that chance :-) > There are good and valid reasons to use the rpms and have a managed > install. In amanda's case, where the correct perms and such are > required for proper overall functionality, and which may vary > according to the users whims, something the rpms don't seem to handle > right, I've found the tarballs to be much the easier way to maintain > amanda. And I've learned the hard way to never, ever, let the > up2date utility anywhere near your amanda install. One early > version, if not the first one released, must have been a bit buggy > though. I did not check anything amanda related, but it did it > anyway. Took me 2 days to clean up the mess that made. > Yes, amanda is one thing I make sure yum ignores since I upgrade that by hand myself. > We also spend about 25% of our support efforts here on this list > trying to convince gnubies that they cannot run it reliably using > localhost. Most probably have acquired the localhost habit from an > rpm install. The README etc in the tarballs carry warnings, but > theres no good place in the rpms for such advisories. After a while > some of us can get downright bored, even growly about it. My > apologies in that case :) > Which is why I've only posted the src.rpm and encouraged people to rebuild it using the correct settings for their site. The problem is in distributing it on a large scale (i.e. part of a distro), but there really is no good solution to that. If there is interest in the src.rpm, I'll be sure to post it as it gets updated (assuming Jay doesn't beat me to it). Matt -- Matt Hyclak Department of Mathematics Department of Social Work Ohio University (740) 593-1263
Proposal for more run-time configuration
On Wed, Oct 22, 2003 at 11:07:17AM -0400, Gene Heskett wrote:
> On Wednesday 22 October 2003 08:56, Matt Hyclak wrote:
> > The problem with packaging binary files for
> > amanda is that you have to resort to using localhost where a
> > hostname is required so the thing will at least mostly work.
>
> We also spend about 25% of our support efforts here on this list
> trying to convince gnubies that they cannot run it reliably using
> localhost. Most probably have acquired the localhost habit from an
> rpm install.
This conflict results from a shortcoming in Amanda, namely that
many values that are only needed at run time, must still be
specified at configure time. ISTM that configure-time options
should mostly be:
- Those needed to get the package built and installed (e.g.
--with-includes, --with-suffixes).
- Parameters specific to a particular host environment (e.g.
--with-rundump, --with-broken-fsf). Each of these will have
one optimal value for any given platform, and if someone is
creating a binary distribution, Gentoo ebuild, etc., it's
clearly their job to pick the right one.
- Anything else that's intrinsically needed at compile time
(e.g. --with-assertions)
Anything else should be left to a run-time config file, and that
goes double for values related to site policy.
Unfortunately, doing so will mean introducting a config file onto
Amanda client hosts. I understand that this was purposely
avoided; I believe that decision should be reconsidered. As I
understand it, the purpose of avoiding client-side config files
was to concentrate all configuration on the server, so that if
one wants to tweak something, one need not run around to all the
machines to change it on each one. That's fine for parameters
which one can indeed change on the server. But that's not the
case for every parameter in Amanda. What's the situation with
the others?
Contrary to the design goal, parameters such as --with-debug-days
must still be changed on each client -- but the only way to do
that is to rebuild and reinstall Amanda. Not exactly a savings
in convenience over editing a client-side config file. For
parameters like --with-tape-server, one can override the
configure-time default (by passing a command-line option to
amrecover); but the only way to permanently change the default,
again, is to rebuild and reinstall.
Thus, I believe that introducing a client-side config file --
just one, *not* one per Amanda configuration -- will not only
help solve the current problem, but will make sysadmins' lives
easier in other respects as well.
My proposal is this:
- Add a global configuration file, directly under the
--with-configdir directory. One possible name might be
global.conf, but that's definitely up for discussion. So the
structure would look like:
/global.conf
//amanda.conf
//disklist
where comes from "configure --with-configdir="
- global.conf should exist on both server and clients (if the
server is also a client, both roles share the same copy of
the file)
- When looking for a config parameter, use the first of these
that's found:
- if you have a //amanda.conf (i.e. you're
in the in the Amanda-server role, and you know which
configuration you're working with), the value in that
file
- the value in /global.conf
- the compiled in default, if any (see below)
- If none of those are available, abort
- For config parameters that are searchable in this way, it
should NOT be required to specify them at configure time. If
you don't, the compiled in default will be "undefined", in
which case you WILL be required to specify the value in a
run-time config file (either global.conf or the appropriate
amanda.conf).
- ISSUE: What if /global.conf doesn't exist? I'd like
to say, just ignore the fact (maybe report it as an
"info"-level log message), and skip to the next step on the
search for a value.
FWIW, here's my stab at classifying Amanda 2.4.4's many configure
options.
These are properly configure-time options:
--with-includes=DIRsite header files for readline, etc in DIR
--with-libraries=DIR site library directories for readline, etc in DIR
--with-suffixesinstall binaries with version string appended to name
--without-client do not build client stuff
--without-server do not build server stuff (set --without-restore)
--without-restore do not build amrestore nor amidxtaped
--without-amrecoverdo not build amrecover
--with-rundump use rundump (setuid-root) to invoke dump
--with-broken-fsf only enable if tape fsf calls fail mid-file
--with-db={text,db,dbm,gdbm,ndbm} use the selected database format text
--with-mmapforce use of mmap instead of shared memory support
--with-assertions compile assertions into code
--with-gnu-ld assume the
Re: Help, Strange Error !!
I had something very similar to this happen with my AIT-2 changer when it had to be reset to company defaults. Unbeknownst to me, the default tape for the changer (drive? I don't remember) was DLT -- and, when it didn't find AIT-2 tapes, it complained bitterly, but not with any error that was obvious. If you've done anything "interesting" to your changer/drive lately, you just might want to make sure it's still configured correctly. $.02, Ken D'Ambrosio Sr. SysAdmin, Xanoptix, Inc. > Roberto Samarone Araújo (RSA) wrote: > >>Hi, >> >> I have an Amanda Backup that was working fine now, when I try to >> use: >>su -c "/usr/sbin/amlabel Daily1 DAILY1-01" backup, the system return me: >> >> st0: Error with sense data: Current st09:00: sense key Medium >>Error >> Additional sense indicates Write error >> >> >> If I try: mt erase /dev/st0, it return me: >> >>st0: Error with sense data: Current st09:00: sense key Medium >>Error >>Additional sense indicates Write error >>mt: /dev/tape: Input/Output error >> >>I change my SDT-9000 tape to a new one and the problem persist. >> >>I saw on the logs the messages: >> >>st0: Block limits 1 - 16777215 bytes >>st0: Error with sense data: Current st09:00 sense key Medium >>Error >>Additional sense indicates Write error >> >>Does anyone could help me please ? When a try to recover a backup >> it >>worked fine. >> >>Roberto Samarone Araujo >> >> >> >> >> > I'd check my perms on /dev/st0 as well...make sure the restore didn't > change any setting back that you may have edited. Otherwise you could > have a hardware problem...but I'd lean more to perms. > > =G=
Re: amrecover: Why does it use disklist and log files
Hello Jean- Jean-Louis Martineau wrote: Hi Toralf, On Wed, Oct 22, 2003 at 10:09:56AM +0200, Toralf Lund wrote: As far as I can't tell, amrecover won't work unless 1. Log file from the backup you are trying to recover is still present The log are needed to find which dump are on which tape and where on that tape. We have the need to keep both weekly full and daily incrementals on disk (tapeless) so that we won't have to go to slow media. We then copy full backups (data and inex) to magnetic tapes for a rotation of 8 tapes using tar. The disk won't hold up to 8 full backups, so it is set up with only one "tape". After full backup, data and index are copied immediately to tape. This way, we can go back one week, up to any day, using data on disk; and go back every week before that, using data on tapes. We do not care much about previous week's incrementals. Recover using tapes is done, first with untarring it from tape onto disk and replacing necessary index (with data on disk renamed first for preservation, of course), then running amrecover. My questions is: Must I have log files tarred to tape along with data and index in order to run amrecover? I have never needed to go back more than one week from tape. Thanks in advance.
Re: amrecover: Why does it use disklist and log files
Hi Toralf, On Wed, Oct 22, 2003 at 10:09:56AM +0200, Toralf Lund wrote: > As far as I can't tell, amrecover won't work unless > > 1. Log file from the backup you are trying to recover is still present The log are needed to find which dump are on which tape and where on that tape. > 2. DLE is still in the disklist That's what amanda use, but for some command (eg, amrecover, amadmin find, ...) it should build its disklist dynamicaly from the log file? That will help a lot if you remove an entry from your disklist. > Why? Shouldn't amrecover work from the index alone? Having an index doesn't mean that the dump is somewhere. Jean-Louis -- Jean-Louis Martineau email: [EMAIL PROTECTED] Département IRO, Université de Montréal C.P. 6128, Succ. CENTRE-VILLETel: (514) 343-6111 ext. 3529 Montréal, Canada, H3C 3J7Fax: (514) 343-5834
RE: How to handle archival runs (again)?
I use a separate config for Archives. I find it easy to maintain and easy to think about. The disklist looks the same for both. And the amanda.conf looks the same for both (with the exception of the config name). I do monthly archives. So I set up the amanda.conf for two years worth of tapes (24 tapes). When it's time for me to make an archive, I do the following: - find a new tape and label it with amlabel - force a full dump of all filesystems with "amadmin force" command - run the amdump - verify I can restore from the tape by grabbing random files and directories off the archive and comparing them to what's on the filesystem (for static files at least) I've been doing this for a couple years, and it's worked out really well. Regards, Michael Martinez Linux System Administrator ISTM/CSREES United States Department of Agriculture --> -Original Message- --> From: JC Simonetti [mailto:[EMAIL PROTECTED] --> Sent: Wednesday, October 22, 2003 11:57 AM --> To: Toralf Lund --> Cc: [EMAIL PROTECTED] --> Subject: Re: How to handle archival runs (again)? --> --> --> For archival purposes, personnaly I use a combination of --> your two solutions. --> I use a different config of Amanda with "dumpcycle 0", --> "strategy noinc", but the main goal of a different config --> for me is concerning the logs: it's easier to restore data --> if your archives are not in the middle of your incremental backups. --> Moreover if you play with the "no-reuse" option in the --> middle of your daily backups, one day you will forget to --> no-use a tape and erase your precious data... --> --> I like my solution because I run 2 different separated --> configs which have no relation between each other, one for --> my daily backups and one for my archives when I have to --> archive some data. --> --> --> On Wed, 22 Oct 2003 17:35:38 +0200 --> Toralf Lund <[EMAIL PROTECTED]> wrote: --> --> > Reviewing the amanda config again in conjunction with a --> tape format --> > update... --> > I forget (and list search doesn't return anything --> conclusive): How do --> > you people recommend handling archival runs? There are --> two obvious ways: --> > --> >1. Via a special config. --> >2. Using the normal config, but special labels and --> "amadmin ... no-reuse" --> > --> > What are the pros and cons of each of these? --> > --> > Note: I know that one argument against 2) is that you --> normally want --> > different behaviour with regard to incrementals, but that --> doesn't really --> > apply in my case as there are no incrementals in any case --> (in the main --> > config; I have a separate one for incrementals as they --> are written to a --> > different medium.) --> > --> > - Toralf --> > -->
Re: [UPDATE] How to control which tape is next?
Hi Paul, I commited your patch with a small change. In write_tapelist, it return 1 instead of calling error(), all caller handle the return code correctly. Jean-Louis On Wed, Oct 22, 2003 at 04:04:19PM +0200, Paul Bijnens wrote: > [EMAIL PROTECTED] wrote: > > >Check to see if some problem has truncated your tapelist file. If a > >problem (e.g., no space left on a device) prevents the tapelist from > >being created or some other problem truncated the file, then you > >could expect to see a problem like this. Check to see if there have > >been any drive faults or other system events at the time when Amanda > >started giving you strange results. > > I have created a patch, which seems not yet included in the current > sources, for similar errors: > > http://groups.yahoo.com/group/amanda-hackers/message/3769 > > (but it seems that this is not the problem, as Lucio seems to indicate > that there ARE enough entries in the tapelist file. Maybe a permission > problem? Or looking at a file with the same name but not the one > as configured in amanda.conf?) > > > Jean-Louis, > > This patch was posted, while you were on holiday, or burried under the > work... I believe it's nice to include anyway. > > -- > Paul Bijnens, XplanationTel +32 16 397.511 > Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 > http://www.xplanation.com/ email: [EMAIL PROTECTED] > *** > * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * > * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * > * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * > * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * > * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...* > * ... "Are you sure?" ... YES ... Phew ... I'm out * > *** > -- Jean-Louis Martineau email: [EMAIL PROTECTED] Département IRO, Université de Montréal C.P. 6128, Succ. CENTRE-VILLETel: (514) 343-6111 ext. 3529 Montréal, Canada, H3C 3J7Fax: (514) 343-5834
Re: Help, Strange Error !!
Roberto Samarone Araújo (RSA) wrote: Hi, I have an Amanda Backup that was working fine now, when I try to use: su -c "/usr/sbin/amlabel Daily1 DAILY1-01" backup, the system return me: st0: Error with sense data: Current st09:00: sense key Medium Error Additional sense indicates Write error If I try: mt erase /dev/st0, it return me: st0: Error with sense data: Current st09:00: sense key Medium Error Additional sense indicates Write error mt: /dev/tape: Input/Output error I change my SDT-9000 tape to a new one and the problem persist. I saw on the logs the messages: st0: Block limits 1 - 16777215 bytes st0: Error with sense data: Current st09:00 sense key Medium Error Additional sense indicates Write error Does anyone could help me please ? When a try to recover a backup it worked fine. Roberto Samarone Araujo I'd check my perms on /dev/st0 as well...make sure the restore didn't change any setting back that you may have edited. Otherwise you could have a hardware problem...but I'd lean more to perms. =G=
Re: How to handle archival runs (again)?
For archival purposes, personnaly I use a combination of your two solutions. I use a different config of Amanda with "dumpcycle 0", "strategy noinc", but the main goal of a different config for me is concerning the logs: it's easier to restore data if your archives are not in the middle of your incremental backups. Moreover if you play with the "no-reuse" option in the middle of your daily backups, one day you will forget to no-use a tape and erase your precious data... I like my solution because I run 2 different separated configs which have no relation between each other, one for my daily backups and one for my archives when I have to archive some data. On Wed, 22 Oct 2003 17:35:38 +0200 Toralf Lund <[EMAIL PROTECTED]> wrote: > Reviewing the amanda config again in conjunction with a tape format > update... > I forget (and list search doesn't return anything conclusive): How do > you people recommend handling archival runs? There are two obvious ways: > >1. Via a special config. >2. Using the normal config, but special labels and "amadmin ... no-reuse" > > What are the pros and cons of each of these? > > Note: I know that one argument against 2) is that you normally want > different behaviour with regard to incrementals, but that doesn't really > apply in my case as there are no incrementals in any case (in the main > config; I have a separate one for incrementals as they are written to a > different medium.) > > - Toralf >
Re: Help, Strange Error !!
On Wed, 22 Oct 2003 at 12:41pm, Roberto Samarone Araújo (RSA) wrote >st0: Error with sense data: Current st09:00: sense key Medium > Error >Additional sense indicates Write error Try cleaning the drive. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: Help, Strange Error !!
--On Wednesday, October 22, 2003 12:41:02 -0700 "Roberto Samarone Araújo (RSA)" <[EMAIL PROTECTED]> wrote: > Hi, > > I have an Amanda Backup that was working fine now, when I try to use: > su -c "/usr/sbin/amlabel Daily1 DAILY1-01" backup, the system return me: > >st0: Error with sense data: Current st09:00: sense key Medium > Error >Additional sense indicates Write error > > >If I try: mt erase /dev/st0, it return me: > > st0: Error with sense data: Current st09:00: sense key Medium > Error > Additional sense indicates Write error > mt: /dev/tape: Input/Output error > > I change my SDT-9000 tape to a new one and the problem persist. > > I saw on the logs the messages: > > st0: Block limits 1 - 16777215 bytes > st0: Error with sense data: Current st09:00 sense key Medium > Error > Additional sense indicates Write error > > Does anyone could help me please ? When a try to recover a backup it > worked fine. > > Roberto Samarone Araujo > Is the tape write-protected? Frank -- Frank Smith [EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Help, Strange Error !!
Hi, I have an Amanda Backup that was working fine now, when I try to use: su -c "/usr/sbin/amlabel Daily1 DAILY1-01" backup, the system return me: st0: Error with sense data: Current st09:00: sense key Medium Error Additional sense indicates Write error If I try: mt erase /dev/st0, it return me: st0: Error with sense data: Current st09:00: sense key Medium Error Additional sense indicates Write error mt: /dev/tape: Input/Output error I change my SDT-9000 tape to a new one and the problem persist. I saw on the logs the messages: st0: Block limits 1 - 16777215 bytes st0: Error with sense data: Current st09:00 sense key Medium Error Additional sense indicates Write error Does anyone could help me please ? When a try to recover a backup it worked fine. Roberto Samarone Araujo
Help, Strange Error !!!
Hi, I have an Amanda Backup that was working fine now, when I try to use: su -c "/usr/sbin/amlabel Daily1 DAILY1-01" backup, the system return me: st0: Error with sense data: Current st09:00: sense key Medium Error Additional sense indicates Write error If I try: mt erase /dev/st0, it return me: st0: Error with sense data: Current st09:00: sense key Medium Error Additional sense indicates Write error mt: /dev/tape: Input/Output error I change my SDT-9000 tape to a new one and the problem persist. Does anyone could help me please ? When a try to recover a backup it worked fine. Roberto Samarone Araujo
How to handle archival runs (again)?
Reviewing the amanda config again in conjunction with a tape format update... I forget (and list search doesn't return anything conclusive): How do you people recommend handling archival runs? There are two obvious ways: 1. Via a special config. 2. Using the normal config, but special labels and "amadmin ... no-reuse" What are the pros and cons of each of these? Note: I know that one argument against 2) is that you normally want different behaviour with regard to incrementals, but that doesn't really apply in my case as there are no incrementals in any case (in the main config; I have a separate one for incrementals as they are written to a different medium.) - Toralf
Re: [UPDATE] How to control which tape is next?
On Wednesday 22 October 2003 08:56, Matt Hyclak wrote: >On Wed, Oct 22, 2003 at 07:04:29AM -0400, Gene Heskett enlightened us: >> We did at one time have someone subscribed here that was doing the >> redhat rpm's, and he would speak up anytime we started to get down >> on the rpm vs the tarballs, but he has not made any posts here in >> many months now that I'm aware of. I would be nice if he spoke >> up, possibly answering your question specificly. > >I'm not him, obviously, but he is lurking. Jay is usually idle on > the #amanda irc channel, and I have had some discussion with him > about the state of the RPMs for redhat. Unfortunately he also has a > hojillion other packages to maintain, so he can't dedicate a lot of > time to amanda. Yes, Jay is the one I was trying to remember. Thanks, my aged grey matter fails again. Its 69 FWTW. >FWIW, I have made packages of 2.4.4-p1 that are pretty much the RH > packages with a couple tweaks to the .spec file. Namely, there are > 2 variables at the top of the .spec to define your tapeserver and > your config name. The problem with packaging binary files for > amanda is that you have to resort to using localhost where a > hostname is required so the thing will at least mostly work. > Because of this, I put the variable at the top of the spec file and > recommend people rebuild the source rpm after making the > appropriate changes to the .spec. > >If anyone is interested in this, you can get it from (sorry it > wraps): > http://www.math.ohiou.edu/mirror/casit/contrib/9/SRPMS/amanda-2.4.4 >p1-2mrh3.src.rpm > >To install it "correctly" goes something like this: > >$ rpm -i amanda-2.4.4p1-2mrh3.src.rpm >edit the .spec file (in /usr/src/redhat/SPECS if you build as root) Q: Does this automaticly set the ownerships and perms in the built rpm? Amanda should be built by a non-priviledged user, then installed by root. Otherwise the perms get fubared. I ask because I've never done it this way to test. >$ rpmbuild -ba amanda.spec ># rpm -Uvh amanda-2.4.4p1-2mrh3.i386.rpm ... > (in /usr/src/redhat/RPMS/i386 if you build as root) > >You don't have to build amanda as root from the rpm (and I recommend > that you don't just on principle). I've fed these changes up to Jay > and he's created bugzilla entries (or at least was going to. If he > hasn't, maybe this can be his poke in the ribs...) to make it a > little easier to build amanda for your location and still have the > package be managed instead of resorting to *cringe* tarballs. ;-) > >Matt Just out of curiosity, why the cring at the thought of tarballs? There are good and valid reasons to use the rpms and have a managed install. In amanda's case, where the correct perms and such are required for proper overall functionality, and which may vary according to the users whims, something the rpms don't seem to handle right, I've found the tarballs to be much the easier way to maintain amanda. And I've learned the hard way to never, ever, let the up2date utility anywhere near your amanda install. One early version, if not the first one released, must have been a bit buggy though. I did not check anything amanda related, but it did it anyway. Took me 2 days to clean up the mess that made. We also spend about 25% of our support efforts here on this list trying to convince gnubies that they cannot run it reliably using localhost. Most probably have acquired the localhost habit from an rpm install. The README etc in the tarballs carry warnings, but theres no good place in the rpms for such advisories. After a while some of us can get downright bored, even growly about it. My apologies in that case :) -- Cheers, Gene AMD [EMAIL PROTECTED] 320M [EMAIL PROTECTED] 512M 99.27% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attornies please note, additions to this message by Gene Heskett are: Copyright 2003 by Maurice Eugene Heskett, all rights reserved.
tapecycle: Are "no-reuse" tapes counted?
It looks like Amanda will count *all* tapes written after the tape in question, even the ones marked as "no-reuse", when comparing count with tapecycle to determine if a tape may be overwritten. Is this observation correct? Should "no-reuse" tapes be included like that? -- Toralf
Re: [UPDATE] How to control which tape is next?
[EMAIL PROTECTED] wrote: Check to see if some problem has truncated your tapelist file. If a problem (e.g., no space left on a device) prevents the tapelist from being created or some other problem truncated the file, then you could expect to see a problem like this. Check to see if there have been any drive faults or other system events at the time when Amanda started giving you strange results. I have created a patch, which seems not yet included in the current sources, for similar errors: http://groups.yahoo.com/group/amanda-hackers/message/3769 (but it seems that this is not the problem, as Lucio seems to indicate that there ARE enough entries in the tapelist file. Maybe a permission problem? Or looking at a file with the same name but not the one as configured in amanda.conf?) Jean-Louis, This patch was posted, while you were on holiday, or burried under the work... I believe it's nice to include anyway. -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...* * ... "Are you sure?" ... YES ... Phew ... I'm out * ***
RE: [UPDATE] How to control which tape is next?
Lucio: Check to see if some problem has truncated your tapelist file. If a problem (e.g., no space left on a device) prevents the tapelist from being created or some other problem truncated the file, then you could expect to see a problem like this. Check to see if there have been any drive faults or other system events at the time when Amanda started giving you strange results. Don Donald L. (Don) Ritchey E-mail: [EMAIL PROTECTED] -Original Message- From: Lucio [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 22, 2003 5:08 AM To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: [UPDATE] How to control which tape is next? > Lucio: > > Until all the tapes have been used at least once, Amanda had no idea of > which tape to use next. All the tapes have already been used at least twice, and during the first two cycles (more or less) Amanda had been telling me what tape number to put in the unit. Then a cloudy day it stopped doing so. This e-mail and any of its attachments may contain Exelon Corporation proprietary information, which is privileged, confidential, or subject to copyright belonging to the Exelon Corporation family of Companies. This e-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this e-mail is strictly prohibited and may be unlawful. If you have received this e-mail in error, please notify the sender immediately and permanently delete the original and any copy of this e-mail and any printout. Thank You.
Re: [UPDATE] How to control which tape is next?
On Wed, Oct 22, 2003 at 08:56:10AM -0400, Matt Hyclak enlightened us: > If anyone is interested in this, you can get it from (sorry it wraps): > http://www.math.ohiou.edu/mirror/casit/contrib/9/SRPMS/amanda-2.4.4p1-2mrh3.src.rpm > Oops, that should be http://www.math.ohiou.edu/mirror/casit/contrib/9/SRPMS/amanda-2.4.4p1-2mrh.src.rpm The package builds for sure on RH9. You might need to tweak the dependencies and .spec in regards to the auto tools to build on earlier versions. Matt -- Matt Hyclak Department of Mathematics Department of Social Work Ohio University (740) 593-1263
Re: [UPDATE] How to control which tape is next?
On Wed, Oct 22, 2003 at 07:04:29AM -0400, Gene Heskett enlightened us: > We did at one time have someone subscribed here that was doing the > redhat rpm's, and he would speak up anytime we started to get down on > the rpm vs the tarballs, but he has not made any posts here in many > months now that I'm aware of. I would be nice if he spoke up, > possibly answering your question specificly. > I'm not him, obviously, but he is lurking. Jay is usually idle on the #amanda irc channel, and I have had some discussion with him about the state of the RPMs for redhat. Unfortunately he also has a hojillion other packages to maintain, so he can't dedicate a lot of time to amanda. FWIW, I have made packages of 2.4.4-p1 that are pretty much the RH packages with a couple tweaks to the .spec file. Namely, there are 2 variables at the top of the .spec to define your tapeserver and your config name. The problem with packaging binary files for amanda is that you have to resort to using localhost where a hostname is required so the thing will at least mostly work. Because of this, I put the variable at the top of the spec file and recommend people rebuild the source rpm after making the appropriate changes to the .spec. If anyone is interested in this, you can get it from (sorry it wraps): http://www.math.ohiou.edu/mirror/casit/contrib/9/SRPMS/amanda-2.4.4p1-2mrh3.src.rpm To install it "correctly" goes something like this: $ rpm -i amanda-2.4.4p1-2mrh3.src.rpm edit the .spec file (in /usr/src/redhat/SPECS if you build as root) $ rpmbuild -ba amanda.spec # rpm -Uvh amanda-2.4.4p1-2mrh3.i386.rpm ... (in /usr/src/redhat/RPMS/i386 if you build as root) You don't have to build amanda as root from the rpm (and I recommend that you don't just on principle). I've fed these changes up to Jay and he's created bugzilla entries (or at least was going to. If he hasn't, maybe this can be his poke in the ribs...) to make it a little easier to build amanda for your location and still have the package be managed instead of resorting to *cringe* tarballs. ;-) Matt -- Matt Hyclak Department of Mathematics Department of Social Work Ohio University (740) 593-1263
reverse the aging process now
Title: rand LATEST BREAKTHROUGH - NEWS FLASH The BAD News: As you Age your body produces less hormones causing you to look older, feel older and be weaker! The GOOD News: Experts in the New England Journal of Medicine, report that Human Growth Hormone therapy makes you look and feel 20 YEARS YOUNGER! Click Here For More Info
Re: [UPDATE] How to control which tape is next?
On Wednesday 22 October 2003 06:07, Lucio wrote: >> Lucio: >> >> Until all the tapes have been used at least once, Amanda had no >> idea of which tape to use next. > >All the tapes have already been used at least twice, and during the > first two cycles (more or less) Amanda had been telling me what > tape number to put in the unit. Then a cloudy day it stopped doing > so. Ok, by now you should have a 'tapelist' file located in whatever directory the rpm install uses for its configuration storage. Here, that directory is /usr/local/etc/amanda/ConfigName, and that file at this instant looks like this: -- 20031022 DailySet1-04 reuse 20031021 DailySet1-03 reuse 20031020 DailySet1-02 reuse 20031019 DailySet1-01 reuse 20030817 DailySet1-28 reuse 20030816 DailySet1-27 reuse 20030815 DailySet1-26 reuse 20030814 DailySet1-25 reuse 20030813 DailySet1-24 reuse 20030812 DailySet1-23 reuse 20030811 DailySet1-22 reuse 20030810 DailySet1-21 reuse 20030809 DailySet1-20 reuse 20030808 DailySet1-19 reuse 20030807 DailySet1-18 reuse 20030806 DailySet1-17 reuse 20030805 DailySet1-16 reuse 20030804 DailySet1-15 reuse 20030803 DailySet1-14 reuse 20030802 DailySet1-13 reuse 20030801 DailySet1-12 reuse 20030731 DailySet1-11 reuse 20030730 DailySet1-10 reuse 20030729 DailySet1-09 reuse 20030728 DailySet1-08 reuse 20030727 DailySet1-07 reuse 20030726 DailySet1-06 reuse 20030725 DailySet1-05 reuse -- and amanda will expect to use DailySet1-05 tomorrow night. The tape it just finished using is placed at the top of the list, having taken it off the bottom of the list when it was reused. If you have edited that file as root, the perms may have been changed such that the amanda user hasn't any read rights, remember that the amanda user should have perms to read and write that file. Does this help? -- Cheers, Gene AMD [EMAIL PROTECTED] 320M [EMAIL PROTECTED] 512M 99.27% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attornies please note, additions to this message by Gene Heskett are: Copyright 2003 by Maurice Eugene Heskett, all rights reserved.
Re: [UPDATE] How to control which tape is next?
On Wednesday 22 October 2003 05:23, Lucio wrote: >> >Are you telling me that this is a known problem of 2.4.3? >> > >> >It's a production system, I'm afraid it's quite a risk to update >> > a rpm by compiling from source (especially for an amanda newbie >> > like me). I'm going to do this only if I have no other chance. >> >> I don't blame you for being a bit reticent, it can bite you. And, >> its for that reason that I don't personally recommend using the >> rpm's, ever. > >[...] > >> ISTR I had some sort of a problem, the details of which I can't >> recall now, and that it was fixed the next day, back someplace in >> the 2.4.3 tree. ISTR there was a typo in the source, and it made >> it into the rpm somehow. > >Am I the only one here who uses the Amanda version 2.4.3 bundled > with RH9? If not, and if this is a known problem of that version, > there must be someone else here experiencing the same > difficulties... and maybe he/she has already found the solution. I > believed RedHat was widespread enough. Download the tarball and read the ChangeLog, paying attention to those dates in the weeks prior to the redhat 9 release for the final word. I could be mistaken, and have been before and probably will be again. :) Those of us who use it everyday, and offer our support (such as it is) to other users on this list are often surprised at the amount of jurassic dust on the versions that somehow manage to ship with the major distros. Even more amazing is the difficulty in getting the distros to issue an updated package. This is for the most part, an entirely user supported software package, with only occasional input from the currently active authors, who understandably have other, paycheck related duties to take care of and have no real desire to spend what little spare time they may be able to squeeze out of a days work in hand-holding the amanda users. We will, because we think amanda is a "choice lady", try and figure out any problems presented to the group, and each of us has developed his or her own methods, or specialty areas of expertise. My own method of choice is to stay current by building each new snapshot so that if there is a problem that effects how it runs in my personal configuration, I may already be aware of it by the time someone posts a problem. That of course depends to an extent on that particular configuration. As a home user, my 70 real gigs system is of course smaller than most business systems would be, and the loss of one backup does not to me, represent a potential loss in cash flow. The point I was trying to make is that 2.4.3 is getting close to a year old, and some features have been added, and a few bugs fixed in the elapsed time since 2.4.3 was current. We on this mailing list generally see that as a plus, and I'll repeat once again that staying current has not, by itself, cost me any lost data in maybe 3.5 years time since I started useing amanda. Thats not to say I haven't lost a tape or 6 (DDS2's are cheap and you really DO get what you pay for) or made my own stupid mistakes. But the mistakes or errors were mine or my hardware's, not amanda's. FWIW, amanda has maintained backwards compatibility between all versions since well before I started using it, so it is not required that you update all clients at the same time as the server if those logistics are concerning you. Achieving that long term compatibility is far more related to useing a consistent configuration script such as the one I posted to show the framework, than it is to the version of amanda running on machine so-and-so. Thats why I post it from time to time, often enough I suppose that some on this list could quote it verbatum from memory! You can probably look at where the configs, logs and indices are being kept on your system and adjust that script to make you a build from the tarball that will go right on top of the older rpm install. We did at one time have someone subscribed here that was doing the redhat rpm's, and he would speak up anytime we started to get down on the rpm vs the tarballs, but he has not made any posts here in many months now that I'm aware of. I would be nice if he spoke up, possibly answering your question specificly. -- Cheers, Gene AMD [EMAIL PROTECTED] 320M [EMAIL PROTECTED] 512M 99.27% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attornies please note, additions to this message by Gene Heskett are: Copyright 2003 by Maurice Eugene Heskett, all rights reserved.
Re: tape type for HP DDS3 C5708A
Thanks Eric, Jon. As adviced, I'm introducing DLE's one by one. I also temporarly removed windows backups from this amanda process (I'll handle it manually for now). I'll closely monitor amanda when it backups up my linux servers and maybe at some point later.. reintroduce windows boxes. ...Rohit - Original Message - From: "Eric Siegerman" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, October 21, 2003 1:48 AM Subject: Re: tape type for HP DDS3 C5708A > On Sat, Oct 18, 2003 at 03:29:13PM -0400, Jon LaBadie wrote: > > On Sat, Oct 18, 2003 at 11:24:05PM +0530, Rohit Peyyeti wrote: > > > FAILURE AND STRANGE DUMP SUMMARY: > > > localhost /h lev 0 FAILED [dumps too big, but cannot incremental dump new disk] > > > [plus three more of the same] > > > > This suggests to me that the DLE's are each larger than your tape. > > I don't think so. In that case, the message would have been > "dump larger than tape, but cannot yada yada" (Phase 1 of > delay_dumps()). > > The "dumps too big" variant comes from Phase 2, when a full dump > is due, but planner wants to postpone it and do an incremental > instead, to fit all the DLEs onto the tape. In the case of a new > disk, as you pointed out, the do-an-incremental-instead option > isn't possible, so planner's only choice is to skip the DLE > entirely. > > Rohit: > > The answer, as Jon said, is to add DLEs a few at a time -- or, in > your case, it looks like *one* at a time :-(, so as not to ask > Amanda to put more on a tape than will fit. > > Or else just don't worry about it; leave all of the DLEs in there > and let them fight it out for tape space :-) Sooner or later, > they'll all make it onto tape, as //windows/UsersG3 did this > time. I doubt that it'll happen any faster if you follow the > usual advice and only add them slowly. The only advantages of > doing it that way are: > - you won't get Amanda shouting at you that YOUR BACKUPS > FAILED!! > > - if some DLEs are more important to back up than others, you > get to put those into the backup system first, rather than > letting Amanda choose randomly which one(s) to add in any > given run > > > > > --> some NT_STATUS_OBJECT_NAME_NOT_FOUND errors <-- > > Someone recently posted a solution to that, I think. Couldn't > hurt to check the archives for it. > > -- > > | | /\ > |-_|/ > Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED] > | | / > When I came back around from the dark side, there in front of me would > be the landing area where the crew was, and the Earth, all in the view > of my window. I couldn't help but think that there in front of me was > all of humanity, except me. > - Michael Collins, Apollo 11 Command Module Pilot
Re: [UPDATE] How to control which tape is next?
Lucio wrote: Am I the only one here who uses the Amanda version 2.4.3 bundled with RH9? If not, and if this is a known problem of that version, there must be someone else here experiencing the same difficulties... and maybe he/she has already found the solution. I believed RedHat was widespread enough. I don't believe it is (was) a problem in 2.4.3 or even before. Just make sure that "grep -c -v no-reuse tapelist" is the greater than or equal to your tapecycle. -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...* * ... "Are you sure?" ... YES ... Phew ... I'm out * ***
amrecover: Why does it use disklist and log files
As far as I can't tell, amrecover won't work unless 1. Log file from the backup you are trying to recover is still present 2. DLE is still in the disklist Why? Shouldn't amrecover work from the index alone? - Toralf
Re: [UPDATE] How to control which tape is next?
> Lucio: > > Until all the tapes have been used at least once, Amanda had no idea of > which tape to use next. All the tapes have already been used at least twice, and during the first two cycles (more or less) Amanda had been telling me what tape number to put in the unit. Then a cloudy day it stopped doing so.
Re: [UPDATE] How to control which tape is next?
> >Are you telling me that this is a known problem of 2.4.3? > > > >It's a production system, I'm afraid it's quite a risk to update a > > rpm by compiling from source (especially for an amanda newbie like > > me). I'm going to do this only if I have no other chance. > > I don't blame you for being a bit reticent, it can bite you. And, its > for that reason that I don't personally recommend using the rpm's, > ever. [...] > ISTR I had some sort of a problem, the details of which I can't recall > now, and that it was fixed the next day, back someplace in the 2.4.3 > tree. ISTR there was a typo in the source, and it made it into the > rpm somehow. Am I the only one here who uses the Amanda version 2.4.3 bundled with RH9? If not, and if this is a known problem of that version, there must be someone else here experiencing the same difficulties... and maybe he/she has already found the solution. I believed RedHat was widespread enough.
f i r s t g l o b a l dedicated WEB Auction Stores Platform for Electronic
lead1auction Ladies and Gentlemen Be informed that the f i r s t g l o b a l dedicated WEB Auction and Stores Platform for Electronics, Semiconductor and PCB products is ready for public access and product upload from now on. We invite you to participate on this unique business service . You can subscribe from now on and check on the structure of these platforms as well prepare upload of goods. Your Registration is total free of cost.http://www.lead1auction.com Yours Lead1Auction Team Email: [EMAIL PROTECTED] WEB-Portal for ElectronicsAUCTIONS - STORES - FACTORY OUTLETS <<7neu.GIF>>
