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 MySQL Databases

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.
 

*UPDATE

I knew 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 I originally had.


Tags:

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

  • FreePBX 17 How To Add a Trunk
  • Docker Container Onboot Policy - How to make sure a container is always running
  • FreePBX 17 How To Add Phones / Extensions and Register
  • Warning: The driver descriptor says the physical block size is 2048 bytes, but Linux says it is 512 bytes. solution
  • Cisco How To Use a Third Party SIP Phone (eg. Avaya, 3CX)
  • Cisco Unified Communication Manager (CUCM) - How To Add Phones
  • pptp / pptpd not working in DD-WRT iptables / router
  • systemd-journald high memory usage solution
  • How to Install FreePBX 17 in Linux Debian Ubuntu Mint Guide
  • How To Install Cisco's CUCM (Cisco Unified Communication Manager) 12 Guide
  • Linux Ubuntu Redhat How To Extract Images from PDF
  • Linux and Windows Dual Boot Issue NIC Won't work After Booting Windows
  • Cisco CME How To Enable ACD hunt groups
  • How to install gns3 on Linux Ubuntu Mint
  • How to convert audio for Asterisk .wav format
  • Using Cisco CME Router with Asterisk as a dial-peer
  • Cisco CME How To Configure SIP Trunk VOIP
  • Virtualbox host Only Network Error Failed to save host network interface parameter - Cannot change gateway IP of host only network
  • Cisco CME and C7200 Router Testing and Learning Environment on Ubuntu 20+ Setup Tutorial Guide
  • Abusive IP ranges blacklist