gitlab-com-seaweedfs/seaweedfs
1
0
Fork 0
mirror of https://github.com/seaweedfs/seaweedfs.git synced 2024-01-19 02:48:24 +00:00
Code Issues Projects Releases Wiki Activity

Updated Async Backup (markdown)

Chris Lu 2021-03-01 21:43:51 -08:00
parent 2171d11cc4
commit f75a81d0bf
1 changed files with 11 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

12
Async-Backup.md

@ -51,7 +51,17 @@ is_incremental = false
1. Make sure the `replication.toml` is in place. 1. Make sure the `replication.toml` is in place.
1. Start the backup by running `weed filer.backup`. 1. Start the backup by running `weed filer.backup`.
# Incremental Mode Unless interrupted, the `weed filer.backup` will run continuously and keep retrying if any error happens.
The `weed filer.backup` process can also be stopped at any time. The current backup progress, which is the "offset" for normal message queues, is stored on filer with the key as `<sink_name, sink_folder>`. So to resume, you can just restart, or even start from another server, as long as you have the same `replication.toml` file
# Backup Strategies
There are 2 backup strategies supported as of now:
1. Continuously replicated changes. All the content are stored with the same directory structure as the source, but in a remote machine or a cloud vendor.
2.
## Incremental Mode
If `is_incremental = true`, all the files are backed up under the `YYYY-MM-DD` directories, which the timestamps are based on modified time. If `is_incremental = true`, all the files are backed up under the `YYYY-MM-DD` directories, which the timestamps are based on modified time.
So So
* Each date directory contains all new and updated files. * Each date directory contains all new and updated files.