<Failed to open backup> error message while consolidating current backup
I have received the following error message, during consolidation, at each of my last 3 (weekly) backups.
<Failed to open backup of F:\My Files_full_b21_s1_v1.tib. Make sure the backup location is accessible and contains all versions of the backup.
If you moved it or renamed it, return it to the same location or restore the initial file name, respectively, and then click retry.>
I deleted the (b21) version chain using the Acronis> Backups> My Files dropdown list and felt sure that this would be problem free. Seems I was over-optimistic.
This error message started to appear after I applied the latest version 25.5.32010 on October 14.
Prior to that date there had been no error message. I select cancel the message and the new backup is successfully saved each time but I would like to find a way to remedy the cause of the error and the error message at each backup.
Recent backup history:
September 9: In file backup options I manually deleted f:\My Files_full_b21_s1_v1.tib and its chain following completion of the latest full backup f:\My Files_full_b24_s1_v1.tib.
This left me with 2 full version chains and the latest full backup file.
September 9: I also implemented automatic cleanup (see attachment <Acronis backup options.jpg>)
The current version chains are listed in attachment <Acronis_Target drive_backup list.JPG>
Attachment | Size |
---|---|
Acronis backup options.jpg | 117.51 KB |
Acronis_Target drive_backup list.JPG | 164.86 KB |


- Log in to post comments

Steve, thanks for your comments.
I highlighted in my original query "I deleted the (b21) version chain using the Acronis> Backups> My Files dropdown list and felt sure that this would be problem free. Seems I was over-optimistic."
I am aware that I should make no changes in explorer and I manually deleted a backup set using the appropriate tool in the backup folder.
I am concerned that this has resulted in an error message that has only appeared since I installed version 25.5.32010; prior to that I had received no error messages using the initial upgrade to TI 2021.
Could this be because I implemented automatic clean up and set it to retain 3 full backup sets at a time when I only had 2 full sets?
I shall take your advice and do a manual validation in hope that I can clear this error.
- Log in to post comments

Andy,
If the validation does not fix the issue AND assuming that the validation did not report the backup as corrupt, I would suggest that you remove the backup task from the GUI and then add it back which should have the effect of overwriting the database information of the backup task.
To do this you would click to select the backup task in the GUI then expand the menu for the task and select Delete. In the box that appears select Remove which will remove the backup task from the application but will retain all the files created by the task. Once that completes then at the bottom of the backup task column expand the Add backup by clicking on the down carat then click on Add existing backup, navigate to the location where the backup files are stored on your F: drive and select the oldest file in the list, then click on Add. This should cause the backup to be restored to the GUI and fully update the task database.
- Log in to post comments

Hello Enchantech,
Thanks for your advice; I ran a manual validate and <ignored> the error message: the validation was successful.
I will wait for my next weekly backup to run and, if it runs correctly, I will leave things as they are and set aside the task <to remove the backup task from the GUI and then add it back> for possible future use.
Thanks again for your help
- Log in to post comments

Andy,
Very good. Report back with your results please.
- Log in to post comments

Hello Enchantech,
Backup ran perfectly today; no error message.
Thanks for your help
- Log in to post comments

Andy,
Thank you for posting back your results.
- Log in to post comments