The mysqlbackup commands to perform a restore
copy-back (for directory backup
only; see Section 5.1.6, “Advanced: Preparing and Restoring a Directory Backup”). Normally, the
restoration process requires the database server to be already
shut down (or, at least not operating on the directory you are
restoring the data to), except for restorations of backups created
--use-tts option; see
explanations below. The
process copies the data files, logs, and other backed-up files
from the backup directory back to their original locations, and
performs any required post-processing on them.
Example 5.1 Restoring a Database
mysqlbackup --defaults-file=<my.cnf> -uroot --backup-image=<image_name> \ --backup-dir=<backupTmpDir> --datadir=<restoreDir> copy-back-and-apply-log
achieves two things:
Extracts the backup from the image file and copies it to the data directory on the server to be restored.
Performs an apply log operation to the restored data to bring them up-to-date.
The restored data includes the
table, where MySQL Enterprise Backup records details of each backup. The table
allows you to perform future incremental backups using the
When performing a restore, make sure the target data directories are all clean, containing no old or unwanted data files (this might require manual removal of files at the locations specified by the
--innodb_undo_directoryoptions). The same cleanup is not required for restoring backups created with the
--use-ttsoption (in which case other requirements described in Section 5.1.4, “Restoring Backups Created with the
--use-ttsOption” apply though).
Due to a known issue (Bug# 20485910), restoring a partial image backup created with MySQL Enterprise Backup 3.11 or earlier requires using the
The following subsections describe a number of different scenarios for restoring a backup.