From: Mauro de Pascale <mauro.depascale.work@outlook.it>
To: "pve-devel@lists.proxmox.com" <pve-devel@lists.proxmox.com>
Cc: Mauro de Pascale <mauro.depascale.work@outlook.it>
Subject: [PATCH 0/2] RFC: manager: add direct VM backup export/import support
Date: Fri, 26 Jun 2026 16:43:56 +0000 [thread overview]
Message-ID: <20260626164354.44747-1-mauro.depascale.work@outlook.it> (raw)
From: Mauro de Pascale <mauro.depascale.work@outlook.it>
This RFC proposes a minimal implementation for direct VM backup export and
import workflows, avoiding the need for an intermediate storage location.
The goal is to explore a possible extension of Proxmox VE towards a workflow
already available in other virtualization platforms, where VM archives can be
transferred directly between the client and the host.
This series implements the manager side of the feature:
* add an API endpoint to stream vzdump output directly to the client;
* extend the web interface to export backups and upload VMA archives for
restore.
The implementation intentionally keeps the changes small and reuses existing
Proxmox components:
* vzdump is used as the existing backup generator;
* existing upload and restore mechanisms are reused for import;
* no new transfer protocol or storage layer is introduced.
The corresponding pve-storage change is required for the complete import
workflow, as it extends the existing upload path to handle VMA restore
operations.
This is an RFC and is intended to gather feedback about the approach rather
than propose a final feature implementation. Possible future improvements
could include richer progress reporting, improved error handling, additional
transfer workflows, or a dedicated API if this direction is considered useful.
Depends on:
- pve-storage RFC: storage: allow VM restore from uploaded VMA archives
Mauro de Pascale (2):
manager: add API endpoint for streamed VM backup export
manager: add GUI support for backup export and import
PVE/API2/VZDump.pm | 65 ++++++++++++++++++++++++++
www/manager6/Utils.js | 16 +++----
www/manager6/grid/BackupView.js | 24 +++++++++-
www/manager6/storage/BackupView.js | 29 +++++++++++-
www/manager6/window/Backup.js | 33 ++++++++++++-
www/manager6/window/UploadToStorage.js | 65 ++++++++++++++++++++++++--
6 files changed, 213 insertions(+), 19 deletions(-)
--
2.47.3
next reply other threads:[~2026-07-01 8:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-26 16:43 Mauro de Pascale [this message]
2026-06-26 16:43 ` [PATCH 1/2] manager: add API endpoint for streamed VM backup export Mauro de Pascale
2026-06-26 16:43 ` [PATCH 2/2] manager: add GUI support for backup export and import Mauro de Pascale
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=20260626164354.44747-1-mauro.depascale.work@outlook.it \
--to=mauro.depascale.work@outlook.it \
--cc=pve-devel@lists.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