Indexes expected to be in the Index Cache are instead being restored from protected storage

Article ID: MA0001 Browse of recent backups are restoring indexes from protected storage.

Symptom

Indexes expected to be in the Index Cache are instead being restored from protected storage.

Cause

For incremental backup indexing, the previous index is copied to create the new index. However, for performance reasons, indexes over 2GB (2048MB) are moved/renamed instead of being copied. A Browse/Restore operation requiring the previously named index will not find the index in the Index Cache and instead restore the index from protected storage.

Resolution

There exists a sSpaceSaver registry value to change the behavior of the Index Cache. You can increase the rename threshold (default 2048MB) or force it to always COPY or RENAME. The registry value must be changed on the MediaAgent used to create the new index.

Value Name

sSpaceSaver

Value Type

String

Windows

HKEY_LOCAL_MACHINE\SOFTWARE\CommVault Systems\Galaxy\Instance\MediaAgent

Unix

/etc/CommVaultRegistry/Galaxy/Instance/MediaAgent/.properties

Default Value

2048

Description

Controls indexing behavior - copy vice rename during index update.

y or Y = always rename.

0 = always copy (infinite threshold).

Other decimal number in the form of a string is interpreted as the threshold in MB.

Any cache directory less than the threshold in total size is copied, and any cache directory greater than or equal to the threshold in total size is renamed.