From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <pve-devel-bounces@lists.proxmox.com> Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id 2A7FB1FF173 for <inbox@lore.proxmox.com>; Mon, 10 Mar 2025 10:15:01 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 6855E14D81; Mon, 10 Mar 2025 10:14:52 +0100 (CET) Message-ID: <c355aa91-fcdf-46d2-9ed7-89c215ae5d01@proxmox.com> Date: Mon, 10 Mar 2025 10:14:13 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>, Thomas Lamprecht <t.lamprecht@proxmox.com> References: <PH0PR20MB4520A4201D4560B18A0C830798C82@PH0PR20MB4520.namprd20.prod.outlook.com> <PH0PR20MB45201A18272FF3B7B386D98B98C82@PH0PR20MB4520.namprd20.prod.outlook.com> <2402a2e8-63a5-46c4-9b66-d998f6e421c7@proxmox.com> <mailman.766.1741156631.293.pve-devel@lists.proxmox.com> Content-Language: en-US From: Fiona Ebner <f.ebner@proxmox.com> In-Reply-To: <mailman.766.1741156631.293.pve-devel@lists.proxmox.com> X-SPAM-LEVEL: Spam detection results: 0 AWL -0.043 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_RPBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_SAFE_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: Re: [pve-devel] About PVE Backup Integration Guide X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion <pve-devel.lists.proxmox.com> List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/pve-devel>, <mailto:pve-devel-request@lists.proxmox.com?subject=unsubscribe> List-Archive: <http://lists.proxmox.com/pipermail/pve-devel/> List-Post: <mailto:pve-devel@lists.proxmox.com> List-Help: <mailto:pve-devel-request@lists.proxmox.com?subject=help> List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel>, <mailto:pve-devel-request@lists.proxmox.com?subject=subscribe> Reply-To: Proxmox VE development discussion <pve-devel@lists.proxmox.com> Cc: Anuradha Joshi <Anuradha.Joshi@veritas.com>, Jason Voneberstein <Jason.vonEberstein@veritas.com>, Sudhir Subbarao <Sudhir.Subbarao@veritas.com> Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pve-devel-bounces@lists.proxmox.com Sender: "pve-devel" <pve-devel-bounces@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