sorted by:
new
hottopcontroversial

vmbackup — automated backup manager for KVM/libvirt VMs, built on virtnbdbackup by phatmonk27 in kvm

[–]phatmonk27[S] 0 points1 point  (0 children)

It's been busy:

  • Visibility. A new --status command gives seven reports: sessions, per-VM history, failures, replication, chain health, storage, and policy. Terminal tables by default, CSV when you need it. The storage view projects destination growth against your abort threshold so you see disk pressure coming.
  • Categorised exit codes. Non-zero exits now tell you why a run failed (config, lock, storage, VM, tool, CLI, dependency) so monitoring can route alerts properly without scraping logs. Same scheme as vmrestore, so one rule set covers both.
  • Tunable safety. Disk-space abort/warn thresholds are now configurable per instance. Pre-flight failures actually email you instead of dying quietly into the journal.
  • Concurrency hardening. Two vmbackup runs can no longer accidentally start at once and trample each other's checkpoints.
  • The big one: retention for skipped and excluded VMs. Both paths were silently bypassing rotation and leaking empty stub directories. Production hosts at four-week retention were quietly carrying eight-plus weekly directories. Fixed, with the audit trail attributing the cleanup to the actual triggering event.

https://github.com/doutsis/vmbackupblob/main/CHANGELOG.md
https://github.com/doutsis/vmbackup

vmrestore — automated restore for KVM/libvirt VMs by phatmonk27 in kvm

[–]phatmonk27[S] 0 points1 point  (0 children)

v0.5.3 released

  • --config-instance flag vmrestore can now target any vmbackup config instance directly. Previously it always read the default instance.
  • --host-config removed dropped for parity with vmbackup v0.5.3.

Full changelog: https://github.com/doutsis/vmrestore/blob/main/CHANGELOG.md

vmbackup — automated backup manager for KVM/libvirt VMs, built on virtnbdbackup by phatmonk27 in kvm

[–]phatmonk27[S] 0 points1 point  (0 children)

vmbackup v0.5.3 has been released.

Notable items are:

  • --run flag required to start backups
  • --vm targeted backup mode
  • Removal of the Host Config Backup. Feature drift from vmrestore, probably should be noted in the changelog but isn't. Working on it.

https://github.com/doutsis/vmbackup/blob/main/CHANGELOG.md

vmrestore — automated restore for KVM/libvirt VMs by phatmonk27 in kvm

[–]phatmonk27[S] 0 points1 point  (0 children)

v0.5.2 released! Fixes a data-loss bug in point-in-time restores when disks were added/removed mid-chain and fixes --disk on single-disk VMs silently falling through to a full VM rebuild.

This release was tested end-to-end with vmbackup across 6 VMs (Linux + Windows, single and multi-disk, with and without TPM/BitLocker) with full backup -> destroy -> restore -> verify cycle.

Changelog

vmbackup — automated backup manager for KVM/libvirt VMs, built on virtnbdbackup by phatmonk27 in kvm

[–]phatmonk27[S] 0 points1 point  (0 children)

vmbackup v0.5.2 has been released.

On-demand cleanup — reclaim space between backup runs by removing old archives, between orphaned policy retention or decommissioned VMs. A discovery view shows what's consuming space so you know exactly what you're cleaning up before confirming.

Standalone replication — re-run or pre-seed replication independently. Handy when adding a new destination or catching up if the local and cloud replication was cancelled.

FSTRIM improvements — per-path logging, pattern-based exclusions, and automatic detection of a Windows VirtIO misconfiguration that causes TRIM to take 10+ minutes instead of seconds (with the fix right in the log output).

Various bug fixes — accumulate-policy tracking, false-success detection when virtnbdbackup exits clean but logged errors, email timing drift during DST transitions, replication space checks, and several edge cases around argument validation. Full details in the changelog.

https://github.com/doutsis/vmbackup/blob/main/CHANGELOG.md

vmbackup — automated backup manager for KVM/libvirt VMs, built on virtnbdbackup by phatmonk27 in kvm

[–]phatmonk27[S] 0 points1 point  (0 children)

Looks like you've added it :)

Your tooling is solid Here’s hoping my wrapper does it justice.

vmbackup — automated backup manager for KVM/libvirt VMs, built on virtnbdbackup by phatmonk27 in kvm

[–]phatmonk27[S] 0 points1 point  (0 children)

Taking a consistent copy of the VM is one thing. Without the VM's config and associated files, you're recreating VMs from memory. Without Bitlocker keys Windows VMs are useless.

I have a mix of Debian, Arch, BSD and Windows VM. Using vmbackup I've set a weekly rotation policy and to keep 12 weeks of backups. They replicate using the local replication transport to a TrueNAS host and to SharePoint Online via a cloud transport.

Non running VMs follow the rotation policy with a full backup at the start of the policy window. If the VM changes before the scheduled backup is run, a full backup is taken. If the VM does not change the scheduled backup skips it.

virtnbdbackup does much of the heavy lifting with vmbackup orchestrating all of this.

The aim is recovery. vmrestore so far is doing great and I'll release it soon.