From cdb5a8115f4b565032dd67d3ce18ca6f51602553 Mon Sep 17 00:00:00 2001 From: Michele Cereda Date: Sat, 30 Aug 2025 11:32:06 +0200 Subject: [PATCH] fix(dblab): push on using multiple disks --- knowledge base/dblab engine.md | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/knowledge base/dblab engine.md b/knowledge base/dblab engine.md index 0b0736e..5ff9d0b 100644 --- a/knowledge base/dblab engine.md +++ b/knowledge base/dblab engine.md @@ -105,11 +105,11 @@ Refer [How to install DBLab manually]. Requirements: - [Docker Engine] must be installed, and usable by the user running DBLab. -- One or more extra disks or partitions to store all DBLab Engine's data. +- One or more extra disks, or partitions, to dedicate to DBLab Engine's data. > [!tip] > Prefer dedicating extra disks to the data for better performance.
- > The Engine can also use two or more disks or partitions to [automatically full refresh data without downtime]. + > The Engine can use multiple ZFS pools (or LVM volumes) to [automatically full refresh data without downtime].
@@ -388,12 +388,14 @@ DBLab Engine can use two or more ZFS pools or LVM logical volumes to perform an without downtime. > [!tip] -> Dedicate a disk or a partition to each pool or logical volume to avoid overloading a single disk. +> Prefer dedicating an entire disk to each pool or logical volume.
+> This avoids overloading a single disk when syncing, and prevents the whole data failing should a disk fail. ## Further readings - [Website] - [Codebase] +- [PostgreSQL] - [Documentation] - [`dblab`][dblab] @@ -417,7 +419,8 @@ without downtime. [dblab]: dblab.md [Docker engine]: docker.md -[PostgreSQL backup]: postgresql#backup +[PostgreSQL]: postgresql/README.md +[PostgreSQL backup]: postgresql/README.md#backup [ZFS]: zfs.md