Re: Does Amanda need shell?
Previously I wrote: > Amanda server running 2.4.2p1 on FreeBSD 4.3 > Amanda client running 2.4.2p2 on Linux 2.4.12 (Slackware 8) > > In an attempt to tighten up security a bit I changed the amanda > user's shell from /bin/bash to /nonexistent on the Slackware > machine. Ran su amanda -c "amcheck -c MYCONFIG" on FreeBSD machine, > it reported that everything was fine. But when the actual backup > process ran, I got the report indicating that connection to > Slackware machine cannot be established. Additional bit of information: even after reverting the shell to /bin/bash, the backup still fails. I suspect it has something to do with my colleague modifying IPCHAINS configuration on the Slackware machine. It's strange, though, that amcheck doesn't see any problems. -- Toomas Aas | [EMAIL PROTECTED] | http://www.raad.tartu.ee/~toomas/ * How much net work could a network work, if a network could net work?
gnutar/amanda croaks and evilly corrupts .Z compressed file
we are having a problem with large( +2 gig) .Z compressed tarballs (made w/ solaris compress utility) getting truncated/corrupted when they are backed up w/ amanda (using gnutar). Conveniently found this out when we attempted a restore. What happens is that if one of these large compressed files is encountered by the amanda backup, it silently stops backing up at that point, and if the file is restored, it is a truncated/corrupted version of the original file. gnutar has no problem backing up/restoring larger (3.9 g) tarballs which are not compressed. we will attempt a workaround by using a new version of gzip, but I am curious as to whether this has been seen before, and whether it is a gnutar bug, and if so , where I shoud report it. I am currently running a test of gnutar w/o amanda on this file, but if it works properly I am left scratching my head as to whether the problem is with amanda or gnutar. details follow: -- amanda version Amanda-2.4.2p2 gnutar version 1.13.19 OS: solaris 2.6 /sparc I have been testing on holding disk w/o using tape drive at all. sample holding disk file : # head foo.someuniversity.edu._raid.1 AMANDA: FILE 20011025 foo.someuniversity.edu /raid lev 1 comp N program /usr/local/bin/gnutar To restore, position tape at start of file and run: dd if= bs=32k skip=1 | /usr/local/bin/gnutar -f... - -- "restore" file off of holding disk: # amrestore foo.someuniversity.edu._raid.1 amrestore: 0: restoring foo.someuniversity.edu._raid.20011025.1 # ls -rw--- 1 amanda users178585600 Oct 25 01:35 foo.someuniversity.edu._raid.1 -rw-r- 1 user other178552832 Oct 25 11:19 foo.someuniversity.edu._raid.20011025.1 # gnutar -tvf foo.someuniversity.edu._raid.20011025.1 > tableofcont gnutar: Unexpected EOF in archive gnutar: Error is not recoverable: exiting now Note that the .Z file is the last file listed, even tho there are many more to be backed up... obviously gnutar/amanda choked. # tail -3 tableofcont drwxr-xr-x www/nobody 29 2001-05-11 14:40:53 ./tmp/etc/WebEvent/cals/cal7/ -rw-r--r-- user/other0 2001-10-25 00:03:48 ./foo -rw-r--r-- user/other 200973 2001-10-24 22:52:24 ./backup/10-24-2001.tar.Z -- # gnutar -xvpf foo.someuniversity.edu._raid.20011025.1 ./backup/10-24-2001.tar.Z ./backup/10-24-2001.tar.Z gnutar: Unexpected EOF in archive gnutar: Unexpected EOF in archive gnutar: Error is not recoverable: exiting now # cd backup # ls total 344100 drwxr-xr-x 2 user other512 Oct 25 11:38 ./ drwx-- 3 amanda users512 Oct 25 11:38 ../ -rw-r--r-- 1 user other176077824 Oct 25 11:39 10-24-2001.tar.Z What the #%^#$%&*() is this file note much smaller size than the original, # file 10-24-2001.tar.Z 10-24-2001.tar.Z: USTAR tar archive (???) (but this was a .Z compressed file previously ? and just for grins, lets try to extract...) # # tar -tvf 10-24-2001.tar.Z -rw-r--r-- 0/1 15704064 Oct 24 23:45 2001 07365732347/./backup/test.tar -rw--- 1311/100 4715 Oct 24 12:41 2001 07365613346/./export/systems/deny ce/.history -rw--- 101/100 925207 Oct 24 15:43 2001 07321545437/./export/systems/kaa/mail/foo tar: directory checksum error curiouser and curiouser... none of these files were in the original tar.Z file, in fact, looking at the numbers on the front, these files were backed up by gnu tar, not by the solaris tar which created the orig file. --- amadmin DailySet info foo /raid Current info for foo.someuniversity.edu /raid: Stats: dump rates (kps), Full: 4142.0, 3329.0, 3367.0 Incremental: 3229.0, 3999.0, 2880.0 compressed size, Full: -100.0%,-100.0%,-100.0% Incremental: -100.0%,-100.0%,-100.0% Dumps: lev datestmp tape file origK compK secs 0 20011019 DailySet10 9 5103000 5103008 1232 1 20011025 0 174350 174368 54 --- amadmin DailySet version build: VERSION="Amanda-2.4.2p2" BUILT_DATE="Fri Jun 29 17:13:55 MST 2001" BUILT_MACH="SunOS foo.someuniversity.edu 5.6 Generic_105181-11 sun4u sparc SUNW,Ultra-5_10" CC="gcc" paths: bindir="/usr/local/bin" sbindir="/usr/local/sbin" libexecdir="/usr/local/libexec" mandir="/usr/local/man" AMANDA_TMPDIR="/tmp/amanda" AMANDA_DBGDIR="/tmp/amanda" CONFIG_DIR="/usr/local/etc/amanda" DEV_PREFIX="/dev/dsk/" RDEV_PREFIX="/dev/rdsk/" DUMP="/usr/sbin/ufsdump" RESTORE="/usr/sbin/ufsrestore" GNUTAR="/usr/local/bin/gnutar" COMPRESS_PATH="/usr/local/bin/gzip" UNCOMPRESS_PATH="/usr/local/bin/gzip" MAILER="/usr/ucb/Mail" listed_incr_dir="/usr/local/var/amanda/gnutar-lists" defs: DEFAULT
amanda/gnutar croaks/corrupts big .Z compressed file
we are having a problem with large( +2 gig) .Z compressed tarballs (made w/ solaris compress utility) getting truncated/corrupted when they are backed up w/ amanda (using gnutar). Conveniently found this out when we attempted a restore. What happens is that if one of these large compressed files is encountered by the amanda backup, it silently stops backing up anything on that filesystem at that point, and if the file is restored, it is a truncated/corrupted version of the original file. gnutar has no problem backing up/restoring larger (3.9 g) tarballs which are not compressed. we will attempt a workaround by using a new version of gzip, but I am curious as to whether this has been seen before, and whether it is a gnutar bug, and if so , where I shoud report it. I am currently running a test of gnutar w/o amanda on this file, but if it works properly I am left scratching my head as to whether the problem is with amanda or gnutar. details follow: -- amanda version Amanda-2.4.2p2 gnutar version 1.13.19 OS: solaris 2.6 /sparc I have been testing on holding disk w/o using tape drive at all. sample holding disk file : # head foo.someuniversity.edu._raid.1 AMANDA: FILE 20011025 foo.someuniversity.edu /raid lev 1 comp N program /usr/local/bin/gnutar To restore, position tape at start of file and run: dd if= bs=32k skip=1 | /usr/local/bin/gnutar -f... - -- "restore" file off of holding disk: # amrestore foo.someuniversity.edu._raid.1 amrestore: 0: restoring foo.someuniversity.edu._raid.20011025.1 # ls -rw--- 1 amanda users178585600 Oct 25 01:35 foo.someuniversity.edu._raid.1 -rw-r- 1 user other178552832 Oct 25 11:19 foo.someuniversity.edu._raid.20011025.1 # gnutar -tvf foo.someuniversity.edu._raid.20011025.1 > tableofcont gnutar: Unexpected EOF in archive gnutar: Error is not recoverable: exiting now Note below that the .Z file is the last file listed, even tho there are many more to be backed up... obviously gnutar/amanda choked. # tail -3 tableofcont drwxr-xr-x www/nobody 29 2001-05-11 14:40:53 ./tmp/etc/WebEvent/cals/cal7/ -rw-r--r-- user/other0 2001-10-25 00:03:48 ./foo -rw-r--r-- user/other 200973 2001-10-24 22:52:24 ./backup/10-24-2001.tar.Z -- # gnutar -xvpf foo.someuniversity.edu._raid.20011025.1 ./backup/10-24-2001.tar.Z ./backup/10-24-2001.tar.Z gnutar: Unexpected EOF in archive gnutar: Unexpected EOF in archive gnutar: Error is not recoverable: exiting now # cd backup # ls total 344100 drwxr-xr-x 2 user other512 Oct 25 11:38 ./ drwx-- 3 amanda users512 Oct 25 11:38 ../ -rw-r--r-- 1 user other176077824 Oct 25 11:39 10-24-2001.tar.Z What the #%^#$%&*() is this file note much smaller size than the original, # file 10-24-2001.tar.Z 10-24-2001.tar.Z: USTAR tar archive (???) (but this was a .Z compressed file previously ? and just for grins, lets try to extract...) # # tar -tvf 10-24-2001.tar.Z -rw-r--r-- 0/1 15704064 Oct 24 23:45 2001 07365732347/./backup/test.tar -rw--- 1311/100 4715 Oct 24 12:41 2001 07365613346/./export/systems/deny ce/.history -rw--- 101/100 925207 Oct 24 15:43 2001 07321545437/./export/systems/kaa/mail/foo tar: directory checksum error curiouser and curiouser... none of these files were in the original tar.Z file, in fact, looking at the numbers on the front, these files were backed up by gnu tar, not by the solaris tar which created the orig file. they are other files off the same filesystem . --- amadmin DailySet info foo /raid Current info for foo.someuniversity.edu /raid: Stats: dump rates (kps), Full: 4142.0, 3329.0, 3367.0 Incremental: 3229.0, 3999.0, 2880.0 compressed size, Full: -100.0%,-100.0%,-100.0% Incremental: -100.0%,-100.0%,-100.0% Dumps: lev datestmp tape file origK compK secs 0 20011019 DailySet10 9 5103000 5103008 1232 1 20011025 0 174350 174368 54 --- amadmin DailySet version build: VERSION="Amanda-2.4.2p2" BUILT_DATE="Fri Jun 29 17:13:55 MST 2001" BUILT_MACH="SunOS foo.someuniversity.edu 5.6 Generic_105181-11 sun4u sparc SUNW,Ultra-5_10" CC="gcc" paths: bindir="/usr/local/bin" sbindir="/usr/local/sbin" libexecdir="/usr/local/libexec" mandir="/usr/local/man" AMANDA_TMPDIR="/tmp/amanda" AMANDA_DBGDIR="/tmp/amanda" CONFIG_DIR="/usr/local/etc/amanda" DEV_PREFIX="/dev/dsk/" RDEV_PREFIX="/dev/rdsk/" DUMP="/usr/sbin/ufsdump" RESTORE="/usr/sbin/ufsrestore" GNUTAR="/usr/local/bin/gnutar" COMPRESS_PATH="/usr/local/bin/gzip" UNCOMPRESS_PATH="/usr/local/bin/gzip" MAILER="/us
(no subject)
subscribe
Re: restoring a particular file
On Thu, Oct 25, 2001 at 11:00:43AM +0300, Hery Zo RAKOTONDRAMANANA wrote: > Hi all, > > I'm a newbie on using amanda. > I'm using amanda-2.2-p1-12 on debian potato systems. I'va already set up > amanda and Amdump seems working (reports seems good). > I'm doing backups on a HP DAT SureStore. > > Now I want to test restoring from backups I've done and I'm a little bit > confused about options I have to give to amrestore if I want to restore > a particular file. > For example, let's say my configuration name is "Testconf" > My cartridges are labeled TestConf01, TestConf02, ... > Can anyone tell me the options I have to give amrestore (or amrecover?) > if I want to restore a file called /etc/test.txt which has been backep > up from host "seine" from filesystem "/etc"? > > Is this restore going to replace my actual /etc/test.txt? If so, how can > I tell amrestore (or amrecover ?) to restore it in /tmp so that I can > copy it manually if needed. > amrestore gives you only the image from the tape. You need to pipe it through your restore program: cd /tmp amrestore /dev/nst0 seine /etc | tar xvpSf - ./etc/test.txt See http://www.backupcentral.com/amanda-23.html -- Alles Gute / best wishes Dietmar GoldbeckE-Mail: [EMAIL PROTECTED] Reporter (to Mahatma Gandhi): Mr Gandhi, what do you think of Western Civilization? Gandhi: I think it would be a good idea.
Re: More than one page worth of dumps on report
Stan Brown wrote: > > I'm backing up 99 filesystems. I am using one of the postscript forms > (forget which one) to print out a report at the end of the run. Clearly 99 > won't fit in one page. I'm using example/3hole.ps and my 81 filesystems fit on 2 sides of a single piece of paper. I don't think I've modified the file from what John Jackson wrote several years ago. It's easy enough to shrink fonts to fit more onto a page (the postscript file's quite readable). -- [EMAIL PROTECTED] - HMC UNIX Systems Manager My opinions are my own and probably don't represent anything anyway.
Re: [Amanda-users] Please Help! Problems with amverify and amrecover
I've had/have this exact problem, I'm at the end of my rope now. from what I understand alot of the problems have to do with block sizes but that didn't help me none. if I try and dd from the drive I get and "could not allocate memory error" I can dump fine and now I can even amverify, but its all just luck I don't know why it just started working. I have tried two different drives in two differenet machines and get the same problems. It's just f%@ked. I'm about to install windows! On Thu, Oct 25, 2001 at 11:17:04AM -0700, Michael Sobik wrote: > I posted this earlier, but I have yet more information. It seems that I > cannot manually recover the dump images from tape like I previously posted. > I can restore some of them, the smaller ones. If I try something like: > > dd if=/dev/nst0 of=/dev/null bs=32k skip=1 > > the drive reads for a couple of seconds, then just goes back to ready > status. If I look at the process list I see dd having status D (I think > that's waiting for I/O). > > I thought it must be a problem with my SCSI adaptor (Tekram DC315u) and/or > drive, but I can dd large mp3 files to and from the tape with compression > on/off without problems. The drive is a cs1553 and I'm using the > SURESTORE-12000E tapetype. Does anyone have any idea where I can start > looking for the problem? BTW the dumps all complete fine, it seems that > reading them back from tape is the problem. Thanks a lot! PGP signature
Does Amanda need shell?
Hello! Situation: Amanda server running 2.4.2p1 on FreeBSD 4.3 Amanda client running 2.4.2p2 on Linux 2.4.12 (Slackware 8) In an attempt to tighten up security a bit I changed the amanda user's shell from /bin/bash to /nonexistent on the Slackware machine. Ran su amanda -c "amcheck -c MYCONFIG" on FreeBSD machine, it reported that everything was fine. But when the actual backup process ran, I got the report indicating that connection to Slackware machine cannot be established. I was on the site at the time backup ran and I am sure that the machine was running. Now I changed amanda's shell back to /bin/bash and ran amdump manually. After couple of hours it should be finished. Does the amanda user really need shell access to work? -- Toomas Aas | [EMAIL PROTECTED] | http://www.raad.tartu.ee/~toomas/ * Windws is ine for bckgroun comunicaions - Bll Gats, 192
ip not in list (fwd) GOT IT!
Please disregard. I figured it out. Thanks anyways. Drew -- Forwarded message -- Date: Thu, 25 Oct 2001 15:39:29 -0400 (EDT) From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: ip not in list Hello, I have question that is probably really easy. I am receiving the error (i have changed the hostname): ERROR: hostname.net: [ip address 192.168.254.244 is not in the ip list for hostname.net] The host in question has two ips that it round robins between. This is necessary and can not change. They are 192.168.254.244 and 192.168.253.244. For some odd reason if the client received the .254.244 ip as the servers ip it returns the above error. Forward and reverse DNS for this IP work. I have both ips in the /etc/hosts on the client, and the client is setup to check hosts then dns. TIA. Andrew
ip not in list
Hello, I have question that is probably really easy. I am receiving the error (i have changed the hostname): ERROR: hostname.net: [ip address 192.168.254.244 is not in the ip list for hostname.net] The host in question has two ips that it round robins between. This is necessary and can not change. They are 192.168.254.244 and 192.168.253.244. For some odd reason if the client received the .254.244 ip as the servers ip it returns the above error. Forward and reverse DNS for this IP work. I have both ips in the /etc/hosts on the client, and the client is setup to check hosts then dns. TIA. Andrew
Re: OK, what stupid mistake am I making?
On Thu Oct 25 14:54:38 2001 Bernhard R. Erdmann wrote... > >Stan Brown wrote: >> >> I'm in the process of moving my Amanda server from a HP-UX machine to a >> Linux one. The new machines name is debian. >> >> I'm having problems with the tar exclude feature on the new tapejost >> itself. Heres the info > > >please post your exclude list > > >> /usr/local/lib/gnutar_exclude_list itself >> --- >> >> ./net >> ./dev/gpmctl >> ./dev/log >> ./home/oracle/9.01/software/app/oracle/oradata/debian/control02.ctl >> ./home/oracle/9.01/software/app/oracle/oradata/debian/redo02.log >> ./home/oracle/9.01/software/app/oracle/oradata/debian/control01.ctl >> ./home/oracle/9.01/software/app/oracle/product/release/oradata/debian/undotbs01.dbf >> ./tmp/.ICE-unix >> ./tmp/.X11-unix >> ./var/run/postgresql/.s\* >> ./var/run/sendmail/smcontrol >> ./var/tmp/.oracle/s\* >> ./tmp/.sawfish-stan >> ./tmp/orbit-stan >> ./tmp/ssh\* >> -- Stan Brown [EMAIL PROTECTED]843-745-3154 Charleston SC. -- Windows 98: n. useless extension to a minor patch release for 32-bit extensions and a graphical shell for a 16-bit patch to an 8-bit operating system originally coded for a 4-bit microprocessor, written by a 2-bit company that can't stand for 1 bit of competition. - (c) 2000 Stan Brown. Redistribution via the Microsoft Network is prohibited.
Re: AMANDA WEBSITE ???
On Thu, 25 Oct 2001, Bernhard R. Erdmann wrote: > > We don't need to do backups. We have RAID. :-; > > Yeah, we've RAID - guess how many people have been bitten by RAID and > having no backup... ;-) That was my point. But I typed in a hurry and messed up the winkie emoticon. -Mitch
Re: OK, what stupid mistake am I making?
Stan Brown wrote:
>
> I'm in the process of moving my Amanda server from a HP-UX machine to a
> Linux one. The new machines name is debian.
>
> I'm having problems with the tar exclude feature on the new tapejost
> itself. Heres the info
please post your exclude list
>
> FAILURE AND STRANGE DUMP SUMMARY:
> debian hde4 lev 0 STRANGE
>
> FAILED AND STRANGE DUMP DETAILS:
>
> /-- debian hde4 lev 0 STRANGE
> sendbackup: start [debian:hde4 level 0]
> sendbackup: info BACKUP=/usr/local/bin/tar
> sendbackup: info RECOVER_CMD=/bin/gzip -dc |/usr/local/bin/tar -f... -
> sendbackup: info COMPRESS_SUFFIX=.gz
> sendbackup: info end
> ? gtar: ./home/oracle/9.01/software/app/oracle/oradata/debian/control03.ctl: file
>changed as we read it
> | gtar: ./tmp/ssh-XXFiBGDE/agent.9980: socket ignored
> ? gtar: ./usr/local/amanda/adm/DailyDump/index/cems/_/20011024_1.gz.tmp: Warning:
>Cannot stat: No such file or directory
> ? gtar: ./usr/local/amanda/adm/DailyDump/index/cogenal/ad0s1f/20011024_1.gz.tmp:
>Warning: Cannot stat: No such file or directory
tar is just whining about files changing during the backup including the
amanda index files itself
> ? gtar: ./usr/local/amanda/adm/DailyDump/index/cogenwp/c0t3d0s7/20011024_0.gz.tmp:
>Warning: Cannot stat: No such file or directory
> ? gtar: ./usr/local/amanda/adm/DailyDump/index/phse1/c0t0d0/20011024_1.gz.tmp:
>Warning: Cannot stat: No such file or directory
> ? gtar: ./usr/local/amanda/adm/DailyDump/index/phse1/c0t1d0/20011024_1.gz.tmp:
>Warning: Cannot stat: No such file or directory
> ? gtar:
>./usr/local/amanda/adm/DailyDump/index/stripper/_dev_md_dsk_d5/20011024_1.gz.tmp:
>Warning: Cannot stat: No such file or directory
> ? gtar: ./usr/local/amanda/adm/DailyDump/index/stripperal/ad0s1f/20011024_1.gz.tmp:
>Warning: Cannot stat: No such file or directory
> ? gtar:
>./usr/local/amanda/adm/DailyDump/index/waterap/_dev_md_dsk_d5/20011024_1.gz.tmp:
>Warning: Cannot stat: No such file or directory
> ? gtar: ./usr/local/amanda/adm/DailyDump/index/waterwp/c0t3d0s6/20011024_0.gz.tmp:
>Warning: Cannot stat: No such file or directory
> | gtar: ./var/run/postgresql/.s.PGSQL.5432: socket ignored
> | gtar: ./var/tmp/.oracle/s#406.1: socket ignored
> | gtar: ./var/tmp/.oracle/sEXTPROC: socket ignored
> | Total bytes written: 8280053760 (7.7GB, 379kB/s)
> sendbackup: size 8085990
> sendbackup: end
> \
>
> From disklist
> ---
> debian hde4 comp-user-tar 1 local
> debian hde1 comp-user-tar 1 local
> debian hdf1 holding-disk-tar 2 local
> debian hdg1 nocomp-user 3 local # Compressing compressed data makes it
> # larger
>
> From amanda.conf
> --
> define dumptype user-tar {
> root-tar
> comment "user partitions dumped with tar"
> priority medium
> }
>
> define dumptype comp-user-tar {
> user-tar
> exclude list "/usr/local/lib/gnutar_exclude_list"
> compress client fast
> }
>
> ls -l of /usr/local/lib/gnutar_exclude_list
>
> -rw-r--r--1 amanda staff 472 Oct 24 07:52
>/usr/local/lib/gnutar_exclude_list
>
> /usr/local/lib/gnutar_exclude_list itself
> ---
>
> ./net
> ./dev/gpmctl
> ./dev/log
> ./home/oracle/9.01/software/app/oracle/oradata/debian/control02.ctl
> ./home/oracle/9.01/software/app/oracle/oradata/debian/redo02.log
> ./home/oracle/9.01/software/app/oracle/oradata/debian/control01.ctl
> ./home/oracle/9.01/software/app/oracle/product/release/oradata/debian/undotbs01.dbf
> ./tmp/.ICE-unix
> ./tmp/.X11-unix
> ./var/run/postgresql/.s\*
> ./var/run/sendmail/smcontrol
> ./var/tmp/.oracle/s\*
> ./tmp/.sawfish-stan
> ./tmp/orbit-stan
> ./tmp/ssh\*
>
> Now clearly the files I wan't to exclude, are not being excluded! Also
> what's with the Amanda files themselves, that it's complaining about?
>
> The holding disk is /dev/hdf1, so that should not be related to the
> problems with this disk.
>
> --
> Stan Brown [EMAIL PROTECTED]843-745-3154
> Charleston SC.
> --
> Windows 98: n.
> useless extension to a minor patch release for 32-bit extensions and
> a graphical shell for a 16-bit patch to an 8-bit operating system
> originally coded for a 4-bit microprocessor, written by a 2-bit
> company that can't stand for 1 bit of competition.
> -
> (c) 2000 Stan Brown. Redistribution via the Microsoft Network is prohibited.
Re: AMANDA WEBSITE ???
Mitch Collinsworth wrote: [...] > We don't need to do backups. We have RAID. :-; Yeah, we've RAID - guess how many people have been bitten by RAID and having no backup... ;-)
Please Help! Problems with amverify and amrecover
I posted this earlier, but I have yet more information. It seems that I cannot manually recover the dump images from tape like I previously posted. I can restore some of them, the smaller ones. If I try something like: dd if=/dev/nst0 of=/dev/null bs=32k skip=1 the drive reads for a couple of seconds, then just goes back to ready status. If I look at the process list I see dd having status D (I think that's waiting for I/O). I thought it must be a problem with my SCSI adaptor (Tekram DC315u) and/or drive, but I can dd large mp3 files to and from the tape with compression on/off without problems. The drive is a cs1553 and I'm using the SURESTORE-12000E tapetype. Does anyone have any idea where I can start looking for the problem? BTW the dumps all complete fine, it seems that reading them back from tape is the problem. Thanks a lot! Mike - Original Message - From: "Michael Sobik" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, October 24, 2001 7:45 AM Subject: RE: Problems with amverify and amrecover - more info > If I try: > > amrestore -p /dev/ no-such-host > /dev/null > > amrestore correctly lists all the dump images on the tape. However, if I > try and restore with: > > amrestore -p /dev/ > /dev/null > > I get: > > amrestore: 3: restoring realhostname.diskimage.0 > > the console seems to hang and NO lights flash on the drive, it just sits > there with Ready status. Once again, I can get the image with mt, dd, and > tar. > > Mike > - Original Message - > From: "Michael Sobik" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Wednesday, October 24, 2001 6:25 AM > Subject: Problems with amverify and amrecover > > > > All, > > > > Thanks to the help of this list, I have just recently configured Amanda > and > > run my first backups. However, I'm experiencing problems with amverify > and > > amrecover. The morning after the first backups ran, I tried to run > amverify > > on the first tape of the run. Here's the report I got back from amverify > > (ran for at least an hour): > > > > Tapes: linuxman11 > > Errors found: > > linuxman11 (linuxman._mnt_share_Angela.20011023.0): > > amrestore: 0: skipping start of tape: date 20011023 label linuxman11 > > amrestore: 1: restoring linuxman._mnt_share_Angela.20011023.0 > > amrestore: read error: Input/output error > > /bin/tar: Unexpected EOF in archive > > /bin/tar: Error is not recoverable: exiting now > > 64+0 records in > > 64+0 records out > > linuxman11 (): > > amrestore: error reading file header: Input/output error > > ** No header > > 0+0 records in > > 0+0 records out > > linuxman11 (): > > amrestore: error reading file header: Input/output error > > ** No header > > 0+0 records in > > 0+0 records out > > linuxman11 (): > > amrestore: error reading file header: Input/output error > > ** No header > > 0+0 records in > > 0+0 records out > > linuxman11 (): > > amrestore: error reading file header: Input/output error > > ** No header > > 0+0 records in > > 0+0 records out > > linuxman11 (): > > amrestore: error reading file header: Input/output error > > ** No header > > 0+0 records in > > 0+0 records out > > amtape: could not load slot 2: Unloading Data Transfer Element into > Storage > > Element 1...mtx: Request Sense: Long Report=yes > > amtape: could not load slot 2: Unloading Data Transfer Element into > Storage > > Element 1...mtx: Request Sense: Long Report=yes > > > > amverify linuxman > > Tue Oct 23 17:34:44 MST 2001 > > > > Loading 1 slot... > > Using device /dev/nst0 > > Volume linuxman11, Date 20011023 > > ** Error detected (linuxman._mnt_share_Angela.20011023.0) > > amrestore: 0: skipping start of tape: date 20011023 label linuxman11 > > amrestore: 1: restoring linuxman._mnt_share_Angela.20011023.0 > > amrestore: read error: Input/output error > > /bin/tar: Unexpected EOF in archive > > /bin/tar: Error is not recoverable: exiting now > > 64+0 records in > > 64+0 records out > > ** Error detected () > > amrestore: error reading file header: Input/output error > > ** No header > > 0+0 records in > > 0+0 records out > > ** Error detected () > > amrestore: error reading file header: Input/output error > > ** No header > > 0+0 records in > > 0+0 records out > > ** Error detected () > > amrestore: error reading file header: Input/output error > > ** No header > > 0+0 records in > > 0+0 records out > > ** Error detected () > > amrestore: error reading file header: Input/output error > > ** No header > > 0+0 records in > > 0+0 records out > > ** Error detected () > > amrestore: error reading file header: Input/output error > > ** No header > > 0+0 records in > > 0+0 records out > > Too many errors. > > Loading next slot... > > ** Error loading slot next > > amtape: could not load slot 2: Unloading Data Transfer Element into > Storage > > Element 1...mtx: Request Sense: Long Report=yes > > Advancing past the last tape... > > ** Error advancing after last slot > > amtape: could not load slot 2: U
Re: client setup on RH 7.1?
In message <[EMAIL PROTECTED]>, "Michael Sobik" writes: > Sorry, > > I meant .amandahosts not hostauth. I know that in my file I have an entries > like this: > > localhost amanda > localhost@localdomain amanda > host amanda > host@domain amanda You mean: localhost.localdomain amanda host.domain amanda Regardless, I did say in my first message and my followup to your reply that I had a .amandahosts file on my Linux client machine. The fix was this: On the RH7.1 client machine, it was not correct to have the line "serverhost.domain amanda". I needed the line "serverhost amanda". On my HP clients, it was sufficient to have the line "serverhost.domain amanda" in the .amandahosts file. The reason this might be is that my Linux boxes do NOT have FQDNs as their hostname, which seems to be the RH default. I set the domain name in /etc/resolv.conf only. Setting the machine name with the FQDN is ugly. Cheers, --Dave Chin > - Original Message - > From: "David Chin" <[EMAIL PROTECTED]> > To: "Michael Sobik" <[EMAIL PROTECTED]> > Cc: <[EMAIL PROTECTED]> > Sent: Thursday, October 25, 2001 9:43 AM > Subject: Re: client setup on RH 7.1? > > > > > > In message <[EMAIL PROTECTED]>, "Michael Sobik" > writes: > > > You need to edit /var/lib/amanda/.amandahostauth to allow access as > amanda > > > from fooserver > > > > What should it contain? I already had ~amanda/.amandahosts, which > contained: > > > >fooserver.f.q.d.n amanda > >
Re: client setup on RH 7.1?
In message <[EMAIL PROTECTED]>, "Michael Sobik" writes: > You need to edit /var/lib/amanda/.amandahostauth to allow access as amanda > from fooserver What should it contain? I already had ~amanda/.amandahosts, which contained: fooserver.f.q.d.n amanda And then I sym-linked it to ~amanda/.amandahostauth I still get the same error: ERROR: fooclient: [access as amanda not allowed from amanda@fooserver] \ amandahostsauth failed I downloaded the src, and the docs only mention the .amandahosts file, which was the method which worked on the HP-UX clients. --Dave Chin [EMAIL PROTECTED]
Re: AMANDA WEBSITE ???
On Thursday 25 October 2001 10:12 am, Rebecca Pakish wrote: >>We might want to think about doing this during off-hours as well. >> >>Ahm, should we take a survey to figure out which timezone most users >>are in first? >> >>Oh, we have a recent backup of the internet in case the reboot fail, >>right? Is it safe to chuckle at this thread yet?, I'm about to blow a gasket trying not to. Cheers, Gene
Re: Redhat 7.1 troubles
Hmmm,
It looks like I spoke too soon. The wait change did indeed make the
timeout error go away, but when the backup actually occured later that
night I remembered why I had changed the wait to no in the first place:
my_computer /dev/hda2 lev 0 FAILED [nak error:amandad busy]
So, I changed wait back to no, and added the EXTRAPOTIONS="-loop 100" to
/etc/sysconfig/xinetd.
That allowed it to run for several hours and into the backup. Only one
partition failed with:
my_computer /dev/hda3 lev 1 FAILED [could not connect to my_computer]
I've flushed the iptables, so it's not a firewall issue.
Any additional suggestions would be greatly appreciated.
My original message and reply follows.
Thanks,
Jenn
Jennifer Peterson wro
te:
> I would like to thank everybody for their replies. Changing my wait =
> no to wait = yes in xinetd.d/amanda did the trick.
>
> Jennifer Peterson wrote:
>
>> Hi,
>>
>> I wonder if anybody can help me out with this problem. I installed
>> amanda-client-2.4.2p2-1.i386.rpm on my Redhat 7.1 box, and I have
>> amandad running through xinetd like so:
>> service amanda
>> {
>> socket_type= dgram
>> protocol= udp
>> wait= no
>> user= amanda
>> group= disk
>> server= /usr/lib/amanda/amandad
>> disable= no
>> groups = yes
>> only_from = "backup_computer"
>> }
>>
>> When I restart xinetd, the amanda service starts up just fine, and
>> when I amcheck from my backup computer, no errors are reported.
>> However, after about 20 minutes or so, I get this in my syslog:
>>
>> Oct 22 15:24:11 my_computer xinetd[29480]: amanda service was
>> deactivated because of looping
>> Oct 22 15:24:41 my_computer amandad[30051]: error receiving message:
>> timeout
>>
>> The amandad error log on my_computer reads basically the same thing:
>> amandad: dgram_recv: timeout after 30 seconds
>> amandad: error receiving message: timeout
>>
>> At this point amcheck also fails.
>>
>> If I restart xinetd right before the backup begins, then the backup
>> works.
>>
>> Any suggestions?
>>
>> Thanks,
>>
>> Jenn Peterson
>>
>>
>
>
client setup on RH 7.1?
I have amanda 2.4.2p2 that came with RH 7.1. I am having trouble getting the client side to work (though the server side works fine). I enabled the amanda client service through xinetd, and installed a .amandahosts file in ~amanda. However, running amcheck on the server gives me the error: ERROR: fooclient: [access as amanda not allowed from amanda@fooserver] amandahostsauth failed Do I need something in /etc/hosts.allow? (I thought that was for tcp-wrappers, only.) Thanks for any clues, --Dave Chin [EMAIL PROTECTED]
HP-UX client setup
I'm posting this because someone had asked me about my HP-UX client setup and I want a record of this: amanda 2.4.2p2 -- server on RedHat 7.1 client on HP-UX 10.20, with Logical Volume Manager (LVM) [compiled with SoftBench cc] amanda user had to be added to group adm for access to disks. Cheers, --Dave Chin [EMAIL PROTECTED]
RE: AMANDA WEBSITE ???
>We might want to think about doing this during off-hours as well. >Ahm, should we take a survey to figure out which timezone most users >are in first? >Oh, we have a recent backup of the internet in case the reboot fail, >right? -- >Seeya, >Paul Can we wait until next week? That level 0 dump I've been working on for the past 6 weeks just hasn't finished yet. Besides...DST is this Saturday...best to wait until after that...
Re: NT backups
I posted my version of the setup instructions to this list last week, since the ones included with the client are a bit difficult to read (for all I know, so are mine :) ). For all who are interested, I posted them to the project's "help" forum. "Rivera, Edwin" wrote: > > http://sourceforge.net/projects/amanda-win32/ > > it's a bit tricky to get working... > > -edwin > > -Original Message- > From: Stephen Carville [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, October 24, 2001 3:17 PM > To: Amanda Users > Subject: NT backups > > I recently read a message here about a native NT client (doesn't > require samba) for backing up NT boxes using Amanda but I cannot fond > the message in Google or the archives. Can someone point me to a web > or ftp site?
Re: AMANDA WEBSITE ???
On Thu, 25 Oct 2001, Paul Lussier wrote: > > In a message dated: Wed, 24 Oct 2001 17:13:09 EDT > Mitch Collinsworth said: > > >On Wed, 24 Oct 2001, Rivera, Edwin wrote: > > > >> we may have to reboot the internet for this. > > > >Which of course means we first have to send a notice to all users... > > We might want to think about doing this during off-hours as well. > > Ahm, should we take a survey to figure out which timezone most users > are in first? > > Oh, we have a recent backup of the internet in case the reboot fail, > right? We don't need to do backups. We have RAID. :-; -Mitch
Re: AMANDA WEBSITE ???
In a message dated: Wed, 24 Oct 2001 17:13:09 EDT Mitch Collinsworth said: >On Wed, 24 Oct 2001, Rivera, Edwin wrote: > >> we may have to reboot the internet for this. > >Which of course means we first have to send a notice to all users... We might want to think about doing this during off-hours as well. Ahm, should we take a survey to figure out which timezone most users are in first? Oh, we have a recent backup of the internet in case the reboot fail, right? -- 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
OK, what stupid mistake am I making?
I'm in the process of moving my Amanda server from a HP-UX machine to a
Linux one. The new machines name is debian.
I'm having problems with the tar exclude feature on the new tapejost
itself. Heres the info
FAILURE AND STRANGE DUMP SUMMARY:
debian hde4 lev 0 STRANGE
FAILED AND STRANGE DUMP DETAILS:
/-- debian hde4 lev 0 STRANGE
sendbackup: start [debian:hde4 level 0]
sendbackup: info BACKUP=/usr/local/bin/tar
sendbackup: info RECOVER_CMD=/bin/gzip -dc |/usr/local/bin/tar -f... -
sendbackup: info COMPRESS_SUFFIX=.gz
sendbackup: info end
? gtar: ./home/oracle/9.01/software/app/oracle/oradata/debian/control03.ctl: file
changed as we read it
| gtar: ./tmp/ssh-XXFiBGDE/agent.9980: socket ignored
? gtar: ./usr/local/amanda/adm/DailyDump/index/cems/_/20011024_1.gz.tmp: Warning:
Cannot stat: No such file or directory
? gtar: ./usr/local/amanda/adm/DailyDump/index/cogenal/ad0s1f/20011024_1.gz.tmp:
Warning: Cannot stat: No such file or directory
? gtar: ./usr/local/amanda/adm/DailyDump/index/cogenwp/c0t3d0s7/20011024_0.gz.tmp:
Warning: Cannot stat: No such file or directory
? gtar: ./usr/local/amanda/adm/DailyDump/index/phse1/c0t0d0/20011024_1.gz.tmp:
Warning: Cannot stat: No such file or directory
? gtar: ./usr/local/amanda/adm/DailyDump/index/phse1/c0t1d0/20011024_1.gz.tmp:
Warning: Cannot stat: No such file or directory
? gtar:
./usr/local/amanda/adm/DailyDump/index/stripper/_dev_md_dsk_d5/20011024_1.gz.tmp:
Warning: Cannot stat: No such file or directory
? gtar: ./usr/local/amanda/adm/DailyDump/index/stripperal/ad0s1f/20011024_1.gz.tmp:
Warning: Cannot stat: No such file or directory
? gtar:
./usr/local/amanda/adm/DailyDump/index/waterap/_dev_md_dsk_d5/20011024_1.gz.tmp:
Warning: Cannot stat: No such file or directory
? gtar: ./usr/local/amanda/adm/DailyDump/index/waterwp/c0t3d0s6/20011024_0.gz.tmp:
Warning: Cannot stat: No such file or directory
| gtar: ./var/run/postgresql/.s.PGSQL.5432: socket ignored
| gtar: ./var/tmp/.oracle/s#406.1: socket ignored
| gtar: ./var/tmp/.oracle/sEXTPROC: socket ignored
| Total bytes written: 8280053760 (7.7GB, 379kB/s)
sendbackup: size 8085990
sendbackup: end
\
>From disklist
---
debian hde4 comp-user-tar 1 local
debian hde1 comp-user-tar 1 local
debian hdf1 holding-disk-tar 2 local
debian hdg1 nocomp-user 3 local # Compressing compressed data makes it
# larger
>From amanda.conf
--
define dumptype user-tar {
root-tar
comment "user partitions dumped with tar"
priority medium
}
define dumptype comp-user-tar {
user-tar
exclude list "/usr/local/lib/gnutar_exclude_list"
compress client fast
}
ls -l of /usr/local/lib/gnutar_exclude_list
-rw-r--r--1 amanda staff 472 Oct 24 07:52
/usr/local/lib/gnutar_exclude_list
/usr/local/lib/gnutar_exclude_list itself
---
./net
./dev/gpmctl
./dev/log
./home/oracle/9.01/software/app/oracle/oradata/debian/control02.ctl
./home/oracle/9.01/software/app/oracle/oradata/debian/redo02.log
./home/oracle/9.01/software/app/oracle/oradata/debian/control01.ctl
./home/oracle/9.01/software/app/oracle/product/release/oradata/debian/undotbs01.dbf
./tmp/.ICE-unix
./tmp/.X11-unix
./var/run/postgresql/.s\*
./var/run/sendmail/smcontrol
./var/tmp/.oracle/s\*
./tmp/.sawfish-stan
./tmp/orbit-stan
./tmp/ssh\*
Now clearly the files I wan't to exclude, are not being excluded! Also
what's with the Amanda files themselves, that it's complaining about?
The holding disk is /dev/hdf1, so that should not be related to the
problems with this disk.
--
Stan Brown [EMAIL PROTECTED]843-745-3154
Charleston SC.
--
Windows 98: n.
useless extension to a minor patch release for 32-bit extensions and
a graphical shell for a 16-bit patch to an 8-bit operating system
originally coded for a 4-bit microprocessor, written by a 2-bit
company that can't stand for 1 bit of competition.
-
(c) 2000 Stan Brown. Redistribution via the Microsoft Network is prohibited.
Re: indexes
On Tue Oct 23, 2001 at 06:11:40PM -0400, Jon LaBadie wrote: > On Tue, Oct 23, 2001 at 10:43:10PM +0200, Marek Florianczyk wrote: > > Hi > > > > I've got amanda serwer 2.4.2p2 on freebsd 4.4rc5 and amanda client > > on linux RH7.0 and freebsd 3.4 release. > > There isn't a lot of data to backup, only 2 GB from every host. > > Backup is done every night, starting from cron. > > Streamer is 40/80GB Tandberg DLT1, I've only one tape. > > In my opinion amanda should write next backup on tape just after the > > previous, so on one tape 80 GB there is a lot of place for lets say > > 4 backups. > > > In the opinion of amanda developers multiple backups on one > tape is a very bad/dangerous thing. Yes, but this hosts are in place where there is no people, and I don't want to change tapes. Maybe this solution is impossible with amanda? Has anybody this same settings and indexes working fine with one tape? > > Suggestion 1, if that is what you want, seek a different > backup solution. > > Suggestion 2, buy more tapes Isn't your data worth it? > If not, why back it up? > > > But when I run amrecover and type setdate ---21 (today is 23 ) > > amrecover says: > > 200 Working date set to 2001-10-21. > > No index records for cwd on new date > > Setting cwd to mount point > > I've no clue why this set of errors, but I can't understand > your amanda.conf file. > > > dumpcycle 2 weeks # the number of days in the normal dump cycle > > runspercycle 0 # the number of amdump runs in dumpcycle days > > # (4 weeks * 5 amdump runs per week -- just weekdays) > > You want at least one full dump of every system every 2 weeks. Ok. > You are going to run 0 backups during those 2 weeks? > > > -- > Jon H. LaBadie [EMAIL PROTECTED] > JG Computing [EMAIL PROTECTED] > 4455 Province Line Road(609) 252-0159 > Princeton, NJ 08540-4322 (609) 683-7220 (fax) >
restoring a particular file
Hi all, I'm a newbie on using amanda. I'm using amanda-2.2-p1-12 on debian potato systems. I'va already set up amanda and Amdump seems working (reports seems good). I'm doing backups on a HP DAT SureStore. Now I want to test restoring from backups I've done and I'm a little bit confused about options I have to give to amrestore if I want to restore a particular file. For example, let's say my configuration name is "Testconf" My cartridges are labeled TestConf01, TestConf02, ... Can anyone tell me the options I have to give amrestore (or amrecover?) if I want to restore a file called /etc/test.txt which has been backep up from host "seine" from filesystem "/etc"? Is this restore going to replace my actual /etc/test.txt? If so, how can I tell amrestore (or amrecover ?) to restore it in /tmp so that I can copy it manually if needed. Thanks for your help. -- Hery Zo RAKOTONDRAMANANA Simicro Internet Tél: (261) 20 22 648 83 Fax: (261) 20 22 661 83 Mobile: (261) 33 11 427 45 Save Our Smile ;-) --
