It seems like backintime uses hard links at the target, not between the source and the snapshots. This means that it would be easy to move the taget directory to a server using for example GIO/gvfs. GIO uses urls for bookmarks, and I believe that the url for a ssh target could be used with a rsync-command with little work. If its ssh-mounts only is ok for us.
Harlinks (same inode-number) in snabshots, another inode for the source- file. aw@biblioteket:~/Backup/backintime$ ls -i 20110224-100001/backup/home/aw/openerp-client_6.0.1-0_all.deb 6424056 20110224-100001/backup/home/aw/openerp-client_6.0.1-0_all.deb aw@biblioteket:~/Backup/backintime$ ls -i 20110213-000002/backup/home/aw/openerp-client_6.0.1-0_all.deb 6424056 20110213-000002/backup/home/aw/openerp-client_6.0.1-0_all.deb aw@biblioteket:~/Backup/backintime$ ls -i /home/aw/openerp-client_6.0.1-0_all.deb 5374595 /home/aw/openerp-client_6.0.1-0_all.deb aw@biblioteket:~/Backup/backintime$ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/453169 Title: (enhancement) backup to samba share, sshfs, ftp etc -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
