From: Prashant Patil via pve-devel <pve-devel@lists.proxmox.com>
To: Thomas Lamprecht <t.lamprecht@proxmox.com>,
Fiona Ebner <f.ebner@proxmox.com>,
Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Cc: Prashant Patil <Prashant.Gamepatil@veritas.com>,
Anuradha Joshi <Anuradha.Joshi@veritas.com>,
Sudhir Subbarao <Sudhir.Subbarao@veritas.com>,
Jason Voneberstein <Jason.vonEberstein@veritas.com>
Subject: Re: [pve-devel] About PVE Backup Integration Guide
Date: Wed, 2 Apr 2025 09:04:35 +0000 [thread overview]
Message-ID: <mailman.478.1743584689.359.pve-devel@lists.proxmox.com> (raw)
In-Reply-To: <decec1c7-e9f9-47a1-8bbd-23456a8eb410@proxmox.com>
[-- Attachment #1: Type: message/rfc822, Size: 16942 bytes --]
From: Prashant Patil <Prashant.Gamepatil@veritas.com>
To: Thomas Lamprecht <t.lamprecht@proxmox.com>, Fiona Ebner <f.ebner@proxmox.com>, 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>
Subject: RE: [pve-devel] About PVE Backup Integration Guide
Date: Wed, 2 Apr 2025 09:04:35 +0000
Message-ID: <PH0PR20MB4520725FF56C2F89E6A6EDDE98AF2@PH0PR20MB4520.namprd20.prod.outlook.com>
Ok, will give plugins a try and see if we can achieve backup/restore management from our backup solution.
1. Can we just implement backup provider plugin and not storage plugin? We can build storage plugin in subsequent releases.
2. What are the steps to configure/deploy plugins?
3. Can I use the example plugins provided to test? Which one exactly? What are the involved steps to test this?
4. Is this the REST API to be used to create backup task? POST /api2/json/nodes/{node}/vzdump
Regards
Prashant
-----Original Message-----
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
Sent: 02 April 2025 12:45 PM
To: Prashant Patil <Prashant.Gamepatil@veritas.com>; Fiona Ebner <f.ebner@proxmox.com>; 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>
Subject: Re: [pve-devel] About PVE Backup Integration Guide
CAUTION: This email originated from outside the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. If you believe this is a phishing email, use the Report to Cybersecurity icon in Outlook.
Am 02.04.25 um 08:20 schrieb Prashant Patil:
> Basically, the backup/restore tasks will be managed through our backup solution. So, all we needed is VM config which can be fetched through PVE REST API and a API to get access to consistent disk image which can be then transferred to backup storage that we support. But it looks like this is not possible with current design of provider APIs.
It is though, just create PVE backup task for the VMs in question for a Job you manage and a Plugin following the mechanism here gives you exactly that.
> Is there any chance of developing new library which can provide access to consistent disk image in near future?
Above already provides that, we enforce this running in our standard backup environment to ensure it's can be as native as integrated solutions and that all ACL and resource management is followed correctly while being able to create an efficient implementation for both sides, ours and the running VMs and your solution pulling of the data, e.g. including more advanced techniques like changed block tracking and getting the allocation map to skip over holes, allowing one to dramatically speed up the backup process.
Same holds for containers, which we also support and a backup solution should also implement to provide a complete experience that actually nicely integrates into PVE, and not feels tacked on.
This message was sent by an employee of Arctera.
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
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-04-02 9:05 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
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 [this message]
[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=mailman.478.1743584689.359.pve-devel@lists.proxmox.com \
--to=pve-devel@lists.proxmox.com \
--cc=Anuradha.Joshi@veritas.com \
--cc=Jason.vonEberstein@veritas.com \
--cc=Prashant.Gamepatil@veritas.com \
--cc=Sudhir.Subbarao@veritas.com \
--cc=f.ebner@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal