From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>,
Christian Ebner <c.ebner@proxmox.com>
Subject: [pbs-devel] applied: [PATCH proxmox-backup 1/1] docs: explain some further caveats of the change detection modes
Date: Tue, 26 Nov 2024 12:24:49 +0100 [thread overview]
Message-ID: <51c2fda9-f509-46b0-9162-c34c3057ca84@proxmox.com> (raw)
In-Reply-To: <20241126085502.77438-1-c.ebner@proxmox.com>
Am 26.11.24 um 09:55 schrieb Christian Ebner:
> Explain that the change detection mode data makes sure that no files
> are considered reusable, even if their metadata might match and that
> the use of ctime and inode number is not possible for detection of
> unchanged files if the filesystem was synced to a temporary location,
> therefore the mtime and size are used for detection.
>
> Also note the reduced deduplication when storing snaphshots with
> mixed archive formats on the same datastore.
>
> Further, mention the backwards compatibility to older version of the
> Proxmox Backup Server.
>
> Suggested-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
> Signed-off-by: Christian Ebner <c.ebner@proxmox.com>
> ---
> docs/technical-overview.rst | 36 +++++++++++++++++++++++++++++++++---
> 1 file changed, 33 insertions(+), 3 deletions(-)
>
>
applied, thanks!
_______________________________________________
pbs-devel mailing list
pbs-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel
prev parent reply other threads:[~2024-11-26 11:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-26 8:55 [pbs-devel] " Christian Ebner
2024-11-26 11:24 ` Thomas Lamprecht [this message]
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=51c2fda9-f509-46b0-9162-c34c3057ca84@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=c.ebner@proxmox.com \
--cc=pbs-devel@lists.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