←back to thread

Restic: Backups done right

(restic.net)
231 points fanf2 | 1 comments | 13 Oct 24 17:42 UTC | HN request time: 0.2s | source
Show context
thekashifmalik ◴[13 Oct 24 19:22 UTC] No.41830760[source]▶
Big fan of restic! The only feature I found missing was the ability to browse historical snapshots like regular files.

I wrote and now use the rsync-based, browsable, incremental backup CLI: https://rincr.com/

replies(4): >>41830805 #>>41830809 #>>41830810 #>>41832927 #
dmd ◴[13 Oct 24 19:28 UTC] No.41830809[source]▶
What do you mean by that? "restic mount" has been part of restic since the very start.
replies(1): >>41830961 #
thekashifmalik ◴[13 Oct 24 19:48 UTC] No.41830961[source]▶
That command works well and accomplishes some of what rincr what built to solve. For example, when I mention browse-ability, I mean on the backup host without any dependencies so I can use standard file tools and browsers.

I also needed both "pull" (backup remote files) and "push" (backup local files) backup features and if I'm not mistaken restic still only supports the "push" model.

EDIT: Added more details

replies(3): >>41831295 #>>41831714 #>>41832158 #
1. rakoo ◴[13 Oct 24 22:12 UTC] No.41832158[source]▶
> I mean on the backup host without any dependencies so I can use standard file tools and browsers.

This means the backups are not encrypted though, and is something you really have to think twice before requiring

> "pull" (backup remote files)

You can mount the server to backup on the backup host, or you can ssh from the backup host to the server to backup, call `tar cf - /folder`, and ingest that from stdin on the backup host. Both will retransmit the totality of the files to backup