V11 SP8
Loading...

Deduplication - Settings

Use this dialog box to configure deduplication database settings.

Do not Deduplicate against objects older than n day(s)
The number of days after which a unique data block cannot be used for deduplication during new data protection jobs. Setting this value ensures that very old data blocks are not allowed as the 'origin' data for newer data protection jobs that are deduplicated.
Default value: 365 days
Range: 30 - 12427 days
Enable Software compression with Deduplication
By default, when a storage policy is configured to use deduplication, compression is automatically enabled for the storage policy copy. All the subclients associated to this storage policy will use storage policy compression settings. That is, Use Storage Policy option is enabled on the Subclient Properties dialog box of all subclients associated to the storage policy.
When compression is enabled, data blocks are compressed and signatures are generated on the compressed block. Software compression method reduces the amount of space needed for storing data.
When this option is disabled, you can configure compression settings on the subclient level. See Modifying Software Compression on a Subclient or Instance for instructions.
Use DDB Priming option with Source-Side Deduplication
Whenever a new DDB is created, a fresh copy of signatures and first occurrence of each subsequent data block is written to storage. However these data blocks may already exist in storage with signature contained in the sealed DDBs residing in the MediaAgent or Data Center. The DDB Priming feature looks for signatures in the previously sealed DDBs and uses them to baseline the new DDB. In source-side deduplication, this saves the need for clients to transfer data blocks that are already available in the storage.
Use this option to reduce the data transfer between clients that have source-side deduplication enabled and connect to the MediaAgent over a WAN. We recommend you to not enable this option if the client exists in the Data Center or performance throughput is critical.
Exception:
  • DDB Priming is not supported with High Latency Optimization.

    To use DDB Priming, disable High Latency Optimization option on the Advanced Client Computer Properties dialog box or on the Deduplication - Advanced tab of the Copy Properties dialog box.

  • DDB Priming is not supported with silo copy.
Enable transactional DDB
Use this option to enable transactional DDB to allow instant recovery of the DDB, in the event of disaster.
When you enable this option, a number of add, update and delete operations are consolidated into a single transaction and the data is stored on the transaction based database.
Notes:
  • To enable this option, ensure that no backup jobs have been run to the deduplicated storage policy or global deduplicated storage policy.
  • If this option need to be enabled for existing deduplicated storage policy or global deduplicated storage policy with backup data, seal the DDB, and then enable or disable the option.

You can also convert a non-Transactional DDB to a Transactional DDB (memdb) with the SIDB2 tool. For details, see Converting Deduplication Database to Transactional Deduplication Database.

Allow jobs to run to this copy while at least [ ] partition(s) are available
This option is available only for the storage policy configured with multiple partitioned DDB.

When this option selected and if you have a partially available DDB that is one of the partition is offline:

  • The backup or Auxiliary copy jobs can continue with remaining available partition of the DDB.

    However, we recommend you that to recover the offline partition as soon as possible to balance the load on the available partition.

  • The pruning of deduplicated data from the disk will not happen completely unless all partitions are available.

    So, make sure to recover the offline partitions to reclaim the disk space. This is also applicable for data associated with the sealed DDB.

DDB Availability Option
Seal and Start new DDB automatically on detection of inconsistency
When this option is selected, if DDB or one of the partition of the DDB is found offline or invalid, the DDB (includes all partitions) is automatically sealed and a new DDB is created.
Pause and Recover current DDB
When this option is selected the DDB partition is automatically reconstructed from the DDB backup when the system detects that the DDB partition is offline or unavailable for use.
Default: Enabled
Block level Deduplication factor (in KB)
The data block size used for deduplication.