restic VS Snebu

Restic - GitHub

I religiously use Google contacts. It's the simplest way to keep people contacts up to date on Android.

I archive all important documents in specific folders by subject and date. This is backed up to back blaze with restic. https://restic.net/

I use https://ente.io for pictures. I convinced my wife to use it, and she agreed to auto share her photos so I don't nag her for copies. It had simple import from Facebook and Google.

I also keep extensive journals, which really helps to tie it all together. I can basically grep for hangouts, conversations, etc.

I also separate work journal from personal, and have essentially a journal for each project. https://jodavaho.io/tags/bullet-journal.html for how.

I religiously use Google calendar for all plans, you can easily search it for past events to get dates.

I also use monicahq for some notes about things I should remember about people but the habit never stuck.

After Borg, I switched to Restic:

https://restic.net/

AFAIK, the only difference is that Restic doesn't require Restic installed on the remote server, so you can efficiently backup to things like S3 or FTP. Other than that, both are fantastic.

I'm curious, too. I know they've had some issues in the past:

https://github.com/restic/restic/issues/3268#issuecomment-78...

On the other hand, I tested around 15,000 backups last year (multiple hourly backups, daily tests) and they all passed.

I use and recommend restic. I use it for about 60 machines on my LAN, and it's absolutely fantastic.

As such, I use tar for the serialization of backup data for Snebu (https://www.snebu.com), which has a plugin (tarcrypt) that operates on the data streams. Snebu ingests tar format, and emits tar format, so all you need to backup/restore a host is ssh access (server can pull backups, or client can push backups). So tarcrypt was added as way to do client-side encryption, but still be able to to submit recognizable tar files to Snebu's backend (which indexes, de-duplicates, and snapshots backups).

Snebu, on github. Simple Network Encrypting Backup Utility.

Details are at https://www.snebu.com/tarcrypt.html if you want to look it over (and tarcypt is part of the Snebu project https://github.com/derekp7/snebu). I'd love to get another pair of eyes on this to point out any non-obvious security limitations.

Since I've had a handful of users ask about cloud storage for Snebu, Would you be interested in adding Snebu as a supported protocol? It should be similar to how you currently support Borg. For Snebu, the client runs find and tar, sending results via ssh to the snebu binary on the remote host. And more recently client-side public key encryption support has been added via a client-side filter called "tarcrypt". Ideally, a customer would use Snebu to back up to a local device on their network (for example a Raspberry Pi with a large USB drive attached), and then use Snebu's efficient replication to send deltas to the cloud-hosted server. Client files are stored individually (deduplicated) on the Snebu server, and metadata is in an SQLite DB (advantages over Borg is more open standards for the data storage and public-key encryption, disadvantage is file-level instead of block-level deduplication and a project that isn't as widely used).

If you are interested, I would be more then happy to have an extended discussion with you going over implementation options, and updating the client side script to make it work better with your service. (https://www.snebu.com, https://github.com/derekp7/snebu, and the tarcrypt extensions to tar are described at https://www.snebu.com/tarcrypt.html).

Would a mention of my open source backup system, Snebu (or https://github.com/derekp7/snebu) fit in this thread? Elevator pitch -- GPLv3 C code, snapshot-based, compresses, encrypts, deduplicates, can back up clients without installing an agent (just need ssh, bash, tar, and find commands on client for "pull" backups), push backups can have restricted permissions (i.e., give a client permission to push backups only, but not delete backups, or give a user restore-only permissions). Uses tar to collect the data, stores metadata in an SQLite DB on the server, files are stored in LZO format (can be read directly with lzop) (unless client-side encryption is used, but the data can still be decrypted with openssl then decompressed with lzop). Encryption is public-key based instead of needing to keep a shared symmetric key or passphrase laying around on your backup server.

I created and use Snebu -- I'm working on getting it submitted to Fedora (waiting on package review now), doing daily snapshots of my fleet to a raspberry pi with external 12 TB WD Easystore drive. Provides push or pull based backups, granular access permissions, client-side public key encryption (RSA + AES-256) with HMAC validation, server-based data catalog housed in SQLite, multiple client support, global (cross client) file-level deduplication and compression. Works great for backing up a large range of OS versions since the client-side doesn't need an agent -- just bash, tar, find, and ssh.

snebu (c) - https://github.com/derekp7/snebu