60129: Acronis Cyber Protect Cloud: "The archive is invalid or its type is unsupported" error

use Google Translate

Operating Systems: 

Last update: 31-05-2021


You are backing up any data to a local drive or a network share of any type. Backup schedule is other than "Always incremental". Always incremental archives are not affected by this issue as this backup scheme produces archives of another type.

The issue occurs when the backup process tries to access the faulty file while applying retention rules, which provides us with two scenarios:

1. At some point when you already have a full backup and create subsequent backups, the process starts failing or producing a warning:

2. You try to delete the recovery point of the backup from the Cyber Protection console and the warning appears:

| line: 0xa1d3981537c68861
| file: k:\3917\enterprise\backup\impl\location_impl.cpp:867
| function: Backup::Impl::OpenArchiveById
| id: computer_name-C9C692D9-3B48-4057-91D9-932EAD6B5E1E-6E87707A-BAA9-43EF-877B-0433ACB7679EA_2017_07_20_09_10_10_558F1.TIB
| $module: disk_bundle_vsa64_3917
| error 0x400355: Failed to open archive 'computer_name-C9C692D9-3B48-4057-91D9-932EAD6B5E1E-6E87707A-BAA9-43EF-877B-0433ACB7679EA_2017_07_20_09_10_10_558F1.TIB'.
| line: 0x6a1198d1b8be2c30
| file: k:\3917\enterprise\backup\impl\archive_data_creator.cpp:236
| function: `anonymous-namespace'::OpenArchive
| $module: disk_bundle_vsa64_3917
| error 0x400001: The archive is invalid or its type is unsupported.
| line: 0x98130db273d2482
| file: k:\3917\enterprise\backup\archivers\is\archive.cpp:153
| function: Backup::ISArchive::Open
| $module: disk_bundle_vsa64_3917


This might happen when one of the previous backups failed, for example, because the destination did not have enough free space or the media was disconnected. In case the backup process was stopped abruptly and could not be resumed, the subsequent backup might not be able to read the incomplete previous backup and fails.


Go to the location of the backups and find the affected file, it is always mentioned in the error message.

In our example its name is:

You may notice that all full backups are named using the same logic:

All incremental and differential backups have an additional numeral which indicates the number of the subsequent (incremental or differential) backup. Each file with a numeral should be stored near the file without the number.

In the example above the full backup file should be named:
The subsequent incremental file is named:

Remove files with the 'number of the subsequent backup' which do not have a related file without the number.

Then run the backup job or wait for it to start as per schedule.

Additional information

In future versions, the new archive type, which is not affected by this issue, will completely replace the old archive type.