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 [IPv6:2a01:7e0:0:424::9])
by lore.proxmox.com (Postfix) with ESMTPS id ACAC91FF16E
for <inbox@lore.proxmox.com>; Mon, 29 Jul 2024 22:49:49 +0200 (CEST)
Received: from firstgate.proxmox.com (localhost [127.0.0.1])
by firstgate.proxmox.com (Proxmox) with ESMTP id A8F8C32409;
Mon, 29 Jul 2024 22:49:48 +0200 (CEST)
In-Reply-To: <1137775171.7131.1722093632719@webmail.proxmox.com>
Date: Sat, 27 Jul 2024 16:36:14 -0400
References: <mailman.0.1722092937.302.pve-devel@lists.proxmox.com>
<1137775171.7131.1722093632719@webmail.proxmox.com>
To: Dietmar Maurer <dietmar@proxmox.com>
X-Mailman-Approved-At: Mon, 29 Jul 2024 22:49:46 +0200
MIME-Version: 1.0
Message-ID: <mailman.36.1722286187.302.pve-devel@lists.proxmox.com>
List-Id: Proxmox VE development discussion <pve-devel.lists.proxmox.com>
List-Post: <mailto:pve-devel@lists.proxmox.com>
From: Jonathan Nicklin via pve-devel <pve-devel@lists.proxmox.com>
Precedence: list
Cc: Jonathan Nicklin <jnicklin@blockbridge.com>,
Proxmox VE development discussion <pve-devel@lists.proxmox.com>
X-Mailman-Version: 2.1.29
X-BeenThere: pve-devel@lists.proxmox.com
List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel>,
<mailto:pve-devel-request@lists.proxmox.com?subject=subscribe>
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/>
Reply-To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
List-Help: <mailto:pve-devel-request@lists.proxmox.com?subject=help>
Subject: Re: [pve-devel] [RFC qemu/storage/qemu-server/container/manager
00/23] backup provider API
Content-Type: multipart/mixed; boundary="===============0088925907952590080=="
Errors-To: pve-devel-bounces@lists.proxmox.com
Sender: "pve-devel" <pve-devel-bounces@lists.proxmox.com>
--===============0088925907952590080==
Content-Type: message/rfc822
Content-Disposition: inline
Return-Path: <jnicklin@blockbridge.com>
X-Original-To: pve-devel@lists.proxmox.com
Delivered-To: pve-devel@lists.proxmox.com
Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68])
(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
key-exchange X25519 server-signature RSA-PSS (2048 bits))
(No client certificate requested)
by lists.proxmox.com (Postfix) with ESMTPS id AB251C0324
for <pve-devel@lists.proxmox.com>; Sat, 27 Jul 2024 22:36:24 +0200 (CEST)
Received: from firstgate.proxmox.com (localhost [127.0.0.1])
by firstgate.proxmox.com (Proxmox) with ESMTP id 8783E5020
for <pve-devel@lists.proxmox.com>; Sat, 27 Jul 2024 22:36:24 +0200 (CEST)
Received: from mail-qv1-xf30.google.com (mail-qv1-xf30.google.com [IPv6:2607:f8b0:4864:20::f30])
(using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits)
key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256)
(No client certificate requested)
by firstgate.proxmox.com (Proxmox) with ESMTPS
for <pve-devel@lists.proxmox.com>; Sat, 27 Jul 2024 22:36:23 +0200 (CEST)
Received: by mail-qv1-xf30.google.com with SMTP id 6a1803df08f44-6b796667348so15262796d6.0
for <pve-devel@lists.proxmox.com>; Sat, 27 Jul 2024 13:36:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=blockbridge.com; s=google; t=1722112576; x=1722717376; darn=lists.proxmox.com;
h=to:references:message-id:content-transfer-encoding:cc:date
:in-reply-to:from:subject:mime-version:from:to:cc:subject:date
:message-id:reply-to;
bh=QJA64KL134V1u5rEyAbb3cUZ64zV4FS1UWgMgwe56wE=;
b=Cw8rFZ25Ievs7H8gZlpkRAmf9dLjB3P3VXaj4ab4W7L2KjPIcilR8bVA44WyuxYy1r
riKYPhKslH1VsrjwxFbTidzwX6s5G4/jKuouA5BqA7PEe5lJeR5b2eEbqA06aNGIO0ho
qb/IgQIrkAQEMag0Cg5IKuUPRybULuIInmouO0ZF0IoHlmEMvw02D2xTSUtoAWnvyvM5
3t3SQswWmOM1ukRAtuFwy/kSht9eLhOmx2k1EcuLZMB9rESaszsP9QCnWSnKJuD/lRbL
olmCergPlX/hDcJKrEGFIlYMP7CAj3RfvlCPnP6za4Ni7pGR6nBTkbGE+DRzhcb5WDRX
c3AQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20230601; t=1722112576; x=1722717376;
h=to:references:message-id:content-transfer-encoding:cc:date
:in-reply-to:from:subject:mime-version:x-gm-message-state:from:to:cc
:subject:date:message-id:reply-to;
bh=QJA64KL134V1u5rEyAbb3cUZ64zV4FS1UWgMgwe56wE=;
b=dRhVk5mpUf4WV9M++8NupH+n0pzOdz9+35UyK3qGXeC/HeJrFtz3i9GQQVpVQMalwn
2TPTIILEoDd0+qJtne2Mi1uriPwglrfwiEKhMSVacuiKiCT+O7d70SRph44FNZcJzCXJ
Ccwgqvig9M2gQBHgntyLbyAWy66/Adq3S06rrt7Mu8JJhvghJJA4GjQ2gzkBQWpwAj6E
OMJkASLwbBWY8++meUfWezZnPGqQu8W7NIqQYODtnbgUAP20JRl9OhLLKiY61NgAsO9m
3maBaMzIM5HSWGG3onewlEYaRlRMtK4zsZ0Y1v/YwPsl5KIvaqQymfiZE4tCQt+CzkQf
U/pQ==
X-Gm-Message-State: AOJu0YyTQzbhuQnxRm1wmuvhmXU6wr6xvnqcBfwRy763aAL0c5Yfmafu
4VReZdVIYNNW/FS7mcf4khLE66sJEgkWfWcvEoHCgt6Bsa1GCSDIAxhvDWsDYqVrZBOiPXzl80l
v
X-Google-Smtp-Source: AGHT+IGiVUufat8YZVshdeqQqMaMjrhUHHQy6f7TzcA4hD19uNuNq9BLRF+mdRo68ukx660bJ441pA==
X-Received: by 2002:a05:6214:124a:b0:6b7:9554:7f20 with SMTP id 6a1803df08f44-6bb56319ca0mr64384186d6.15.1722112576017;
Sat, 27 Jul 2024 13:36:16 -0700 (PDT)
Received: from smtpclient.apple (pool-108-7-52-138.bstnma.fios.verizon.net. [108.7.52.138])
by smtp.gmail.com with ESMTPSA id 6a1803df08f44-6bb3f8d81e2sm33260986d6.25.2024.07.27.13.36.15
(version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128);
Sat, 27 Jul 2024 13:36:15 -0700 (PDT)
Content-Type: text/plain;
charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.20.0.1.32\))
Subject: Re: [pve-devel] [RFC qemu/storage/qemu-server/container/manager
00/23] backup provider API
From: Jonathan Nicklin <jnicklin@blockbridge.com>
X-Priority: 3
In-Reply-To: <1137775171.7131.1722093632719@webmail.proxmox.com>
Date: Sat, 27 Jul 2024 16:36:14 -0400
Cc: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Content-Transfer-Encoding: 7bit
Message-Id: <E6295C3B-9E33-47C2-BC0E-9CEC701A2716@blockbridge.com>
References: <mailman.0.1722092937.302.pve-devel@lists.proxmox.com>
<1137775171.7131.1722093632719@webmail.proxmox.com>
To: Dietmar Maurer <dietmar@proxmox.com>
X-Mailer: Apple Mail (2.3693.20.0.1.32)
X-SPAM-LEVEL: Spam detection results: 0
AWL 0.459 Adjusted score from AWL reputation of From: address
BAYES_00 -1.9 Bayes spam probability is 0 to 1%
DKIM_SIGNED 0.1 Message has a DKIM or DK signature, not necessarily valid
DKIM_VALID -0.1 Message has at least one valid DKIM or DK signature
DKIM_VALID_AU -0.1 Message has a valid DKIM or DK signature from author's domain
DKIM_VALID_EF -0.1 Message has a valid DKIM or DK signature from envelope-from domain
DMARC_PASS -0.1 DMARC pass policy
RCVD_IN_DNSWL_NONE -0.0001 Sender listed at https://www.dnswl.org/, no trust
SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record
SPF_PASS -0.001 SPF: sender matches SPF record
URIBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [blockbridge.com]
X-Mailman-Approved-At: Mon, 29 Jul 2024 22:49:46 +0200
> On Jul 27, 2024, at 11:20 AM, Dietmar Maurer <dietmar@proxmox.com> wrote:
>
>> Would adding support for offloading incremental difference detection
>> to the underlying storage be feasible with the API updates? The QEMU
>> bitmap strategy works for all storage devices but is far from
>> optimal.
>
> Sorry, but why do you think this is far from optimal?
>
The biggest issue we see reported related to QEMU bitmaps is
persistence. The lack of durability results in unpredictable backup
behavior at scale. If a host, rack, or data center loses power, you're
in for a full backup cycle. Even if several VMs are powered off for
some reason, it can be a nuisance. Several storage solutions can
generate the incremental difference bitmaps from durable sources,
eliminating the issue.
That said, using bitmaps or alternative sources for the incremental
differences is slightly orthogonal to the end goal. The real
improvement we're hoping for is the ability to eliminate backup
traffic on the client.
Today, I believe the client is reading the data and pushing it to
PBS. In the case of CEPH, wouldn't this involve sourcing data from
multiple nodes and then sending it to PBS? Wouldn't it be more
efficient for PBS to read it directly from storage? In the case of
centralized storage, we'd like to eliminate the client load
completely, having PBS ingest increment differences directly from
storage without passing through the client.
--===============0088925907952590080==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
--===============0088925907952590080==--