QA:How to restore data in MySQL or MariaDB

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
Line 5: Line 5:
 
Suppose you have backed-up data into a dump file backup.sql
 
Suppose you have backed-up data into a dump file backup.sql
  
=== Prerequisities ===
+
=== Prerequisites ===
  
 
* make sure a user you are connecting to a database under has enough privileges to create all backed-up tables
 
* make sure a user you are connecting to a database under has enough privileges to create all backed-up tables

Revision as of 04:43, 30 April 2013

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

Contents

Restoring from a dump file

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

Prerequisites

  • 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 (medium size).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

Expected results

After starting the database daemon the data will work.