User`s guide
345 Copyright © Acronis, Inc., 2000-2010
regular basis. The end results are intended to provide software improvements and enhanced
functionality to better meet the needs of Acronis customers. Acronis does not collect any
personal data. The terms of participation can be found on the Acronis Web site.
Disable
The information will not be sent.
Disabled
The same as Not configured.
7.2.2 Parameters set through GUI
The following parameters can be set through the graphical user interface (GUI):
For Acronis Backup & Recovery 10 Management Server: Collecting Logs, Windows Event Log,
SNMP, SNMP Address, and SNMP Community
For Acronis Backup & Recovery 10 Agent: Windows Event Log, SNMP, SNMP Address,
SNMP Community and Customer Experience Program
You will find the description of these parameters in the correspondent topic about configuration
through the administrative template.
7.2.3 Parameters set through Windows registry
The following are the parameters of Acronis Backup & Recovery 10 Storage Node that can be set only
by editing the registry.
Parameter related to deduplication
CompactingTriggerThreshold
Description: Specifies the percentage of used items in the data stores below which compacting
occurs.
Possible values: Any integer number between 0 and 100
Default value: 80
Registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Acronis\ASN\Configuration\StorageNode\CompactingTrigge
rThreshold
As backups are deleted from a deduplicating vault, its deduplication data stores (p. 64) may
contain unused items: files or disk blocks that are no longer referred to from any backup. The
storage node processes both data stores in turn to delete the unused items. This operation is
called compacting.
Since compacting is a resource-consuming operation, it should occur only when the number of
unused items is significant.
The CompactingTriggerThreshold parameter enables you to set up a balance between the extra
space required to store unused items and the compacting frequency. The larger the value of this
parameter, the fewer unused items are allowed in the data stores, but compacting will likely be
more frequent.
This parameter applies separately to disk-level and file-level backups. So, compacting may be
performed for one data store and skipped for the other.