Upstream software project

virt-backup

Backup script for libvirt managed VM

About virt-backup

Backup script for libvirt managed VM

This project links 2 native package records across 2 recorded operating-system releases. Compare the retained versions and architectures below, then open the package for your own release.

These are catalog observations, not a guarantee of installation, compatibility, or upstream support.

Project pictures and package coverage

Fedora 43: 1 package records; Fedora 44: 1 package records. Catalog coverage diagram, not an application screenshot.virt-backup: recorded package coverageFedora 431 recordsFedora 441 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
virt-backup
Publisher
Not authoritatively mapped
Native package records
2
Operating systems
fedora-43, fedora-44
License expression
GPL-2.0-or-later
Source repository
Not reported

Source-reported description

The fullest retained description is shown with its source. Distribution packaging descriptions may include downstream details.

This script allows you to backup Virtual Machines managed by libvirt. It has only be tested with KVM based VM This script will dump (or mount as a set of chunks): * each block devices * optionnally the memory (if --state flag is given) * the XML description of the VM

Description source

Packages by operating system

Compare recorded versions, then open a package for dependency, file, checksum, and repository evidence. Version strings are distribution-specific, not a ranking of newer software.

Fedora 43

  1. Package virt-backup

    43 (Fedora 43) (Unspecified): Backup script for libvirt managed VM

    0.2.25-15.fc43: noarch

    Source: virt-backup

Fedora 44

  1. Package virt-backup

    44 (Fedora 44) (Unspecified): Backup script for libvirt managed VM

    0.2.25-16.fc44: noarch

    Source: virt-backup

Project resources and further reading

Mapping provenance

Only source-backed identity signals create public cross-OS links. A reviewer can later approve or dispute an inferred relationship without rewriting native package history.

No field-level source record is published yet.