error log failed to exclusively access ...during consolidation

no up ... I'm not sure to be able to restore anything with this error if some thinks goes wrong ...

Hello Frederic,

sorry for the delay with answer.

Please contact our support team, they help you to investigate the issue.

Thank you.

I've got a similar problem to this where a full disk backup to my "S" drive ( an external USB drive ) seems to complete successfully i.e. the image has been created of about the right size - then the logfile tells me it's going into a "Consolidate Backup Archive" process then there's loads of error messages about not getting exclusive access to a file location on a completely different drive ( my "V" drive ) where this job has NEVER been backing up to.
My main concern is whether these backups are any use at all ??
The "V" drive is usually disconnected as it's a drive I use at another location but I do have manually launched TI jobs backing up to it if I am working at that location.
I've tried deleting these files and recreating new jobs but the problem just keeps coming back. I've even run the Acronis TI cleanup program and installed a new copy of TI2014 to no avail so my patience is wearing very thin with Acronis.
One clue seems to be that if I run a "Validation" on the failed job I immediately get a message saying it can't find all the backups ( which is consistent with the problem ) then if I say "Ignore" and let the validation complete it seems to complete ok - then a re run of the backup works fine with no errors !!
Problem is a few weeks later it'll start again and I just don't know why.
Anyone got any ideas ?
Thanks

Hello kgee,

thank you for your posting!

Could you please share settings of your backup task and error log that you receive by consolidation?

Thank you.

Thanks for the reply.
The following attachments show the logs from 3 runs of the same job :
The first is a successful run, the second shows the job failing and shows reference to the unrelated drive and finally the third log is from a run of the job AFTER a validation routine was run. This then appears to have gone on to finish successfully every time it was run.

I am having the same problem with the same Event Code: 0x01E50017+0x00040007+0x0000FFF0+0x80070003 as Frederick above. The backup creates a file but during the consolidation it fails and says "Failed to exclusively access backup" then says "make sure the backup file is not opened in other applications". I am backing up to a QNAP NAS. I have about 7 backups that I run that backup specific directories. I have them all starting around the same time. This is an incremental backup that it fails on.

On 21 Jan it completed a Full and on 22 Jan in successfully completed a incremental and then failed on 23 Jan and 24 Jan with the same error yet the backups are there and I can see them (don't know if I can truest them). My settings are "Custom", Incremental, Create a full every 5 days, Delete version chains older than 7 days.

I've only had this product for 40 days so I'm really worried since I've never asked for support and the free 30 day support ran out.

Any help would be appreciated.

Have you tried to run the "Validation" routine on the job ? I found that after running this ( and ignoring the missing file message at the beginning ) the job ran perfectly thereafter.
Unfortunately after running a completely different job which backs up to a different drive the problem comes back again.

Kgee:

Thanks a lot for the reply. I had validation turned on (Validate Backup When It Was Created) under the Custom setting. I have deleted the backups and I'm starting over. I will try this when it occurs again. Thanks for the suggestion. I've had this error numerous times so my guess is that it is a bug because my backups will run for several days and then randomly I get this (and I have about 7 file backups that I have in my list - it is not the same one every time.

Mike

Hello Everyone,

thanks to gathered logs we were able to determine the issue and most likely it will be fixed in the next version of the product.

In the meanwhile you can use the scheme with automatic cleanup rules.

Thank you.

Similar issue with new backups trying to access prior unrelated backups (different name and locations). The error reads "Failed to open backup G:\folder...b5_s4_v1.tib. Make sure the backup location is accessible and contains all versions of the backup. This back up may also be corrupt." I'm already using the automatic cleanup rules controlling the number of versions and chains but don't see how this will help in controlling searches for backup by other names and locations.
Deleting old backups hangs up running for hours and hours and must be terminated from Task manager.
Is there a way to clear all of the references to old or even all backups and start fresh? How do I avoid this issue in the future. I think it started when Windows changed the drive letter on me but have since assigned the letter but continue to have issues when trying to create new and independent backups.

Similar issue with new backups trying to access prior unrelated backups (different name and locations). The error reads "Failed to open backup G:\folder...b5_s4_v1.tib. Make sure the backup location is accessible and contains all versions of the backup. This back up may also be corrupt." I'm already using the automatic cleanup rules controlling the number of versions and chains but don't see how this will help in controlling searches for backup by other names and locations.
Deleting old backups hangs up running for hours and hours and must be terminated from Task manager.
Is there a way to clear all of the references to old or even all backups and start fresh? How do I avoid this issue in the future. I think it started when Windows changed the drive letter on me but have since assigned the letter but continue to have issues when trying to create new and independent backups.

Thomas wrote:

I think it started when Windows changed the drive letter on me but have since assigned the letter but continue to have issues when trying to create new and independent backups.

Assign a drive letter such as x or y or z to the external disk so the insertion of a flash drive, other usb drive, Camera, maybe printer/scanner will not affect the backup task as default assigned letter wil be changed if any of those devices are inserted prior to a backup. If you assign a new letter (x,y,z) to the disk, a new task is needed with the correct drive letter. No edits to the task, please.

Is there a way to clear all of the references to old or even all backups and start fresh? How do I avoid this issue in the future.

History is controlled in an Acronis folder called DATABASE and the file holding this data is ARCHIVES.XML

This file can be renamed OLD-ARCHIVES.XML or deleted. The file will be recreated with no history.
All tasks will need to be recreated.

This link may be of interest.
http://forum.acronis.com/forum/54475

Thanks for the tip on the Archive database. I renamed the file ARCHIVES.XML to a .OLD suffix. Also renamed all of the scripts (.tis extension).
For others, these are located in
C:\ProgramData\Acronis\TrueImageHome\Database\archives.xml
C:\ProgramData\Acronis\TrueImageHome\Scripts\*.tib.tis
It may not have been necessary to rename the script files but it provided clarity on which ones were no longer in use.

I created new and empty folders for new backups and ran a new full backup (disk mode, weekly - differential with automatic cleanup) and a selected files backup (daily - differential w/ automatic cleanup).

All of the old tasks are gone and all of new backups started at version 1 (the prior ones picked up version numbers from other backup and then tried and failed to access them). A few more successful iterations will improve my confidence level but all seems to be well so far.

The only remaining small issue is that the pull down list for destinations for backups continues to show folders that have been deleted and are not referenced by any of the current backup tasks. I don't know if attempting to select one of these would send the program off on a never ending search or not. Hopefully I'll remember which ones are real if I go to create any new backup tasks. If anyone knows where this list is kept I'd like to update it.

The learnings out of this seem to be (any one with more knowledge is invited to elaborate or correct these).
The True Image software is confused by changes in the drive letter and continues to have trouble dealing with the issue
- Use Windows to assign fixed drive letters to any USB devices that you use for backups
- Only delete backup files after deleting the related tasks in the ATI program (if prior issues don't send it into a multi hour/perpetual delete)
- If you errors running a backup that show it tried to open a deleted backup file - you may have to manually rename/delete the archive.xml file and recreate all of your backups.

I would expand on your comments about using Windows to assign drive letters is that the letters assigned by the user should be letters at the upper end of the alphabet such as x or y or z. I would assign drive letters to storage devices where the drive letters are outside the range of the range of normally assigned letters. The insertion of a camera or flash drive, etc will cause Windows to assign the next drive letter and I prefer to make sure the next choice is not one that is already assigned to a removable device. Perhaps I am paranoid but I want to remove the chance of wrong letter being assigned--if I have any control over it.

Once the program has malfunctions or error out about a file not found, I have found the best solution to be creating a new task with the correct letter (after a fixed letter change to the external disk) and changing the old task to "not scheduled" or use the "Remove from list" option.

Regarding deletions. If you want the program to track the deletions, then the deletions must be done via the program delete options.
Any deletions outside the program will confuse the backup task--if it is still in use. Sometimes the resulting errors can be corrected by the user continually clicking the ignore option.

This link may be of interest.
http://forum.acronis.com/forum/54475

Good point on using higher letters for the drive designation.
I'm no sure how I got into the issue of new backup tasks (new name new destination) trying to open files for prior tasks when running the incremental or differential backups (the initial full ran without error). I'm still afraid that this will reoccur down the road if I start modifying may backups by creating new and different tasks.

Thomsas wrote:

I'm still afraid that this will reoccur down the road if I start modifying may backups by creating new and different tasks.

As I view this and the rules that I practice is to isolate the backups. Each new task points to a new folder or sub-folder, the backup file name differs, no edits to the task. Thus adding new tasks or removing old task should have effect on the running of other backup tasks. My experience has been that if I set up a custom task with automatic cleanup and do not later edit the task, the task will run successfully if left alone.

I had a similar problem. When daily bkup job A completed then went to consolidate it tried to access an old backup file from Job B that once existed on a removable drive--now disconnected. What's scary is that any unrelated backup task is messing with old, verified backup files ????
When I tried to get help via the Acronis chat I was told this was NOT a bug but it was a "software problem.' and I would have to pay to get help with it. I replied that it was either 1) a bug; or (2) a seriously poor intentional design.

Glad to see it's recognized as a bug. When will a new version be released and how do I get on the release notification list?
Thanks.

I had a similar problem. When daily bkup job A completed then went to consolidate it tried to access an old backup file from Job B that once existed on a removable drive--now disconnected. What's scary is that any unrelated backup task is messing with old, verified backup files ????
When I tried to get help via the Acronis chat I was told this was NOT a bug but it was a "software problem.' and I would have to pay to get help with it. I replied that it was either 1) a bug; or (2) a seriously poor intentional design.

Glad to see it's recognized as a bug. When will a new version be released and how do I get on the release notification list?
Thanks.

Yes, I agree it's just not good enough. I' am experiencing this all the time, particularly when my PC is not connected to my regular backup drive and my scheduled backup job has tried to run but obviously can't because it's unavailable. I've unchecked the "missed backup" parameter because I just want it to abort if the drive is not available and I don't want it to interfere with subsequent backup jobs but it clearly does. It keeps producing error messages in the system tray area and then if I run a manual backup to a completely different drive, that job then fails because it is trying to consolidate backups from the failed job !
The only fix I find is to run a validate on both jobs and opt to ignore the "missing" backups then everything seems to run fine again.
In summary the first fix needs to be a proper abort if backup drives are unavailable and the second is to ensure the history of backup files does not get mixed up.
Why should this be so difficult ?

Another option which exists is the "Drive Notify" program by MVPMudCrab.
This is a progam which advises the user to attach a specific backup drive by way of a Open Window Message.
Window remains open until the target disk is attached and recognized.

For more info, click on my signature link 1 below and browse to index item 4A and AA.
There is both a free version and a $9.99 automation version.

It works great for me.

Or another opiton is at this link.
http://forum.acronis.com/forum/42887

Thanks for the suggestion.
Just so I can try to understand how this might help does this process actually stop the Acronis job running if the drive is not found i.e the Trueimage Pre/Post command executes this program ( checking for the presence of the drive ) then aborts if not found after 60min or other user intervention. This then stops the scheduled Acronis job running ?
If so this probably will solve my problem.
I am justl astonished that Acronis TI2014 doesn't have similar functionality.
Perhaps we can have a definitive statement from Acronis as to what their software is actually supposed to do in this type of scenario.
There's not much point in designing a scheduling module that can't cope with the possibility that a backup drive or network location is temporarily unavailable.

Anna.Trifonova:

Thanks for your suggestion above (Turn on Automatic Cleanup). I always choose this option. My backup scheme is a full backup (weekly), keep no more than 4, and auto validation. It ran fine until the 4th week and then I had green checkmarks for these tasks:

The following backups have been successfully created
Validate Backup Archive
Consolidate Backup Archive

Then it errors with this:
Failed to exclusively access backup Z:\NetBakData\Mikey@KIWIASROCK\AcronisBackups\Imatch5_PackGo\Imatch5_PackGo_full_b2_s1_v1.tib during consolidation. Make sure the backup file is not opened in other applications.

This has now happened for the last 4 weeks. When I run validate I get no errors.

I hate to get rid of these backups and start over by having to create a new backup. See my post above (1/24/14) where the same issue occurred. An update from Acronis just came out. Was this update supposed to fix this? How should I proceed?

Thanks!

Mike

kgee wrote:

then aborts if not found after 60min or other user intervention. This then stops the scheduled Acronis job running ?

I am not sure that the job would abort as the batch program (DriveNotify) is active and still looking and waiting for the target disk tol be attached. Normal behavior for Drive Notify is to show the Attach message and wait. Once the disk is attached, the Drive Notify closes and the batch closes and TI can begin its backup.

M Link,

In my opinion, using consolidation is something I refuse to do. Consolidation is like fitting a1000 piece puzzle togther hoping all the pieces fit with many almost identical.
My preference that I promote is the Custom Scheme with automatic cleanup using the option "store no more than x recent chains"

Here is an example of full wtih cleanup. User can set the number of chains to be retained.

Figure 11-Full: Example of custom/full backup method settingsIf using Full backups only, this is a recommended method. These automatic cleanup settings will provide for automatic deletion of the oldest backups after the "Store no more than X number of chains" quota has been reached.
In this example, deletion of oldest backup will occur immediately following creation of backup #5.

Allow space for 1 more full backup in addition to "Store no more than X number of chains" as the program will NOT delete the oldest full until its replacement has been successfully created.

and here is an exampple if incremental and cleanup.

GroverH:

Thanks for the reply. I do have "Store no more than 4 recent versions". I have attached my custom settings in the first attachment. In the second attachment I have taken a screen capture of the log that shows the failure.

You mentioned consolidation. I did not choose this option (nor do I see this option in any of the Custom Tabs) in the custom settings. I was describing what I see in the log (which shows several steps as part of the backup). The log shows that after the backup has been created, it validates (which I chose in the Custom Settings) and then it says "Consolidate Backup Archive". What this does I am not sure.

I hope the attachments may help identify what may be going on.

Thanks for everyone's help that may be having the same issue.

Mike

Yes, my experience is exactly as M Link - I use GroverH's process, have never specified any form of consolidation but yet it does show that in the log- worse still trying to consolidate with completely unrelated backup files from a different drive - and then produces error messages but still actually produces the backup file.
The big problem with all these inconsistencies is having confidence that the backup would be of any use in the event of a catastrophic failure and this just doesn't fill me with confidence.
Also just back to one of my earlier points does anyone know what's actually supposed to happen when a scheduled job :
a) misses the schedule because the PC is switched off - on my system it still runs as soon as the PC is switched on ( despite the fact I have specifically unticked the option to run if missed )
b) tries to run because it get's to the scheduled time ( PC is running ) but the target disk drive is not connected. On my system it still tries to run and subsequently messes up other backups. Interestingly I am sure on earlier versions e.g TI2013 I used to get a message saying the job couldn't run and it would abort after a further 10min. Don't seem to recall seeing this now so perhaps something has changed.

I am going to step out on a limb here so to speak concerning this thread. It is obvious in reading through here that the TI 2014 app is a far departure from previous versions. In reading I am reminded of the growing pains users had with the transition from Win XP to Vista. I am going to suggest here that the release of TI 2014 is much the same as the progression from Win XP to Vista.

I believe this is a result of the advancement in OS structure specifically as it relates to the continued move of consumer grade products to more closely mimic Enterprise grade products. Reason, security and stability. Vista enhanced security in a huge way when it was introduced and wrought a large learning curve for users. Win 7 enhanced that even more and Win 8 has gone even further.

The common factor in this thread is Consolidation. That feature is obviously at the root of this discussion. So what is Consolidation and why the issues surrounding it.

Consolidation is the procedure of consolidating backups, a sort of backup of backups which in theory will compare a series of X number of backups in a chain, determine what has changed within those backups, then consolidate or create a new backup that melds the chain together into a new, and I hate say this but, complete backup of the chain. Consolidation originated in the Enterprise level product Acronis Disk Director and was targeted at IT departments need for such a tool. Seeing how this feature is now obviously tightly integrated in the TI 2014 product indicates the the TI product is incorporating these higher security level components into the the consumer grade product much like the advancement of security in Windows has undergone. I would suggest that this is necessary for the TI product because of the changes in the Windows OS. I am attaching a link here that talks about Consolidation and provides some interesting and educational reading for those whom care to know.

http://www.acronis.com/en-us/oem/resource/tips-tricks/2006/consolidatio…

Why do the issues here exist because of Consolidation. I will suggest that for the consumer level the problems arise because at the consumer level, security is the last thing on users minds and not being mindful of it brings with it problems like we see here. Basically users are prone to violate the best practices of security as it relates to data and therefore are faced with the issues discussed here and many others as well.

So having said all that it appears to me that some best practices regarding security of data must be kept in mind when deciding a backup scheme and the keeping of that scheme as well. Example Question: Why would you want to devise and schedule a backup scheme using a removable storage device and then not have that device attached to the system when desiring to perform additional backups? Obviously this practice has wrought havoc for the user. So bottom line is that is not good practice. From a security stand point, at least in the IT world, backup solutions are permanent in that they are not contemplated to be moved about nor the removal of the storage solution for the backup scheme or plan. The backup theory is not meant to be portable.

With that it appears to be obvious that the TI app has some default mannerisms that need to be addressed with consolidation and other features of sync and scheduling as well that were not thought of during the development of the product. I am sure it was not thought that users would attempt a backup when a previous device used for backup was no longer attached to the system.

I suspect that consolidation turning itself on even when clearly marked in the app to not run is a programming error and will be addressed. In the mean time users should gain at least a basic understanding of what consolidation is, how it works and what it does, and based on that knowledge make better decisions on backup schedules, schemes, and backup storage devices/locations. Doing so would greatly lessen the problems we see here.

How is not having a removable drive attached at the time of the scheduled backup different from network storage not being available at that time (for whatever reason)? It can happen. Shouldn't TI deal with it, report that it couldn't back up and give the user a chance to attach the drive (or get the network connection sorted out)?

I get the same error that it "fails to exclusively access backup L:\My Backups\Data (E)\Data (E)_full_b1_s1_v1.tib during consolidation. Make sure the backup file is not open in other applications."

I'm using the latest version of True Image 2015 and have successfully backed up other jobs with other drives in my computer but not this one. What's odd is the backup location listed in the error message is incorrect. The backup Drive location should be D:\Acronis\ Data E.

It seems to be trying to validate against a job that I previously removed. I used to have a job that pointed to that backup location but no more. I deleted the new job backup file, rebooted my computer and tried again but it still get the same error.

I'm using a custom version of the single version scheme. I also notice on all backup jobs that files older than 7 days are not being deleted like the job is supposed to do.

It's frustrating because when I click on the solution link none is found and now you guys want to charge me to call you when it looks like it's a bug in your software.

I'm hoping I get a prompt solution here in the forum.