Skip to main content

Cannot backup to Synology NAS

Thread needs solution

Trying to do a simple backup to a Synology NAS (DSM 6).

Authenticates just fine. Then...

See pdf for quick easy visualiztion of issue.

Thanks for any help!

Jeff

Attachment Size
forum_post_-_cannot_backup_to_nas.pdf 120.51 KB
0 Users found this helpful

Here are some links that may be helpful in troubelshooting the issue.  Is this a recent occurance (ie. the task used to work but does not now)?  What OS are your using?  If Windows 10 what build?  Your error indicates a possible dropped connection so you should have a look at power settings making sure they are not set to turn off the connection after a set length of time.

https://kb.acronis.com/content/45527

https://kb.acronis.com/content/58000

Hi Enchantech and thanks for the reply. Unfortunately, I've already been there and tried info from both of the links provided.

It is a "Trusted App" (firewall) and authentication works fine to MAP to the ATI Destination, just not the ATI backup process.

Problemn has been from day 1... about 4-5 months ago. Thought I would give this a try before looking at other solutions.

OS = Win7 Ultimate 64-bit

Network stellar! Rock solid backbone in house.

Drive time outs are not the issue... this problem happens immediately after mapping to the destination drive and hitting "Backup Now". Plus, thinking it (network/NAS) might be the problem, I made sure the drives were spun up before attempting during one evolution.

This is a real bummer and PITA since I have moved a lot of data to the NAS. It has its own backup to an external set of drives, so not too concerned about data loss, though I am tinkering with the thought of adding a Cloud backup to the NAS as well.

Anyway, thanks for the advice. Any other thoughts? Looks like you are pretty familiar with the product line...

Most often hangs in backup if not time out related would be disk corruption or file system error.  Have you run diagnostics on the NAS using the Synology Diskstation Manager:

https://www.synology.com/en-us/knowledgebase/DSM/help/DSM/StorageManage…

You can run chkdsk on your backup source disks to check for disk integrity (chkdsk /f /r)

If backing up Windows system disks run sfc /scannow on the C: partition.

You can sometimes narrow down a problem source disk if the issue is full disk related by backing up disk partitions one at a time.  Often the trouble partition will surface when doing this.

Jeff,

Something to try and I'd be curios to know your results:

1) kill your NAS backup task - delete it (you don't have ot delete the backup files - if there are any, just the task settings).

2) Then go into the registry and delete everything under the SMB key as described in this KB article:  https://kb.acronis.com/content/58004

3) Reboot

4) Launch Acronis and create a new backup task to the NAS and re-enter the credentials when prompted - make sure to test the connection to see successful before connecting.

Also, there is a Windows limitation that prevents a Windows user from having multiple connections to the NAS with different NAS profiles.  So, if you have one NAS logon say for some media shares, and are trying to access a NAS share to backups using different NAS credentials - it may fail because Windows wil only let you access the NAS share with one account (NAS account) at a time (under that Windows session).  It seems like synology has a software for accessing the NAS, so don't have that authenticated/running when trying to connect in Acronis as that may be part of the block. 

 

Hi Enchantech,

Pipes are clean! :)  Storage Manger completed with no errors, chkdsk and sfc = no errors found.

Currently, have 8.65 Tb available to backup to.

Came home to find ATI churning away trying to backup to the NAS as I forgot to delete that profile. Local USB drive is fine though. (Thought ATI quit after 5 attempts to perform backup?)

Thanks again for help... it IS appreciated!

Jeff

Hi Bobbo_3C0X1,

So it appears this regedit/key delete worked! Now, thing is the "task" worked ONCE before. So I will repost later in the week when the "Scheduled Task" is supposed to run, if or not it completes.

Wierd thing happend though, my attached (USB 2.0 drive) task failed!? It had been working fine up until the regedit, which should have nothing to do with this particular "task" since it does not require authentication. Re-built the local "tasK" and it worked fine... strangest thing...

Also, before I forget, the Synology NAS is NOT listed in the SMB Devices list when I build the task to backup to it. I get at it, and authenticate, via the "Network" browse option. Do not know if this makes any difference to ATI given teh SMB reg key.? Lastly, rebuilt NAS task, it authenticated initially, errored as usual, then ran perfectly??? Strange huh?

Ok, so I'll re-post when the network task runs again.

THANKS to EVERYONE to date for their assistance!

Regards,

Jeff

Jeff...I am using a Synology NAS (which I really like), and may be able to help.  

In ATI 2016, my Synology appears under Network, not under NAS...this is fixed in ATI 2017.

Are you validating the backup when it is created?  I believe your original error message could be caused by validating the backup when it is created.  If you are, then I recommend creating a backup task without validating and see if it completes without error.

As a beta tester for ATI 2017, I can state that ATI 2017 is much improved in NAS support.

Regards

Hi FtrPilot,

Thanks for the post.

(I like my Synology too... sort of, I was hoping for a better video experience. Though it is very stable otherwise and easy to setup and get to internally and externally. PLEX runs fine but NAS falls on its face at higher resolutions. Hate to look at a new one... hoping that maybe a SW driven boost may be in the offing and not only HW, but it probably is wishful thinking on my part! Don't quite understnd the thinking with the lower end chips???)

In answer to your question, yes actually, I am Validating the backup. So is it a bug that it does not work? Do you have any idea if they are planning to fix?

I'll repost after the "Scheluded" run end of the week. Thanks again.

Regards,

Jeff

Yeah, seems it could be a bug. Others have reported that the backup "fails" when validation is turned on to run in conjunction with the backup.  The work-a-round is to disable validation in the backup task and then manually validate the job after that.  For what it's worth, I pretty much never validate my backups.  INstead, I just try to double click the .tib files and make sure it opens... or right click "mount".  If those work, you're in good shape.  For a real validation though, I will restore an image to a VM or a different disk in my computer and make sure it boots like it's supposed to.  VM's make this realworld validation a little bit easier to do. 

To all who commented and offered suggestions/support... my apologies for not replying until now.

Bobbo_3C0X1... your suggestion seems to have worked! I did wipe the Reg of the key you suggested and re-authenticated and the backups, again, seem to be running just fine. I know it has been a month since the last post, but between wanting to make sure it worked and life in general, I am just now getting around to replying. My sincerest apologies to all.

Hopefully this gets resolved in the 2017 version and the Validation issue is corrected. I am still waffeling on the upgrade to 2017 though... if anyone has any convincing arguments, I am open to them!

Thanks again to all contributors!

Regards,

Jeff

Jeff,

Thanks for the feedback...it's never too late for feedback.

ATI 2017 improves NAS support, however I am unsure if the validation issue is corrected...personally, I don't perform validations, like Bobbo, I perform a "Mount" for confidence and occasionally, I perform a "Restore" to a spare drive.   

Acronis have a no questions asked refund policy as long as you are within 30 days of purchase.  So, you could give ATI 2017 a try, and if the problems aren't fixed to your liking, you could get a refund.

Regards,

FtrPilot