summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorLingxian Kong <anlin.kong@gmail.com>2021-02-16 12:23:19 +1300
committerLingxian Kong <anlin.kong@gmail.com>2021-02-18 17:34:37 +0000
commit6fdf11ea7f5c77e83dd746fa33b7a354417aec08 (patch)
treed66f3528a6a36911dd55ce654b095aca8cceb3aa /doc
parent9c2e0bf3a0f1bc0b35a148174d8a4d2083f2b3c5 (diff)
downloadtrove-6fdf11ea7f5c77e83dd746fa33b7a354417aec08.tar.gz
Support to restore backup from remote location
In multi-region deployment with geo-replicated Swift, the user can restore a backup in one region by manually specifying the original backup data location created in another region. Change-Id: Iefef3bf969163af707935445bc23299400dc88c3
Diffstat (limited to 'doc')
-rw-r--r--doc/source/user/backup-db.rst18
1 files changed, 18 insertions, 0 deletions
diff --git a/doc/source/user/backup-db.rst b/doc/source/user/backup-db.rst
index 9a1a10e5..9aa5e13b 100644
--- a/doc/source/user/backup-db.rst
+++ b/doc/source/user/backup-db.rst
@@ -276,3 +276,21 @@ Create an incremental backup based on a parent backup:
| status | NEW |
| updated | 2014-03-19T14:09:13 |
+-------------+--------------------------------------+
+
+Restore backup from other regions
+---------------------------------
+
+Restoring backup from other regions were introduced in Wallaby,
+
+In multi-region deployment with geo-replicated Swift, the user is able to
+create a backup in one region using the backup data created in the others,
+which is useful in Disaster Recovery scenario. Instance ID is not required in
+this case when restoring backup, but the original backup data location (a swift
+object URL), the local datastore version and the backup data size are required.
+
+.. warning::
+
+ The restored backup is dependent on the original backup data, if the
+ original backup is deleted, the restored backup is invalid.
+
+TODO: Add CLI example once supported in python-troveclient.