On 5.7.2011 16.13, Dominic Raferd wrote:
I agree. IMO rdiff-backup should never be run over an internet
connection, only on a stable local network. If you want to get the
rdiff-backup data offsite, create your rdiff-backup repository locally
and then use rsync to mirror it to the offsite location. This is the
technique used for TimeDicer primary/mirror servers.
Thanks for all the input. I am now trying Dominic's solution, modified
(because I have easier hands-on access to the target machine):
First I rsync the data from source to target machine, then I use that to
make a local rdiff-backup archive.
(Good luck that 2TB HDs are already so inexpensive.)
If it works, then we will know that the errors were related to unstable
network connection - as I beliebe they were. Too bad I did not get more
exact information on the causes. I did increase verbosity both in
rdiff-backup and ssh, but all I found out was that the connection seems
to break now and then, quite irregularly.
- Jussi
_______________________________________________
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki
