cut-off time for rsync ?
rsync-list-m829 at sizone.org
Wed Jul 1 08:34:29 MDT 2015
What is taking time, scanning inodes on the destination, or recopying the entire
backup because of either source read speed, target write speed or a slow interconnect
Do you keep a full new backup every day, or are you just overwriting the target
On Wed, Jul 01, 2015 at 10:06:57AM +0200, Dirk van Deun said:
>> If your goal is to reduce storage, and scanning inodes doesnt matter,
>> use --link-dest for targets. However, that'll keep a backup for every
>> time that you run it, by link-desting yesterday's copy.
>The goal was not to reduce storage, it was to reduce work. A full
>rsync takes more than the whole night, and the destination server is
>almost unusable for anything else when it is doing its rsyncs. I
>am sorry if this was unclear. I just want to give rsync a hint that
>comparing files and directories that are older than one week on
>the source side is a waste of time and effort, as the rsync is done
>every day, so they can safely be assumed to be in sync already.
>Dirk van Deun
>Ceterum censeo Redmond delendum
Ken Chase - ken at heavycomputing.ca skype:kenchase23 +1 416 897 6284 Toronto Canada
Heavy Computing - Clued bandwidth, colocation and managed linux VPS @151 Front St. W.
More information about the rsync