From 74ffd64137f1a25db0681f53301fe19a7a5960f1 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Micha=C5=82=20Fr=C4=85ckiewicz?=
 <1836094+SystemZ@users.noreply.github.com>
Date: Tue, 20 Feb 2024 20:18:18 +0100
Subject: [PATCH] explain better what happens when saving and loading metadata,
 explain one example case when to do it

---
 Filer-Stores.md | 7 +++++--
 1 file changed, 5 insertions(+), 2 deletions(-)

diff --git a/Filer-Stores.md b/Filer-Stores.md
index 38e130a..2c67698 100644
--- a/Filer-Stores.md
+++ b/Filer-Stores.md
@@ -30,12 +30,14 @@ The Filer Store persists all file metadata and directory information.
 | TiKV         | O(logN)| unlimited | Distributed, Fast     |Atomic|Yes| Yes| Scalable. High Availability. Need to manually build. |
 
 #### Switching between different Stores
-It is easy to switch between different filer stores.
+It is easy to switch between different filer stores.  
+This is useful if you started with embedded DB and want to move to distributed one or in reverse.
 
 For example:
 ```sh
 
-# first save current filer meta data
+# make sure you don't create or modify files in filer before this to maintain consistency of metadata
+# save current filer meta data to local disk
 
 $ weed shell
 > fs.cd /
@@ -45,6 +47,7 @@ total 65 directories, 292 files
 meta data for http://localhost:8888/ is saved to localhost-8888-20190417-005421.meta
 > exit
 
+# you can turn off old filer if you have metadata saved to file
 # now switch to a new filer, and load the previously saved metadata
 $ weed shell
 > fs.meta.load localhost-8888-20190417-005421.meta