Index Cache - Online Help
Use this dialog box to view and modify index cache parameters and retention criteria.
SnapProtect Version 10 now supports locating the index cache only on a local drive. You must move an old shared index cache to a local drive if you make any changes to its configuration. To set up a local index cache, see Index Cache - Configuration.
- Index Cache Directory
This is the directory where index cache data resides.
You can change this directory. If it does not already exist, the MediaAgent software creates it.
When you designate an different directory for index cache, the MediaAgent moves the existing cache contents and directs all new cache entries to that directory. Note, however, that the Windows MediaAgent copies the existing cache contents, so you may have to manually delete the original directory to free the disk space it occupied in the old location.
- Use a file system dedicated to index cache data, so that non-index data does not consume index cache capacity.
- Estimate your index cache space requirements with a margin of safety. Allocate a bit more space, rather than less. If you are maintaining backward-compatible content indexes generated by a previous software version, the index cache folder may need more space.
- Do not locate the index cache on a compressed drive.
- For best performance, locate the index cache on an SSD (solid state drive) disk.
- For Windows, do not place the index cache folder directly under the software_installation_directory.
- For Unix, do not specify root as the index cache directory.
- When entering the complete index path:
- Do not exceed 200 characters.
- Do not use the "!" character.
- Do not use any Unicode characters.
- Do not host the index cache on your CommServe computer unless it has your only MediaAgent.
Click to locate and set the Index Cache Directory.
- Enable this Access Path
Clear this option to disable the index cache.
- Offline Reason
If the index cache is offline, this field displays the reason.
- Index retention time in days
Sets the number of days an index for a subclient is retained in the MediaAgent. When an index is older than this, it is aged (deleted) within 24 hours.
- Index cleanup percent
When an event-driven cleanup runs, if the percentage of used space remaining after aged indexes are deleted is still greater than the value you set here, additional indexes are removed on a least-recently-used basis until the used disk space percentage becomes equal to or less than this value.
- Minimum Free Space (MB)
Sets the total amount of free space in megabytes that must be available at all times in the index cache. If the available amount falls below this value, an event-driven cleanup begins and the index cache is taken offline while an event-driven cleanup is performed.
- Free Space Warning (MB)
Sets the amount of free space in megabytes on the index cache volume below which disk space is considered to be low enough to require action. When this threshold is crossed, the MediaAgent generates an event message in the CommCell Console, and sends a MediaAgents (Disk Space Low) alert email if that is configured. It also begins deleting the least-recently-used indexes until the amount of used space falls below the Index cleanup percent value.
- Index Cache Total Space
Displays the total space in gigabytes that is available in the Index Cache Directory. Note that when the Index Cache Directory is changed, the Index Cache Total Space shown in the CommCell Console may not reflect the new value for up to 30 minutes.
- Index Cache Free Space
Displays the free space available in the Index Cache Directory. Note that when the Index Cache Directory is changed, the Index Cache Free Space value in the CommCell Console may not reflect the new value for up to 30 minutes.