Determining where and when the Index from snapshot operation occurs
The index from snapshot operation may be time consuming and slow down the system resources. For example, to perform the operation, it is required that the snapshot is mounted or NetBackup gathers content details from the file system to populate the catalog.
To help mitigate the extra resource and time that the operation may take, administrators can control when and where the index from snapshot operation runs:
Use the Storage lifecycle policy option in the Window tab to schedule when the Index form Snapshot operation can run. Schedule the operation to run when it is least likely to interfere with other jobs.
Use the following points to determine where to position the Index from snapshot operation in the SLP operations list:
Each NetBackup environment needs to determine where the operation works best in a specific SLP. To place the Index from snapshot operation too early (toward the top of the operations list), may consume time when the restore capabilities are not needed. To place the operation toward the end of the operations list may cause a delay to restore operations until earlier snapshots or replications are complete.
Use the Index from snapshot operation in an SLP only once. You can perform a restore from any snapshot after one image .f file is created.
Any operations list that includes a backup from snapshot operation, does not need an Index from snapshot operation. The backup from snapshot operation creates an image .f file. The only exception may be if the index is needed for restores before the backup from snapshot operation occurs.