From 66a20e0ec76a1b3fc63705ab4d603d38b19d22c5 Mon Sep 17 00:00:00 2001 From: Mark Bishop Date: Thu, 24 May 2018 11:50:13 -0700 Subject: [PATCH] retitled etcd back to ha backup and restore per Sheng --- .../v2.x/en/installation/after-installation/_index.md | 5 ----- .../en/installation/backups-and-restoration/_index.md | 5 +++++ .../ha-backup-and-restoration}/_index.md | 10 +++++----- .../single-node-backup-and-restoration/_index.md | 0 4 files changed, 10 insertions(+), 10 deletions(-) delete mode 100644 content/rancher/v2.x/en/installation/after-installation/_index.md create mode 100644 content/rancher/v2.x/en/installation/backups-and-restoration/_index.md rename content/rancher/v2.x/en/installation/{after-installation/etcd-backup-and-restoration => backups-and-restoration/ha-backup-and-restoration}/_index.md (93%) rename content/rancher/v2.x/en/installation/{after-installation => backups-and-restoration}/single-node-backup-and-restoration/_index.md (100%) diff --git a/content/rancher/v2.x/en/installation/after-installation/_index.md b/content/rancher/v2.x/en/installation/after-installation/_index.md deleted file mode 100644 index f9935d7a4f5..00000000000 --- a/content/rancher/v2.x/en/installation/after-installation/_index.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: After Installation -weight: 360 ---- -This section contains information about how to perform system maintenance on your Rancher install. diff --git a/content/rancher/v2.x/en/installation/backups-and-restoration/_index.md b/content/rancher/v2.x/en/installation/backups-and-restoration/_index.md new file mode 100644 index 00000000000..592aed08f7b --- /dev/null +++ b/content/rancher/v2.x/en/installation/backups-and-restoration/_index.md @@ -0,0 +1,5 @@ +--- +title: Backups and Restoration +weight: 360 +--- +This section contains information about how to create backups of your Rancher data and how to restore them in a disaster scenario. diff --git a/content/rancher/v2.x/en/installation/after-installation/etcd-backup-and-restoration/_index.md b/content/rancher/v2.x/en/installation/backups-and-restoration/ha-backup-and-restoration/_index.md similarity index 93% rename from content/rancher/v2.x/en/installation/after-installation/etcd-backup-and-restoration/_index.md rename to content/rancher/v2.x/en/installation/backups-and-restoration/ha-backup-and-restoration/_index.md index 63d14cbef4f..110e5836fbd 100644 --- a/content/rancher/v2.x/en/installation/after-installation/etcd-backup-and-restoration/_index.md +++ b/content/rancher/v2.x/en/installation/backups-and-restoration/ha-backup-and-restoration/_index.md @@ -1,8 +1,8 @@ --- -title: Etcd Snapshots +title: High Availability Backup and Restoration weight: 370 --- -You can configure a Rancher Kubernetes Engine (RKE) cluster to automatically take snapshots of etcd. In a disaster scenario, you can restore these snapshots, which are stored on other cluster nodes. +In a high availability Rancher configuration, you can configure Rancher Kubernetes Engine (RKE) to automatically take backup snapshots of the cluster's etcd database. In a disaster scenario, you can restore these snapshots, which are stored on other cluster nodes. >**Note:** Commands for one-time snapshots and recurring snapshots are available only in RKE v0.1.7 and later. @@ -28,7 +28,7 @@ INFO[0006] Finished saving snapshot [rke_etcd_snapshot_2018-05-17T23:32:08+02:00 The command will save a snapshot of etcd from each etcd node in the cluster config file and will save it in `/opt/rke/etcd-snapshots`. This command also creates a container for taking the snapshot. When the process completes, the container is automatically removed. -## Etcd Recurring Snapshots +## Recurring Snapshots To schedule a recurring automatic etcd snapshot save, enable the `etcd-snapshot` service. `etcd-snapshot` runs in a service container alongside the `etcd` container. `etcd-snapshot` automatically takes a snapshot of etcd and stores them to its local disk in `/opt/rke/etcd-snapshots`. @@ -56,9 +56,9 @@ services: Snapshots are saved to the following directory: `/opt/rke/etcd-snapshots/`. snapshots are created on each node that runs etcd. -## Etcd Disaster Recovery +## High Availablity Restoration -`etcd snapshot-restore` is used for etcd Disaster recovery, it reverts to any snapshot stored in `/opt/rke/etcd-snapshots` that you explicitly define. When you run `etcd snapshot-restore`, RKE removes the old etcd container if it still exists. To restore operations, RKE creates a new etcd cluster using the snapshot you choose. +`etcd snapshot-restore` is used for etcd disaster recovery. This command reverts to any snapshot stored in `/opt/rke/etcd-snapshots` that you explicitly define. When you run `etcd snapshot-restore`, RKE removes the old etcd container if it still exists. To restore operations, RKE creates a new etcd cluster using the snapshot you choose. >**Important:** When restoring the etcd database, you must restore each etcd to the _same_ snapshot, this means the exact same copy, so to restore you have to copy the snapshot from one of the nodes to the others before doing the `etcd snapshot-restore` diff --git a/content/rancher/v2.x/en/installation/after-installation/single-node-backup-and-restoration/_index.md b/content/rancher/v2.x/en/installation/backups-and-restoration/single-node-backup-and-restoration/_index.md similarity index 100% rename from content/rancher/v2.x/en/installation/after-installation/single-node-backup-and-restoration/_index.md rename to content/rancher/v2.x/en/installation/backups-and-restoration/single-node-backup-and-restoration/_index.md