amrecover: no index records for host
I added 'index yes' in the dumptype “Comp-root-tar”. I ran amdump using that dumptype with no error reporting. When I use “amrecover –C ”, I still got the same error”no index records for host”. amandaidx service is enabled in xinetd. Please help. Thank you, lei
Re: amrecover: No index records for host?
> > > Hello, > > I don't have the record tag but seems ok to me :) Great! > > On the client when running ./configure I get > > [cut] > > checking for gtar... no > > checking for gnutar... no > > checking for tar... /usr/local/bin/tar > > [cut] > > > > But there is a parameter called "with-gnu-tar" or > something (do a ./configure --help). Then it should > work. This is what I ran it as ./configure --with-user=amanda --with-group=amanda --with-config=incrementat --with-gnutar --without-server --with-index-server=fil.esc.net.au > > however, > > > > www# which tar > > /usr/local/bin/tar > > www# tar --version > > tar (GNU tar) 1.13.25 > > Copyright (C) 2001 Free Software Foundation, Inc. > > This program comes with NO WARRANTY, to the extent > > permitted by law. > > You may redistribute it under the terms of the GNU > > General Public License; > > see the file named COPYING for details. > > Written by John Gilmore and Jay Fenlason. > > > > > > Any more suggestions? > > > > > > > Hope this helps > > > > > > JV. > > > > > > --- Stavros Patiniotis <[EMAIL PROTECTED]> > > escribió: > > > > > > > > Hello, > > > > > > > > I get the error, No index records for host? > > I've > > > > upgraded tar, linked the > > > > old tar location to the new (ln -s > > > > /usr/local/bin/tar /usr/bin/tar), and > > > > still get the above error. In the /tmp/amanda > > dir I > > > > get no errors in the > > > > amrecover files, however in the amandaindexd > > files, > > > > I get an error like: > > > > > > > > > OISD / > > > > < 500 No dumps available on or before date > > > > "2001-12-07" > > > > > OISD / > > > > < 500 No dumps available on or before date > > > > "2001-12-07" > > > > > > > > The partition in question definately has a > > backup as > > > > the Amanda daily > > > > report says its been backed up. > > > > > > > > I do not record to tape, but leave my backups on > > the > > > > holding disk. > > > > > > > > Any suggestion? > > > > > > > > > > > > Kind Regards, > > > > > > > > > > > > > > > > > > 0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0 > > > > escape net > > > > m a k i n g t h e n e t w o r k f o > > r > > > > y o u > > > > > > > > 465b South Road > > > > > > ph 8293 2526 > > > > KESWICK SA 5035 > > > > > > fx 8293 2949 > > > > > > > > > > 0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0 > > > > > > > > > > > > > > = > > > System Engineer, José Vicente Nuñez Zuleta > > ([EMAIL PROTECTED]) > > > Newbreak System Administrator > > (http://www.newbreak.com) > > > Phone: 203-355-1511, 203-355-1510 > > > Java 2 Certified Programmer > > > Java 2 Certified Developer > > > > > > > > > _ > > > Do You Yahoo!? > > > ¿Quieres armar tu própia página Web pero no sabes > > HTML? > > > Usa los asistentes de edición de Yahoo! Geocities > > > y tendrás un sitio en sólo unos minutos. > > > Visítanos en http://espanol.geocities.yahoo.com > > > > > > > = > System Engineer, José Vicente Nuñez Zuleta ([EMAIL PROTECTED]) > Newbreak System Administrator (http://www.newbreak.com) > Phone: 203-355-1511, 203-355-1510 > Java 2 Certified Programmer > Java 2 Certified Developer > > _ > Do You Yahoo!? > ¿Quieres armar tu própia página Web pero no sabes HTML? > Usa los asistentes de edición de Yahoo! Geocities > y tendrás un sitio en sólo unos minutos. > Visítanos en http://espanol.geocities.yahoo.com >
Re: amrecover: No index records for host?
Hello, What i did was to recompile the amanda server and also added the option "index" to the dumpiles type (for example comp-user) in the amanda.conf file. I got it working for Tar, and i let you know if that fixes my dump errors too (i got that error with dump). Hope this helps JV. --- Stavros Patiniotis <[EMAIL PROTECTED]> escribió: > > Hello, > > I get the error, No index records for host? I've > upgraded tar, linked the > old tar location to the new (ln -s > /usr/local/bin/tar /usr/bin/tar), and > still get the above error. In the /tmp/amanda dir I > get no errors in the > amrecover files, however in the amandaindexd files, > I get an error like: > > > OISD / > < 500 No dumps available on or before date > "2001-12-07" > > OISD / > < 500 No dumps available on or before date > "2001-12-07" > > The partition in question definately has a backup as > the Amanda daily > report says its been backed up. > > I do not record to tape, but leave my backups on the > holding disk. > > Any suggestion? > > > Kind Regards, > > > 0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0 > escape net > m a k i n g t h e n e t w o r k f o r > y o u > > 465b South Road > ph 8293 2526 > KESWICK SA 5035 > fx 8293 2949 > 0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0 > > = System Engineer, José Vicente Nuñez Zuleta ([EMAIL PROTECTED]) Newbreak System Administrator (http://www.newbreak.com) Phone: 203-355-1511, 203-355-1510 Java 2 Certified Programmer Java 2 Certified Developer _ Do You Yahoo!? ¿Quieres armar tu própia página Web pero no sabes HTML? Usa los asistentes de edición de Yahoo! Geocities y tendrás un sitio en sólo unos minutos. Visítanos en http://espanol.geocities.yahoo.com
amrecover: No index records for host?
Hello, I get the error, No index records for host? I've upgraded tar, linked the old tar location to the new (ln -s /usr/local/bin/tar /usr/bin/tar), and still get the above error. In the /tmp/amanda dir I get no errors in the amrecover files, however in the amandaindexd files, I get an error like: > OISD / < 500 No dumps available on or before date "2001-12-07" > OISD / < 500 No dumps available on or before date "2001-12-07" The partition in question definately has a backup as the Amanda daily report says its been backed up. I do not record to tape, but leave my backups on the holding disk. Any suggestion? Kind Regards, 0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0 escape net m a k i n g t h e n e t w o r k f o r y o u 465b South Road ph 8293 2526 KESWICK SA 5035 fx 8293 2949 0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0
Re: amrecover: No index records for host?
> Hello,
Hi!
> What i did was to recompile the amanda server and also
> added the option "index" to the dumpiles type (for
> example comp-user) in the amanda.conf file. I got it
> working for Tar, and i let you know if that fixes my
> dump errors too (i got that error with dump).
Ok, I have now recomplied the server and client after installing tar
1.13.25, previously I had only link the old tar location to the new
tar. I have the following in amanda.conf:
define dumptype incremental {
comment "General Data Backup"
priority medium
program "GNUTAR"
compress client fast
index yes
record yes
}
On the client when running ./configure I get
[cut]
checking for gtar... no
checking for gnutar... no
checking for tar... /usr/local/bin/tar
[cut]
however,
www# which tar
/usr/local/bin/tar
www# tar --version
tar (GNU tar) 1.13.25
Copyright (C) 2001 Free Software Foundation, Inc.
This program comes with NO WARRANTY, to the extent permitted by law.
You may redistribute it under the terms of the GNU General Public License;
see the file named COPYING for details.
Written by John Gilmore and Jay Fenlason.
Any more suggestions?
> Hope this helps
>
> JV.
>
> --- Stavros Patiniotis <[EMAIL PROTECTED]> escribió:
> >
> > Hello,
> >
> > I get the error, No index records for host? I've
> > upgraded tar, linked the
> > old tar location to the new (ln -s
> > /usr/local/bin/tar /usr/bin/tar), and
> > still get the above error. In the /tmp/amanda dir I
> > get no errors in the
> > amrecover files, however in the amandaindexd files,
> > I get an error like:
> >
> > > OISD /
> > < 500 No dumps available on or before date
> > "2001-12-07"
> > > OISD /
> > < 500 No dumps available on or before date
> > "2001-12-07"
> >
> > The partition in question definately has a backup as
> > the Amanda daily
> > report says its been backed up.
> >
> > I do not record to tape, but leave my backups on the
> > holding disk.
> >
> > Any suggestion?
> >
> >
> > Kind Regards,
> >
> >
> >
> 0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0
> > escape net
> > m a k i n g t h e n e t w o r k f o r
> > y o u
> >
> > 465b South Road
> > ph 8293 2526
> > KESWICK SA 5035
> > fx 8293 2949
> >
> 0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0
> >
> >
>
> =
> System Engineer, José Vicente Nuñez Zuleta ([EMAIL PROTECTED])
> Newbreak System Administrator (http://www.newbreak.com)
> Phone: 203-355-1511, 203-355-1510
> Java 2 Certified Programmer
> Java 2 Certified Developer
>
> _
> Do You Yahoo!?
> ¿Quieres armar tu própia página Web pero no sabes HTML?
> Usa los asistentes de edición de Yahoo! Geocities
> y tendrás un sitio en sólo unos minutos.
> Visítanos en http://espanol.geocities.yahoo.com
>
Re: amrecover: No index records for host?
Hello, --- Stavros Patiniotis <[EMAIL PROTECTED]> escribió: > > > > > Hello, > > > > I don't have the record tag but seems ok to me :) > > Great! > > > > On the client when running ./configure I > get > > > [cut] > > > checking for gtar... no > > > checking for gnutar... no > > > checking for tar... /usr/local/bin/tar > > > [cut] > > > > > > > But there is a parameter called "with-gnu-tar" or > > something (do a ./configure --help). Then it > should > > work. > > This is what I ran it as > > ./configure --with-user=amanda --with-group=amanda > --with-config=incrementat --with-gnutar > --without-server > --with-index-server=fil.esc.net.au > Yes but you should provide the whole path to the tar program, like: --with-gnutar=/usr/local/bin/tar > > > however, > > > > > > www# which tar > > > /usr/local/bin/tar > > > www# tar --version > > > tar (GNU tar) 1.13.25 > > > Copyright (C) 2001 Free Software Foundation, > Inc. > > > This program comes with NO WARRANTY, to the > extent > > > permitted by law. > > > You may redistribute it under the terms of the > GNU > > > General Public License; > > > see the file named COPYING for details. > > > Written by John Gilmore and Jay Fenlason. > > > > > > > > > Any more suggestions? > > > > > > > > > > Hope this helps > > > > > > > > JV. > > > > > > > > --- Stavros Patiniotis <[EMAIL PROTECTED]> > > > escribió: > > > > > > > > > > Hello, > > > > > > > > > > I get the error, No index records for host? > > > I've > > > > > upgraded tar, linked the > > > > > old tar location to the new (ln -s > > > > > /usr/local/bin/tar /usr/bin/tar), and > > > > > still get the above error. In the > /tmp/amanda > > > dir I > > > > > get no errors in the > > > > > amrecover files, however in the amandaindexd > > > files, > > > > > I get an error like: > > > > > > > > > > > OISD / > > > > > < 500 No dumps available on or before date > > > > > "2001-12-07" > > > > > > OISD / > > > > > < 500 No dumps available on or before date > > > > > "2001-12-07" > > > > > > > > > > The partition in question definately has a > > > backup as > > > > > the Amanda daily > > > > > report says its been backed up. > > > > > > > > > > I do not record to tape, but leave my > backups on > > > the > > > > > holding disk. > > > > > > > > > > Any suggestion? > > > > > > > > > > > > > > > Kind Regards, > > > > > > > > > > > > > > > > > > > > > > > > > 0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0 > > > > > escape net > > > > > m a k i n g t h e n e t w o r k > f o > > > r > > > > > y o u > > > > > > > > > > 465b South Road > > > > > > > > > ph 8293 2526 > > > > > KESWICK SA 5035 > > > > > > > > > fx 8293 2949 > > > > > > > > > > > > > > > 0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0 > > > > > > > > > > > > > > > > > > = > > > > System Engineer, José Vicente Nuñez Zuleta > > > ([EMAIL PROTECTED]) > > > > Newbreak System Administrator > > > (http://www.newbreak.com) > > > > Phone: 203-355-1511, 203-355-1510 > > > > Java 2 Certified Programmer > > > > Java 2 Certified Developer > > > > > > > > > > > > > > _ > > > > Do You Yahoo!? > > > > ¿Quieres armar tu própia página Web pero no > sabes > > > HTML? > > > > Usa los asistentes de edición de Yahoo! > Geocities > > > > y tendrás un sitio en sólo unos minutos. > > > > Visítanos en > http://espanol.geocities.yahoo.com > > > > > > > > > > > = > > System Engineer, José Vicente Nuñez Zuleta > ([EMAIL PROTECTED]) > > Newbreak System Administrator > (http://www.newbreak.com) > > Phone: 203-355-1511, 203-355-1510 > > Java 2 Certified Programmer > > Java 2 Certified Developer > > > > > _ > > Do You Yahoo!? > > ¿Quieres armar tu própia página Web pero no sabes > HTML? > > Usa los asistentes de edición de Yahoo! Geocities > > y tendrás un sitio en sólo unos minutos. > > Visítanos en http://espanol.geocities.yahoo.com > > > = System Engineer, José Vicente Nuñez Zuleta ([EMAIL PROTECTED]) Newbreak System Administrator (http://www.newbreak.com) Phone: 203-355-1511, 203-355-1510 Java 2 Certified Programmer Java 2 Certified Developer _ Do You Yahoo!? ¿Quieres armar tu própia página Web pero no sabes HTML? Usa los asistentes de edición de Yahoo! Geocities y tendrás un sitio en sólo unos minutos. Visítanos en http://espanol.geocities.yahoo.com
Re: amrecover: No index records for host?
On Fri, 7 Dec 2001 at 9:46am, Stavros Patiniotis wrote > I get the error, No index records for host? I've upgraded tar, linked the > old tar location to the new (ln -s /usr/local/bin/tar /usr/bin/tar), and > still get the above error. In the /tmp/amanda dir I get no errors in the > amrecover files, however in the amandaindexd files, I get an error like: > > > OISD / > < 500 No dumps available on or before date "2001-12-07" > > OISD / > < 500 No dumps available on or before date "2001-12-07" > > The partition in question definately has a backup as the Amanda daily > report says its been backed up. Obvious question: Is indexing turned on? Do the index files exist? What do the contents look like? > I do not record to tape, but leave my backups on the holding disk. > What version of amanda? I think 2.4.2p2 may be needed to read backups from disk. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: amrecover: No index records for host?
Hello,
--- Stavros Patiniotis <[EMAIL PROTECTED]> escribió:
>
>
>
> > Hello,
>
> Hi!
>
> > What i did was to recompile the amanda server and
> also
> > added the option "index" to the dumpiles type (for
> > example comp-user) in the amanda.conf file. I got
> it
> > working for Tar, and i let you know if that fixes
> my
> > dump errors too (i got that error with dump).
>
> Ok, I have now recomplied the server and client
> after installing tar
> 1.13.25, previously I had only link the old tar
> location to the new
> tar. I have the following in amanda.conf:
>
> define dumptype incremental {
> comment "General Data Backup"
> priority medium
> program "GNUTAR"
> compress client fast
> index yes
> record yes
> }
>
I don't have the record tag but seems ok to me :)
> On the client when running ./configure I get
> [cut]
> checking for gtar... no
> checking for gnutar... no
> checking for tar... /usr/local/bin/tar
> [cut]
>
But there is a parameter called "with-gnu-tar" or
something (do a ./configure --help). Then it should
work.
> however,
>
> www# which tar
> /usr/local/bin/tar
> www# tar --version
> tar (GNU tar) 1.13.25
> Copyright (C) 2001 Free Software Foundation, Inc.
> This program comes with NO WARRANTY, to the extent
> permitted by law.
> You may redistribute it under the terms of the GNU
> General Public License;
> see the file named COPYING for details.
> Written by John Gilmore and Jay Fenlason.
>
>
> Any more suggestions?
>
>
> > Hope this helps
> >
> > JV.
> >
> > --- Stavros Patiniotis <[EMAIL PROTECTED]>
> escribió:
> > >
> > > Hello,
> > >
> > > I get the error, No index records for host?
> I've
> > > upgraded tar, linked the
> > > old tar location to the new (ln -s
> > > /usr/local/bin/tar /usr/bin/tar), and
> > > still get the above error. In the /tmp/amanda
> dir I
> > > get no errors in the
> > > amrecover files, however in the amandaindexd
> files,
> > > I get an error like:
> > >
> > > > OISD /
> > > < 500 No dumps available on or before date
> > > "2001-12-07"
> > > > OISD /
> > > < 500 No dumps available on or before date
> > > "2001-12-07"
> > >
> > > The partition in question definately has a
> backup as
> > > the Amanda daily
> > > report says its been backed up.
> > >
> > > I do not record to tape, but leave my backups on
> the
> > > holding disk.
> > >
> > > Any suggestion?
> > >
> > >
> > > Kind Regards,
> > >
> > >
> > >
> >
>
0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0
> > > escape net
> > > m a k i n g t h e n e t w o r k f o
> r
> > > y o u
> > >
> > > 465b South Road
>
> > > ph 8293 2526
> > > KESWICK SA 5035
>
> > > fx 8293 2949
> > >
> >
>
0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0o0
> > >
> > >
> >
> > =
> > System Engineer, José Vicente Nuñez Zuleta
> ([EMAIL PROTECTED])
> > Newbreak System Administrator
> (http://www.newbreak.com)
> > Phone: 203-355-1511, 203-355-1510
> > Java 2 Certified Programmer
> > Java 2 Certified Developer
> >
> >
>
_
> > Do You Yahoo!?
> > ¿Quieres armar tu própia página Web pero no sabes
> HTML?
> > Usa los asistentes de edición de Yahoo! Geocities
> > y tendrás un sitio en sólo unos minutos.
> > Visítanos en http://espanol.geocities.yahoo.com
> >
>
=
System Engineer, José Vicente Nuñez Zuleta ([EMAIL PROTECTED])
Newbreak System Administrator (http://www.newbreak.com)
Phone: 203-355-1511, 203-355-1510
Java 2 Certified Programmer
Java 2 Certified Developer
_
Do You Yahoo!?
¿Quieres armar tu própia página Web pero no sabes HTML?
Usa los asistentes de edición de Yahoo! Geocities
y tendrás un sitio en sólo unos minutos.
Visítanos en http://espanol.geocities.yahoo.com
Re: amrecover: No index records for host?
Thanks guys, worked like a charm. I figured that must have been it, didn't see a version of tar later than 1.13 at the mirror I went to initially. I'm using gnu tar 1.13.25 now with no problems (yet!) Thanks again, Rafe On Tue, 4 Dec 2001, Joshua Baker-LePain wrote: > On Mon, 3 Dec 2001 at 11:56am, Rafe Thayer wrote > > > 06573011000/./security/dev/audio > > 06573011000/./security/dev/fd0 > > 06573011000/./security/dev/sr0 > > 06573011000/./security/dev/st0 > > 06573011000/./security/dev/st1 > > > (these are just the contents of /etc on each host). The version of tar on > > the solaris machine is 1.13. I've heard tar can cause some problems. Do > > you think that might be it? > > Those are corrupted index files due to a bad version of tar. You need at > least 1.13.17, or 1.13.19. They're available from alpha.gnu.org. If the > location of GNUtar moves when you reinstall it, make sure to recompile > amanda so that it picks up the correct version. > > -- > Joshua Baker-LePain > Department of Biomedical Engineering > Duke University > >
Re: amrecover: No index records for host?
On Mon, 3 Dec 2001 at 11:56am, Rafe Thayer wrote > Hi Folks, > Another question for ya. After I did an amdump to test out dumping our > disks to tape, I tried to do an amrecover to see if restoring the data > would work. It seems to work for our linux machines, but the solaris box > has some trouble. When I start up amrecover, it reports: > ... > 200 Config set to imash. > 501 No index records for host: hostname. Invalid? > Trying hostname.domainname... > 200 Dump host set to hostname.domainname > ... > > > Then I do a setdisk /etc and it reports: > > 200 Disk set to /etc. > No index records for disk for specified date > If date correct, notify system administrator > > So I figured that the index must not have been created for some reason, > but I checked that out on the server and it looks fine. Has the right > permissions and ownership. The wierd thing is, if I look into the index > files for the host that's giving me trouble, they look a little different > than the others. It looks like this: > > 06573011000/./security/dev/audio > 06573011000/./security/dev/fd0 > 06573011000/./security/dev/sr0 > 06573011000/./security/dev/st0 > 06573011000/./security/dev/st1 > ... > > Whereas for the linux hosts, the index looks like this: > > / > /CORBA/ > /CORBA/servers/ > /X11/ > ... > > (these are just the contents of /etc on each host). The version of tar on > the solaris machine is 1.13. I've heard tar can cause some problems. Do > you think that might be it? > > Thanks for your help! > > Rafe > > > -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: amrecover: No index records for host?
On Mon, 3 Dec 2001 at 11:56am, Rafe Thayer wrote > 06573011000/./security/dev/audio > 06573011000/./security/dev/fd0 > 06573011000/./security/dev/sr0 > 06573011000/./security/dev/st0 > 06573011000/./security/dev/st1 > (these are just the contents of /etc on each host). The version of tar on > the solaris machine is 1.13. I've heard tar can cause some problems. Do > you think that might be it? Those are corrupted index files due to a bad version of tar. You need at least 1.13.17, or 1.13.19. They're available from alpha.gnu.org. If the location of GNUtar moves when you reinstall it, make sure to recompile amanda so that it picks up the correct version. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: amrecover: No index records for host?
On Mon, 3 Dec 2001 [EMAIL PROTECTED] wrote: > Hi Rafe: > I had a similar problem while setting up my configuration last week and I > think it was realted with not specifying the fully qualified name of the clients > in the disklist and .amandahosts file. You may try with that. > Hope this helps. Sincerely... Ana Maria Hi Ana Maria, I checked them, and they are using the fully qualified name for the client. Any other suggestions? Rafe > > > Quoting Rafe Thayer <[EMAIL PROTECTED]>: > > > Hi Folks, > > Another question for ya. After I did an amdump to test out dumping our > > disks to tape, I tried to do an amrecover to see if restoring the data > > would work. It seems to work for our linux machines, but the solaris box > > has some trouble. When I start up amrecover, it reports: > > ... > > 200 Config set to imash. > > 501 No index records for host: hostname. Invalid? > > Trying hostname.domainname... > > 200 Dump host set to hostname.domainname > > ... > > > > > > Then I do a setdisk /etc and it reports: > > > > 200 Disk set to /etc. > > No index records for disk for specified date > > If date correct, notify system administrator > > > > So I figured that the index must not have been created for some reason, > > but I checked that out on the server and it looks fine. Has the right > > permissions and ownership. The wierd thing is, if I look into the index > > files for the host that's giving me trouble, they look a little different > > than the others. It looks like this: > > > > 06573011000/./security/dev/audio > > 06573011000/./security/dev/fd0 > > 06573011000/./security/dev/sr0 > > 06573011000/./security/dev/st0 > > 06573011000/./security/dev/st1 > > ... > > > > Whereas for the linux hosts, the index looks like this: > > > > / > > /CORBA/ > > /CORBA/servers/ > > /X11/ > > ... > > > > (these are just the contents of /etc on each host). The version of tar on > > the solaris machine is 1.13. I've heard tar can cause some problems. Do > > you think that might be it? > > > > Thanks for your help! > > > > Rafe > > > > > > > - > This mail sent through IMP: http://horde.org/imp/ >
Re: amrecover: No index records for host?
Hi Rafe: I had a similar problem while setting up my configuration last week and I think it was realted with not specifying the fully qualified name of the clients in the disklist and .amandahosts file. You may try with that. Hope this helps. Sincerely... Ana Maria Quoting Rafe Thayer <[EMAIL PROTECTED]>: > Hi Folks, > Another question for ya. After I did an amdump to test out dumping our > disks to tape, I tried to do an amrecover to see if restoring the data > would work. It seems to work for our linux machines, but the solaris box > has some trouble. When I start up amrecover, it reports: > ... > 200 Config set to imash. > 501 No index records for host: hostname. Invalid? > Trying hostname.domainname... > 200 Dump host set to hostname.domainname > ... > > > Then I do a setdisk /etc and it reports: > > 200 Disk set to /etc. > No index records for disk for specified date > If date correct, notify system administrator > > So I figured that the index must not have been created for some reason, > but I checked that out on the server and it looks fine. Has the right > permissions and ownership. The wierd thing is, if I look into the index > files for the host that's giving me trouble, they look a little different > than the others. It looks like this: > > 06573011000/./security/dev/audio > 06573011000/./security/dev/fd0 > 06573011000/./security/dev/sr0 > 06573011000/./security/dev/st0 > 06573011000/./security/dev/st1 > ... > > Whereas for the linux hosts, the index looks like this: > > / > /CORBA/ > /CORBA/servers/ > /X11/ > ... > > (these are just the contents of /etc on each host). The version of tar on > the solaris machine is 1.13. I've heard tar can cause some problems. Do > you think that might be it? > > Thanks for your help! > > Rafe > - This mail sent through IMP: http://horde.org/imp/
Re: amrecover: No index records for host?
This one burned me too :-) Update tar to at least 1.13.17. I've found that 1.13.17 and 1.13.19 both work On Mon, 3 Dec 2001, Rafe Thayer wrote: - Hi Folks, - Another question for ya. After I did an amdump to test out dumping our - disks to tape, I tried to do an amrecover to see if restoring the data - would work. It seems to work for our linux machines, but the solaris box - has some trouble. When I start up amrecover, it reports: - ... - 200 Config set to imash. - 501 No index records for host: hostname. Invalid? - Trying hostname.domainname... - 200 Dump host set to hostname.domainname - ... - - - Then I do a setdisk /etc and it reports: - - 200 Disk set to /etc. - No index records for disk for specified date - If date correct, notify system administrator - - So I figured that the index must not have been created for some reason, - but I checked that out on the server and it looks fine. Has the right - permissions and ownership. The wierd thing is, if I look into the index - files for the host that's giving me trouble, they look a little different - than the others. It looks like this: - - 06573011000/./security/dev/audio - 06573011000/./security/dev/fd0 - 06573011000/./security/dev/sr0 - 06573011000/./security/dev/st0 - 06573011000/./security/dev/st1 - ... - - Whereas for the linux hosts, the index looks like this: - - / - /CORBA/ - /CORBA/servers/ - /X11/ - ... - - (these are just the contents of /etc on each host). The version of tar on - the solaris machine is 1.13. I've heard tar can cause some problems. Do - you think that might be it? - - Thanks for your help! - - Rafe - - -- -- Stephen Carville UNIX and Network Administrator Ace Flood USA 310-342-3602 [EMAIL PROTECTED]
amrecover: No index records for host?
Hi Folks, Another question for ya. After I did an amdump to test out dumping our disks to tape, I tried to do an amrecover to see if restoring the data would work. It seems to work for our linux machines, but the solaris box has some trouble. When I start up amrecover, it reports: ... 200 Config set to imash. 501 No index records for host: hostname. Invalid? Trying hostname.domainname... 200 Dump host set to hostname.domainname ... Then I do a setdisk /etc and it reports: 200 Disk set to /etc. No index records for disk for specified date If date correct, notify system administrator So I figured that the index must not have been created for some reason, but I checked that out on the server and it looks fine. Has the right permissions and ownership. The wierd thing is, if I look into the index files for the host that's giving me trouble, they look a little different than the others. It looks like this: 06573011000/./security/dev/audio 06573011000/./security/dev/fd0 06573011000/./security/dev/sr0 06573011000/./security/dev/st0 06573011000/./security/dev/st1 ... Whereas for the linux hosts, the index looks like this: / /CORBA/ /CORBA/servers/ /X11/ ... (these are just the contents of /etc on each host). The version of tar on the solaris machine is 1.13. I've heard tar can cause some problems. Do you think that might be it? Thanks for your help! Rafe
