>amrestore: can't open /2/amanda/20010420/mmri1001._2.0.1: No such file or
>directory
>
>huh? why did amrestore trim /net/mmri1011 off the path?
That's why I asked if the files were really in the holding disk.
They only sort of are in your case.
To deal with multiple holding disks and chunks being scattered around,
the header on the files contains a link to the next file. It's absolute
and valid from the server point of view. I suspect that's something we
need to think about in the future (I can see it causing other problems),
but is certainly nailing you right now.
Any chance you can create temporary symlinks on the client to emulate
the server holding disk structure? Like "ln -s /net/mmri1011/2 /2"?
Or, another approach is to run amrestore on the server and rsh/ssh the
image back to the client:
mmri1001 # rsh mmri1011 amrestore -p /2/amanda/20010420/mmri1001._2.0 | tar ...
Or you can always use emacs and so some binary editing :-).
>Todd Pfaff
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
