Hello again, still didn't find solution for timeout. What exactly is happening during initial "no progress" period? I guess, destination rsync is computing checksum of whole destination file before transfer starts from source?
Is there any way to force rsync to start copying data (almost) immediately - let's say, after computing checksum of 10% of file? With regards Libor On Thursday 02 August 2012 12:26:13 Libor Klepáč wrote: > > When i try to rsync over ssh, it takes ages to show progress status (around > 1 hour for smaller file, 4-5 hours for big file). > Whats going out there? > Source server is idle during this "no progress" period, destination Qnap has > one rsync process eating cpu. > > My commands are (example with one file) > for rsyncd > rsync --inplace --progress --numeric-ids --times --password-file .passwd > iscsi/iscsiDisk1 rsync://backup-rsync@192.168.5.250:/iSCSI-backup/iscsiDisk1 > > for ssh > rsync --inplace --progress --numeric-ids --times iscsi/iscsiDisk1 > admin@192.168.5.250:/share/MD0_DATA/iSCSI-backup/iscsiDisk1
signature.asc
Description: This is a digitally signed message part.
-- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
