From 3f42c51a573cde11b2b018c42caede573e1d4b2b Mon Sep 17 00:00:00 2001 From: Chris McKee Date: Mon, 29 Apr 2019 11:39:50 +0100 Subject: [PATCH] Split the rancher ha-restoration into local / s3 based and add versions. Add process to restore from s3 with note on state file / cluster file. --- .../restorations/ha-restoration/_index.md | 30 ++++++++++++++++++- 1 file changed, 29 insertions(+), 1 deletion(-) diff --git a/content/rancher/v2.x/en/backups/restorations/ha-restoration/_index.md b/content/rancher/v2.x/en/backups/restorations/ha-restoration/_index.md index 94093b8a135..e1d0e4bf522 100644 --- a/content/rancher/v2.x/en/backups/restorations/ha-restoration/_index.md +++ b/content/rancher/v2.x/en/backups/restorations/ha-restoration/_index.md @@ -33,10 +33,38 @@ We recommend that you start with fresh nodes and a clean state. Alternatively yo ### 2. Place Snapshot and PKI Bundle +**Local Snapshots** + Pick a one of the clean nodes. That node will be the "target node" for the initial restore. Place the snapshot and PKI certificate bundle files in the `/opt/rke/etcd-snapshots` directory on the "target node". * Snapshot - `.db` -* PKI Bundle - `pki.bundle.tar.gz` +* PKI Bundle - `pki.bundle.tar.gz` *(Pre RKE 0.2.0 only; after 0.2 you should have an cluster.rkestate file)* + +***Continue to step 3*** + + + +**Remote Snapshots** (rancher 2.1 / rke 0.2.0 onwards) + + +Ensuring your `cluster.rkestate` file is present, run rke restore from s3. + +```shell +rke etcd snapshot-restore --config rancher-cluster-restore.yml \ +--name snap-shot-name.db \ +--s3 --access-key KEY --secret-key SECRET \ +--bucket-name my-rancher-etcd-backup-bucket \ +--s3-endpoint s3.amazonaws.com \ +--region eu-west-2 +``` + +Once the process has completed, if rancher has been installed via helm, the UI will load (can take a few minutes). + +At this point the restoration is complete. + +> Note: At this point it is a good idea to ensure your `kube_config_cluster.yml` and `cluster.rkestate` are backed up and preserved for any future maintenance. + + ### 3. Configure RKE