From 0ac9ec8f7e673dc9a2a99834aec6693db6e941c6 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Torkel=20=C3=96degaard?= Date: Fri, 28 Apr 2017 11:04:56 +0200 Subject: [PATCH] docs: added restore instructions to backup section in upgrading doc article, closes #5680 --- docs/sources/installation/upgrading.md | 15 ++++++++++++--- 1 file changed, 12 insertions(+), 3 deletions(-) diff --git a/docs/sources/installation/upgrading.md b/docs/sources/installation/upgrading.md index b636d51e6a1..846a42b454c 100644 --- a/docs/sources/installation/upgrading.md +++ b/docs/sources/installation/upgrading.md @@ -15,7 +15,7 @@ weight = 10 We recommend everyone to upgrade Grafana often to stay up to date with the latest fixes and enhancements. In order make this a reality Grafana upgrades are backward compatible and the upgrade process is simple & quick. -Upgrading is generally always safe (between many minor and one major version) and dashboards and graphs will look the same. There can be minor breaking changes in some edge cases which are usually outlined in the [Release Notes](https://community.grafana.com/c/releases) and [Changelog]https://github.com/grafana/grafana/blob/master/CHANGELOG.md) +Upgrading is generally always safe (between many minor and one major version) and dashboards and graphs will look the same. There can be minor breaking changes in some edge cases which are usually outlined in the [Release Notes](https://community.grafana.com/c/releases) and [Changelog](https://github.com/grafana/grafana/blob/master/CHANGELOG.md) ## Database Backup @@ -30,12 +30,21 @@ installed grafana to custom location using a binary tar/zip it is usally in ` grafana_backup.sql +backup: +> mysqldump -u root -p[root_password] [grafana] > grafana_backup.sql + +restore: +> mysql -u root -p grafana < grafana_backup.sql ``` #### postgres + ``` -pg_dump grafana > grafana_backup +backup: +> pg_dump grafana > grafana_backup + +restore: +> psql grafana < grafana_backup ``` ### Ubuntu / Debian