View source for Manual:Backing up a wiki

<languages/>
<translate>
<!--T:1-->
It is important to make regular '''backups of your wiki''' (data and files). This page provides an overview of the backup process for a typical MediaWiki wiki; you will probably want to devise your own backup scripts or schedule to suit the size of your wiki and your individual needs.</translate>

{{Note
 |1=<translate><!--T:100--> <tvar name=1>{{ll|Help:Export}}</tvar> is a quick and easy way to save all pages on your wiki.</translate>
}}
<translate>
== Overview == <!--T:2-->

<!--T:3-->
MediaWiki stores important data in two places:
;Database : Pages and their contents, users and their preferences, metadata, search index, etc.
;File system : Software configuration files, custom skins, extensions, images (including deleted images), etc.

<!--T:4-->
Consider making the wiki read-only before creating the backup - see <tvar name=readOnly>{{ll|Manual:$wgReadOnly|$wgReadOnly}}</tvar>. This makes sure all parts of your backup are consistent (some of your installed extensions may write data nonetheless).

=== File transfer === <!--T:5-->

<!--T:6-->
You will have to choose a method for transferring files from the server where they are:

<!--T:7-->
*Non-private data you can simply [<tvar name=url>https://github.com/WikiTeam/wikiteam/wiki/Tutorial#user-content-Publishing_the_dump</tvar> publish on archive.org] and/or in a <code>dumps/</code> directory of your webserver.
*SCP (or WinSCP), SFTP/FTP or any other [[Wikipedia:List of file transfer protocols|transfer protocol]] you choose.
*The hosting company might provide a file manager interface via a web browser; check with your provider.

== Database == <!--T:8-->
</translate>
<translate><!--T:9--> ''Most'' of the critical data in the wiki is stored in the database.</translate>
<translate><!--T:123--> If your wiki is currently offline, its database can be backed up by simply copying the database file.</translate>

<translate>
<!--T:124-->
When using the default [[<tvar name=1>Special:MyLanguage/Manual:MySQL</tvar>|MySQL or MariaDB backend]], the database can be ''dumped'' into a script file which can be used later to recreate the database and all the data in it from scratch.
</translate>

=== MySQL ===

====Automysqlbackup====
<translate>
<!--T:83-->
See the package on Debian:
</translate>

<syntaxhighlight lang="shell-session">
$ 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.
[...]
</syntaxhighlight>

<translate>
<!--T:84-->
Install the package:
</translate>

<syntaxhighlight lang="shell-session">
# apt install automysqlbackup
</syntaxhighlight>

<translate>
<!--T:85-->
All your databases will be saved in <tvar name=dir>/var/lib/automysqlbackup/</tvar>:
</translate>

<syntaxhighlight lang="shell-session">
$ find /var/lib/automysqlbackup/
/var/lib/automysqlbackup/
/var/lib/automysqlbackup/weekly
/var/lib/automysqlbackup/weekly/my_wiki
/var/lib/automysqlbackup/weekly/my_wiki/my_wiki_week.18.2016-05-07_15h32m.sql.gz
/var/lib/automysqlbackup/monthly
/var/lib/automysqlbackup/daily
/var/lib/automysqlbackup/daily/my_wiki
</syntaxhighlight>

<translate>
<!--T:86-->
Manual backup:
</translate>

<syntaxhighlight lang="shell-session">
# automysqlbackup
</syntaxhighlight>

<translate>
<!--T:87-->
Restore a database:
</translate>

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

<translate>
<!--T:88-->
For other distributions, see on [<tvar name=url>https://sourceforge.net/projects/automysqlbackup/</tvar> Sourceforge].

====Mysqldump from the command line==== <!--T:11-->

<!--T:12-->
The most convenient way to create a dump file of the database you want to back up is to use the standard MySQL dump tool <tvar name=mysqldump>[http://dev.mysql.com/doc/refman/5.6/en/mysqldump.html mysqldump]</tvar> from the command line. '''Be sure to get the parameters right or you may have difficulty restoring the database.''' Depending on database size, mysqldump could take a considerable amount of time.

<!--T:13-->
First insert the following line into LocalSettings.php
</translate>

<syntaxhighlight lang="php">
$wgReadOnly = 'Dumping Database, Access will be restored shortly';
</syntaxhighlight>

<translate>
<!--T:14-->
this can be removed as soon as the dump is completed.

<!--T:15-->
Example of the command to run on the Linux/UNIX shell:
</translate>

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

<translate><!--T:16--> Substituting <tvar name=1><code>hostname</code></tvar>, <tvar name=2><code>userid</code></tvar>, <tvar name=3><code>charset</code></tvar>, and <tvar name=4><code>dbname</code></tvar> as appropriate.</translate>
<translate><!--T:92--> All four may be found in your <tvar name=1>{{ll|Manual:LocalSettings.php|LocalSettings.php}}</tvar> (LSP) file.</translate>
<translate><!--T:93--> <tvar name=2><code>hostname</code></tvar> may be found under <tvar name=1>{{ll|Manual:$wgDBserver|$wgDBserver}}</tvar>; by default it is localhost.</translate>
<translate><!--T:94--> <tvar name=4><code>userid</code></tvar> may be found under <tvar name=1>{{ll|Manual:$wgDBuser|$wgDBuser}}</tvar>, <tvar name=5><code>charset</code></tvar> may be found under <tvar name=2>{{ll|Manual:$wgDBTableOptions|$wgDBTableOptions}}</tvar>, where it is listed after <tvar name=3><code>DEFAULT CHARSET=</code></tvar>.</translate>
<translate><!--T:95--> If <tvar name=1><code>charset</code></tvar> is not specified mysqldump will likely use the default of utf8, or if using an older version of MySQL, latin1.</translate>
<translate><!--T:96--> While <tvar name=2><code>dbname</code></tvar> may be found under <tvar name=1>{{ll|Manual:$wgDBname|$wgDBname}}</tvar>.</translate>
<translate><!--T:97--> After running this line from the command line mysqldump will prompt for the server password (which may be found under <tvar name=1>{{ll|Manual:$wgDBpassword}}</tvar> in LSP).</translate>

<translate>
<!--T:17-->
See [http://dev.mysql.com/doc/refman/5.6/en/mysqldump.html mysqldump] for a full list of command line parameters.

<!--T:18-->
The output from mysqldump can instead be piped to [[w:gzip|gzip]], for a smaller output file, as follows
</translate>

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

<translate><!--T:129--> Some newer versions of MySQL might show an error about tablespaces and PROCESS privilege.</translate>
<translate><!--T:128--> MediaWiki does not use tablespaces.</translate>
<translate><!--T:136--> The solution is to add the <tvar name="1"><code>--no-tablespaces</code></tvar> option to the command:</translate>

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

<translate>
<!--T:19-->
A similar mysqldump command can be used to produce [[w:XML|XML]] output instead, by including the --xml parameter.
</translate>

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

<translate>
<!--T:20-->
and to compress the file with a pipe to gzip
</translate>

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

<translate>
<!--T:173-->
Additional options you should consider using with <tvar name="1">mysqldump</tvar> for a backup includes the following.
</translate>

{| class="wikitable"
|+ <translate><!--T:171--> Additional <tvar name="1">Mysqldump</tvar> Options</translate>
|-
! <translate><!--T:155--> Option</translate> !! <translate><!--T:156--> Description</translate>
|-
| --default-character-set || <translate><!--T:157--> Specify default character set</translate>
|-
| --no-tablespaces || <translate><!--T:172--> Do not write <tvar name="1">CREATE LOGFILE GROUP</tvar> or <tvar name="2">CREATE TABLESPACE</tvar> statements in output</translate>
|-
| --single-transaction || <translate><!--T:176--> Issue a <tvar name="1">BEGIN SQL</tvar> statement before dumping data from server</translate>
|-
| --triggers || <translate><!--T:158--> Dump triggers for each dumped table</translate>
|-
| --routines || <translate><!--T:159--> Dump stored routines (procedures and functions) from dumped databases</translate>
|-
| --events || <translate><!--T:160--> Dump events from dumped databases</translate>
|-
| --add-drop-table || <translate><!--T:177--> Add <tvar name="1">DROP DATABASE</tvar> statement before each <tvar name="2">CREATE DATABASE</tvar> statement</translate>
|-
| --create-options || <translate><!--T:178--> Include MySQL-specific table options in <tvar name=1>CREATE TABLE</tvar> statements</translate>
|-
| --extended-insert || <translate><!--T:179--> Use multiple-row <tvar name="1">INSERT</tvar> syntax</translate>
|}

<translate>
<!--T:174-->
If you do not use <tvar name="1">--single</tvar>-transaction, then you should consider using the <tvar name="2">--lock</tvar>-tables and <tvar name="3">--add</tvar>-locks options.
</translate>

<translate><!--T:175--> Due to an unexpected change in MySQL versions 5.7.41 and 8.0.32 in February 2023, the <tvar name="1">--single</tvar>-transaction option required the backup user to have <tvar name="2">RELOAD</tvar> or <tvar name="3">FLUSH_TABLES</tvar> privileges.</translate>
<translate><!--T:161--> The issue was fixed in MySQL versions <tvar name="1">5.7.42</tvar> and <tvar name="2">8.0.33</tvar>.</translate>
<translate><!--T:162--> See [<tvar name=url>https://bugs.mysql.com/bug.php?id=109685</tvar> MySQL Bug 109685] and [<tvar name="url2">https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/2003866</tvar> Ubuntu Bug 2003866] for details.</translate>

<translate>
<!--T:21-->
Remember to backup the additional file system components used by the wiki that might be required during a restore, like images, logo, skins and extensions.

====Running mysqldump with Cron==== <!--T:22-->

<!--T:23-->
[[w:Cron|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. 

<!--T:24-->
A sample command that you may run from a [[w:cron|crontab]] may look like this:
</translate>
<pre style="white-space:pre-wrap; word-wrap:break-word;overflow:auto;">
nice -n 19 mysqldump -u $USER --password=$PASSWORD $DATABASE -c | nice -n 19 gzip -9 > ~/backup/wiki-$DATABASE-$(date '+%Y%m%d').sql.gz
</pre>
<translate>
<!--T:25-->
The <code>nice -n 19</code> lowers the priority of the process.

<!--T:26-->
Use valid values for <code>$USER</code>, <code>$PASSWORD</code>, and <code>$DATABASE</code>. 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 [[<tvar name=backup>User:Flominator/Backup MW</tvar>|this one]].
</translate>

{{warning|1=<translate><!--T:27--> Do '''not''' attempt to back up your MediaWiki database using <tvar name=mysqlhotcopy>[http://dev.mysql.com/doc/refman/5.6/en/mysqlhotcopy.html mysqlhotcopy]</tvar>. The table format used by MediaWiki cannot be backed up with this tool, and it will fail silently!</translate>}}

<translate>
<!--T:28-->
If you want to add this task in Cron through Cpanel then you must escape the character "%"
</translate>

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

<translate>
<!--T:29-->
or you will get an error:
</translate>

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

<translate>
====Running mysqldump with Systemd==== <!--T:154-->
</translate>
<translate><!--T:163--> [<tvar name=url>https://mariadb.com/kb/en/systemd/</tvar> Systemd] unifies service configurations and control.</translate>
<translate><!--T:164--> Timers are systemd unit files that control service files or events.</translate>
<translate><!--T:165--> Timers can be used as an alternative to cron.</translate>
<translate><!--T:166--> An example of systemd unit files and backup script is shown below.</translate>

=====wiki-backup.timer=====

<translate>
<!--T:167-->
The following timer runs the wiki-backup service at 5:10 AM every morning.
</translate>

<pre>
$ cat /etc/systemd/system/wiki-backup.timer

[Unit]
Description=Run the backup service once a day
Documentation=...

[Timer]
OnCalendar=*-*-* 05:10:00
RandomizedDelaySec=600
Persistent=true

[Install]
WantedBy=timers.target
</pre>

=====wiki-backup.service=====

<translate><!--T:168--> When the wiki-backup timer fires, then the service is invoked.</translate>
<translate><!--T:169--> The service runs a script located in <tvar name="1"><code>/sbin</code></tvar>.</translate>

<pre>
$ cat /etc/systemd/system/wiki-backup.service

[Unit]
Description=Run the backup service once a day
Documentation=...

[Service]
Type=oneshot
User=root
ExecStart=/sbin/wiki-backup
</pre>

=====wiki-backup script=====

<pre>
$ cat /sbin/wiki-backup

#!/usr/bin/env bash

# Systemd adds random paths at times. Take full control of PATH.
PATH=/bin:/sbin:/usr/bin:/usr/sbin
export PATH

# Read the backup password from conf or ini Failed
wiki_password=...

# Fix the wiki tables just in case. This step produces a lot of noise,
# so send stdout to /dev/null.
if MYSQL_PWD="${wiki_password}" \
   mysqlcheck my_wiki --auto-repair --user=mwuser 1>/dev/null;
then
    echo "Repair wiki database ok"
else
    echo "Failed to repair wiki database"
    echo "Continuing anyways"
fi

# Disable the connection from Apache to MySQL for the dump
if ! systemctl stop apache2.service ;
then
    echo "Failed to stop Apache service"
    echo "Continuing anyways"
fi

# Lock option choice due to MySQL change at versions 5.7.41 and 8.0.32 in
# February 2023. See https://bugs.mysql.com/bug.php?id=109685 and
# https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/2003866.
if mysql --version 2>&1 | grep -q -E 'mysql[[:space:]]+Ver 8\.0\.32'; then
   echo "Using MySQL --lock-tables --add-locks options"
   mysql_lock_opt="--lock-tables --add-locks"
else
   echo "Using MySQL --single-transaction option"
   mysql_lock_opt="--single-transaction"
fi

if MYSQL_PWD="${wiki_password}" \
   mysqldump --no-tablespaces \
     ${mysql_lock_opt} \
     --events --triggers --routines \
     --add-drop-table --create-options \
     --extended-insert \
     --default-character-set=utf8 \
     -u mwuser -h localhost my_wiki | gzip -q -v9 > /backup/wiki-backup.sql.gz ;
then
    echo "Dump wiki database ok"
else
    echo "Failed to dump wiki database"
    echo "Continuing anyways"
fi

# Re-enable connection from Apache to MySQL for the dump
if ! systemctl start apache2.service ;
then
    echo "Failed to start Apache service"
    echo "Continuing anyways"
fi

exit 0
</pre>

<translate>
==== Tables ==== <!--T:30-->

<!--T:31-->
Some of the [[<tvar name=layout>Special:MyLanguage/Manual:Database layout</tvar>|tables]] dumped have different 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 saving disk space (for example, on a large wiki where restoration speed is paramount).

<!--T:32-->
See mailing list thread [[mailarchive:mediawiki-l/2009-March/030415.html|''mysql5 binary schema'']] about the topic.

==== Latin-1 to UTF-8 conversion ==== <!--T:33-->

<!--T:34-->
See the [[<tvar name=1>Special:MyLanguage/Manual:Upgrading#How do I upgrade from a really old version? In one step, or in several steps?</tvar>|relevant section of the upgrading page]] for information about this process. Also see the [[<tvar name=2>Manual talk:Backing up a wiki</tvar>|talk page]] for more information about working with character sets in general.
</translate>

=== PostgreSQL ===
<translate>
<!--T:36-->
You can use the <code>pg_dump</code> tool to back up a MediaWiki PostgreSQL database. For example:
</translate>

 pg_dump mywiki > mywikidump.sql

<translate>
<!--T:37-->
will dump the <code>mywiki</code> database to mywikidump.sql.

<!--T:38-->
To restore the dump:
</translate>

 psql mywiki -f mywikidump.sql

<translate>
<!--T:39-->
You may also want to dump the global information, e.g. the database users:
</translate>

 pg_dumpall --globals > postgres_globals.sql

=== SQLite ===

{{Manual:SQLite/Back-up}}

===phpMyAdmin===
<translate>
<!--T:43-->
Turn your wiki to read only by adding <tvar name=1><syntaxhighlight lang=php inline>$wgReadOnly = 'Site Maintenance';</syntaxhighlight></tvar> to <tvar name=2>LocalSettings.php</tvar>.
</translate>

<translate><!--T:125--> Find the wiki database in <tvar name=1>LocalSettings.php</tvar>.</translate>
<translate><!--T:126--> Here is an example of what this looks like in <tvar name=1>LocalSettings.php</tvar>:</translate>

<syntaxhighlight lang=php>
## Database settings
$wgDBtype           = "mysql";
$wgDBserver         = "localhost";
$wgDBname           = "sashtmax_mw19999";
$wgDBuser           = "sashtmax_mw19999";
$wgDBpassword       = "S7[88p]jJJ";
</syntaxhighlight>

<ol>
<li><translate><!--T:44--> Open the browser to your phpadmin link, login, choose the wiki database.</translate></li>
<li><translate><!--T:106--> Select Export.</translate>

<translate><!--T:107--> Make sure all items under Export are highlighted, and make sure Structure is highlighted (it's important to maintain the table structure).</translate>

''<translate><!--T:108--> Optionally check Add DROP TABLE to delete existing references when importing.</translate>''

<translate><!--T:109--> Make sure Data is checked.</translate>
</li>
<li><translate><!--T:110--> Select zipped.</translate></li>
<li><translate><!--T:111--> Click on GO and save the backup file.</translate><ref>
[[Manual talk:Backing up a wiki#Ubuntu 10.10 - Step by Step Instructions]]
</ref>
</li>
<li><translate><!--T:45--> Remove <tvar name=1><syntaxhighlight lang=php inline>$wgReadOnly = 'Site Maintenance';</syntaxhighlight></tvar> from LocalSettings.php</translate></li>
</ol>

<translate>
<!--T:46-->
Remember to also backup the file system components of the wiki that might be required, e.g. images, logo, and extensions.

====External links==== <!--T:47-->

<!--T:104-->
*[<tvar name=url>https://docs.phpmyadmin.net/en/latest/faq.html#how-can-i-backup-my-database-or-table</tvar> Backing up the Database]
</translate>

===HeidiSQL (alternative to phpMyAdmin) ===

<translate><!--T:50--> [<tvar name=url>http://www.heidisql.com/</tvar> HeidiSQL] is similar to phpMyAdmin, but without any restrictions of phpMyAdmin's free version.</translate>
<translate><!--T:82--> HeidiSQL requires a direct database connection, where some hosts may only offer web interfaces (phpMyAdmin) to firewalled databases.</translate>

<translate>
== File system == <!--T:51-->

<!--T:52-->
MediaWiki stores other components of the wiki in the file system.

<!--T:121-->
The most important of these are:
</translate>

* {{ll|Manual:LocalSettings.php|LocalSettings.php}}
* <translate><!--T:127--> uploaded files in the <tvar name=1><code>images/</code></tvar> directory ''(including deleted files, thumbnails, and rendered math and SVG images, if applicable)''.</translate>

<translate>
<!--T:53-->
The best method to back these up is to place them into an [[wikipedia:archive file|archive]] file, such as a <code>.tar</code> file, which can then be compressed if desired. On Windows, applications such as WinZip or 7-zip can be used.

<!--T:54-->
For Linux variants, assuming the wiki is stored in <tvar name=1><code>/srv/www/htdocs/wiki</code></tvar>
</translate>

<syntaxhighlight lang="shell">
tar zcvhf wikidata.tgz /srv/www/htdocs/wiki
</syntaxhighlight>

<translate>
<!--T:55-->
It should be possible to backup the entire "wiki" folder in "htdocs" if using XAMPP.

=== Configuration files === <!--T:130-->
</translate>
<translate><!--T:137--> <tvar name="1">{{ll|Manual:LocalSettings.php|LocalSettings.php}}</tvar> is the most important of these, but a wiki might also have things like <tvar name="2"><code>.htaccess</code></tvar> or other web server configuration files that should be backed up.</translate>

<translate>
=== Uploaded files === <!--T:131-->
</translate>
<translate><!--T:138--> Files uploaded to the wiki are by default put into the <tvar name="1"><code>images/</code></tvar> directory, separated into subdirectories such as <tvar name="2"><code>images/8/8f</code></tvar>.</translate>
<translate><!--T:139--> There are also other directories such as <tvar name="1"><code>images/archive/</code></tvar> and <tvar name="2"><code>images/deleted/</code></tvar>.</translate>
<translate><!--T:140--> These should all be backed up.</translate>

<translate><!--T:141--> The <tvar name="1"><code>images/thumb/</code></tvar> can be backed up along with everything else, but can optionally be excluded in order to save backup space.</translate>
<translate><!--T:142--> This directory stores the derived thumbnails of images and other files; generally multiple thumbnails per wiki file.</translate>
<translate><!--T:143--> After restoring from backup, these thumbnails will be recreated as required (although depending on <tvar name="1">{{ll|Manual:$wgGenerateThumbnailOnParse|$wgGenerateThumbnailOnParse}}</tvar> this may need to be a manual process).</translate>

<translate>
== Backup the content of the wiki (XML dump) == <!--T:56-->

<!--T:57-->
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).<ref>XML dumps are independent of the database structure, and can be imported into future (and even past) versions of MediaWiki.</ref> 

<!--T:77-->
XML dumps are less likely to cause problems with [[wikipedia:character encoding|character encoding]], as a means of transferring large amounts of content quickly, and can easily be used by third party tools, which makes XML dumps a good fallback should your main database dump become unusable.
</translate>

<translate><!--T:58--> To create an XML dump, use the command-line tool <tvar name=1><code>{{ll|Manual:dumpBackup.php|dumpBackup.php}}</code></tvar>, located in the <tvar name=2><code>maintenance</code></tvar> directory of your MediaWiki installation.</translate>
<translate><!--T:101--> See <tvar name=1>{{ll|Manual:dumpBackup.php}}</tvar> for more details.</translate>

<translate>
<!--T:59-->
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.
</translate>

<translate><!--T:60--> To import an XML dump into a wiki, use the command-line tool <tvar name=1><code>{{ll|Manual:importDump.php|importDump.php}}</code></tvar>.</translate>
<translate><!--T:102--> 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).</translate>

''<translate><!--T:115--> See <tvar name=1>{{ll|Manual:Importing XML dumps}}</tvar> for more information.</translate>''

<translate>
===Without shell access to the server=== <!--T:62-->
</translate>
==== MediaWiki Dump Generator ====
<translate><!--T:170--> If you have no shell access, use the MediaWiki Client Tools' [<tvar name="url1">https://github.com/mediawiki-client-tools/mediawiki-dump-generator</tvar> MediaWiki Dump Generator] dumpgenerator script.</translate>
<translate><!--T:132--> It is run from the command-line in a terminal.</translate>

<translate><!--T:133--> The XML dump can include full or only most recent page history.</translate>
<translate><!--T:134--> The images dump will contain all file types with associated descriptions.</translate>
<translate><!--T:144--> The <tvar name="1"><code>siteinfo.json</code></tvar> and <tvar name="2"><code>SpecialVersion.html</code></tvar> files will contain information about wiki features such as the installed extensions and skins.</translate>
<translate><!--T:135--> User account information won't be preserved.</translate>

<translate>
<!--T:145-->
Full instructions are at the MediaWiki Client Tools' [<tvar name=url>https://github.com/mediawiki-client-tools/mediawiki-dump-generator/blob/python3/USAGE.md</tvar> MediaWiki Dump Generator] GitHub repository.

<!--T:64-->
See also [[Meta:Data dumps]].

== Scripts == <!--T:65-->
</translate>
{{warning|1=<translate><!--T:66--> Use these at your own risk. Check your wiki's <tvar name=1>{{ll|Manual:LocalSettings.php|LocalSettings.php}}</tvar> for the correct character set to use, as you may need to edit the script to suit.</translate>}}
<translate>
<!--T:68-->
*[[User:Flominator/Backup MW|Unofficial backup script]] by [[User:Flominator|Flominator]]; creates a backup of all files and the database, with optional backup rotation.</translate> Shell script, last updated 2012.
<translate>
<!--T:73-->
* Another [<tvar name=url>https://github.com/samwilson/MediaWiki_Backup</tvar> backup script] that: dumps DB, files (just pictures by default, option to include all files in installation), and XML; puts the site into read-only mode; timestamps backups; and reads the charset from LocalSettings.</translate> <translate><!--T:116--> Script does not need to be modified for each site to be backed up.</translate> <translate><!--T:117--> Does not (yet) rotate old backups.</translate> <translate><!--T:118--> Usage: <tvar name=1><syntaxhighlight lang="bash" inline style="white-space:nowrap">backup.sh -d backup/directory -w installation/directory</syntaxhighlight></tvar>.</translate> <translate><!--T:119--> Also provides a script to restore a backup <tvar name=1><syntaxhighlight lang="bash" inline style="white-space:nowrap">restore.sh -a backup/directory/dated_archive.tar.gz -w installation/directory</syntaxhighlight></tvar>.</translate> <translate><!--T:146--> Shell script, last updated 2013.</translate>
<translate>
<!--T:69-->
*[[User:Darizotas/MediaWiki Backup Script for Windows]] - a script for backing up a Windows MediaWiki install. Note: Has no restore feature.</translate> <translate><!--T:147--> Shell script, last updated 2015.</translate>
<translate>
<!--T:67-->
*[[<tvar name=script>Special:MyLanguage/Manual:Backing up a wiki/Duesentrieb's backup script</tvar>|Unofficial backup script]] by [[User:Duesentrieb]].</translate> <translate><!--T:148--> Shell script, last updated 2016.</translate>
<translate>
<!--T:74-->
* Script to make periodical backups [<tvar name=url>https://github.com/nischayn22/mw_backup</tvar> mw_backup]. This script will make daily, weekly and monthly backups of your database and images directory when run as a daily cron job.</translate> <translate><!--T:149--> PHP script, last updated 2017.</translate>
<translate>
<!--T:98-->
* Another unofficial {{<tvar name=1>ll|Manual:Backing up a wiki/Lanthanis backup CMD</tvar>|MediaWiki backup script for Windows}} by <tvar name=2>[[User:Lanthanis|Lanthanis]]</tvar> that: exports the pages of specified namespaces as an XML file; dumps specified database tables; and adds further specified folders and files to a ZIP backup file.</translate> <translate><!--T:99--> Can be used with Windows task scheduler.</translate> <translate><!--T:150--> Last updated 2019.</translate>
<translate>
<!--T:71-->
*[<tvar name=wikiteam>https://github.com/WikiTeam/wikiteam</tvar> 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 dumpgenerator from WikiTeam tools, (Python 2). See [<tvar name=backups>https://github.com/WikiTeam/wikiteam/wiki/Available-Backups</tvar> some saved wikis].</translate> <translate><!--T:151--> Python 2 script.</translate>
* [https://github.com/mediawiki-client-tools/mediawiki-dump-generator MediaWiki Dump Generator] - <translate><!--T:152--> 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 dumpgenerator from Mediawiki Client Tools, Python 3 script, last update 2023.</translate>

<translate>
== Extensions == <!--T:112-->
</translate>
* {{Ll|Extension:DumpsOnDemand}} – <translate><!--T:113--> Allows users to generate and download database dumps</translate>
* {{Ll|Extension:DataDump}} – <translate><!--T:114--> Allows users to generate and download XML and file/image dumps</translate>

<translate>
==See also== <!--T:75-->
</translate>
* <translate><!--T:153--> <tvar name="1">{{ll|Help:Export}}</tvar> is a quick and easy way to save all pages on your wiki.</translate>
* {{ll|Manual:Restoring a wiki from backup}}
* {{ll|Manual:Moving a wiki}}
* {{ll|Manual:Upgrading}}
* {{ll|Manual:Restoring wiki code from cached HTML}} — <translate><!--T:81--> if you don't have a successful backup</translate>
* {{ll|Exporting all the files of a wiki}}

<translate>
==References== <!--T:76-->
</translate>
<references/>

[[Category:Import/Export{{#translation:}}|{{PAGENAME}}]]
[[Category:MediaWiki for site admins{{#translation:}}]]