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 myconfig
name, I still got the same errorno index records for host.
amandaidx service is enabled in xinetd. Please help. Thank you, lei
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
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...
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
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
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
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
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
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
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
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
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
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
13 matches
Mail list logo
