Jump to: navigation, search
This page is a translated version of the page Manual:Backing up a wiki and the translation is 39% complete.

Other languages:
Deutsch • ‎English • ‎español • ‎français • ‎magyar • ‎Bahasa Indonesia • ‎italiano • ‎日本語 • ‎한국어 • ‎മലയാളം • ‎polski • ‎português • ‎português do Brasil • ‎русский • ‎සිංහල • ‎தமிழ் • ‎中文

ウィキ内のデータのバックアップを定期的に作成することは重要です。このページでは、典型的な MediaWiki ウィキのバックアップ手順の概要を説明します。


MediaWiki は、重要なデータを 2 箇所に保持しています:

ソフトウェア構成ファイル、カスタム外装、拡張機能、画像 (削除されたものを含む) など。

バックアップを作る前に、ウィキを読み取り専用にする($wgReadOnly 参照)ことを検討してください。これによって出来上がったバックアップが自己矛盾の無いものとなります (一部の拡張機能は読み取り専用にしてもデータを書き込むかもしれません)。



  • 非公開ではないデータであれば単にpublish on archive.orgまたはwebサーバーのdumps/ディレクトリの中に入っています。
  • SCP (または WinSCP)、SFTP/FTP などの転送プロトコルが使用できます。
  • ホスティング会社がwebブラウザー上で動作するファイルマネージャーを提供しているかも知れません。





See the package on Debian:

$ apt show automysqlbackup
Description: automysqlbackup creates backup every day, week and month for all of your MySQL database, to a configured folder. There's nothing to do but to install this package, and you'll rest assured that you have a way to go back in the history of your database.


# apt install automysqlbackup

All your databases will be saved in /var/lib/automysqlbackup/:

$ find /var/lib/automysqlbackup/

Manual backup:

# automysqlbackup

Restore a database:

gunzip < /var/lib/automysqlbackup/weekly/my_wiki/my_wiki_week.18.2016-05-07_15h32m.sql.gz|mysql -uUSER -pPASSWORD my_wiki

For other distributions, see on Sourceforge.


最も簡便なのは、MySQLに標準で付属するMySQL ダンプツール (mysqldump)を用いることである。これは、バックアップ対象のデータベース名やテーブル名を指定してダンプファイルを作成することができるコマンドラインアプリケーションである。

First insert the following line into LocalSettings.php

$wgReadOnly = 'Dumping Database, Access will be restored shortly';

this can be removed as soon as the dump is completed.

Linux/UNIX シェル上で実行するコマンドの例:

mysqldump -h hostname -u userid -p --default-character-set=whatever dbname > backup.sql

Substituting hostname, userid, whatever, and dbname as appropriate. All four may be found in your LocalSettings.php (LSP) file. hostname may be found under $wgDBserver; by default it is localhost. userid may be found under $wgDBuser, whatever may be found under $wgDBTableOptions, where it is listed after DEFAULT CHARSET=. If whatever is not specified mysqldump will likely use the default of utf8, or if using an older version of MySQL, latin1. While dbname may be found under $wgDBname. After running this line from the command line mysqldump will prompt for the server password (which may be found under Manual:$wgDBpassword in LSP).

コマンドライン パラメーターの完全な一覧については mysqldump を参照してください。

The output from mysqldump can instead be piped to gzip, for a smaller output file, as follows

mysqldump -h hostname -u userid -p dbname | gzip > backup.sql.gz

A similar mysqldump command can be used to produce XML output instead, by including the --xml parameter.

mysqldump -h hostname -u userid -p --xml dbname > backup.xml

and to compress the file with a pipe to gzip

mysqldump -h hostname -u userid -p --xml dbname | gzip > backup.xml.gz

Remember to also backup the file system components of the wiki that might be required, e.g., images, logo, and extensions.


Cron is the time-based job scheduler in Unix-like computer operating systems. Cron enables users to schedule jobs (commands or shell scripts) to run periodically at certain times or dates.

A sample command that you may run from a crontab may look like this:

nice -n 19 mysqldump -u $USER --password=$PASSWORD $DATABASE -c | nice -n 19 gzip -9 > ~/backup/wiki-$DATABASE-$(date '+%Y%m%d').sql.gz

The nice -n 19 lowers the priority of the process.

Use valid values for $USER, $PASSWORD, and $DATABASE. This will write a backup file with the weekday in the filename so you would have a rolling set of backups. If you want to save the files and extensions as well, you might want to use this one.

警告 警告: Do not attempt to back up your Mediawiki database using mysqlhotcopy. The table format used by Mediawiki cannot be backed up with this tool, and it will fail silently!

If you want to add this task in Cron through Cpanel then you must escape the character "%"

/usr/bin/mysqldump -u $USER --password=$PASSWORD $DATABASE -c | /bin/gzip > ~/backup/wiki-$DATABASE-$(date '+\%Y\%m\%d').sql.gz


/bin/sh: -c: line 0: unexpected EOF while looking for matching `''
/bin/sh: -c: line 1: syntax error: unexpected end of file


Under close examination one finds that some of the tables dumped have various degrees of temporariness. So to save disk space (beyond just gziping), although those tables need to be present in a proper dump, their data does not. However, under certain circumstances the disadvantage of having to rebuild all this data may outweigh the saving in disk space (for example, on a large wiki where restoration speed is paramount).

See mailing list thread mysql5 binary schema about the topic.


See the relevant section of the upgrading page for information about this process. Also see the talk page for more information about working with character sets in general.


You can use the pg_dump tool to back up a MediaWiki PostgreSQL database. For example:

pg_dump mywiki > mywikidump.sql

will dump the mywiki database to mywikidump.sql.


psql mywiki -f mywikidump.sql

You may also want to dump the global information, e.g. the database users:

pg_dumpall --globals > postgres_globals.sql


データベースが現在オフラインなら、データベースファイルをコピーするだけでデータベースをバックアップできます。 もしそうでないなら、 メンテナンス・スクリプト: php maintenance/sqlite.php --backup-to <backup file name>を使用します。この作業はアトミックであり(すべての処理が実行されるか全く実行されないかのいずれかなので)不整合はありません。 ウィキのデータベースが非常に大きかったり、サーバーの負荷が重かったりしなければ、ウィキを編集しているユーザーは多少のもたつきを感じるだけでしょう。 ウィキを読んでいるだけの利用者は何も感じないでしょう。


Turn your wiki to read only by adding $wgReadOnly = 'Site Maintenance'; to LocalSettings.php.

Open the browser to your phpadmin link, login, choose the wiki database. (Check LocalSettings.php if you're not sure). Select Export. Make sure all items under Export are highlighted, and make sure Structure is highlighted (it's important to maintain the table structure). Optionally check Add DROP TABLE to delete existing references when importing. Make sure Data is checked. Select zipped. Then click on GO and save the backup file.[1]

Remove $wgReadOnly = 'Site Maintenance'; from LocalSettings.php

Remember to also backup the file system components of the wiki that might be required, eg. images, logo, and extensions.



HeidiSQL is similar to phpMyAdmin, but without any restrictions of phpMyAdmin's free version. HeidiSQL requires a direct database connection, where some hosts may only offer web interfaces (phpMyAdmin) to firewalled databases.


データベースに保存するよりもファイルシステムに保存した方が適切であるような要素についてはファイルシステムの中に保存されます。例えばサイトの設定ファイル(LocalSettings.phpAdminSettings.php (最終的に 1.23 で除去されました))や画像ファイル(削除された画像、サムネイル、数式やSVGファイルも含む)、スキンのカスタマイズ設定、Extensionファイルなどが該当思案す。


Linuxの場合でWikiが /srv/www/htdocs/wiki に格納されているとすると

  tar zcvhf wikidata.tgz /srv/www/htdocs/wiki

It should be possible to backup the entire "wiki" folder in "htdocs" if using XAMPP.

ウィキのコンテンツのバックアップ (XML ダンプ)

It is also a good idea to create an XML dump in addition to the database dump. XML dumps contain the content of the wiki (wiki pages with all their revisions), without the site-related data (they do not contain user accounts, image metadata, logs, etc).[2]

XML dumps are less likely to cause problems with character encoding, as a means of transfering large amounts of content quickly, and are easily be used by third party tools, which makes XML dumps a good fallback should your main database dump become unusable.

To create an XML dump, use the command-line tool dumpBackup.php, located in the maintenance directory of your MediaWiki installation. See Manual:dumpBackup.php for more details.

You can also create an XML dump for a specific set of pages online, using Special:Export, although attempting to dump large quantities of pages through this interface will usually time out.

To import an XML dump into a wiki, use the command-line tool importDump.php. For a small set of pages, you can also use the Special:Import page via your browser (by default, this is restricted to the sysop group). As an alternative to dumpBackup.php and importDump.php, you can use MWDumper, which is faster, but requires a Java runtime environment.

詳細情報は Manual:XML ダンプの取り込み を参照してください。


If you have no shell access, then use the WikiTeam Python script from a DOS, Unix or Linux command-line. Requires Python v2 (v3 doesn't yet work).

To get an XML, with edit histories, dump and a dump of all images plus their descriptions. Without extensions and LocalSettings.php configs.

python --api= --xml --images

Full instructions are at the WikiTeam tutorial.

Meta:Data dumps も参照してください。


警告 警告: Use these at your own risk. Check your wiki's LocalSettings.php for the correct character set to use, as you may need to edit the script to suit.
  • Unofficial backup script by User:Duesentrieb.
  • Unofficial backup script by Flominator; creates a backup of all files and the database, with optional backup rotation.
  • User:Darizotas/MediaWiki Backup Script for Windows - a script for backing up a Windows MediaWiki install. Note: Has no restore feature.
  • Unofficial web-based backup script, mw_tools, by Wanglong (; you can use it to back up your database, or use the backup files to recover the database, the operation is very easy.
  • WikiTeam tools - if you do not have server access (e.g. your wiki is in a free wikifarm), you can generate an XML dump and an image dump using WikiTeam tools (see some saved wikis)
  • FullsitebackupFullsitebackup
  • Another backup script that: dumps DB, files, and XML; puts the site into read-only mode; timestamps backups; and reads the charset from LocalSettings. Script does not need to be modified for each site to be backed up. Does not (yet) rotate old backups. Usage: -d backup/directory -w installation/directory
  • Script to make periodical backups mw_backup. This script will make daily, weekly and monthly backups of your database and images directory when run as a daily cron job.



  1. Manual_talk:Backing_up_a_wiki#Ubuntu_10.10_-_Step_by_Step_Instructions
  2. XML dumps are independent of the database structure, and can be imported into future (and even past) versions of MediaWiki.