NAS to NAS Rsync Backup

Did you enable RSYNC on the boxes AND on the shares?
Then on NAS1 you could create a backup job with source "Backup" (type "share")
and destination type "remote", Host: NAS2 and path "target" (if that is the name of the destination folder)...

Hope this helps,

Ton

Yes, the rsync activated on both shares,
For push backup job, the source is "Share", and for distanation the remote rsync with ip of another NAS and "sauvegarde" for the path.
The log of result:

Backup Job Name: Nas2Nas Backup Job Type: Incremental Protocol: rsync Backup Source: [Sauvegarde]/ Backup Destination: [remote:rsync]/192.168.6.63::sauvegarde:: Backup Start Time: Tue May 27 2014 20:57:07 Backup Finish Time: Tue May 27 2014 20:57:07 Backup Status: Fail: connection cannot be established. Please check the connection and authentication, if required. @ERROR: Unknown module 'sauvegarde::' rsync error: error starting client-server protocol (code 5) at main.c(1534) [sender=3.0.9]

There is no athentication on distanation share.
If distanation path not configured, the error is next:

Backup Job Name: Nas2Nas Backup Job Type: Incremental Protocol: rsync Backup Source: [Sauvegarde]/ Backup Destination: [remote:rsync]/192.168.6.63:: Backup Start Time: Tue May 27 2014 21:05:58 Backup Finish Time: Tue May 27 2014 21:06:00 Backup Status: Fail: connection cannot be established. Please check the connection and authentication, if required. ERROR: The remote path must start with a module name not a / rsync error: error starting client-server protocol (code 5) at main.c(1534) [sender=3.0.9]

When configuring the destination, make sure you press TEST CONNECTION to ensure it is correct... No "/" to start the path...

Sent from my A700 using Tapatalk

The test connection is ok. But only if no path indicated.

Do you have a share on the destination NAS called sauvegarde ( backup)?

vandermerwe wrote:
Do you have a share on the destination NAS called sauvegarde ( backup)?

yes. i have a share with the same name.

Are you using the admin credentials for the remote share?

Did you see if switching to a different protocol works?

What is the IP of the local NAS and what subnet are you using?

I've used ReadyNAS to ReadyNAS rsync backups via Frontview for a couple years, but when I tried to create a new job today I seem to be seeing the same problem. Setting the path barfs the process and will cause the 'Test connection' button to fail.

My old backup jobs seem to be running fine still.

I recently updated to 4.2.26 on my ReadyNAS pros, so I'm guessing one of the recent firmware changes barfed the interface for setting up the jobs.

I'll post if I figure this out but if you already know the answer please post it here. :)

This is a little disturbing...

Something has been messed up. When you set up the backup job in FrontView, the only acceptable syntax for the Path to a share on another ReadyNAS appears to be

::yoursharename\

Now that is clearly NOT what the documentation and the Help button say. If you do this, FrontView claims its okay and reports the destination as

yourreadynasname.local::::yoursharename\

I'm pretty sure that the 4 colons in a row syntax is not right, but when I did a configuration save and looked at the backup jobs file, that is what it saved. I'm not sure how much more I want to experiment with this until a Jedi weighs in.

did anyone ever figure this out?

I have a new 316 I am trying to configure as the backup device for an existing Ultra 6+.

I cannot get rsync to work. I have defined an rsync user account and password on both systems and use it to authenticate.

I am attempting a "pull" backup, that is, the rsync backup job is configured on the destination device (my 316). But the "test connection" fails with the messages given above.

I currently use pre-existing "pull" backup jobs using rsync running on an NV+ to backup shares on the same Ultra 6+. They run fine.

The mysterious ::mysharename\ syntax does not work either.