mirror of
https://git.proxmox.com/git/proxmox-backup
synced 2025-10-04 19:58:14 +00:00
docs: add information about chunk order option for datastores
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
This commit is contained in:
parent
f963bc0c81
commit
d2c79c54c2
@ -315,3 +315,26 @@ There are a few per-datastore options:
|
|||||||
* :ref:`Notifications <maintenance_notification>`
|
* :ref:`Notifications <maintenance_notification>`
|
||||||
* :ref:`Maintenance Mode <maintenance_mode>`
|
* :ref:`Maintenance Mode <maintenance_mode>`
|
||||||
* Verification of incoming backups
|
* 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 <storename> --tuning 'chunk-order=none'
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user