Direkt zum Inhalt

Operation has been stopped

Thread needs solution

I've set up a scheduled backup everyday at 12:00AM. Backup destination is a NAS. NAS is waken up before the backup and put to sleep after backup (with pre/post commands configured in backup job). Backup scheme is incremental with a full backup every 10 versions.

This has been working fine for a long time. Recently, it kept saying "Operation has been stopped" but no obvious errors. When this happens, the NAS is at the on state. I tried to review the logs but not sure which log to look at. I noticed that on the stopped backup, it says the method is "Full" while it was supposed to be "Incremental". Not sure if that's relevant though.

If I click "back up now" button, the job completed successfully and it shows "Incremental" as it was supposed to be. How can I find the root cause of the problem? Thank you!

Acronis True Image 2020 build 22510
Windows 10 Enterprise 64 bit, version 1909, build 18363.592
Lenovo ThinkPad P50
QNAP TS-870 Pro

0 Users found this helpful

Michael, what type of backup files are being created for your backup task to the NAS?  Are they the older .tib files or the new .tibx files created by ATI 2020 for Disk backups?

For the older .tib files, then the MVP Log Viewer tool (link in my signature below) can be used to review the log file for your backup, clone or other operation.

For the new .tibx files, there is no option in the tool for the backup_worker log files that contain the detailed messages for these backups, so you would need to open C:\ProgramData\Acronis\TrueImageHome\Logs\backup_worker and open the log files in Notepad etc to look through them.

If you need help with reading / understanding the logs, then please zip them (to preserve the file names) before uploading as a file attachment to this forum topic.

Steve,
It's the tib files.  What's the difference between the tib and tibx files?  How does Acronis TrueImage make the decision to create which one?
 
Attached are the logs (for some reasons I cannot upload the 2M zip file).  Thank you very much for your help!
 
 

Michael, your ti_demon logs are showing connection issues to your QNAP location as per the entries below from today:

29/01/2020 00:03:09 :703   Writing incremental version to file: Micron_inc_b2_s3_v1.tib
29/01/2020 00:03:09 :747  Error 0x1e50023: Cannot access backup file \\QNAP\Backup\Micron_inc_b2_s3_v1.tib. Please ensure that you entered the correct credentials for the network share.
29/01/2020 00:03:39 :748  Error 0x1e50023: Reattempting the operation. Error: Cannot access backup file \\QNAP\Backup\Micron_inc_b2_s3_v1.tib. Please ensure that you entered the correct credentials for the network share..
29/01/2020 00:03:39 :753   Writing incremental version to file: Micron_inc_b2_s3_v1.tib
29/01/2020 00:03:39 :797  Error 0x1e50023: Cannot access backup file \\QNAP\Backup\Micron_inc_b2_s3_v1.tib. Please ensure that you entered the correct credentials for the network share.
29/01/2020 00:04:09 :797  Error 0x1e50023: Reattempting the operation. Error: Cannot access backup file \\QNAP\Backup\Micron_inc_b2_s3_v1.tib. Please ensure that you entered the correct credentials for the network share..

The above sequence of log entries is repeated until all the error retries are exhausted.

29/01/2020 00:15:39 :399  Cannot access backup file \\QNAP\Backup\Micron_inc_b2_s3_v1.tib. Please ensure that you entered the correct credentials for the network share.
To specify another location; click Browse.: ⎂Retry//⎂Cancel//: User response:
29/01/2020 00:15:39 :402  Error 0x101f6: Write error.
29/01/2020 00:15:40 :449  Terminated by user.

As shown above, the backup fails and offers the option to Retry or Cancel but doesn't get any response so cancels the task.

The same final sequence of entries was shown on 19/01.

19/01/2020 00:05:28 :829   Writing incremental version to file: Micron_inc_b1_s4_v1.tib
19/01/2020 00:05:28 :867  Error 0x1e50023: Cannot access backup file \\QNAP\Backup\Micron_inc_b1_s4_v1.tib. Please ensure that you entered the correct credentials for the network share.
19/01/2020 00:05:28 :867  Cannot access backup file \\QNAP\Backup\Micron_inc_b1_s4_v1.tib. Please ensure that you entered the correct credentials for the network share.
To specify another location; click Browse.: ⎂Retry//⎂Cancel//
19/01/2020 00:15:28 :312  Cannot access backup file \\QNAP\Backup\Micron_inc_b1_s4_v1.tib. Please ensure that you entered the correct credentials for the network share.
To specify another location; click Browse.: ⎂Retry//⎂Cancel//: User response:
19/01/2020 00:15:28 :313  Error 0x101f6: Write error.
19/01/2020 00:15:29 :310  Terminated by user.
 

Steve,
 
Thank you for your help!
 
My QNAP NAS is acting as a SMB file share.  Acronis backup script wakes up the NAS by WOL(Wake On LAN).  Then trying to copy files to NAS.  After backup, Acronis script put the NAS into sleep.
 
Since the problem is intermittent, what is the best way to configure Acronis so it's more fault/delay tolerant?  e.g. number of retries, etc.?

Michael, if you are issuing the WOL packet from a Pre Command at the start of your backup, then you may want to set a small delay to allow the NAS to be 'fully awake' before the backup is started by ATI.

It is also possible that the NAS is going to sleep while waiting on ATI for further data, so you would need to check what settings control that aspect on the NAS itself?