NFSv4 configuration

Overview

Understand which OS versions support NFSv4. NFSv4 is enabled by default, but the target/staging hosts require additional configuration changes before you can use it.

Redhat/SLES: NFSv4 Only - Enabling Recover Lost Locks

AIX: IBM AIX

AIX systems

While NFSv4 no longer uses the portmap (or rpcbind) service for network communication, and firewalls do not need to allow traffic on port 111, the portmap service must still be running locally on both the AIX client and the Delphix engine.

Disabling the portmap daemon can prevent NFSv4 mounts from working correctly on AIX, even if everything else is configured properly.

OS version

NSFv4 support

RHEL 6.4 or later

Supported

SLES 11.4 or later

Supported

AIX 7.1, 7.2

Supported

Solaris 11

Supported

If these target host configurations are not set, the engine chooses NFSv3. You can see the provided reason (e.g., "OS not supported") for choosing NFSv3 over NFSv4 under the Status tab of your selected VDB in the Delphix engine GUI. Additional information is provided in this tab for datasets and current values.

Dataset status tab NFS reasons

NFS Reason

Notes

Default

NFSv4 is used by default for client mounts.

Old RedHat

NFSv4 is used with RedHat versions 6.4 and newer.

Unsupported OS

NFSv4 is not supported for HP-UX clients.

DNFS

Oracle Direct NFS (dNFS) is in use by the database. NFSv4 is supported by dNFS with Oracle versions 12c and newer.
Cannot use NFSv4 with dNFS for Oracle versions between 19.12 and 19.15 dNFS is in use by the database. dNFS does not work with NFSv4 in Oracle versions 19.12-19.15 due to Oracle bug 33596056.
Cannot use NFSv4 with dNFS for Oracle versions between 21.1 and 21.6 dNFS is in use by the database. dNFS does not work with NFSv4 in Oracle versions 21.1-21.6 due to Oracle bug 33596056.
Cannot use NFSv4 with dNFS for Oracle versions less than 12c dNFS is in use by the database. dNFS does not work with NFSv4 in Oracle versions less than 12c.

Tunable Override

The nfs.version tunable is set to force NFSv3 mounts.

Configuration Override

Appears with default operation, implies that a configuration parameter has changed.

No Recover Lost Locks

On Linux hosts, if the required recover_lost_locks setting is not enabled for the NFS client, then NFSv4 cannot be used.

Incomplete v4 Config

On AIX hosts, if the nfsrgyd daemon is not running or reverse DNS lookup is missing, then NFSv4 cannot be used.

NFSv4-Only mode

A Delphix Engine can be configured only to use NFSv4 and disable NFSv3 services.

Behavioral Differences Compared to Automatic (default):

  • If NFSv4 is not supported on the mount, the Delphix engine fails to mount the VDBs and returns a user exception with the reason "NFSv4 is not supported". 

  • If dNFS is enabled, the Delphix Engine attempts to use NFSv4 in Oracle versions 19.12-19.15 and 21.1-21.6 despite Oracle bug 33596056. Additional details are in this Knowledge Base article.

NFSv4-Only mode disables NFSv3

  • If existing VDBs on a Continuous Data engine use NFSv3, they go down because the mounts no longer serve data once you enable NFSv4-Only mode.

  • If the Continuous Compliance engine uses NFSv3 via remote mounts, they can not access data when you enable NFSv4-Only mode.

This configuration is available via the System Administration CLI.