From 9d6cfe2582951a89a6a105d9142ddfe8e1a6540f Mon Sep 17 00:00:00 2001 From: Michael Stanclift Date: Wed, 21 Oct 2020 20:10:51 -0500 Subject: [PATCH] Created Backup & Restore (markdown) --- Backup-&-Restore.md | 11 +++++++++++ 1 file changed, 11 insertions(+) create mode 100644 Backup-&-Restore.md diff --git a/Backup-&-Restore.md b/Backup-&-Restore.md new file mode 100644 index 0000000..5c10a73 --- /dev/null +++ b/Backup-&-Restore.md @@ -0,0 +1,11 @@ +### The Restore Function + +Gravity Sync can also `restore` the database on the secondary Pi-hole in the event you've overwritten it accidentally. This might happen in the above scenario where you've had your primary Pi-hole down for an extended period, made changes to the secondary, but perhaps didn't get a chance to perform a `push` of the changes back to the primary, before your automated sync ran. + +```bash +./gravity-sync.sh restore +``` + +This will copy your last `gravity.db.backup` and `custom.list.backup` to the running copy on the secondary Pi-hole. + +This function purposefully asks for user interaction to avoid being accidentally automated. \ No newline at end of file