Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion pages/clustering/high-availability.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -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,
Expand Down
5 changes: 3 additions & 2 deletions pages/database-management/backup-and-restore.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -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_<time-since-epoch>`
`.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:

Expand Down