Symptoms

This article is helpful in verifying whether an NFS export is configured correctly.All Data Domain systemsAll Software Releases

Cause

NFS allows a system to share directories and files with others over a network.

Resolution

Verify if NFS is enabled: From the Data Domain Command-Line-Interface (CLI), enable NFS. # nfs enable Verify that the correct mount options are set on the Data Domain system: # nfs show clients path client options ------- ---------------------- ---------------------------------------- /backup * (rw,no_root_squash,no_all_squash,secure) /ddvar * (rw,no_root_squash,no_all_squash,secure) ------- ---------------------- ---------------------------------------- Enabling access to NFS on the Data Domain Restorer: Add NFS clients that can access the Data Domain system. Use a comma- or space-separated (or both) list for multiple clients.A client can be: Fully-qualified domain hostnameIP addressIP range with either netmasks or lengthAn asterisk (*) wildcard with a domain name, such as *.yourcompany.comAn asterisk (*) by itself means no restrictions. A client added to a subdirectory under /backup has access only to that subdirectory. The <nfs-options> are a comma-separated or space-separated (or both) list bounded by parentheses. With no options specified, the default options are rw, root_squash, no_all_squash, and secure. The following options are allowed: ro Read-only permission. rw Read and write permissions. root_squash Map requests from uid/gid 0 to the anonymous uid/gid. no_root_squash Turn off root squashing. all_squash Map all user requests to the anonymous uid/gid. no_all_squash Turn off the mapping of all user requests to the anonymous uid/gid. secure Require that all requests originate on an Internet port that is less than IPPORT_RESERVED (1024). May need "resvport" mount option. See Note below. insecure Turns off the secure option. anonuid=id Set an explicit uid for the anonymous account. The id is an integer bounded from -65635 to 65635. anongid=id Set an explicit gid for the anonymous account. The id is an integer bounded from -65635 to 65635. nolock Do not use file locking. llock Requests that files lock locally at the NFS client. NFS network file locking requests are not sent to the NFS server if the llock option is used. Example: # nfs add /backup 192.168.29.0/24 (rw,no_root_squash,no_all_squash,secure) Export for specific user: CLI Commands: Make note of the user-ID number from first command. Group-ID number is 50 for admin group, and 100 for none or user group. user show list Create new export: nfs add <export-path> <client-IP> (rw,root_squash, all_squash, anonuid=<user-ID #>, anongid=<group-ID #>) Modify existing export: nfs export modify <export-path> clients <client-IP> options (rw,root_squash, all_squash, anonuid=<user-ID #>, anongid=<group-ID #>) NFS Client Service Configuration: The following steps detail the requirements for configuring an NFS client. The examples demonstrate configuration on a Linux host. See the clients operating-specific documentation for additional information. Confirm that the NFSD daemon is running on your Operating System (OS). # /sbin/service nfs status rpc.mountd is stopped nfsd is stopped rpc.rquotad is stopped Currently NFS service is NOT enabled. Issue the following command to enable the NFS client. # /sbin/service nfs start Starting NFS services: [ OK ] Starting NFS quotas: [ OK ] Starting NFS daemon: [ OK ] Starting NFS mountd: [ OK ] Verify that the NFS client service is running. #/sbin/service nfs status rpc.mountd (pid 7748) is running... nfsd (pid 7746 7745 7744 7743 7742 7741 7740 7739) is running... rpc.rquotad (pid 7723) is running... Mounting /backup and /ddvar NFS Shares on the NFS Client: The following procedure provides an example of configuring Linux and Solaris clients to mount NFS shares from the Data Domain system. The procedure is similar for other operating systems; although the specific commands may differ for each step. See the client Operating Systems documentation for specifics.In the following example, the directory "ddr" is used. Create a directory on the NFS client to use for accessing the Data Domain share. Change to the newly created directory.Create two subdirectories called backup and ddvar (within /ddr). NOTE: Ensure the target subdirectories exist or the mount command will fail Mount the file system on the client, using any specific mount-options required for the Operating System.Verify that the mount is successful. Examples Linux: (See Note about "secure" NFS export option below.) # mkdir /ddr # cd /ddr # mkdir backup # mkdir ddvar # mount -t nfs -o hard,intr,nolock,nfsvers=3,tcp,rsize=1048600,wsize=1048600,bg HOSTNAME:/backup /ddr/backup # mount -t nfs -o hard,intr,nolock,nfsvers=3,tcp,rsize=1048600,wsize=1048600,bg HOSTNAME:/ddvar /ddr/ddvar # ls /ddr/backup Where "HOSTNAME" is the hostname or IP address of your Data Domain system. NOTE: About NFS export option "secure": Some versions of Linux defaults to using "resvport" as a mount option.This option corresponds to the NFS export option "secure."macOS and newer Linux versions will require that the option "resvport" be in the mount option if connecting to a NFS export with the "secure" option. Solaris: # mkdir /ddr # cd /ddr # mkdir backup # mkdir ddvar # mount -F nfs -o hard,intr,llock,vers=3,proto=tcp,rsize=1048600,wsize=1048600 HOSTNAME:/backup /ddr/backup # mount -F nfs -o hard,intr,llock,vers=3,proto=tcp,rsize=1048600,wsize=1048600 HOSTNAME:/ddvar /ddr/ddvar # ls /ddr/backup Where "HOSTNAME" is the hostname or IP address of your Data Domain system. AIX: dir /ddr # cd /ddr # mkdir backup # mkdir ddvar # mount -V nfs o intr,hard,llock,rsize=65536,wsize=65536,vers=3,proto=tcp,combehind,timeo=600,retrans=2 -p HOSTNAME:/backup /ddr # mount -V nfs o intr,hard,llock,rsize=65536,wsize=65536,vers=3,proto=tcp,combehind,timeo=600,retrans=2 -p HOSTNAME:/ddvar /ddr # ls /ddr/backup Where "HOSTNAME" is the hostname or IP address of your Data Domain system. Example of how to mount a mtree on a nfs client. # mount -t nfs -o hard,intr,nolock,nfsvers=3,tcp,rsize=1048600,wsize=1048600,bg HOSTNAME:/data/col1/mtree1 /ddr/mtree1

Support Cases