Transitioning from a Shared Cache to a Local Index Cache (Indexing Version 1)

If you want to upgrade to Version 11, but currently have a shared index cache arrangement configured (that is, an index cache server or index cache using network share), then you must transition to a local index cache.

Based on your environment and operational considerations, you can transition to a local index cache using one of three methods.

Before You Begin

1. Verify that the computer on which you wish to locate an index cache has sufficient internal hard disk space of the type required to accommodate the cache (see Index Cache: Planning).

2. Choose one of the following three transition methods that works best for your transition case:

   • Method 1: Set up a MediaAgent as a secondary index server, and then copy the shared index cache contents to the secondary index server.

     Operation: As each job that requires a prior index runs, the prior index is restored from the secondary index server. New indexes are written to the local index cache directory, and a copy is uploaded to the secondary index server.

     Considerations: This method is best suited to most transition cases, and is especially recommended if you use tape as your primary backup medium.

   • Method 2: Configure a local index cache directory on each MediaAgent. Do not copy any data to it when you set it up.

     Operation: Full backups create a new index in the local index cache directory. Incremental backup jobs that require a prior index restore it from the former shared index cache location, and then save it to the local index cache. Eventually, the old shared cache is not needed.

     Considerations: This method may not be suitable if you are using tape for primary backup storage (because of tape restore delay), and is not suitable if those backup tapes are being exported to an offsite location.

   • Method 3: Copy the entire contents of the shared index cache to each MediaAgent that had been using the share.

     Operation: Full backups create a new index in the local index cache directory. As an incremental backup job runs, the prior index is restored from the local disk. As index cache data ages out, disk space is recovered for MediaAgents no longer being supported by the cache, so that over time, the space used on the disk is reduced to only that required for the MediaAgent hosting the local index cache directory.

     Considerations: This method requires that all MediaAgents initially have sufficient available local disk space to hold all shared cache data for all MediaAgents that had been using the share.

Method 1: Copy Index Cache Contents to Secondary Index Server

Use this method to copy the existing index cache contents to a secondary index server.

1. If you have not already set up a secondary index server for your operation, do that now. See Secondary Index Server: Configuration.

2. Allow all running backup jobs to complete, and then stop all Commvault services on the MediaAgent that is hosting the index cache sharing arrangement.

3. Using available operating system tools, copy the index cache data from its old location to its new location on the secondary index server, as follows:

   1. If the old location of the index cache was a network share, create a folder named CatalogServer on the secondary index server under its software_installation_directory/IndexCache/ folder, and then copy the index_cache_directory/CV_Index folder from the network share to that new CatalogServer folder. The resulting path on the secondary index server will be software_installation_directory/IndexCache/CatalogServer/CV_Index, with CV_Index containing the index data from the old network share.

   2. If the old location was an index cache server, copy the contents of the old shared index cache folder to the software_installation_directory/IndexCache/ folder on the secondary index server. See Data to Copy from the Share, below.

4. If the MediaAgent that you stopped services on in Step 2, above, is used for other purposes, restart the services on it.

Method 2: Configure Local Index Cache on Each MediaAgent

Use this method to configure an index cache directory on a local disk on each MediaAgent.

For each MediaAgent, perform the following steps:

1. From the CommCell Console, expand Storage Resources > MediaAgents.

2. Right-click the MediaAgent, and then click Properties.

3. Click the Catalog tab.

4. Click Browse, navigate to the local index cache folder, and then click OK.

Method 3: Copy Index Cache Contents to MediaAgent Local Disk

Use this method to set up a local index cache directory on each MediaAgent, and then copy all of the contents of the existing shared index cache to all of the MediaAgents.

1. Allow all running backup jobs to complete, and then stop all Commvault services on the MediaAgent that is hosting the index cache sharing arrangement.

2. Configure the new index cache directory as follows:

   1. In the CommCell Console, expand Storage Resources > MediaAgents.

   2. Right-click the MediaAgent where you will be placing the local index cache, and then click Properties.

   3. Click the Catalog tab.

   4. Click Browse, navigate to the local index cache folder, and then click OK.

3. Using available operating system tools, copy the data from the old shared index cache directory (network share or cache server) to the directory you just configured. See Data to Copy from the Share, below.

4. If the MediaAgent that you stopped services on in Step 1, above, is used for other purposes, restart the services.

Data to Copy from the Share

The folders in the shared index cache directory that contain the index data to copy to your secondary index server include the following:

• CV_ErasedItems

• CV_FcsIndex

• CV_Index

• CV_Opt1

• CV_SnapMetadata

• CatalogServer

Copy only the folders (and their contents) that you find in the shared index cache directory. Do not copy any files.