Rsyncing huge file, timeout on rsyncd

Hello, let me describe my setup. Source server is debian wheezy, rsync 3.0.9 Destination is qnap TS-410, with rsyncd enabled, rsync 3.0.7 I'm trying to rsync two files, which are exported from source server as iscsi targets (windows iscsi backups). Files are on btrfs, so I use snapshots during

Re: Rsyncing huge file, timeout on rsyncd

Just to clarify When using rsyncd script, there is also no progress from beginning, it just timeouts Libor Dne Thursday 02 August 2012 12:26:13, Libor Klepáč napsal(a): Hello, let me describe my setup. Source server is debian wheezy, rsync 3.0.9 Destination is qnap TS-410, with rsyncd

RE: Rsyncing huge file, timeout on rsyncd

--timeout=SECONDS set I/O timeout in seconds I think this timeout must be set big enough so that data actually gets transferred during the window. Having the target verify that nothing has changed yet seems to not qualify as resetting the timeout. Figure on enough time so that

Re: Rsyncing huge file, timeout on rsyncd

Ok, i'l try setting timeout, but according to documentation, default is timeout=0 which means no timeout. Maybe setting --contimeout to some large value should help? Libor Dne Thursday 02 August 2012 07:03:51, Tony Abernethy napsal(a): --timeout=SECONDS set I/O timeout in

Re: Rsyncing huge file, timeout on rsyncd

On Thu 02 Aug 2012, Libor Klepáč wrote: Ok, i'l try setting timeout, but according to documentation, default is timeout=0 which means no timeout. IIRC setting the timeout explicitly on both ends (if you're using an rsync daemon) to the same value will cause some sort of heartbeat activity.

Re: Rsyncing huge file, timeout on rsyncd

Hello, tried to set timeout=7200 on both sides also enabled logging in rsyncd Here is output from server 2012/08/02 15:07:23 [2339] connect from ms-backup.xx.local (192.168.5.213) 2012/08/02 15:07:23 [2339] rsync to iSCSI-backup/ from backup-rsync@ms- backup.xx.local (192.168.5.213) 2012/08/02

Cache file list in daemon mode?

Hello. I suspect that what I want to do is not possible with rsync, but this is the best place to double-check. We are pushing files to a remote target that stores them on a very slow network file system. There are also over a million files on the target. Consequently, running rsync to

Re: Cache file list in daemon mode?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 is it possible to talk directly to the NFS server via rsyncd or rsync over ssh? Eliminating the extra hop through a network mount should make a big difference. On 08/02/12 18:30, Peter Scott wrote: Hello. I suspect that what I want to do is not

Re: Cache file list in daemon mode?

We're considering that, but it's Gluster, not NFS, and it's peer-to-peer, not client-server. Options in that direction start getting more complicated than the 'find -mtime... scp' approach pretty fast. On 8/2/2012 3:43 PM, Kevin Korb wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 is it

Re: Cache file list in daemon mode?

So what you're really saying is gluster is quite slow at doing recursive directory listings, so how about just using find on the real backend bricks to find the files that have changed since last run, merge those listings together (to get rid of dupes) and then get rsync to just update those