From Fedora Project Wiki

Revision as of 06:21, 23 April 2013 by Hhorak (talk | contribs) (Created page with "For restoring backed-up data choose one of the methods bellow, depending which way you have chosen for back-up. == Restoring from a dump file == Suppose you have backed-up d...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

For restoring backed-up data choose one of the methods bellow, depending which way you have chosen for back-up.

Restoring from a dump file

Suppose you have backed-up data into a dump file backup.sql

Prerequisities

  • make sure a user you are connecting to a database under has enough privileges to create all backed-up tables

Restoring the data

$ mysql -u root -p < backup.sql

Restoring from copied binary files

Warning.png
When to use copying binary files
Copying pure binary files as a backup should work fine in case we will restore them on the same minor version of MySQL or MariaDB daemon. So it is OK to move data stack this way when switching from MySQL to MariaDB or back, but you should use dump and restore alternative when ugrading from 5.1 to 5.5 or similar.

Suppose you have copied the data stack to a location /save/directory/mysql. We should also pay attention on SELinux context, so running restoreconf is a good idea.

# cp -r /save/directory/mysql /var/lib/mysql
# restoreconf -r /var/lib/mysql