39937: Acronis Backup & Recovery 11.5: Replication or Cleanup Activity Task Fails due to Not Being Able to Open Archive of a Different Machine

Also read in:

use Google Translate

Applies to: 

Operating Systems: 

Last update: 16-08-2017

The issue is fixed starting with the build number 37608.

This article applies to:

  • Acronis Backup & Recovery 11.5 (builds 32256, 32266, 32308)


  1. You are performing a backup of several machines with automatic replication / cleanup in an unmanaged centralized vault;
  2. The backup completes successfully but the replication or retention rules fail with an error similar to:

    Command 'Replicating backups/cleaning up archives (1st location)' has failed.
    Additional info:
    Error code: 61
    Module: 309
    LineInfo: 4a8728dc8a1c950f
    Fields: $module : service_process_vs_32256
    Message: Command 'Replicating backups/cleaning up archives (1st location)' has failed.
    Error code: 218
    Module: 161
    LineInfo: b320396adfe3cc9
    Fields: IsReturnCode : 1, $module : disk_bundle_vs_32256
    Message: Failed to delete the backups from archive '\\machine_name\#arl:/archive_name' by the specified filter.
    Error code: 507
    Module: 64
    LineInfo: a1d3981537c687b7
    Fields: id : backup_name.TIB, $module : disk_bundle_vs_32256
    Message: Failed to open the backup archive by the ID.
    Error code: 1
    Module: 64
    LineInfo: 98130db273d2480
    Fields: $module : disk_bundle_vs_32256
    Message: The archive is invalid or its type is unsupported.
    Error code: 9
    Module: 64
    LineInfo: 95962d9a14426d0d
    Fields: $module : disk_bundle_vs_32256
    Message: Failed to find the backup.

  3. The activity task fails due to not being able to open archive of a different machine (not of the machine that is currently being backed up);
  4. Refresh on the corresponding vault resolves the issue only temporaly. After some time the issue is reproduced again.


There are numerous broken (non-existing) links to .TIB files in the meta data on the vault because of manual archive deletions, incorrect backup plan deployments or other factors.

This meta corruption can be only temporarily fixed by manually refreshing the vault location.


The issue is fixed starting with the build number 37608 of this product. Please update to the latest build.