Operation Manual
222 Copyright © Acronis International GmbH, 2002-2015
Compacting - the compacting task deletes from the deduplication data store the blocks which
are no longer referred to. To learn more about compacting, see the "How deduplication works"
(p. 230) section.
Idle - compacting is not running. You can start the compacting by clicking the Run
compacting link.
Running - compacting is running. You can stop the compacting by clicking the Stop link.
Compacting schedule - the compacting task scheduling parameters. Click the Compacting
schedule link to re-schedule the compacting task. Only the time events (daily (p. 80), weekly (p.
82), and monthly (p. 84) schedules) are available for setting up. The preset is: Start the task every
1 week on Sunday at 03:00:00 AM.
Statistics
This tab provides you with information about the original and backed data sizes on all the managed
vaults of the selected storage node.
Vaults
This tab displays a list of vaults managed by the selected storage node. To update the list of vaults
with the most recent information from the management server, click Refresh.
Indexing
This tab lets you examine the current status of indexing for the deduplicating vaults of the storage
node and review the date and time of the last run.
7.5.6.4 Configuring a storage node by using Acronis Administrative
Template
The following are the parameters of Acronis Backup Storage Node that can be set by using Acronis
Administrative Template. For information on how to apply the administrative template, see How to
load Acronis Administrative Template (p. 395).
Parameters related to compacting
As backups are deleted from a deduplicating vault, its deduplication data store (p. 230) may contain
unused data blocks (items) that are no longer referred to from any backup. The storage node
processes the data store to delete the unused items. This operation is called compacting. Compacting
is performed by the compacting task.
Every time the compacting task starts, the storage node determines whether to perform compacting.
To do this, the storage node:
1. Checks the size of the backed-up data that has been deleted from the vault since the last
compacting.
2. Uses the Compacting Trigger Rough Estimation Threshold parameter to determine whether this
size, relative to the size of the remaining backed up data, is significant.
3. If so, uses the Compacting Trigger Threshold parameter to determine whether the deduplication
data store contains a significant number of unused items. If so, the storage node performs
compacting.
The parameters are the following.
Compacting Trigger Rough Estimation Threshold