Proxmox Backup API

[Dennis Klochko]

Hi Thomas,

Thank you for the extra information, that's very helpful.
Another question is about versioning of a plugin vs new Proxmox versions -
in what cases should the plugin be updated?

On Wed, Jul 2, 2025 at 11:17 PM Thomas Lamprecht <t.lamprecht at proxmox.com>
wrote:

> Hello!
>
> Am 25.06.25 um 04:57 schrieb Dennis Klochko:
> > Please share what the official backup API for Proxmox is?
>
> The basic idea is that you create a specialized storage plugin basing
> of our backup provider one, while the base skeleton needs to be in Perl,
> the actual code talking with your backup solution can be anything you
> like and either interface with the perl plugin with some FFI or IPC
> layer.
>
> The base plugin has some [pod] (perl doc format) you can check out, and
> there is now also a git repo that includes [example plugins].
>
> If you have any specific questions feel free to ask them here, we're
> in process of expanding examples and docs, whichs is part of the reason
> why my reply comes a bit late; I wanted to finish preparing the first
> publication of the example git repo.
>
> [pod]:
> https://git.proxmox.com/?p=pve-storage.git;a=blob;f=src/PVE/BackupProvider/Plugin/Base.pm
>
> [example plugins]:
> https://git.proxmox.com/?p=pve-storage-plugin-examples.git;a=summary
>
> regards
>  Thomas
>
>

-- 

Sincere regards,

*Dennis*

*_____________________________________*

Dennis

Dennis Klochko | Technology Alliance Program Manager | NAKIVO Inc. |
www.nakivo.com

E-mail: dennis.klochko at nakivo.com


*Dennis Klochko *| Technical Alliance Program Manager | Nakivo, Inc.|
*www.nakivo.com
<http://www.nakivo.com/>*

*E-mail*: dennis.klochko at nakivo.com

This email and any files transmitted with it are confidential and intended
solely for the use of the individual or entity to whom they are addressed.

If you have received this email in error or would like to prevent receipt
of similar messages in the future, please let the author know via reply and
delete it from your system. Note that any views or opinions presented in
this email are solely those of the author and do not necessarily represent
those of the company.