Reducing the size of the indexes by removing the oldest save sets

You can use one or multiple procedures to reduce the size of the indexes. This procedure addresses how to reduce the index size by removing the oldest full save set and its dependencies.

To reduce the index size by removing the oldest full save set and its dependencies:

  1. Type the following command to check the consistency of the data structures of the save set against the data structures of the volume.
    # nsrim -X
    This option sets the utilization threshold to 30 percent. It aslo remove all of the save set information that is currently outside of the Browse and Retention period. Note: Ensure that the nsrim -X command is automatically run daily. If the command is not run, ensure that the nsrim.priv file exists under the $INSTALL_DIRECTORY/nsr/mm directory. If the file is missing, create a blank file with touch or a text editor and name the file nsrim.prv.
  2. Compress the client file index by using the following command:
    # nsrck -L6
    The nsrck -L6 command checks and extracts each record from each save time. It verifies that each record can be extracted from the database. The digest of each save time is re-computed and compared against the stored digest, and then the internal key files are rebuilt. Note: If the indexes are large, this command might take some time to complete. Remove the oldest full save set and all of its dependant save sets:
  3. Log onto the NetWorker server with an account which has Administrator rights within the NetWorker software.
  4. Start a command line session.
  5. Type the following command:
    nsrim -l
  6. To remove the oldest full save set and its dependant save sets for all of the clients of the NetWorker server from the online indexes, type the following command.
    nsrim -l -c clientname
    IMPORTANT: The nsrim -l -c clientname command will remove information from the online indexes. You will not be able to browse recoveries for the oldest full save and dependant save sets. However, you can recover the data by using the save set recovery option for non-module backups. For all other backups operations, the indexes will need to be rebuilt by using the scanner command or restored from the backup by using the nsrck -L7 command. When running the nsrim -l and the nsrim -l -c clientname commands, consider the following:
    • Browse and retention policies are ignored.
    • The save set header information will print the number of browsable full cycles currently in the online index.
    • Archive and migration save sets are ignored.
    • Manual save sets are treated as normal incremental save sets.
    • The utilization threshold is set to 30 percent.
  7. Adjust the Browse Policy and Retention Policy attributes of clients that are backed up to the NetWorker server. This shortens the period of time that entries remain in the client file indexes. Note: This solution works only for client backups that occur after you have changed these policy attributes:
    1. Log into in NMC.
    2. Expand Enterprise and double-click the NetWorker server where the client is located.
    3. Click the Configuration tab.
    4. Expand clients.
    5. Right-click the client whose indexes are being moving.
    6. Select Properties.
    7. Select the General tab.
    8. Click Browse policy and select a policy which is shorter than the current policy.
    9. Click Ok to save the change.

The nsrim -l -c clientname command will remove information from the online indexes. You will not be able to browse recoveries for the oldest full save and dependant save sets. However, you can recover the data by using the save set recovery option for non-module backups. For all other backups operations, the indexes will need to be rebuilt by using the scanner command or restored from backup by using the nsrck -L7 command.