From: Christian Ebner <c.ebner@proxmox.com>
To: Thomas Lamprecht <t.lamprecht@proxmox.com>,
Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>
Subject: Re: [pbs-devel] [PATCH docs 1/3] docs: explain the working principle of the change detection modes
Date: Tue, 26 Nov 2024 08:29:06 +0100 [thread overview]
Message-ID: <2f6448ed-e19d-4031-9636-2424c1e1bb75@proxmox.com> (raw)
In-Reply-To: <5e5a54b1-3d33-402f-8033-089e63590b43@proxmox.com>
On 11/25/24 22:09, Thomas Lamprecht wrote:
> Am 18.11.24 um 10:24 schrieb Christian Ebner:
>> Describe in more details how the different change detection modes
>> operate and give insights into the inner workings, especially for the
>> more complex `metadata` mode, which involves lookahead caching and
>> padding calculation for reused payload chunks.
>>
>> Suggested-by: Dietmar Maurer <dietmar@proxmox.com>
>> Signed-off-by: Christian Ebner <c.ebner@proxmox.com>
>
> it would be additionally good to describe why mtime, not ctime and when
> metadata detection can fail (if user/tools do bad things).
Agreed, will add more details on this as well.
>
> And for the overview it would be great to note why a data mode exists, as
> there can be some confusions from users interpreting this as three different
> ways to create the archive(s), not two ways to do that with two change detection
> modes.
> Could be also interesting to note that it works with older PBS in general beside
> some archive specific features like file-browsing.
>
Okay, will also add a short note that since the legacy mode and the two
other modes use different archive formats, they do not reuse chunks as
efficiently when using mixed modes on the same datastore.
> This mail is inspired a bit from the post I replied here:
>
> https://forum.proxmox.com/threads/proxmox-ve-8-3-released.157793/page-2#post-723212
_______________________________________________
pbs-devel mailing list
pbs-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel
next prev parent reply other threads:[~2024-11-26 7:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-18 9:24 [pbs-devel] [PATCH docs 0/3] extend documentation for change detection mode Christian Ebner
2024-11-18 9:24 ` [pbs-devel] [PATCH docs 1/3] docs: explain the working principle of the change detection modes Christian Ebner
2024-11-25 21:09 ` Thomas Lamprecht
2024-11-26 7:29 ` Christian Ebner [this message]
2024-11-26 9:22 ` Thomas Lamprecht
2024-11-26 9:45 ` Christian Ebner
2024-11-18 9:24 ` [pbs-devel] [PATCH docs 2/3] docs: reference technical change detection mode section for client Christian Ebner
2024-11-18 9:24 ` [pbs-devel] [PATCH docs 3/3] docs: client: fix formatting by using double ticks Christian Ebner
2024-11-18 15:04 ` Shannon Sterz
2024-11-21 16:04 ` [pbs-devel] applied-series: [PATCH docs 0/3] extend documentation for change detection mode Thomas Lamprecht
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=2f6448ed-e19d-4031-9636-2424c1e1bb75@proxmox.com \
--to=c.ebner@proxmox.com \
--cc=pbs-devel@lists.proxmox.com \
--cc=t.lamprecht@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