>To: Jim Harmon <[EMAIL PROTECTED]>
>cc: [EMAIL PROTECTED]
>Subject: Re: NFS mounted holding disk
>Date: Fri, 13 Apr 2001 12:11:29 -0500
>From: "John R. Jackson" <[EMAIL PROTECTED]>
>X-Scanner: exiscan *14o7BR-0000Mv-00*QV3l7VyiBh2*
http://duncanthrax.net/exiscan/
>
>>Using a NFS mounted holding disk doesn't seem possible ...
>
>I would consider that a feature :-). Why in the world would you drag
>a bunch of dump images across the network to an Amanda server and then
>send them back across the network, using NFS of all things, then turn
>around and drag them back a third time to finally go to tape? Ick.
>
One reason would be the NFS server has a 1Gb interface and the clients and
tape server have only 100Mb.
In fact I would like it if the clients could dump directly to the NFS mounted
holding disk rather than via the tape server.
The only way I can think of to do this at the moment is to run amdump on each
client and then run amflush on the tape server. The problem apart form managing
all the configs is working out what needs to be shared and having to do the
flush by hand.
What would be nice is an option in the dump type to tell the client to dump
directly to the holding disk. Then this information (with chunksize etc) has
to be passed to the client either as command line option or as part of the
protocol.
>That's more or less a rhetorical question. I fully realize (especially
>with universities :-) that some "unusual" configurations are attempted.
>
>>and I don't
>>understand exactly why. amdump writes to it fine but when amflush tries
>>to write to tape I get:
>>
>>The dumps were flushed to tape dailies02.
>>*** A TAPE ERROR OCCURRED: [[writing file: Bad file number]].
>
>You didn't say what version of Amanda this is, but the only reference I
>see to that error message (in 2.4.2) says it comes from trying to write
>to the tape.
>
>There should have been more messages from amflush. Did you run it with
>the -f (foreground) option? If so, they went to your tty. If not,
>there may be an amflush.<NN> file, or a /tmp/amanda/amflush*debug file.
>It would be interesting to see what it had to say about initially opening
>the tape, etc.
>
>I assume you ran amflush as the Amanda user, i.e. the same user that
>ran amdump?
>
>Did it have anything interesting to say when it showed you what holding
>disk areas it found?
>
>>It's not a bad tape or drive and if the files are on a locally mounted
>>file system it's fine.
>
>So with everything exactly the same except the location of the holding
>disk (same Amanda config, same tape drive, etc), it works?
>
>>Anyone else tried using remote holding disk?
>
>Ummmm, no. :-)
>
>>Jim Harmon
>
>John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Anthony Worrall
The University of Reading,
Department of Computer Science,
Whiteknights, PO Box 225
Reading,
Berkshire, UK
RG6 6AY
Tel: +44 (0)1189 318610
Fax: +44 (0)1189 751994
Email: [EMAIL PROTECTED]
