[TriLUG] Add Another NFS Client to NFS Server

[Ron Kelley via TriLUG]

From what I have experienced, performance of NFS relies on the number of NFS daemons running on the server side (RPCNFSDCOUNT= in the /etc/sysconfig/nfs file), the total network through-put of the server (as in 2x1G connections, etc), and the speed of the underlying disk system.  

For example, if you have a single 1G connection on your NFS server, don’t expect both clients to write at full 1G speed at the same time - there is not enough network bandwidth to support both connections.  Likewise, if you have slow disks, you will have performance issues if both clients write at the same time.  

As for the client connections, you can use a single share point as you suggested earlier.  Just stagger the backups at different times so as to not overwhelm the NFS server.



> On Jun 1, 2017, at 7:47 PM, Alan Sterger via TriLUG <trilug at trilug.org> wrote:
> 
> Are performance considerations something that would make either approach better?  I'm performing Oracle RMAN backups from both clients to the NFS server.  I assumed I would need to stagger RMAN's kickoff timing on each client as to not overwhelm the pipe and/or server.  Therefore, I assumed I need a new export path as I'm using '*' as the host id in /etc/exports.
> 
> How would I mount and configure /etc/exports if I didn't NEED a new export path?
> 
> Thanks,
> 
> -- Alan Sterger
> 
> On 6/1/17 7:08 PM, William Sutton wrote:
>> Do you want separate exports for separate clients, or do you want a single export for both clients?
>> 
>> If the former, then your proposal should work.
>> 
>> If the latter, your existing export config is fine (because you don't NEED to add a new export path every time you add a new client).
>> 
>> William Sutton
>> 
>> On Thu, 1 Jun 2017, Alan Sterger via TriLUG wrote:
>> 
>>> Hello Group,
>>> 
>>> Want to add another NFS4 client with its own mountpoint for a total of 2 NFS clients.  The new client need only communicate with the server. Currently have 1 client enabled and it works fine but am scratching my head as to correct method of integrating a second client.
>>> 
>>> Current server-side /etc/exports file with a single client:
>>> /nfs_share *(rw,no_wdelay,no_root_squash,no_all_squash,no_subtree_check)
>>> 
>>> There isn't any active name service and client IP addresses ping but do not resolve, hence the '*' in the host slot (not my system).
>>> 
>>> I suppose going forward I could mofify /etc/exports to:
>>> /nfs_share_db1 *(rw,no_wdelay,no_root_squash,no_all_squash,no_subtree_check)
>>> /nfs_share_db2 *(rw,no_wdelay,no_root_squash,no_all_squash,no_subtree_check)
>>> 
>>> Good enough approach?  Comments?
>>> 
>>> Thanks for any feedback,
>>> 
>>> Alan Sterger
>>> -- 
>>> This message was sent to: William <william at trilug.org>
>>> To unsubscribe, send a blank message to trilug-leave at trilug.org from that address.
>>> TriLUG mailing list : https://www.trilug.org/mailman/listinfo/trilug
>>> Unsubscribe or edit options on the web    : https://www.trilug.org/mailman/options/trilug/william%40trilug.org
>>> Welcome to TriLUG: http://trilug.org/welcome
>> 
> 
> -- 
> This message was sent to: Ron Kelley <rkelleyrtp at gmail.com>
> To unsubscribe, send a blank message to trilug-leave at trilug.org from that address.
> TriLUG mailing list : https://www.trilug.org/mailman/listinfo/trilug
> Unsubscribe or edit options on the web	: https://www.trilug.org/mailman/options/trilug/rkelleyrtp%40gmail.com
> Welcome to TriLUG: http://trilug.org/welcome