pyznap
cv4pve-autosnap
pyznap | cv4pve-autosnap | |
---|---|---|
9 | 6 | |
198 | 364 | |
- | 3.6% | |
0.0 | 4.3 | |
about 1 month ago | 6 days ago | |
Python | C# | |
GNU General Public License v3.0 only | 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.
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)
cv4pve-autosnap
-
Automatic container snapshots? cv4pve or zfs for a small homelab?
From my research, I can see two options: - Proxmox specific cv4pve-autosnap - generic zfs-auto-snapshot, available in repos
-
LVM-Thin vs ZFS
You can use https://github.com/Corsinvest/cv4pve-autosnap to make automated snapshots of guests in proxmox.
-
Advice needed: preparing for the worst
Also, for being able to quickly revert mishaps with your vms, and lxc containers i use https://github.com/Corsinvest/cv4pve-autosnap to make hourly snapshots of all vms and lxc containers (taking snapshots suspends disk io from the vm's point of view. Some software, especially game servers, can't deal with this).
-
Some Proxmox Backup, Snapshot and Storage questions
Since Proxmox natively supports ZFS, you could that to make your snapshots. You can do automatic snapshots with zfs-auto-snapshot or for VMs with cv4pve-autosnap.
-
TUTORIAL: Beauty by simplicity, OR one ZFS Snapshot used by 5 Layers of Applications
to achieve this fabulous glory of software-engineering i utilized this projects: cv4pve-autosnap and Zamba Fileserver on LXC
-
Sanoid for snapshots management?
If you want automatic snapshots that appear in the Proxmox GUI and can be rolled back from there, too, you could check out https://github.com/Corsinvest/cv4pve-autosnap. I recently set it up and it works nicely. It uses the Proxmox API to trigger snapshots. Corsinvest is the company behind this tool. They are part of the Proxmox partner program.
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.)
proxmox-tools - 📦 A collection of stuff that I and others wrote for Proxmox 📦
zfsbackup-go - Backup ZFS snapshots to cloud storage such as Google, Amazon, Azure, etc. Built with the enterprise in mind.
TJs-Kubernetes-Service - Enable enthusiasts and administrators alike to easily provision highly available and production-ready Kubernetes clusters on Proxmox VE.
Vault - A tool for secrets management, encryption as a service, and privileged access management
Cronos - A fully-featured .NET library for working with Cron expressions. Built with time zones in mind and intuitively handles daylight saving time transitions
zfs - OpenZFS on Linux and FreeBSD
barrier - Open-source KVM software
Bitwarden - The core infrastructure backend (API, database, Docker, etc).
zfsbootmenu - ZFS Bootloader for root-on-ZFS systems with support for snapshots and native full disk encryption
zamba-lxc-toolbox - Zamba LXC Toolbox a script collection to setup LXC containers on Proxmox + ZFS. Zamba is the fusion of ZFS and Samba (standalone, active directory dc or active directory member), preconfigured to access ZFS snapshots by "Previous Versions" to easily recover encrypted by ransomware files, accidently deleted files or just to revert changes.