Thanks Jean...your idea works great..why hasn't this been
incorporated previously by chance
Don
Don Potter wrote:
Thanks I setup a cname for the interim which works well until I test
out the hacked amrecover.
Looking at the diff..are you basically taking the extrapolation
On Mon, Mar 18, 2002 at 04:21:22PM -0500, Don Potter wrote:
Thanks Jean...your idea works great..why hasn't this been
incorporated previously by chance
Because nobody reported this problem :-)
Jean-Louis
Jean-Louis Martineau wrote:
Hi Don,
Try this patch on the client, it
Thanks I setup a cname for the interim which works well until I test out
the hacked amrecover.
Looking at the diff..are you basically taking the extrapolation portion
for the disk_regex to setup host_regex, so basically redoing the same
procedure???
That is what I'm getting from this so far.
Thanks Jean...your idea works great..why hasn't this been
incorporated previously by chance
Don
Don Potter wrote:
Thanks I setup a cname for the interim which works well until I test
out the hacked amrecover.
Looking at the diff..are you basically taking the extrapolation
Hi Don,
Try this patch on the client, it makes a stricker pattern by enclosing
it in ^$
Jean-Louis
PS. The patch is untested.
On Fri, Mar 15, 2002 at 10:35:34AM -0500, Don Potter wrote:
Being that I'm restricted to using only the name since the expresion is
ported to amrestore when I do
Okay, this makes no sense whatsoever. This is only occuring on one
filesystem, and it is sporadic in occurances there. When ever I
attempt to do a amrecover of the directory on /var/mail I get the
following:
But I can dd the file from tape and extract it doing a straight
ufsrestore from
... When ever I
attempt to do a amrecover of the directory on /var/mail I get the
following:
Ummm, you didn't post what amrecover was saying. That might help :-).
But I'll save you one round trip. What's in the corresponding
/tmp/amanda/amrecover*debug file. Should be something like
