Windows 10 to NAS Backup Will Not Progress Pass 55GB
I am trying to backup ~700GB to my Unraid NAS. I have over 30TB of free storage on this server. Anytime I try to backup to this server now, the backup hangs at 55GB. After 30 minutes or so, it will say, "The latest backup has been stopped. It will be restarted at __:__. Failed to lock the file."
If I reduce the backup to less than 55GB, it will complete successfully. It's also worth noting that until recently, I've been able to back up to this exact server with no issue. I've tried manually transferring files to this server via SMB (almost 100 to 200GB or so) and it transfers no problem.
Any suggestions would be greatly appreciated. I've uninstalled and reinstalled Acronis, I've reformatted the host PC, I've installed Acronis on another device, and no matter what, the issue persists. Any suggestions are greatly appreciated.

- Log in to post comments

Thank you for these suggestions. I have checked network connectivity and confirmed that my network is not experiencing any kind of interruptions. I have also checked and rechecked the NAS permissions, including making the file publicly available. And I have updated all drivers and software on Unraid, and it is still hanging at the same point.
- Log in to post comments

Download a copy of the MVP Assistant log viewer tool and use this to look at the logs to see if they show any issues during the operation process?
The latest version of the new log viewer tool is at the link below.
MVP Assistant Version 2.6.3 is available.
If you have Disks & Partitions backups created on ATI 2020 or later using .tibx files, then look in the Backup Worker logs.
If you have Files & Folders backups using .tib files (or Disk backups from earlier versions using .tib files) or using Cloning then look in the Demon logs.
Other logs are shown by the MVP Assistant under the 'Active Logs' heading of the Log Viewer page of the Assistant, i.e. Media Builder.
The Schedule2 log contains information related to scheduled task but is one of the more difficult logs to read / work through.
The log files should be zipped to preserve their original file names if sharing in the forums and would need to be less than 3MB in size, otherwise you would need to share the zip file via a Cloud share service such as OneDrive, Dropbox etc.
- Log in to post comments

Download a copy of the MVP Assistant log viewer tool and use this to look at the logs to see if they show any issues during the operation process?
- Log in to post comments

For some reason it didn't upload. It also won't let me add a hyperlink so you'll have to replace [dot] below with a period.
Here is a link: drive [dot] google [dot] com/file/d/1Feu5DSTZPs_aiFIqCXOoGdvJKXsGozXP/view?usp=sharing
- Log in to post comments

Robert, thank you for the Backup Worker logs - these show that the initial backup attempt was progressing correctly then it hit an error as shown below:
11/07/2023 07:28:09:164 AM -07:00 23140 I00000000: Pid: 3860 type=log; level=inf; message=pcs_co_file_sync(\\?\UNC\192.168.1.200\acronis\My disks.tibx) failed: 64 (pcs_err=4);
11/07/2023 07:28:09:164 AM -07:00 23140 I00000000: Pid: 3860 type=log; level=inf; message=io#1: reopen: sync failed with err -5017;
11/07/2023 07:33:27:670 AM -07:00 23140 I00000000: Pid: 3860 type=log; level=inf; message=io#1: reopen: started, timeout 0, previous error -5017;
11/07/2023 07:33:27:681 AM -07:00 23140 I00000000: Pid: 3860 type=log; level=wrn; message=watchdog: pcs evloop #0 was not working for 318 sec;
11/07/2023 07:34:37:706 AM -07:00 23140 I00000000: Pid: 3860 type=log; level=err; message=io: failed to open '\\?\UNC\192.168.1.200\acronis\My disks.tibx' (win_err=-32);
11/07/2023 07:34:37:706 AM -07:00 23140 I00000000: Pid: 3860 type=log; level=inf; message=pcs_sync_open(\\?\UNC\192.168.1.200\acronis\My disks.tibx) failed: 32 (pcs_err=22);
11/07/2023 07:34:37:706 AM -07:00 23140 I00000000: Pid: 3860 type=log; level=err; message=io#1: failed to open "\\?\UNC\192.168.1.200\acronis\\My disks.tibx" (pcs_err=-22);
11/07/2023 07:34:37:706 AM -07:00 23140 I00000000: Pid: 3860 type=log; level=err; message=ar#1: reopen failed: failed to open volume 0: -5015 Object is locked;
11/07/2023 07:34:37:706 AM -07:00 23140 I00000000: Pid: 3860 type=log; level=err; message=io#1: reopen failed (time left 0/0ms): -5015 (Object is locked);
11/07/2023 07:34:37:706 AM -07:00 23140 I00000000: Pid: 3860 type=log; level=err; message=io#1: sync result -5015;
11/07/2023 07:34:37:706 AM -07:00 23140 I00000000: Pid: 3860 type=log; level=err; message=ar#1: autocommit failed (err: -5015, Object is locked);
11/07/2023 07:34:37:729 AM -07:00 23140 I00000000: Pid: 3860 type=log; level=inf; message=ar#1: archive closing \\?\UNC\192.168.1.200\acronis\\My disks.tibx;
The subsequent backup attempts all fail because Acronis cannot open / lock the destination archive (.tibx) file on the remote location.
11/07/2023 07:38:39:437 AM -07:00 15472 I00000000: Pid: 14472 type=log; level=err; message=io: failed to open '\\?\UNC\192.168.1.200\acronis\My disks.tibx' (win_err=-32);
11/07/2023 07:38:39:437 AM -07:00 15472 I00000000: Pid: 14472 type=log; level=inf; message=pcs_sync_open(\\?\UNC\192.168.1.200\acronis\My disks.tibx) failed: 32 (pcs_err=22);
11/07/2023 07:38:39:437 AM -07:00 15472 I00000000: Pid: 14472 type=log; level=err; message=io#1: failed to open "\\?\UNC\192.168.1.200\acronis\\My disks.tibx" (pcs_err=-22);
11/07/2023 07:38:39:437 AM -07:00 15472 I00000000: Pid: 14472 type=log; level=err; message=ar#1: failed to open archive path="\\?\UNC\192.168.1.200\acronis\\My disks.tibx" mode=rewrite uuid=00000000000000000000000000000000, err=-5015 (Object is locked);
11/07/2023 07:38:39:437 AM -07:00 15472 I00000000: Pid: 14472 type=log; level=err; message=unable to open archive file (err -5015);
- Log in to post comments

Robert, when the failure happens, can you check the Unraid NAS to see if it is still at 192.168.1.200. Just wondering if something could be timing out and incorrectly assigning a new IP. Have you made any changes to your router or NAS settings?
- Log in to post comments

Robert, thank you for the Backup Worker logs - these show that the initial backup attempt was progressing correctly then it hit an error.
Robert, when the failure happens, can you check the Unraid NAS to see if it is still at 192.168.1.200. Just wondering if something could be timing out and incorrectly assigning a new IP. Have you made any changes to your router or NAS settings?
- Log in to post comments

How is your PC connected to your local network where the NAS is located?
There could be a faulty network adapter, cable, or if using a USB network connection, the possibility of Windows selective suspend coming into play?
- Log in to post comments

I am connected with a fiber NIC installed in both the NAS and in my PC, using a 10Gbps fiber connection.
- Log in to post comments

Thanks for that information Robert, has anything changed in the period between when all was working correctly and this issue arising?
Do you have any other network connections that you could try using?
Have you considered testing with a different backup application such as Macrium Reflect to see if the same issue is shown or not?
- Log in to post comments

Steve: I did an operating system update on the NAS as well as updating some hardware in it. This is when the issue started. I just used Macrium and was able to do the full backup.
- Log in to post comments

Robert, given that you are running ACPHO latest build #40338 (per the logs provided) and this issue only occurs when using this product, not with Macrium, then this is one that Acronis need to investigate in more depth via your open support ticket (05967007).
- Log in to post comments

Robert Paolella wrote:Steve: I did an operating system update on the NAS as well as updating some hardware in it. This is when the issue started. I just used Macrium and was able to do the full backup.
Hello Robert!
I have updated the ticket and informed the team about the updates you mentioned.
You can expect a contact from our side as soon as possible.
Thanks in advance!
- Log in to post comments