Chat now with support
Chat with Support

NetVault Plug-in for FileSystem 13.1.2 - User Guide

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 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 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.
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.

Performing Incremental and Differential Backups

In Job Name, specify a name for the job.
In the Selections list, select the Backup Selection Set that was used to perform the Full Backup.
In the Plugin Options list, select an existing Backup Options Set, or complete the following steps to create a new set:
Click Create New to open the File System Plugin Backup Options page.

Backup Method

Under Backup Method, select the applicable option:

Standard: For native file system backups, select the option. It is the only available method on Linux and UNIX systems.
Snapshot-Based: On Windows systems that support VSS, select this option to perform a snapshot-based backup.

For more information about backup methods, see About backup methods.

Backup Type

Under Backup Type, select the applicable option. For more information about backup types, see About backup types.

Incremental: Select this option to back up files that were created or modified since the last Full, Incremental, or Differential Backup.
Differential: Select this option to back up files that were created or modified since the last Full Backup.
Create Dump Type Backup: Select this check box to create Dump Type Incremental or Differential Backups.

Dump Type Incremental Backups are standalone Incremental Backups. Such backups can be copied without creating a copy of any other backup in the backup sequence.

Ignore Archive Bit

On Windows, the archive bit helps to determine whether a file has been modified since the last backup. If the file has changed, the archive bit is set to 1, and if the file has not changed, the bit is set to 0. By default, the plug-in backs up a file for which the archive bit is set to 1, and clears the bit after the backup completes.

Regardless of the state of the archive bit, the plug-in backs up a file if certain information, such as the file size or the last modified time, has changed since the previous backup.

To ignore the archive bit settings and use the file size, last update date, and other file attributes to back up a file, select the Ignore Archive Bit check box. This option can be useful in the following events:

When you select the Ignore Archive Bit check box, the plug-in omits the files and directories for which only the file attributes such as Discretionary Access Control List (DACL), System Access Control List (SACL), and Owner Attribute have changed. If you want to back up such files, do not select this check box.

Click Save, and in the Create New Set dialog box, type a name for the set. Click Save to close the dialog box.
To submit the job for scheduling, click Save & Submit. You can monitor the job progress from the Job Status page and view the logs from the View Logs page.
To save the job definition without scheduling it, click Save. You can view, edit, or run this job from the Manage Job Definitions page. This job is not displayed on the Job Status page until you submit it.
For more information about Job Status, View Logs, and Manage Job Definitions, see the Quest NetVault Administrator’s Guide.

Stopping a job

The NetVault lets you stop a job at any point and resume it later from the same point. To have this ability, you must configure the job as restartable

For more information about this option, see the Performing Full Backups.

When you stop the job, the plug-in generates an index for all items that have been processed up to that point and writes the index to the backup media and NetVault Database. The job status is then set to Job Stopped. If the plug-in is writing a large backup index, the jobs status continues to be reported as “Writing to Media: Storing Backup Index” until the index is written. When you restart the job later, the plug-in runs an Incremental Backup job to back up the remaining files and folders.

NOTE: The Stop and Restart methods do not work if you select multiple job instances simultaneously.

Multi-stream backups that are in progress may not be affected by the Stop action, as stopping a backup does not interrupt streaming data. Any data submitted to a stream during the backup job continues to back up. After the in-progress stream is complete, no new streams begin.

Restarting a job

The Restart method lets you resume a backup from the point the job was stopped. To have this ability, you must configure the job as restartable. When you restart a job, the plug-in runs an Incremental Backup job to back up the remaining files and folders.

NOTE: The Stop and Restart methods do not work if you select multiple jobs simultaneously.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating