Re: [rdiff-backup-users] adding --resume back

Hello Marco If you want to do some coding work on rdiff-backup then that would be welcome, but I think you will be on your own. rdiff-backup is not under active development at present, sadly. An alternative is to see if you can prevent the problem of a broken

Re: [rdiff-backup-users] adding --resume back

On 09/04/2014 12:21 PM, Dominic Raferd wrote: If you want to do some coding work on rdiff-backup then that would be welcome, but I think you will be on your own. rdiff-backup is not under active development at present, sadly. Yes, I know that, but any suggestion is useful.

Re: [rdiff-backup-users] adding --resume back

On 04/09/2014 13:01, Marco Mariani wrote: Even if it does, it isn't much use if your communication drops are so frequent that you rarely complete a single backup session, because your last usable backup data might be too old for your purpose. Not only at the level of backup sessions, I must c

Re: [rdiff-backup-users] adding --resume back

Hi all, On Thu, 4 Sep 2014, Dominic Raferd wrote: If I had enough space for the LVM snapshot, I would probably rsync the current data and run rdiff-backup locally on the destination every time rsync succeeds. This would provide - in our setup - the same protection as LVM with respect to broke

Re: [rdiff-backup-users] adding --resume back

On 04/09/2014 15:02, Chris Wilson wrote: Hi all, On Thu, 4 Sep 2014, Dominic Raferd wrote: If I had enough space for the LVM snapshot, I would probably rsync the current data and run rdiff-backup locally on the destination every time rsync succeeds. This would provide - in our setup - the sa