From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: 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 2D20F91718 for ; Fri, 7 Oct 2022 13:55:22 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id EB39E254F0 for ; Fri, 7 Oct 2022 13:54:51 +0200 (CEST) Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com [94.136.29.106]) (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 firstgate.proxmox.com (Proxmox) with ESMTPS for ; Fri, 7 Oct 2022 13:54:50 +0200 (CEST) Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1]) by proxmox-new.maurer-it.com (Proxmox) with ESMTP id 8EADE44824 for ; Fri, 7 Oct 2022 13:54:50 +0200 (CEST) From: Dominik Csapak To: pbs-devel@lists.proxmox.com Date: Fri, 7 Oct 2022 13:54:45 +0200 Message-Id: <20221007115449.3562604-2-d.csapak@proxmox.com> X-Mailer: git-send-email 2.30.2 In-Reply-To: <20221007115449.3562604-1-d.csapak@proxmox.com> References: <20221007115449.3562604-1-d.csapak@proxmox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 AWL 0.068 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: [pbs-devel] [PATCH proxmox-backup v2 1/5] docs: add information about chunk order option for datastores X-BeenThere: pbs-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox Backup Server development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Oct 2022 11:55:22 -0000 Signed-off-by: Dominik Csapak --- docs/storage.rst | 23 +++++++++++++++++++++++ 1 file changed, 23 insertions(+) diff --git a/docs/storage.rst b/docs/storage.rst index ed4e28f2..1909bd84 100644 --- a/docs/storage.rst +++ b/docs/storage.rst @@ -315,3 +315,26 @@ There are a few per-datastore options: * :ref:`Notifications ` * :ref:`Maintenance Mode ` * Verification of incoming backups + +Tuning +^^^^^^ +There are some tuning related options for the datastore that are more advanced +and only available on the CLI: + +* ``chunk-order``: Chunk order for verify & tape backup: + + You can specify the order in which Proxmox Backup Server iterates the chunks + when doing a verify or backing up to tape. The two options are: + + - `inode` (default): Sorts the chunks by inode number of the filesystem before iterating + over them. This should be fine for most storages, especially spinning disks. + - `none` Iterates the chunks in the order they appear in the + index file (.fidx/.didx). While this might slow down iterating on many slow + storages, on very fast ones (for example: NVMEs) the collecting and sorting + can take more time than gained through the sorted iterating. + This option can be set with: + +.. code-block:: console + + # proxmox-backup-manager datastore update --tuning 'chunk-order=none' + -- 2.30.2