From: Dominik Csapak <d.csapak@proxmox.com>
To: pbs-devel@lists.proxmox.com
Subject: [pbs-devel] [PATCH proxmox-backup 4/4] docs: faq: add better clarification on full/incremental
Date: Fri, 26 Aug 2022 10:09:21 +0200 [thread overview]
Message-ID: <20220826080921.1678212-4-d.csapak@proxmox.com> (raw)
In-Reply-To: <20220826080921.1678212-1-d.csapak@proxmox.com>
and add a link to the technical overview
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
---
docs/faq.rst | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/docs/faq.rst b/docs/faq.rst
index 874b081a..4ff68178 100644
--- a/docs/faq.rst
+++ b/docs/faq.rst
@@ -66,9 +66,11 @@ be able to read the data.
:ref:`backup client encryption section <client_encryption>`.
-Is the backup incremental/deduplicated?
+Is the backup incremental/deduplicated/full?
---------------------------------------
With Proxmox Backup Server, backups are sent incrementally to the server, and
data is then deduplicated on the server. This minimizes both the storage
-consumed and the impact on the network.
+consumed and the impact on the network. Each backup still references all
+data and such is a full backup. For details see the
+:ref:`Technical Overview <tech_design_overview>`
--
2.30.2
next prev parent reply other threads:[~2022-08-26 8:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-26 8:09 [pbs-devel] [PATCH proxmox-backup 1/4] add missing proxmox-sys features for client/file-restore Dominik Csapak
2022-08-26 8:09 ` [pbs-devel] [PATCH proxmox-backup 2/4] docs: terminology: update snapshot uniqueness for namespaces Dominik Csapak
2022-08-26 8:09 ` [pbs-devel] [PATCH proxmox-backup 3/4] docs: technical overview: add section about snapshots Dominik Csapak
2022-08-26 8:09 ` Dominik Csapak [this message]
2022-09-12 8:50 ` [pbs-devel] applied-series: [PATCH proxmox-backup 1/4] add missing proxmox-sys features for client/file-restore Fabian Grünbichler
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=20220826080921.1678212-4-d.csapak@proxmox.com \
--to=d.csapak@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