MySQL Bugs: #25942: Database backup is not complete

Bug #25942	Database backup is not complete
Submitted:	30 Jan 2007 12:29	Modified:	19 Feb 2007 13:45
Reporter:	Mikko metsola	Email Updates:
Status:	Unsupported	Impact on me:	None
Category:	MySQL Server: Falcon storage engine	Severity:	S3 (Non-critical)
Version:	mysql-5.2.0-falcon-alpha-win32	OS:
Assigned to:		CPU Architecture:	Any

Description:
It looks like I cannot copy & paste Falcon files <database>.fl<n> without killing the server that uses those files. I guess those are the serial log files.

I execute my backup currently like:

1. flush tables with read lock
2. copy all files to new directory
3. unlock tables

That procedure is inherited from my work with 5.1 MyISAM engine.

The database file itself, <database>.fts file was copied succesfully.

I restored the backup successfully without .fl* files, but I'm not really convinced of the db being in fully synchronized state.

How to repeat:
Make a backup according to instructions listed above.

You cannot back up a Falcon Database this way.  A read lock does not cause a Falcon table (or the database it resides in) to be flushed to disk.  Since the files on disk are still in an active condition during the time frame of the copy of all three files containing the datase and the two serial log files, the resultant cpoied database is very inconsistent.  Falcon does not work like MyISAM.

Online Backup is a feature which is planned for Beta, but not currently supported.

According Kevin's last comment it isn't supported.