RSync uses something call a 'module name' it's kind of like a 'share name' (for windows).
The Synology's default 'module name' for RSync is NetBackup (I assume it's case sensitive). So if you change your command it should work:
From:
c:\cygwin\bin\rsync -avz /cygdrive/e/Lisa/ Lisa@192.168.1.10:/volume1/homes/Lisa/Backup
To:
c:\cygwin\bin\rsync -avz /cygdrive/e/Lisa/ rsync://Lisa@192.168.1.10:873/NetBackup/volume1/homes/Lisa/Backup
(Pardon the Line Wrap, that should be all be one line, with no carriage return / Line Break)
The last part may work without explicitly specifying the protocol (rsync://), and port (:873), just make sure the 'module name' 'NetBackup/' precedes the path.
Additionally make sure that the 'user account' that you picked has full read / write permission on the 'NetBackup' share in the Synology via this link:
http://www.synology.com/tutorials/how_to_backup_Linux_computer.php?lang=us
I saw something in the documentation stating to use either the 'admin' account, or the 'rsync' account. (I always use the 'admin' account). I don't know that other users will work (on older DSM 3.0 or less firmware, as there is nowhere to add user permissions for this). On the newer DSM 4.0+ firmware you have to specifically enable that user for 'Network Backup Privilege' via the above link. Another note about setting up RSync on the older DSM 3.0- firmware (Not for your problem, but it may help others).Is that the Procedure is:
Click the Downward arrow (in the upper left) > Click 'Backup and Restore' > Check the 'Enable network backup service' box. Then use only 'admin', or 'rsync' as users for rsync.
This has some easy to read info on RSync / module name (Not specific to Synology):
http://www.backupassist.com/education/articles/configuring-backupassist-for-rsync-without-ssh.html
You can actually create other 'module names' for the Synology by modifying the rsync config file on the Synology via ssh (not 100% sure about it's name, I assume it is rsyncd.conf)
The Resource temporarily unavailable error typically means you’ve hit a system or process resource limit such as available memory, the number of allowed user processes, the number of files a user can have open at any one time. You can get this error when starting a new process, opening a new file or when a currently running process asks the kernel for more memory.
Some of these limits are user limits which can be set using the ulimit command. Running the ulimit -a command will show what user limits are currently set to, e.g.,
$ ulimit -a
core file size (blocks, -c) unlimited
data seg size (kbytes, -d) unlimited
file size (blocks, -f) unlimited
open files (-n) 256
pipe size (512 bytes, -p) 8
stack size (kbytes, -s) 2036
cpu time (seconds, -t) unlimited
max user processes (-u) 256
virtual memory (kbytes, -v) unlimited
From the error message it sounds like that your problem might be due to running out of file descriptors. It might be worth checking what file descriptors are open by running
ls -l /proc/<PID>/fd
Cygwin specific
Similar problems can also be caused by one of the Big List Of Dodgy Apps (a list of applications that interfere with the normal working of Cygwin by intrusively injecting themselves in the system call chain).
I’ve never used Exim so I don’t know if it forks many child processes while
it’s operating but Fork failures may also be an issue; they are documented in the Cygwin FAQ: How do I fix fork() failures?. Sometimes installed libraries are not updated properly and they have to be updated using the Cygwin setup.exe, or by running rebaseall. See
Finally, I used to receive a lot of Resource temporarily unavailable messages when I was running 32-bit Cygwin. After upgrading to 64-bit, these mostly went away.
Best Answer
The
-aflag torsyncincludes a number of options that don't make sense on Windows; the error you're seeing indicates thatrsyncis trying and failing to preserve file ownership. Try using-rtvxinstead of-avx.