https://logs.paulooi.com/secure-copy-with-failover-rsync-ssh.php Systems Admin, Web Development and etc Tue, 25 Jan 2011 09:00:07 +0000 hourly 1 https://logs.paulooi.com/secure-copy-with-failover-rsync-ssh.php/comment-page-1#comment-65067 Mon, 31 Mar 2008 07:22:18 +0000 http://systems.takizo.com/2008/03/28/secure-copy-with-failover-rsync-ssh/#comment-65067 hey dude, thanks for the tips. much enlightenment!

]]> https://logs.paulooi.com/secure-copy-with-failover-rsync-ssh.php/comment-page-1#comment-65032 Fri, 28 Mar 2008 16:53:31 +0000 http://systems.takizo.com/2008/03/28/secure-copy-with-failover-rsync-ssh/#comment-65032 Should be a double dash (—-inplace and —-progress). I also use -z to compress the files for network transfers.

]]> https://logs.paulooi.com/secure-copy-with-failover-rsync-ssh.php/comment-page-1#comment-65031 Fri, 28 Mar 2008 16:45:36 +0000 http://systems.takizo.com/2008/03/28/secure-copy-with-failover-rsync-ssh/#comment-65031 No quite. When rsync copies the file, it will create a temporary file in the destination. The file name begins with a ‘.’. For example, paulishandsome.iso will be .paulishansome.iso.78qwda. The file will be renamed to paulishansome.iso AFTER it finished transfering. If the file is large, and the connection break, the dot file will be removed, and you have to start all over again. You need to use –inplace so that rsync will not create the temporary file; instead it will write the file immediately to disk and you can safely resume after a broken connection.

]]>