Wiki source code of Backup/Restore
Version 16.2 by Vincent Massol on 2013/05/03
Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 1 | {{box cssClass="floatinginfobox" title="**Contents**"}} | ||
| 2 | {{toc/}} | ||
| 3 | {{/box}} | ||
| 4 | |||
| 5 | It's crucial that you define a backup strategy for your wiki so that you don't lose any data in case of a problem with your wiki installation or in case you have issues upgrading your XWiki instance to a newer version. | ||
| 6 | |||
| 7 | = Backup configuration files = | ||
| 8 | |||
| 9 | There are several configuration files you'll need to backup: | ||
| 10 | |||
| 11 | * ##WEB-INF/hibernate.cfg.xml## (Hibernate configuration) | ||
| 12 | * ##WEB-INF/xwiki.cfg## (old XWiki configuration file but still used) | ||
| 13 | * ##WEB-INF/xwiki.properties## (new XWiki Configuration file) | ||
| 14 | * ##WEB-INF/classes/logback.xml## (Logging configuration) | ||
| 15 | * ##WEB-INF/observation/*## (Cluster configuration) | ||
| 16 | |||
| 17 | To restore them simply copy them at the same location where you backed them up from. | ||
| 18 | |||
| 19 | In addition you may want to also backup any extra files you'll have installed in your XWiki installation such as JDBC drivers, extra plugins, etc. | ||
| 20 | |||
| 21 | = Backup Permanent Data = | ||
| 22 | |||
| 23 | XWiki generates the following data: | ||
| 24 | * Wiki pages (they're saved in a Database) | ||
| 25 | * Attachments on the filesystem | ||
| 26 | * Installed extensions | ||
| 27 | * Lucene index files | ||
| 28 | * Logs | ||
| 29 | |||
| 30 | It's important that you back them up. | ||
| 31 | |||
| 32 | If you've installed the default standalone version of XWiki then all the data is located in the ##data/## directory inside the directory where you've installed XWiki. Simply back up this directory and that'll backup everything. Otherwise, read on below! | ||
| 33 | |||
| 34 | == Backup your database == | ||
| 35 | |||
| 36 | If you've installed XWiki using your own database then you'll need a backup tool for that database to back it up and to restore it. Moreover, if you're backing up a huge amount of data, we advise that you compress the dump files to save disk space (for example with [[7-zip>>http://www.7-zip.org/]]). | ||
| 37 | |||
| 38 | * **MySQL**:((( | ||
| 39 | Backup: {{code}}mysqldump --add-drop-database --databases xwiki > xwiki.sql{{/code}} backs up the xwiki schema (use the option ##~-~-all-databases## instead of ##~-~-databases xwiki## if you're in multiwiki mode) | ||
| 40 | |||
| 41 | {{warning}} | ||
| 42 | It's important that the backup is done with ##~-~-add-drop-database## since when you restore it it's important that tables that might have been created are removed. For example database migrations can create extra tables. If you want to cancel the migration and go back to your clean dump you'll need to have those tables removed as otherwise when you run the migration again later on you might have errors. | ||
| 43 | {{/warning}} | ||
| 44 | ))) | ||
| 45 | * **PostgreSQL**: You can use {{code}}pg_dump xwiki > xwiki.sql{{/code}} to backup the PostgreSQL database. | ||
| 46 | * **Oracle**: Use ##exp## to export data. | ||
| 47 | |||
| 48 | == Backup Attachments == | ||
| 49 | |||
| 50 | Since XWiki 3.x you can choose to [[store attachments on the filesystem>>AdminGuide.Attachments#HAttachmentStorage]] instead of in the database. If you've configured it this way then you need to backup the Permanent Directory which is where attachments saved on the filesystem are located. This directory is configured by the ##environment.permanentDirectory## configuration property in your ##WEB-INF/xwiki.properties## configuration file. | ||
| 51 | |||
| 52 | == Backup Extensions == | ||
| 53 | |||
| 54 | Extensions are also saved on the filesystem in the Permanent Data Directory (i.e. ##environment.permanentDirectory##) in an ##extension## subdirectory. | ||
| 55 | |||
| 56 | == Backup Lucene index files == | ||
| 57 | |||
| 58 | You could decide to backup Lucene index files. However XWiki will regenerate them automatically if they are not found at startup. Now if you have a lot of wiki pages that can take a lot of time and you may want to back them up. They are also located in the Permanent Data Directory (i.e. ##environment.permanentDirectory##) in a ##lucene## subdirectory. | ||
| 59 | |||
| 60 | == Backup Log files == | ||
| 61 | |||
| 62 | XWiki generates logs in the console by default and these will go where your Servlet container has been defined to save them. For Tomcat for example this usually goes in the ##TOMCAT_HOME/logs/catalina.out## file. | ||
| 63 | |||
| 64 | However this is fully [[configurable>>AdminGuide.Logging]] and you may have configured XWiki to output log files elsewhere. If you want to keep those logs, don't forget to save them. Those logs are not needed by XWiki but you may want to save them to review them later on to diagnose issues that happened for example. | ||
| 65 | |||
| 66 | = Using the XWiki Export feature = | ||
| 67 | |||
| 68 | Since most XWiki data is saved in wiki pages one solution to backup a XWiki instance is to export all its pages using XWiki's [[Import/Export feature>>ImportExport]]. However note that this is quite a resource hungry operation and depending on the size of your wiki you may need a lot of memory. As a consequence the recommended backup strategy is to backup the databases. It's much better to use a specialized backup tool that'll backup the database, perform incremental backups, verify backup integrity, etc. | ||
| 69 | |||
| 70 | In addition you should know that currently the following information is not located in wiki pages and is thus not saved in a wiki export: | ||
| 71 | * Activity stream data | ||
| 72 | * Statistics data | ||
| 73 | * Feed plugin data (if you use it) | ||
| 74 | * Deleted documents/attachments data | ||
| 75 | |||
| 76 | Moreover this won't save configuration data or other Permanent Data mentioned above such as installed Extensions, Lucene index files and Logs. | ||
| 77 | |||
| 78 | In practice the Import/Export feature should be reserved for the following use cases: | ||
| 79 | * move data across XWiki instances, including sharing of applications between separate instances | ||
| 80 | * move data to another wiki | ||
| 81 | * convert from one database to another | ||
| 82 | |||
| 83 | = Restore your data = | ||
| 84 | |||
| 85 | * **MySQL**: Assuming you have your ##xwiki.sql## file handy (obtained running ##mysqldump## as explained above), run the following from the command line (or a script). Examples below are for the Linux shell.((( | ||
| 86 | * Disable constraints check first: {{code}}mysql -e "SET FOREIGN_KEY_CHECKS=0;"{{/code}} (restoring may fail with some cryptic error code, leaving the database in an inconsistent state, if you omit this step) | ||
| 87 | * In case the xwiki database was destroyed (or non existant on the fresh host machine): {{code}}mysql -e "CREATE DATABASE IF NOT EXISTS xwiki DEFAULT CHARACTER SET utf8;"{{/code}} | ||
| 88 | * Restore data from the dump file: {{code}}mysql xwiki --user=root -p < xwiki.sql{{/code}}. Alternatively, you can omit the ##-p## by adding a section [mysqldump] in your ##.my.cnf## file (with a user and password line, same as for [mysql]). | ||
| 89 | * Re-enable constraints checks: {{code}}mysql -e "SET FOREIGN_KEY_CHECKS=1;"{{/code}} | ||
| 90 | |||
| 91 | That is not all, now you need to restore the xwiki user rights (assuming the ##xwiki## user exists in MySQL). | ||
| 92 | * Update the xwiki user password from the (previously restored) hibernate configuration file:((( | ||
| 93 | {{code language="none"}} | ||
| 94 | pass=$(cat /etc/xwiki/hibernate.cfg.xml | grep passw| head -1 | sed -e 's/^.*<prop.*password">//' | sed -e 's|</property>.*||') | ||
| 95 | mysql -e "SET PASSWORD FOR 'xwiki'@'localhost' = PASSWORD('$pass');" | ||
| 96 | {{/code}} | ||
| 97 | ))) | ||
| 98 | |||
| 99 | Finally, restore you container, for example in Linux: {{code}}service tomcat7 restart{{/code}} | ||
| 100 | ))) | ||
| 101 | * **PostgreSQL**: {{code}}psql -d xwiki -f xwiki.sql{{/code}} to restore your previously saved data. In case of multiwiki mode, use the binary ##pg_dumpall## instead. | ||
| 102 | * **Oracle**: Use ##imp##. | ||
| 103 | |||
| 104 | = Tips in case you are using nginx = | ||
| 105 | |||
| 106 | Assuming you have a nginx configuration with a {{code}}server_name{{/code}} entry that needs updating, the following script might be useful. | ||
| 107 | |||
| 108 | {{code}} | ||
| 109 | #!/bin/bash | ||
| 110 | configfile="/etc/nginx/sites-available/xwiki-as-root.conf" | ||
| 111 | # The following line works for Amazon EC2 instances. Change accordingly to find this host's IP dynamically. | ||
| 112 | thisip=$(curl -s http://instance-data/latest/meta-data/public-ipv4) | ||
| 113 | if [ ! -f $configfile ]; then | ||
| 114 | echo "Missing file: $configfile" | ||
| 115 | exit 1 | ||
| 116 | fi | ||
| 117 | echo backing-up $configfile | ||
| 118 | cp $configfile $configfile-old | ||
| 119 | |||
| 120 | echo Setting nginx server_name to $thisip | ||
| 121 | old=$(cat $configfile | grep '^\ *server_name' | awk '{print $2}' | sed -e 's/;//' | grep "$thipip" | head -1) | ||
| 122 | if [ $? -eq 0 ] ; then | ||
| 123 | echo Fixing server_name | ||
| 124 | cat $configfile | sed -e "s/$old/$thisip/" > $configfile-new | ||
| 125 | mv $configfile-new $configfile | ||
| 126 | fi | ||
| 127 | |||
| 128 | echo Done. New config file: | ||
| 129 | cat $configfile | ||
| 130 | |||
| 131 | echo restarting nginx | ||
| 132 | service nginx restart | ||
| 133 | {{/code}} |
