pyznap
BorgBackup
pyznap | BorgBackup | |
---|---|---|
9 | 333 | |
198 | 10,559 | |
- | 1.3% | |
0.0 | 9.4 | |
about 1 month ago | 15 days ago | |
Python | Python | |
GNU General Public License v3.0 only | GNU General Public License v3.0 or later |
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)
BorgBackup
-
Ask HN: Open-source Windows 11 backup solutions
i use - and recommend - "borgbackup": for example with the "vorta" graphical frontend
* https://www.borgbackup.org/
* https://vorta.borgbase.com/install/windows/
just my 0.02€
- I Backup
- Ask HN: For what purposes do you use a Raspberry Pi?
-
Duplicity
I used this many, many years ago but switched to Borg[0] about five years ago. Duplicity required full backups with incremental deltas, which meant my backups ended up using too much disk space. Borg lets you prune older backups at will, because of chunk tracking and deduplication there is no such thing as an incremental backup.
[0] https://www.borgbackup.org/
-
What do you use for VPS backup? Would improved borg setup - pull mode - be enough? Or, do you use something else?
Currently, I'm auto-backing it up with borg (push mode) through wireguard tunnel to NAS behind ISP's CGNAT. The borg takes care of deduplication in SQL file, so incremental update (even in append-only mode) is very small for PostgreSQL dump.
- Borg CVE fix requires migration
-
Kopia: Open-Source, Fast and Secure Open-Source Backup Software
Borg 2 has been in development for nearly a year and a half [1] and may probably be released early next year, i.e., early 2024 (just a guess, seeing that even RC1 is not yet released and seems to have a lot of work to be done).
Does anyone know how Borg 1.x and 2 would compare to Kopia?
[1]: https://github.com/borgbackup/borg/issues/6602
- Home backup solution?
-
disc space is not freeing
You could use borgbackup.
- My deduplication solution written in Rust beats everything else: casync, borg...
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.)
Duplicati - Store securely encrypted backups in the cloud!
zfsbackup-go - Backup ZFS snapshots to cloud storage such as Google, Amazon, Azure, etc. Built with the enterprise in mind.
Duplicity - Unnoficial fork of Duplicity - Bandwidth Efficient Encrypted Backup
cv4pve-autosnap - Automatic snapshot tool for Proxmox VE
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)
Vault - A tool for secrets management, encryption as a service, and privileged access management
restic - Fast, secure, efficient backup program
zfs - OpenZFS on Linux and FreeBSD
TimeShift - System restore tool for Linux. Creates filesystem snapshots using rsync+hardlinks, or BTRFS snapshots. Supports scheduled snapshots, multiple backup levels, and exclude filters. Snapshots can be restored while system is running or from Live CD/USB.
barrier - Open-source KVM software
UrBackup - UrBackup - Client/Server Open Source Network Backup for Windows, MacOS and Linux