Re: amrecover and indexes
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---
/etc/PATH
/etc/amandates
/etc/inetd.conf
/etc/oratab
/etc/utmp
/etc/utmpx
/etc/opt/resmon/log/api.log
/etc/opt/resmon/log/armmon.log
/etc/opt/resmon/log/client.log
/etc/opt/resmon/log/fc60mon.log
/etc/opt/resmon/log/registrar.log
/etc/opt/resmon/log/reslog.html
---snip---
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 root local user amanda
amandahosts security check passed200
Access OK
DATE 2001-05-19200
Working date set to 2001-05-19.
SCNF sherpa
200 Config set to sherpa.
HOST basecamp
200 Dump host set to basecamp.
DISK /
200 Disk set to /.
DISK /
200 Disk set to /.
OISD /
500 No dumps available on or before date 2001-05-19
OISD /
500 No dumps available on or before date 2001-05-19
OISD /
500 No dumps available on or before date 2001-05-19
QUIT
200 Good bye.
amindexd: pid 16576 finish time Sat May 19 12:11:45 2001
I got a successful backup summary from amdump. Anything more that I can chase down?
Let me know if there are any other details I should provide.
Thanks,
Ian Prowell
On May 18, 2001, Alexandre Oliva wrote:
07300354473/./etc/
Read docs/INSTALL. You should not have used GNU tar 1.13.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicampoliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist*Please* write to mailing lists, not to me
Re: amrecover and indexes
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 root local user amanda amandahosts security check passed 200 Access OK DATE 2001-05-19 200 Working date set to 2001-05-19. SCNF sherpa 200 Config set to sherpa. HOST basecamp 200 Dump host set to basecamp. Amanda has an index for the host basecamp.sapient.com, but you used sethost basecamp. Did you already try sethost basecamp.sapient.com? Is that domain in your /etc/resolv.conf to be used? Or did you ./configure ... --enable-fqdn? (Don't know what this option really means)
disk offline
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 oak?] I decided to do every dump using tar only. I noticed running amstatus that the estimate could not be get for the remote machines, so I wonder what is the tar command that is used to calculate the estimate. I will try it by hand and see what I can get from it. It seems that syslog reports nothing unusual on the client machine. Dump for the Amanda server, as well as for Windows client Samba'ed from the Amanda server is working great. Best regards, Olivier
Re: amrecover and indexes
./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
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 file system: SECURITY USER rootbsd security: remote host basecamp.sapient.com user root local user amanda amandahosts security check passed 200 Access OK DATE 2001-05-19 200 Working date set to 2001-05-19. SCNF sherpa 200 Config set to sherpa. HOST basecamp 200 Dump host set to basecamp. Amanda has an index for the host basecamp.sapient.com, but you used sethost basecamp. Did you already try sethost basecamp.sapient.com? Is that domain in your /etc/resolv.conf to be used? Or did you ./configure ... --enable-fqdn? (Don't know what this option really means) - End forwarded message -
Re: amverify 'not at start of tape' errors
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 of the tape. It has
absolutely nothing to do with what is actually on the tape. It has to
do with whether amrestore found a tape label in the beginning of the
first section it read or not, and this tape label is only written by
Amanda in the beginning of a tape.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicampoliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist*Please* write to mailing lists, not to me
