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
security: remote host foo.bar.com user root local user amanda
amandahosts security check passed
200 Access OK
DATE 2003-01-13
200 Working date set to 2003-01-13.
SCNF Daily
200 Config set to Daily.
HOST foo.bar.com
501 No index records for host: foo.bar.com. Invalid?
HOST foo.bar.com
501
However, doing a setdisk /data/mm5_uw/calmm5 produces the
same result (appended to the debug file):
DISK /data/mm5_uw/calmm5/
501 No index records for disk: /data/mm5_uw/calmm5/. Invalid?
Bingo (maybe!).
I think you did:
amrecover setdisk /data/mm5_uw/calmm5/
and you
to Daily.
501 No index records for host: foo.bar.com. Invalid?
Trying foo.bar.com ...
501 No index records for host: foo.bar.com. Invalid?
Trying foo ...
200 Dump host set to foo.
Can't determine disk and mount point from $CWD
And yet the entry in /var/lib/amanda/Daily/index/foo for the directory
[root]% amrecover
AMRECOVER Version 2.4.2p2. Contacting server on foo.bar.com ...
220 foo AMANDA index server (2.4.2p2) ready.
200 Access OK
Setting restore date to today (2003-01-10)
200 Working date set to 2003-01-10.
200 Config set to Daily.
501 No index records for host
--On Friday, January 03, 2003 22:18:18 -0500 John R. Jackson [EMAIL PROTECTED] wrote:
Is there a reason indexing isn't on by default? They don't really take up
that much space ...
I beg to differ:
$ du -sk /var/amanda/index/champion
4641743 /var/amanda/index/champion
Yup. Four
On Saturday 04 January 2003 03:03, Frank Smith wrote:
--On Friday, January 03, 2003 22:18:18 -0500 John R. Jackson
[EMAIL PROTECTED] wrote:
Is there a reason indexing isn't on by default? They don't
really take up that much space ...
I beg to differ:
$ du -sk /var/amanda/index/champion
On Sat, Jan 04, 2003 at 04:55:37AM -0500, Gene Heskett wrote:
On Saturday 04 January 2003 03:03, Frank Smith wrote:
--On Friday, January 03, 2003 22:18:18 -0500 John R. Jackson
[EMAIL PROTECTED] wrote:
[...]
Just curious as why some of the defaults are the way they are.
Ah, now that's a
On Sat, Jan 04, 2003 at 12:21:44PM -0500, Jon LaBadie wrote:
Some more data points from a 2.4.2 user.
The exclude list option is defined in the root-tar dumptype in both
2.4.2 and 2.4.3. So no change there. No surprises for anyone.
amcheck in my installation (2.4.2) does not complain if
Is there a reason indexing isn't on by default? They don't really take up
that much space ...
I beg to differ:
$ du -sk /var/amanda/index/champion
4641743 /var/amanda/index/champion
Yup. Four and a half *GBytes*.
Now, granted, this is on a very large Amanda configuration. But it's
not
[root@backup DailySet1]# amrecover
AMRECOVER Version 2.4.2p2. Contacting server on localhost ...
220 backup AMANDA index server (2.4.2p2) ready.
200 Access OK
Setting restore date to today (2002-12-19)
200 Working date set to 2002-12-19.
200 Config set to DailySet1.
501 No index records for host
Working date set to 2002-12-19.
200 Config set to DailySet1.
501 No index records for host: backup.indyme.local. Invalid?
Trying backup.indyme.local ...
501 No index records for host: backup.indyme.local. Invalid?
Trying backup ...
501 No index records for host: backup. Invalid?
amrecover quit
200
--On Thursday, December 19, 2002 18:53:44 -0500 Steve Bertrand [EMAIL PROTECTED] wrote:
In order to have indexing on your backups, you must specify 'index yes' inside of the backup type in amanda .conf. ie:
define dumptype nocomp-user {
comp-user
comment Whatever comment you want
On Thu, Dec 19, 2002 at 06:53:44PM -0500, Steve Bertrand wrote:
In order to have indexing on your backups, you must specify 'index yes'
inside of the backup type in amanda .conf. ie:
define dumptype nocomp-user {
comp-user
comment Whatever comment you want
compress client fast
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
.
--- 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
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
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
Hello,
Can someone please update the FAQ under Troubleshooting, amrecover:
For the following errors:
501 No index records for host:
500 No dumps available on or before date
Further to what the FAQ says is to get back to basics and
set the permissions correctly on the holding disk, so
[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
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
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
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
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
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
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
, but there is no index records
for the host on any backup date. The other machine is solaris 8. The
amanda box is Linux. If I look in daily/index/flare/_etc, there are
.gz files for all the dates.
What are you using to backup flare? If tar, what version?
Do the contents of the index files look
OK, the server that runs the amanda stuff is what gets backed up. I
added another host to the list, flare:/etc. It seems to backup fine;
I get a size and time and everything in the email reports. When I run
amrecover, I can sethost and setdisk, but there is no index records
for the host on any
29 matches
Mail list logo
