To back up Unix data (at a local or remote mount point) to a vault, you can use Network File System (NFS) on Linux, AIX, Solaris, and HP-UX.
In the Web Agent Console application, create a new Job, and select “NFS Files” from the dropdown list.
NFS servers must share their exports in order to make them available to client systems. If you currently run a Unix Agent on an NFS client system, and you want to perform a mount-point backup or restore, the NFS server must be available, and it must provide sufficient privileges to your client system. Also, the NFS must be mounted on your client system at the time of the backup or restore.
Notes
If you restore an NFS backup, and the NFS mount does not exist, the restore will proceed as if it were local. It will put the data on the local disk (using a similar but local path) without using a mount-point (NFS) path. The Job does not indicate any sort of failure. If the local disk does not have sufficient space, this can cause a problem.
A user might not realize that the restore has occurred locally. If overwriting is enabled, the restore will overwrite the local data (while the user intended to overwrite the mount-point data).
Refreshing the NFS browse list
In Web Agent Console, Network File Systems are displayed and selectable for backup as local file systems.
Because "object browsed” events are cached for performance purposes, NFS mounts are treated as local file systems at first. If you expand a folder that has already been loaded, you might not see all of the files until the folder is refreshed.
If there is no activity for more than three minutes (the timeout period), the Agent will refresh the mounted file system on the next request (and display all of the files). To refresh immediately, you must exit and re-enter the selection panel. That is, you need to stop and start the Wizard again.