From: Prashant Patil via pve-devel <pve-devel@lists.proxmox.com>
To: Fiona Ebner <f.ebner@proxmox.com>,
Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Thomas Lamprecht <t.lamprecht@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: Tue, 1 Apr 2025 11:54:50 +0000 [thread overview]
Message-ID: <mailman.415.1743508533.359.pve-devel@lists.proxmox.com> (raw)
In-Reply-To: <94a5f198-ed41-4655-ba89-e1d9d9fc8cae@proxmox.com>
[-- Attachment #1: Type: message/rfc822, Size: 17118 bytes --]
From: Prashant Patil <Prashant.Gamepatil@veritas.com>
To: Fiona Ebner <f.ebner@proxmox.com>, Proxmox VE development discussion <pve-devel@lists.proxmox.com>, Thomas Lamprecht <t.lamprecht@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: Tue, 1 Apr 2025 11:54:50 +0000
Message-ID: <PH0PR20MB452007780D6055D15DFD565098AC2@PH0PR20MB4520.namprd20.prod.outlook.com>
Instead of making such multiple hops, can we have APIs exposed by Proxmox VE which we can use? E.g. API to get consistent snapshot-access to a virtual disk.
This way we have better control on monitoring jobs, API contracts are decided, it is also easy to troubleshoot issues on each side, etc. Let me know your thoughts on this. With Proxmox VE REST APIs, we already have several APIs for nodes/VMs management.
Regards
Prashant
-----Original Message-----
From: Fiona Ebner <f.ebner@proxmox.com>
Sent: 01 April 2025 04:49 PM
To: Prashant Patil <Prashant.Gamepatil@veritas.com>; Proxmox VE development discussion <pve-devel@lists.proxmox.com>; Thomas Lamprecht <t.lamprecht@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 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
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-01 11:55 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 [this message]
[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=mailman.415.1743508533.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