MySQL Restoring And Dumping/Backing UP MySQL Data/Tables/Databases

Backing MySQL Databases

Backing Up/Dumping All Mysql Databases To A Single File

mysqldump --all-databases -u admin -p > allmysqldatabases.sql

The "-all-databases" clause is pretty obvious isn't it? It means that it will backup all databases.

The "-u admin" means login using the user "admin", if you have another user such as root or a specific user that can access/dump all databases you can use that one.

The ">allmysqldatabases.sql" part tells it to output all the database information to a file called "allmysqldatabases.sql" and don't forget the ">" as that is redirection and is what writes all the info to a file. Without redirecting the output, you'll see lines and lines of gibberish on your screen, because otherwise MySQL assumes you want to print all the output to the screen.

This method is a quick and dirty way to migrate several databases at once. After that if you want to get fancy, you can gzip your database dump, this will protect against unknown data corruption and of course make the file transfer quicker since compressing with gzip reduces the size.

For example the file was originally 279MB and gzip took it to 179MB.

To gzip your backed up mysql databases just run this command (works on any file other than just .sql dumps of course):

gzip allmysqldatabases.sql and it leaves you with "allmysqldatabases.sql.gz" in compressed gzip format.

Backing Up A Single Mysql Database

mysqldump --databases mysql -u admin -p > mysqlbackup.sql

The "--databases" clause specifies you are going to backup one or more database as specified in the command.

If you wanted databases "mysql" and "someothedb" you would use "--databases mysql someotherdb"

Backing Up A Specific Table

mysqldump -u user -p databasename tablename tablename > thetable.sql

As you can see after specifying the db name you can specific as many tables you want. By default the tables will be populated with the data. If you just want the structure use this instead.

mysqldump -d -u user -p databasename tablename tablename > thetable.sql

The "-d" switch causes only the structure to be dumped.

Restoring MySQL Databases

What fun is backing up without being able to restore? Restoring can be a bit more tricky and there's a few different scenarios and options you have.

I'll focus on the most common one, a new MySQL Server install with no previous data or tables.

I'm assuming you've transferred your database backup "allmysqldatabases.sql.gz"

To restore all your database(s) and information to MySQL just run this following command:

mysql -u root < allmysqldatabases.sql

Restoring a specific MySQL database/script backup to a specific database

mysql -u $username --password="$password" --database="$dbname" < $sqlscript

Issues/Problems/Complications with Restoring MySQLDatabases

One issue I have is that despite backing up and restoring the database "mysql" I cannot authenticate successfully with my old login information. I don't know why because a query of the mysql table shows the usernames I am expecting to see.

I'll have to research more on this point, but the good news is that all the other tables/databases and entries are there as expected.


Iknew everything was there and that the "mysql" table was fully populated. All I had to do was restart mysql server (mysqld) and everything worked as normal with the old passwords and privileges Ioriginally had.


mysql, restoring, dumping, backing, databasesbacking, databases, mysqldump, admin, allmysqldatabases, sql, quot, clause, isn, login, user, output, database, redirection, writes, info, redirecting, ll, gibberish, assumes, method, migrate, gzip, corruption, quicker, compressing, reduces, originally, mb, dumps, gz, compressed, format, mysqlbackup, specifies, specified, someothedb, someotherdb, databasename, tablename, thetable, specifying, db, default, populated, restore, tricky, scenarios, server, install, previous, ve, username, password, dbname, sqlscript, complications, authenticate, successfully, query, usernames, entries, update, restart, mysqld, passwords, privileges,

Latest Articles

  • Linux How To Create A RamDisk
  • mdadm force resync when resync=PENDING solution
  • Proxmox Breaks Storage/LVM Backing If Killing QEMU-IMG
  • Proxmox trying to acquire lock... TASK ERROR: can't lock file '/var/lock/qemu-server/lock-102.conf' - got timeout
  • Debian 9 SSH root password authentication failure password not working problem / solution
  • QEMU / KVM How To Manually Create Basic Virtual Machine VM
  • Linux wlan0 check all wireless clients
  • PHP Issues With Decoding Strange Smart Quotes And Non-Standard ASCII Characters
  • /etc/iproute2/rt_tables default settings file in Linux Centos 6,7 and most other NIX's
  • bind named error solutions named[2169]: error (no valid DS) resolving / error (broken trust chain) resolving / : error (no valid RRSIG) resolving 'com/DS/IN':
  • iptables how to log ALL dropped incoming packets
  • How To Edit Linux Based NM Network Manager Connection Settings Without GUI
  • Linux Disable IPV6 Centos / Debian / Mint Howto
  • Linux use growisofs to burn a larger file on a BD-R / Bluray Disc
  • Linux partprobe/partx cannot access last and 4th partition
  • DRBD Errors Caused By Physical Corruption
  • mdadm: add new device failed for /dev/sdb4 as 3: Invalid argument solution
  • Linux named / bind how to dump, view and clear the cache!
  • Centos 6 / 7 / 8 How To Change Default nameservers in /etc/resolv.conf when using DHCP / dhclient
  • Adobe Acrobat Reader for Linux to use and view XFA Fillable Forms