rustic

Save snapshots to a local or supported remote repository and restore files when needed. It uses the restic repository format, while deduplication avoids storing identical data repeatedly.

Because rustic uses the restic repository format, read our restic guide when comparing backup and recovery workflows.

When it is useful

rustic is useful when you want recoverable versions of a folder rather than only a second copy of its current contents. A snapshot lets you return to an earlier state after an accidental edit, while deduplication reduces repeated storage of identical data. Plan the destination around the failure you want to survive: a repository on the same physical disk does not help if that disk fails, even when the backup command completed successfully.

A practical way to get started

Start with a small test folder and an empty repository. Make a backup, change a file, make another backup and restore the earlier version into a separate location. Open the restored files and confirm that you understand which snapshot you selected. Only then add larger folders, exclusions and a schedule. Keep the repository password and access details available through a recovery method that does not depend on the computer you are backing up.

What to consider before choosing

Retention and storage cleanup deserve separate attention from creating snapshots. Decide how many historical versions you need before removing old ones, and review the proposed changes before pruning data. Automated runs also need visible failure reporting; a schedule alone is not evidence of a usable backup. Test restores periodically, including after changing storage providers. rustic fits users willing to manage that workflow, rather than those expecting a fully configured backup service after installation.