In my search for a reliable backup program i have come across rdiff-backup which seems like a good solution for me. To test it a little bit i did the following:
- Create a directory a
- Add three files to it (1.jpg, 2.jpg, 3.jpg)
- Create a directory b
- Create a backup by running rdiff-backup a b
- Delete 3.jpg from directory b (let's assume accidental deletion, file corruption etc.)
- Run backup again using rdiff-backup a b
Ok so here i would expect rdiff-backup to detect that a file is missing, warn, backup it again. But it doesn't.
So let's see if we can make sure the backup is alright:
- Run rdiff-backup --verify b
This just hangs without giving any useful information even with -v 9
So my question is: Can you reproduce this ? If so, how the hell can this happen with a widely used backup tool ? This is the most basic thing i expect that the backup will detect that it no longer has a copy of a source file.
I really hope i'm simply overlooking something here...