V11 SP8

Converting Deduplication Database to Transactional Deduplication Database

A transactional deduplication database (DDB) is useful for faster recovery of the DDB in the event of process or computer crash.

You can use the memdb option with SIDB2 tool to convert the deduplication database (DDB) to transactional DDB.

Support: v10 and v11 DDBs can be converted to transactional deduplication database.

Note: Use memdb only if you want to take advantage of the Transactional DDB feature. This conversion tool is optional for all upgrades, because v10 DDBs will work in the non-transaction mode even after the MediaAgent that hosts the DDB is upgraded to v11.

Before You Begin

Before you run the tool, make sure the following:

  • The MediaAgent that hosts the DDB is upgraded to v11.
  • The DDB must be hosted on the SSD.
  • Run DDB backup.


  1. Log on to the MediaAgent computer that is hosting the DDB.
  2. On the command line, go to the software_installation_directory/Base folder, and run the following command by using the following parameters.
    Options Descriptions
    -memdb The keyword to convert v10 DDB to transactional DDB.
    -in The instance of the software that uses the tool.
    -cn The client name of the MediaAgent that hosts the DDB.
    -i The ID of the DDB.

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

    -split The partition number of the DDB. You can view the split number by accessing the path of the DDB.

    For example, in the following location, the split number is 1.

    E:\<DDB Folder>\CV_SIDB\2\86\Split01


    • Windows

      sidb2 -convert memdb -in <instance_number> -cn <client_name> -i <engine_id> -split<splitnum>

    • Linux

      ./sidb2 -convert memdb -in <instance_number> -cn <client_name> -i <engine_id> -split <splitnum>


  • In case of failures which do not corrupt the ddb, you may resume the conversion process after fixing the cause behind the failure.
  • If you have multiple partitions, and in case of non- corruption failure of a specific partition, you can mark that partition for recovery, and after the partition is recovered, you may resume the conversion process. For more details on marking ddb for recovery, see Marking the Deduplication Database for Recovery.

    However, if some of the partitions are already converted successfully, they will not be eligible to be marked for recovery. This is because of a version mismatch between the ddb backup and the upgraded ddb.

  • The ddb store will appear in maintenance mode until all the partitions are converted successfully.


To convert the split 1 of DDB with ID as 86, located on DDBMediaAgent01, run the following command:

sidb2 -convert memdb -in Instance001 -cn DDBMediaAgent01 -i 86 –split 1


The following information is a sample of the output.

sidb2 -convert memdb -in Instance001 -i 86 –split 1

Getting information for engine [86]
Converting property file. Recs [93]
    Rebuilding data file...
    96% (90/93)
    Rebuilding index file...
    96% (90/93)
    Writing index file...
    96% (90/93)
Converting primary file. Recs [148]
    Rebuilding data file...
    97% (145/148)
    Rebuilding index file...
    97% (145/148)
    Writing index file...
    97% (145/148)
    Rebuilding additional index #1.
    97%    (145/148)
    Writing index file...
    97% (145/148)
Converting zeroref file. Recs [0]
    Rebuilding data file...
    Rebuilding index file...
    Writing index file...
    Rebuilding additional index #1
    Writing index file...
Converting archive file. Recs [4]
    Rebuilding data file..
    Rebuilding index file.
    Writing index file...
2016/02/02 10:53:29    UpdateUpgradePhaseToMM: Store upgrade completed successfully