SaaSHub helps you find the best software and product alternatives Learn more →
Pyznap Alternatives
Similar projects and alternatives to pyznap
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
vendor-reset
Linux kernel vendor specific hardware reset module for sequences that are too complex/complicated to land in pci_quirks.c
-
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.)
-
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)
-
zfsbackup-go
Backup ZFS snapshots to cloud storage such as Google, Amazon, Azure, etc. Built with the enterprise in mind.
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
pyznap reviews and mentions
- 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)
-
A note from our sponsor - SaaSHub
www.saashub.com | 25 Apr 2024
Stats
yboetz/pyznap is an open source project licensed under GNU General Public License v3.0 only which is an OSI approved license.
The primary programming language of pyznap is Python.
Sponsored