Backup errors: "failed to exclusively access" long gone file
Each and every backup generates errors and the message "The last backup has failed." Viewed in the log, everything is fine up through "Consolidate Backup Archive". then errors are generated with the following explanation:
****
"Failed to exclusively access backup \\other computer name\Seagate (F)\Dell I15R Images\Dell_I15R_partition_inc_b1_s47_v1.tib during consolidation. Make sure the backup file is not opened in other applications.
More information about this error and solutions may be available online in the Acronis Knowledge Base.
To access the online resource manually, enter the event code at: http://kb.acronis.com/errorcode/
Event code: 0x01E50017+0x00040007+0x0000FFF0+0x80070035"
****
The backup that has not been "exclusively accessed" is long gone. At the time that it existed, the drive was attached to a different computer on my home network, namely "other computer name" above. that backup was long ago deleted as were all the related .tib files. I have created new backups using the drive directly on the subject computer and removed prior backups from the list and eventually deleted them with the related .tib files. Nevertheless, the above error is generated with reference to the same long dead and gone file.
When trying to access backup files, a series of requests of the general form "identify the location of file number 1", or something like that, are generated at the top of the explorer window. After cancelling a raft of those, one eventually gets to open the mounted backup files and they appear fine.
Any help will be appreciated. Ron
First, thank you very much for the excellent advice. I had nearly entirely successful results: I followed your advice and the last backup generated no errors.
I still got the "Identify the location of volume number 6" message the first time or two I viewed the backup files, but not just now when I went to confirm the wording. Is that typical? I am also a little mystified about the archive file. I viewed it before deleting it and after it regenerated and in both cases it had listings of all the old backup files going back to 2013, including the one that was the problem to begin with. I went through the process several times, introducing a computer restart after deleting the file. Same result. Nevertheless, the error is gone, So I'm happy though confused.
Again, many thanks for the help.
Ron
There are probably some references to those backup files that are no longer on your disk that remain in the Windows Registry. The application scans your system for backups when you start the application so I think what happens is that even though the app should give you a choice to ignore a backup reference that no longer exists that choice is not saved as it were so you continue to get the error message. If the database is forced to rebuild itself that changes. I would say the value for those backups in the Registry are changed and so the app stops complaining about it.
Makes sense. I was wondering if it might even find it in the tib files themselves -- in the backed up archive file.
Anyway, all seems to be OK. Thanks again.