Skip to main content

The mysterious _v11.tib file access error.

Thread needs solution
Forum Star
Posts: 181
Comments: 1713

This issue with the mysterious _v11.tib file access error keeps coming up. I'm starting a separate thread in order to help consolidate user experience with it as right now I see it coming up in a number of different threads.

My feeling is that it has nothing to do with NAS credentials, but rather is a program bug that occurs after some sequence of events which we've not been able to determine precisely as of yet.

Acronis wants to close my support case, which is OK because I seem to have a working backup task now. But I have been trying to get this problem address by the development team.

It has occurred on both my PCs with tasks that have been running for months. In both cases, there was an interruption to the schedule before it occurred. On one machine, I manually stopped the task due to something else I was doing. On the next scheduled backup it failed. On the other machine, I was away on vacation when the backup was scheduled so the machine was off. Next time it failed. On my machines all failures were when running tasks by schedule, not manually.

The only way I could get by it was to 1) remove the backup task (but not deleting the files), 2) add the backup task from the latest backup file, 3) reconfigure the backup task as I'd like it. So far, so good.

I did a search of the forums for "_v11.tib" and have found a number of reported errors dating back to ATI 2017 and earlier which seem to be bringing up the same error. The conditions can vary, but the common thread is they all want to access a file which is not part of the chain. Here's a partial list of threads:

https://forum.acronis.com/forum/acronis-true-image-2018-forum/backup-fa…

https://forum.acronis.com/forum/acronis-true-image-2018-forum/problem-b…

https://forum.acronis.com/forum/acronis-true-image-2018-forum/how-safel…

https://forum.acronis.com/forum/acronis-true-image-2018-forum/one-my-ba…

https://forum.acronis.com/forum/acronis-true-image-2017-forum/backups-n…

https://forum.acronis.com/forum/acronis-true-image-2017-forum/user-stop…

https://forum.acronis.com/forum/acronis-true-image-home-forum-older-ver…

I would suggest to all that when errors occur and you look at logs, see if this is happening.

0 Users found this helpful
Legend
Posts: 109
Comments: 28229

Thanks Bruno for bring all these topics together.  Please drop a message to Ekaterina about this too and request she get one of the more senior Acronis Support folk to review both your support case and these forum topics where this has featured.

Forum Hero
Posts: 57
Comments: 9276

BrunoC wrote:

"This issue with the mysterious _v11.tib file access error keeps coming up. I'm starting a separate thread in order to help consolidate user experience with it as right now I see it coming up in a number of different threads.

My feeling is that it has nothing to do with NAS credentials, but rather is a program bug that occurs after some sequence of events which we've not been able to determine precisely as of yet."

Bruno,

I agree v11.tib error message is not related to network credentials.  It is related to TI being unable to access a backup file for any number of reasons.  I think that the v11 is an arbitrary number that TI gives the error.  I also think that the error occurs when TI determines or believes that the subject .tib file is already open or in use by another app such as Windows Explorer, another file browser type app such as an NAS web-UI management app, or an established network connection to the network share location of the subject file.

Kudos for doing the leg work to pull all related threads together on this error.  This should help in driving focus to the issue. 

Forum Member
Posts: 13
Comments: 77

As we have been looking at my situation in my thread here: https://forum.acronis.com/forum/acronis-true-image-2018-forum/backup-fa…

and you guys are suspicious I have the same issue I thought I should add the following.

 

I had TI 2016 working with a scheduled Differential backup task (Daily, full every 6 differentials, cleanup after 2 full cycles) and had zero issues with this bug. 

 

Installed TI 2018 with same backup system (new backup file not continuing old one) - will not commence backup.

Reinstalled as part of troubleshooting - still won't work.

Reinstalled TI 2016 - works immediately.

Reinstalled TI 2018 to troubleshoot more for support and help here - NOT working.

 

EDIT:

I found I can get a backup working to my NAS - only if I use an existing backup.

1. add existing backup (browse to \\192.168.0.3\   ...)

2. reconfigure 

3. backup .... and it works. Same settings as I normally use and my normal directories.

 

 

 

 

Frequent Poster
Posts: 4
Comments: 566

BrunoC, mgrobins, I have asked the Development Team to have a look into this issue, check the reports and all the information you've provided.

It is clear that it is hard to replicate the issue on demand and catch the problem in the program, but hopefully we will be able to get to the root cause and correct it.

Thank you!

Legend
Posts: 109
Comments: 28229

Slava, another forum topic on this topic in the 2017 forums this morning:

See Unability to create a fresh backup task for a partition I previously had a task set up where another report of the _v11.tib is given.

In reply to by Slava

Forum Member
Posts: 13
Comments: 77

Thank you Slava :).

I am attempting to get additional reports to the support team as well.... just having issues with no internet (tethered to 4g on my ph just now to message), and accessing your ftp site to upload.

 

Discussion on my own thread has led us toward Bonjour as the possible cause or link to issues I am facing.

It was mentioned TI 2016 used the printer element of Bonjour and TI 2018 is using a newer version and structured differently in its interface with bonjour.....