Yes you're right, rsync would update only a few parts of the file, but
network usage would be even worst.
The only solution would finally be to have rsync on the target system.
Ben
On 14 Mar, 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 --whole-file for a good reason.
On 03/14/2018 10:05 AM, Ben RUBSON via rsync wrote:
On 14 Mar 2018, Lentes, Bernd via rsync wrote:
----- On Mar 14, 2018, at 2:19 PM, Ben RUBSON ben.rub...@gmail.com wrote:
On 14 Mar 2018, Lentes, Bernd via rsync wrote:
I would now expect a rsync from the snap would transfer just some megay
bytes to the file from the day before.
But it doesn't:
ha-idg-1:/cluster/guests/servers_alive # time rsync -av --stats
sa.raw.snap /mnt/idg-2/SysAdmin_AG_Wurst/backup/cluster/test
Hi Bernd,
When doing rsync locally, diff alg is not involved, this is why file is
fully transferred.
Ben
Hi Ben,
also when the target is a cifs share, it's still considered as local ?
Yes as it's mounted locally.
Is there something i can do to get the diff algorithm used ?
Perhaps --no-whole-file would do the trick ?
Copying via ssh to the cifs server is unfortunately not possible.
Bernd
--
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
