Hello James,
What's the output of 'amadmin config find'?, amrecover will not
use a dump that is not listed.
Could you also provide your amindexd.*.debug file.
Jean-Louis
On Fri, Oct 04, 2002 at 01:39:03PM -0400, James Shearer wrote:
Hello.
I am new to amanda, and recently attempted a test
Hello.
I am new to amanda, and recently attempted a test recovery using amrecover.
Alas, I did not get very far. I recieved the No index records for disk for
specified date error, despite having enabled indexing in my amanda.conf.
Google turned up alot of hits for this error, one of which
I get this error every time I run amrecover from a directory that isn't
in my disklist, or from a host that isn't the backup server.
Try using the sethost, setdisk, and setdate commands in amrecover.
For example:
sbs|amv: /tmp sudo amrecover Gemini
AMRECOVER Version 2.4.2p2.
I get this error every time I run amrecover from a directory that isn't
in my disklist, or from a host that isn't the backup server.
Try using the sethost, setdisk, and setdate commands in amrecover.
Yep. I've tried that before. It's still no good, as you can see:
#
--On Friday, October 04, 2002 13:39:03 -0400 James Shearer [EMAIL PROTECTED] wrote:
Hello.
I am new to amanda, and recently attempted a test recovery using amrecover.
Alas, I did not get very far. I recieved the No index records for disk for
specified date error, despite having enabled
I'm not sure editing is a fix. Someone on this list reported that
restoring
from one of the bad tar archives resulted in the files being OK but the
directories were all renamed (I think to big numbers), and that if you
knew what the paths were supposed to be you could (with a lot of work)
Well, so much for that. . .
What do the directories and data look like in your curinfo directory? I
don't remember if that tar problem corrupts it also.
Anthony
On Fri, 2002-10-04 at 10:26, James Shearer wrote:
I get this error every time I run amrecover from a directory that isn't
On Fri, Oct 04, 2002 at 02:26:36PM -0400, James Shearer wrote:
I get this error every time I run amrecover from a directory that isn't
in my disklist, or from a host that isn't the backup server.
Try using the sethost, setdisk, and setdate commands in amrecover.
Yep. I've tried
