From: Dominik Csapak <d.csapak@proxmox.com>
To: pbs-devel@lists.proxmox.com
Subject: [pbs-devel] [PATCH proxmox-backup 3/4] docs: technical overview: add section about snapshots
Date: Fri, 26 Aug 2022 10:09:20 +0200 [thread overview]
Message-ID: <20220826080921.1678212-3-d.csapak@proxmox.com> (raw)
In-Reply-To: <20220826080921.1678212-1-d.csapak@proxmox.com>
to clarify that snapshots get uploaded in an incremental manner, but
still represent a full backup.
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
---
docs/technical-overview.rst | 21 +++++++++++++++++++++
1 file changed, 21 insertions(+)
diff --git a/docs/technical-overview.rst b/docs/technical-overview.rst
index 59a59c11..f3e25b59 100644
--- a/docs/technical-overview.rst
+++ b/docs/technical-overview.rst
@@ -18,6 +18,27 @@ referenced by the indexes in a backup snapshot. This means that multiple
indexes can reference the same chunks, reducing the amount of space needed to
contain the data (even across backup snapshots).
+Snapshots
+---------
+
+A Snapshot is the collection of manifest, blobs and indexes that represent
+a backup. When a client creates a snapshot, it can upload blobs (single files
+which are not chunked, e.g. the client log), or one or more indexes
+(fixed or dynamic).
+
+When uploading an index, the client first has to read the source data, chunk it
+and send the data as chunks with their identifying checksum to the server.
+
+If there is a previous Snapshot in the backup group, the client can first
+download the chunk list of the previous Snapshot. If it detects a chunk that
+already exists on the server, it can send only the checksum instead of data
+and checksum. This way the actual upload of Snapshots is incremental while
+each Snapshot references all chunks and is thus a full backup.
+
+After uploading all data, the client has to signal to the server that the
+backup is finished. If that is not done before the connection closes, the
+server will remove the unfinished snapshot.
+
Chunks
------
--
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 ` Dominik Csapak [this message]
2022-08-26 8:09 ` [pbs-devel] [PATCH proxmox-backup 4/4] docs: faq: add better clarification on full/incremental Dominik Csapak
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-3-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