Updated Async Filer Metadata Backup (markdown)

Chris Lu 2021-06-06 19:52:07 -07:00
parent 5a4c15984f
commit d09850e42a

@ -11,17 +11,33 @@ With `-peers` option, if the filers are not sharing the same filer metadata stor
See https://github.com/chrislusf/seaweedfs/wiki/Filer-Store-Replication#file-store-replication
# Async filer metadata backup to a remote store
# Async filer metadata backup to a different store
We can also continuously backup filer metadata to a remote store, without running a filer instance.
We can also continuously backup filer metadata to a different store, without running a filer instance.
```
Metadata Changes
Filer --------------------> `weed filer.meta.backup` ---> Remote Store(LevelDB/RocksDB/
Filer --------------------> `weed filer.meta.backup` ---> A backup store(LevelDB/RocksDB/
Mysql/Postgres/
Redis/Cassanra/...)
```
Just need to configure the remote store the same way as `filer.toml`.
Just need to configure the backup store the same way as `filer.toml`.
`weed filer.meta.backup` can be stopped and resumed. The metadata backup progress is tracked in the remote store itself. So you can pause/resume any time, and even resume from a separate machine.
`weed filer.meta.backup` can be stopped and resumed. The metadata backup progress is tracked in the backup store itself. So you can pause/resume any time.
It is worth noting that the remote store can be different from the source filer store. E.g., you can use a cheaper on disk LevelDB as a remote store to backup Redis.
It is worth noting that the backup store can be different from the source filer store. E.g., you can use a cheaper on disk LevelDB as a remote store to backup Redis.
```
Metadata Changes
Filer --------------------> `weed filer.meta.backup` ---> A backup store(LevelDB)
on Redis
```
You can even do this:
```
Metadata Changes sqlite streaming
Filer --------------------> `weed filer.meta.backup` ---> A backup store(Sqlite) ------------------> S3
on Redis
```