zfsbackup-go
pyznap
zfsbackup-go | pyznap | |
---|---|---|
5 | 9 | |
318 | 198 | |
- | - | |
0.0 | 0.0 | |
about 1 year ago | about 1 month ago | |
Go | Python | |
MIT License | GNU General Public License v3.0 only |
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.
zfsbackup-go
- ZFS Backup to Cloud Storage Services
-
Incremental backups / replication to non-ZFS destinations?
Z3 doesn't seem to be maintained. This script seems to be a oneoff. ZFSBackup Go seems more full featured but also unmaintained and out of date as well.
-
Don't do VFIO to save money...or time (opinion piece)
6) build zfsbackup-go https://github.com/someone1/zfsbackup-go
-
I know it’s not recommended to expose Pihole to the internet but how secure is this?
I have a similar setup, but I use DoH-server to pass queries to pihole. Pihole is not accessible to the world on UDP 53. I guess this could be abused with a TCP reflection attack, but I don't think anymore so than just having an open web server, which I also have. That's sort of the whole point of a web server.
-
Cloud backup solution that is ZFS-friendly
i’d also like to share: https://github.com/someone1/zfsbackup-go (can’t vet it fully, it seems promising and i started down the path but didn’t complete)
pyznap
- Python Port of 600 Line Bash Script: rsync-time-machine.py for Rsync Backups
-
Should I be using zfs replicate, mirror, or something else entirely?
Sanoid/syncoids been mentioned but honestly for once a week learning by doing . Pyznap also excellent when you want to automate. https://github.com/yboetz/pyznap
-
Vdevs and snapshots?
In contrast, zfs snapshots are immutable, and thus anything short of a hardware failure can be addressed with a simple zfs rollback command. This includes deliberate, accidental, and malicious actions. They can also be automated (I personally use pyznap but syncoid is also quite popular), creating what is effectively an incremental backup. I maintain - for each dataset - 24 hourly, 7 daily, 6 monthly, and 1 yearly snapshot. Additionally, I have a wholly separate server that wakes up once a day to ingest these snapshots via zfs send/recv, so even if I made a horrible mistake or suffered a catastrophic hardware failure, I could completely restore from the other server. This last point brings snapshots firmly into the realm of backups, IMO.
-
Sanoid for snapshots management?
Another favorite option is Pyznap, which is python based and originally created to have have a few features and changes compared to sanoid. The author is also active here on reddit. I and not sure what the differences are anymore, it'll come down to trying them and preference.
- Advice on settings for spin-down (Ubuntu Server)
-
A small script to wake up a node that doesn't like to boot
I have two Supermicro X9 2Us, each with Proxmox. One has allegedly existed solely as a backup target, which wakes up daily to ingest ZFS snapshots using pyznap. Unfortunately, for reasons which are unclear, this particular node doesn't always like to see its boot device, which is an NVMe drive. It's the exact same board as my primary, with the exact same modified BIOS to allow booting from NVMe. It usually takes 2-3 cycles before it'll see it and boot.
-
Pros/cons of visible dataset for backups vs. only snapshots
I have two nearly identical systems, both running Proxmox, with Debian VMs. One is a backup, which (once this is worked out) will wake up daily to ingest incremental backups. I'm using pyznap to handle the backup strategy.
-
Ubuntu server 21.04 native encrypted root on zfs zfsbootmenu pyznap
https://github.com/yboetz/pyznap/issues/1#issuecomment-351015432
- Don't do VFIO to save money...or time (opinion piece)
What are some alternatives?
restic - Fast, secure, efficient backup program
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.)
zrepl - One-stop ZFS backup & replication solution
cv4pve-autosnap - Automatic snapshot tool for Proxmox VE
z3 - Backup your ZFS snapshots to S3.
Vault - A tool for secrets management, encryption as a service, and privileged access management
rclone - "rsync for cloud storage" - Google Drive, S3, Dropbox, Backblaze B2, One Drive, Swift, Hubic, Wasabi, Google Cloud Storage, Azure Blob, Azure Files, Yandex Files
zfs - OpenZFS on Linux and FreeBSD
vendor-reset - Linux kernel vendor specific hardware reset module for sequences that are too complex/complicated to land in pci_quirks.c
barrier - Open-source KVM software
scream - Virtual network sound card for Microsoft Windows
zfsbootmenu - ZFS Bootloader for root-on-ZFS systems with support for snapshots and native full disk encryption