Title: Plan an NFS Implementation
Course: CIS 208: Linux/UNIX III: Intermediate System Administration, Networking, and Security ~ For IGNITE Review > Section: Learning Modules

Plan an NFS Implementation

The Network File System (NFS) protocol is the preferred method of sharing a filesystem in a Unix and Linux environment.  It has several features that make if useful both in the enterprise and in a smaller environment.

- It fully supports normal file permissions.
- Ownership is based on operating system user accounts.
- It is ideal for sharing data directories accessed by servers.
- Can provide users with a single home directory available on any workstation.
- Provides a central location for user data which is easy to backup and restore.

Planning for NFS begins with options for the servers:

- Choose between v3 (the standard) and v4 (if special features are required).
- Select the number of servers to be used.  In a small environment one server will suffice, however one or more servers may be needed per project.
- For each server, create a list of shares, then decide how much disk space will be required for each.
- Create a separate partition for each share that needs a dedicated amount.

As part of the preparation, it will be necessary to ensure that a given user account on the server match the UID of the same account on every client.  If all hosts use a directory service, the UIDs will match.  If each host maintains its own user database, they will need to be synchronized.  To plan this:

- Create a list of all users who will access the NFS shares.
- Devise a UID and GID numbering scheme for these accounts selecting numbers that are not currently in use.  If the current UID or GID is less than 500, try to not change it unless necessary.  If the current UID or GID is over 499, start at a higher number, perhaps 10000.
- Each host will need to be updated or verified before implementation.