Re: amrecover and indexes

2001-05-19 Thread Ian Prowell
Well I went through the INSTALL doc and read it again. I changed to tar 1.13.19, but am getting the same message from amrecover. The indexes now look different through: gzip -dc /usr/adm/amanda/sherpa/index/basecamp.sapient.com/_/20010519_1.gz now produces output that looks like: ---snip---

Re: amrecover and indexes

2001-05-19 Thread Bernhard R. Erdmann
gzip -dc /usr/adm/amanda/sherpa/index/basecamp.sapient.com/_/20010519_1.gz [...] It seems like amindex does not think that I have a dump for this file system: SECURITY USER rootbsd security: remote host basecamp.sapient.com user

disk offline

2001-05-19 Thread Olivier Nicole
Hello, I have upgraded to tar 1.13.19 but when I try to activate amanda on a client machine, I get disk off line error: FAILURE AND STRANGE DUMP SUMMARY: oak/home/fidji lev 0 FAILED [disk /home/fidji offline on oak?] oak/home/hawai lev 0 FAILED [disk /home/hawai offline on

Re: amrecover and indexes

2001-05-19 Thread Olivier Nicole
./configure ... --enable-fqdn? (Don't know what this option really means) Means fully qualified domain name I think, so a host basecamp would always be renamed basecamp.sapient.com Olivier

Re: amrecover and indexes

2001-05-19 Thread Ian Prowell
The sethost seems to have done the trick. Thanks for the help. Now the important part of the backup and recover scheme is working. -Ian Prowell gzip -dc /usr/adm/amanda/sherpa/index/basecamp.sapient.com/_/20010519_1.gz [...] It seems like amindex does not think that I have a dump for this

Re: amverify 'not at start of tape' errors

2001-05-19 Thread Alexandre Oliva
On May 19, 2001, Carey Jung [EMAIL PROTECTED] wrote: we seem to get a lot of 'not at start of tape' errors It's not an error, just a warning that the tape section numbers that follow do not reflect the actual tape section numbers on tape, because you hadn't started amrestore at the beginning