zrepl
go-snaps
Our great sponsors
| zrepl | go-snaps | |
|---|---|---|
| 22 | 2 | |
| 894 | 128 | |
| 1.1% | - | |
| 6.8 | 6.5 | |
| about 1 month ago | 14 days ago | |
| Go | Go | |
| MIT License | MIT 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.
zrepl
- Zrepl – ZFS replication
- zrepl: A one-stop, integrated solution for ZFS replication
- PVE Host disk upgrade
-
Void Linux and root-on-ZFS question
Lastly there is zrepl. This is an automatic snapshot creation, pruning and replication daemon. It lets you automate the creation of ZFS snapshots at specific intervals, apply a retention policy to them, and replicate them out to a remote system with ZFS, like a NAS with TrueNAS on it.
- Container Updating Strategies
-
How do you all prepare for a disaster recovery of your nextcloud instance?
I run it in a FreeBSD jail and take frequent ZFS snapshots using zrepl. I’ve had to restore after failed updates and it worked flawlessly.
-
Recommend ZFS automation scripts for off-server backups?
As others have noted, I use syncoid but zrepl is an alternative that could be considered.
-
Imagine You're a Goofball: Dynamic Preventative ZFS Snapshots
I’m going to throw out Zrepl again because it’s amazing: https://zrepl.github.io/
- Using ZFS backup drive for rsync manually
-
Question about best way to do zfs replication to a friends server
Current idea: We offer some form of container each other, where we have that zvol mounted somewhere for the replication use. This would mean that I could create an "inside zfs" where I create a filebased zpool. How is performance on a filebased zpool? (Although it is technically not so important that it performs critically, just trying to find the - or one of - "best" ways). Then we would offer each an ssh endpoint into that container (It doesn't have to be ssh, but it is so far convenient to setup and resilient to be open to the public). And my current plan is to use zrepl (https://zrepl.github.io/) to organise replication from my home server to this "inside" zpool.
go-snaps
-
Snapshot testing in golang
https://github.com/gkampitakis/go-snaps. Have a look, feedback is always welcome.
-
Snapshot testing in Golang
In the repository, you can find examples and more information in README.
What are some alternatives?
sanoid - These are policy-driven snapshot management and replication tools which use OpenZFS for underlying next-gen storage. (Btrfs support plans are shelved unless and until btrfs becomes reliable.)
cupaloy - Simple Go snapshot testing
zfs_autobackup - ZFS autobackup is used to periodicly backup ZFS filesystems to other locations. Easy to use and very reliable.
spawn - Spawn your Go server from within its own test suite, for end-to-end tests
zfs - OpenZFS on Linux and FreeBSD
lxd-snapper - LXD snapshots, automated
zfswatcher - ZFS pool monitoring and notification daemon
zfsbackup-go - Backup ZFS snapshots to cloud storage such as Google, Amazon, Azure, etc. Built with the enterprise in mind.
yunohost - YunoHost is an operating system aiming to simplify as much as possible the administration of a server. This repository corresponds to the core code, written mostly in Python and Bash.
Mailpile - A free & open modern, fast email client with user-friendly encryption and privacy features
docker-mailserver - Production-ready fullstack but simple mail server (SMTP, IMAP, LDAP, Antispam, Antivirus, etc.) running inside a container.
Cypht - Cypht: Lightweight Open Source webmail written in PHP and JavaScript