|
|
The Collect true image restore information with move detection attribute specifies what true image incremental backups should include. Enable this attribute to include the files that were moved, renamed, or newly installed from a tar or a zip archive. (Depending on how the files were packaged and how they were installed, some newly installed files are not backed up by non-TIR incremental backups.)
Without move detection, NetBackup skips the files and directories that were moved, renamed, or newly installed 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 an inode number is new or changed, the file or directory is backed up.
The following examples show how move detection backs up the files that otherwise would not be backed up:
A file that is named C:\pub\doc is moved to or installed in C:\spec\doc. Here, the archive bit is unchanged but C:\spec\doc is new in the C:\spec\ directory and is backed up.
A directory that is named C:\security\dev\ is renamed as C:\security\devices\. Here, the archive bit is unchanged but C:\security\devices\ is a new directory and is backed up.
NetBackup begins to collect the information that is required for move detection with the next full or incremental backup for the policy. This first backup after the attribute is set, always backs up all files, even if it is an incremental backup.
Move detection consumes space on the client and the backup can fail if there is not enough disk space available.