Wiki source code of Backup/Restore
Version 11.1 by Vincent Massol on 2012/07/09
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 backupped them 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 data are 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 backup a huge amount of data, we advise that you compress the dump files to save disk (for example with gzip). | ||
| 37 | |||
| 38 | * **MySQL**: You can use {{code}}mysqldump xwiki > xwiki.sql{{/code}} to backup the xwiki schema (use the option ##~-~-all-databases## if you're in multiwiki mode) and {{code}}mysql xwiki --user=root -p < xwiki.sql{{/code}} to restore it. | ||
| 39 | * **PostgreSQL**: You can use {{code}}pg_dump xwiki > xwiki.sql{{/code}} to backup PostgreSQL database and {{code}}psql -d xwiki -f xwiki.sql{{/code}} to restore it. In case of multiwiki mode, use the binary ##pg_dumpall## instead. | ||
| 40 | * **Oracle**: Use ##exp## to export data and ##imp## to restore it. | ||
| 41 | |||
| 42 | == Backup Attachments == | ||
| 43 | |||
| 44 | Since XWiki 3.x you can choose to [[store the 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. | ||
| 45 | |||
| 46 | == Backup Extensions == | ||
| 47 | |||
| 48 | Extensions are also saved on the filesystem in the Permanent Data Directory (i.e. ##environment.permanentDirectory##) in an ##extension## subdirectory. | ||
| 49 | |||
| 50 | == Backup Lucene index files == | ||
| 51 | |||
| 52 | 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. | ||
| 53 | |||
| 54 | == Backup Log files == | ||
| 55 | |||
| 56 | 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 ##TOMCAT_HOME/logs/catalina.out## file. | ||
| 57 | |||
| 58 | 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. | ||
| 59 | |||
| 60 | = Using the XWiki Export feature = | ||
| 61 | |||
| 62 | 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. | ||
| 63 | |||
| 64 | 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: | ||
| 65 | * Activity stream data | ||
| 66 | * Statistics data | ||
| 67 | * Feed plugin data (if you use it) | ||
| 68 | * Deleted documents/attachments data | ||
| 69 | |||
| 70 | Moreover this won't save configuration data or other Permanent Data mentioned above such as installed Extensions, Lucene index files and Logs. | ||
| 71 | |||
| 72 | In practice the Import/Export should be reserved for the following use cases: | ||
| 73 | * move data across XWiki instances, including sharing of applications between separate instances | ||
| 74 | * move data to another wiki |
