Reclaiming Space on the Deduplication Database Disk

You can use the DDBParam qscript to reclaim space on the drive where the deduplication database (DDB) is hosted.

You can use the DDBParam qscript to reclaim space only on version 11 MediaAgents that host the v11 DDB.

MediaAgents with previous release versions are not affected.

About This Task

Use the following properties to run the DDBParam qscript:

Parameter

Description

setOrGet

Use set value for enabling or modifying the parameters.

Use get value to view the existing settings.

StoreId

The ID of the DDB.

You can view the ID from the Deduplication Engines node from the CommCell Browser.

ddb_id

paramName

Use MaxNumOfAFsInSecondaryFile value to reclaim space on the DDB disk.

paramValue

The number of in each secondary file of the DDB.

Range: 4 to 256. The value must be the power of 2.

dDefault: 16

Before You Begin

  • Before running the qscript, make sure that there are no backup or auxiliary copy jobs run against the deduplicated storage policy associated with the DDB.

    For existing deduplicated storage policy with backup data, seal the DDB and then run the qscript.

Procedure

  1. Log on to the CommServe by running the qlogin command.

  2. To reclaim the space, run the following command:

    Syntax

    • Windows

      qoperation execscript -sn DDBParam -si setOrGet -si StoreId -si paramName -si paramValue
    • Linux

      ./qoperation execscript -sn DDBParam -si setOrGet -si StoreId -si paramName -si paramValue

    See the table in About This Task section for a description of the properties.

  3. Use the compactfile secondary option to run the DDB compaction. For more information about compacting the DDB, see Compacting the Deduplication Database.

Examples

To set four archive files in the secondary file for a DDB with an ID as 86, run the following command:

qoperation execscript -sn DDBParam -si set -si 86 -si MaxNumOfAFsInSecondaryFile -si 4

When the value is set to four, the DDB stores up to four job references in each secondary file on the disk. The fewer the number of job references in each secondary file, the faster the file is pruned and the space is reclaimed.

Loading...