Feature Request: Support "Map Backup" and "Move Backup" for Veeam Plug-in for oVirt

[cfs-ks]

I am writing to request the implementation of "Map Backup" and "Move Backup" features for the Veeam Plug-in for oVirt (KVM), similar to what is currently available for VMware and Hyper-V.
Current Challenges:
Job Reconfiguration: Without "Map Backup," we cannot move a VM from one backup job to another while retaining the existing backup chain. This forces a new active full backup for the moved VM, which is a major bottleneck for large-scale environments.
Repository Migration: When changing the backup repository for a job, we cannot use "Move Backup" to migrate the data seamlessly. This again requires starting a new backup chain from scratch.

Specific Use Case:
We are planning an upgrade from v12 to v13. However, since the AlmaLinux we use for our current repository is reaching its end of support (or compatibility), we need to migrate to a new repository. Without "Map Backup" or "Move Backup," we are forced to perform a full backup for all VMs, which is making us hesitant to proceed with the upgrade.
Are there any plans to include these features in the upcoming roadmap?

P.S. Regarding AlmaLinux support, could you clarify its status in VBR v13? Is it officially being deprecated?

[rovshan.pashayev]

Hi

Backup Map feature will be available in an upcoming release.
Backup Move is on the roadmap, but there is no ETA at this time.
Regarding AlmaLinux, it has been deprecated starting with v13. Please refer to the User Guide here.