From 80d28610151f80a77e0c7c7064a9d76b981f658e Mon Sep 17 00:00:00 2001
From: Mark Bishop <37810556+MBishop17@users.noreply.github.com>
Date: Wed, 9 May 2018 15:42:43 -0700
Subject: [PATCH] Update _index.md

---
 .../after-installation/etcd-backup-and-restoration/_index.md    | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/content/rancher/v2.x/en/installation/after-installation/etcd-backup-and-restoration/_index.md b/content/rancher/v2.x/en/installation/after-installation/etcd-backup-and-restoration/_index.md
index 846dc65b49e..7d325de0332 100644
--- a/content/rancher/v2.x/en/installation/after-installation/etcd-backup-and-restoration/_index.md
+++ b/content/rancher/v2.x/en/installation/after-installation/etcd-backup-and-restoration/_index.md
@@ -76,6 +76,8 @@ INFO[0011] Finished backup on all etcd hosts
 
 `etcd restore` is a command used to recover from an etcd cluster disaster. The command reverts to any snapshot stored in `/opt/rke/etcdbackup` that you explicitly define. When you run `etcd 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, or the disaster recovery will not work.
+
 >**Warning:** Restoring an etcd backup deletes your current etcd cluster and replaces it with a new one. Before you run the `etcd restore` command, backup any important data in your current cluster.
 
 ```