zfsnapr
restic
Our great sponsors
zfsnapr | restic | |
---|---|---|
7 | 357 | |
21 | 23,620 | |
- | 2.5% | |
5.6 | 9.7 | |
8 months ago | 7 days ago | |
Ruby | Go | |
BSD 2-clause "Simplified" License | BSD 2-clause "Simplified" License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
zfsnapr
-
Kopia: Open-Source, Fast and Secure Open-Source Backup Software
FreeBSD had a pretty decent option in the base system two decades ago - FFS snapshots and a stock backup tool that would use them automatically with minimal effort, dump(8). Just chuck `-L` at it and your backups are consistent.
Now of course it's all about ZFS, so there's at least snapshots paired with replication - but the story for anything else is still pretty bad, with you having to put all the fiddly pieces together. I'm sure some people taught their backup tool about their special named backup snapshots sprinkled about in `.zfs/snapshot` directories, but given the fiddly nature of it I'm also sure most people just ended up YOLOing raw directories, temporal-smearing be damned.
I know I did!
I finally got around to fixing that last year with zfsnapr[1]. `zfsnapr mount /mnt/backup` and there's a snapshot of the system - all datasets, mounted recursively - ready for whatever backup tool of the year is.
I'm kind of disappointed in mentioning it over on the Practical ZFS forum that the response was not "why didn't you just use ", but "I can see why that might be useful".
Well, yes, it makes backups actually work.
> Also, it's unclear to me what happens if you attempt a snapshot in the middle of something like a database transaction or even a basic file write. Seems likely that the snapshot would still be corrupted
A snapshot is a point-in-time image of the filesystem at a given point. Any ACID database worth the name will roll back the in-flight transaction just like they would if you issued it a `kill -9`.
For other file writes, that's really down to whether or not such interruptions were considered by the writer. You may well have half-written files in your snapshot, with the file contents as they were in between two write() calls. Ideally this will only be in the form of temporary files, prior to their rename() over the data they're replacing.
For everything else - well, you have more than one snapshot backed up, right?
-
ZFS for Dummies
I make remote snapshot backups with Borg using this: https://github.com/Freaky/zfsnapr
zfsnapr mounts recursive snapshots on a target directory so you can just point whatever backup tool you like at a normal directory tree.
I still use send/recv for local backups - I think it's good to have a mix of strategies.
-
BorgBackup, Deduplicating archiver with compression and encryption
This is why I made https://github.com/Freaky/zfsnapr
Instead of working out how to teach my backup tools about snapshots, I just mount them in a subtree and use that as a chroot env.
-
Ask HN: Can I see your scripts?
borg-backup.sh, which runs my remote borg backups off a cronjob: https://github.com/Freaky/borg-backup.sh
zfsnapr, a ZFS recursive snapshot mounter - I run borg-backup.sh using this to make consistent backups: https://github.com/Freaky/zfsnapr
mkjail, an automatic minimal FreeBSD chroot environment builder: https://github.com/Freaky/mkjail
run-one, a clone of the Ubuntu scripts of the same name, which provides a slightly friendlier alternative to running commands with flock/lockf: https://github.com/Freaky/run-one
-
Correct Backups Require Filesystem Snapshots
I wrote https://github.com/Freaky/zfsnapr a few months ago so I could finally have point-in-time consistent Borg backups with ZFS snapshots, without having the mess of teaching Borg where every .zfs directory was.
It recursively snapshots mounted pools, and recursively mounts snapshots of the mounted datasets into a target ready to point your backup tools at. I do so via a chroot so I didn't need to make any changes to my Borg setup - just to how I run it.
-
Snapshot stat changes on access
This is the approach I take with zfssnapr - make a recursive snapshot of pools and then use mountpoint/canmount to recursively mount datasets on a location. Then I can just point borg at it without having to teach it where exactly each .zfs directory is.
- zfsnapr — recursively mount a system snapshot on a given location
restic
-
Building a Managed Service Provider Business With Open Source
Restic - GitHub
-
Ask HN: What is your approach for managing personal digital assets?
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.
- Restic – Backups Done Right
- Data corruption issue in restic 0.16.3 with max compression
- Rclone syncs your files to cloud storage
-
Duplicity
After Borg, I switched to Restic:
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.
- Restic – Simple Backups
-
The Drive Stats of Backblaze Storage Pods
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.
- Selfhostate e avete un homelab?
-
best backup for ubuntu ?
I use and recommend restic. I use it for about 60 machines on my LAN, and it's absolutely fantastic.
What are some alternatives?
BorgBackup - Deduplicating archiver with compression and authenticated encryption.
ioztat - ioztat is a storage load analysis tool for OpenZFS. It provides iostat-like statistics at an individual dataset/zvol level.
Duplicati - Store securely encrypted backups in the cloud!
benchmarks - Benchmarks of different backup tools.
Duplicity - Unnoficial fork of Duplicity - Bandwidth Efficient Encrypted Backup
RcloneZFSBackup - Backup ZFS snapshots to cloud storage using RCLone
kopia - Cross-platform backup tool for Windows, macOS & Linux with fast, incremental backups, client-side end-to-end encryption, compression and data deduplication. CLI and GUI included.
borgmatic - Simple, configuration-driven backup software for servers and workstations
Duplicacy - A new generation cloud backup tool
borgtui - A nice TUI for BorgBackup
Rsnapshot - a tool for backing up your data using rsync (if you want to get help, use https://lists.sourceforge.net/lists/listinfo/rsnapshot-discuss)