|
It will not work for NFS. NFS is working based on server
hand over an opaque packet to the client. Client since
then will communicate with the server based on that opaque
handle. Normal NFS construct that opaque handle involves
some file system ID from that particular server, which most
likely will be different from one server to the other.
At 04:06 PM 9/1/00 -0400, Jeremy Hansen wrote:
>I've never tried this myself, but I'm curious, can nfs handle picking up
>client machine in a failover situation. If my primary nfs server dies,
>and my secondary takes over the first, can nfs clients handle this?
>Something tells me nfs wouldn't be very happy in this situation.
>
>Thanks
>-jeremy
>
>> On Fri, 1 Sep 2000, Matthew Enger wrote:
>>
>> > Hello,
>> > I am looking into running two NFS servers, one as a backup for
>> > serving lots of small text files and am wondering what would be the best
>> > solution for doing this. Does anyone have any recomendations.
>>
>> I assume you are wondering if balancing NFS servers behind a director is a
>> good idea. LVS handles NFS just fine (see the performance document on the
>> docs page of the lvs website and will make a good file server. You have to
>> handle the problem of writes yourself to keep both NFS servers in sync.
>>
>> Joe
>>
>> >
>> >
>>
>> --
>> Joseph Mack mack@xxxxxxxxxxx
>>
>>
>>
>
>eholes.org * jeremy@xxxxxxxxxx
>-----------------------------------------
>eholes have feelings too...
>
>
>
|
