From 83b9eba24f8a6ce19616f98f39f65db38a5e9927 Mon Sep 17 00:00:00 2001 From: Adrian Goins Date: Tue, 13 Nov 2018 15:54:23 -0300 Subject: [PATCH] fix incorrect command changed `dir` to `ls` and made minor changes to language for smoother flow --- .../backups/backups/single-node-backups/_index.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/content/rancher/v2.x/en/backups/backups/single-node-backups/_index.md b/content/rancher/v2.x/en/backups/backups/single-node-backups/_index.md index 9ea7cce9ddf..92ac00ab4a7 100644 --- a/content/rancher/v2.x/en/backups/backups/single-node-backups/_index.md +++ b/content/rancher/v2.x/en/backups/backups/single-node-backups/_index.md @@ -6,11 +6,11 @@ aliases: - /rancher/v2.x/en/installation/backups-and-restoration/single-node-backup-and-restoration/ --- -After completing your single node installation of Rancher, we recommend creating backups of it on a regular basis. Use these backups as a restoration point in a disaster scenario. +After completing your single node installation of Rancher, we recommend creating backups of it on a regular basis. Having a recent backup will let you recover quickly from an unexpected disaster. ## Before You Start -During creation of your backup, you'll enter a series of commands, filling placeholders with data from your environment. These placeholders are denoted with angled brackets and all capital letters (``). Here's an example of a command with a placeholder: +During the creation of your backup, you'll enter a series of commands, replacing placeholders with data from your environment. These placeholders are denoted with angled brackets and all capital letters (``). Here's an example of a command with a placeholder: ``` docker run --volumes-from rancher-data- -v $PWD:/backup alpine tar zcvf /backup/rancher-data-backup--.tar.gz /var/lib/rancher @@ -31,11 +31,11 @@ Cross reference the image and reference table below to learn how to obtain this | `` | `9-27-18` | The date that the data container or backup was created. |
-You can obtain `` and `` by logging into your Rancher Server by remote connection and entering the command to view the containers that are running: `docker ps`. You can also view containers that are stopped using a different command: `docker ps -a`. Use these commands for help anytime during while creating backups. +You can obtain `` and `` by logging into your Rancher Server by remote connection and entering the command to view the containers that are running: `docker ps`. You can also view containers that are stopped with `docker ps -a`. Use these commands for help anytime while creating backups. ## Creating a Backup -This procedure creates a backup that you can restore to in case Rancher encounters a disaster scenario. +This procedure creates a backup that you can restore if Rancher encounters a disaster scenario. 1. Using a remote Terminal connection, log into the node running your Rancher Server. @@ -57,11 +57,11 @@ This procedure creates a backup that you can restore to in case Rancher encounte docker run --volumes-from rancher-data- -v $PWD:/backup alpine tar zcvf /backup/rancher-data-backup--.tar.gz /var/lib/rancher ``` - **Step Result:** A stream of commands runs on screen. + **Step Result:** A stream of commands runs on the screen. -1. Enter the `dir` command to confirm that the backup tarball was created. It will have a name similar to `rancher-data-backup--.tar.gz`. +1. Enter the `ls` command to confirm that the backup tarball was created. It will have a name similar to `rancher-data-backup--.tar.gz`. -1. Move your backup tarball to a safe location external from your Rancher Server. Then delete the `rancher-data-` container from your Rancher Server. +1. Move your backup tarball to a safe location external to your Rancher Server. Then delete the `rancher-data-` container from your Rancher Server. 1. Restart Rancher Server. Replace `` with the name of your [Rancher container](#before-you-start).