Where Does rdiff-backup Store Increments?
rdiff-backup mirrors source to destination with reverse increments in rdiff-backup-data beside each mirror, restorable to any point with --restore-as-of.
Last updated
rdiff-backup keeps a live mirror plus history in one destination tree. The mirror reflects the latest source state while rdiff-backup-data beside it holds reverse increments reaching backward in time. Restores pick any recorded date.
That design makes the destination self describing. No separate catalog tracks versions because increments name themselves by time. Copying mirrors preserves history automatically when the data folder travels along.
Where rdiff-backup stores this, by platform
rdiff-backup-data (in destination)
Live mirror plus reverse increments together. Restore any date with restore-as-of. Copy whole tree for backups.
Frequently asked questions
How do I list rdiff-backup versions?
Run rdiff-backup --list-increments on the destination to see available dates, since every session appends one. Old increments prune with --remove-older-than. Each increment stores reverse diffs only.
How do I back up an rdiff-backup repo?
Copy the whole mirror including rdiff-backup-data, since increments reference the current mirror state. Restores need both halves together. Verify with --verify after big copies.
Notice an outdated path? Let us know.