Last update: Mon, 2017-07-24 10:29
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:
Failures on initial deduplication configuration: these types of failures and errors happen when setting up a new backup to a deduplicated vault or very shortly after.
Run the same type of backup to a managed vault without Deduplication. If this backup also fails, the issue is not related to deduplication;
Make sure that all backup Agents showing the failure have a proper deduplication license assigned;
Make sure that the vault and database locations are fully accessible by the Storage Node service account.
Log on to Windows under Administrator account;
Right click the folders which are the vault and database locations and select “Properties”;
Open “Security” tab and highlight the ASN User (if there is no such user in the list, see below );
Look at the permissions specified:
On “Security” tab of the folder properties, click “Edit” button;
Highlight the ASN User (if there is no such user in the list, see below );
Tick the “Full control” check box and then click “OK” -> “OK” buttons.
On “Security” tab of the folder properties, click “Edit” button, then click the “Add…” button;
Enter the name of ASN user or find the ASN User by clicking “Advanced” -> “Find now” buttons:
Accept the changes and specify permissions for the ASN user by selecting “Full control” check box and then click “OK” button:
Once all of the steps above are checked and the failure is still present, go to Collect information part.
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 if it can be created;
Collect the operations log showing this failure;
Collect System Report from the Storage Node machine and one of the Agent machines showing this failure: see instruction for Acronis Backup 11.7/11.5 Generating System Report , if this fails for any reason, you can use this AcronisInfo Utility .
With information collected contact Acronis Customer Central .
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 operations log showing this failure;
Collect System Report from the Storage Node machine and one of the Agent machines showing this failure: see instruction for Acronis Backup 11.7/11.5 Generating System Report , if this fails for any reason, you can use this AcronisInfo Utility
Collect the output of the following command “tree <location_of_deduplicated_vault> /a /f > C:\tree.txt”
Copy the .meta folder from the vault.
With information collected contact Acronis Customer Central .
