On Fri, 20 Apr 2001, John R. Jackson wrote:
> If those files are truely in the holding disk (i.e. you didn't bring
> them back from tape), amrestore (certainly in 2.4.2 and I think before
> that) already knows how to read from the holding disk and will do all
> the chaining for you. So it would be:
>
> amrestore -p /path/to/mmri1001._2.0 | tar tf ...
ran into a problem...
the holding disk is nfs-exported from the amanda server to the client i'm
restoring. i access this nfs share via the path /net/server/path. the
client is mmri1001, the server is mmri1011. so, on mmri1001 i did:
amrestore -p /net/mmri1011/2/amanda/20010420/mmri1001._2.0 | tar xvf -
it got through the first chunk and then reported:
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?
--
Todd Pfaff \ Email: [EMAIL PROTECTED]
Computing and Information Services \ Voice: (905) 525-9140 x22920
ABB 132 \ FAX: (905) 528-3773
McMaster University \
Hamilton, Ontario, Canada L8S 4M1 \
