ATI 2020 "Failed to lock the file"

Fred, you would need to look at the backup logs for the time when you saw the error message about failing to lock the file to try to identify what actual file may have caused the error?

The MVP Log Viewer tool can help to a certain extent, but the most detailed log information is stored in the new backup_worker logs which are not offered as an option by the Log Viewer, so you would need to go look at the raw files in C:\ProgramData\Acronis\TrueImageHome\Logs to get an answer.

Personally, the only times I have seen similar issues have been caused by my security / antivirus software wanting to quarantine something it thought was suspect but turned out to be a false-positive warning.

Thanks once again Steve.

I downloaded and ran the Log Viewer and I don't see anything of note. In the log there are twelve occurrences that show the failure. With the exception of the timestamp they all exactly like this. I will whitelist ATI in my security software and see what happens tonight.

phred wrote:

My questions are:
1- what was locking what file and preventing the backup from running?
2- why did I get two emails, a minute apart, for one successful backup?
3- why wasn't the successful backup appended to the original tibx as it had done for the previous days?

For question #3 - could you provide a screenshot of the file information compared to the original in Windows Explorer (particularly file size)?  I suspect it is a new backup chain (a new full).  Acronis will use the existing .tibx for an incremental chain, but will create a new file when a new chain has been started.  If using a single backup scheme or a differential backup scheme, there is a new .tibx created each time a backup is run.

Regarding question 3, I'm not sure exactly what you mean by "...the file information..."

The only file info I can provide is a screenshot from my file manager. Which I suspect confirms what you suspect. Namely that Susan.tibx ran for 1 full and 6 incrementals, and then on the next run, it ran another full, naming it Susan-0001.tibx. The backup scheme I'm using attached, as is a shot of the file manager.

Interesting that I got no 'file is locked' error from last night's backup. But I did get a "Network disconnected" error three times in a row over the course of one minute. Followed by a "backup succeeded" notice. I guess the good news is that with the previous "file locked" error and with the "network disconnect" error, ATI keeps trying. And that's a good thing.

I saw Steve's thread today about using .tib instead of .tibx. I don't like the new format only from the standpoint of not know what's going on. Yes, I can see the file date has changed along with the file size. But the .tib format (at least from the TIH2014 version I was using) has more useful information in the filename. Do you know if I use Steve's method to switch over to .tib will it show filenames like this:Susan_full_b2_s1_v1.tib and Susan_inc_b2_s2_v1.tib as I find them much more informative.

Thanks.

Correct. That's what I was looking for. So it looks correct to me.

I haven't played around with modifying the file format yet. I suspect it would name them the old way though, but maybe Steve can confirm. It was using the old naming method in 2015-2019 too.

I've been advocating for file name change of the new .tibx since beta too. I doubt it will happen as the Backup 12.5 version for business is using the same name scheme we are seeing now. I greatly prefer the old file names too and suggested some options for .tibx but not sure if they will ever be considered.

Submit in app feedback though! The more who request, the more likely it might happen.

Thanks Bobbo. I've just submitted feedback asking for an option to let the user choose between the two formats. Now I'll cut and paste my comment from above into Steve's thread about changing to .tib.

Thanks Phred!