Full backups on NAS share "looping"
Just curious if anyone else is experiencing this issue. I have a custom backup scheme of a full followed by week's worth of incrementals saved onto my Synology NAS via CIFS. I had a ridiculous amount of trouble getting TI2017 to actually attach to my NAS, involving finally ending up setting up my own DNS server, but that's whole other set of issues, though I wonder if it could be related.
Anyway, what I've been seeing and I'm curious if others are experiencing this, is that randomly - not always - a full backup will begin to repeat back to back. Like if my backup totals 150GB, I will have a 150GB file called xxxx.tib, then another 150GB file called xxxx-1.tib, then xxxx-2.tib, and so on until it either suddenly decides it's satisfied with one and stops, or more frequently the drive quota is exhausted and the job fails. At which point I have to discard all the backups and take a new full.
I certainly didn't have this before 2017, and I don't actually recall it happening before the last major patch. Is anyone else seeing this, or am I alone in having this problem? I don't see anything that jumps out at me as a cause in the logs, and it seems to be perfectly happy doing its thing until it suddenly fails with an out of disk space error.


- Log in to post comments

Thanks for the log viewer advice! Got some interesting info out of the logs. One one of the looping full backups it says it completed with errors, in the finalization after completing the actual backup process I've got a few lines that probably indicate a cause, I just have to figure out exactly what they are referencing:
Failed to open data stream. Try to remove the backup from the list, add it again by clicking 'Browse for backup' and recreate the backup settings
then it's followed by
The process cannot access the file because it is being used by another process
Now the question is, are those errors referencing the backup file itself or the backup status database on the local disk? It looks like next steps are looking at the Synology for any potential SMB file locking issues (disable opportunistic locking, etc.), and checking if Avast is having one of it's spectacularly unhelpful moments and locking files up. Whatever the root cause, it seems to be new, as it's only started after the last build. It could be the NAS bug like you said. I have another NAS, a cheap and slow old thing with pretty much the simplest SMB service possible, I'll set up a backup with identical settings on that and see if I can replicate the behavior to rule in or out the Synology as the cause.
- Log in to post comments

You're welcome - it's a really nice logviewer and fills the void until Acronis builds their own back in.
As a quick and easy test, I'd create a new backup task to the the existing NAS, but try using the UNC pathc with IP instead of the built in NAS option or even the UNC path with hostname.
To get around the initial issue of the Acronis bug with it not accepting credentials while you have mapped drives, stop and start the workstation service before you try and that should allow it to authenticate and save the task. Once it's saved, it will continue to work - it's just a bug getting the credentials set initially when mapped drives are connected.
- Log in to post comments

See new KB document: 59051: Acronis True Image 2017: Connection to NAS fails with errors "Connection failed", "Failed to check credentials", "Can not find files and folders" which offers: Replace TrueImage.exe and ti_managers.dll with fixed versions that you can download from the link provided in the KB document.
- Log in to post comments