I'm trying to wrap my head around
rsync behaviour when using
--link-dest as my personal backup.
My setup is a Mac Pro with a separate data partition which I want to backup to an ubuntu server. Trying this with Time machine did not work out so far (last issue: wrong max target size of 46 GB).
I got the whole thing working with
rsync over ssh and that's fine for me.
Last thing I tried was to make incremental backups using the
I got it working via ssh (201_10_08 is a full backup)
rsync -avh --delete --link-dest=/mnt/backup_data/2014_10_08 /Volumes/Data/ user@host:/mnt/backup_data/2014_10_09
This works just fine with the
--link-dest path pointing to the folder on the target system.
Now I tried to simplify this by defining
backup_data as a Samba drive and mounting it from the Mac (updated rsync to 3.0.9 on the mac due to slow performance over samba of old version).
Result: Despite the same modification date, owner and group of the files on the mounted drive (as verified by
stat), subsequent backups generate full backups and no hard links on the target system
--link-dest=/mnt/backup_data/old (result: path could not be found, which makes sense since access is only to smb share not the whole target system) as well as
--link-dest=/Volume/mount/old (with path via smb mount on mac, result: no hard links, full backup).
I can work with the solution I worked out, but I would like to understand the behaviour.