Am 05.03.25 um 07:36 schrieb Prashant Patil via pve-devel: > 1. How much part of the plugins method is done?
It is an initial, functional version of the API. > 2. How soon we can start the integration? The patches were not applied yet, feedback is welcome. As Thomas already said "We would be open to fast-track this effort for inclusion with feedback from backup vendors". I'll see if I can get around to post a rebased version this week. > 3. Is there any plugin method's documentation already available? If yes, > could you please share? It's part of the patches, see: https://lore.proxmox.com/pve-devel/20241114150754.374376-10-f.eb...@proxmox.com/ > 1. How to get allocated blocks/sectors from the snapshot of the raw format > virtual disk attached to a running VM (disk present on the block based > storage such as lvm, lvm-thin, etc)? > 2. How to get allocated blocks/sectors from the snapshot of the vmdk > format virtual disk attached to a running VM? > 3. As per below link, certain storage types do not support snapshots. In > such cases, what is the recommended way to take backup of the running VM? The block tracking is ideally done via QEMU, then you don't require any special features for the underlying storages. You can also do dirty tracking for incremental backups. See the following for how this is done internally with the proposed API: https://lore.proxmox.com/pve-devel/20241114150754.374376-4-f.eb...@proxmox.com/ https://lore.proxmox.com/pve-devel/20241114150754.374376-5-f.eb...@proxmox.com/ Best Regards, Fiona _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
