Aller au contenu principal

Sporadically file lock error ...

Thread needs solution

Hi,

we are using one storing location based on a QNAP NAS share. Two jobs are configured to use this storage location, one short starting at 9:00pm and one long starting at 8:00pm. Sporadically we get errors related locking a file when the job tries to delete old backups based on the retention time.

Error codes 22, 217, 12, 23 and 65520 (in this order) are reportet in details.txt. Error message like "process not able to access the file because it's used from another process".

We wondering because the two jobs are handling different files / different sources. Are there any problems using one storage location with multiple jobs / is this scenario supported?

Many thanks,

Erik

0 Users found this helpful
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Contributions: 250
Commentaires: 7092

Hello Erik,

Backing up data from multiple sources to the same location shouldn't be an issue. Any device passively connected to NAS may hold the lock at any time, 3rd party software and even native NAS file scan and security measures can be locking the file. If the NAS has any means of running the audit log you can double check which users are accessing the files at which times and check for the conflicts. If you can reproduce the issue, I'd suggest collecting the Process Monitor logs from the device with the related Agent https://kb.acronis.com/content/2295  and looking through the log. Messages in this log may shed the light on what processes are locking the archive. If the root cause is still unclear, it's worth raising a support ticket for investigation

Hi Erik,

What build number are you running.

We had the exact same issue with our NAS server and upgrading to build 10130 solved our problem.

Regards

Duncan

Hi Duncan,

currently we use Build 11010. Yesterday I did a firmware update and reboot of our NAS system, last backup was fine.

Erik

Hi Ekaterina,

you're right, file lock from a different system was the problem. We had some Windows Server Backups configured to use the same share as ABA 12.5. Now we're using a new share for this type of backups, I'm shure that this was the reason.

Many thanks and have a nice weekend ...

Erik

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Contributions: 250
Commentaires: 7092

Erik, good to hear of positive results! Thank you for the update and sharing the information of how you resolved this issue which will be of value for other users.