|Subject:||Re: [rdiff-backup-users] adding --resume back|
|Date:||Thu, 04 Sep 2014 14:01:54 +0200|
|User-agent:||Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.0|
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,
Yes, I know that, but any suggestion is useful.
<http://www.timedicer.co.uk/programs/help/rdiff-backup-regress.sh.php>.) So in
Not only at the level of backup sessions, I must consider the case of single
files that are so big they won't go though in a single session. The network
may be mobile or in a hostile environment. It may be up only part of the day.
Servers may be restarted or have power failures once per day.
_*Backup to a snapshot*_[...]
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 broken increments, but also resume a partial session after network shortage
and server restarts.
Thanks a lot for your reply, I think that my only option is to change the code.
|[Prev in Thread]||Current Thread||[Next in Thread]|