On Apr 5, 2006, at 2:43 AM — 4/5/06, Scott Russell wrote:
Greets.
I've got an odd thing going on with a recovery I'm doing where old
files are recovered instead of
the current file. The example below talks about the /etc directory
which is part of the / saveset of
my RHEL4u3 box. I'm running 7.3 client and server.
In the recover shell I can add the entire /etc/ directory for
recovery like so:
[root@dotbak tmp]# recover -c imap -s dotbak
recover: Current working directory is /var/tmp/
recover> relocate /var/tmp
recover> add -q /etc
2245 file(s) marked for recovery
Scott, I do not run 7.3, but you have me curious. What happens if you
change you recovery process a bit?
What happens if you do the following:
cd /etc
recover -c imap -s dotbak
relocate /var/tmp
add -q .
recover
or if /etc does not exist, how about ...
recover -c imap -s dotbak
cd /etc
relocate /var/tmp
add -q .
recover
I am not suggesting either method will resolve your problem, I am
only curious if you get the same results.
To sign off this list, send email to listserv AT listserv.temple DOT edu and type
"signoff networker" in the
body of the email. Please write to networker-request AT listserv.temple DOT edu
if you have any problems
wit this list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
| 