From: Fiona Ebner <f.ebner@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Thomas Lamprecht <t.lamprecht@proxmox.com>
Cc: Anuradha Joshi <Anuradha.Joshi@veritas.com>,
Jason Voneberstein <Jason.vonEberstein@veritas.com>,
Sudhir Subbarao <Sudhir.Subbarao@veritas.com>
Subject: Re: [pve-devel] About PVE Backup Integration Guide
Date: Mon, 10 Mar 2025 10:14:13 +0100 [thread overview]
Message-ID: <c355aa91-fcdf-46d2-9ed7-89c215ae5d01@proxmox.com> (raw)
In-Reply-To: <mailman.766.1741156631.293.pve-devel@lists.proxmox.com>
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.ebner@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.ebner@proxmox.com/
https://lore.proxmox.com/pve-devel/20241114150754.374376-5-f.ebner@proxmox.com/
Best Regards,
Fiona
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2025-03-10 9:15 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <PH0PR20MB4520A4201D4560B18A0C830798C82@PH0PR20MB4520.namprd20.prod.outlook.com>
2025-03-04 15:47 ` [pve-devel] FW: " Prashant Patil via pve-devel
[not found] ` <PH0PR20MB45201A18272FF3B7B386D98B98C82@PH0PR20MB4520.namprd20.prod.outlook.com>
2025-03-04 16:37 ` [pve-devel] " Thomas Lamprecht
2025-03-05 6:36 ` Prashant Patil via pve-devel
2025-03-10 9:14 ` Fiona Ebner [this message]
2025-03-17 7:02 ` Prashant Patil via pve-devel
[not found] ` <PH0PR20MB4520C688E38C97D5DE5FC25B98DF2@PH0PR20MB4520.namprd20.prod.outlook.com>
2025-03-17 10:53 ` Fiona Ebner
2025-03-17 13:30 ` Prashant Patil via pve-devel
[not found] ` <PH0PR20MB4520276B3A7061528854180598DF2@PH0PR20MB4520.namprd20.prod.outlook.com>
2025-03-18 8:59 ` Prashant Patil via pve-devel
[not found] ` <PH0PR20MB45209D60E2A2A691D643A3C998DE2@PH0PR20MB4520.namprd20.prod.outlook.com>
2025-03-20 8:34 ` Prashant Patil via pve-devel
2025-03-21 14:13 ` Fiona Ebner
2025-03-24 5:20 ` Prashant Patil via pve-devel
[not found] ` <PH0PR20MB4520584B52872E16277A621198A42@PH0PR20MB4520.namprd20.prod.outlook.com>
2025-03-25 8:59 ` Fiona Ebner
2025-03-25 10:23 ` Prashant Patil via pve-devel
[not found] ` <PH0PR20MB4520FF39B329114AB45B2ADD98A72@PH0PR20MB4520.namprd20.prod.outlook.com>
2025-03-25 10:39 ` Fiona Ebner
2025-03-26 15:06 ` Prashant Patil via pve-devel
[not found] ` <PH0PR20MB452084FCE3C6D7DD55BDEBC398A62@PH0PR20MB4520.namprd20.prod.outlook.com>
2025-03-27 8:49 ` Fiona Ebner
2025-03-27 9:05 ` Prashant Patil via pve-devel
[not found] ` <PH0PR20MB452056ED55E525FF89127CFA98A12@PH0PR20MB4520.namprd20.prod.outlook.com>
2025-03-27 12:59 ` Fiona Ebner
[not found] ` <PH0PR20MB45200BE3B210EC8C69046E6698A02@PH0PR20MB4520.namprd20.prod.outlook.com>
2025-03-28 10:08 ` Fiona Ebner
2025-04-01 7:02 ` Prashant Patil
2025-04-01 8:07 ` Fiona Ebner
2025-04-01 8:45 ` Fiona Ebner
2025-04-01 8:52 ` Prashant Patil via pve-devel
[not found] ` <PH0PR20MB45208AD2006C9D22F1EBF0A998AC2@PH0PR20MB4520.namprd20.prod.outlook.com>
2025-04-01 9:05 ` Fiona Ebner
2025-04-01 10:59 ` Prashant Patil via pve-devel
[not found] ` <PH0PR20MB45206E718C1F7B1C4660D00098AC2@PH0PR20MB4520.namprd20.prod.outlook.com>
2025-04-01 11:18 ` Fiona Ebner
2025-04-01 11:54 ` Prashant Patil via pve-devel
[not found] ` <PH0PR20MB452007780D6055D15DFD565098AC2@PH0PR20MB4520.namprd20.prod.outlook.com>
2025-04-01 15:38 ` Fiona Ebner
2025-04-02 6:20 ` Prashant Patil via pve-devel
[not found] ` <PH0PR20MB4520109F59C59C3976298E8798AF2@PH0PR20MB4520.namprd20.prod.outlook.com>
2025-04-02 7:15 ` Thomas Lamprecht
2025-04-02 9:04 ` Prashant Patil via pve-devel
[not found] ` <PH0PR20MB4520725FF56C2F89E6A6EDDE98AF2@PH0PR20MB4520.namprd20.prod.outlook.com>
2025-04-09 13:26 ` Fiona Ebner
[not found] ` <PH0PR20MB4520446B9B012DE3352A8C1F98CB2@PH0PR20MB4520.namprd20.prod.outlook.com>
2025-03-05 15:44 ` Prashant Patil via pve-devel
2025-03-04 13:21 Prashant Patil via pve-devel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c355aa91-fcdf-46d2-9ed7-89c215ae5d01@proxmox.com \
--to=f.ebner@proxmox.com \
--cc=Anuradha.Joshi@veritas.com \
--cc=Jason.vonEberstein@veritas.com \
--cc=Sudhir.Subbarao@veritas.com \
--cc=pve-devel@lists.proxmox.com \
--cc=t.lamprecht@proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal