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 C85E41FF172 for <inbox@lore.proxmox.com>; Tue, 1 Apr 2025 13:19:10 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id D532C1F8DE; Tue, 1 Apr 2025 13:18:59 +0200 (CEST) Message-ID: <94a5f198-ed41-4655-ba89-e1d9d9fc8cae@proxmox.com> Date: Tue, 1 Apr 2025 13:18:56 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird To: Prashant Patil <Prashant.Gamepatil@veritas.com>, Proxmox VE development discussion <pve-devel@lists.proxmox.com>, Thomas Lamprecht <t.lamprecht@proxmox.com> References: <PH0PR20MB4520A4201D4560B18A0C830798C82@PH0PR20MB4520.namprd20.prod.outlook.com> <PH0PR20MB4520584B52872E16277A621198A42@PH0PR20MB4520.namprd20.prod.outlook.com> <3c13a721-14c4-41ae-8ad2-b52a2d84bd38@proxmox.com> <PH0PR20MB4520FF39B329114AB45B2ADD98A72@PH0PR20MB4520.namprd20.prod.outlook.com> <766af997-a62a-4dd2-804f-9c018cd7b707@proxmox.com> <PH0PR20MB452084FCE3C6D7DD55BDEBC398A62@PH0PR20MB4520.namprd20.prod.outlook.com> <65b843b1-af29-40fd-807c-3f2e4d03ae94@proxmox.com> <PH0PR20MB45200BE3B210EC8C69046E6698A02@PH0PR20MB4520.namprd20.prod.outlook.com> <2316485c-f24a-4a74-8427-4afeaca86567@proxmox.com> <PH0PR20MB4520E9A4E56E11C9FDC9981598AC2@PH0PR20MB4520.namprd20.prod.outlook.com> <6e1b4e46-ddc6-46a2-bdc3-649a354a3525@proxmox.com> <PH0PR20MB45208AD2006C9D22F1EBF0A998AC2@PH0PR20MB4520.namprd20.prod.outlook.com> <359a361e-bab9-4d5c-b9e1-b3d081bdac8d@proxmox.com> <PH0PR20MB45206E718C1F7B1C4660D00098AC2@PH0PR20MB4520.namprd20.prod.outlook.com> Content-Language: en-US From: Fiona Ebner <f.ebner@proxmox.com> In-Reply-To: <PH0PR20MB45206E718C1F7B1C4660D00098AC2@PH0PR20MB4520.namprd20.prod.outlook.com> X-SPAM-LEVEL: Spam detection results: 0 AWL -0.038 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>, Sudhir Subbarao <Sudhir.Subbarao@veritas.com>, Jason Voneberstein <Jason.vonEberstein@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 01.04.25 um 12:59 schrieb Prashant Patil: > Just for clarity - The backup/restore jobs will be configured on the > Proxmox VE side, the job gets triggered on Proxmox VE side and that is > where the provider API comes into picture to take backups to specified > storage. Is this understanding correct? Yes, the API is designed for the integrated backup/restore tasks on the Proxmox VE side. The implementation of the API methods will serve as a bridge to your backup server. If you really want, nothing prevents to manage your own jobs from the server side. You'd just need to issue the relevant API calls via the Proxmox VE REST API, e.g.: 1. Your job on the server side decides to run a backup. 2. It sends the 'vzdump' API call to the Proxmox VE node. 3. The Proxmox VE node will call the methods of your backup provider API implementation. 4. Inside these methods, you get access to the data that can be transferred to your backup server. Best Regards, Fiona _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel