I am experiencing this bug as well. Hard links are simply not possible in sshfs mounts. Perhaps this will be resolved in the SFTP protocol. In the meantime, there seems to be no way to use BiT to backup over SSH.
-- Hardlink issues in mounted ssh filesystems https://bugs.launchpad.net/bugs/430646 You received this bug notification because you are a member of Back In Time Team, which is subscribed to Back In Time. Status in Back In Time: New Bug description: I want to use this great tool (BiT) to backup my laptop (dir /home/user) to a remote server (NAS with HD 320 Gb ext2). I'm using sshfs to mount the backup-dir (NAS) in my local path /mnt/backup-server and I'm trying to make diary snapshots. But BiT is doing full-backups always, because it seems that hardlink creation is not supported in ssh (¿and smb?) mounted filesystems (syslog: WARNING: Command "cp -al OLD-BACKUP NEW SNAPSHOT return 256). That's the reason BiT is transferring all files every time. I think It's not a problem related to permissions, etc. In fact, I don't know how to resolve this problem. Due to this issue, BiT can't be my backup tool. Before trying BiT, I did backups with my own rsync-snapshots script without problems using ssh transport and "--link-dest" option. Also, I use GRSYNC to do full-backups using ssh transport. In any case, I haven't to mount smb or ssh filesystems locally. I think that it would be a great BiT feature to support backups to remote servers using ssh capabilities of rsync (and its "--link-dest" option). _______________________________________________ Mailing list: https://launchpad.net/~bit-team Post to : bit-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~bit-team More help : https://help.launchpad.net/ListHelp
