View Source

{page-title}{excerpt}Why mysqlhotcopy Is Not So Hot{excerpt}
\\

[mysqlhotcopy|http://www.google.com/url?sa=U&start=1&q=http://dev.mysql.com/doc/en/mysqlhotcopy.html&ei=hfUqSZ3-BYTeM7-fkYAC&usg=AFQjCNFzJftULVYIUPBm1WeEMat9C6qqrQ] is a command line utility provided with MySQL that automates the process of taking of doing a [lock and copy|TP:Lock and Copy] on MyISAM tables.  Read more about the [lock and copy MySQL backup method|TP:Lock and Copy].  

h3. How Does mysqlhotcopy Work?

mysqlhotcopy sounds as if it should be an online or "Hot" backup method.  It is not.  The challenge with mysqlhotcopy is that it must hold table locks for the duration of the entire MyISAM backup.  This means the database is unavailable while tables are being copies.  For most production environments this rnders mysqlhotcopy usless unless it is used during maintenance periods where down time is acceptable.  mysqlhotcopy is some times used with great success to take a backup copy of a MySQL Slave replica in larger production environments.
\\
\\
| {color:#cc0000}Category{color}\\ | [Legacy|TP:Categories of MySQL Backup Software]\\ |
| Archive Type | Disk \\ |
| {color:#cc0000}MySQL Storage Engines Supported{color} | {color:#cc3300}MyISAM Only{color}\\ |
| Supported O/S | All \\ |
| Binlog Backup & Restore | {color:#cc0000}No{color} |
| {color:#cc0000}Zero Business Interruption (Online Backups){color} | {color:#cc0000}No{color}\\ |
| {color:#00cc00}Granular (Table Level) Restore{color} \\ | {color:#00cc00}Yes{color} \\ |
| Easy to Use Graphical User Interface \\ | {color:#cc0000}No{color} |
| Complete Server Protection (Backup All Data or just MySQL?) \\ | {color:#cc0000}No{color} |
| Backup Type \\ | [Full|TP:Backup Method - Full Backup]\\ |
| {color:#cc3300}Backup Window Length{color} \\ | {color:#cc3300}Long{color} \\ |
| {color:#cc3300}Server Disk I/O and Load Impact{color} \\ | {color:#cc3300}Heavy{color} \\ |
\\