|Subject:||Re: [rdiff-backup-users] [a2] Please help getting my backups running.|
|Date:||Wed, 31 Oct 2012 06:52:06 +0000|
|User-agent:||Mozilla/5.0 (X11; Linux i686; rv:16.0) Gecko/20121028 Thunderbird/16.0.2|
From what I can tell this doesn't seem to be a problem with rdiff-backup but some sort of issue with ssh? Anyway...
ssh-copy-id -i /home/clientrdiff/.ssh/id_rsa.pub address@hidden as both root and clientrdiff returns
I am not familiar with ssh-copy-id but checking on man page it looks as if it does not support the -p option and I guess you are using a non-standard ssh port? So don't use ssh-copy-id, just add the public key manually; you only have to do it once for each remote user (root and clientrdiff). Do you know how to do this?
/etc/fstab address@hidden:/home/serverrdiff/ToBeBackedUp /home/clientrdiff/mnt/server.com:/home/clientrdiff/ToBeBackedUp fuse user,noauto,ro 0 0Your second problem seems to be with sshfs, your syntax looks strange to me. To mount the remote directory 'ToBeBackedUp' at say /home/clientrdiff/remotebackup I think it should be like this:
$ mkdir -p /home/clientrdiff/mnt/remotebackup
$ sshfs address@hidden:/home/serverrdiff/ToBeBackedUp /home/clientrdiff/mnt/remotebackup -o workaround=rename
But why are you using sshfs at all? You don't need this for rdiff-backup, unless rdiff-backup cannot be installed on either client and server. Using sshfs will make backups slower and use more bandwidth.
Here is an example of rdiff-backup doing a push backup (i.e. run on client) using a non-standard ssh port 9222:
$ rdiff-backup --remote-schema "ssh -C -p9222 %s rdiff-backup --server" /home/clientrdiff/ToBeBackedUp address@hidden::/home/serverrdiff/ToBeBackedUp
BTW both your machines are using a very old version of rdiff-backup (1.0.5), you should use 1.2.8 (the last stable version) or 1.3.3 (the last unstable, but seems to work fine).
On 30/10/12 19:21, Gary Rickert wrote:
I have spent the last week googling to figure this out but have failed.
|[Prev in Thread]||Current Thread||[Next in Thread]|