NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Rsync backup problem using dyndns hostname
I have two readyNAS drives, one at work and one at home, they have both been working fine but I wanted to put a larger drive in the one at home so I started again with setting up my backups. When...
Hi Stephen,
No the two drives are in different locations.
One Local (in the office)
One remote (at home)
They work prefectly fine when they are on the same LAN and they used to work when they were apart.
One drive is an older ReadyNAS Duo (RND2000) This one is Local
The other drive os the DuoV2 - This one is remote
The way it used to work was the remote drive would only turn on in the evening after the office has closed, "pull" the data for backup then turn off.
If these drives can perform rsync over SSH then it is something I would consider, I was not aware it was that risky doing normal rsync.
Regards,
Gareth
gjenkins87 wrote:
I was not aware it was that risky doing normal rsync.
The older NAS (the duo v1 in particular) might not be fast enough to do rsync over ssh. I think there is an old add-on which would be needed to enable it (though we'd have to search for it). Using ordinary rsync does create a security risk, since the data transfer isn't encrypted.
If you can set up a VPN connection between the two locations, then you'd have an encrypted connection, and you might not need ddns. However, you would need VPN software in the routers.
gjenkins87 wrote:
Hi Stephen,
No the two drives are in different locations.
One Local (in the office)
One remote (at home)
One drive is an older ReadyNAS Duo (RND2000) This one is Local
The other drive os the DuoV2 - This one is remote
The way it used to work was the remote drive would only turn on in the evening after the office has closed, "pull" the data for backup then turn off.
Ok. So the dyndns name is assigned to the local office system. TCP Port 873 needs to be forwarded in the office router to the v1 NAS, and that NAS needs to have a reserved (or static) IP address on the office LAN in order to do that.
Reviewing the earlier posts, I think you did that, but wanted to confirm.
Correct Stephen,
Although earlier today I adjusted the MTU settings on the NAS to match that of the router , which was 1500 but since the switch to fibre and PPPoE the MTU is now 1492 ( I guess due to an extra 8 bits of network overhead?).
Anyways, since this change I have not been able to access the local NAS admin page, the drive is sitll working and I can access all the folders on it, I just don't want to reboot it or factory reset or anything while people are working.
i'm considering making a completely separate backup and starting from scratch with both drives again...
gjenkins87 wrote:
Correct Stephen,
Although earlier today I adjusted the MTU settings on the NAS to match that of the router , which was 1500 but since the switch to fibre and PPPoE the MTU is now 1492 ( I guess due to an extra 8 bits of network overhead?).
Well, 8 bytes. The overhead is the PPPoE part.
Did you make that change on the local (office) NAS or the remote NAS?
I made that change on the local NAS drive, i can still teamview into the remote one via my computer at home.
I can't think why that would have upset it but then it has always been slow and temperamental.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
