Collect True Image Restore With Move Detection

The Collect True Image Restore With Move Detection policy attribute specifies that true-image incremental backups include files that were moved, renamed, or newly installed.

Without move detection, NetBackup skips these files and directories because their modification times are unchanged. With move detection, NetBackup compares path names and inode numbers with those from the previous full or incremental backup. If a name or inode number is new or changed, the file or directory is backed up.

The following are examples where using move detection backs up files that otherwise would not be backed up:

• A file named /home/pub/doc is moved to /home/spec/doc. Here, the modification time is unchanged but /home/spec/doc is new in the /home/spec/ directory and is backed up.
• A directory named /etc/security/dev is renamed as /etc/security/devices. Here, the modification time is unchanged but /etc/security/devices is a new directory and is backed up.
• A file named /home/pub/doc is installed by extracting it from a UNIX tar file. Here, the modification time is before the time of the last backup but the doc is new in the /home/pub/ directory and is backed up.
• A file named docA is removed and then a file named docB is renamed as docA. Here, the new docA has the same name but its inode number changed so it is backed up.

NetBackup starts collecting information required for move detection beginning with the next full or incremental backup for the policy. This first backup after setting the attribute always backs up all files, even if it is an incremental.

Move detection takes space on the client and can fail if there is not enough disk space available.