This article provides information on troubleshooting possible failures during Deduplication.
Deduplication is a complex process involving many operations and components and thus has a number of possible points of failure. In order to properly troubleshoot and resolve such issues, the first step is to find the exact point of failure. Once this clear, we have to collect the proper diagnostic information. Please follow the guide below in order to do this.
Select the situation that applies:
Deduplication failures after a large amount of data has been deduplicated after a number of backups have been successfully created and indexed.
Make sure that the ASN is not showing any crashes and that the vault is still fully available;
Make sure that all Agents showing failures can access the vault;
Make sure that indexing task is finishing correctly before the next backup task is started. If this is not the case, see this article;
If the issue is not tied to performance, we are probably facing a problem with the existing deduplication data on this vault. Go to Collect information part below.
Step-by-step description of actions that lead to this failure;
Clarify if this happens on just one Agent, some Agents or all Acronis Agents doing the backup;
Clarify the exact backup sources and targets;
Collect an export of the backup plan;
Note the size of deduplication database and datastore;
Collect the output of the following command “tree <location_of_deduplicated_vault> /a /f > C:\tree.txt” where <location_of_deduplicated_vault> is the path to the deduplicated vault.