Chat now with support
Chat with Support

Please note, you may experience access issues between 6am - 7am Eastern time on Saturday, May 28 2022 due to planned maintenance

NetVault Plug-in for FileSystem 13.0.2 - User Guide

Inclusion list considerations

Adding an inclusion list

On the NetVault Selections page, open the NetVault Client to which you want to add the inclusion list.
In the list of plug-ins, select File System, and click Show inclusion lists.
Open the Inclusion Lists node.
Open Browse for inclusion files.
Select Specify inclusion files and click Add inclusion file.
In the Enter path to inclusion file dialog box, type the file path for the inclusion list.

Removing an inclusion list

On the NetVault Selections page, open the applicable NetVault machine.
In the list of plug-ins, select File System, and click Show inclusion lists.
Open the Inclusion Lists node.
Depending on the method used to add the Inclusion List, open Browse for inclusion files or Specify inclusion files. Open the directory tree, if applicable, and clear the check box corresponding to the Inclusion List.

Additional notes

Backup file path length limitations: The maximum length of a backup file path depends on the operating system and the file system the data resides on.
For backups of Linux and UNIX clients, NetVault uses the cpio tape format that does not impose these limitations. However, OS imposed limitations do apply. For more information about the OS imposed limitations, see the relevant OS documentation.
Hard links on Linux- and UNIX-based clients: Various instances of hard-linked files on the Linux and UNIX clients are considered separate entities. The NetVault Plug‑in for FileSystem backs up the complete file and the link information for each selected hard-linked file. To back up all instances of a hard-linked file, include each instance in the selection.
Symbolic links on Linux- and UNIX-based clients: When a symbolic link is explicitly selected for a backup, only the link information is backed up. The plug-in does not back up the file or directory the link points to.
Solaris zones partitioning: On systems using the Solaris Zones Partitioning Technology, the non‑global zones share files with the global zone using loopback file system read-only mounts, usually /usr, /lib, /sbin, and /platform. When the global zone (that is, “/”) is selected for a file system backup, these directories are backed up for the global zone and for each zone configured on the system. For example, if four zones are configured on the system and root is selected for a file system backup, the plug-in backs up five copies of the global zone directories. To avoid multiple backups of the directories during the global zone backup, de-select them individually, or create an exclusion list
Special mount points: The NetVault Plug‑in for FileSystem treats certain file system types as special mount points, and does recurse into these mount points. However, the mount point itself, which is a directory, is backed up.
Consider a Linux client on which the proc file system is mounted as follows:

Linux and HP-UX

FreeBSD and Mac OS X




Special files: On Solaris, doors are not backed up. On Linux and UNIX, sockets are not backed up.
Windows registry keys: On Windows, the files listed under the following registry keys are not backed up:
Distributed File System (DFS) paths: If a user account configured to access the root node in the DFS tree does not have access to the shared folders, a symbolic link icon accompanies the shares instead of a folder icon. If the user does not have necessary privileges, a backup completes with warnings.
The NetVault Plug‑in for FileSystem only backs up the DFS files and directories; it does not back up the DFS tree. If the tree structure does not exist during restore, the data is restored to the local file system.
Extended attributes on NSS volumes: To back up and restore the novell.metadata extended attributes on NSS volumes, install the attr package, and enable ListXattrNWMetadata and CtimeIsMetadataModTime switches. The following example illustrates how to enable these switches from the NSS Console (NSSCON):
Cluster data: While backing up cluster data using a virtual client, only the LUNs owned by the active node are backed up; LUNs owned by passive nodes are not backed up.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating