> Documentation > Data Management > Optimize Storage Space Using Deduplication > Protect the Deduplication Database from Hardware Failure > Deduplication Database Recovery

Modifying the Properties for Deduplication Database Recovery

You can modify the DDB recovery settings to recover the DDB based on your environment.

When the deduplication database (DDB) is in an invalid state or is offline, the DDB is recovered though a Dedup Reconstruction job based on the DDB Recovery options configured on the storage policy copy. By default, the DDB has the Automatic recovery option enabled on the storage policy copy to automatically recover the DDB from the DDB backup.

Note: While running the DDB reconstruction job, if the restored DDB is found invalid or corrupted, then both the Last DDB Backup Job Id and the Last DDB Backup Time stamp are reset. You must run a full reconstruction process that deletes the existing DDB content, reads the entire data on the disk, and re-creates a new DDB from the deduplicated data read on the disk.

Procedure

  1. From the CommCell Browser, expand Policies > Storage Policies > storage policy.

  2. Right-click the appropriate storage policy copy, and then click Properties.

  3. In the Copy Properties dialog box, click Deduplication tab, and then click Settings tab.

  4. Under DDB Availability Options, choose appropriate settings to recover the DDB when it is detected as invalid:

    Options

    Description

    Seal and Start new DDB automatically on detection of inconsistency

    Select this option to automatically seal the invalid DDB and create a new DDB when active DDB goes offline and DDB backup is not available.

    Pause and Recover current DDB

    Automatically recover the DDB from the DDB backup.

    For detailed information of the options, see Settings.

  5. Click OK.

Results

  • If the Seal and Start new DDB automatically on detection of inconsistency option is enabled, the following conditions apply:

    • When the offline DDB or the partitions of a DDB are detected, the database is automatically sealed and a new DDB is created, including all partitions.

    • If the Allow jobs to run to this copy while at least [ ] partition(s) are available option is enabled, and if one of the partitions goes offline, sealing and start of a new DDB is prevented, and the backups continue to other active partitions.

    • The software does not perform DDB backup operations.

  • If the Pause and Recovery current DDB option is enabled, the following conditions apply:

    • When the offline DDB or the partition of the DDB is detected, the Dedup DB Reconstruction and Restore job are automatically started in the Job Controller window. To view the reconstruction job history on a partition, see Viewing Deduplication Database Reconstruction Job History.

    • For partitioned DDB, if a reconstruction job is already running for an offline partition of the DDB and if another partition goes offline during this job, the reconstruction job for the offline partition starts only when the existing job is finished.

Modifying the Properties of a Global Deduplication Policy Primary Copy

Loading...