When implementing NFS with a Dell EMC Data Domain system, why should hard mounts be used?

Question

Options

• AEnable backups of individual mounts
• BEnsure server availability after reboots or outages
• CPrevent non-administrators from accessing the mounts
• DEnsure availability ofmounts through other protocol

• A
  8% (3)
• B
  78% (29)
• C
  11% (4)
• D
  3% (1)

Explanation

If you have mounted the NFS filesystem using hard mount, it will repeatedly retry to contact the server. Once the server is back online, the program will continue to execute undisturbed from the state where it was during server crash. We can use the mount option "intr" which allows NFS requests to be interrupted if the server goes down or cannot be reached. Hence the recommended settings are hard and intr options. Note: Soft Mount Suppose you have mounted a NFS filesystem using "soft mount". When a program or application requests a file from the NFS filesystem, NFS client daemons will try to retrieve the data from the NFS server. But, if it doesn't get any response from the NFS server (due to any crash or failure of NFS server), the NFS client will report an error to the process on the client machine requesting the file access. The advantage of this mechanism is "fast responsiveness" as it doesn't wait for the NFS server to respond. But the main disadvantage of this method is data corruption or loss of data. So this is not a recommended option to use. https://linoxide.com/nfs/difference-soft-hard-nfs-mount/

No community discussion yet for this question.