I'm about to buy a RN516 with 6 Seagate 4TB 3.5" SATA3 64MB Cache OEM Hard Drive (ST4000VN000) that I will install myself. I currently keep all my media data on a ReadyNAS Pro 6350.I intend to use the RN516 as my new media server with the ReadyNAS Pro as my backup (until I run out of space).A few questions before I start the project:1) Any tips on the best way to setup the diskless RN516 with the 6 new 4TB drives? Should I start expanding with 1 drive or several installed at once?2) Once the 516 is setup, I have 8TB of data to move to the RN516. Is there a faster way than setting up a RSync backup from the PRO to the RN516 through the network?Thanks for your help!

You can install them at once, you will have only a single rebuild, if you add them it will rebuild once per disk added I think (rebuild is very long ;) really, I have a RN104 with 4*4To (same model as yours, works like a charm) it took 38hours to rebuild, the 516 should be quicker but still expect 10 hours for you 6 disks at least). USB3 is faster than ethernet, e-sata is too so if you have USB disk that can keep up... otherwise rsync or FTP I believe the speed is nearly the same, even AFP/SMB shouldn't be that slow IMO. If you don't have gigabit network you may want to get a PC with a gigabit switch (or two gig NIC on the PC). Maybe jumbo frames can help. That said I believe that no matter what you are doing the Duo will struggle and limit the speed anyway so...

Rsync or nfs (over the network) will be quicker than usb because with usb you need to transfer twice.Certainly if you have a gigabit network that it is the case. Using NFS and then editing the backup to use rsync and rerunning it is a good strategy

Yes, the network is a gigabit. I only considered using RSync. I'm interested in learning more about NFS as you seem to be suggesting it would be quicker for the initial backup.Where I can learn more about NFS and how it applies to the ReadyNAS?Thanks

Nfs is a file sharing protocol like CIF/SMB or AFP. Since it is native to linux generally is the fastest protocol between two linux machines. You can easily select it in the backup menu.Rsync is good at incremental backup and full preservation of owners and permissions. If you edit the backup job after the first time you run it to use rsync, then subsequent backups will use that. The remote share needs to have both enabled.Note that if you create a new backup job, it will do a full backup the first time it runs even if the files are already in the destination share. You need to use the editing trick to avoid that.

Excellent! Great tip.Once the PRO is running reliably as an Rsync backup NAS to the RN516, is it possible to backup to the PRO from a remote location (my office)? I'm worried about chewing up too much bandwidth once I make a connection.Thanks

ReadyNAS Pro to RN516 Upgrade | NETGEAR Communities

54 Replies

Replies have been turned off for this discussion

herbg
Tutor
Nov 29, 2014
I'm happy to report that, after escalation at Netgear, this problem was resolved. It appears that the problem was caused by the Backup settings.

So here are the correct settings:

For a share called 'MUSIC'
- Created a job called 'MUSIC'

- Here are the settings for the job:
- General - Name: 'MUSIC'
- Source - Type: share
- Source - Name: share: MUSIC
- Source - Host: (null)
- Source - Path: /
- Source - Login: (null)
- Source - Password: (null)

- Destination - Type: remote
- Destination - Name: remote: Rsync Server
- Destination - Host: (ReadyNAS PRO)
- Destination - Path: MUSIC
- Destination - Login: (null)
- Destination - Password: (null)

- I've left the options under the Advanced, Schedule and Options tabs at defaults.

The critical aspect are the Source:PATH settings: adding the "/" prevents the embedding of a 2nd "MUSIC" folder back into the Destination Share

I'm glad this is resolved. Unfortunately, I wasted much time and effort with the 1st level of Netgear tech support who did not know how to fix this and, at one point, suggested shipping a new unit to solve the problem.
Thanks to StephenB and mdgm for extra-ordinary assistance!
vandermerwe
Master
Nov 29, 2014
Interesting.
Are you needing to do this with 6.2.0 as well?
herbg
Tutor
Nov 29, 2014
Yes ... this was only tested with 6.20.
siigna
NETGEAR Employee Retired
Dec 01, 2014
herbg wrote:
I'm happy to report that, after escalation at Netgear, this problem was resolved. It appears that the problem was caused by the Backup settings.

Glad to hear everything's working! Let me know if you see any other oddities.

vandermerwe wrote:
Interesting.
Are you needing to do this with 6.2.0 as well?

Off the top of my head I believe this was an issue for 6.1.9 and below, so you'll need to upgrade to 6.2.0 to take advantage.
Looking through the internal bug list seems to confirm that some changes were made in 6.2.0 to ensure that users can utilize both relative and absolute paths on rsync.

Forum Discussion

ReadyNAS Pro to RN516 Upgrade

54 Replies

Related Content

RN516 bios & memory

RN516 finally EOL?

ReadyNAS RN516 stuck on boot after FW upgrade

ReadyNAS support for RN516?

Failed 6.9.3 upgrade RN516

NETGEAR Academy

ProSupport for Business