ROroryokane·Mar 31, 2013
In Today is World Backup Dayderekp7
snebu
C2013–2021
derekp7 / snebu
snebu
Simple Network Encrypting Backup Utility
3Distinct people
16Mentions
0Explicit recommenders
111GitHub stars
What to know before exploring
What it is
Simple Network Encrypting Backup Utility
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
- andrewchambers/bupstash · linked in 3 of the same discussions
- borgbackup/borg · linked in 3 of the same discussions
- dpc/rdedup · linked in 3 of the same discussions
Mentioned in the same Hacker News threads. That is not proof they are substitutes.
This week on Hacker News
Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 4:00:59 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year16 dated mentions
Observed mentions: 2013-02-05 03:08:46 UTC to 2021-11-13 14:35:38 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2013 | 2013-01-01 00:00:00 UTC | 2014-01-01 00:00:00 UTC | 4 | 0 | 4 |
| 2014 | 2014-01-01 00:00:00 UTC | 2015-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2015 | 2015-01-01 00:00:00 UTC | 2016-01-01 00:00:00 UTC | 3 | 0 | 3 |
| 2016 | 2016-01-01 00:00:00 UTC | 2017-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 2 | 1 | 1 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 1 | 1 | 0 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 6 | 0 | 6 |
What Hacker News says
4 sourcesI used to use a homebrew script that implemented rsync/snapshots (that is, rsync data to a directory on another server, then "cp -al" all files to create hard links into a directory called "server-datestamp-weekly" (or daily, monthly, etc).
After running into scaling issues (esp. when needing to find a specific file that I didn't have a date or server name), I wrote (and open-sourced) Snebu. This works effectively like rsync/snapshots, but it stores the file metadata in an sqlite database (so there is very little setup complexity / maintanence), and individual files are stored compressed in a vault directory, named by the SHA1 checksum of the file. This gets cross server file-level deduplication for free. This is somewhat similar to how git stores files.
Just recently posted a 1.0 release, although I need to improve the documentation a
Read the rest
bit and post a few more front-end scripts (and finish the in-app help pages). But would love to get some feedback on it.
The site is www.snebu.com if you are interested (this points to the Github-hosted page, the project page is github.com/derekp7/snebu).
For data retention, I keep daily backups for a couple weeks, weekly backups for 6 weeks, monthlys for a year, and yearlys for as long as I have space.
This post is so apropos for me (at least the title is) -- I'm perfectly fine with the Git part of github, but was struggling with the other parts of it. For example, trying to figure out how to make a versioned release. The download link they provide gets you the latest version from the repository. Took me a bit of searching and looking at other projects to realize that if you tag a release, it can make that available too.
But now trying to get that to show up in the project page (using their auto page generator) -- I ended up having to hand edit the html code, because I wanted the web page to have a list of specific releases. But even their source download link isn't fully intuitive. For example, mine shows up as "https://github.com/derekp7/snebu/archive/1.0.tar.gz, but it downloads a file called "snebu-1.0.tar.gz".
Oh, and to get t
Read the rest
he readme file to utilize their markdown, you have to call it reamde.md, instead of readme.txt. And I'm looking for where my users can leave feedback or discuss things, other then opening an issue in the issue tracker. But they don't have any mailing lists or forums (I guess most projects set up a separate forum, and link to it from the readme.md file or the gh-pages page).
What I'd like to see is a document going over the entire lifecycle of all the features offered through github, including documenting the standard practices for items that they don't provide (such as the forums thing). Anyone got any pointers?
I've had that same resolution, to do regular backups, but couldn't settle on a good method. I have a problem with the regular full/differential/incremental on monthly/weekly/daily schedule, as there was too much file duplication (therefore I couldn't maximize my backup history). I too settled on using the rsync with hard links method (homebrew scripts similar to rsnapshot, etc), but felt like I was still wasting too much space because this didn't support compression (plus you had to ssh in as root on the target host to store your files).
Long story short, in order to get something I was comfortable with I eventually wrote my own backup tool that accomplished something similar (incremental backups forever, but full snapshots of the system on each backup), but has compression and uses SQLite for its database backend. I'm working on final
Read the rest
izing it as an open source project up on Github if anyone is interested in it (need to finish the documentation, and add status report functionality yet, along with some misc. cleanup). But so far it seems to be working for me.
Edit: I forgot to mention the project name. It is on github.com/derekp7/snebu and I just set up a domain today pointing to it, http://www.snebu.com. Like I said, a work in progress (the download links on the web page are auto-generated by Github, and will always pull the current version from the git repository). In the next few days I'm going to load test it a bit more, once I get the unit tests written (and dogfood it a bit more) I'll tag a 1.0 release and update the page.