From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <pve-devel-bounces@lists.proxmox.com>
Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68])
	by lore.proxmox.com (Postfix) with ESMTPS id 337081FF189
	for <inbox@lore.proxmox.com>; Fri,  4 Apr 2025 09:16:17 +0200 (CEST)
Received: from firstgate.proxmox.com (localhost [127.0.0.1])
	by firstgate.proxmox.com (Proxmox) with ESMTP id 45B6FF906;
	Fri,  4 Apr 2025 09:16:03 +0200 (CEST)
Date: Fri, 4 Apr 2025 09:15:29 +0200 (CEST)
From: =?UTF-8?Q?Fabian_Gr=C3=BCnbichler?= <f.gruenbichler@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
 Andreas Rogge <andreas.rogge@bareos.com>,
 Wolfgang Bumiller <w.bumiller@proxmox.com>
Message-ID: <86122982.5994.1743750929479@webmail.proxmox.com>
In-Reply-To: <793a9b31-f0eb-4b21-af24-54bcef808167@bareos.com>
References: <20241114150754.374376-1-f.ebner@proxmox.com>
 <20241114150754.374376-10-f.ebner@proxmox.com>
 <66969dc5-7587-46fc-8b36-8ecf0d5d744a@bareos.com>
 <866f1cdd-780c-4012-b4fa-709ae1165891@proxmox.com>
 <dktagxdpeqlvvmqhv2hr5n3dxmdh7nfyctluo64mwqgsimread@jbjcwstbk5fn>
 <c79787cf-4cc7-4ac6-9e8f-f864f77c1812@bareos.com>
 <ey5nze36xsp7iaipishhlsvxo5xyllyvze2sevxutbcttofyye@bxzkiqxcm2no>
 <793a9b31-f0eb-4b21-af24-54bcef808167@bareos.com>
MIME-Version: 1.0
X-Priority: 3
Importance: Normal
X-Mailer: Open-Xchange Mailer v7.10.6-Rev75
X-Originating-Client: open-xchange-appsuite
X-SPAM-LEVEL: Spam detection results:  0
 AWL 0.047 Adjusted score from AWL reputation of From: address
 BAYES_00                 -1.9 Bayes spam probability is 0 to 1%
 DMARC_MISSING             0.1 Missing DMARC policy
 KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment
 RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to
 Validity was blocked. See
 https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more
 information.
 RCVD_IN_VALIDITY_RPBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to
 Validity was blocked. See
 https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more
 information.
 RCVD_IN_VALIDITY_SAFE_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to
 Validity was blocked. See
 https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more
 information.
 SPF_HELO_NONE           0.001 SPF: HELO does not publish an SPF Record
 SPF_PASS               -0.001 SPF: sender matches SPF record
Subject: Re: [pve-devel] [PATCH storage v4 09/27] plugin: introduce
 new_backup_provider() method
X-BeenThere: pve-devel@lists.proxmox.com
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Proxmox VE development discussion <pve-devel.lists.proxmox.com>
List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/pve-devel>, 
 <mailto:pve-devel-request@lists.proxmox.com?subject=unsubscribe>
List-Archive: <http://lists.proxmox.com/pipermail/pve-devel/>
List-Post: <mailto:pve-devel@lists.proxmox.com>
List-Help: <mailto:pve-devel-request@lists.proxmox.com?subject=help>
List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel>, 
 <mailto:pve-devel-request@lists.proxmox.com?subject=subscribe>
Reply-To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Cc: Thomas Lamprecht <t.lamprecht@proxmox.com>,
 Philipp Storz <philipp.storz@bareos.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: pve-devel-bounces@lists.proxmox.com
Sender: "pve-devel" <pve-devel-bounces@lists.proxmox.com>


> Andreas Rogge <andreas.rogge@bareos.com> hat am 03.04.2025 18:08 CEST geschrieben:
> Am 03.04.25 um 09:24 schrieb Wolfgang Bumiller:
> > I *believe* `qemu-nbd` should be able to bind all the storage types we
> > want to restore to to /dev/nbdXY devices, which would give the provider
> > a bunch of block devices to write to in whichever way they want to, so
> > the provider would then only need to figure out how to receive the data
> > and forward that to the devices.
> > We'll need to try.
> 
> That's pretty much what I had hoped for.

just because that recently came up in another context - there is also
qemu-storage-daemon which can export anything qemu can read/write via
different interfaces - NBD, but also a vhost-user-blk device via a socket,
or a "fake raw file" provided via FUSE ;)

given the annoying properties of NBD on the kernel side (Fiona can tell
you more ;)), we might want to check out those as well. not sure how much
performance overhead the FUSE variant has, it would probably be the easiest
to implement considering both our and the backup provider end.

of course, if you already have an NBD client implementation and just need
the export data without it being "bound" on the PVE side, that would also
be fairly simple ;) same applies to vhost-user-blk - in both cases, if you
already know how to write to such a "block device", then PVE would just need to
- allocate the image
- export it via qemu-storage-daemon
- tell you where the socket/NBD server is/make it accessible


_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel