Ruben S. Montero
Ruben S. Montero
Consider this together with #5463
Check support for revert added in this libvirt version https://libvirt.org/news.html#v9-9-0-2023-11-01
We have been disusing this internally and, what we call "in-place" restore is something we want to tackle, We'll keep this issue to address this feature. However, I don't agree...
Even more important as incremental backups impose important limitations for snapshots.
planned for next maintenance
Deleted the comments related to support as the user has been redirected to the forum by OP. Thanks!
I think we can consider this issue as implemented by this one: #6313
Just to double check is BACKUP_VOLATILE set to YES? https://docs.opennebula.io/6.8/management_and_operations/backups/operations.html#reference-backup-configuration-attributes
> I would also like to add, that `saveas` action cant be done over a volatile disk. Does it have something related with the missing property "SAVE" that @nachowork90 said...
About `SAVE` this attribute marks the disk as persistent, it is not used to determine which disks needs to be backup. In the backup logic it is checked because persistent...