public/rancher-docs
1
0
Fork 0
mirror of https://github.com/rancher/rancher-docs.git synced 2026-09-27 21:50:21 +00:00
Code Issues Packages Projects Releases Wiki Activity

upgrade/rollback/backup updates

Browse Source
This commit is contained in:
Denise Schannon
2018-07-26 22:38:55 -07:00
committed by Denise
parent c974696029
commit e9631a4613
4 changed files with 38 additions and 32 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/rancher/v2.x/en/backups/rollbacks/single-node-rollbacks/_index.md
+10 -8
View File
@@ -16,19 +16,21 @@ docker pull rancher/rancher:<PRIOR_VERSION>
2. Stop the container currently running Rancher Server. Replace `<RANCHER_CONTAINER_ID>` with the ID of your Rancher container.
```bash
```
docker stop <RANCHER_CONTAINER_ID>
```
3. Go to the location where you saved your backup tar balls. And run the following command.
3. Go to the location where you saved your [backup tar balls]({{< baseurl>}}/rancher/v2.x/en/upgrades/single-node-upgrade/#backup). Run the following command to create a data container from the backup tar ball.
```bash
docker run --volumes-from rancher-data-<PRIOR_VERSION> -v $PWD:/backup alpine sh -c "rm /var/lib/rancher/* -rf && tar zxvf /backup/<BACKUP_FILENAME>.tar.gz"
```
```
docker run --volumes-from rancher-data-<PRIOR_VERSION> \
-v $PWD:/backup alpine sh -c "rm /var/lib/rancher/* -rf \
&& tar zxvf /backup/<BACKUP_FILENAME>.tar.gz"
```
4. Start a new Rancher Server container with the `<PRIOR_VERSION>` tag.
4. Start a new Rancher Server container with the `<PRIOR_VERSION>` tag pointing to the data container.
```
docker run -d --volumes-from rancher-data-<PRIOR_VERSION> --restart=unless-stopped \
-p 80:80 -p 443:443 rancher/rancher:<PRIOR_VERSION>
docker run -d --volumes-from rancher-data-<PRIOR_VERSION> \
--restart=unless-stopped -p 80:80 -p 443:443 rancher/rancher:<PRIOR_VERSION>
```
>**Note:** _Do not_ stop the rollback after initiating it, even if the rollback process seems longer than expected. Stopping the rollback may result in database issues during future upgrades.