Loading...

Index Cache: Transitioning from a Shared Cache

Overview

If you currently have an index cache sharing arrangement configured (Index Cache Server or Index Cache Using Network Share), to upgrade to Version 11, you must transition to a local index cache disk. This page tells you how to do that.

You can transition to a local index cache by three different methods, based on your environment and operational considerations, as described next.

Before You Begin

  1. Verify that any 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. You may need more than this amount initially, depending on the transition method you choose next.
  2. Choose the transition method that works best for your operation. You have three options:
    • Method 1: This is the method best suited to most transition cases. Under this method, you set up a MediaAgent as a Secondary Index Server, then copy the shared index cache contents to that server one time.

      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 especially recommended for customers using tape for their 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 directory. Incremental backup jobs that require a prior index restore it from the former shared index cache location, 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 off-site location.

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

      Operation: Full backups create a new index in the local 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 the MediaAgents initially have sufficient available local disk space to hold all the 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: Configuring the Feature.
  2. Allow all running backup jobs to complete, then stop all NetApp 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, 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.
  4. If the MediaAgent that you stopped services on 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 in each MediaAgent.

For each MediaAgent, perform these steps:

  1. From the CommCell Console, expand Storage Resources > MediaAgents.
  2. Right-click the MediaAgent, then click Properties.
  3. Click the Catalog tab.
  4. Click Browse, navigate to the local index cache folder and click OK twice.

Method 3: Copy Index Cache Contents to MediaAgent Local Disk

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

  1. Allow all running backup jobs to complete, then stop all NetApp 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, then click Properties.
    3. Click the Catalog tab.
    4. Click Browse, navigate to the local index cache folder and click OK twice.
  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.
  4. If the MediaAgent that you stopped services on 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:

  • 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.

Most MediaAgents will have only some of the folders named above, not all of them. What they have depends on the configuration of the MediaAgent.