Manual:Backing up a wiki/es

Es importante que de forma periódica hagas una copia de seguridad de los datos de tu wiki. Esta página describe este proceso para un wiki típico basado en MediaWiki; probablemente quieras hacerte tus propios scripts que se encarguen de esto automáticamente, o usar una frecuencia distinta para esta tarea según el tamaño de tu wiki y tus necesidades particulares.

Sumario
MediaWiki guarda información importante en dos lugares:
 * La base de datos
 * Las páginas y su contenido, los usuarios y sus preferencias personales, metadatos, índice de búsqueda, etc.


 * Sistema de archivos
 * Archivos de configuración del software, apariencias personalizadas, extensiones, imágenes y archivos multimedia (incluyendo los archivos borrados), etc.

Deberías poner tu wiki en modo lectura antes de empezar a crear la copia: mira $wgReadOnly. Esto garantizará que todas las partes de tu copia de seguridad sean consistentes, aunque algunas de las extensiones que tengas instaladas puedan escribir información al disco de todos modos.

Transferencia de archivos
Tendrás que elegir un método para transferir los archivos desde el servidor en el que se encuentran:


 * En el caso de información que no sea privada, puedes simplemente publicarla en archive.org y/o en un directorio  de tu servidor web.
 * SCP (o WinSCP), SFTP/FTP o cualquier otro protocolo de transferencia con el que tengas experiencia o esté disponible.
 * La empresa que hospeda el wiki podría a lo mejor ofrecer una interfaz administrativa accesible con un navegador; consúltales.

Base de datos
La mayor parte de la información vital que contiene el wiki se encuentra en la base de datos, de la que normalmente es bastante sencillo hacer una copia de seguridad. Al usar la interfaz de comunicación integrada para MySQL, la base de datos puede volcarse en un archivo script que puede usar más tarde para recrear desde cero la base de datos y toda la información que contiene.

Mysqldump desde la línea de comandos
La forma más práctica de crear un volcado de la base de datos que quieres copiar es usar la herramienta de volcado estándar de MySQL mysqldump desde la línea de comandos. Asegúrate de usar los parámetros correctos, o tendrás problemas para restaurar la base de datos. Dependiendo del tamaño de la base de datos, mysqldump puede tardar un tiempo considerable.

Antes de nada, añade esta línea a LocalSettings.php: $wgReadOnly = 'Dumping Database, Access will be restored shortly'; Puedes quitar esa línea en cuanto concluya el proceso de volcado de información.

Ejemplo del comando a ejecutar en la línea de comandos de Linux/UNIX: mysqldump -h hostname -u userid -p --default-character-set=whatever dbname > backup.sql Sustituye,  ,   y   según corresponda. Encontrarás el valor de los cuatro parámetros en tu archivo LocalSettings.php. será el valor de $wgDBserver; de forma predeterminada es localhost. será el valor de $wgDBuser, mientras que el valor adecuado de  podrás encontrarlo en $wgDBTableOptions, después de. Si no especificas un valor para, mysqldump probablemente usará utf8 de forma predeterminada, o bien latin1 en el caso de una versión más antigua de MySQL. Por último,  debería ser el valor de $wgDBname. Una vez introducida la orden, mysqldump te pedirá la contraseña para acceder al servidor (que corresponde al valor de $wgDBpassword).

Mira mysqldump para ver una lista completa de los parámetros que admite el comando.

La salida de mysqldump puede pasarse por tubería a gzip para producir un archivo de salida más pequeño, de este modo: 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.

Running mysqldump with 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.

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  lowers the priority of the process.

Use valid values for,  , and. 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.

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

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

Tablas
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.

Conversión Latin-1 a UTF-8
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.

PostgreSQL
You can use the  tool to back up a MediaWiki PostgreSQL database. For example: pg_dump mywiki > mywikidump.sql will dump the  database to mywikidump.sql.

To restore the dump: 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

phpMyAdmin
Turn your wiki to read only by adding  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.

Elimina  de LocalSettings.php

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

Enlaces externos

 * For a tutorial, see Siteground: MySQL Export: How to backup a MySQL database using phpMyAdmin''
 * Backing up the Database

HeidiSQL
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.

Sistema de archivos
MediaWiki stores other components of the wiki in the file system where this is more appropriate than insertion into the database, for example, site configuration files (,  (finally removed in 1.23)), image files (including deleted images, thumbnails and rendered math and SVG images, if applicable), skin customisations, extension files, etc.

The best method to back these up is to place them into an archive file, such as a  file, which can then be compressed if desired. On Windows, applications such as WinZip or 7-zip can be used if preferred.

For Linux variants, assuming the wiki is stored in /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.

Backup the content of the wiki (XML dump)
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).

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, located in the   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. 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  and , you can use MWDumper, which is faster, but requires a Java runtime environment.

See Manual:Importing XML dumps for more information.

Without shell access to the server
If you have no shell access, then use the WikiTeam Python script dumpgenerator.py from a DOS, Unix or Linux command-line. To run the script see the WikiTeam tutorial.

See also Data dumps.

Scripts

 * 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 (allwiki.com); 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)


 * Fullsitebackup


 * 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:


 * 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.

Véase también

 * Manual:Restoring a wiki from backup
 * Manual:Trasladar un wiki
 * Manual:Actualización
 * Manual:Restoring wiki code from cached HTML (if you don't have a successful backup)