Full backups on NAS share "looping"

I will have a 150GB file called xxxx.tib, then another 150GB file called xxxx-1.tib, then xxxx-2.tib

Hi Matthew,

the -1, -2 at the end usually means that the backup job did not complete for some reason and Acronis is trying to complete it again, using the exact same name, so it has to append a number to the end since the other file already still exists.  I don't see this very often, but have a few times.  Generally, it occurs when there is some kind of network hiccup and instead of Acronis picking up where it left off, it seems to want to start over. 

Grab FTRPilot's logviewer app and check some of the service.logs for clues that might be tucked in some of the log files.  

It could be related to the NAS connectivity issue you experienced and because you're using DNS hosname instead of IP.  I use hostname as well, but am not running local DNS.  

1) The NAS connectiivty issue is documented now.  It generally is a problem if there is ANY mapped network drive in Windows.  This is defintiely a bug.  This can be circumvented a couple of ways.... a) tempoararily start/stop the worskation service before creating a new NAS backup task or before editing an existing one... b) unmap Windows mapped drives first, make your Acronis NAS changes and save and then map the network shares... c) edit your local host file with a direct mapping of the NAS DNS name to the IP (make sure the IP is static or has a DHCP reservation).  This should get fixed in the next release (hopefully) and is definitely a new bug introduced in 2017 5554.

2) Don't use the newer NAS option in the backup.  INstead, use the old "browse" / network option and enter the UNC path via IP isntead of the DNS Host name

As for other connectivity issues, could your NAS or home router being timing out, having latency or dropping packets during a large file transfer?  Perhaps, run a steady ping from sysetm to the NAS durin the course of a backup and save it to a .txt file to review later for latency or disconnects.  

example:

ping -t NASIPADDRESS > C:\username\desktop\NASPINGBACKUPTEST.txt

Are your NAS and PC both hard wired? Double check the cables and reseat them if they are.  Any extra switches in the loop (be careful of green switches that get lazy and go into power saver mode.  Speaking of power saver, during the backup, is your PC or NAS trying to enter power saver, USB suspend, etc. since there may be no physical contact for a large part of this time?  I have disabled power saving on my WD-MyCloud 4TB and althoguh my PC is set to balanced power, I have disabled USB selective suspend, don't allow the hard drive to enter power saver for at least 2 hours, etc.  

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.

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.   

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.