Skip to main content
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.

Dell NetWorker 19.9 Administration Guide

The ALL save set

The ALL save set is the default save set when you create a Client resource.

Save sets included in the ALL save set

The following table provides a list of the save sets that are in the ALL save set for supported operating systems.

Table 1. Data in the ALL save set
Operating system Files
Windows
  • DISASTER_RECOVERY:\
  • Noncritical volumes
Mac OS X All local and mounted volumes
UNIX
  • When the backup starts, the savefs process reads the contents of the /etc/vfstab file on Solaris clients, the /etc/fstab file on HP-UX and Linux clients, or the /etc/filesystems file on AIX clients. The contents of the file are compared to the currently mounted file systems and BTRFS sub-volumes. Only currently mounted file systems and BTRFS sub-volumes that are configured in these files are backed up. When NetWorker encounters a sub-directory that has a sub-volume ID that differs from the parent sub-volume ID, NetWorker will not backup the contents of the subdirectory, unless you specify the save -x in the Backup command field or select the Cross mount points enabled option in the properties of the Client resource.
  • For a Solaris sparse or whole root zone client, all mounted file systems in the sparse or whole root zone that are not normally skipped, such as NFS, are backed up.
  • ZFS file systems are backed up.
  • If the save set name includes a symbolic link, a save set recovery is not supported.

Save sets excluded from the ALL save set

The following directories, file systems, and files are excluded from the ALL save set:

Table 2. File systems excluded from the ALL save setThis table specifies the file systems excluded from the ALL save set.
  • hsfs
  • proc
  • fd
  • cachefs
  • lofs
  • mntfs
  • ctfs
  • objfs
  • sharefs
  • nfs2
  • nfs3
  • nfs3perf
  • profs
  • nfs4
  • nfs
  • brfs
  • dfs
  • autofs
  • iso9060
  • udf
  • sysfs
  • debugfs
  • subfs
  • usbdevfs
  • binfmt_misc
  • usbfs
  • devpts
  • cifs
  • swap
  • tmp
  • tmpfs
  • nucfs
  • nucam
  • fdfs
  • xx
  • none
NOTE:When you use the ALL save set for a backup, the NetWorker software creates a temporary file similar to a directive under each drive. The file name uses the format drive guid.txt and lists the files that are excluded from the backup. The file is temporary and is automatically deleted when the backup completes.

Keywords for scheduled file system backups

You can use special keywords with the ALL save set to define the file systems to include in a backup. The following table provides a list of the special ALL save sets and the backup behavior.

Table 3. Special ALL save sets This table provides the Special ALL save set syntax and backup behaviour.
Special ALL save set syntax Backup behavior
all-file_system
  • Only back up locally mounted file systems of a particular type, where file_system is zfs, ntfs, btrfs, or ext3. For example:
    • all-zfs backs up all locally mounted ZFS file systems on a Solaris host.
    • all-btrfs backs up all mounted BTRFS sub-volumes that appear in the /etc/fstab file.
  • File systems such as NFS that are normally skipped are still skipped.
  • The NetWorker E-LAB Navigator provides a list of the supported file system for each operating system.
all-mounts
  • On UNIX clients, back up all currently mounted file systems.
  • On Windows clients, the all-mounts save set is equivalent to the ALL save set.
  • File systems such as NFS that are normally skipped are still skipped.
all-local
  • For a global zone client, the file systems in the sparse or whole root zone on the physical host are backed up. File systems in the global zone are skipped.
  • For a sparse or whole root zone client, the all-local save set is equivalent to the ALL save set.
all-global
  • For a global zone client, all file systems in the global zone are backed up. All sparse and whole root zone file systems on the physical host are skipped.
  • For a Solaris sparse or whole root zone client, the all-global save set is equivalent to the ALL save set.

Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\