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 CF4A71FF17C
	for <inbox@lore.proxmox.com>; Wed,  2 Apr 2025 10:33:40 +0200 (CEST)
Received: from firstgate.proxmox.com (localhost [127.0.0.1])
	by firstgate.proxmox.com (Proxmox) with ESMTP id 282C4C58C;
	Wed,  2 Apr 2025 10:33:29 +0200 (CEST)
Message-ID: <324b156c-0b12-47e9-bffb-403a733c2b7d@proxmox.com>
Date: Wed, 2 Apr 2025 10:33:25 +0200
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
 Thomas Lamprecht <t.lamprecht@proxmox.com>,
 Andreas Rogge <andreas.rogge@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>
Content-Language: en-US
From: Fiona Ebner <f.ebner@proxmox.com>
In-Reply-To: <866f1cdd-780c-4012-b4fa-709ae1165891@proxmox.com>
X-SPAM-LEVEL: Spam detection results:  0
 AWL -0.038 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
 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: 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>

Am 01.04.25 um 20:21 schrieb Thomas Lamprecht:
> Am 01.04.25 um 18:02 schrieb Andreas Rogge:
>>> The backup provider gives a path to the disk image that will be
>>> restored. The path needs to be something 'qemu-img' can deal with,
>>> e.g. can also be an NBD URI or similar.
>> 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 idea! I'll look into adding a second restore mechanism with this
approach.

>> For Bareos this requirement would imply that we need an unpleasantly 
>> large staging area on the PVE node to facilitate a restore: As we can 
>> only stream the data we'd have to create a temporary disk image that PVE 
>> can then read. This sounds pretty inefficient - especially when 
>> comparing with qmrestore's ability to just read read from stdin.
> 
> Bareos could provide a NBD that is streamed directly from the backup
> repository, this should be quite efficient w.r.t. space usage.
> But as this was v4 and a few things changed, and I'm less involved as
> the actual author it might make more sense for her to answer this.

It's still mostly the same in the current version. But yes, you can
provide an NBD URI or path to a FUSE virtual file to avoid the need for
a temporary image.

Best Regards,
Fiona


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