On 2019-02-13 10:47 a.m., Delian Krustev via rsync wrote:
>
>
> Free space at the beginning and end of the backup:
> Filesystem 1M-blocks Used Available Use% Mounted on
> /dev/mapper/bkp 102392 76872 20400 80% /mnt/bkp
> /dev/mapper/bkp 102392 78768
On 2019-02-13 5:26 p.m., Delian Krustev via rsync wrote:
>
> The copy is needed for the comparison of the blocks as "--inplace" overwrites
> the destination file. I've tried without "--backup" but then the delta
> transfers too much data - close to the size of the backed-up files.
>
It's
On 2018-03-14 10:29 AM, Kevin Korb via rsync wrote:
> It would still be downloading the whole file only to write out a new
> one. Rsync writes out a whole new file because it assumes it is doing
> so locally. The source of that new file can be a combination of parts
> of the existing file and
On 2018-03-14 09:41 AM, Lentes, Bernd via rsync wrote:
>
> also when the target is a cifs share, it's still considered as local ?
> Is there something i can do to get the diff algorithm used ?
> Copying via ssh to the cifs server is unfortunately not possible.
>
If you really wanted to, you
On 2018-03-14 10:07 AM, Kevin Korb via rsync wrote:
> --no-whole-file would only make it even worse. It would have to read
> the remote file over the network in order to do the diff then it would
> write the whole file over the network anyway (--inplace would help a
> little). Local copies force
