Operation Manual

The following diagram illustrates the result of deduplication at target.

The indexing activity may take considerable time to complete. You can view this activity's state on

the management server, by selecting the corresponding storage node and clicking View details (p.

221). You can also manually start or stop this activity in that window.

If you back up a large amount of unique data, the indexing activity may fail due to insufficient RAM on the

storage node. The backups will continue to run. You can add more RAM to the storage node, or delete

unnecessary backups and run compacting. After the next backup, the indexing will run again.

Compacting

After one or more backups or archives have been deleted from the vault—either manually or during

cleanup—the data store may contain blocks which are no longer referred to from any archive. Such

blocks are deleted by the compacting task, which is a scheduled task performed by the storage node.

By default, the compacting task runs every Sunday night at 03:00. You can re-schedule the task by

selecting the corresponding storage node, clicking View details (p. 221), and then clicking

Compacting schedule. You can also manually start or stop the task on that tab.

Because deletion of unused blocks is resource-consuming, the compacting task performs it only

when a sufficient amount of data to delete has accumulated. The threshold is determined by the

Compacting Trigger Threshold (p. 222) configuration parameter.

7.5.7.3 When deduplication is most effective

The following are cases when deduplication produces the maximum effect: