Difference between revisions of "Backup your existing openQRM environment"
(3 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
[[Category:Tutorial]] | [[Category:Tutorial]] | ||
[[Category:Backup]] | [[Category:Backup]] | ||
+ | Here a screenshot of a existing, fully configured openQRM Setup | ||
+ | [[File:01.png|none|thumb|390x390px|Fully configured openQRM Setup]] | ||
+ | Here a screenshot of the version details of this openQRM Setup | ||
+ | [[File:02.png|none|thumb|390x390px|Version details openQRM Setup]] | ||
+ | openQRM consist of "files" and a "database". Having a backup of both parts allow to "roll-back" the update at any point. | ||
+ | |||
+ | All files in openQRM are located within the openQRM base-directory (normally /usr/share/openqrm). To create a simply backup please run the following commands as 'root' on your openQRM Server:<blockquote>''cp -aR /usr/share/openqrm /usr/share/openqrm.before-update''</blockquote>To backup the openQRM database content (assuming mysql as the database backend) please run:<blockquote>''mysqldump openqrm - p > /usr/share/openqrm.before-update/openqrm-db.sql''</blockquote>This command will ask for the openQRM database password. | ||
+ | |||
+ | '''NOTE''' | ||
+ | |||
+ | At any time you can roll-back to your previous state of your openQRM environment by running as 'root'<blockquote>''mv /usr/share/openqrm /usr/share/openqrm-update-rolled-back && mv /usr/share/openqrm.before-update /usr/share/openqrm && /etc/init.d/openqrm restart''</blockquote>Furthermore openQRM provides a 'state-backup' which captures the full-state (all configuration files and the databases content). A 'state-backup' of openQRM also allows to "roll-back" the update at any point. To run a state backup please run:<blockquote>''/usr/share/openqrm/bin/openqrm state backup -n before-update''</blockquote>To list all state backups please run:<blockquote>''/usr/share/openqrm/bin/openqrm state list''</blockquote>To apply/restore a state backups please run e.g.:<blockquote>''/usr/share/openqrm/bin/openqrm state restore -n [backup-name]''</blockquote>Here the commands to apply for a standard backup before an update: | ||
+ | [[File:03.png|none|thumb|390x390px|Commands to apply]] | ||
+ | |||
+ | === Congratulations! === | ||
+ | You have completed this openQRM Backup How-To. You can now fully automate your OpenStack deployments with openQRM. |
Latest revision as of 12:05, 16 November 2020
Here a screenshot of a existing, fully configured openQRM Setup
Here a screenshot of the version details of this openQRM Setup
openQRM consist of "files" and a "database". Having a backup of both parts allow to "roll-back" the update at any point.
All files in openQRM are located within the openQRM base-directory (normally /usr/share/openqrm). To create a simply backup please run the following commands as 'root' on your openQRM Server:
cp -aR /usr/share/openqrm /usr/share/openqrm.before-update
To backup the openQRM database content (assuming mysql as the database backend) please run:
mysqldump openqrm - p > /usr/share/openqrm.before-update/openqrm-db.sql
This command will ask for the openQRM database password.
NOTE
At any time you can roll-back to your previous state of your openQRM environment by running as 'root'
mv /usr/share/openqrm /usr/share/openqrm-update-rolled-back && mv /usr/share/openqrm.before-update /usr/share/openqrm && /etc/init.d/openqrm restart
Furthermore openQRM provides a 'state-backup' which captures the full-state (all configuration files and the databases content). A 'state-backup' of openQRM also allows to "roll-back" the update at any point. To run a state backup please run:
/usr/share/openqrm/bin/openqrm state backup -n before-update
To list all state backups please run:
/usr/share/openqrm/bin/openqrm state list
To apply/restore a state backups please run e.g.:
/usr/share/openqrm/bin/openqrm state restore -n [backup-name]
Here the commands to apply for a standard backup before an update:
Congratulations!
You have completed this openQRM Backup How-To. You can now fully automate your OpenStack deployments with openQRM.