From 83b0be5ae5abecd2076cab8b7ab2a84e9756034a Mon Sep 17 00:00:00 2001 From: EuAndreh Date: Tue, 28 May 2019 00:46:24 -0300 Subject: Add backup routing before possibly tearing down machine Create a new backup entry before running =terraform apply=, which may (or may not) destroy the current machine. This shouldn't be an issue for the backup itself, since all of the data should be stored in a separate Block Storage Volume, but we can take advantage of the sevices already needing to be taken down in order to perform a full backup of the data. --- TODOs.org | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) (limited to 'TODOs.org') diff --git a/TODOs.org b/TODOs.org index 2f8d3ba..596793e 100644 --- a/TODOs.org +++ b/TODOs.org @@ -27,7 +27,8 @@ Put it in an environment variable? Done by appending to content of =~/.ssh/config=. **** DOING Automate deployment with Terraform and deployment scripts **** NEXT Use DigitalOcean's Floating IP in front of the droplet -**** TODO Backup data during deployments +**** DONE Backup data during deployments +CLOSED: [2019-05-28 Tue 00:48] Is this approach feasible? Will it make the deployment take too much longer? What are the alternatives? Initial sketch of the backup commands: @@ -36,6 +37,8 @@ rsync --verbose --progress --stats --update --recursive "$HOME/backups/" "$RSYNC borg create -svp -C lzma,6 "~/borgbackup::{hostname}-{now}-${VPS_COMMIT_SHA} ${VOLUME_HOME}" rsync --verbose --progress --stats --update --recursive "$RSYNC_REMOTE" "$HOME/borgbackups/" #+END_SOURCE + +Implemented with help from https://jstaf.github.io/2018/03/12/backups-with-borg-rsync.html **** TODO Test provisioning DNS entries with other DNS registrars **** DONE Namecheap whitelist IP limitation CLOSED: [2019-05-26 Sun 17:14] -- cgit v1.3