NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Backup home folders on ReadyNAS 528X using replicate
Finely i am able to get a real backup solution set up using my old ready nas's, after losing most files when readycloud went down this yea.... i am trying to get home folders (where i put most...
craer wrote:
i dont know if the router where the remote nas will be has a dns on it. (YET)
cause i would rather push if i could chouse.
To be clear, you want DDNS, not ordinary DNS. If the router doesn't support it, you can also install a DDNS client on a PC in that location.
craer wrote:
i am using the moth on INT ips so exp:192.168.1.10 for Nas A and 192.168.1.20 for Nas B
not sure if i nead to open the port 22 when i get it working on Int IP and more it over to
EXT IP ( over the internet)
Of course test the backup job on your local network.
Later on (for push) you will need to replace the IP address for NAS B with the DDNS name. And you will need to forward port 22 on the router for NAS B.
craer wrote:
did you see and thing else i did wrong on any other part of the setup? such as the shair ? its a shair strait off the main root Data/(share name)
Again, getting the backup(s) working on the local lan will flush out any mistakes in the backup job settings. In general, you will need rsync enabled for the destination share(s) on NAS B.
craer wrote:
not sure what realy to do with the "key" A text file will be downloaded with the public key. Generally, this goes in ~/.ssh/authorized_keys of your destination
You just download the key, and then install it using the import key instructions (steps 1-8 on using a remote host).
It's best to do this in both directions (installing each key on the other NAS).
craer wrote:
such as have to nas B pull it from A
or Nas A push it To B
Push backups have small benefit - the source NAS takes a snapshot, and backs up the snapshot. That ensures that nothing on the source changes while the backups are being run. If your backups run on-shift (or if the source NAS is used 24/7), then I'd use push.
However, if the backup NAS runs on a power schedule, then a pull backup is needed - since the remote NAS might still be booting up when the backup starts.
Note that if you do a push, then DDNS needs to be running on the backup NAS router. If you do a pull, then DDNS needs to be running on the source NAS router.
There are some instructions here: https://kb.netgear.com/23945/How-do-I-set-up-Dynamic-DNS-on-my-Nighthawk-router-if-I-already-have-a-Dynamic-DNS-account
You can create an account at noip.com.
thanks some good infor on the push pull.
i dont know if the router where the remote nas will be has a dns on it. (YET)
cause i would rather push if i could chouse.
i did the host user on both and swaped keys as you tell me to do and still nothing,
i am using the moth on INT ips so exp:192.168.1.10 for Nas A and 192.168.1.20 for Nas B
not sure if i nead to open the port 22 when i get it working on Int IP and more it over to
EXT IP ( over the internet)
so my questions atm is when setting up ssh backup i put that host user account as the login and it doesent ask for a password for some reason?? (odd) and dont use admin or root account (Right?) and did you see and thing else i did wrong on any other part of the setup? such as the shair ? its a shair strait off the main root Data/(share name)
and just fyi the import key instructions are not user friendly kinda confusing. be nice if some one can do a utube vid on it Wink Wink
once more guys and gals thanks for everything
craer wrote:
i dont know if the router where the remote nas will be has a dns on it. (YET)
cause i would rather push if i could chouse.
To be clear, you want DDNS, not ordinary DNS. If the router doesn't support it, you can also install a DDNS client on a PC in that location.
craer wrote:
i am using the moth on INT ips so exp:192.168.1.10 for Nas A and 192.168.1.20 for Nas B
not sure if i nead to open the port 22 when i get it working on Int IP and more it over to
EXT IP ( over the internet)
Of course test the backup job on your local network.
Later on (for push) you will need to replace the IP address for NAS B with the DDNS name. And you will need to forward port 22 on the router for NAS B.
craer wrote:
did you see and thing else i did wrong on any other part of the setup? such as the shair ? its a shair strait off the main root Data/(share name)
Again, getting the backup(s) working on the local lan will flush out any mistakes in the backup job settings. In general, you will need rsync enabled for the destination share(s) on NAS B.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
