Remove backup named archive_[date1]_D1.tib
This article applies to:
- Acronis vmProtect
Symptoms
Previously successful backup task fails with the following error message:
Task '*Backup Acronis' failed: 'Failed to create a backup.
Additional info:
--------------------
Error code: 3
Module: 435
LineInfo: 555b5abba09501ce
Fields:
Message: Failed to create a backup.
--------------------
Error code: 66
Module: 161
LineInfo: bd0bef9bf345a7d
Fields:
Message: Failed to create the backup archive. Operation parameters: /XXXXX/; Location login: YYY\ZZZ
--------------------
Error code: 16
Module: 161
LineInfo: bd0bef9bf34582e
Fields:
Message: Archive with the same name already exists.
Cause
The creation of the previous backup has not been finished properly, so the current backup cannot continue the chain due to leftovers (incomplete files) in the backup storage.
By design, the archives created in multiple-files (legacy) format are named in accordance with the following scheme:
archive_[date1]_D.tib -> First full backup
archive_[date1]_D2.tib
archive_[date1]_D3.tib
archive_[date1]_Dn.tib -> Succeeding incremental backups.
When the next chain of the backups saved into this archive starts again from full (for example if you set up to create full backups every X days), the names are changed into:
archive_[date2]_D.tib -> First full backup
archive_[date2]_D2.tib
archive_[date2]_D3.tib
archive_[date2]_Dn.tib -> Succeeding incremental backups*
While the backup task is being processed though, the archive being created has the name archive_[date1]_D1.tib. Upon the successful completion of the task “D1” changes into “DX” where X is the number of the backup in the chain.
*It is important to keep in mind that the archives “archive_[date2]_Dn.tib” and “archive_[date2]_D(n+1).tib” are not necessarily separate incremental backups. These could be as well two parts of the same incremental backup. It may happen due to network disconnection during backup - if the data tranmission into archive is interrupted and retried then there is an additional “archive_[date2]_D(n+1).tib” created.
Solution
The idea is to clean up the unfinished files before running backup again. You should remove the file named archive_[date1]_D1.tib which cannot be a valid backup unless there is currently an active backup task running into it. If there are no tasks running, then this D1.tib file becomes useless and will prevent future backups from finishing successfully.
More information
See also:
Multiple files backup scheme (Legacy mode)
Single file backup scheme (Always Incremental mode)