Rsync hardware configuration and recommended vendors

Make sure it’s Rsync compatible

When selecting hardware to use as an Rsync server, make sure it’s able to support the Rsync protocol.
This means that a Windows system needs to be able to run cwRsync.

A NAS device must have Rsync specified as one of the protocols listed. If in doubt, ask the hardware vendor for confirmation. 

Processing Speed is Important!

Rsync can be a very processing intensive protocol with the use of checksums needed to calculate what needs to be transferred.

A lot of NAS devices come with lower range CPUs inbuilt – this will affect the overall time taken to complete the Rsync backup.

Plenty of Disk Space Available

While you may feel that you have enough disk space available when you first implement your Rsync backup, a very common cause of Rsync issues is that the storage space being exhausted causes a lot of issues.
Some inbuilt schemes are designed for great amounts of retention – meaning that the space used could be more than you expect!

Make sure you set the correct backup path

Some NAS devices contain a boot partition (similar to Windows Server 2008 R2).
Sometimes if you input the incorrect path, your Rsync backup will write to this boot partition – which could in turn cause major issues with your backup and hardware.

Seeding a backup

If you’re planning on using a NAS device, you can run your seed backup by connecting this to the local network and running the backup. This avoids having to seed to a USB drive, then run the seed to the NAS in a two-step process (saving you a lot of time).

Double Check Permissions

Even though you’re logged in as a Domain Admin, most NAS devices require users to be set up locally within the unit and have permissions configured locally as well.
If you receive permission issues, this is usually the main reason as to why.

www.qnap.com

www.drobo.com

www.netgear.com

www.synology.com