Re: [pve-devel] [PATCH storage v4 09/27] plugin: introduce new_backup_provider() method

2025-04-04 Thread Andreas Rogge
h, a nice integration into PVE and additional features and capabilities of backup solution like yours. Sure. But we consider being inaccessible from the production system a feature. While many users might not need this, this is still what we are planning and preparing for. Best Regards, Andrea

Re: [pve-devel] [PATCH storage v4 09/27] plugin: introduce new_backup_provider() method

2025-04-04 Thread Andreas Rogge
don't have the data in a format that qemu-img can consume, things become complicated. Best Regards, Andreas -- Andreas Rogge andreas.ro...@bareos.com Bareos GmbH & Co. KG Phone: +49 221-630693-86 http://www.bareos.com Sitz der Gese

Re: [pve-devel] [PATCH storage v4 09/27] plugin: introduce new_backup_provider() method

2025-04-03 Thread Andreas Rogge
Am 03.04.25 um 09:24 schrieb Wolfgang Bumiller: On Wed, Apr 02, 2025 at 06:16:57PM +0200, Andreas Rogge wrote: Am 02.04.25 um 10:30 schrieb Wolfgang Bumiller: On Tue, Apr 01, 2025 at 08:21:30PM +0200, Thomas Lamprecht wrote: But I do wonder if - to reduce space-requirements for backing up

Re: [pve-devel] [PATCH storage v4 09/27] plugin: introduce new_backup_provider() method

2025-04-03 Thread Andreas Rogge
Am 02.04.25 um 10:33 schrieb Fiona Ebner: Am 01.04.25 um 20:21 schrieb Thomas Lamprecht: Am 01.04.25 um 18:02 schrieb Andreas Rogge: Um... that has nothing to do with what you provided when we take the backup. Is there a reason PVE cannot provide a writeable block device to restore to? Good

Re: [pve-devel] [PATCH storage v4 09/27] plugin: introduce new_backup_provider() method

2025-04-01 Thread Andreas Rogge
duction system is as strictly separated from the backup data as possible. While we understand how nice tight integration with PVE would be, we see this primarily as unnecessary attack surface. For a nicely integrated solution that can bring back last week's VM snapshot with a