Save/Amanda/ZRM
Aller à la navigation
Aller à la recherche
Installation
Le paquet MySQL-zrm est disponible sur le dépôt epel. L'installation se résume à
yum install MySQL-zrm
On va définir un utilisateur MySQL qui sera capable de sauvegarder et de restorer les bases de données.
mysql> SET SESSION old_passwords=0;
mysql> GRANT SELECT, INSERT, UPDATE, CREATE, DROP, RELOAD, SHUTDOWN, ALTER, SUPER, LOCK TABLES, REPLICATION CLIENT ON *.* TO 'backup-user'@'localhost' IDENTIFIED BY 'zrmpasswd';
mysql> GRANT SELECT, INSERT, UPDATE, CREATE, DROP, RELOAD, SHUTDOWN, ALTER, SUPER, LOCK TABLES, REPLICATION CLIENT ON *.* TO 'backup-user'@'192.168.0.89' IDENTIFIED BY 'zrmpasswd';
Configuration
Comme pour Amanda, on va configurer un profil d'exécution que l'on va appelé dailyrun
mkdir /etc/mysql-zrm/dailyrun
cp /etc/mysql-zrm/mysql-zrm.conf /etc/mysql-zrm/dailyrun/
On va éditer maintenant éditer le fichier <path>/etc/mysql-zrm/dailyrun/mysql-zrm.conf</path>, afin de modifier certains paramètres
- Création d'une sauvegarde complète ( non-incrémentale )
backup-level=0
- Sauvegarde logique ( utilisant mysqldump )
backup-mode=logical
- Politique de sauvegarde sur 10 jours
retention-policy=10D
- Compression des sauvegardes
compress=1
- Sauvegarde de toutes les bases de données
all-databases=1
- Utilisateur MySQL pour la sauvegarde
user="backup-user"
password="zrmpasswd"
- Sauvegardes bavardes dans un premier temps. Ceci pourra être remis à 0 une fois en production.
verbose=1
- Envoi de mail une fois la sauvegarde terminée, quelque soit le status
mailto="srs@b2pweb.com"
mail-policy=always
Fichier complet
#
# Template for Zmanda Recovery Manager for MySQL configuration file
#
# Global configuration file is /etc/mysql-zrm/mysql-zrm.conf
# The file should be copied to /etc/mysql-zrm/<backup set name>/mysql-zrm.conf
# if backup set specific modifications are required.
#
# MySQL ZRM configuration file describes the backup configuration for
# a backup set. This file is organized into five sections for convenience
# - Backup parameters,
# - Databases/tables that are part of backup set,
# - MySQL server parameters
# - ZRM parameters.
# - ZRM plugin parameters.
#
# For more information about Zmanda Recovery Manager for MySQL, please
# see mysql-zrm(1) and/or Administration manual at Zmanda Network.
#
#
# Any line starting with '#' are comments and will be ignored
#
# Backup parameters
#
# Backup comment. This is a text string which can be retrieved
# using the mysql-zrm-reporter(1) tool. You can store some notes
# about the backup set.
# This parameter is optional and has no defaults.
#comment=This is a comment
# Backup level. It can be full or incremental
# Use 0 for full and 1 for incremental backups
# This parameter is optional and default value is full backup.
#
backup-level=0
# Backup method
# Values can be "raw" or "logical". Logical backup are backups using
# mysqldump(1) tool
# This parameter is optional and default value is "raw".
#
backup-mode=logical
# Size of LVM snapshot. This parameter is optional and is required only
# for "raw" backup-mode and if the MySQL database data are stored in
# LVM logical volumes.
# A size suffix of k for kilobyte, m for megabyte, g for gigabyte
# or t for terabyte
#
#lvm-snapshot=10M
# specifies the plugin for snapshot operations
#
#snapshot-plugin="/usr/share/mysql-zrm/plugins/lvm-snapshot.pl"
# Specifies the type of backup
# Values can be "regular" or "quick".
# Quick backup type uses the snapshot itself as the backup
# without copying the data from the snapshot volume
#backup-type=quick
# Directory to which backups are done. All backups are stored under this
# directory. This parameter is optional and the default
# value is "/var/lib/mysql-zrm"
#
#destination=/var/lib/mysql-zrm
# Specifies how long the backup should be retained. The value can be
# specified in days (suffix D), weeks (suffix: W), months (suffix: M) or
# years (suffix Y). 30 days in a month and 365 days in a year are assumed
# This parameter is optional and the default is the backups are retained
# forever.
#
retention-policy=10D
# This parameter should be set to 1 if MySQL ZRM backups are being on done on a
# MySQL replication slave.
#replication=1
# This parameter should be set to 1 if backups should be compressed. If this
# parameter is set, gzip(1) command is used by default. If different
# compression algorithm should be used, it must be set in "compress-plugin"
# parameter. Default: There is no data compression.
compress=1
# This specifies the program to be used for compression. The "compression"
# parameter must be set for this parameter to be used. The compression
# command should also support -d option for uncompress backup images. If
# value is not specified then gzip(1) is used for compression.
#compress-plugin=/usr/bin/gzip
# This parameter should be set to 1 if backups should be encrypted.
# The "encrypt-plugin" parameter must be configured. Default: There is no
# data encryption.
#encrypt=1
# This parameter specifies that the program that should be used for
# backup data encryption. "decrypt-option" parameter should also be specified.
#encrypt-plugin="/usr/share/mysql-zrm/plugins/encrypt.pl"
# This specifies the option to be passed to the encryption
# program specified as "encrypt-plugin" parameter for decryption.
#decrypt-option="-d"
#
# Databases/Tables in the backup set
#
# One of the "all-databases" or "databases" or "tables"/"database" parameters
# should be specified. If none of the them are specified, "all-databases"
# is assumed.
#
# This parameter should be set to 1 if all databases are part of this backup set
#
all-databases=1
# List of databases that are part of this backup set. Multiple database
# names are separated by space character. This parameter is ignored if
# "all-databases" is set 1.
#
#databases=wikidb doku
# List of specific tables that are part of this backup set. This parameter
# should not be specified if all tables in the databases in "databases"
# parameter are part of the backup set. Multiple table names should be
# separated by space character. The database to which these tables belong
# to should be specified in "database" parameter.
#
#tables=text user page
#database="wikidb"
#
# The list of databases or tables that are excluded from the backup if the
# database name or table name matches the pattern. Wildcard characters *, ?,
# [, ] are supported. See mysql-zrm-backup man page for details
#
# exclude-pattern=<pattern>
# MySQL server parameters
# MySQL database user used for backup and recovery of the backup set.
# This parameter is optional. If this parameter is not specified, values from
# my.cnf configuration file.
#
user="backup-user"
# MySQL database user password.
# This parameter is optional. If this parameter is not specified, values from
# my.cnf configuration file or no password is used.
#
password="zrmpasswd"
# Fully qualified domain name of the MySQL server.
# This parameter is optional. If this parameter is not specified, values from
# my.cnf configuration file.
#
#host="localhost.company.com"
# Port to which the MySQL server is listening to. This parameter is optional
# and default value is 3306
#
#port=3306
#Name of Socket file that can be used for connecting to MySQL
#
#socket=/var/lib/mysql/mysql.sock
# ssl-options are arguments that are passed to MySQL client commands
# for SSL connection to the MySQL server. This parameter is optional and is
# required only if MySQL server allows SSL connections.
#
#ssl-options="--ssl --ssl-ca=file1 --ssl-cert=file2 --ssl-key=file3"
# This can be set to specify that mysqldump should dump stored routines also.
# This paramter is optional and the default is that stored routines are
# not dumped my mysqldump
#routines=1
# This can be set to 0 to specify that the --single-transaction
# should not be used for mysqldump
#single-transaction=0
# This can be used to specif the character set name that mysqldump should
# use as default. This parameter is optional.
# If not specified utf8 is used as the default character set.
#default-character-set=latin1
# Directory where MySQL commands can be found. The parameter is optional.
#
#mysql-binpath="/opt/lampp/bin"
# Directory where MySQL binary logs can be found. The parameter is optional.
#
#mysql-binlog-path="/var/log/mysql"
# Directory to use for temporary storage. This parameter is optional
#
#tmpdir=/tmp
#
# ZRM parameters
#
# This parameter controls the verbosity of MySQL ZRM logging. The MySQL ZRM logs
# are available at /var/log/mysql-zrm/mysql-zrm.log. This parameter is optional
# default value is 0 (less verbose).
# The valid values are 0 and 1
#
verbose=1
# After a backup run the backup report is emailed to the mailto address
# This parameter is optional and default behavior is not to send mail
# notifications.
#
mailto="srs@b2pweb.com"
# Policy on when the mail should be sent
# Values can be "always", "never" or "only-on-error"
mail-policy=always
# The list of backup reports that are generated after each backup run if
# "html-report-directory" parameter is specified.
# If this parameter is not specified, "backup-status-info" report is generated.
# Valid report names are : backup-method-info, backup-status-info,
# backup-retention-info, backup-performance-info,
# restore-full-info, restore-incr-info,
# replication-info, backup-app-performance-info
# See mysql-zrm-reporter(1) for details of backup reports.
# Multiple report names should be separated by ",".
#
#html-reports=backup-status-info
# Directory in which Text/HTML reports will be created by mysql-zrm-reporter(1)
# tool. If this parameter is specified, the mysql-zrm-reporter(1) creates the
# backup reports in this directory after each successful or unsuccessful
# backup run.
# Text reports will be created under "Text" sub-directory
# HTML reports will be created under "Html" sub-directory
#
#html-report-directory=/var/www/mysql-zrm/reports/
# If backup reports are required as RSS feed, "webserver-url" parameter must
# be specified. The value must be set to a valid location on the web server
# in which HTML reports are located and that URL can be used by
# administrator/user to browse HTML reports and can get to the RSS feeds.
# If this parameter is not specified, backup reports are not generated as
# RSS feeds. The list of reports that are available as RSS feed is specified
# in "html-reports".
#
#webserver-url=http://www.company.com/reports/html/
# Location of RSS header file. Administrators can customize RSS channel
# properties using this file. A template for RSS header is available in
# /usr/share/mysql-zrm/plugins/RSS.header file. Location of RSS header
# must be provided if "webserver-url" is specified.
#
#rss-header-location=/etc/mysql-zrm/
#
# ZRM plugin parameters.
# ZRM provides plugin interfaces to allow MySQL administrators to customize
# the backup to their environment.
#
# COPY plugin: Only one copy-plugin must be configured for a backup set.
#
# Socket Copy plugin is to used to transfer backup files from MySQL server to
# the machine running ZRM for MySQL with sockets.
#
# Please read the Notes at /usr/share/doc/mysql-zrm/README-plugin-socket-copy
#
#copy-plugin=/usr/share/mysql-zrm/plugins/socket-copy.pl
# SSH Copy plugin is to used to transfer backup files from MySQL server to
# the machine running ZRM for MySQL with ssh
#
# Please read the Notes at /usr/share/doc/mysql-zrm/README-plugin-ssh-copy
#
#copy-plugin=/usr/share/mysql-zrm/plugins/ssh-copy.pl
# PRE-BACKUP plugin: Plugin that will be called before a backup run for
# the backup set.
#pre-backup-plugin="/usr/share/mysql-zrm/plugins/pre-backup.pl"
# Set of parameters passed to the pre-backup-plugin. These parameters are
# passed to "pre-backup-plugin" before a backup run for the backup set.
# "pre-backup-plugin" parameter must be specified.
#pre-backup-plugin-options="option1 option2"
# POST-BACKUP plugin: Plugin that will be called after a backup run for
# the backup set.
#post-backup-plugin="/usr/share/mysql-zrm/plugins/post-backup.pl"
# Set of parameters passed to the post-backup-plugin. These parameters are
# passed to "post-backup-plugin" after a backup run for the backup set.
# "post-backup-plugin" parameter must be specified.
#post-backup-plugin-options="option1 option2"
# PRE-SCHEDULER plugin: Plugin that can be used to dynamically determine the
# start time for a backup run.
#pre-scheduler-plugin="/usr/share/mysql-zrm/plugins/pre-scheduler.pl"
# ZRM Plugin configuration parameters
# This parameter is used by the encrypt plugin and
# specifies the file containing the passphrase.
#passfile="/tmp/a.pass"
# This parameter is used by ssh-plugin.pl plugin to specify the user to be
# used to ssh to the remote host
#ssh-user="root"
# This parameter is used by the ssh-copy.pl and socket-copy.pl plugins
# to specify the location of mysql client binaries on the remote host.
#remote-mysql-binpath="/usr/bin"
# This parameter is used by the socket-copy.pl plugin to specify the port
# to be opened on the remote host.
#socket-remote-port="25300"
# This parameter is used by the windows-copy.pl plugin to specify the port
# to be opened on the windows machine during backup
#windows-backup-port="10080"
# This parameter is used by the windows-copy.pl plugin to specify the port
# to be opened on the windows machine during restore
#windows-restore-port="10081"
Sauvergarder
Créer une sauvegarde
On your MySQL Server, as root run ZRM for MySQL to start the dailyrun Backup on the Movies Database.
mysql-zrm-scheduler --now --backup-set dailyrun
schedule:INFO: ZRM for MySQL Community Edition - version 2.2.0
Logging to /var/log/mysql-zrm/mysql-zrm-scheduler.log
backup:INFO: ZRM for MySQL Community Edition - version 2.2.0
dailyrun:backup:INFO: START OF BACKUP
dailyrun:backup:INFO: PHASE START: Initialization
dailyrun:backup:INFO: The quick backup-type is supported only for snapshot backups. Setting backup-type to 'regular'
dailyrun:backup:INFO: Mail address: dfabert@b2pweb.com is ok
dailyrun:backup:INFO: ZRM Temporary configuration file = /etc/mysql-zrm/dailyrun/tmpOs0hP.conf
dailyrun:backup:INFO: {
dailyrun:backup:INFO: quiet=0
dailyrun:backup:INFO: verbose=1
dailyrun:backup:INFO: retention-policy=10D
dailyrun:backup:INFO: backup-level=0
dailyrun:backup:INFO: mailto=srs@b2pweb.com
dailyrun:backup:INFO: all-databases=1
dailyrun:backup:INFO: mail-policy=always
dailyrun:backup:INFO: backup-mode=logical
dailyrun:backup:INFO: password=******
dailyrun:backup:INFO: backup-type=regular
dailyrun:backup:INFO: compress=
dailyrun:backup:INFO: user=backup-user
dailyrun:backup:INFO: }
dailyrun:backup:INFO: Getting mysql variables
dailyrun:backup:INFO: mysqladmin --user="backup-user" --password="*****" variables
dailyrun:backup:INFO: datadir is /var/lib/mysql/
dailyrun:backup:INFO: mysql_version is 5.6.13-log
dailyrun:backup:WARNING: Binary logging is off.
dailyrun:backup:INFO: backup set being used is dailyrun
dailyrun:backup:INFO: backup-set=dailyrun
dailyrun:backup:INFO: backup-date=20130805094038
dailyrun:backup:INFO: mysql-server-os=Linux/Unix
dailyrun:backup:INFO: backup-type=regular
dailyrun:backup:INFO: host=localhost
dailyrun:backup:INFO: backup-date-epoch=1375688438
dailyrun:backup:INFO: retention-policy=10D
dailyrun:backup:INFO: mysql-zrm-version=ZRM for MySQL Community Edition - version 2.2.0
dailyrun:backup:INFO: mysql-version=5.6.13-log
dailyrun:backup:INFO: backup-directory=/var/lib/mysql-zrm/dailyrun/20130805094038
dailyrun:backup:INFO: backup-level=0
dailyrun:backup:INFO: backup-mode=logical
dailyrun:backup:INFO: PHASE END: Initialization
dailyrun:backup:INFO: PHASE START: Running pre backup plugin
dailyrun:backup:INFO: Executing pre-backup-plugin
dailyrun:backup:INFO: PHASE END: Running pre backup plugin
dailyrun:backup:INFO: PHASE START: Flushing logs
dailyrun:backup:INFO: Flushing the logs
dailyrun:backup:INFO: mysqladmin --user="backup-user" --password="*****" flush-logs
Warning: Using a password on the command line interface can be insecure.
dailyrun:backup:INFO: Getting master logname using command mysql --user="backup-user" --password="*****" -e "show master status"
dailyrun:backup:INFO: PHASE END: Flushing logs
dailyrun:backup:INFO: PHASE START: Creating logical backup
dailyrun:backup:INFO: Getting list of Databases
dailyrun:backup:INFO: mysql --user="backup-user" --password="*****" -e "show databases;"
dailyrun:backup:INFO: backup of the following databases will be done mysql performance_schema wikiexploit wikihotline wikisrs
dailyrun:backup:INFO: Command used for logical backup is mysqldump --opt --extended-insert --create-options --default-character-set=utf8 --single-transaction
--user="backup-user" --password="*****" --all-databases > "/var/lib/mysql-zrm/dailyrun/20130805094038/backup.sql"
Warning: Using a password on the command line interface can be insecure.
dailyrun:backup:INFO: Logical backup done for the following database(s)
mysql performance_schema wikiexploit wikihotline wikisrs
dailyrun:backup:INFO: logical-databases=mysql performance_schema wikiexploit wikihotline wikisrs
dailyrun:backup:INFO: PHASE END: Creating logical backup
dailyrun:backup:INFO: PHASE START: Calculating backup size & checksums
dailyrun:backup:INFO: backup-size=31.72 MB
dailyrun:backup:INFO: PHASE END: Calculating backup size & checksums
dailyrun:backup:INFO: PHASE START: Compression/Encryption
dailyrun:backup:INFO: Compressing backup
dailyrun:backup:INFO: Command used is 'tar --same-owner -cpsC "/var/lib/mysql-zrm/dailyrun/20130805094038" --exclude=backup-data --exclude=index
--exclude=zrm_checksum --exclude=backup-sql . 2>/tmp/1do5ZgAqtt | gzip 2>/tmp/bklRrDx3ag > "/var/lib/mysql-zrm/dailyrun/20130805094038/backup-data" 2>/tmp/JZJ03Igqhy'
dailyrun:backup:INFO: compress=
dailyrun:backup:INFO: backup-size-compressed=5.81 MB
dailyrun:backup:INFO: Removing all of the uncompressed/unencrypted data
dailyrun:backup:INFO: PHASE END: Compression/Encryption
dailyrun:backup:INFO: read-locks-time=00:00:01
dailyrun:backup:INFO: flush-logs-time=00:00:00
dailyrun:backup:INFO: compress-encrypt-time=00:00:21
dailyrun:backup:INFO: backup-time=00:00:03
dailyrun:backup:INFO: backup-status=Backup succeeded
dailyrun:backup:INFO: Backup succeeded
dailyrun:backup:INFO: PHASE START: Running post backup plugin
dailyrun:backup:INFO: Executing post-backup-plugin
dailyrun:backup:INFO: PHASE END: Running post backup plugin
dailyrun:backup:INFO: PHASE START: Mailing backup report
dailyrun:backup:INFO: mailing file /tmp/CENnZs7WRi
dailyrun:backup:INFO: mail command is cat "/tmp/CENnZs7WRi"|mail -s "[ZRM for MySQL Report] backup-set dailyrun" srs@b2pweb.com
dailyrun:backup:INFO: PHASE END: Mailing backup report
dailyrun:backup:INFO: PHASE START: Cleanup
dailyrun:backup:INFO: PHASE END: Cleanup
dailyrun:backup:INFO: END OF BACKUP
/usr/bin/mysql-zrm started successfully
Rapports de sauvegardes
- Rapport concis sur le status d'exécution
mysql-zrm-reporter --where backup-set=dailyrun --show backup-status-info
reporter:WARNING: Backup root directory not specified, Assigning default value as /var/lib/mysql-zrm
REPORT TYPE : backup-status-info
backup_set backup_date backup_level backup_status backup_type comment
-----------------------------------------------------------------------------------------------------------------------------
dailyrun Mon 05 Aug 2013 09:40:38 0 Backup succeeded regular ----
AM CEST
- Rapport concis sur le temps d'exécution de la sauvegarde
mysql-zrm-reporter --where backup-set=dailyrun --show backup-performance-info
reporter:WARNING: Backup root directory not specified, Assigning default value as /var/lib/mysql-zrm
REPORT TYPE : backup-performance-info
backup_set backup_date backup_level backup_size backup_size_compressed backup_time backup_type compress_encrypt_time
----------------------------------------------------------------------------------------------------------------------------------------------------------------
dailyrun Mon 05 Aug 2013 09:40:38 0 31.72 MB 5.81 MB 00:00:03 regular 00:00:21
AM CEST
- Rapport sur la vérification du backup
mysql-zrm --action verify-backup --backup-set dailyrun verify-backup:INFO: ZRM for MySQL Community Edition - version 2.2.0 dailyrun:verify-backup:INFO: Verification successful
Tâche planifiée
Il est possible de planifier la sauvegarde
- ajout d'une tâche planifiée de sauvegarde
- Tous les jours
- Démarrage à 01h00
- Sauvegarde complète
mysql-zrm-scheduler --add --interval daily --start 01:00 --backup-level 0 --backup-set dailyrun Logging to /var/log/mysql-zrm/mysql-zrm-scheduler.log DONE
- Vérification de la bonne configuration de la tâche planifiée
-bash-3.1# mysql-zrm-scheduler --query Logging to /var/log/mysql-zrm/mysql-zrm-scheduler.log 0 1 * * * /usr/bin/zrm-pre-scheduler --action backup --backup-set dailyrun --destination /var/lib/mysql-zrm --backup-level 0 --interval daily
Restauration d'une sauvegarde
- Avec le compte root de MySQL, on supprime la base de donnée concernée directement sur le serveur où la sauvegarde doit être restauréeEn effet, les bases ne sont pas restaurées si elles existent déjà.
mysql -e 'DROP DATABASE base'
- On liste les sauvegardes existantes
mysql-zrm-reporter --show restore-info --where backup-set=dailyrun
REPORT TYPE : restore-info
backup_set backup_date backup_level backup_directory backup_status comment
-----------------------------------------------------------------------------------------------------------------------------------------------------
wiki Wed 07 Aug 2013 02:37:25 0 /var/lib/mysql-zrm/dailyrun/20130807143725 Backup succeeded ----
PM CEST
wiki Mon 05 Aug 2013 11:39:53 0 /var/lib/mysql-zrm/dailyrun/20130805113953 Backup failed ----
AM CEST
- On restaure en sélectionnant la sauvegarde qui nous intéresse
mysql-zrm --action restore --backup-set dailyrun --source-directory /var/lib/mysql-zrm/dailyrun/20130807143725
restore:INFO: ZRM for MySQL Community Edition - version 2.1.1
wiki:restore:INFO: The quick backup-type is supported only for snapshot backups. Setting backup-type to 'regular'
wiki:restore:INFO: Mail address: srs@b2pweb.com is ok
wiki:restore:INFO: ZRM Temporary configuration file = /etc/mysql-zrm/wiki/tmpBtcSX.conf
wiki:restore:INFO: {
wiki:restore:INFO: verbose=1
wiki:restore:INFO: retention-policy=10D
wiki:restore:INFO: backup-level=0
wiki:restore:INFO: all-databases=1
wiki:restore:INFO: destination=/var/lib/mysql-zrm
wiki:restore:INFO: mailto=srs@b2pweb.com
wiki:restore:INFO: source-directory=/var/lib/mysql-zrm/dailyrun/20130807143725
wiki:restore:INFO: host=wiki.b2pweb.com
wiki:restore:INFO: mail-policy=always
wiki:restore:INFO: password=******
wiki:restore:INFO: backup-mode=logical
wiki:restore:INFO: backup-type=regular
wiki:restore:INFO: user=backup-user
wiki:restore:INFO: compress=
wiki:restore:INFO: copy-plugin=/usr/share/mysql-zrm/plugins/ssh-copy.pl
wiki:restore:INFO: }
wiki:restore:INFO: Getting mysql variables
wiki:restore:INFO: mysqladmin --user="backup-user" --password="*****" --host="wiki.b2pweb.com" variables
wiki:restore:INFO: datadir is /var/lib/mysql/
wiki:restore:INFO: mysql_version is 5.6.13-log
wiki:restore:WARNING: Binary logging is off.
wiki:restore:INFO: Command used is 'cat "/var/lib/mysql-zrm/dailyrun/20130807143725/backup-data" | gzip -d | tar --same-owner -xpsC "/var/lib/mysql-zrm/wiki/20130807143725" 2>/tmp/KpvgNbcjKU'
wiki:restore:INFO: restoring using command mysql --user="backup-user" --password="*****" --host="wiki.b2pweb.com" -e "set character_set_client=utf8;set character_set_connection=utf8;set character_set_database=utf8;set character_set_results=utf8;set character_set_server=utf8;source /tmp/wEdX27lhm7;"
Warning: Using a password on the command line interface can be insecure.
wiki:restore:INFO: Restored database(s) from logical backup: mysql performance_schema wikiexploit wikihotline wikisrs
wiki:restore:INFO: Removing all of the uncompressed/unencrypted data
wiki:restore:INFO: Restore done in 12 seconds.
- On redémarre mysql
service mysqld start