Aller au contenu principal

True Image 2013 is trying to access a drive that no longer exists

Thread needs solution

In True Image 2013 running on Windows 8.1, the drive image cloning fails when TI looks for the wrong disk image to consolidate.

There was a drive J, but I removed it. The drive I've set up TI to save to is M. The backup goes well until TI tries to access this image that was part of a totally different set of backups.

How do I reset TI and get rid of this problem?

Here's the error message:

Failed to exclusively access backup J:\My backups\disk_image_2013_i7_to_FreeAgent_3T_daily_full_b35_s1_v1.tib during consolidation. Make sure the backup file is not opened in other applications.

0 Users found this helpful

Please check this link. As you have 2013 and 8.1, you qualify for the free upgrade to 2014. 2013 and 8.1 are not compatible.

http://forum.acronis.com/forum/50750

As for your specific problem, if I am understanding correctly, you created a backup task and the drive letter was changed by Windows.

To prevent this type occurrence, it is best to permanently assign a drive letter to the storage disk with a letter such as x or y or z and this can be done from within Windows Disk Management. This will prevent a drive letter change when another device is inserted.

I believe you can use the "move" option and get the program to respond to the new location. If the move option is not successful, you will need to stop using the existing task and create a new task pointing to the new storage disk as the task and the storage disk are mated and cannot be changed.

GH6. How to use the MOVE backup option to relocate storage folder.

Thanks for the tip on TI 2014. I've installed that and recreated an event, but got the same error message:
Failed to exclusively access backup J:\My backups\disk_image_2013_i7_to_FreeAgent_3T_daily_full_b35_s1_v1.tib during consolidation. Make sure the backup file is not opened in other applications.

It occurs to me that I didn't change the name of the event and location of the backup, so TI just saw it as another in the same version it had been doing earlier. I'm going to try again. I'll let you know how it goes.

Arthur,
There have been reports of similar issues with consolidation. Frankly, I discourage any use of consolidation because of these reported issues. I much prefer to use non-consolidation options. If interested, post more about your backup scheme. Where is drive J? Is this network or ???

User editing of backup tasks has also reported not to produce the expected results.

I prefer to have the program delete the old backups with automatic cleanup--much like this example.

https://forum.acronis.com/system/files/forum/2009/11/5940/example-folde…

Hello, GroverH, Thanks again for your help.

I've been doing more testing.

One thing I tried was removing similarly named backup set files and settings, thinking that this might clear the old data about a backup on J:. That didn't work.

Another thing I did was to plug in a USB flash drive stick, which was read as J:. That didn't help either, probably because there was no backup on that drive. I also tried reassigning J: to R:, but that didn't help either.

Is there a way to reset True Image, removing all data of prior backups so nothing interferes with my current backups?

It's odd that I have another backup that is working perfectly and doesn't try to access J drive.

Just in case it helps, my new Event code is: 0x01E50015+0x01E5001A+0x000B041D+0x00040011+0x0000FFF0+0x80070002

And the Event details are: Failed to open backup J:\My backups\disk_image_2013_i7_to_FreeAgent_3T_daily_full_b35_s1_v1.tib. Make sure the backup location is accessible and contains all versions of the backup. This backup may also be corrupted.

As you examine the storage folder contents, does Full _b35 actually exist?
Which version of Wndows?

2013 & 2014 work from a history file, This is the archives.xml file stored in the History folder. This file can be deleted and TI will be cleared of ALL BACKUP TASKS--including any good working tasks. The actual tib backup files will be untouched but all tasks wsill be deleted. The next links shows how.

GH55. Delete Database History Archives.xml.
GH55A. Acronis servicesCreate Custom Full Backup Scheme.Keep 4 versions (chains). The 4 is user choice.
GH12. Create Custom Incremental Backup Scheme. 6 Inc, Keep 4 chains. The 6-4 is user choice.
GH13. Create Custom Differential Backup Scheme. 2 Diff, Keep 2 chains. The 2-2 is user choice.

I set up my tasks so personal tib deletes are not needed but if you do need to delete one manually, here is how to use the program to perform the delete.

GH5. How to delete backup files using Acronis Backup 'Explorer'

If you have not done so, I would invest some time in reviewing the fine points of 2014. Click on my signature link 2A. It covers how to create special tasks and has a listing at the end on how to use the many options. This can be time well spent even for the experienced user.

This next link show how to remove a single backup task from the listing of tasks. Tib files remain. Only the task is removed.
GH21. How to add backup files to the listing of backup tasks for assorted uses        

Hi, GroverH. Your advice has been very helpful. Thanks!

I've not been using consolidation recently, because your experience with consolidation problems matches mine.

The Full_b35 must have been an old backup folder because it no longer exists.

I've deleted the folders you listed in the GH55 page, uninstalled, and reinstalled TI. It appears to be working again!

I've read the messages you suggested. You're a real asset to Acronis. They should put you on staff!

Thanks so much!

Glad you found the information helpful. That helps make the time spent creating the guides to have been worthwhile.