Can't Backup to Synology NAS "Connection Failed"
Hello Acronis Users/Support
I bought ATI17 and try to backup my whole Computer to my Synology NAS..
In explorer under windows i'm connected with some drives on the NAS, the backupdrive too! I now opening ATI and klick on backup, from there i choose my NAS. Now i have to enter Username and PW (the user on the NAS) but it tells me everytime "Verbindung Fehlgeschlagen" (connection failed).
User and PW are correct, its the same user i take for mapping drives in explorer. I then made another User on my NAS just for acronis, but i didn't help.
i tried:
\\192.168.0.50\User or just the User or \\synologynas\user but it wont connect. Going from explorer via unc path etc. i can read and write, everything is working w/o problem...
I'm using ATI since version 10 and never had such problems. So whats wrong?
please help, thanks!


- Se connecter pour poster des commentaires

If your installed TI 2017 version is 5554 then you should attempt the suggestions found in the link below:
- Se connecter pour poster des commentaires

This is exactly why I hate installing new versions of TI. If I had a dime for every time a new version came out and fouled up NAS backups...
The 2016 version came out and was just fine though.
So, this time, when the 2017 version came out, I bought the license and sat on it since August (August?). I saw a big patch come out a week ago. I thought, surely it's okay to jump in at this point. Nope. Now you have to patch the software (manually) and in Safe Boot no less.
Acronis, get a Synology NAS in your QA department and attempt just one test. Just one. It's really not hard.
- Se connecter pour poster des commentaires

David, I have a Synology DS215 NAS myself and have had no problems using it with ATIH 2017 without needing to put on the new patch from https://kb.acronis.com/content/59051 so there must be other variables at play here too.
- Se connecter pour poster des commentaires

Im with Dave...
I just upgraded from TI2016 and so first thing I do - check my existing backups and first attempt to go to "options" on my backup which is located on my NAS ( a ReadyNas 102) I get the credentials popup.. WTF? its a completely open share!!! I have no idea what it expects!!
I will try the manual fix/update - but I am with David.. it is really not good enough.
The KB seems to talk about "limitations of NT".. I really dont care.. your products needs to "just work"..it is really not good enough. I am fairly tech/competent - but any kind of "manual fix" is really poor.
TBH.. you really should ensure the base is really solid before you waste time on crap features (for me) such as "manage from your mobile device".. serioulsy.. who gives a shit, if the core does not work and "you cant backup to a network share" without grief?
You will be sure to hear more if the workaround does not work..
And I assume you will get it sorted for next patch? I dont expect I will need reapply manual fixes every time you release an update?
Cant say I am happy :(
Cheers
- Se connecter pour poster des commentaires

Quick update - the good news.. the KB59051 fix seems to have worked for me, even though I was not getting the error scenarios exactly as described (i.e. I was not getting "errors".. I was just getting the credentials prompts)
Cheers..
- Se connecter pour poster des commentaires

Spoke too soon.. My backups going from my PC to the NAS worked fine.. but the backup from the NAS to my machine failed, saying it could not see the files on the NAS to backup.
I tried reselect the files (since I could navigate to the NAS OK), but I think something was corrupted - as it ignored my selections (where I had excluded a sub folder) and backed up the full NAS directory (96GB instead of 7GB).
So I ended up deleting the old backup and recreating from scratch - and it seems to be working.
Really unimpressed.. :(
Cheers
- Se connecter pour poster des commentaires

See also: Forum post 127047. I suspect it's related.
Larry
- Se connecter pour poster des commentaires

Ha ha - having experienced the same problems as you (as well as many more) I've decided to ditch ATI 2017. There are too many low level issues that make it too unreliable to trust.
I regularly receive errors when attempting to backup (can't find previous files) and worringly similar errors (can't find version 1) when trying to restore. How can a product suffer from so many 'corrupt' XML database issues?
- Se connecter pour poster des commentaires

I have just upgraded from 2015 to 2017, I am beginning to regret it, to avoid confusion I logged three seperate threads, if people have difficulties connecting to their Synology the first link may help them:
https://forum.acronis.com/forum/127610
https://forum.acronis.com/forum/127611
https://forum.acronis.com/forum/127612
EDIT:
Well my first entire PC backup (Windows 10) to Synology DS410 worked, I've also logged those three issues to Acronis support.
- Se connecter pour poster des commentaires