Salta al contenuto principale

"Failed to exclusively access a backup file during consolidation" error

Thread needs solution

My apologies for formatting/errors, first time forum user. 

 

I have been experiencing this problem for about a month. Any time I try any backup through Acronis (image backup, file backup, etc.), I receive the following error: http://puu.sh/ounvi/9909fb3ef8.png (error in subject line). Here are a few things I have tried:

  • Restart and begin backup immediately
  • Switching SATA cables to drive
  • Switching drives entirely (I tried to back up on 4 separate drives, 3 SATA and 1 USB)
  • Restarted a full backup (not incremental)

All of these have failed. I'm not sure where to go next, as I haven't found someone on the forums with a similar issue. I love Acronis and I want to continue using it but I can't if every backup I run fails. 

Forum, any thoughts? Please let me know if there is any additional information I should give. 

0 Users found this helpful

Hello Matthew, welcome to this user forum.

Please download a copy of the Log File Viewer app from the forum and use this to look for more detailed messages in the logs produced by the backup task where these errors are being reported.  Please attach a copy of one of the logs so that we can also see what is being reported.

Note: the logs are stored in C:\ProgramData\Acronis\TrueImageHome\Logs - this may be hidden on some systems.

Next, please confirm that you are using ATIH 2016 with the latest build version 6559 - if not, please update to this build.

It may be worth considering performing either a Repair or clean install of ATIH 2016.  

A Repair install is performed by taking the option to uninstall the software but then taking the Repair option when offered.

A Clean install is performed as follows:

Uninstall the program via the Control Panel (or use an uninstaller such as Revo).

Run the Acronis Cleanup Tool (link in my signature below), then restart the computer.

Reinstall the ATIH 2016 software (download a fresh copy from your Acronis Account if needed or if you don't have the 6559 build version installer).  Run the install as an Administrator (right-click on the installer to take this option).

Note: The cleanup tool will remove all your backup tasks and task history.  If you want to protect this information, then open C:\ProgramData\Acronis\TrueImageHome\ in Windows Explorer - this may be hidden on some systems - if so, go to the Folder option in the View pane and enable hidden files & folders).

Save a copy of the Database and Scripts folders to another location to restore back later.

Note 2: In order to restore the above folders & contents, you must stop all Acronis Services & Programs else you will encounter locked files in the Database folder.
 

Mr. Smith,

Thanks for your info! It should be noted (I neglected to mention this) that I have already attempted a repair of Acronis, and that I am on the current build 6559. 

Here is a .rar of my log files: http://puu.sh/ousEY/c073346d0e.rar . I believe I have included nearly all of those that were failures and some that were successes. Before attempting a clean install, is there anything noticeable in the log files that might point to a potential fix?

Thanks again for your help!

Any chance the backup is already mounted in Windows file explorer or mounted in Windows?  Have you rebooted and then let the backup run without mounting the .tib file manually (just to be sure it's not actually already in use by Windows)?

What happens if you create a new backup task and a fresh backup to the same location, but use a new, unique name and put it in its own folder?  Does that one run or give you the same error?

Bobbo,

I can't thank you enough for your suggestion. I tried the Process Explorer program Acronis suggests, but I didn't find any other process using my backup files. That being said, once I created a new backup task in a fresh folder, I was able to successfully run both a file backup and an image backup onto the same drive! So glad to have it working again! I believe the bad backup tasks were from an older version of the program, and they may have just become corrupted. In any case, it's working now. 

Thanks again all who helped! This topic can be marked as closed/solved.