What happens if rsnapshot / rdiff-backup gets interrupted in the middle of a transfer?

Question

Question says it all:

What happens if rsnapshot or rdiff-backup gets interrupted in the middle of a transfer?

I know that rsnapshot tries to make a complete snapshot of your system in rotating fashion, and rdiff-backup makes a differential backup, which is going to be based on the files previously saved behind it.

So: What happens if it gets interrupted in the middle?

Does this result in an "incomplete snapshot"?

Will other snapshots which are dependent on this one be corrupted? (Surely not, but... ?)

Solution 1

My understanding is that...

rdiff-backup will detect the incomplete increment the next time it runs. It will delete the incomplete increment so that the backup location is the same as if the interrupted backup attempt had never been started.

rsnapshot is a little more complicated because its routine is more stepwise and varies depending on the use of the sync_first and use_lazy_deletes options.

• If you use sync_first and rsnapshot sync gets interrupted, you can simply run rsnapshot sync again to straighten things out. If you accidentally run rsnapshot <backup level> at this point instead, the latest backup point will remain incomplete and will be carried through rotations.
• If you don't use sync_first, you're just stuck with an incomplete backup point that is a hybrid of old and new version of files. Unless you manually reverse-rotate each backup point, the incomplete backup point will be carried through rotations.
• In both cases, running rsnapshot <backup level> will cause the oldest backup point to be lost unless use_lazy_deletes is enabled.

Note that sync_first and use_lazy_deletes come at the cost of using more disk space.

---

A reminder/disclaimer: This should go without saying, but never just blindly trust others' advice on the internet. If you plan to use rdiff-backup or rsnapshot for something mission-critical, read every word of the manual and test, test, test everything yourself!

Solution 2

That just happened to me. my external drive became full half-way through rsnapshot's incremental backup:

rsync: write failed on "<path>": No space left on device (28) 

Now I'd like to share a couple of things I learnt from this. ie to repair and limit considerabily chances for such a case to bite me back ;)

Resume a Rsnapshot's interrupted backup

I know two ways to roll back that safely.

Manually

1. Delete the last directory (e.g. daily.0)
2. Rename consecutive directories (daily.1 -> daily.0, ...); possible script1
3. Run the backup as usual (again).

Automatically

rsnapshot has no pause/stop and resume capabilities (except for the limited "skipped due to rollback plan" 2), so we have to use a wrapper to handle these features.

rsnapshot-once3 by Philipp C. Heckel is a wrapper for rsnapshot in PHP that:

• works without modifying your rsnapshot's conf
• ensure that daily, weekly and monthly tasks are run only once in the respective time period, via cron (nice for laptops)
• rollback of failed backup (checks if the last backup was complete; if not the last directory is deleted and consecutive directories are renamed eg daily1. -> daily.0, ...)

Using it for a year I am a happy user: I edited php.ini's openbase_dir for my backup need and voila, lucky day ^_^ Smoother and safer than my previous raw rsnapshot based solution.

Note: slm linked me here from duplicate question: Rsnapshot destination full - how to safely rerun?

Comments

[William Brendel]

Wouldn't it have been much clearer if you had separated this question in to two separate questions?

[RusGraf]

@andol If he was looking for information on how to recover from an interrupted transfer, I think it would be better as two questions. I interpreted this is more of a request for a comparison of how much trouble you'd be in if you used each utility, though, like it's a variant of "help me decide which to use."

[emf]

Thanks Andol; but no, I think this stands as one question. Basically, "what happens if rsnapshot/rsync gets interrupted in middle of transfer?", and I think the tools span one specific niche, so this does not IMO warrant two separate questions. I posed the question of 'incomplete snapshot' as one potential result for clarification purposes.

[emf]

An appreciable reminder, and good practice to keep up with this kind of "proper methods" culture, we don't want linux to turn into dumb-consumer-land. Thanks for the note.

[emf]

So, understanding correctly: having an incomplete backup "carried through the rotations" for rsnapshot will amount to two things: 1. That snapshot will be incomplete if referred back to at a later point 2. Any higher-level snapshots will still be complete, but will not properly refer back to previous hard-linkable files which were missed in the incomplete snapshot. Is this correct?

[topher217]

Thank you for the ideas on how to restart the backup process, but can you comment on how you freed up enough space to resume without running into the same error?