questions!
Thanks for the help!
g
- Forwarded message from gj [EMAIL PROTECTED] -
Date: Tue, 26 Apr 2005 21:23:59 +0100
From: gj [EMAIL PROTECTED]
Reply-To: gj [EMAIL PROTECTED]
Subject: Re: q: amrecover, directories okay but no files
To: amanda-users@amanda.org
Sorry
On Mon, May 02, 2005 at 12:08:08PM +0100, gj enlightened us:
I finally have some more clarifying(?) details of my problem(s) that some of
you
were asking for!
The amrecover error I am writing about in this email is slightly different
from
the problem in my original post, but perhaps they
How about the indexes for the questionable DLE's.
Do they show the files you expect were in fact backed up?
The indexes should show everything on the tape.
If indexes are the listings you get when you ls in amrecover, then the
indexes seem to stop at certain subdirectories. That is, when I ls
gj wrote:
If indexes are the listings you get when you ls in amrecover, then the
indexes seem to stop at certain subdirectories. That is, when I ls in the
subdirectory (listed in the index) where the file to be recovered is, I only
get a . (no files listed even though the original machine had
Maybe the tar or dump process that is doing the actual recovery simply
hasn't finished yet. It doesn't stop after having recovered the file you
requested, it goes through the entire backup image in any case. With big
backup images this may take some time.
Yes, I was hoping that was the case
On Sun, Apr 17, 2005 at 04:57:13PM +0100, gj wrote:
Maybe the tar or dump process that is doing the actual recovery simply
hasn't finished yet. It doesn't stop after having recovered the file you
requested, it goes through the entire backup image in any case. With big
backup images this
gj wrote:
In case this may be related, sometimes when I am successful in
extracting/recovering a file, amrecover stalls. When I wait awhile, I see in a
different terminal that the file has been recovered, but I don't get the
amrecover prompt back and I need to ^C to quit.
Maybe the tar or dump
Hi,
I'm testing out my backup system and randomly selecting files from different
hosts to recover (with amrecover). Even though I would not have an error
message associated with the DLE I'm trying to recover files from, I've found
that amrecover reports that there are no files in the folder in
