Diamond Notes

Dr. Bell summarized new features found in the implementation of backup and restore in version 6.0.

SQL Driven — run from the command line

Database level backup

• tables
• views
• stored procedures
• stored functions
• triggers
• events

Enterprise level consistitency — from point in time

non-blocking DML operations on Innodb and Falcon

streaming backup data (only to local server file now..should extend to tape or other servers)

tablespace support for falcon

no data engine backup eg: blackhole, merge (didn’t quite understand why this is useful but he gave some reasons)

synchronization with binary log for point-in-time recovery

defaults to mysql datadir although you can specify a directory in the backup filename

example:

BACKUP DATABASE database_name TO ‘database.bak’;

RESTORE command is destructive

backup log information looks useful but Dr. Bell indicates it will be changing probably.

Future plans:

• coverage for all MySQL storage engines
• use plug-in architecture
• backup to other media/servers
• standalone mysqlbackuptool
• full server, database and enhanced point-in-time recovery

Still a work in progress but looks very promising!! Honestly, the backup parts of 6.0 might be the most important features of the upcoming 6.0 servers. Falcon looks nice and sounds nice, but backups rule the day when the $%#@ hits the fan. I personally am excited to finally see development on this front.

Resources:

http://forge.mysql.com/wiki/OnlineBackup