This article covers a version of Ubuntu that is no longer supported. If you are currently operate a server running Ubuntu 12.04, we highly recommend upgrading or migrating to a supported version of Ubuntu:
Reason: Ubuntu 12.04 reached end of life (EOL) on April 28, 2017 and no longer receives security patches or updates. This guide is no longer maintained.
This guide might still be useful as a reference, but may not work on other Ubuntu releases. If available, we strongly recommend using a guide written for the version of Ubuntu you are using. You can use the search functionality at the top of the page to find a more recent version.
MySQL is a popular database management solution that uses the SQL querying language to access and manipulate data. It can easily be used to manage the data from websites or applications.
Backups are important with any kind of data, and this is especially relevant when talking about databases. MySQL can be backed up in a few different ways that we will discuss in this article.
For this tutorial, we will be using an Ubuntu 12.04 VPS with MySQL 5.5 installed. Most modern distributions and recent versions of MySQL should operate in a similar manner.
One of the most common ways of backing up with MySQL is to use a command called "mysqldump".
There is an article on how to export databases using mysqldump here. The basic syntax of the command is:
mysqldump -u username -p database_to_backup > backup_name.sql
To restore a database dump created with mysqldump, you simply have to redirect the file into MySQL again.
We need to create a blank database to house the imported data. First, log into MySQL by typing:
mysql -u username -p
Create a new database which will hold all of the data from the data dump and then exit out of the MySQL prompt:
CREATE DATABASE database_name; exit
Next, we can redirect the dump file into our newly created database by issuing the following command:
mysql -u username -p database_name < backup_name.sql
Your information should now be restored to the database you've created.
You can save the data from a table directly into a text file by using the select statement within MySQL.
The general syntax for this operation is:
SELECT * INTO OUTFILE 'table_backup_file' FROM name_of_table;
This operation will save the table data to a file on the MySQL server. It will fail if there is already a file with the name chosen.
Note: This option only saves table data. If your table structure is complex and must be preserved, it is best to use another method!
There is a utility program called "automysqlbackup" that is available in the Ubuntu repositories.
This utility can be scheduled to automatically perform backups at regular intervals.
To install this program, type the following into the terminal:
sudo apt-get install automysqlbackup
Run the command by typing:
The main configuration file for automysqlbackup is located at "/etc/default/automysqlbackup". Open it with administrative privileges:
sudo nano /etc/default/automysqlbackup
You can see that this file, by default, assigns many variables by the MySQL file located at "/etc/mysql/debian.cnf". This contains maintenance login information
From this file, it reads the user, password, and databases that must be backed up.
The default location for backups is "/var/lib/automysqlbackup". Search this directory to see the structure of the backups:
daily monthly weekly
If we look into the daily directory, we can see a subdirectory for each database, inside of which is a gzipped sql dump from when the command was run:
ls -R /var/lib/automysqlbackup/daily
.: database_name information_schema performance_schema ./database_name: database_name_2013-08-27_23h30m.Tuesday.sql.gz ./information_schema: information_schema_2013-08-27_23h30m.Tuesday.sql.gz ./performance_schema: performance_schema_2013-08-27_23h30m.Tuesday.sql.gz
Ubuntu installs a cron script with this program that will run it every day. It will organize the files to the appropriate directory.
It is possible to use MySQL replication to backup data with the above techniques.
While replication allows for data mirroring, it suffers when you are trying to save a specific point in time. This is because it is constantly replicating the changes of a dynamic system.
To avoid this problem, we can either:
You can disable replication for the slave temporarily by issuing:
mysqladmin -u user_name -p stop-slave
Another option, which doesn't completely stop replication, but puts it on pause, so to speak, can be accomplished by typing:
mysql -u user_name -p -e 'STOP SLAVE SQL_THREAD;'
After replication is halted, you can backup using one of the methods above. This allows you to keep the master MySQL database online while the slave is backed up.
When this is complete, restart replication by typing:
mysqladmin -u user_name -p start-slave
You can also ensure a consistent set of data within the server by making the data read-only temporarily.
You can perform these steps on either the master or the slave systems.
First, log into MySQL with enough privileges to manipulate the data:
mysql -u root -p
Next, we can write all of the cached changes to the disk and set the system read-only by typing:
FLUSH TABLES WITH READ LOCK; SET GLOBAL read_only = ON;
Now, perform your backup using mysqldump.
Once the backup is complete, return the system to its original working order by typing:
SET GLOBAL read_only = OFF; UNLOCK TABLES;
MySQL includes a perl script for backing up databases quickly called "mysqlhotcopy". This tool can be used to quickly backup a database on a local machine, but it has limitations that make us avoid recommending it.
The most important reason we won't cover mysqlhotcopy's usage here is because it only works for data stored using the "MyISAM" and "Archive" storage engines.
Most users do not change the storage engine for their databases and, starting with MySQL 5.5, the default storage engine is "InnoDB". This type of database cannot be backed up using mysqlhotcopy.
Another limitation of this script is that it can only be run on the same machine that the database storage is kept. This prevents running backups from a remote machine, which can be a major limitation in some circumstances.
Another method sometimes suggested is simply copying the table files that MySQL stores its data in.
This approach suffers for one of the same reasons as "mysqlhotcopy".
While it is reasonable to use this technique with storage engines that store their data in files, InnoDB, the new default storage engine, cannot be backed up in this way.
There are many different methods of performing backups in MySQL. All have their benefits and weaknesses, but some are much easier to implement and more broadly useful than others.
The backup scheme you choose to deploy will depend heavily on your individual needs and resources, as well as your production environment. Whatever method you decide on, be sure to validate your backups and practice restoring the data, so that you can be sure that the process is functioning correctly.
Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in our Questions & Answers section, find tutorials and tools that will help you grow as a developer and scale your project or business, and subscribe to topics of interest.Sign up
Click below to sign up and get $100 of credit to try our products over 60 days!