Error while backing up w/ RSync on 4.2.12

After doing some searching (Google/etc) on rsync, I've come to one simple conclusion,
buoyed up by 30+ years experience in the IT field where I've worked with/on various
flavors of Unix professionally as well as every Windows version since 3.1 and DOS
before that.

rsync is simply NOT a flawless or mature protocol in it's linux implementation.

It is NOT ready for prime-time - aka use in a PRODUCTION environment.

It fails - for many people - without any definable cause or permanent solution/fix.

(Well, no one has defined the cause of these current failures to MY satisfaction!)

It IS a perfect example of a "horse made by committee" and Netgear needs to get IN GEAR
to provide its BUSINESS users with a protocol that "just WORKS" for synchronizing one NAS
unit with another NAS unit - both of their manufacture.

I can consistently make rsync fail, yet a CIFS backup (sorry, mdgm - it just WORKS!) works
and completes - even if dreadfully slow.

For those that doubt rsync's "cruftiness" - please just google:

error in rsync protocol data stream (code 12) at io.c(760) [receiver=3.0.7]

or

error in rsync protocol data stream (code 12) at io.c(601) [generator=3.0.7]

You will find currently 300+ hits on the first, and 600+ on the second.

We don't ALL have "network errors"

I know I don't.

Neither NAS logs any errors, nor does my HP Procurve 2824 switch.

The cables connecting the NAS units to the Procurve are 5ft Cat6 cables that
have each individually been CERTIFIED by ME using a FLUKE analyzer to well
beyond 350MHz.

(Yes, I have the toys that most don't have to find network errors - it was cheaper
to buy all the tools/toys than to bring in a commercial electrician to wire up all
the networking (over 50 runs of cat6E) in my new house - Analyzers, Sniffers, TDR's)

So how about it, Netgear?

Can we have a RELIABLE NAS-to-NAS backup?

Or do I keep using CIFS - as I did for 4 years on my Infrant RN600's?