@Andrew Yeah but XOA is still using it hence my interest in aligning my XO-CE instance with XOA as close as possible.

@rzr Great. Thank you!

@Bastien-Nollet I'm running c1e5f btw

another example, on another client server : yesterday we were on XOA 6.0.3 [image: 1775673583836-44f9a93b-3e8e-45b4-9a98-767489a3cb80-image.jpeg] today we updated to XOA 6.3.2 [image: 1775673618586-91898d80-a37f-4ca7-bcb1-f3340d45530b-image.jpeg] clean-vm get from 4min to an hour on this single VM ! for barely 5Gb transfer size same VMs, same NFS remote on same NAS, nothing changed except XOA version whole backup window on this 12 VMs job is shifted +4hours (still not finished...)

@Tristis-Oris maybe a few comparative screenshots would help

Hi, Someone from the Hypervisor & Kernel team will have a look shortly, we'll get back to you with our findings. Thanks a lot for the very detailed report! Yann

+1 this. We would like to run certain VM's only in certain datacenters, but allow the VM to migrate to other hosts in the same datacenter.

@TechGrips Hi, Unused XVA means a XVA file is not linked to any metadata (to remove a backup, we first remove the metadata file linked to it, then we remove the XVA), it should be removed by clean vm step. It is not an issue, just an information. For the second warning "XVA might be broken", this is because the compressed file seems to be corrupted but we cannot be sure. We prefer to warn the user there may be an issue in the file. This should encourage to remake a backup.