Notes On True Image Restores and Move Detection

• Because the additional information that NetBackup collects for incrementals is the same as for a full backup, incremental backups take much more disk space when you are collecting true-image restore information. Adding move detection requires even more additional space.
• You can set the period of time that NetBackup keeps the true-image restore information by setting Keep TIR Information on the Global properties dialog.
• Incremental backups are slower for a policy where true-image restore information is being collected.
• If you are using the indexing feature, the INDEX files take much more space when you are collecting true-image restore information. (This warning applies only to ASCII catalogs---the binary catalog does not need INDEX files.) For more information, see Reduce Restore Times by Indexing the Image Catalog.
• You can perform true-image restores only on directories that were backed up by a policy for which NetBackup is collecting true-image restore information.

If you intend to restore an entire file system or disk by using a true-image restore, ensure that all the desired directories are backed up by a policy that is collecting true-image restore information.

• For true-image restores, you can list and select only directories. In true-image restore mode, the client-user interface does not show individual files or let you select them. The NetBackup user's guides explain this further and provide instructions for performing true-image restores.
• A true-image restore preserves files that are currently in the directory but were not present when the backup was done. In our previous example, assume you created a file named file5 after the incremental backup occurred on 12/04/2003, but before doing the restore. In this case, the contents of the directory after the restore is:

   file1
   file2
   file4
   file5