•   There are several files/paths NetBackup will not backup by default
•   ALL_LOCAL_DRIVES will exclude some files
•   Using / in backup selections will not back up some files

•   Unable to locate certain files for restore
•   Full restore of client operating system may not include all expected files
•   Solaris 10 client will not boot after full restore from global zone backup completed

• NFS files or directories, unless you set Follow NFS. These files are likely backed up by the home host.
• Files or directories in a different file system if you do not set Cross Mount Points or include those mount points in
• Files or directories with path lengths longer than 1023 characters.
• Files or directories where the operating system does not return inode information (the lstat system call failed).
• Directories that NetBackup cannot access (cannot use the cd command to access).
• On a disk managed by Storage Migrator, migrated files or directories where Storage Migrator does not return inode information (mig_stat fails). Note that NetBackup Server does not support Storage Migrator.
• Socket special files (named pipes are backed up).
• Door files
• Locked files when mandatory locking is enabled by an application that currently has the file open.
• Busy files. If a file is open, NetBackup backs up the last saved version of the file.

 NetBackup automatically excludes the following file system types on most platforms:

• cdrom (all UNIX/Linux platforms)
• cachefs (AIX, Solaris, SGI, UnixWare)
• devpts (Linux)
• mntfs (Solaris)
• proc (UNIX/Linux platforms; does not exclude automatically for AIX, so /proc must be added manually to exclude list. If not added manually, partially successful backups may result when using the ALL_LOCAL_DRIVES directive on AIX)
• tmpfs (Linux)
• usbdevfs