Local Synology NAS to Remote Synology NAS (Problem)

[VTech]

Hi all,

I'm new here.
I'm a complete noob.
Yes I've read threads that have a similar problem, but I tried a few things and read online and it still doesn't seem to work. I'm only understanding half of what I'm reading, so I started this thread before I do anything stupid.

I have a local NAS DS1817+ that I want to backup using Synology Hyper Backup to a remote NAS DS916+
I first made a back-up with cable, so that I don't have to transfer 4TB.
After that, I made the wireless connection at the same place where my local NAS is.
Everything worked up to this point.

Than I moved the NAS offsite to another location, other network.
I can connect to the destination NAS through quick connect. So network wise it works I would say with my limited knowledge.
But I can not seem to connect my local to the destination NAS through the Hyper Backup.

Well it worked once!
I read somewhere on synology forums that a DDNS should be setup.
I did this, gave it a name. Entered the hostname at the Hyper Backup and was able to login and make (re-establish) connection.
And afterwards was also able to back-up to the destination NAS from the local NAS.

But after one day it failed to automatically back-up, it couldn't connect.
And I couldn't manually connect as well.

So my question is: what should I do?
And could you explain it to me like I'm a 10 year old?

 

[fredbert]

Welcome to the forum.

So my question is: what should I do?

Isn't it now working?


I don't think Hyper Backup works with Quick Connect, so the local NAS would have to access the destination NAS using an IP address assigned to the remote site.

I'm assuming it's a simple ISP connection with one dynamically assigned WAN IP address:

• Instead of an IP address you could set up DDNS at the remote site, then set the local Hyper Backup task to use the DDNS domain name as the destination.
• You would need to configure port forward rules on the destination site's router. Rules for the Hyper Backup ports you are using (see the link).
• Across the Internet you should be using encrypted connections, which is part of the task setup.
• If you can set up VPN access between the sites then that could be another way to encrypt the traffic.

What network ports are used by DSM services? - Synology Knowledge Center

Synology Knowledge Center offers comprehensive support, providing answers to frequently asked questions, troubleshooting steps, software tutorials, and all the technical documentation you may need.

kb.synology.com

And could you explain it to me like I'm a 10 year old?

It's a school night and getting late. You can see one episode of Dr Who but then it's bed for you!

 

[VTech]

Welcome to the forum.


Isn't it now working?


I don't think Hyper Backup works with Quick Connect, so the local NAS would have to access the destination NAS using an IP address assigned to the remote site.

I'm assuming it's a simple ISP connection with one dynamically assigned WAN IP address:

• Instead of an IP address you could set up DDNS at the remote site, then set the local Hyper Backup task to use the DDNS domain name as the destination.
• You would need to configure port forward rules on the destination site's router. Rules for the Hyper Backup ports you are using (see the link).
• Across the Internet you should be using encrypted connections, which is part of the task setup.
• If you can set up VPN access between the sites then that could be another way to encrypt the traffic.

What network ports are used by DSM services? - Synology Knowledge Center

Synology Knowledge Center offers comprehensive support, providing answers to frequently asked questions, troubleshooting steps, software tutorials, and all the technical documentation you may need.

kb.synology.com

It's a school night and getting late. You can see one episode of Dr Who but then it's bed for you!

Thank you for the quick reply and the welcome

I edited my post, I forgot to add it only worked for one day.
So if I understand correctly, I don't have to do anything on the destination NAS, but on the destination router where the NAS is connected to?

 

[VTech]

I was a bit busy during a few days.
I would like to solve the problem.
Can anyone confirm I understood correctly that I have to do something on the destination router instead of on the destination NAS?

Thanks!

 

[Deleted member 5784]

The Synology guide to setting this up is here. You'll likely have done some of the steps; its far easier for you to know what you have/havent done than for us to try and guess. So, follow the guide systematically at your end.

When you get to the step that says "enter the IP address and account information of the remote NAS device or the file server", this is what @fredbert was referring to in his DDNS point above. If you have given your remote router a DDNS name, you can use this name instead of the WAN IP address of the remote router. This name/IP address is how your local NAS knows where to go to connect to the remote NAS.

When you get to the Notes section, item 1 says "If your source server and destination server are located on different networks, please make sure the ports and firewall settings are correctly configured". This applies to your situation. It's what @fredbert's 2nd point above is about. What it means is that you need to configure the router at the remote end of the connection to allow incoming connections on the specified ports through its firewall; and further you need to configure port-forwarding on those ports on the remote router so that the incoming connections are routed to your remote NAS behind its router.

The ports & protocols (TCP) are all specified in the link in @fredbert's post above. You should look online for instructions on how to open ports & config port-forwarding on your particular router.

hth