From eca1fabc95ffb1952c3e95b2bd63f73bec55f5f6 Mon Sep 17 00:00:00 2001 From: Andreja Tonev Date: Mon, 10 Nov 2025 21:20:49 +0100 Subject: [PATCH 1/2] old dir info --- pages/clustering/high-availability.mdx | 3 ++- pages/database-management/backup-and-restore.mdx | 5 +++-- 2 files changed, 5 insertions(+), 3 deletions(-) diff --git a/pages/clustering/high-availability.mdx b/pages/clustering/high-availability.mdx index 92307249d..f1f83f1a7 100644 --- a/pages/clustering/high-availability.mdx +++ b/pages/clustering/high-availability.mdx @@ -619,7 +619,8 @@ the cluster: synchronize its state. - The replica's old durability files will be preserved in a `.old` directory in `data_directory/snapshots` and `data_directory/wal` folders, allowing admins - to manually recover data if needed. + to manually recover data if needed. The `.old` directory is reused for subsequent + recovery operations, meaning only a single backup is maintained at any time. Depending on the replication mode used, there are different levels of data loss that can happen upon the failover. With the default `SYNC` replication mode, diff --git a/pages/database-management/backup-and-restore.mdx b/pages/database-management/backup-and-restore.mdx index 658827587..0632f7227 100644 --- a/pages/database-management/backup-and-restore.mdx +++ b/pages/database-management/backup-and-restore.mdx @@ -91,8 +91,9 @@ Use an absolute path when specifying the snapshot location. If you provide a rel to the Memgraph execution path. Before modifying the local data directory, Memgraph will move all existing WALs and snapshots to a hidden -directory in the format: -`.old_` +`.old` directory. This directory is reused for subsequent recovery operations, meaning only a single backup +is maintained at any time. Files already present in the `.old` directory will be deleted before moving +the current files, ensuring only the most recent backup is preserved. If the instance is not freshly started, add the `FORCE` flag to your command: From 3c8c74bbc0e69d0c6ae9605d28f40248e331f37c Mon Sep 17 00:00:00 2001 From: Matea Pesic <80577904+matea16@users.noreply.github.com> Date: Wed, 12 Nov 2025 12:18:12 +0100 Subject: [PATCH 2/2] Apply suggestions from code review --- pages/clustering/high-availability.mdx | 2 +- pages/database-management/backup-and-restore.mdx | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/pages/clustering/high-availability.mdx b/pages/clustering/high-availability.mdx index f1f83f1a7..2c8cf46dd 100644 --- a/pages/clustering/high-availability.mdx +++ b/pages/clustering/high-availability.mdx @@ -620,7 +620,7 @@ the cluster: - The replica's old durability files will be preserved in a `.old` directory in `data_directory/snapshots` and `data_directory/wal` folders, allowing admins to manually recover data if needed. The `.old` directory is reused for subsequent - recovery operations, meaning only a single backup is maintained at any time. + recovery operations, meaning **only a single backup is maintained at any time**. Depending on the replication mode used, there are different levels of data loss that can happen upon the failover. With the default `SYNC` replication mode, diff --git a/pages/database-management/backup-and-restore.mdx b/pages/database-management/backup-and-restore.mdx index 0632f7227..76eeb487e 100644 --- a/pages/database-management/backup-and-restore.mdx +++ b/pages/database-management/backup-and-restore.mdx @@ -91,8 +91,8 @@ Use an absolute path when specifying the snapshot location. If you provide a rel to the Memgraph execution path. Before modifying the local data directory, Memgraph will move all existing WALs and snapshots to a hidden -`.old` directory. This directory is reused for subsequent recovery operations, meaning only a single backup -is maintained at any time. Files already present in the `.old` directory will be deleted before moving +`.old` directory. This directory is reused for subsequent recovery operations, meaning **only a single backup +is maintained at any time**. Files already present in the `.old` directory will be deleted before moving the current files, ensuring only the most recent backup is preserved. If the instance is not freshly started, add the `FORCE` flag to your command: