Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[dns-320.user]

Finally have my identical DNS-320's up and running.  They successfully connect over the internet during setup, and I can choose my remote source folder. Here's a summary:

NAS A- 500GB
  Static IP location
  Ports 22, 873, 62057 forwarded
  Running Backup Server

NAS B- 500GB
  Dynamic IP
  Ports 22, 873, 62057 forwarded
  Two Backup jobs scheduled on this NAS

I hit start backup now, and the status changes from "Ready" to "Backup Now:0%" and stays there for many hours until it fails. (both my B to A, and A to B jobs)  I notice intermittent LAN light activity. I would expect a lot more activity if my data was moving. Does anyone have a similar setup? Is there something I could have missed during setup?

[hoppo1]

What sort of backup are you running? I use NAS to Linux / Local to remote for mine (Not to another 320 and not over the internet but should work the same)

Remote Backups uses RSYNC so you will also need port 873 forwarded. Search through this forum for RSYNC as there are a couple of posts about getting this working over the WWW and what you need to do.

[ivan]

We do that for our overnight backups.  The only apparent difference between your setup and ours is that all our NAS are on fixed IP.

[dns-320.user]

It's a NAS to NAS backup... ivan, can you post the details of your working configuration please? That's exactally what I'm trying to do! 

[ivan]

Have a look at my comment on http://forums.dlink.com/index.php?topic=50225.0 it should work the same way with two units that are the same.  As far as I remember that was how we set them up a long time ago.

[dns-320.user]

read through that post. My NASes should be backing up across the internet  ... I'm using the Remote Backups app

[ivan]

If they don't, and you are backing up over the internet and not the local net, did you forward the necessary ports on your router.

If you are just going nas to nas over your local network did you set that under the service type as well as the correct direction - local to remote - with the local nas being the one you are backing up or -remote to local - if you want to backup to the nas you are setting up?

In the remote settings did you give the correct IP.  This is where problems can occur if the IP is supplied by DHCP and the lease time is short.  Also did you give the correct password for the remote nas?

Most of the other settings should be simple and self explanatory, just watch that you don't set an impossible time on scheduled backups or you will have to wait a lot of hours for anything to happen.   We were caught out by that once when setting up our second off site backup, no one noticed the time was set incorrectly and it wasn't until 23 hours later that the backup started - it hasn't missed a day since then though.

[dns-320.user]

Yup! I checked all those settings again. All my jobs are scheduled on the nas with dhcp service, with the target being the fixed IP location. I've forwarded the three ports (22, 873, 62057) on both ends, but after checking firewall logs, some traffic was going out on ports around 564xx  My nases "see" each other, in that it passes the connection test and I can select my destination folder on my target. My backup however doesn't go past 0%... backups on the local net work just fine...

[telemaxx]

I had to forward Port:
55536-55663 and 21.

You can see this range in the dns320 web ui:
Manage-> Application MAnagement -> FTPserver

[dns-320.user]

I had to forward Port:
55536-55663 and 21.

... on both the source and target Nases?

are you using the encryption option? I'm trying a backup w/o encryption, and it reached 4%... it hasn't moved for a while...

[dns-320.user]

I used the DMZ feature on my routers to forward all ports to my NAS on both ends. The backup still failed... To the best of my understanding, DMZ forwards all ports to the IP you choose. Ironically, when I use the remote backup feature on the local net, it works...