mirror of
https://github.com/rancher/rancher-docs.git
synced 2026-09-25 04:28:15 +00:00
making updates per feedback from Will and Denise
This commit is contained in:
Mark Bishop
Mark Bishop
+1
-1
@@ -6,7 +6,7 @@ You can configure a Rancher Kubernetes Engine (RKE) cluster to automatically tak
|
||||
|
||||
## One-Time Snapshots
|
||||
|
||||
RKE introduce a new command that can take a snapshot of a running etcd node in rke cluster, the snapshot will be automatically saved in `/opt/rke/etcd-snapshots`, the commands works as following:
|
||||
RKE v0.1.7 and includes a command that takes a snapshot of a etcd node running in your RKE cluster, which is automatically saved to `/opt/rke/etcd-snapshots`. The commands works as follows:
|
||||
```
|
||||
./rke etcd snapshot-save --config cluster.yml
|
||||
|
||||
|
||||
+49
@@ -0,0 +1,49 @@
|
||||
---
|
||||
title: Single Node Backup and Restoration
|
||||
weight: 365
|
||||
---
|
||||
|
||||
After completing your single node installation of Rancher, or before your upgrade to a newer version of Rancher, create a backup of your current installation. Use this backup as a restoration point your Rancher install or upgrade encounters issues.
|
||||
|
||||
## Backing Up Your Rancher Server
|
||||
|
||||
>**Prerequisite:** Open Rancher and write down the version number displayed in the lower-left of the browser (example: `v2.0.0`). You'll need this number during the backup process.
|
||||
|
||||
1. Stop the container currently running Rancher Server. Replace `<RANCHER_CONTAINER_ID>` with the ID of your Rancher container.
|
||||
|
||||
```
|
||||
docker stop <RANCHER_CONTAINER_ID>
|
||||
```
|
||||
|
||||
>**Tip:** You can obtain the ID for your Rancher container by entering the following command: `docker container ls`
|
||||
|
||||
2. Create a backup container. This container backs up the data from your current Rancher Server, which you can use as a recovery point.
|
||||
|
||||
- Replace `<RANCHER_CONTAINER_ID>` with the same ID from the previous step.
|
||||
- Replace `<RANCHER_CONTAINER_TAG>` and `<RANCHER_VERSION>` with the version of Rancher that you are currently running, as mentioned in the **Prerequisite** above.
|
||||
|
||||
```
|
||||
docker create --volumes-from <RANCHER_CONTAINER_ID>
|
||||
--name rancher-backup-<RANCHER_VERSION> rancher/rancher:<RANCHER_CONTAINER_TAG>
|
||||
```
|
||||
|
||||
3. Restart Rancher Server. Replace `<RANCHER_CONTAINER_ID>` with the ID of your Rancher container.
|
||||
|
||||
```
|
||||
docker start <RANCHER_CONTAINER_ID>
|
||||
```
|
||||
|
||||
|
||||
## Restoring Your Rancher Server
|
||||
|
||||
1. Stop the container currently running Rancher Server. Replace `<RANCHER_CONTAINER_ID>` with the ID of your Rancher container.
|
||||
|
||||
```
|
||||
docker stop <RANCHER_CONTAINER_ID>
|
||||
```
|
||||
|
||||
2. Launch a new Rancher Server container using the most recent `rancher-backup-<RANCHER_VERSION>` container.
|
||||
|
||||
```
|
||||
docker run -d --volumes-from rancher-backup-<RANCHER_VERSION> --restart=unless-stopped \
|
||||
-p 80:80 -p 443:443 rancher/rancher:<CURRENT_RANCHER_VERSION>
|
||||
@@ -311,4 +311,5 @@ By default, Rancher automatically generates self-signed certificates for itself
|
||||
|
||||
## What's Next?
|
||||
|
||||
Log in to Rancher to make sure it deployed successfully. Open a web browser and navigate to the FQDN chosen in [Configure DNS](#part-3-configure-dns).
|
||||
- Log in to Rancher to make sure it deployed successfully. Open a web browser and navigate to the FQDN chosen in [Configure DNS](#part-3-configure-dns).
|
||||
- Configure RKE to take snapshots of etcd that you can use as a backup in a disaster scenario. For more information, see [etcd recurring snapshots]({{< baseurl >}}/rancher/v2.x/en/installation/after-installation/etcd-backup-and-restoration/#etcd-recurring-snapshots).
|
||||
|
||||
@@ -396,4 +396,5 @@ By default, Rancher automatically generates self-signed certificates for itself
|
||||
|
||||
## What's Next?
|
||||
|
||||
Log in to Rancher to make sure it deployed successfully. Open a web browser and navigate to the FQDN chosen in [Configure DNS](#part-3-configure-dns).
|
||||
- Log in to Rancher to make sure it deployed successfully. Open a web browser and navigate to the FQDN chosen in [Configure DNS](#part-3-configure-dns).
|
||||
- Configure RKE to take snapshots of etcd that you can use as a backup in a disaster scenario. For more information, see [etcd recurring snapshots]({{< baseurl >}}/rancher/v2.x/en/installation/after-installation/etcd-backup-and-restoration/#etcd-recurring-snapshots).
|
||||
|
||||
@@ -167,6 +167,10 @@ By default, Rancher automatically generates self-signed certificates for itself
|
||||
2. Select **Settings** > **cacerts**.
|
||||
3. Choose `Edit` and remove the contents. Then click `Save`.
|
||||
|
||||
## What's Next?
|
||||
|
||||
Create a backup of your Rancher Server in case of a disaster scenario. For more information, see [Backing Up Your Rancher Server]({{< baseurl >}}/rancher/v2.x/en/installation/after-installation/single-node-backup-and-restoration/#backing-up-your-rancher-server).
|
||||
|
||||
## SSL FAQ / Troubleshooting
|
||||
|
||||
{{< ssl_faq >}}
|
||||
|
||||
@@ -136,6 +136,10 @@ docker run -d --restart=unless-stopped \
|
||||
|
||||
>**Remember:** Let's Encrypt provides rate limits for requesting new certificates. Therefore, limit how often you create or destroy the container. For more information, see [Let's Encrypt documentation on rate limits](https://letsencrypt.org/docs/rate-limits/).
|
||||
|
||||
## What's Next?
|
||||
|
||||
Create a backup of your Rancher Server in case of a disaster scenario. For more information, see [Backing Up Your Rancher Server]({{< baseurl >}}/rancher/v2.x/en/installation/after-installation/single-node-backup-and-restoration/#backing-up-your-rancher-server).
|
||||
|
||||
## SSL FAQ / Troubleshooting
|
||||
|
||||
{{< ssl_faq >}}
|
||||
|
||||
@@ -13,7 +13,7 @@ To upgrade Rancher 2.x running in a high availablity configuration, run an upgra
|
||||
|
||||
1. From your workstation, open **Terminal**.
|
||||
|
||||
2. Enter the ng command:
|
||||
2. Enter the following command:
|
||||
|
||||
```
|
||||
kubectl --kubeconfig=kube_config-rancher-cluster.yml set image deployment/cattle cattle-server=rancher/rancher:<VERSION_TAG> -n cattle-system
|
||||
|
||||
@@ -4,7 +4,10 @@ weight: 1010
|
||||
---
|
||||
To upgrade Rancher Server 2.x to the latest version, you need to enter only a few commands.
|
||||
|
||||
>**Prerequisite:** Open Rancher and write down the version number displayed in the lower-left of the browser (example: `v2.0.0`). You'll need this number during the upgrade process.
|
||||
>**Prerequisites:**
|
||||
>
|
||||
> - Create a backup of your current Rancher installation. For more information, see [Backing Up Your Rancher Server]({{< baseurl >}}/rancher/v2.x/en/installation/after-installation/single-node-backup-and-restoration/#backing-up-your-rancher-server).
|
||||
> - Open Rancher and write down the version number displayed in the lower-left of the browser (example: `v2.0.0`). You'll need this number during the upgrade process.
|
||||
|
||||
1. Stop the container currently running Rancher Server. Replace `<RANCHER_CONTAINER_ID>` with the ID of your Rancher container.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user