Modifying Index Pruning Settings for Subclient-Level Indexes

You can modify index pruning settings at the subclient level.

The active index database is retained in the MediaAgent's index cache indefinitely so that it can be accessed during operations such as browse and find, and reporting. During data backup jobs, the system writes new action logs and then plays back those logs into the index, thus keeping the active index continuously updated.

In addition, indexing metadata from the latest two cycles are maintained in the index database, and are pruned from the database after successful index backups in order to reduce disk usage.

When the system ages off backed-up data via retention rules, the system flags that data and deletes (prunes) the aged jobs records (that is, metadata) from the active index. This process, called compaction, decreases the size of the index and frees up storage space.

During compaction, the records of unaged cycles are also pruned according to the following rules:

• Only the index for the latest two cycles of backup jobs is retained, as specified in Advanced Subclient Properties > Indexing > Enable index pruning settings. For more information, see "Procedure", below.

• By default, the system retains the latest two cycles in the index.

• After the index is backed up, the system drops data index records of older cycles from the index as specified in the pruning settings. This ensures that the latest index remains in the cache. For example, suppose you select two cycles of index retention in the pruning settings. At the third cycle, the system backs up the index and then drops one cycle (that is, the first cycle) of indexed data from the index cache.

• If you browse cycle(s) that have already been pruned from the index, the system will restore that index using an older checkpoint that still contains the index of those cycles.

  Example:

  • The retention setting for a subclient is set as two cycles.

  • The system runs three cycles.

  • The system runs an index backup. The index has now been backed up for all three cycles.

  • Upon a compaction request, the system prunes the records of the first cycle from the index.

    The system retains only the latest two cycles (that is, Cycle 2 and Cycle 3). However, if you browse Cycle 1, the system restores the index (called a temporary index) from a checkpoint (that is, the index backup noted above). This temporary index will be deleted from the index cache automatically after 7 days if there are no further browse/restore/find operations performed on it.

    The system attempts to recover a checkpoint that includes the dataset and time range that the user is browsing. If the required job is not part of any available checkpoint, the system will use the latest checkpoint and then restore the required action log files and play them back into the main and currently available checkpoint, in order to complete the browse operation.

Procedure

1. Open the CommCell Console.

2. In the CommCell Browser, click Client Computers.

3. Expand the desired client and backupset.

4. Right-click the subclient, and then click Properties > Advanced.

   The Advanced Subclient Properties dialog box appears.

5. On the Index tab, in the Index Server list, the subclient's current index server MediaAgent is shown. To change the index server, select it from the Index Server list.

6. To enable index pruning, select Enable index pruning, and then select one of the following:

   • Retain index in cache for all jobs. The active index in the index cache will retain indexed data from all the backup jobs indefinitely (no job’s index data/index records will be pruned from index).

   • Retain index in cache for [Number] cycles. The active index in the index cache will retain indexed data for the selected number of cycles.

     For example, suppose you select two cycles. After three cycles, the system backs up the index and drops one cycle (that is, the first cycle) of indexed data from the index cache.

   • Retain index in cache for [Number] days. The active index in the index cache will retain data for the selected number of days.

     For example, suppose you enter 5 days in this field (note that a minimum of 2 cycles will be retained, no matter what number you enter in this field). The system retains all of the cycles from the last 5 days, and drops the remaining cycle(s) after an index backup occurs.

7. Click OK.