MySQL 5.1 Reference Manual :: 8 Client and Utility Programs :: 8.13 mysqldump — A Database Backup Program

shell> mysqldump [options] db_name [tables]
shell> mysqldump [options] --databases db_name1 [db_name2 db_name3...]
shell> mysqldump [options] --all-databases

shell> mysqldump db_name > backup-file.sql

shell> mysql db_name backup-file.sql

shell> mysql -e "source /path-to-backup/backup-file.sql" db_name

shell> mysqldump --opt db_name | mysql --host=remote_host -C db_name

shell> mysqldump --databases db_name1 [db_name2 ...] > my_databases.sql

shell> mysqldump --all-databases > all_databases.sql

shell> mysqldump --all-databases --single-transaction > all_databases.sql

shell> mysqldump --all-databases --master-data=2 > all_databases.sql

shell> mysqldump --all-databases --flush-logs --master-data=2
              > all_databases.sql

Previous / Next / Up / Table of Contents

User Comments

Posted by [name withheld] on August 10 2002 7:56am

[Delete] [Edit]

If you want to compress your backups directly even
without hitting your HD. You can try this command:
#mysqldump --opt -u user --password="password"
database | bzip2 -c > database.sql.bz2

Posted by [name withheld] on October 27 2002 11:33am

[Delete] [Edit]

I'm using the following script as daily cron, it works.

#!/bin/sh
date=`date -I`
mysqldump --opt --all-databases | bzip2 -c
> /var/backup/databasebackup-$date.sql.bz2

Posted by P J on February 21 2003 2:17pm

[Delete] [Edit]

To dump only select records into a file based on a timestamp field you can use this (last_modified is the timestamp field). This is used in a shell script to be used as a cron to take records that are more than a month old and dump them into an archive file (then the dumped records are deleted).
/yourpath/mysqldump "--where=(month(last_modified)+year(last_modified)*12 month(current_date)+(year(current_date)*12)-1)" database table > archive.sql

Posted by Alexander Keremidarski on December 14 2003 8:55pm

[Delete] [Edit]

To P J

Your example is very bad. There is much more elegant way and also in your example no index can be used to optimize query.


Here is better where clause to "take records that are more than a month old"

WHERE last_modified or
WHERE last_modified
depending on time resolution needed.

Posted by christopher sagayam on January 9 2004 12:50am

[Delete] [Edit]

for "mysqldump" ing innodb tables

take the dump as you would normally do using mysqldump

open the dump file put this statement at the beginning

SET FOREIGN_KEY_CHECKS=0;

of the sql dump text file

and import the same file as you would nomally import an sql dump file

Posted by Don Vu on January 27 2004 12:15pm

[Delete] [Edit]

If you have a value for "database=" in your my.cnf file mysqldump will not work and will give you error "mysqldump: option `--databases' doesn't allow an argument".

Posted by Jason Dias on February 16 2004 12:33pm

[Delete] [Edit]

For a faster "mysqldump" innodb tables
1. mysqldump --opt --user=username --password database > filetosaveto.sql

2. open the dump file put this statement at the beginning of the sql dump text file:

SET FOREIGN_KEY_CHECKS=0;

3. mysql --user=username --password database
Very fast.

Posted by Tim To on February 24 2004 10:56am

[Delete] [Edit]

After adding "SET FOREIGN_KEY_CHECKS=0;" remember to append the "SET FOREIGN_KEY_CHECKS=1;" at the end of the import file. The potential problem is that any data inconsistency that would've made the foreign key failed during import would have made it into the database even after the forieng keys are turned back on. This is especially true if the foreign keys aren't turned back on after a long period of time which can happen if the "SET FOREIGN_KEY_CHECKS=1;" was not appended to the import file in the first place.

Posted by Christopher Huhn on July 1 2004 12:18pm

[Delete] [Edit]

You can even do your mysqldump backups with logrotate.
Simply put something like this into /etc/logrotate.conf:

/var/backups/mysql/dump.sql {
daily
rotate 14
missingok
compress
postrotate
/usr/bin/mysqldump --defaults-extra-file=/.../backup-credentials.cnf --opt --flush-logs --all-databases > /var/backups/mysql/dump.sql
endscript
}

Posted by Vesa Kivistö on August 26 2004 7:06pm

[Delete] [Edit]

Following mysqldump import example for InnoDB tables is at least 100x faster than previous examples.


1. mysqldump --opt --user=username --password database > dumbfile.sql


2. Edit the dump file and put these lines at the beginning:

SET AUTOCOMMIT = 0;
SET FOREIGN_KEY_CHECKS=0;


3. Put these lines at the end:

SET FOREIGN_KEY_CHECKS = 1;
COMMIT;
SET AUTOCOMMIT = 1;


4. mysql --user=username --password database

Posted by Stefan Rindeskar on September 7 2004 2:31pm

[Delete] [Edit]

Notice that from 4.1 the default behaviour for mysqldump has changed.
In 4.0 all variables was FALSE by default and you could for example use the short -e to start using extended inserts.
In 4.1 this and several other mysql specific variables are set to TRUE by default.

If you want to set them to FALSE again you have two choices:
Either create a default file where you turn of the variables that you choose.

Or you can use the long variable name combined with a value like this:
mysqldump --extended-insert=FALSE

This works for all variables that controls the behaviour of mysqldump which can be found at the end of a "mysqldump --help" listing.

Posted by David Goldfeder on February 8 2005 4:52pm

[Delete] [Edit]

If you're using phpMyAdmin's PDF and MIME type features and you're dumping those tables, you need to use the --allow-keywords options. The pma_history table created for those features has a column named "table" and if you dump without the --allow-keywords you'll get a syntax error when you try to import them later.

Posted by Corey Tisdale on February 23 2005 3:53pm

[Delete] [Edit]

If you want to schedule a task on windows to backup and move your data somewhere, the lack of documentation and command-line tools in windows can make it a real beast. I hope this helps you keep your data safe.

First off, you will need a command line file compressor (or your should use one, anyway). I like GNU gzip. You can get it for windows here http://gnuwin32.sourceforge.net/packages/gzip.htm

Secondly, you will need to use windowsw FTP via command line. It took me all day to find documentation on this guy, so I hope this saves some time for somebody.

Anyway, you need two files -- the batch file and a script for your ftp client. The Batch file should look like this guy (it uses random numbers in the file name so that multiple backups are not overwritten):



@ECHO OFF

@REM Set dir variables. Use ~1 format in win2k
SET basedir=C:\BACKUP~1
SET workdir=c:\TEMP
SET mysqldir=c:\mysql\bin
SET gzipdir=c:\PROGRA~1\GnuWin32\bin
SET mysqlpassword=mygoodpassword
SET mysqluser=myrootuser

@REM Change to mysqldir
CD %mysqldir%

@REM dump database. This is all one line
mysqldump -u %mysqluser% -p%mysqlpassword% --all-databases >%workdir%\backup.sql

@REM Change to workdir
CD %workdir%

@REM Zip up database
%gzipdir%\gzip.exe backup.sql

@REM Move to random file name
MOVE backup.sql.gz backup.%random%.gz

@REM FTP file to repository
FTP -n -s:%basedir%\ftp-commands.txt

@REM Remove old backup files
del backup.sql
del backup.*.gz

@REM Change back to base dir
CD %basedir%



And your ftp script should look like this guy (and be named ftp-commands.txt so the above script can find it)



open
ftp.mybackuplocation.com
user
myusername
mypassword
bin
put backup.*.gz
quit



Make sure both of the above files are in whatever directory you set up as %basedir% and test it out and make sure everything works for you. Then schedule it to run every day to protect your data!

Posted by Lon B on March 1 2005 2:29pm

[Delete] [Edit]

Corey's example is helpful, but I don't care for the random file name. Here is the manual script I use on Windows for kicking off a MYSQL backup.

You could easily add all the other bells and whistles of ZIP, FTP, and scheduling should you need it. Note that I didn't use a password or many of the other args for mysqldump, you can add those if ya need 'em.

@ECHO OFF
for /f "tokens=1-4 delims=/ " %%a in ('date/t') do (
set dw=%%a
set mm=%%b
set dd=%%c
set yy=%%d
)

SET bkupdir=C:\path\to\where\you\want\backups
SET mysqldir=D:\path\to\mysql
SET dbname=this_is_the_name_of_my_database
SET dbuser=this_is_my_user_name

@ECHO Beginning backup of %dbname%...

%mysqldir%\bin\mysqldump -B %dbname% -u %dbuser% > %bkupdir%\dbBkup_%dbname%_%yy%%mm%%dd%.sql
@ECHO Done! New File: dbBkup_%dbname%_%yy%%mm%%dd%.sql
pause

Posted by David Tonhofer on March 4 2005 4:45pm

[Delete] [Edit]

A little reformulation of the actions that occur during an online dump with log-point registration, i.e. a dump that does not unduly disturb clients using the database during the dump (N.B.: only from 4.1.8 on!) and that can be used to start a slave server from the correct point in the logs.

Use these options:

--single-transaction
--flush-logs
--master-data=1
--delete-master-logs

If you have several databases that are binary-logged and you want to keep a consistent binary log you may have to include all the databases instead of just some (is that really so?):

--all-databases

Now, these are the actions performed by the master server:

1) Acquire global read lock using FLUSH TABLES WITH READ LOCK. This also flushes the query cache and the query result cache. Caused by option --single-transaction.
2) All running and outstanding transactions terminate. MySQL server stalls for further updates.
3) Read lock on all tables acquired.
4) All the logs are flushed, in particular the binary log is closed and a new generation binary log is opened. Caused by option --flush-logs
5) Binary lock coordinates are read and written out so that the slave can position correctly in the binary log. Caused by --master-data=1
6) Read lock is released, MySQL server can proceed with updates. These updates will also go to the binary log and can thus be replayed by the slave. Meanwhile, the InnoDB tables are dumped in a consistent state, which is the state they were in in step 5. (Not guaranteed for MyISAM tables)
7) Dump terminates after a possibly long time.
8) Any old binary log files are deleted. Caused by --delete-master-logs.

Additionally, there are performance-influencing options:

--extended-insert: use multiple-row insert statements
--quick: do not do buffering of row data, good if tables are large

And there are format-influencing options:

--hex-blob: dump binary columns in hex
--complete-insert: use complete insert statements that include column names works nicely with --extended-insert
--add-drop-table: add a DROP TABLE statement before each CREATE TABLE statement.

Posted by James Day on March 9 2005 9:53am

[Delete] [Edit]

4.1 to earlier version backwards compabibility: Bug 203 notes that database names are only quoted using -q from mysqldump version 10.1 (part of 4.1) because the mysql command line program does not support quoted database names until version 13.0. Version 12 is the one distributed with 4.0. This can be a problem if you are using mysqldump 10.1 and need quoted table and field names but can't have quoted database names for import into a 4.0 or earlier server. Using the later mysql client program on the destination or the earlier mysqldump version on the source may be a workaround.

Bug 203: http://bugs.mysql.com/bug.php?id=203

Posted by Mike Ng on May 16 2005 5:40pm

[Delete] [Edit]

Following Lon B helpful post:

You can pipe it to gzip to compress in windows. I didn't think it would work on windows, but apparently it does.

@ECHO Beginning backup of %dbname%...

%mysqldir%\bin\mysqldump -B %dbname% -u %dbuser% | gzip> %bkupdir%\dbBkup_%dbname%_%yy%%mm%%dd%.sql.gz

Of course,you need gng gzip in your path or directory.

Posted by Eric Martel on January 16 2006 4:10pm

[Delete] [Edit]

When using mysqldump on a replication master, if you want the slave(s) to follow, you may want to avoid the --delete-master-logs option, because it can delete binary logs before the "CHANGE MASTER" is read by the slaves, therefore breaking the replication (then you have to issue manually the "CHANGE MASTER" on the slave(s)). If you want to get rid of old and useless binary logs, it is better to issue a "PURGE MASTER" SQL command on the master after the mysqldump.

Posted by Wade Hedgren on January 22 2006 6:02am

[Delete] [Edit]

I moved my MySQL installation from Linux to Windows 2003 and had to create a new backup script. I was using hotcopy but with windows it's not avaliable.

So, Inspired by Lon B and Corey Tisdale (above) I created a batch file that will create a mysqldump GZiped file for each database and put them into seperate folders. It also creates a log file. You will have to set the vars at the top to match your system.

You will also need GZip to do the compression...

It could still use some work (like no error trapping etc...) but it's in production for me now.

I used a utility "commail.exe" to send the log file to me after the backup is complete.

//--- Begin Batch File ---//
@echo off

:: Set some variables
set bkupdir=E:\MySQL\backup
set mysqldir=E:\MySQL
set datadir=E:\MySQL\data
set logdir=E:\MySQL\logs
set dbuser=username
set dbpass=password
set zip=C:\GZip\bin\gzip.exe
set endtime=0

:GETTIME

:: get the date and then parse it into variables
for /F "tokens=2-4 delims=/ " %%i in ('date /t') do (
set mm=%%i
set dd=%%j
set yy=%%k
)

:: get the time and then parse it into variables
for /F "tokens=5-8 delims=:. " %%i in ('echo.^| time ^| find "current" ') do (
set hh=%%i
set ii=%%j
set ss=%%k
)

:: If this is the second time through then go to the end of the file
if "%endtime%"=="1" goto END

:: Create the filename suffix
set fn=_%yy%%mm%%dd%_%hh%%mm%%ss%

:: Switch to the data directory to enumerate the folders
pushd %datadir%

:: Write to the log file
echo Beginning MySQLDump Process > %logdir%\LOG%fn%.txt
echo Start Time = %yy%-%mm%-%dd% %hh%:%ii%:%ss% >> %logdir%\LOG%fn%.txt
echo --------------------------- >> %logdir%\LOG%fn%.txt
echo. >> %logdir%\LOG%fn%.txt

:: Loop through the data structure in the data dir to get the database names
for /d %%f in (*) do (

:: Create the backup sub-directory is it does not exist
if not exist %bkupdir%\%%f\ (
echo Making Directory %%f
echo Making Directory %%f >> %logdir%\LOG%fn%.txt
mkdir %bkupdir%\%%f
) else (
echo Directory %%f Exists
echo Directory %%f Exists >> %logdir%\LOG%fn%.txt
)

:: Run mysqldump on each database and compress the data by piping through gZip
echo Backing up database %%f%fn%.sql.gz
echo Backing up database %%f%fn%.sql.gz >> %logdir%\LOG%fn%.txt
%mysqldir%\bin\mysqldump --user=%dbuser% --password=%dbpass% --databases %%f --opt --quote-names --allow-keywords --complete-insert | %zip% > %bkupdir%\%%f\%%f%fn%.sql.gz
echo Done...
echo Done... >> %logdir%\LOG%fn%.txt
)

:: Go back and get the end time for the script
set endtime=1
goto :GETTIME

:END
:: Write to the log file
echo. >> %logdir%\LOG%fn%.txt
echo --------------------------- >> %logdir%\LOG%fn%.txt
echo MySQLDump Process Finished >> %logdir%\LOG%fn%.txt
echo End Time = %yy%-%mm%-%dd% %hh%:%ii%:%ss% >> %logdir%\LOG%fn%.txt
echo. >> %logdir%\LOG%fn%.txt

:: Return to the scripts dir
popd

:: Send the log file in an e-mail
c:\commail\commail -host=smtp.yourcompany.com -from="server " [email protected] -subject="MySQL Backup" -msg=%logdir%\LOG%fn%.txt

//--- End Batch File ---//

Posted by Philip Sbrogna on February 2 2006 4:05pm

[Delete] [Edit]

Here's a bash wrapper for mysqldump I cron'd to run at night. It's not the sexiest thing but it's reliable.

It creates a folder for each day, a folder for each db & single bzip2'd files for each table. There are provisions for exclusions. See below where it skips the entire tmp & test db's and in all db's, tables tbl_session & tbl_parameter. It also cleans up files older than 5 days (by that time they've gone to tape).

Be sure to update & . Ideally these would be in constants but I couldn't get the bash escaping to work.

# setup
suffix=`date +%Y%m%d`
dest=/mirror/mysqldumps
cmd='/usr/bin/mysqldump'

databases=(`echo 'show databases;' | mysql -u --password='' | grep -v ^Database$`)

for d in "${databases[@]}"; do
if [[ $d != 'tmp' && $d != 'test' ]]
then
echo "DATABASE ${d}"
s="use ${d}; show tables;"
tables=(`echo ${s} | mysql -u --password='' | grep -v '^Tables_in_'`)
for t in "${tables[@]}"; do
if [[ $t != 'tbl_parameter' && $t != 'tbl_session' ]]
then
echo " TABLE ${t}"
path="${dest}/${suffix}/${d}"
mkdir -p ${path}
${cmd} --user= --password='' --quick --add-drop-table --all ${d} ${t} | bzip2 -c > ${path}/${t}.sql.bz2
fi
done
fi
done

# delete old dumps (retain 5 days)
find ${dest} -mtime +5 -exec rm {} \;

Posted by Julien GARINO on March 19 2006 11:38pm

[Delete] [Edit]

You always wanted to BACKUP your most important database somewhere in your Linux system, as well as send the dump by email, so that you can recover the entire content if the system crashes.
You can use these 2 scripts.

First Step:
-Install the mutt client that will transfer emails on the command-line : "apt-get install mutt"
-Create the backup directory : "mkdir /home/backups"

Second Step:
- Copy these 2 scripts on your root directory or your user directory :

#!/bin/sh
# Script name : auto_mysql_dump.sh
# Backup the dbname database
dir=`date +%Y-%m-%d`
dbname=`mybase`
if [ -d /home/backups ]; then
mkdir /home/backups/$dir
mysqldump -B --user=user_of_my_base --password=pwd_of_my_base --host=host_of_my_base $dbname > /home/backups/$dir/$dbname.sql
fi
# End of script auto_mysql_dump.sh



#!/bin/sh
# Script Name : auto_mail_dump.sh
# Sends an email with the dump realized before
dir=`date +%Y-%m-%d`
dbname=`mybase`
mutt -s "Today backup" -a /home/backups/$dir/$dbname.sql [email protected] # End of script auto_mail_dump.sh

-Don't forget to change the access to make them executable:
"chmod 700 auto_mysql_dump.sh"
"chmod 700 auto_mail_dump.sh"

Third step:
-Edit the CronTab to schedule the execution of the two scripts.
"crontab -e" (you will use the vi editor)
We consider that the 2 scripts are in the /root directory
-I want the dump to be executed at 8.30 everyday
-I want the mail to be sent at 9.00 everyday
Thus I add these 2 rows after the existing lines :
Hit the "i" to insert new characters...

30 8 * * * /root/auto_mysql_dump.sh > /dev/null
00 9 * * * /root/auto_mail_dump.sh > /dev/null

Save the crontab by hitting : "Esc" + ":wq" (means Write and Quit)

What you should do now :
Once you've written the scripts, test-them !

Enjoy the automatic backup from now on :-)

Posted by [name withheld] on March 22 2006 12:00pm

[Delete] [Edit]

When you need to import the data from a mysqldump, instead of using "shell>mysql source dump.sql" is much better.

This way of importing the data avoids problems with language specific characters being turned into garble.

Posted by Mathieu van Loon on June 29 2006 7:02pm

[Delete] [Edit]

Here's a DOS script that will backup all your databases to a seperate file in a new folder, zip the folder, encrypt the zip and email the encrypted zip to one or many adresses. If the backup is larger than a specified limit only the logfile is emailed. The unencrypted zipfile is left on your local machine.

The script is also available at http://www.jijenik.com/projects/mysqlbackup/

Many thanks to Wade Hedgren whose script formed the basis for this version.


//--- Begin Batch File ---//
::
:: Creates a backup of all databases in MySQL.
:: Zip, encrypts and emails the backup file.
::
:: Each database is saved to a seperate file in a new folder.
:: The folder is zipped and then deleted.
:: the zipped backup is encrypted and then emailed, unless the file exceeds the maximum filesize
:: In all cases the logfile is emailed.
:: The encrypted backup is deleted, leaving the unencrypted zipfile on your local machine.
::
:: Version 1.1
::
:: Changes in version 1.1 (released June 29th, 2006)
:: - backups are now sent to the address specified by the mailto variable
::
:: The initial version 1.0 was released on May 27th, 2006
::
::
:: This version of the script was written by Mathieu van Loon ([email protected])
:: It is based heavily on the script by Wade Hedgren (see comments at http://dev.mysql.com/doc/refman/5.0/en/mysqldump.html)
::
:: This script requires several freeware libraries:
:: - zipgenius (a compression tool), www.zipgenius.it
:: - blat (an emailer tool), www.blat.net
:: - doff (extracts datetime, ignores regional formatting), www.jfitz.com/dos/index.html
::
:: Some areas where this script could be improved:
:: - include error trapping and handling
:: - make steps such as encryption and email optional
:: - allow the user to specify a single database on the command line
::
@echo off

::
:: Configuration options
::

:: The threshold for emailing the backup file. If the backup is larger
:: it will not be emailed (the logfile is always sent).
set maxmailsize=10000000

:: The passphrase used to encrypt the zipfile. Longer is more secure.
set passphrase=secret

:: Name of the database user
set dbuser=root

:: Password for the database user
set dbpass=password

:: Recipients of database backup, comma seperated, enclosed in quotes
set mailto="[email protected],[email protected]"

:: From address for email
set mailfrom="MySQL Backup Service "

:: Email server
set mailsmtp=localhost

:: Email subject
set mailsubject="MySQL Backup"

:: directory where logfiles are stored
set logdir=C:\DatabaseBackups\logs

:: directory where backup files are stored
set bkupdir=C:\DatabaseBackups

:: Install folder of MySQL
set mysqldir=C:\Program Files (x86)\MySQL\MySQL Server 4.1

:: Data directory of MySQL (only used to enumerate databases, we use mysqldump for backup)
set datadir=C:\Program Files (x86)\MySQL\MySQL Server 4.1\data

:: Path of zipgenius compression tool
set zip=C:\Program Files (x86)\ZipGenius 6\zg.exe

:: Path of blat mail tool
set mail=C:\DatabaseBackups\Backupscript\libraries\Blat250\full\blat.exe

:: Path of doff date tool (specify only the folder not the exe)
set doff=C:\DatabaseBackups\Backupscript\libraries\doff10

::
::
:: NO NEED TO CHANGE ANYTHING BELOW
::
::

:: get the date and then parse it into variables
pushd %doff%
for /f %%i in ('doff.exe yyyymmdd_hhmiss') do set fn=%%i
for /f %%i in ('doff.exe dd-mm-yyyy hh:mi:ss') do set nicedate=%%i
popd

set logfile="%logdir%\%fn%_Backuplog.txt"

:: Switch to the data directory to enumerate the folders
pushd "%datadir%"

:: Write to the log file
echo Beginning MySQLDump Process > %logfile%
echo Start Time = %nicedate% >> %logfile%
echo --------------------------- >> %logfile%
echo. >> %logfile%


:: Create the backup folder
if not exist "%bkupdir%\%fn%\" (
echo Making Directory %fn%
echo Making Directory %fn% >> %logfile%

mkdir "%bkupdir%\%fn%"
)

:: Loop through the data structure in the data dir to get the database names
for /d %%f in (*) do (

:: Run mysqldump on each database and compress the data by piping through gZip
echo Backing up database %fn%_%%f.sql
echo Backing up database %fn%_%%f.sql >> %logfile%
"%mysqldir%\bin\mysqldump" --user=%dbuser% --password=%dbpass% --databases %%f --opt --quote-names --allow-keywords --complete-insert > "%bkupdir%\%fn%\%fn%_%%f.sql"
echo Done... >> %logfile%
)

:: return from data dir
popd

pushd %bkupdir%

echo Zipping databases
echo Zipping databases >> %logfile%
REM C9 : maximum compression
REM AM : Delete source files
REM F1 : Store relative path
REM R1 : include subfolders
REM K0 : Do not display progress

"%zip%" -add "%fn%_MySQLBackup.zip" C9 AM F1 R1 K0 +"%bkupdir%\%fn%"

echo Crypting zipfile
echo Crypting zipfile >> %logfile%

REM C : Create non-executable zip
REM S : Do not delete after x tries
REM 3 : Use AES encryption
"%zip%" -encrypt "%fn%_MySQLBackup.zip" C S 3 "%passphrase%" %mailfrom%

echo Deleting directory %fn%
echo Deleting directory %fn% >> %logfile%

rmdir /s /q "%bkupdir%\%fn%"

:: Go back and get the end time for the script
set endtime=1

:: return from backup dir
popd


:: update the nicedate for the log
pushd %doff%
for /f %%i in ('doff.exe dd-mm-yyyy hh:mi:ss') do set nicedate=%%i
popd


:: Write to the log file
echo. >> %logfile%
echo --------------------------- >> %logfile%
echo MySQLDump Process Finished >> %logfile%
echo End Time = %nicedate% >> %logfile%
echo. >> %logfile%


:: Send the log file in an e-mail, include the backup file if it is not too large
:: We use the CALL Trick to enable determination of the filesize (type CALL /? at prompt for info)
:: note that you _must_ specify the full filename as the argument

pushd %bkupdir%
Call :MAILFILE "%bkupdir%\%fn%_MySQLBackup.czip"
echo Backup completed
goto :EOF

:MAILFILE

if /i %~z1 LSS %maxmailsize% (
echo Emailing backup file
"%mail%" %logfile% -q -attach %1 -serverSMTP %mailsmtp% -f %mailfrom% -to %mailto% -subject %mailsubject%
) ELSE (
echo Size of backup file %~z1 B exceeds configured email size %maxmailsize% B.
echo Emailing logfile only
echo Size of backup file %~z1 B exceeds configured email size %maxmailsize% B. only emailing logfile. >> %logfile%

"%mail%" %logfile% -q -serverSMTP %mailsmtp% -f %mailfrom% -to %mailto% -subject %mailsubject%
)

echo Deleting encrypted backup file
del %1

popd
//--- End Batch File ---//

Posted by Don Gilman on July 25 2006 11:11pm

[Delete] [Edit]

RE: Mathieu van Loon

Excellent, I had this installed and configured in about 10 minutes. I do have one minor fix however.

You aren't getting the time portion of the DOFF command captured into your variable. It appears that the output formatting string MUST NOT CONTAIN ANY BLANKS so I changed mine to:

for /f %%i in ('doff.exe dd-mm-yyyy_at_hh:mi:ss') do set nicedate=%%i

This is terrific, wish I found it 10 hrs ago (darn mySQL Administrator Backup - such a waste!!!
***
Now the problem is that my backups won't restore.... I am backing up multiple instances of MediaWiki, Mantis, and Joomla. I'm playing around with the
--max_allowed_packet= nnn and that should fix it based on manual backups working. Now is that nnn bytes or an abbreviation? Hmmm.

Posted by Enrico Modanese on July 13 2006 1:05pm

[Delete] [Edit]

I often get errors [MySQL 4.* and 5.*] on reloading a dump of databases having big blobs. I found the solution disabling the --extended-insert (that comes inside the multiple option --opt, enabled by default) with --skip-extended-insert. I think this way is safer, but it is also more more slow.

Posted by Sjaak Lauwers on August 9 2006 6:27pm

[Delete] [Edit]

RE: Mathieu van Loon

Excellent, I had this installed and configured in about 10 minutes.

But how to execute the script automatically in windows XP everyday on the sime time without the user having to start the bat file.

Posted by Gregert Johnson on August 22 2006 3:51pm

[Delete] [Edit]

Changing the default behavior of a utility like mysqldump on a version upgrade is a terrible idea. No matter how reasonable such a change may seem to be, there is always the possibility of unforeseen consequences. Here is an example:

We have been using mysqldump to copy table structures from one server to another, in a process that initializes a replication relationship. The input of the copy is to be the slave of the configuration, the output the eventual master. Data collection programs eventually write to the master (which is kept very small), and replication then updates the far larger slave.

Upgrading to version 4.1 allows us to use the black hole engine for the master tables; consequently, when the master tables are created from those on the slave, their engine types are changed to "blackhole". This is done in a script that pipes the output of mysqldump running on one server (S) through a filter that changes the engine type to blackhole, and then to the other mysql server (M).

If through an error this initialization process were to be run on a system where replication was already in place, the "CREATE TABLE … ENGINE=BLACKHOLE" statements executed on M could be replicated back to S. The SQL generated by the 4.0 version of mysqldump (default behavior) contains only CREATE TABLE statements; if these statements were executed on the slave they would fail with errors, and no harm would be done. With the 4.1 version, however, the CREATE TABLE statements are prefaced with DROP TABLE statements – the result would be to destroy the existing tables on S.

It is of course our responsibility to thoroughly check the behavior of our software after a database upgrade, and we have taken steps to avoid this tragedy (using the --skip-opt option in mysqldump, taking pains to disable replication, etc.). But for MySQL developers to create additional pitfalls for us to fall into by changing default behavior is – allow me to use a pompous word here – outrageous!

Posted by [name withheld] on September 5 2006 8:59am

[Delete] [Edit]

To backup certain tables in a database, you have to set the -B operator (for the proper database) AND use the --tables operator to list the tables you wish to backup.
Example:

mysqldump --user=.. --password=.. -B --tables

Posted by Roddi Walker on October 8 2006 1:41am

[Delete] [Edit]

Here's a python script that does rolling WinRAR'd backups on Windows. It should be trivial to change to Linux, or another compression program.
Please note:
1) this was a quick hack, so please test thoroughly before using in production. Still, I hope it will be a useful basis for your own script.
2) the --single-transaction switch is used as I am backing up InnoDB tables.
3) mysqldump is run with the root user. It would be A Good Thing to make this more secure - eg. create a backup user with read-only permissions to the tables.
4) is the tab character. Indentation is significant in Python.

import glob
import os
import time

# configuration
baseBackupFileName = "backupName"
maxBackups = 3
mySqlDumpCommand = "d:\\programs\\mysql\\bin\\mysqldump --user=root --password=rootpass --single-transaction DBName Table1Name Table2Name Table3Name"
winRarPath = "\"c:\\Program Files\\WinRAR\\WinRAR.exe\"" # path is quoted as it contains spaces

print "--- START ---"

# create new backup
newBackupFileName = baseBackupFileName + time.strftime("_%Y%m%d_%H%M%S", time.localtime())
os.system(mySqlDumpCommand+" > "+newBackupFileName+".sql")

# compress new backup
os.system(winRarPath+" a "+newBackupFileName+" "+newBackupFileName+".sql")
os.remove(newBackupFileName+".sql")
print "Created new backup \""+newBackupFileName+".rar\""

# delete old backups
oldBackupFileNames = glob.glob(baseBackupFileName+"_*_*.rar")
oldBackupFileNames.sort()
if len(oldBackupFileNames) > maxBackups:
for fileName in oldBackupFileNames[0:len(oldBackupFileNames)-maxBackups]:
os.remove(fileName)
print "Deleted old backup \""+fileName+"\""

print "--- END ---"

Posted by jon doe on October 27 2006 5:50am

[Delete] [Edit]

The example I was taught goes simply like this:

mysql>mysqldump -u root -p DATABASENAME > DATABASENAME.sql

If you wanted to test it, you could drop the database:

mysql>DROP DATABASE DATABASENAME;
(DATABASE referring to DATABASENAME, the one you just backed up)

The quit mysql:

mysql>q

Log back in:

]$ mysql -u root -p
mysql>CREATE DATABASE PREVIOUS_DATABASENAME;
mysql> \q
Bye
]$ mysql -u root -p PREVIOUS_DATABASENAME Enter password:


And it will be restored!

Posted by kenji h on November 6 2006 6:20am

[Delete] [Edit]

--master-data
"default value" seems to be "1" under my environment, MySQL 5.0.24 on Linux 2.6 kernel.

Thanks,
Kenji

Posted by Mario Moore on March 5 2007 5:00am

[Delete] [Edit]

Corey and Lon,

The scripts were very helpful!

Thank you.

Posted by Kenny Gryp on March 20 2007 12:47pm

[Delete] [Edit]

the --master-data option also requires the SUPER or REPLICATION CLIENT privilege.

Add your own comment.

Top / Previous / Next / Up / Table of Contents