Re: tape changer
Alan Pham [EMAIL PROTECTED] wrote: 2. How do I configure amanda.conf so data will be APPEND to current tape in drive? The default is overwrite. This isn't wise, because be prepared to loose upto X days of backups if the tape breaks. Knowing that, and having evaluated your risks you can then install the `append-patch' from http://www-internal.alphanet.ch/archives/local/alphanet/divers/patches/amanda/
Re: .amandahosts not working
On Thu, 20 Sep 2001 at 4:38pm, Jeremy Wadsack wrote Just like the settings are. Is there any where else I can look to find out why this is failing? Are there any permissions on the amandahosts file that are wrong? # ls -lA ~tape/ -r 1 tape disk 34 Sep 20 23:06 .amandahosts What are the permissions on ~tape (the directory) itself? I was able to get this to work on the backup server (with root to root, which I know isn't safe, but (a) the traffic should never pass the net card or router at worst case and (b) it works). Am I right to say that amanda is still configured to run as user root on the backup server? If so, try setting up a 'tape' user there, reinstalling amanda, changing .amandahosts on the client to contain only the amanda server hostname, and giving it another shot. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
getting message lev 0 failed [data timeout]
Hello I'm getting this error whenever I try to run amdump (2.4.2p1) on freebsd 4.2: /-- galadriel. /usr lev 0 FAILED [data timeout] sendbackup: start [galadriel.shcorp.com:/usr level 0] sendbackup: info BACKUP=/usr/local/bin/gtar sendbackup: info RECOVER_CMD=/usr/local/bin/gtar -f... - sendbackup: info end ? sendbackup: index tee cannot write [Broken pipe] ? index returned 1 sendbackup: error [/usr/local/bin/gtar got signal 13] \ All the other partitions on galadriel and the other hosts I'm backing up are OK, so the amanda client install seems alright. I've also tried installing the latest version of gnutar; 1.13.22 and increasing the dtimeout setting in amanda.conf from 1800 to 3600. Is there anything else I can try (such as upping one of the other timeout settings)? here's /tmp/amanda/sendbackup.debug; doesn't seem to shed any light on it (although I wonder why it says 1970): sendbackup: debug 1 pid 10243 ruid 1000 euid 1000 start time Wed Sep 19 02:13:31 2001 /usr/local/libexec/amanda/sendbackup: got input request: GNUTAR /usr 0 1970:1:1:0:0:0 OPTIONS |;bsd-auth;index;exclude-list=/usr/local/lib/amanda/exclude.gtar; parsed request as: program `GNUTAR' disk `/usr' lev 0 since 1970:1:1:0:0:0 opt `|;bsd-auth;index;exclude-list=/usr/local/lib/amanda/exclude.gtar;' waiting for connect on 3189, then 3190, then 3191 got all connections sendbackup: doing level 0 dump as listed-incremental: /usr/local/var/amanda/gnutar-lists/galadriel.shcorp.com_usr_0.new sendbackup: doing level 0 dump from date: 1970-01-01 0:00:00 GMT sendbackup: spawning /usr/local/libexec/amanda/runtar in pipeline sendbackup: argument list: gtar --create --directory /usr --listed-incremental /usr/local/var/amanda/gnutar-lists/galadriel.shcorp.com_usr_0.new --sparse --one-file-system --ignore-failed-read --totals --file - --exclude-from /usr/local/lib/amanda/exclude.gtar . sendbackup-gnutar: pid 10245: /usr/local/libexec/amanda/runtar --create --directory /usr --listed-incremental /usr/local/var/amanda/gnutar-lists/galadriel.shcorp.com_usr_0.new --sparse --one-file-system --ignore-failed-read --totals --file - /usr/local/lib/amanda/exclude.gtar--exclude-from/usr/local/lib/amanda/exclude.gtar sendbackup: started index creator: /usr/local/bin/gtar -tf - 2/dev/null | sed -e 's/^\.//' index tee cannot write [Broken pipe] index tee cannot write [Broken pipe] sendbackup: pid 10244 finish time Wed Sep 19 02:28:02 2001 error [/usr/local/bin/gtar got signal 13] error [/usr/local/bin/gtar got signal 13] sendbackup: pid 10243 finish time Wed Sep 19 02:28:02 2001
Re: .amandahosts not working
Joshua Baker-LePain ([EMAIL PROTECTED]): On Fri, 21 Sep 2001 at 8:43am, Jeremy Wadsack wrote Joshua Baker-LePain ([EMAIL PROTECTED]): What are the permissions on ~tape (the directory) itself? drwx-- 4 tape disk 1024 Sep 20 23:06 tape Also: [root /home]# su tape [tape /home]$ cat ~/.amandahosts net-cf9a5425 root Well, thinking about this all more, this should work. Urgh. That's what I thought. Which is why I brought it to the list... :) Am I right to say that amanda is still configured to run as user root on the backup server? If so, try setting up a 'tape' user there, reinstalling amanda, changing .amandahosts on the client to contain only the amanda server hostname, and giving it another shot. Ok, I'll give this a shot. I'm hesitant to recompile or rebuild because it works, but this would be something I need to do eventually anyway, so I'll take that step now. Ah, good. Tried this, same error. I'm also getting this cryptic message from amcheck: Amanda Backup Client Hosts Check ERROR: running as user tape instead of root The amcheck binary was updated today. The amandad log (on the backup server itself, so same build run) shows that CLIENT_LOGIN is 'tape'. I don't see anything similar for amcheck in it's logs. And it logs-in just fine on the backup server (as it did before). It just gives this 'ERROR.' I've tried with and without 'tape' in the client amandahosts and I don't get access. Here's something else that might help. 'hostname' on the server gives me 'net-cf9a5431'. But when it connects to other machines, it looks like 'net-cf9a5425'. I tried adding both to the client and it still won't connect. Any suggestion where I can look next? Thanks, -- Jeremy Wadsack Wadsack-Allen Digital Group
make on solaris 7 dies
Trying to install 2.4.2 on solaris 7. Make dies here: gcc -DHAVE_CONFIG_H -I. -I. -I../config -I./../regex-src -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -g -O2 -c version.c gcc -DHAVE_CONFIG_H -I. -I. -I../config -I./../regex-src -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -g -O2 -c pipespawn.c rm -f libamanda.a cru libamanda.a alloc.o amflock.o debug.o dgram.o error.o file.o fileheader.o match.o protocol.o regcomp.o regerror.o regexec.o regfree.o security.o statfs.o stream.o token.o util.o version.o versuff.o pipespawn.o /usr/bin/sh: cru: not found make[1]: *** [libamanda.a] Error 1 make[1]: Leaving directory `/usr/local/src/amanda-2.4.2/common-src' make: *** [all-recursive] Error 1 Seems to be tied to common-src/Makefile not having AR defined. My rh71 box has AR = /usr/bin/ar. Can't find any utility called ar on the sparc system. Is this the problem? What is the solution? Thanks -- toby I believe we are on an irreversible trend toward more freedom and democracy -- but that could change - Dan Qualye
Re: make on solaris 7 dies
Toby Bluhm wrote: Trying to install 2.4.2 on solaris 7. Make dies here: gcc -DHAVE_CONFIG_H -I. -I. -I../config -I./../regex-src -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -g -O2 -c version.c gcc -DHAVE_CONFIG_H -I. -I. -I../config -I./../regex-src -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -g -O2 -c pipespawn.c rm -f libamanda.a cru libamanda.a alloc.o amflock.o debug.o dgram.o error.o file.o fileheader.o match.o protocol.o regcomp.o regerror.o regexec.o regfree.o security.o statfs.o stream.o token.o util.o version.o versuff.o pipespawn.o /usr/bin/sh: cru: not found make[1]: *** [libamanda.a] Error 1 make[1]: Leaving directory `/usr/local/src/amanda-2.4.2/common-src' make: *** [all-recursive] Error 1 Seems to be tied to common-src/Makefile not having AR defined. My rh71 box has AR = /usr/bin/ar. Can't find any utility called ar on the sparc system. Is this the problem? What is the solution? I fixed it. Needed SUNWbtool package which was installed but /usr/ccs/bin was not in the path. I should have been more patient in figuring this out. -- toby I believe we are on an irreversible trend toward more freedom and democracy -- but that could change - Dan Qualye
Re: make on solaris 7 dies
Put /usr/ccs/bin in your $PATH before running configure. Marty Toby Bluhm wrote: Trying to install 2.4.2 on solaris 7. Make dies here: gcc -DHAVE_CONFIG_H -I. -I. -I../config -I./../regex-src -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -g -O2 -c version.c gcc -DHAVE_CONFIG_H -I. -I. -I../config -I./../regex-src -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -g -O2 -c pipespawn.c rm -f libamanda.a cru libamanda.a alloc.o amflock.o debug.o dgram.o error.o file.o fileheader.o match.o protocol.o regcomp.o regerror.o regexec.o regfree.o security.o statfs.o stream.o token.o util.o version.o versuff.o pipespawn.o /usr/bin/sh: cru: not found make[1]: *** [libamanda.a] Error 1 make[1]: Leaving directory `/usr/local/src/amanda-2.4.2/common-src' make: *** [all-recursive] Error 1 Seems to be tied to common-src/Makefile not having AR defined. My rh71 box has AR = /usr/bin/ar. Can't find any utility called ar on the sparc system. Is this the problem? What is the solution? Thanks -- toby I believe we are on an irreversible trend toward more freedom and democracy -- but that could change - Dan Qualye -- Marty Shannon, RHCE, Independent Computing Consultant mailto:[EMAIL PROTECTED]
Re: .amandahosts not working
... I'm also getting this cryptic message from amcheck: Amanda Backup Client Hosts Check ERROR: running as user tape instead of root This says you ran amcheck as tape but dumpuser in amanda.conf is set to root. Shouldn't it be set to tape? ERROR: net-cf9a5410: [access as tape not allowed from root@net-cf9a5425] First of all, this line speaks the truth about host names. In other words, host net-cf9a5410 got a request from an IP that it mapped back to net-cf9a5425. Whatever net-cf9a5425 thinks about itself does not matter. And it also (in theory) tells you exactly what to put in your .amandahosts, which you appear to have done. Some other things to look at. Is the access time (ls -lu) on your .amandahosts changing when you run amcheck? If not, then we're not even getting to the file. Next, grep USE_AMANDAHOSTS in a recent /tmp/amanda/amandad*debug file on net-cf9a5410 and make sure that client was set up to use .amandahosts. Next, you didn't mention what version of Amanda you're using, but the amandad*debug file *may* contain a little more information about why it refused the connection -- the latest Amanda versions do a little more logging. Finally, on that client: cd common-src make security then run ./security **as tape** and answer the remote host questions with the exact same text as was in the message. It should trace the actions in more detail and hopefully give some more information. Jeremy Wadsack John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Which archive utility to use?
OK, I think I have amanda figured out :-) At least I can save to a tape and then restore from it using amrestore. One of the reasons I chose amanda was it used 'standard' tools. However I have not been able to read a tape made with amanda using tar. I've tried tar -tvf /dev/rmt/0cbn and using dd and piping the output to tar but I just get 'this doesn't look like a tar archive' Being able to restore using 'standard' UNIX utilities is important to my overall backup strategy so can I use tar to restore from a tape made with amanda? If not, will dump work better? I'm not prejudiced either way. -- -- Stephen Carville http://www.heronforge.net/~stephen/gnupgkey.txt == Government is like burning witches: After years of burning young women failed to solve any of society's problems, the solution was to burn more young women. ==
Re: with-tape-device
However, what would be the config command to compile the client with this tape device? ./configure --with-tape-device=server.address:/dev/nst0? or ./configure --with-tape-device=/dev/nst0? Or neither? The latter (--with-tape-device=/dev/nst0). All --with-tape-device does is set a default for the amrecover tool. You can override it (and the tape server) on the command line. Lalo John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
