Michael Ablassmeier

ok, now i see the full picture, the disk is configured differently as in your first posts here: https://github.com/abbbi/virtnbdbackup/issues/286#issuecomment-3434172733 The disk is configured as type "network" disk: `` there is...

either way, maybe you can prepare an pull request?

wow, thats lots of changes for this feature .. not yet sure if im going to merge.. maybe it makes sense you run on your own branch for a while...

have you actually tried the approach with the data-file/datastore configuration in libvirt? It would be interesting if this would work, too. Then no changes are required for backup.

something like this, just adjusted to ceph should work: ``` ``` like: ``` ``` this way the image /var/lib/libvirt/images/metadata.qcow2 would be used as metadata image for checkpoints and bitmaps and...

or as alternative pointing to an RBD device directly: ``` ```

currently differential backup always refers back to the *latest* backup available in the chain. I think this is more flexible. Why backup changed data multiple times if not required? The...

the only way i see is to implement at new command line parameter allowing to change behavior to not break the current workflow for existing installations.

> for greater flexibility, we can use command line option for virtnbdbackup utility, for example, --from virnbdbackup.0 or another checkpoint that could introduce a whole lot of problems if used...

> ### Each diff backup should save all changes that have occurred since the last full backup. > if args.level == "diff": > parentCheckpoint = checkpoints[0] #for take ONLY full...