←back to thread

231 points fanf2 | 5 comments | | HN request time: 0.808s | source
Show context
thekashifmalik ◴[] 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 #
1. dmd ◴[] No.41830809[source]
What do you mean by that? "restic mount" has been part of restic since the very start.
replies(1): >>41830961 #
2. thekashifmalik ◴[] 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 #
3. homebrewer ◴[] No.41831295[source]
If you're doing pull to prevent remotes from destroying old backups (in case of malware takeover, etc), this can be solved by running rest-server with --append-only

https://github.com/restic/rest-server

It 403's any attempt to overwrite or delete old data.

4. luoc ◴[] No.41831714[source]
Browsing without dependencies is a bit tricky due to a) deduplication, b) encryption and c) compression of restic's backups.
5. rakoo ◴[] 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