how to recover to remote amanda client with amrecover
Hi, I want to recover files into amanda remote client from amanda tape server. I executed "amrecover mailde" command on amanda tape server. mailde is amanda remote client hostname. # amanda mailde amrecoversethost mailde 200 Dump host set to mailde. amrecoversetdisk / 200 Disk set to /. amrecovercd /root /root amrecoveradd .emacs.el Added /root/.emacs.el amrecover extract Extracting files using tape drive /dev/nst0 on host bakubak. The following tapes are needed: DailySet10 Restoring files into directory /root Continue? [Y/n]: Y Load tape DailySet10 now Continue? [Y/n]: Y ./root/.emacs.el amrecover I could not recover .emacs.el file into remote host (mailde). .emacs.el file was recovered into tape server's /root directory. Could you tell me how to recover files into amanda remote host ? Best regards, Masafumi Hikawa
Re: most efficient use of holding disk
Hi! Chris Marble wrote: Martin Oehler wrote: I use amanda on a solaris 7 box with a DTL drive (20 GB) attached. My dumpcyle is 4 weeks with 20 runs per cycle. Because the size of one incremental backup is only between 2-4 GB I don't want to change the tape each day. You could crank your dumpcycle down to 3 (or whatever number would get Amanda to use most of your tape capacity). Hmmm, I didn't want to use a constant value because it can happen that there is a 8 GB or 10 GB incremental backup. Is there a way I can calculate the needed size on tape (approx.) before the backup process starts? CU, thanks Martin
Solved -- samba backups offline
About 2 weeks ago I asked the following: I'm backing up a single W2K machine to my tape server. There are 4 partitions on the windows box. Some nights al 4 partitions are processed normally. Most nights 1 or more of the partitions fail with the query host offline? which obviously it is not as the other partitions are backing up. I got a reply from Chris Marble that helped: I'd try cranking down maxdumps for just that host. See if that helps. Rather than change the maxdumps parameter (which probably would have solved the problem) I chose to use the spindle feature and indicate each of the 4 partitions are on the same spindle. Amanda limits the number of dumps on each spindle to 1 at a time. Since the change 10 days ago, not a single offline partition. Thanks Chris! -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
disk offline - addendum
sorry, I forgot OS is: SunOS fav 5.4 Generic_101945-43 sun4m sparc regards, rainer.
cautionary note about KT133 southbridge systems
HI all- Awhile ago, I built a system which was destined to be my webserver which was a AMD Duron 800 with the fabled Kt133a Southbridge chipset. AFter numerous backups with amanda, I kept on getting i/o errors and strange dump reports using an IBM 45 gig ATA 100 drive. On the system, the drive was filled with dma retries and resets. I tried a whole bunch of stuff to solve this including stepping the system down to no-DMA but still had the problems. This was on a 2.4.13 kernel with the VIA ide driver enabled; which usually fixes this sort of thing. At the end of things, the drive started clanking on copying my build to a replacement disk drive and I realized that the drive was probably gonna fail on me at any moment. It also made me doubt that validity of backups since each one seemed to have the strange dump reports in it but they all completed. My main note here is to move carefully when using this particular chipset and controller and different IDE drives. For me, any amount of intensive disk io caused the system to burp out literally hundreds of dma reset/retry errors. Replacing the drive with a Maxtor DiamondMax 80g drive solved the problems completely. If you see dma resets/retries when doing amanda dumps, you may want to doublecheck what you are using as far as dma settings on the drive. -- Michael Perry | Do or do not; there is no try Master Yoda [EMAIL PROTECTED] | http://www.lnxpowered.org
Re: cautionary note about KT133 southbridge systems
Don't know if this will help or not but this problem was discussed at some length on various VIA HArdware sites. IIRC, it was tracked down to an incompatibility between the Southbridge and, of all things, the Soundblaster Live! sound card. Do you have such an animal in this machine? Either way, recent BIOS updates have come out to correct just this issue. You might want to try snagging one from your manufacturer. A BIOS upgrade certainly helped MY system out. Michael Perry wrote: HI all- Awhile ago, I built a system which was destined to be my webserver which was a AMD Duron 800 with the fabled Kt133a Southbridge chipset. AFter numerous backups with amanda, I kept on getting i/o errors and strange dump reports using an IBM 45 gig ATA 100 drive. On the system, the drive was filled with dma retries and resets. I tried a whole bunch of stuff to solve this including stepping the system down to no-DMA but still had the problems. This was on a 2.4.13 kernel with the VIA ide driver enabled; which usually fixes this sort of thing. At the end of things, the drive started clanking on copying my build to a replacement disk drive and I realized that the drive was probably gonna fail on me at any moment. It also made me doubt that validity of backups since each one seemed to have the strange dump reports in it but they all completed. My main note here is to move carefully when using this particular chipset and controller and different IDE drives. For me, any amount of intensive disk io caused the system to burp out literally hundreds of dma reset/retry errors. Replacing the drive with a Maxtor DiamondMax 80g drive solved the problems completely. If you see dma resets/retries when doing amanda dumps, you may want to doublecheck what you are using as far as dma settings on the drive. -- -- Aaron Smith vox: 616.226.9550 Network Directorfax: 616.349.9076 Nexcerpt, Inc. [EMAIL PROTECTED]
no tpchanger specified
When I run the extract command in amrecover, I get: extract_file_setup(): will request tape DailySet100 file 0. EOF, check amidxtaped.debug file on myhostname. amrecover: short block 0 bytes UNKNOWN file amrecover: Can't read file header extract_list - child returned non-zero status: 1 Upon closer inspection of the debug file, I found: amrestore: seeking label DailySet100 file 0 config DailySet1. amtape: no tpchanger specified in /usr/local/amanda-2.4.2p2/etc/amanda/DailySet1/amanda.conf amrestore: couldn't locate tape `DailySet100' My setup is that I have no tape changer, which has been accounted for in my amanda.conf file: tapedev /dev/nst0 # the no-rewind tape device to be used #runtapes 1 # number of tapes to be used in a single run of amdump #tpchanger chg-manual # the tape-changer glue script #rawtapedev /dev/null # the raw device to be used (ftape only) #changerfile /var/lib/amanda/DailySet1/changer #changerfile /var/lib/amanda/DailySet1/changer-status #changerfile /etc/amanda/DailySet1/changer.conf #changerdev /dev/null So my questions are: 1. Is amrecover suppose to be running amtape if I have no tape changer specified? When I run amtape DailySet1 show, I get: amtape: no tpchanger specified in /usr/local/amanda-2.4.2p2/etc/amanda/DailySet1/amanda.conf 2. How can I prevent amanda from stopping on this tpchanger problem, isn't my configuration setup properly to not use a tapechanger? Marc - Sitepak
disk relabeling
I have mislabled a disk but amanda has done dump to it. If i remove and relabel it, will i loose the backup? Hussain
Re: (tapeless) amanda-242-tape make failure
On Fri, Dec 28, 2001 at 08:41:29PM -0800, Amanda Listee wrote: Hi, I'm trying to install the tapeless amanda-242-tapeio sourceforge version on a FreeBSD-4.4 white box: Use amanda-243-branch instead of amanda-242-tapeio. Maybe some of your software are not up to date? You can download a current snapshot, follow the link from http://www.amanda.org/download.html Jean-Louis -- Jean-Louis Martineau email: [EMAIL PROTECTED] Departement IRO, Universite de Montreal C.P. 6128, Succ. CENTRE-VILLETel: (514) 343-6111 ext. 3529 Montreal, Canada, H3C 3J7Fax: (514) 343-5834
Re: disk offline ?
Rainer Fuegenstein [EMAIL PROTECTED] wrote: After adding a new old server named fav to amanda, I keep getting the following message: FAILURE AND STRANGE DUMP SUMMARY: fav/home2 lev 0 FAILED [disk /home2 offline on fav?] It doesn't matter if the disk is specified by device file or mount directory: favc1t4d0s6tar-srv-low# /home2 fav/home2 tar-srv-low# /home2 Looks familiar... Try to supply the absolute path for the obstinate drive. If that helps, we're two... hauke -- Hauke Fath /~\The ASCII tangro software components GmbH \ / Ribbon Campaign D-69115 Heidelberg X Against Ruf +49-6221-13336-0, Fax -21 / \ HTML Email!
.amanda.exclude.gtar
Hi, I'm using the .amanda.exclude.gtar script to exclude a few things from our backup. I am having a problem with netscape cache. In the exclude script I have the following line: */.netscape/cache/* I still get problems in the backup report: ? gtar: ./home/monachus/.netscape/cache/13/cache3C2C0E93DA8B3B8.css: Warning: Cannot stat: No such file or directory ? gtar: ./home/monachus/.netscape/cache/14/cache3C2C0DF4D94B3B8.png: Warning: Cannot stat: No such file or directory ? gtar: ./home/monachus/.netscape/cache/14/cache3C2C0DF4D95B3B8.png: Warning: Cannot stat: No such file or directory ? gtar: ./home/monachus/.netscape/cache/14/cache3C2C0E94DB0B3B8.gif: Warning: Cannot stat: No such file or directory ? gtar: ./home/monachus/.netscape/cache/14/cache3C2C0E94DB4B3B8.gif: Warning: Cannot stat: No such file or directory ? gtar: ./home/monachus/.netscape/cache/15/cache3C2C0DF5D96B3B8.png: Warning: Cannot stat: No such file or directory ? gtar: ./home/monachus/.netscape/cache/15/cache3C2C0DF5D97B3B8.png: Warning: Cannot stat: No such file or directory ? gtar: ./home/monachus/.netscape/cache/15/cache3C2C0DF5D98B3B8.png: Warning: Cannot stat: No such file or directory ? gtar: ./home/monachus/.netscape/cache/15/cache3C2C0DF5D99B3B8.png: Warning: Cannot stat: No such file or directory ? gtar: ./home/monachus/.netscape/cache/16/cache3C2C0DF6D9AB3B8.png: Warning: Cannot stat: No such file or directory Any suggestions? Thanks!
tape io errors on Ecrix VXA-1
I am curious if people see failed backups regularly, occasionally, or hardly at all due to IO errors on the tapeserver bus. My own failed backups seem to be linked to questionable tapes which may have been ready to fail anyways. Unfortunately, the ecrix tapes are very expensive to me and I hate having to replace them since each one is almost $100. The tape errors are about rewinding or issues with the tape itself. What are other's experiences with the VXA-1 or is tape just a dirty media and tapes fail very often, etc? I wish I knew the history of some of the tapes, but I don't. I also upgraded the firmware on the VXA-1 since I have no idea when that was last done. I have run a tape cleaner through the tape drive recently (perhaps a week ago or so). Secondarily, I am curious if people have recommendations for scsi-based tape drive solutions which would work well on a home LAN configured as follows: 2 debian unstable systems doing desktop and one webserver on testing 1 Windows XP Pro box (workstation/desktop) 1 BSD box doing critical stuff (firewall) 1 Windows 98 SE box (kidster computer) 1 debian laptop The linux systems are all running a recent kernel. Each system probably has a few gigs of used up space except for the BSD box. Now the VXA-1 backs up all the *nix stuff easily on one tape and I like that operation! Thanks and a happy New Year to all of you! -- Michael Perry | Do or do not; there is no try Master Yoda [EMAIL PROTECTED] | http://www.lnxpowered.org
add machine to home net, put in iptables_nat rules, amanda dies.
Hi folks, got one here at home. I added a second machne to the home network, and added some iptable NAT/MASQUERADE rules, and now amcheck is returning this error: WARNING: gene.coyote.den: selfcheck request timed out. Host down? Here is the /home/amanda/.amandahosts file: gene.coyote.den amanda coyote.coyote.den amanda And here is the hosts file: # Do not remove the following line, or various programs # that require network functionality will fail. 127.0.0.1 localhost.localdomain localhost 192.168.1.1 gene.coyote.den gene 192.168.1.2 amiga.coyote.denamiga 192.168.1.3 coyote.coyote.den coyote when I run an amcheck, this gets added to the /var/log/messages file: Never mind, I think I just found it, the message file advises me that the latest xinetd I put in needs libstdc-so-6(GCC3.0) version. Sine there aren't an rpms that will actually install here without a kajillion dependency errors, I'm still running GCC-2.96-101. Gawd, thats about the 20th time I've got bit, trying to install crap that doesn't say a thing about needing this newer library in its dependency lists, and then won't run because it can't find it. Its pure, fresh, still steaming and green, bull excrement is what is was, to parody Andy Griffith's famous song. -- Cheers, gene
Suspend amanda
hi, Imagine that during the christmass vacation nobody stay in the company, so no more people are going to modify any files... Is there a way to tell amanda to suspend is work for 1 week..without stressing it when we restart.. I have no idea on how to proceed, anyone, anyone I was thinking to mofify the dumpcyle by make it bigger of 1 week...and then after ?? thanks in advance
Re: add machine to home net, put in iptables_nat rules, amanda dies.
Gene, Don't know if this is your first networked machine, but in case your just getting started with xinetd, bear in mind that by default, the old inetd configuration used to have all services enabled. Xinetd, on the other hand, comes standard with all services 'disabled'. So, check the contents of your /etc/xinetd.d/ directory, and change all of the amanda related files so that they have 'disable' set to 'no'. Good luck. Jeff. Gene Heskett wrote: Hi folks, got one here at home. I added a second machne to the home network, and added some iptable NAT/MASQUERADE rules, and now amcheck is returning this error: WARNING: gene.coyote.den: selfcheck request timed out. Host down? Here is the /home/amanda/.amandahosts file: gene.coyote.denamanda coyote.coyote.den amanda And here is the hosts file: # Do not remove the following line, or various programs # that require network functionality will fail. 127.0.0.1 localhost.localdomain localhost 192.168.1.1gene.coyote.den gene 192.168.1.2amiga.coyote.denamiga 192.168.1.3coyote.coyote.den coyote when I run an amcheck, this gets added to the /var/log/messages file: Never mind, I think I just found it, the message file advises me that the latest xinetd I put in needs libstdc-so-6(GCC3.0) version. Sine there aren't an rpms that will actually install here without a kajillion dependency errors, I'm still running GCC-2.96-101. Gawd, thats about the 20th time I've got bit, trying to install crap that doesn't say a thing about needing this newer library in its dependency lists, and then won't run because it can't find it. Its pure, fresh, still steaming and green, bull excrement is what is was, to parody Andy Griffith's famous song.
Merry Christmas and a happy New Year
Title: We wish you all a Merry Christmas and a happy New Year Aykut Çakýl (Incoming Dept. Manager) ACTIVE TRAVEL AGENCY Lufthansa City Center Istanbul - Turkey Phone: + 90 216 349 55 90 Fax: + 90 216 349 55 94 Email: [EMAIL PROTECTED] Web: www.activeturkey.com
amandad keeps dying for some unknown reason......
I have Solaris 8 box using Amanda 2.4.2 (client). And when I run amcheck from the tape server I get the following errors on the console: Dec 31 09:54:18 oligo inetd[170]: [ID 858011 daemon.warning] /var/adm/amanda/libexec/amandad: Killed Dec 31 09:55:28 oligo inetd[170]: [ID 667328 daemon.error] amanda/udp server failing (looping), service terminated I thought it was an issue pertaining to the OS version only. But I have been able to use amanda on other 5.8 boxes. The only differance is that I used different GCC to compile the software. The failing box uses 3.0.2 and the working boxes utilize 2.8.1 of gcc (upgrading the compiler). Has anybody seen issues of this variety by chance. I'm not sure if this is even related to the gcc rev. Thanks for any advice. Don Potter
Re: amandad keeps dying for some unknown reason......
This could be an inetd issue, if you have a whole lot of disklist entries pointing to the server in question. Rate limiting is a common inetd feature. The idea is that more than some number of requests per unit time means the same request is coming in repeatedly, and the server isn't satisfying it. As anybody who has ever tried to run even a moderatly busy SMTP server over inetd has discovered, this feature, while preventing machine meltdown due to overspawning a failing server, may also bring about server failures under slightly different circumstances. Of course this was not unexpected, and inetd makes allowances for this. See man inetd. At least on Linux. I'd expect similar allowance on Solaris, too. From man 5 inetd.conf, an entry like amanda dgram udp wait.100 amanda /usr/libexec/amandad amandad specifies that 100 server processes may be spawned in one minute. On Wed, Jan 02, 2002 at 12:18:01PM -0500, Don Potter wrote: I have Solaris 8 box using Amanda 2.4.2 (client). And when I run amcheck from the tape server I get the following errors on the console: Dec 31 09:54:18 oligo inetd[170]: [ID 858011 daemon.warning] /var/adm/amanda/libexec/amandad: Killed Dec 31 09:55:28 oligo inetd[170]: [ID 667328 daemon.error] amanda/udp server failing (looping), service terminated I thought it was an issue pertaining to the OS version only. But I have been able to use amanda on other 5.8 boxes. The only differance is that I used different GCC to compile the software. The failing box uses 3.0.2 and the working boxes utilize 2.8.1 of gcc (upgrading the compiler). Has anybody seen issues of this variety by chance. I'm not sure if this is even related to the gcc rev. Thanks for any advice. Don Potter -- - Dan Wilder [EMAIL PROTECTED] Technical Manager Editor SSC, Inc. P.O. Box 55549 Phone: 206-782-8808 Seattle, WA 98155-0549URL http://embedded.linuxjournal.com/ -
Re: (tapeless) amanda-242-tape make failure
On January 2 2002, I wrote: [much deleted] You'll notice that USE_GMAKE= yes appears in the FreeBSD ports of Amanda (/usr/ports/misc/amanda24-server/Makefile is the master makefile for the ports), for this very reason. Actually, it looks like the maintainer of the FreeBSD Amanda ports has upgraded them to use the amanda 2.4.3b1 release and renamed them to just amanda-server and amanda-client. You should find that the whole tapeio feature set is part of the port, and that the port is very easy to build. If you have updated your ports distribution since December 3 or thereabouts, you should find the Amanda ports in: /usr/ports/misc/amanda-server and /usr/ports/misc/amanda-client The build process will build and install GNU tar and GNU make before building Amanda. There are a few of the configure options that may be manipulated, type make pre-fetch to see them before making/installing. Again, I hope this helps, -Ben -- Benjamin Lewis [EMAIL PROTECTED] Database Analyst/Programmer Instructional Computing Services - Accounts Group Purdue University
about amanda holding disk...
Hi, Since my incremental backup is not so big(about 20G)per day. I want amanda to put daily incremental backup to the holding disk first. and then after 3 or 4 days, I flush it to one tape(100G capacity).That means the holding disk will have 3 or 4 days of incremental backup. how can I do this in configuration file or which command should I run? Another rookie question is: Currently I use Sony AIT2 50/100 tape device, each time I run amdump manually to do the backup. Now I want amanda to do it automatedly. But, Amanda automatically schedules full/incremental dumps to maintain balanced daily runtimes and tape usage, If I do a full backup each month, then the backup machine is totally down in the middle of the month, does that means the only backup I have is the backup of last month?(since this month's full backup is not finished) Thank you very much,bow...
strange amanda header
Someone has never had a similar problem? amrestore: 0: skipping start of tape: date 20011213 label Daily1-CdC-001 amrestore: strange amanda header: AMANDA: FILE 20011211 leonardo / let 1 comp .gz program /bin/gtar I do not see nothing strange? Thanks, Alessandro
Running programs during client execution?
I'm a new subscriber, so apologies in advance if this is an FAQ, I was unable to find an answer on the site. I'll take all relevant redirection to solutions. I'm running a large amanda installation without any problems whatsoever, but with a few desires. The largest of these is client-side backup customizations. For example, I would like to write a script to perform CVS write locks before backing up our CVS tree (which is on a partition by itself). I know how to do the locking, but the question is: How do I get my own program to run during this process? I'd love to hear there's a way to do this... I don't want to just wrapper the whole amandad, because I'd like to make sure that the scripts only get run during the backup process, NOT during amcheck hits or spurious connections from curious users). Suggestions or comments? :) TIA, -mh. -- Mark Hazen DataBuilt, Inc. (843) 836-2101 Ext. 251 They may forget what you said, but they will never forget how you made them feel. --Carl W. Buechner
(tapeless) amanda-242-tape make failure
Hi, I'm trying to install the tapeless amanda-242-tapeio sourceforge version on a FreeBSD-4.4 white box: I ran autogen twice, getting which I assume is a harmless error: configure.in:1617: warning: AC_TRY_RUN called without default to allow cross compiling I ran configure thusly, which seems to go well: hotpink# ./configure --prefix=/home/amanda --with-user=amanda \ --with-group=backup The make doesn't get very far: hotpink# make Making all in config Making all in common-src Makefile, line 440: Need an operator make: fatal errors encountered -- cannot continue *** Error code 1 Line 440 of common-src/Make looks like: 438 DEPS_MAGIC := $(shell mkdir .deps /dev/null 21 || :) 439 440 -include $(DEP_FILES) 441 442 mostlyclean-depend: Don't know what to do at this point. Thanks, Alex Neilson Zarcomm Consulting Linux FreeBSD Solaris [EMAIL PROTECTED]
Getting the current fs position
I'm using amanda 2.4.2p2 with a patch to append backups to the same tape. Everything works well and I have managed to retrieve files using amrecover. Problem is, after running that command, I'm guessing I need to reset the position of the tape to 1 beyond the last filesystem written to tape. Is there a command to do this? I looked around and it would seem amadmin with the balance option should return that value, but it does not return the total number of filesystems written to disk to date. So how can I find this information? Marc - Sitepak
Re: disk relabeling
On Thursday 27 December 2001 02:44 pm, Hussain Ali wrote: I have mislabled a disk but amanda has done dump to it. If i remove and relabel it, will i loose the backup? Hussain Yes. -- Chris Dahn, SERG Code Ninja 3141 Chestnut St. Attn: MCS Department Philadephia, PA 19104 Office: 215.895.0203 Fax: 215.895.1582 -Software Engineering Research Group- Feel the SERG! http://serg.mcs.drexel.edu/ CAT 186, The Microwave http://pgp.mit.edu:11371/pks/lookup?search=Christopher+Dahnop=index
Re: about amanda holding disk...
At 14:26 03-01-2002 -0500, Dengfeng Liu wrote: Since my incremental backup is not so big(about 20G)per day. I want amanda to put daily incremental backup to the holding disk first. and then after 3 or 4 days, I flush it to one tape(100G capacity).That means the holding disk will have 3 or 4 days of incremental backup. how can I do this in configuration file or which command should I run? Another rookie question is: Currently I use Sony AIT2 50/100 tape device, each time I run amdump manually to do the backup. Now I want amanda to do it automatedly. Starting with the second question. Run amdump as a cronjob or a similar thing that will let you run commands at a specific time. With this working you dont have to do anything to get your dumps to the holding disk. If you dont put a tape in the drive amdump will complain a bit and dump to the holding disk. You can then flush to tape at when appropriate. But, Amanda automatically schedules full/incremental dumps to maintain balanced daily runtimes and tape usage, If I do a full backup each month, then the backup machine is totally down in the middle of the month, does that means the only backup I have is the backup of last month?(since this month's full backup is not finished) As far as I know, No, you have what has been backed the first half of the month. Not knowing the detail I would guess that amanda gives priority to new and changed files so the damage is minimised - but others on this list will know better... Kasper
How to use xfsdump with Amanda?
Hi, I have several partitions using XFS and would like to ask how I can use xfsdump with Amanda? The backup server runs on Debian Linux and the debian packages amanda-server amanda-common and amanda-client are installed. Regards, Ben
Re: strange amanda header
On Wed, Jan 02, 2002 at 09:52:04PM +0100, Alessandro Prete wrote: Someone has never had a similar problem? amrestore: 0: skipping start of tape: date 20011213 label Daily1-CdC-001 amrestore: strange amanda header: AMANDA: FILE 20011211 leonardo / let 1 comp .gz program /bin/gtar It should be: AMANDA: FILE 20011211 leonardo / lev 1 comp .gz program /bin/gtar ^ It look like a memory bug, one bit is fliped. Jean-Louis -- Jean-Louis Martineau email: [EMAIL PROTECTED] Departement IRO, Universite de Montreal C.P. 6128, Succ. CENTRE-VILLETel: (514) 343-6111 ext. 3529 Montreal, Canada, H3C 3J7Fax: (514) 343-5834
Re: Index problems
On Wed, 2 Jan 2002 at 3:39pm, [EMAIL PROTECTED] wrote in 20020102_1 (head) 07414661435/./var/amanda/gnutar-lists/dagaz.lib.unomaha.edu_usr_local_1 07414664217/./amanda-2.4.2p2/amplot/amcat.awk 07414664217/./amanda-2.4.2p2/amplot/amcat.awk.in 07414664217/./amanda-2.4.2p2/amplot/amplot.awk 07414664217/./amanda-2.4.2p2/amplot/amplot.g 07414664217/./amanda-2.4.2p2/amplot/amplot.sh 07414664217/./amanda-2.4.2p2/amplot/amplot.sh.in 07414664217/./amanda-2.4.2p2/amplot/Makefile 07414664217/./amanda-2.4.2p2/amplot/Makefile.am 07414664217/./amanda-2.4.2p2/amplot/Makefile.in ^^^ Those characters indicate a corrupt index file generated by a bad version of tar... client tar (GNU tar) 1.13 And that's your culprit. Upgrade to at least 1.13.17, preferably higher. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: (tapeless) amanda-242-tape make failure
On December 28 2001, Amanda Listee wrote: I'm trying to install the tapeless amanda-242-tapeio sourceforge version on a FreeBSD-4.4 white box: [snip] hotpink# make Making all in config Making all in common-src Makefile, line 440: Need an operator make: fatal errors encountered -- cannot continue *** Error code 1 Nearly every time I've seen the Need an operator error when building something on FreeBSD, it has been because the Makefile is generated for GNU make, and the BSD make does not like it. Autoconf almost always produces these types of makefiles, and the Amanda build is not unique in this. If you don't have it installed already, install GNU make (cd /usr/ports/ devel/gmake; make all make install) and then use it to make Amanda (type gmake rather than make). You should also try using gmake whenever you see that Need an operator error while building something from source. In some cases, and I can't remember if this is true of Amanda, you'll need to make sure that gmake spawns itself when multiple make processes are involved. You can do this by setting the environment variable MAKE. I usually invoke gmake like this: gmake MAKE=gmake target Where target is the Makefile target (usually all or install). You'll notice that USE_GMAKE= yes appears in the FreeBSD ports of Amanda (/usr/ports/misc/amanda24-server/Makefile is the master makefile for the ports), for this very reason. Of course, you should probably also follow the advice you received from Jean-Louis Martineau and use the amanda-243-branch sources. I hope this helps, -Ben -- Benjamin Lewis [EMAIL PROTECTED] Database Analyst/Programmer Instructional Computing Services - Accounts Group Purdue University
Re: amandad keeps dying for some unknown reason......
On Wed, Jan 02, 2002 at 02:30:57PM -0500, Don Potter wrote: Dan Wilder wrote: This could be an inetd issue, if you have a whole lot of disklist entries pointing to the server in question. Rate limiting is a common inetd feature. The idea is that more than some number of requests per unit time means the same request is coming in repeatedly, and the server isn't satisfying it. [ ... ] This is a initial installation so there are only 3 total entries in the disklistI don't believe that there is an equivilant to increase a number of given server processes in Solaris as there is Linux by modifying the /etc/inetd.conf. I would assume that would be in the /etc/system, but it wouldn't be the first time that I'm wrong. Aaah, rats. I strike out on that one. Can't see that three disklist entries would exceed whatever's allowed under inetd, in any way. Back to you, Don, and your hypothesis that amandad is really dying. Is there anything in /tmp/amanda/amandad.debug after the failure? -- - Dan Wilder [EMAIL PROTECTED] Technical Manager Editor SSC, Inc. P.O. Box 55549 Phone: 206-782-8808 Seattle, WA 98155-0549URL http://embedded.linuxjournal.com/ -
Re: Index problems
tar version 1.13 puts those extra numbers at the start of each entry. These mess up the indexing. Uprade to a later version. I use 1.13.17 and 1.13.19 with no problems. On Wed, 2 Jan 2002 [EMAIL PROTECTED] wrote: - I have the index = yes setup in the conf file - - when i connect i get: - - 220 index/tape_server AMANDA index server (2.4.2p2) ready. - 200 Access OK - Setting restore date to today (2002-01-02) - 200 Working date set to 2002-01-02. - 200 Config set to normal. - 200 Dump host set to dagaz.site.edu. - Can't determine disk and mount point from $CWD - amrecover setdisk /usr/local - Scanning /var/backups/amanda... - 200 Disk set to /usr/local. - No index records for disk for specified date - If date correct, notify system administrator - - - in /var/amanda/index/host/disk/: - - -rw---1 amanda bin 2968629 Jan 2 12:38 20011221_0 - -rw---1 amanda bin258910 Dec 21 16:41 20011221_0.gz - -rw---1 amanda bin 13409 Dec 21 14:39 20011221_1.gz - -rw---1 amanda bin160235 Jan 2 16:33 20020102_1 - -rw---1 amanda bin 15990 Jan 2 15:10 20020102_1.gz - - in 20020102_1 - - (head) - 07414661435/./var/amanda/gnutar-lists/dagaz.lib.unomaha.edu_usr_local_1 - 07414664217/./amanda-2.4.2p2/amplot/amcat.awk - 07414664217/./amanda-2.4.2p2/amplot/amcat.awk.in - 07414664217/./amanda-2.4.2p2/amplot/amplot.awk - 07414664217/./amanda-2.4.2p2/amplot/amplot.g - 07414664217/./amanda-2.4.2p2/amplot/amplot.sh - 07414664217/./amanda-2.4.2p2/amplot/amplot.sh.in - 07414664217/./amanda-2.4.2p2/amplot/Makefile - 07414664217/./amanda-2.4.2p2/amplot/Makefile.am - 07414664217/./amanda-2.4.2p2/amplot/Makefile.in - - - so it looks like all the info is there but the server is not reading them - ?? - - btw - server tar (GNU tar) 1.13.19 - client tar (GNU tar) 1.13 - - thanks - - -- -- Stephen Carville UNIX and Network Administrator Ace Flood USA 310-342-3602 [EMAIL PROTECTED]
AMANDA Configuration
Hi, I have the following configuration: O/S:Debian 2.2 (potato) Amanda: amanda-client amanda-server amanda-common packages direct from Debian. Client: Server: Client SambaTest Server:calvin tapedir/tbu The client has the base Debian install, samba, dump, amanda-common, and amanda-client. The server has the base Debian install,.amanda-common, and amanda server When I run AmCheck it returns no errors. When I run AmDump and look at /tbu I can see a file being written to. The Client has about 3.8Gig total on it's disk however the file in /tbu reaches a size of about 141MB and not other action occurres. It takes another 10 minutes or so for the prompt to apear on the server. The tape never functions. The log is ^^ START planner date 20020102 INFO planner Adding new disk SambaTest.stgregoryschool.net:hda1. START driver date 20020102 START taper datestamp 20020102 label DAY00 tape 0 FINISH planner date 20020102 STATS driver startup time 50.501 FAIL dumper SambaTest.stgregoryschool.net hda1 0 [data timeout] sendbackup: start [SambaTest.stgregoryschool.net:hda1 level 0] sendbackup: info BACKUP=/sbin/dump sendbackup: info RECOVER_CMD=/bin/gzip -dc |/sbin/restore -f... - sendbackup: info COMPRESS_SUFFIX=.gz sendbackup: info end | DUMP: Date of this level 0 dump: Wed Jan 2 08:44:36 2002 | DUMP: Date of last level 0 dump: the epoch | DUMP: Dumping /dev/hda1 (/) to standard output | DUMP: Label: none | DUMP: mapping (Pass I) [regular files] | DUMP: mapping (Pass II) [directories] | DUMP: estimated 3986989 tape blocks. | DUMP: Volume 1 started at: Wed Jan 2 08:47:20 2002 | DUMP: dumping (Pass III) [directories] | DUMP: dumping (Pass IV) [regular files] INFO taper tape DAY00 kb 0 fm 0 [OK] FINISH driver date 20020102 time 2227.357 ^^ I'm at a total loss. Any help greatly appreciated. Thanks, Keith
Re: add machine to home net, put in iptables_nat rules, amanda dies.
On Wednesday 02 January 2002 02:56 am, Jeffrey S. Mulliken wrote: Gene, Don't know if this is your first networked machine, but in case your just getting started with xinetd, bear in mind that by default, the old inetd configuration used to have all services enabled. Xinetd, on the other hand, comes standard with all services 'disabled'. So, check the contents of your /etc/xinetd.d/ directory, and change all of the amanda related files so that they have 'disable' set to 'no'. I think I have that part under control. I've even written a couple of things for the xinetd.d directory. I reverted xinetd to 2.3.3 and everything is now working once again, including last nights backup. Once you begin to understand xinetd, it does seem to be a better way to do things. I went back and checked xinetd-2.4.3's dependencies and the only place it has a problem is in its requesting the newer, can't build a kernel with it, version of gcc AT RUN TIME. I for one fail to see the logic in flooding the rawhide site with stuff that can be installed, but will not run on any existing distro. A fresh version of gcc-3.10-0.11 was released on Dec 28, and even if you try to install every related, identically versioned package in one swell foop, the broken dependency list, other stuff on the system that will break, is probably 2-3 letter sized pages long and includes the huge majority of your everyday applications! Thats why my bit of a tirade and the comparison to fresh male bovine excrement. I'd consider dl'ing and building the new gcc released yesterday, but I'd rather have rpms for such an important piece of the system. I don't even know if it can be built with 2.96-101 in one pass, they've released code before that had to be built in 2 steps, first with the older compiler, and then repeat with itself before it was right. I've got better things to do, like trying to make an epson 1250u scanner work without bringing the system down. -- Cheers, Gene
Index problems
I have the index = yes setup in the conf file when i connect i get: 220 index/tape_server AMANDA index server (2.4.2p2) ready. 200 Access OK Setting restore date to today (2002-01-02) 200 Working date set to 2002-01-02. 200 Config set to normal. 200 Dump host set to dagaz.site.edu. Can't determine disk and mount point from $CWD amrecover setdisk /usr/local Scanning /var/backups/amanda... 200 Disk set to /usr/local. No index records for disk for specified date If date correct, notify system administrator in /var/amanda/index/host/disk/: -rw---1 amanda bin 2968629 Jan 2 12:38 20011221_0 -rw---1 amanda bin258910 Dec 21 16:41 20011221_0.gz -rw---1 amanda bin 13409 Dec 21 14:39 20011221_1.gz -rw---1 amanda bin160235 Jan 2 16:33 20020102_1 -rw---1 amanda bin 15990 Jan 2 15:10 20020102_1.gz in 20020102_1 (head) 07414661435/./var/amanda/gnutar-lists/dagaz.lib.unomaha.edu_usr_local_1 07414664217/./amanda-2.4.2p2/amplot/amcat.awk 07414664217/./amanda-2.4.2p2/amplot/amcat.awk.in 07414664217/./amanda-2.4.2p2/amplot/amplot.awk 07414664217/./amanda-2.4.2p2/amplot/amplot.g 07414664217/./amanda-2.4.2p2/amplot/amplot.sh 07414664217/./amanda-2.4.2p2/amplot/amplot.sh.in 07414664217/./amanda-2.4.2p2/amplot/Makefile 07414664217/./amanda-2.4.2p2/amplot/Makefile.am 07414664217/./amanda-2.4.2p2/amplot/Makefile.in so it looks like all the info is there but the server is not reading them ?? btw server tar (GNU tar) 1.13.19 client tar (GNU tar) 1.13 thanks
Re: .amanda.exclude.gtar
Hi, I'm using the .amanda.exclude.gtar script to exclude a few things from our backup. I am having a problem with netscape cache. In the exclude script I have the following line: */.netscape/cache/* I still get problems in the backup report: ? gtar: ./home/monachus/.netscape/cache/13/cache3C2C0E93DA8B3B8.css: Warning: Cannot stat: No such file or directory I think gtar expects regular expressions. What you have written is just shell wildcarding - not half as powerful by the way. Better try .*/.netscape/cache/.* The . means exact one character, the asterisk means none or more of the thing before. For more information see man regexp :-) Regards, Christopher
Re: .amanda.exclude.gtar
Hello, Use ./home/monachus/.netscape/cache if /home is the root of the partition being backed up. Remeber exclude are relative to the partition being backed up. Andrew On Fri, 28 Dec 2001, Troy Nachtigall wrote: Hi, I'm using the .amanda.exclude.gtar script to exclude a few things from our backup. I am having a problem with netscape cache. In the exclude script I have the following line: */.netscape/cache/* I still get problems in the backup report: ? gtar: ./home/monachus/.netscape/cache/13/cache3C2C0E93DA8B3B8.css: Warning: Cannot stat: No such file or directory ? gtar: ./home/monachus/.netscape/cache/14/cache3C2C0DF4D94B3B8.png: Warning: Cannot stat: No such file or directory ? gtar: ./home/monachus/.netscape/cache/14/cache3C2C0DF4D95B3B8.png: Warning: Cannot stat: No such file or directory ? gtar: ./home/monachus/.netscape/cache/14/cache3C2C0E94DB0B3B8.gif: Warning: Cannot stat: No such file or directory ? gtar: ./home/monachus/.netscape/cache/14/cache3C2C0E94DB4B3B8.gif: Warning: Cannot stat: No such file or directory ? gtar: ./home/monachus/.netscape/cache/15/cache3C2C0DF5D96B3B8.png: Warning: Cannot stat: No such file or directory ? gtar: ./home/monachus/.netscape/cache/15/cache3C2C0DF5D97B3B8.png: Warning: Cannot stat: No such file or directory ? gtar: ./home/monachus/.netscape/cache/15/cache3C2C0DF5D98B3B8.png: Warning: Cannot stat: No such file or directory ? gtar: ./home/monachus/.netscape/cache/15/cache3C2C0DF5D99B3B8.png: Warning: Cannot stat: No such file or directory ? gtar: ./home/monachus/.netscape/cache/16/cache3C2C0DF6D9AB3B8.png: Warning: Cannot stat: No such file or directory Any suggestions? Thanks!
Re: access as operator not allowed from....
On Thu, Jan 03, 2002 at 03:13:10PM +0100, Tom Beer wrote: ERROR: strawberry.system: [access as operator not allowed from [EMAIL PROTECTED]] open of //.amandahosts failed [...] /usr/home/operator/.amandahosts We've always had to put .amandahosts in /, for whatever reason. Ok, I've done this and the straight on results are Amanda Backup Client Hosts Check ERROR: strawberry.system: [can not read/write /usr/local/var/amanda/gnutar-lists/.: No such file or directory] Client check: 1 host checked in 0.097 seconds, 1 problem found if I do a 777 on the whole tree I get Amanda Backup Client Hosts Check ERROR: strawberry.system: [can not read/write /usr/local/var/amanda/gnutar-lists/.: Permission denied] Client check: 1 host checked in 0.109 seconds, 1 problem found or vice versa ;-|
amanda,Lotus Notes and win2000
Is anyone out there, backing up a Lotus Notes server (on win 2k) with amanda? Any succes, failures? Also how much success/failures has anyone had with a restoring about everything on a windows box? I know backing up data is easy to restore, but for most programs you need to re-install. -Hussain
Re: strange amanda header
You should probably double check your hardware. I once had a similar error where every ~2,000,000,000th double word on the tape was corrupted. It turned out to be a bad mainboard (asus a7v133 pci problem). Run amverify regulary for a while, gzip will report these kind of errors (crc error). Greetings, Moritz You are right, but I have realized that many tapes have the same (let instead lev) error or a gzip corrupted data format and never a tape header error. I tested the drive with tar (1.13.17, 1.13.19 and 1.13.25) cpio and dd (on old and new tapes) and it seems to work properly. Could the problem be an exausted 6 tape set ? Why dumps terminate without any I/O error? Now, having changed some tapes, upgraded tar to 1.13.25 and gzip to 1.3.2 (it was a thing that I already had to do), amrestoring tapes seems to work, but I'm not sure of the problem. [...]
access as operator not allowed from....
Hi, I'm trying to get amanda(client) running on a Freebsd4.3-Release. I fetched the ports did a ./configure \ --with-user=operator \ --with-group=operator \ --with-amandahosts \ --with-config=daily \ --with-gnutar=/bin/tar \ --with-tape-server=milestonenfs.system \ --with-configdir=/etc/amanda \ --without-server \ --with-index-server=milestonenfs.system and make install everything went on smoothly but a amcheck -c on the server fails regularly with Amanda Backup Client Hosts Check ERROR: strawberry.system: [access as operator not allowed from [EMAIL PROTECTED]] open of //.amandahosts failed Client check: 1 host checked in 0.033 seconds, 1 problem found (brought to you by Amanda 2.4.2p2) I have to mention that on the server p2 and on the client p1 is running, if that makes any difference. /usr/home/operator/.amandahosts milestonenfs.system operator /etc/inetd.conf amanda dgramudp waitoperator/usr/local/libexec/amandad amandad /etc/hosts.allow amandad : 192.168.1.0/255.255.255.240 : allow On a linux client, with the same configuration it works perfect. Thanks for any suggestions Tom
Can't restore from Ultrium: changing volumes on pipe input, abort?
Since attempting to replace our old DDS3 tape drives with HP Ultriums,
Amanda backups haven't worked properly. The HP tape drives themselves
seem OK when we back things up to them directly. However when we use
Amanda, the backups seem to work properly but restores fail.
In slightly more detail: we have a Sun Ultra E250 running Solaris 2.6.
It has an old DDS3 tape drive and an HP SureStore Ultrium 230 tape
drive, both external. Amanda 2.3.0 is installed, and we've used it
happily for some time with the DDS3 drives. We can write data to
Ultrium tapes with tar or ufsdump, and read it back with tar or
ufsrestore. It seems to be only with Amanda that problems occur.
Restoring files from one backup on the Amanda tape is usually done
with this command:
amrestore -p /dev/rmt/0n machine name disk | ufsrestore -if -
When this is tried with one of the Ultrium backup tapes, the restore
proceeds as normally: I choose the files to be restored, type
extract, and ufsrestore successfully restores some of the files from
the tape; but before finishing the restore, it stops and gives me the
message
changing volumes on pipe input
abort? [yn]
I tried asking Sun, thinking that this might be a Solaris issue
(before I noticed that the problem only occurs with Amanda-written
ufsdump tapes), but Sun hasn't heard of this problem and says that
it's never heard of Amanda and doesn't support it. Has anyone here
come across a problem like this, or do you know what might be going
wrong?
I'm not sure that I should trust the tapetype definition that I've
been using - the second of the definitions below. Does anyone have a
better one?
define tapetype Ultrium {
comment HP Ultrium 2300 LTO drive, native
length 101376 mbytes
filemark 0 kbytes
speed 13334 kbytes
}
define tapetype Ultrium-compressed {
comment HP Ultrium 2300 LTO drive using compression
length 16 mbytes
filemark 0 kbytes
speed 13334 kbytes
}
If more information would help, just ask, and I'll try to supply it.
Happy New Year,
--
-- Chris Cooke.
Division of Informatics, University of Edinburgh, Scotland.
Re: Amanda 2.4.2 and Onstream ADR 50 Tape?
On Thu, 2002-01-03 at 13:07, Moritz Both wrote: Hi, actually yes. I have. I did restore some backups a while ago, but it _could_ be that the Tape drive was connected to a Sym53c875. I experience exactly the same problem that you describe at the moment (on an Adaptec UW controller). I currently have a brand new advance exchange unit directly from OnStream (while my local dealer was a complete failure in getting any support, the people from the OnStream hotline are very nice and competent and _really_ helpful. For their support, I can really recommend Onstream). This brand new tape drive shows exactly the same symptoms. So I do consider this either a systematic failure in our (quite similar) HW setup (I use RH6.2+ with 2.2 kernel) or a real issue with the drive firmware which would be very sad. I'm right now in the process of swapping SCSI controllers; I will keep you informed. Regards Henning Henning, have you ever been able to actually *restore* files from amanda tapes using this device? Which is the firmware verison it has? See also my email on the list from half an hour ago. Greetings, Moritz -- Dipl.-Inf. (Univ.) Henning P. Schmiedehausen -- Geschaeftsfuehrer INTERMETA - Gesellschaft fuer Mehrwertdienste mbH [EMAIL PROTECTED] Am Schwabachgrund 22 Fon.: 09131 / 50654-0 [EMAIL PROTECTED] D-91054 Buckenhof Fax.: 09131 / 50654-20
Re: strange amanda header
You are right, but I have realized that many tapes have the same (let instead lev) error or a gzip corrupted data format and never a tape header error. I tested the drive with tar (1.13.17, 1.13.19 and 1.13.25) cpio and dd (on old and new tapes) and it seems to work properly. Could the problem be an exausted 6 tape set ? Why dumps terminate without any I/O error? Now, having changed some tapes, upgraded tar to 1.13.25 and gzip to 1.3.2 (it was a thing that I already had to do), amrestoring tapes seems to work, but I'm not sure of the problem. Thanks, Alessandro - Original Message - From: Jean-Louis Martineau [EMAIL PROTECTED] To: Alessandro Prete [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Wednesday, January 02, 2002 10:57 PM Subject: Re: strange amanda header On Wed, Jan 02, 2002 at 09:52:04PM +0100, Alessandro Prete wrote: Someone has never had a similar problem? amrestore: 0: skipping start of tape: date 20011213 label Daily1-CdC-001 amrestore: strange amanda header: AMANDA: FILE 20011211 leonardo / let 1 comp .gz program /bin/gtar It should be: AMANDA: FILE 20011211 leonardo / lev 1 comp .gz program /bin/gtar ^ It look like a memory bug, one bit is fliped. Jean-Louis -- Jean-Louis Martineau email: [EMAIL PROTECTED] Departement IRO, Universite de Montreal C.P. 6128, Succ. CENTRE-VILLETel: (514) 343-6111 ext. 3529 Montreal, Canada, H3C 3J7Fax: (514) 343-5834
Re: How to use xfsdump with Amanda?
In a message dated: Thu, 03 Jan 2002 11:08:35 +1100 Ben Wong said: Hi, I have several partitions using XFS and would like to ask how I can use xfsdump with Amanda? The backup server runs on Debian Linux and the debian packages amanda-server amanda-common and amanda-client are installed. You should be able to just configure, compile, and install the amanda client sw on that system and it should work. The ./configure script should look for xfsdump and note it's location for use with xfs partitions. I didn't have to do anything special for my system running xfs under Linux, other than create a symlink to where amanda was looking for xfsdump (IRIX places the binary in a different location than it ends up under Linux, and configure didn't detect it). But that's since been fixed IIRC. -- Seeya, Paul God Bless America! ...we don't need to be perfect to be the best around, and we never stop trying to be better. Tom Clancy, The Bear and The Dragon
Problems with dumps
Hi all, I'm having trouble getting one of my clients backed up. There are 13 file systems on the client which need to be dumped, totalling about 12GB of data. I'm getting error messages like the following for several of the file systems: hacluster1 /dev/sda12 lev 0 FAILED [dumps too big, but cannot\ incremental dump skip-incr disk] I know that amanda seems to think that the dumps are too big, and failing these file systems because I've dis-allowed incremental backups. However, I've also specified the use of 2 tapes for the backups, and amanda doesn't seem to be filling both: Estimate Time (hrs:min)0:10 Run Time (hrs:min) 9:26 Dump Time (hrs:min)7:51 7:49 0:02 Output Size (meg) 54711.454709.12.2 Original Size (meg) 89777.289755.3 22.0 Avg Compressed Size (%)60.9 61.0 10.2 (level:#disks ...) Filesystems Dumped 33 28 5 (1:5) Avg Dump Rate (k/s) 1981.3 1991.6 15.7 Tape Time (hrs:min)6:50 6:50 0:00 Tape Size (meg) 54712.454710.02.4 Tape Used (%) 156.3 156.30.0 (level:#disks ...) Filesystems Taped33 28 5 (1:5) From the 'Tape Used' it appears that amanda is only filling 50% of the second tape. The 'Tape Size' seems to indicate I'm only filling about 55GB worth of tape. I'm using a DLT7000 drive with DLT4 tapes. I should be able to get 70GBs worth of data across 2 tapes, no? So, I should be able to get another 15GBs onto the second tape, by my calculations, which is fine, since there's less than 12GB currently failing. Any ideas? Thanks, -- Seeya, Paul God Bless America! ...we don't need to be perfect to be the best around, and we never stop trying to be better. Tom Clancy, The Bear and The Dragon
SUMMARY: Re: onstream adr50 problems
Hello everyone who considers using the Onstream ADR50 drive with amanda, I won't let you wait any longer since Onstream support do not get back to me this time. The ADR50 drive, which is supposed to be a full linux compatible SCSI tape drive (it should work with the standard st scsi tape driver), does *not* work with amanda with firmware version 2.39. Although I had posted the problem desciption some time ago in this thread, I include it below again for completness. The problem description shows that we have spend quite a while to track down the problem. The problem is timeout related. It seems that the ADR50 gets into trouble when it runs out of data during writing a file and then receives the command to write a file mark. The drive will proceed to write the data, but reading the tape only the first file appears to be readable. After the first file has been read, the device reports a media error. Amanda *always* writes the file mark just before starting to write the next file, not right after a file has been written completely. The timeout in question happens after writing the tape label during the estimate collection phase. 90 seconds are enough. Onsteam support did respond to my inquiery two times. The second email I have got was cc'ed to me. In that email, a staff member guessed the problem would be firmware related and asked someone else to look into it. This has happened a month ago. I asked them when they will look into it but I so far haven't heared from them. I agree the problem is likely to be firmware related. The firmware version we can speak about is 2.39; there is currently no newer version available. We had asked on the amanda users list for people using the ADR50 drive with amanda. Only one person responded, saying that after trying the ADR drive, they had returned it and are now using a DAT drive. I will respond to myself here if I hear anything new about the problem. Greetings, Moritz Problem description follows --- -- 8 - We have a problem with our new OnStream ADR50 tape streamer. Brief problem description: The ADR50 device writes data which it cannot read afterwards under certain conditions. Those conditions are described below. Hardware description: AMD Duron 750. Asus A7V133 main board. 256 MB RAM. Adaptec 29160N SCSI controller. SCSI LVD bus internal with 2 devices: HDD IBM 20 GB (scsi id 0), tape device OnStream ADR50 internal (scsi id 5) Firmware rev. 2.39 S/N EA21J290564 Other SCSI bus (narrow 50pin internal): CDROM drive (scsi id 6). Software description: OS: RedHat Linux 7.1 kernel: 2.4.2, 2.4.9 (both RedHat patched versions; the problem appears with both) Tried Adaptec SCSI driver verison 6.1.7 (w/ kernel 2.4.2), 6.2.1 and 6.2.4 (w/ kernel 2.4.9); the problem appears with all of them Description of problem: Although the problem initially appeared when using the amanda backup software, it could be reproduced using a small C program which simulates what amanda does. The program performs the following steps: 1. open the tape device (given on the command line) in read/write mode (it remains open for all following steps) 2. rewind the tape. 3. read 32 KBytes of data from the tape. 4. rewind again. 5. write 32 KByte of data. 6. wait for 120 seconds 7. write an end of file mark 8. write another 1024 KBytes of data 9. write an end of file mark 10. rewind the tape 11. read 32 KBytes of data 12. try to read 32 KBytes of data, expect to get 0 bytes but pass the file mark 13. read 32 KBytes of data (file 2) When doing this, step 13 fails reproducibly. The program gets error code I/O error. Note that the no rewind tape device (/dev/nst0) was used for the tests in all cases. The most interesting part is that everything works fine when the program skips step 6 (wait for 120 seconds). What I have tried without success: * Replaced the SCSI controller * different kernel versions (see above) * different new SCSI drivers (aic7xxx, see above) Full details follow below. This is a transcript of a typical test program session: ---8- [root@hl tapetest]# ./test1 /dev/nst0 test1: rewind... success test1: reading 32768 bytes using 32768 byte blocks... + success test1: rewind... success test1: writing 32768 bytes using 32768 byte blocks... + success test1: sleeping for 120 s...woke up. test1: write filemark... success test1: writing 1048576 bytes using 32768 byte blocks... success test1: write filemark... success test1: rewind... success test1: reading 32768 bytes using 32768 byte blocks... + success test1: skipping file mark... done.test1: reading 1048576 bytes using 32768
Re: Can't restore from Ultrium: changing volumes on pipe input, abort?
On Thu, Jan 03, 2002 at 03:20:02PM +, Chris Cooke wrote: with this command: amrestore -p /dev/rmt/0n machine name disk | ufsrestore -if - When this is tried with one of the Ultrium backup tapes, the restore proceeds as normally: I choose the files to be restored, type extract, and ufsrestore successfully restores some of the files from the tape; but before finishing the restore, it stops and gives me the message changing volumes on pipe input abort? [yn] I tried asking Sun, thinking that this might be a Solaris issue (before I noticed that the problem only occurs with Amanda-written ufsdump tapes), but Sun hasn't heard of this problem and says that it's never heard of Amanda and doesn't support it. Has anyone here come across a problem like this, or do you know what might be going wrong? Amanda 2.4.2p2, Solaris 2.6 server, Solaris 2.6 client, DLT-7000, file system size ~25GB. You're not the only person to see this. If you search the amanda-users archive for: changing volumes on pipe input, you'll find a not-terribly cheerful thread from last May. I've seen it once, so it appears to be intermittent for me. In my case, I got all files, but 'ufsrestore i' and 'ufsrestore x' failed with your error message, so I didn't get proper directory owner/group/permissions. In my case, 'ufsrestore r' did work perfectly, so I'm not quite as frightened as I would be otherwise. The trials I ran were: Trial Results - --- amrecover Fail with changing volumes on pipe input amrestore to file, then: ufsrestore if Fail with Specify next volume #. ufsrestore xf Fail with Specify next volume #. ufsrestore rf Worked perfectly. It's not clear to me if this is ufsdump problem, a ufsrestore problem, a taper problem, or some strange combination. I'm moving everything to Solaris 8 in the next two months, and have fantasized that the issue will go away; though the amanda-users archive is not terribly optimistic about that, either. :-) -- Jay Lessert [EMAIL PROTECTED] Accelerant Networks Inc. (voice)1.503.439.3461 Beaverton OR, USA(fax)1.503.466-9472
restoring with amrestore
hello, is anybody out there who can tell me, whether I can put the saved files from the tape directly on the original position of a client? I backuped an etc-directory over eth0 and want to write it back directly in the old etc-directory. is this possible over ethernet? and how? Thank you very much! Leonie
RE: Problems with dumps
Paul, A couple of things might help track down where the problem is coming from. First, if you can add a third tape to a run, that will indicate whether the problem is with AMANDA's tape size estimate or not. Next, do you have enough holding disk space for that backup? You can test this by configuring that entry in disklist to use a backup type that does not go to the holding disk. That should help narrow down where the limitation is. Paul -Original Message- From: Paul Lussier [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 03, 2002 11:35 AM To: [EMAIL PROTECTED] Subject: Problems with dumps Hi all, I'm having trouble getting one of my clients backed up. There are 13 file systems on the client which need to be dumped, totalling about 12GB of data. I'm getting error messages like the following for several of the file systems: hacluster1 /dev/sda12 lev 0 FAILED [dumps too big, but cannot\ incremental dump skip-incr disk] I know that amanda seems to think that the dumps are too big, and failing these file systems because I've dis-allowed incremental backups. However, I've also specified the use of 2 tapes for the backups, and amanda doesn't seem to be filling both: Estimate Time (hrs:min)0:10 Run Time (hrs:min) 9:26 Dump Time (hrs:min)7:51 7:49 0:02 Output Size (meg) 54711.454709.12.2 Original Size (meg) 89777.289755.3 22.0 Avg Compressed Size (%)60.9 61.0 10.2 (level:#disks ...) Filesystems Dumped 33 28 5 (1:5) Avg Dump Rate (k/s) 1981.3 1991.6 15.7 Tape Time (hrs:min)6:50 6:50 0:00 Tape Size (meg) 54712.454710.02.4 Tape Used (%) 156.3 156.30.0 (level:#disks ...) Filesystems Taped33 28 5 (1:5) From the 'Tape Used' it appears that amanda is only filling 50% of the second tape. The 'Tape Size' seems to indicate I'm only filling about 55GB worth of tape. I'm using a DLT7000 drive with DLT4 tapes. I should be able to get 70GBs worth of data across 2 tapes, no? So, I should be able to get another 15GBs onto the second tape, by my calculations, which is fine, since there's less than 12GB currently failing. Any ideas? Thanks, -- Seeya, Paul God Bless America! ...we don't need to be perfect to be the best around, and we never stop trying to be better. Tom Clancy, The Bear and The Dragon
AW: Index problems
Hi, it's a bug in tar version 2.13. Just update your tar on the client side. Following I documented how it should look like: --- ERROR: tar v2.13 --- 07372062604/./user/.bash_history 07372062604/./user/.profile 07372603054/./user/.mc/history 07372603054/./user/.mc/ini 07372772335/./user/tmp/dante-1.1.10/BUGS --- ERROR: tar v2.13 --- --- OK: tar v2.13.19 --- /user/.bash_history /user/.profile /user/.mc/history /user/.mc/ini /user/tmp/dante-1.1.10/BUGS --- OK: tar v2.13.19 --- cheers, Chrstian -Ursprüngliche Nachricht- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Gesendet: Mittwoch, 2. Januar 2002 22:40 An: [EMAIL PROTECTED] Betreff: Index problems I have the index = yes setup in the conf file when i connect i get: 220 index/tape_server AMANDA index server (2.4.2p2) ready. 200 Access OK Setting restore date to today (2002-01-02) 200 Working date set to 2002-01-02. 200 Config set to normal. 200 Dump host set to dagaz.site.edu. Can't determine disk and mount point from $CWD amrecover setdisk /usr/local Scanning /var/backups/amanda... 200 Disk set to /usr/local. No index records for disk for specified date If date correct, notify system administrator in /var/amanda/index/host/disk/: -rw---1 amanda bin 2968629 Jan 2 12:38 20011221_0 -rw---1 amanda bin258910 Dec 21 16:41 20011221_0.gz -rw---1 amanda bin 13409 Dec 21 14:39 20011221_1.gz -rw---1 amanda bin160235 Jan 2 16:33 20020102_1 -rw---1 amanda bin 15990 Jan 2 15:10 20020102_1.gz in 20020102_1 (head) 07414661435/./var/amanda/gnutar-lists/dagaz.lib.unomaha.edu_us r_local_1 07414664217/./amanda-2.4.2p2/amplot/amcat.awk 07414664217/./amanda-2.4.2p2/amplot/amcat.awk.in 07414664217/./amanda-2.4.2p2/amplot/amplot.awk 07414664217/./amanda-2.4.2p2/amplot/amplot.g 07414664217/./amanda-2.4.2p2/amplot/amplot.sh 07414664217/./amanda-2.4.2p2/amplot/amplot.sh.in 07414664217/./amanda-2.4.2p2/amplot/Makefile 07414664217/./amanda-2.4.2p2/amplot/Makefile.am 07414664217/./amanda-2.4.2p2/amplot/Makefile.in so it looks like all the info is there but the server is not reading them ?? btw server tar (GNU tar) 1.13.19 client tar (GNU tar) 1.13 thanks
Re: how to recover to remote amanda client with amrecover
On Mon, 18 Feb 2002 at 5:13pm, Hikawa wrote I could not recover .emacs.el file into remote host (mailde). .emacs.el file was recovered into tape server's /root directory. Could you tell me how to recover files into amanda remote host ? amrecover recovers files onto whatever host it is run on. So, if you want to recover files onto mailde, run amrecover on mailde. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: restoring with amrestore
On Mon, 18 Feb 2002 at 1:30pm, Nünighoff, Leonie, NUE wrote is anybody out there who can tell me, whether I can put the saved files from the tape directly on the original position of a client? I backuped an etc-directory over eth0 and want to write it back directly in the old etc-directory. is this possible over ethernet? and how? Thank you very much! Run amrecover on the client in the root directory of the disklist entry. Recovered files will go right back where they came from. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: Compile error
--- Thomas Hepper [EMAIL PROTECTED] wrote: Hi, On Thu, Feb 14, 2002 at 03:00:00PM +, Robert Early wrote: Hi, I;m getting the following compile error when trying to compile amanda amanda-2.4.3b2: gcc -D_FILE_OFFSET_BITS=64 -g -O2 -o chg-scsi-chio chg-scsi-chio.o scsi-hpux.o scsi-chio.o ../server-src/.libs/libamserver.a ../tape-src/.libs/libamtape.a ../common-src/.libs/libamanda.a -lgen -lm -ltermcap -lnsl -lcur_colr /usr/ccs/bin/ld: Unsatisfied symbols: config_dir (data) collect2: ld returned 1 exit status *** Error exit code 1 Any ideas? Which OS, which configure flags ?? It's HPUX 11.0, with the following configure flags: configure --with-user=amanda --prefix=/opt/amanda --localstatedir=/var/opt --with-configdir=/etc/opt/amanda --with-amandahosts --with-group=sys Robert. __ Do You Yahoo!? Everything you'll ever need on one web page from News and Sport to Email and Music Charts http://uk.my.yahoo.com
restoring to a windows client
I think I know the answer, but I'm fairly new to amanda so I wanted to make sure. I have amanda backing up 8-10 solaris/linux boxes and just recently 3 windows boxes. I am assuming that if I need to recover anything for the windows boxes, i have to amrecover to one of the unix/linux boxes (tape server or another) and then ftp the recovered files to windows? I haven't seen any mention of an amanda client for windows. Right? Thanks, Gene -- Gene Matthews Matthews Midrange Consulting, Inc. (678) 923-8327 (877) 882-6291 (toll free) http://mmc-inc.com
Re: restoring to a windows client
I run a proftpd server for Windows recovery on the Amanda backup server. When I need to recover files from a MS box, I cd to the ftp server's root directory and run amrecover there. I then have the MS client's user ftp into the server and download the files that they need. It works well in my situation. (about 50-60 Windows clients). You can also use HTTP to do individual file recovery. Good Luck! On Mon, 2002-02-18 at 08:45, Gene Matthews wrote: I think I know the answer, but I'm fairly new to amanda so I wanted to make sure. I have amanda backing up 8-10 solaris/linux boxes and just recently 3 windows boxes. I am assuming that if I need to recover anything for the windows boxes, i have to amrecover to one of the unix/linux boxes (tape server or another) and then ftp the recovered files to windows? I haven't seen any mention of an amanda client for windows. Right? Thanks, Gene -- Gene Matthews Matthews Midrange Consulting, Inc. (678) 923-8327 (877) 882-6291 (toll free) http://mmc-inc.com -- Brad Tilley, OUB Sys. Admin. http://bursar.vt.edu/rtilley/pgpkey
Re: Amanda 2.4.2 and Onstream ADR 50 Tape?
Henning, have you ever been able to actually *restore* files from amanda tapes using this device? Which is the firmware verison it has? See also my email on the list from half an hour ago. Greetings, Moritz
Re: amandad keeps dying for some unknown reason......
Dan Wilder wrote: This could be an inetd issue, if you have a whole lot of disklist entries pointing to the server in question. Rate limiting is a common inetd feature. The idea is that more than some number of requests per unit time means the same request is coming in repeatedly, and the server isn't satisfying it. As anybody who has ever tried to run even a moderatly busy SMTP server over inetd has discovered, this feature, while preventing machine meltdown due to overspawning a failing server, may also bring about server failures under slightly different circumstances. Of course this was not unexpected, and inetd makes allowances for this. See man inetd. At least on Linux. I'd expect similar allowance on Solaris, too. From man 5 inetd.conf, an entry like amanda dgram udp wait.100 amanda /usr/libexec/amandad amandad specifies that 100 server processes may be spawned in one minute. On Wed, Jan 02, 2002 at 12:18:01PM -0500, Don Potter wrote: I have Solaris 8 box using Amanda 2.4.2 (client). And when I run amcheck from the tape server I get the following errors on the console: Dec 31 09:54:18 oligo inetd[170]: [ID 858011 daemon.warning] /var/adm/amanda/libexec/amandad: Killed Dec 31 09:55:28 oligo inetd[170]: [ID 667328 daemon.error] amanda/udp server failing (looping), service terminated I thought it was an issue pertaining to the OS version only. But I have been able to use amanda on other 5.8 boxes. The only differance is that I used different GCC to compile the software. The failing box uses 3.0.2 and the working boxes utilize 2.8.1 of gcc (upgrading the compiler). Has anybody seen issues of this variety by chance. I'm not sure if this is even related to the gcc rev. Thanks for any advice. Don Potter -- - Dan Wilder [EMAIL PROTECTED] Technical Manager Editor SSC, Inc. P.O. Box 55549 Phone: 206-782-8808 Seattle, WA 98155-0549URL http://embedded.linuxjournal.com/ - This is a initial installation so there are only 3 total entries in the disklistI don't believe that there is an equivilant to increase a number of given server processes in Solaris as there is Linux by modifying the /etc/inetd.conf. I would assume that would be in the /etc/system, but it wouldn't be the first time that I'm wrong. I'm not sure on how to determine the max number of invocatiions of a given server process spawned by inetd. Does anybody else? Don
Re: Suspend amanda
Paul Bijnens wrote: BRINER Cedric wrote: Imagine that during the christmass vacation nobody stay in the company, so no more people are going to modify any files... Is there a way to tell amanda to suspend is work for 1 week..without stressing it when we restart.. First let me start by stating that it is not necessary. And some files will be modified: incoming email, several logfiles Just let amanda go on, and it will dump to the holdingdisk. When dumping to disk without tape amanda saves space by doing only incremental backups (unless you specify to reserve less than 100% for the incremental backups with the parameter 'reserve' in amanda.conf). So when you're off for a few days, amanda keeps doing the backups (mostly incremental) to disk, and when you come back, you can flush them to tape (amflush config), all to one tape if you like (and if it fits, otherwise amanda will ask for more tapes). Even with a small holdingdisk this is useful (mine is 4 GByte and I have to backup a total of 195 GByte). I have no idea on how to proceed, anyone, anyone I was thinking to mofify the dumpcyle by make it bigger of 1 week...and then after ?? But if you really, really want to temporarily shut down amanda, just comment out the crontab entry on your amandaserver. Or modify it to something like: 5 * * * 2-6 test -e ~amanda/DoNotBackup || amdump daily Yeah but the problem is that amanda has to schedule at least one full backup in a dumpcycle... So let's suppose it is @ 2weeks and I shut the system down for 1 weekthen amanda will try to push 2 times more of full backup in the next week $ )... I thought about making bigger the dumpcycle of n days if I want to stop amanda for n days...and slowly come back at my original value... and you can indicate the go/no-go with the presence of absence of a file named DoNotBackup in the amanda home directory. -- Paul Bijnens, Lant Tel +32 16 40.51.40 Interleuvenlaan 15 H, B-3001 Leuven, BELGIUM Fax +32 16 40.49.61 http://www.lant.com/ email: [EMAIL PROTECTED] briner
Problems with Amanda through a firewall with NAT
I'm hoping someone can give me some advice on setting up Amanda with a
firewall and Network Address Translation.
My amanda system backs up hosts both inside and outside the firewall.
The clients's inside backup fine. I've never been able to get the ones
outside to pass the amcheck DailySet1 -c check:
amanda@admin:~ amcheck DailySet1 -c
Amanda Backup Client Hosts Check
WARNING: external: selfcheck request timed out. Host down?
WARNING: www: selfcheck request timed out. Host down?
WARNING: real: selfcheck request timed out. Host down?
Client check: 8 hosts checked in 30.058 seconds, 3 problems found
(brought to you by Amanda 2.4.3b1)
amanda@admin:~
I compiled amanda, both on admin (inside the firewall tapeserver
host) and on www (outside the firewall amanda client) with this
configuration:
./configure --with-tcpportrange=10084,10100 --with-udpportrange=932,948
--with-user=amanda --with-group=disk
In my /home/amanda/.amandahosts file on admin, the tapeserver, I have:
www.jhuccp.org amanda
My /home/amanda/.amandahosts file on www is:
www:~ # cat /home/amanda/.amandahosts
162.129.225.189 amanda
www:~ #
162.129.225.189 is the IP address for the host admin. This host's
reverse lookup doesn't resolve to a domain name outside the firewall,
just an IP address.
I've run netcat on admin on ports 932/tcp and /udp and 10100/tcp and
/udp. Here's two samples of the output on each end. In the first, www
is sending on 932/tcp:
www:~ # netcat -v 162.129.225.189 932
162.129.225.189: inverse host lookup failed: Unknown host : No such
file or directory
(UNKNOWN) [162.129.225.189] 932 (?) open
ddd
punt!
www:~ #
admin:~ # netcat -v -l -p 932
listening on [any] 932 ...
connect to [172.16.2.7] from www.jhuccp.org [162.129.225.190] 35919
ddd
admin:~ #
Notice that NAT translates the IP address which www is sending to
(162.129.225.189) outside the firewall to 162.129.225.190, which is used
inside the firewall. I don't know why this is necessary. The guy
configuring the firewall assures me that it is. This then is resolved by
a DNS reverse lookup to www.jhuccp.org. The fact that the packets
('ddd') pass okay reassures me that it is working.
In this second example of using netcat, www is listening on port
10100/tcp:
admin:~ # netcat -v www 10100
www.jhuccp.org [162.129.225.190] 10100 (?) open
fff
punt!
admin:~ #
www:~ # netcat -v -l -p 10100
listening on [any] 10100 ...
162.129.225.189: inverse host lookup failed: Unknown host : No such
file or directory
connect to [162.129.225.190] from (UNKNOWN) [162.129.225.189] 41885
fff
www:~ #
Based on this, I think the firewall's passing the traffic and the NAT
is working properly.
Anyone have any further suggestions for things I can change or other
diagnostic methods I can use to fix this?
Thank you all very much for your time and thoughts. Have a happy and
safe New Year.
-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
OT: Old message zombies
Hi, Somehow old messages from December and January get replayed to the list. Please keep an eye on message dates before answering. Johannes Nieß Received: from internal.mail.telinco.net (internal.mail.telinco.net [212.1.128.4]) by surly.omniscient.com (8.11.6/8.11.6) with ESMTP id g1IAoWv413836 for [EMAIL PROTECTED]; Mon, 18 Feb 2002 05:50:33 -0500 (EST) Received: from root by internal.mail.telinco.net with local (Exim 3.22 #1) id 16clNF-0006jZ-00; Mon, 18 Feb 2002 10:50:21 + Received: from guiness.omniscient.com ([64.134.101.78]) by internal.mail.telinco.net with esmtp (Exim 3.22 #1) id 16LmnD-00088x-00 for [EMAIL PROTECTED]; Wed, 02 Jan 2002 14:54:59 + Received: from surly.omniscient.com (surly.omniscient.com [64.134.101.69]) by guiness.omniscient.com (8.12.1/8.12.1) with ESMTP id g02EPZsh015358; Wed, 2 Jan 2002 09:26:31 -0500 (EST)
Re: most efficient use of holding disk
Martin Oehler wrote: Chris Marble wrote: Martin Oehler wrote: I use amanda on a solaris 7 box with a DTL drive (20 GB) attached. My dumpcyle is 4 weeks with 20 runs per cycle. Because the size of one incremental backup is only between 2-4 GB I don't want to change the tape each day. You could crank your dumpcycle down to 3 (or whatever number would get Amanda to use most of your tape capacity). Hmmm, I didn't want to use a constant value because it can happen that there is a 8 GB or 10 GB incremental backup. Is there a way I can calculate the needed size on tape (approx.) before the backup process starts? madmin config balance will try and figure out how much needs to go on each tape in a dumpcycle. I'm suggesting that you lower dumpcycle so you might get a full backup of one partition every day and incrementals of the others. -- [EMAIL PROTECTED] - HMC UNIX Systems Manager My opinions are my own and probably don't represent anything anyway.
Re: gnutar-lists problem
Brandon Moro wrote: It seems to be expecting an entry in the gnutar-lists file, and didn't find it. Can someone give me a better explanation concerning what exactly the gnutar-lists do? (what function it serves?) See if those files get created once you've got the backups running. I may have touched files in those directories to quiet things down - don't remember. Amanda will populate the files. They seem to be what it uses to figure out what belongs on an incremental backup. I have the /use and the /export/home partitions set to be backed up as separate partitions (two lines in the disklist file). Why is the error for the /export/home backup listed in the /usr report? There was no entry in the reports last night for the /export/home. I assume it was not backed up. /-- host.local. /usr lev 0 STRANGE sendbackup: start [host.local.site.corp:/usr level 0] sendbackup: info BACKUP=/bin/gtar sendbackup: info RECOVER_CMD=/bin/gtar -f... - sendbackup: info end ? gtar: ./local/var/amanda/gnutar-lists/host.loca.site.corp_export_home_0.new: Warning: Cannot stat: No such file or directory | Total bytes written: 1148590080 (1.1GB, 602kB/s) sendbackup: size 1121670 sendbackup: end \ This was just a warning. You'd been running a backup on export/home which apparently died while this backup of /usr was happening. This report was on a file /usr/local/var/amanda/gnutar-lists/host.loca.site.corp_export_home_0.new -- [EMAIL PROTECTED] - HMC UNIX Systems Manager My opinions are my own and probably don't represent anything anyway.
Re: Merry Christmas and a happy New Year
We wish you all a Merry Christmas and a happy New Year Aykut Çakýl (Incoming Dept. Manager) ACTIVE TRAVEL AGENCY Lufthansa City Center Istanbul - Turkey Phone: + 90 - 216 - 349 55 90 Fax: + 90 - 216 - 349 55 94 Email: [EMAIL PROTECTED] Web: www.activeturkey.com Is this some sort of new virus? I have got this email about 10 times today... Seems to have been stuck/looped for seven weeks on internal.mail.telinco.net: Received: from [64.134.101.69] (helo=surly.omniscient.com) by mxng04.kundenserver.de with esmtp (Exim 3.22 #2) id 16cmtC-rL-00; Mon, 18 Feb 2002 13:27:26 +0100 Received: from internal.mail.telinco.net (internal.mail.telinco.net [212.1.128.4]) by surly.omniscient.com (8.11.6/8.11.6) with ESMTP id g1IAbNv417253 for [EMAIL PROTECTED]; Mon, 18 Feb 2002 05:37:36 -0500 (EST) Received: from root by internal.mail.telinco.net with local (Exim 3.22 #1) id 16clAh-0003ul-00 for [EMAIL PROTECTED]; Mon, 18 Feb 2002 10:37:23 + Received: from surly.omniscient.com ([64.134.101.69]) by internal.mail.telinco.net with esmtp (Exim 3.22 #1) id 16IZXC-tI-00 for [EMAIL PROTECTED]; Mon, 24 Dec 2001 18:09:10 + Received: from smtp2.doruk.net.tr (smtp2.doruk.net.tr [212.58.5.5]) by surly.omniscient.com (8.11.6/8.11.6) with ESMTP id fBOGo5N497468 for [EMAIL PROTECTED]; Mon, 24 Dec 2001 11:50:06 -0500 (EST) Received: from AYKUT ([195.174.64.47]) by smtp2.doruk.net.tr with Microsoft SMTPSVC(5.0.2195.2966); Mon, 24 Dec 2001 18:51:30 +0200 Reply-To: [EMAIL PROTECTED] From: AYKUT CAKIL [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Merry Christmas and a happy New Year Date: Mon, 24 Dec 2001 18:09:47 +0200 Organization: ACTIVE TOURISM INC.
Re: Merry Christmas and a happy New Year
Rebecca Pakish wrote: I am wondering the same thing...I only received it from the list, but anything with a Christmas subject in February pricks my sys admin ears. I can't find anything from my usual virus sources...if anyone knows anything I would appreciate the info. A lot of mails seem to have been stuck. Today, I got around 90 mails of amanda-users from Dec 24 2001 to Jan 3 2002. They are doubles to mails already received. It's always internal.mail.telinco.net in between. Maybe the box of [EMAIL PROTECTED] looped. Received: from [64.134.101.78] (helo=guiness.omniscient.com) by mxng00.kundenserver.de with esmtp (Exim 3.22 #2) id 16cm6W-0002c8-00 for [EMAIL PROTECTED]; Mon, 18 Feb 2002 12:37:08 +0100 Received: from surly.omniscient.com (surly.omniscient.com [64.134.101.69]) by guiness.omniscient.com (8.12.1/8.12.1) with ESMTP id g1IBVjmW013054; Mon, 18 Feb 2002 06:32:13 -0500 (EST) Received: (from root@localhost) by surly.omniscient.com (8.11.6/8.11.6) id g1IBVtj417539 for amanda.org.amanda-users-list; Mon, 18 Feb 2002 11:31:55 GMT Received: from internal.mail.telinco.net (internal.mail.telinco.net [212.1.128.4]) by surly.omniscient.com (8.11.6/8.11.6) with ESMTP id g1IArWv418616 for [EMAIL PROTECTED]; Mon, 18 Feb 2002 05:53:38 -0500 (EST) Received: from root by internal.mail.telinco.net with local (Exim 3.22 #1) id 16clPr-0007Jk-00 for [EMAIL PROTECTED]; Mon, 18 Feb 2002 10:53:04 + Received: from guiness.omniscient.com ([64.134.101.78]) by internal.mail.telinco.net with esmtp (Exim 3.22 #1) id 16MH6F-0008j6-00 for [EMAIL PROTECTED]; Thu, 03 Jan 2002 23:16:39 + Received: from surly.omniscient.com (surly.omniscient.com [64.134.101.69]) by guiness.omniscient.com (8.12.1/8.12.1) with ESMTP id g03MrMsh011090; Thu, 3 Jan 2002 17:53:59 -0500 (EST) Received: (from root@localhost) by surly.omniscient.com (8.11.6/8.11.6) id g03Mbo5520487 for amanda.org.amanda-users-list; Thu, 3 Jan 2002 22:37:50 GMT Received: from mail.databuilt.com (f12-1-3-00-0899.beready.att.net [63.241.179.71]) by surly.omniscient.com (8.11.6/8.11.6) with ESMTP id g03MblB377090 for [EMAIL PROTECTED]; Thu, 3 Jan 2002 17:37:48 -0500 (EST) Received: from dither.corp.databuilt.com (dyn.pool-1-129.r99.r100.scptvl.infoave.net [64.53.71.129]) by mail.databuilt.com (8.10.2/8.10.2) with ESMTP id g03Mbc203590 for [EMAIL PROTECTED]; Thu, 3 Jan 2002 17:37:38 -0500 Subject: Running programs during client execution? From: Mark Hazen [EMAIL PROTECTED] To: [EMAIL PROTECTED] Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/1.0.0.99+cvs.2001.12.14.08.57 (Preview Release) Date: 03 Jan 2002 17:37:38 -0500 Message-Id: [EMAIL PROTECTED]
Re: OT: Old message zombies
Somehow is [EMAIL PROTECTED] Perhaps the list manager can unzubscribe him until he has his problems sorted out. -Mitch On 18 Feb 2002, Johannes Niess wrote: Hi, Somehow old messages from December and January get replayed to the list. Please keep an eye on message dates before answering. Johannes Nieß Received: from internal.mail.telinco.net (internal.mail.telinco.net [212.1.128.4]) by surly.omniscient.com (8.11.6/8.11.6) with ESMTP id g1IAoWv413836 for [EMAIL PROTECTED]; Mon, 18 Feb 2002 05:50:33 -0500 (EST) Received: from root by internal.mail.telinco.net with local (Exim 3.22 #1) id 16clNF-0006jZ-00; Mon, 18 Feb 2002 10:50:21 + Received: from guiness.omniscient.com ([64.134.101.78]) by internal.mail.telinco.net with esmtp (Exim 3.22 #1) id 16LmnD-00088x-00 for [EMAIL PROTECTED]; Wed, 02 Jan 2002 14:54:59 + Received: from surly.omniscient.com (surly.omniscient.com [64.134.101.69]) by guiness.omniscient.com (8.12.1/8.12.1) with ESMTP id g02EPZsh015358; Wed, 2 Jan 2002 09:26:31 -0500 (EST)
Reg:Changing the tape sequence
Hi everyone I have a HP-DAT 24*6 tape drive attached to my backup server running on linux. I do partial backups on 5 tapes labelled as Archive - Mon to Arhive -Fri on weekdays and full backup on the sixth tape on weekends Archive-Wek. For some reasons the backup on the 5th tape failed. Now on monday when I am supposed to backup on Archive-Mon Iam still held up on Archive-Wek. Is there any way I can revert back to the normal sequence ie. Archive-Mon regards chandrasekar _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
Re: Merry Christmas and a happy New Year
On Mon, 18 Feb 2002, Lewis Watson wrote: Yup. Has been delivered here about six times, we scan for virus' at the server and its not seeing anything. Nothing at sarc.com at this time... Regardless of whether or not it's a virus can people PLEASE stop replying to the amanda-users-list address? The correct address to send mail to this list is [EMAIL PROTECTED] I do not know why these virus/spam emails get sent there, but when you reply please change the header. If you send them to amanda-users-list you bypass some majordomo aliases which insert useful headers. -- Brandon D. Valentine [EMAIL PROTECTED] Computer Geek, Center for Structural Biology This isn't rocket science -- but it _is_ computer science. - Terry Lambert on [EMAIL PROTECTED]
Hmm. Ok
- Original Message - From: Brandon D. Valentine [EMAIL PROTECTED] To: Lewis Watson [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Monday, February 18, 2002 3:11 PM Subject: Re: Merry Christmas and a happy New Year On Mon, 18 Feb 2002, Lewis Watson wrote: Yup. Has been delivered here about six times, we scan for virus' at the server and its not seeing anything. Nothing at sarc.com at this time... Regardless of whether or not it's a virus can people PLEASE stop replying to the amanda-users-list address? The correct address to send mail to this list is [EMAIL PROTECTED] I do not know why these virus/spam emails get sent there, but when you reply please change the header. If you send them to amanda-users-list you bypass some majordomo aliases which insert useful headers. -- Brandon D. Valentine [EMAIL PROTECTED] Computer Geek, Center for Structural Biology This isn't rocket science -- but it _is_ computer science. - Terry Lambert on [EMAIL PROTECTED] Hmm. Ok. The only reason I was responding here was because they came from within the list. Sorry to have inconvenienced you. Lewis Watson
amanda and gpg again
Hello, (I know this is not part of amanda's default behavior so if this is not ok for this list please let me know) I am having much trouble getting amanda to work with gpg. I am little confused and could use some pointers. I have re-compiled the client and server and installed the new binaries. I ran amdump and everything appeared to be working I saw the gtar process running, I saw the gpg process, I saw the gzip process running, I have a gpg.debug file in /tmp. The image appeared to write to tape correctly. The email output showed no signs of failure. Here is the issue. I can not restore from the image on tape no matter what I try. The error is: gzip: stdin: not in gzip format gpg: decrypt_message failed: eof ( I assume here that either the wrong data, or corrupted data made it to tape, other issues??) Also the /tmp/amanda/gpg.debug file is still on the disk after the backup completed. Here is the odd part. I copied the gpg.debug file to my backup server and manually ran: gpg -d --homedir=/var/backups/.gnupg/ -r [EMAIL PROTECTED] gpg.debug | tar tvfp - And it worked perfectly. So I guess my questions are: Why does this setup write to /tmp/amanda/gpg.debug? Why was this not written to tape? Why was /tmp/amand/gpg.debug not removed? What was written to tape? Thank you again for all the awesome assistance in advance. Andrew
Re: Hmm. Ok
On Mon, 18 Feb 2002, Lewis Watson wrote: Hmm. Ok. The only reason I was responding here was because they came from within the list. Sorry to have inconvenienced you. I don't think you understood me. It's perfectly okay to reply *here*, this is [EMAIL PROTECTED] If you will all go look back through your INBOX you'll find in the headers that the offending emails were To: [EMAIL PROTECTED]. Emails sent to that address bypass part of the majordomo resend mechanism. If you compare the headers between this message I'm sending you via the list and the spam message you'll see the difference. -- Brandon D. Valentine [EMAIL PROTECTED] Computer Geek, Center for Structural Biology This isn't rocket science -- but it _is_ computer science. - Terry Lambert on [EMAIL PROTECTED]
Re: [Amanda-users] Re: backups still failing.
John, have I lost your attention with this, are you too busy? Thanks. On Tue, Feb 12, 2002 at 02:14:03PM +1100, Jason Thomas wrote: On Mon, Feb 11, 2002 at 09:50:31PM -0500, John R. Jackson wrote: Could you try this again and make sure you remove the /tmp files first. Also, try it with bs=64k. Did you try the above (bs=64k, remove the /tmp files)? John, here it is: root@bast:~# mt -f /dev/scsi/host0/bus0/target15/lun0/mtn setblk 0 root@bast:~# mt -f /dev/scsi/host0/bus0/target15/lun0/mtn status SCSI 2 tape drive: File number=0, block number=0, partition=0. Tape block size 0 bytes. Density code 0x26 (DDS-4 or QIC-4GB). Soft error count since last status=0 General status bits on (4101): BOT ONLINE IM_REP_EN root@bast:~# mt -f /dev/scsi/host0/bus0/target15/lun0/mtn rewind root@bast:~# dd if=/dev/scsi/host0/bus0/target15/lun0/mtn bs=64k of=/tmp/first-record count=1 0+1 records in 0+1 records out root@bast:~# mt -f /dev/scsi/host0/bus0/target15/lun0/mtn rewind root@bast:~# dd if=/dev/scsi/host0/bus0/target15/lun0/mtn bs=64k of=/tmp/first-file 0+8 records in 0+8 records out root@bast:~# ls -la /tmp/first-* -rw-r--r--1 root root32768 Feb 12 14:12 /tmp/first-file -rw-r--r--1 root root 4096 Feb 12 14:11 /tmp/first-record root@bast:~# and also I've probably said this before but, Thanks for your help. ___ Amanda-users mailing list [EMAIL PROTECTED] http://mail.topic.com.au/cgi-bin/mailman/listinfo/amanda-users -- Jason Thomas Phone: +61 2 6257 7111 System Administrator - UID 0 Fax:+61 2 6257 7311 tSA Consulting Group Pty. Ltd. Mobile: 0418 29 66 81 1 Hall Street Lyneham ACT 2602 http://www.topic.com.au/
Re: [Amanda-users] Re: backups still failing.
John, have I lost your attention with this, are you too busy? Any point in trying to use 4k (I assume hardware) blocksize? My experience has shown DDS drives are best driven at hardware blocksize of 0 (variable) and Amanda writing with 32k blocks.
bad versions of tar, index files and restores
I ran across a machine using a bad version of tar (big numbers in the index files). That has been fixed, and a full backup is being forced tonight, but I'm wondering about backups on old tapes. I realize that I wouldn't be able to interactively use amrecover, but would a manual fsf and tar -x of a level 0 return a full backup of the directory, or is it all so much wasted tape? In other words, do corrupted indexes mean corrupted data or just partial incrementals? Just curious, Frank -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: [Amanda-users] Re: backups still failing.
On Tue, Feb 19, 2002 at 12:25:00AM +0100, Bernhard R. Erdmann wrote: John, have I lost your attention with this, are you too busy? Any point in trying to use 4k (I assume hardware) blocksize? My experience has shown DDS drives are best driven at hardware blocksize of 0 (variable) and Amanda writing with 32k blocks. well I had it at 0 initially, and struggled with failures reading back from the tape constantly. I changed it to 4096 and it seems to be a little more reliable. BUT, I still get errors. just less. I happy to use any block size that will work. why would I get more errors with DDS4 tapes compared to DDS3 tapes.
Amanda and IPv6
I was wondering if any of you had experience with Amanda on IPv6 machines. I am expermenting with IPv6 and on a RedHat 7.2 machines Amanda seems to break if I give the machine an IPv6 address. The same machine works when I remove the IPv6 address and only have an IPv4 address. I am able to backup an OpenBSD 3.0 machine that has multiple IPv6 addresses and IPv4 addresses. All the machines in question are using an IPv4 address to backup. As far as I am aware Amanda does not support IPv6. Any thoughts, comments, or suggestions? -Ian -- Ian Prowell gpg: http://www.prowell.org/~iprowell/public_key.txt They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety. - Benjamin Franklin, Historical Review of Pennsylvania, 1759.
Re: [Amanda-users] Re: backups still failing.
well I had it at 0 initially, and struggled with failures reading back from the tape constantly. I changed it to 4096 and it seems to be a little more reliable. BUT, I still get errors. just less. I happy to use any block size that will work. why would I get more errors with DDS4 tapes compared to DDS3 tapes. You might have faulty hardware, there could be anything from SCSI cabling to the drive, the head or the tape.
Re: disk offline ?
Hi! Hauke Fath wrote: Rainer Fuegenstein [EMAIL PROTECTED] wrote: After adding a new old server named fav to amanda, I keep getting the following message: FAILURE AND STRANGE DUMP SUMMARY: fav/home2 lev 0 FAILED [disk /home2 offline on fav?] It doesn't matter if the disk is specified by device file or mount directory: favc1t4d0s6tar-srv-low# /home2 fav/home2 tar-srv-low# /home2 Looks familiar... Try to supply the absolute path for the obstinate drive. If that helps, we're two... I got the same problem with one of my boxes. Are there known problems with amanda and ReiserFS? My log entries messages look like: got result for host pc20 disk /: 0 - -1K, -1 - -1K, -1 - -1K 0: pc20 / planner: FAILED pc20 / 0 [disk / offline on pc20?] Seems like amanda can't get the size of the disk. Any suggestions? Should I use tar unstead of dump? CU and thanks Martin
Re: bad versions of tar, index files and restores
I realize that I wouldn't be able to interactively use amrecover, but would a manual fsf and tar -x of a level 0 return a full backup of the directory, or is it all so much wasted tape? In other words, do corrupted indexes mean corrupted data or just partial incrementals? Just the incremental index is corrupted but no data.
Re: [Amanda-users] Re: backups still failing.
On Tue, Feb 19, 2002 at 07:57:39AM +0100, Bernhard R. Erdmann wrote: well I had it at 0 initially, and struggled with failures reading back from the tape constantly. I changed it to 4096 and it seems to be a little more reliable. BUT, I still get errors. just less. I happy to use any block size that will work. why would I get more errors with DDS4 tapes compared to DDS3 tapes. You might have faulty hardware, there could be anything from SCSI cabling to the drive, the head or the tape. I've been through all that. this is another machine with a different tape drive and different tapes and different scsi cables. It really has to be something I'm doing otherwise we'd see more of this. the machine is used all day long and serves home directorys for about 35 users, so my assumption is that the scsi card and cable are probably okay, and the other hardware is probably fine too. as I also said initially, I don't think amanda is at fault, but was hoping someone here would know what I was talking about and could help. Thanks
