From f75a81d0bf81fa5eb512fbe6e02f6a32b2d9e7e4 Mon Sep 17 00:00:00 2001 From: Chris Lu Date: Mon, 1 Mar 2021 21:43:51 -0800 Subject: [PATCH] Updated Async Backup (markdown) --- Async-Backup.md | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/Async-Backup.md b/Async-Backup.md index 4394eb9..d0acc60 100644 --- a/Async-Backup.md +++ b/Async-Backup.md @@ -51,7 +51,17 @@ is_incremental = false 1. Make sure the `replication.toml` is in place. 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 ``. 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. So * Each date directory contains all new and updated files.