Failed to lock the file
I am using True Image 2021 to back up two desktop machines, one wired and one wireless, to a NAS box which is wired to the modem/router. The scheme is to do a full back up and incrementals every 5 days, storing no more than 2 recent versions, on each machine. One backs up a 2:00 AM, the other at 4:00 AM.
It had been working without a hitch for months, but recently I started getting failure error messages for the wireless machine. The backup fails intermittently with one of two error messages, either:
'Failed to lock the file' or
'access to the file is denied'
It's weird because it only happens every 4th or 5th day. It will error one night, and complete successfully the next several days, but then fail again.
I recently had problems with my network, but not a strictly wireless issue, rather a whole network connectivity issue. It has been resolved, but I still keep getting errors with this one machine. There is a link after the error message that allows me to test the connection and it is always successful (see pic).
Any help or suggestions appreciated.
Rip
I would follow Steve's advise here. Many such issues can and are resolved by a machine restart.
I restarted and re-tried the backup twice, resulting in the same failure. The third time, it looked like it was going to fly, the progress bar started and timer started counting, but ultimately, it failed again, unable to lock the file. But, I'm pretty sure I saw a 'network not connected' message near the progress bar at one point, so I'm chalking it up to network glitches. I think his would explain why I don't have problems with the wired machine.
So, now there's another problem to tackle. Thanks your the input.
Ripper
I had the same issue with one of my laptops. Backup to NAS. Location validation with the normal credentials, is just fine. Multiple reboots of laptop do not solve the issue. Acronis 2021 up2date.
So hence I started looking what ATI could do with existing backups by trying to validate it. once validation was running I aborted it (assumin it indeed would be able actually go through the .tibx files).
Then I had a look if I could delete the oldest backup chain. That was also possible, a full backup and all of its incrementals depending on it, were deleted.
So far, so good. So ATI appears to be able to access the backup files.
After that I had no issue making the next backup. SO next time I will first try to do a validation, maybe that by itself might have been enough. I rather not have to delete a whole backup chain, just to have ATI be able to not run into the locked file issue.
The whole backup destination approach with the new .tibx format is rather cumbersome to say the least. Whenever anything changes, then you might be out of luck as you cannot change the destination. You can forget about all the backups you had before and start a new backup chain. I had this when I was making backups to a USB drive connected to the NAS. The exact device name - and because of that the whole UNC network path - could change - alas - at times on NAS end invalidating the configured initial location, not giving you an option to change/correct it. so you had to start completely anew with a backup chain. You could still import the old backups, but not continue the full/incr scheme I was using (1 full and 5 incr, one backup per week). so had to start each and everytime with a new full backup again.
In the end I simply added larger disks to the NAS, increased its filesystem to put the backups on the NAS internal raid system instead of a USB drive connected to the NAS. So that was the ebnd of that issue, but with the introduction of the .tibx format, some of the flexibility of the old format to simply move around the files however you saw fit, is much more limited...
For the rest I only had recurring issues with the locked file error from at least ATI2019 onwards then and again, which I never could really put my finger on...
This is terrible. This happens to me every other month and I have to lose all my backups and start again. There is 0 support from Acronins,