Index from snapshot (indexing) for D-NAS
The index from snapshot operation indexes the contents of the existing snapshots. When NetBackup indexes a snapshot, it creates an image catalog file in the NetBackup catalog for each snapshot. This image catalog file assists you when you restore a file from the snapshot.
Note:
The index of a NAS share that uses NFS protocol on a Linux host is faster as compared to the SMB protocol on Windows hosts. It is recommended to enable mixed protocols for the NAS share on the storage array and use NFS protocol (using Linux host) for the index operation.
The backup from snapshot operation also creates an image catalog file. If a backup from snapshot occurs frequently for the restore job in the environment, then an index from snapshot is not required.
For example, if the backup from snapshot runs once per week but the file restores are required daily, consider to use index from snapshot.
The index from snapshot operation can run from a full or an incremental schedule.
For non-VCT based index, the entries that are added to the image catalog file for any of the schedules, are the full set of files.
For index from snapshot operations a single stream is used per volume, unlike backup from snapshot operation.
A single SLP can have either index from snapshot or backup from snapshot operation, but not both.
Location of image catalog (. f) is:
<NetBackup Installation directory>/db/images/<StorageArrayFiler>/<directory>To dump or check the contents of the image catalog, use the cat_convert utility as follows:
: /usr/openv/netbackup/bin/cat_convert -dump <. f file name>
Note:
The index of a NAS share uses the NFS protocol, which is faster than the SMB protocol for indexing operations. It is recommended to enable mixed protocols for the NAS share on the storage array and use NFS protocol (using Linux host) for the index operation.