NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
NAS Mirror
Currently I have 1 ReadyNAS RN2120v2. We had a recent failure on site and lost all 16TB on the NAS. Looks like a 3138 would be close match to the 2120. 3138 is probably a little faster. I wan...
Hi FG
The RN3138 is better than 2100 due to its specification and features.
It would be better to have two identical NAS model for the setup you want to have; this is to speed up your transition to the Backup NAS in the event of failure by restoring the configuration on the other unit and have users able to access it just like the primary NAS.
Regarding backups, backing up each share using rsync on the source or destination NAS would do the job.
If you will have two different units, the best way is to unplug the RN3138 and plug in the Backup NAS and reconfigure. This is not the best resolution for failover unlike with restoring the configuration from the same NAS, but other community members might have better ideas.
Backing up and restoring configuration steps is available here.
Backup using rsync is here.
Regarding the suggestion you may want to check this thread.
Hope this helps!
Regards
Some clarifcation for me.
If you want to mirror nas 1 to nas 2, what is the best way to connect their ethernet cables?
- For each nas do you BOND the network cards together and then plug cables into the switch?
- Can you plug one nas directly into another nas?
- How would you do that? For nas 1, one cable is plugged into the switch and the 2nd is plugged into the nas 2. Then nas 2 has its 2nd cable plugged into the switch as well.
I suggest wiring them both to your switches/routers, and run rsync over the normal network.
You can use bonding if you like, but I don't think you should do that specifically for backup. If your NAS has a lot of simultaneous users, then bonding will increase the throughput.
If bonding increases throughput then why do you not suggest the bond for a backup?
Thanks for the time.
Marc_V
Thank you for the info.
In the link below, step #9, in the remote settings, once I choose the Remote: Rsync Server for the protocol the PORT field is displayed. What port should I use. Step 9 does not show a port field.
I am trying to back up one nas to another.
On the admin page of MainNAS, under System - Settings. Rsync service is NOT enabled. The instructions did not say to do this.
On the admin page of BackupNAS, under System - Settings. Rsync is enabled
Hi FG
Rsync can be disabled on the MainNAS since the procedure is to push the data to BackupNAS.
Port being requested for RSYNC should be Port 873, please take note that you may have to configure port forwarding on your router.
following the article I am sure will get us through the backup configuration. Please let me know once everything has been set.
Happy New year!
Regards
This may be a "dumb" question, but it both MainNas and BackupNas are plugged into same switch, then I wouldn't need to mess with the router, correct?
Port forwarding may be if one NAS was offsite?
FG wrote:
On the admin page of MainNAS, under System - Settings. Rsync service is NOT enabled. The instructions did not say to do this.
No harm in enabling it, and I suggest doing that.
FG wrote:
In the link below, step #9, in the remote settings, once I choose the Remote: Rsync Server for the protocol the PORT field is displayed. What port should I use. Step 9 does not show a port field.
Choosing the port is a new feature, so the KB article is a slightly behind,
You should be able to leave it out. Or you can enter 873 (which is the default RSYNC port).
The backup job will not let you proceed unless you enter a valid port number, I am just saying you can't leave it blank.
What is the pro to using Rsync vs SMB backup? Rsync has the ablitly to removes files from destination that have been deleted from source location without making a FULL backup again, correct?
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
