MySQL Bugs: #59956: Data from memory engine is lost after copy-back operation of mysqlbackup

Bug #59956	Data from memory engine is lost after copy-back operation of mysqlbackup
Submitted:	4 Feb 2011 20:17	Modified:	28 Feb 2013 16:08
Reporter:	Hema Sridharan	Email Updates:
Status:	Not a Bug	Impact on me:	None
Category:	MySQL Enterprise Backup	Severity:	S3 (Non-critical)
Version:	MEB 3.6	OS:	Any
Assigned to:		CPU Architecture:	Any

Description:
Create database and tables
Create table with Memory storage engine also.
Execute MEB .
Stop the server, apply-logs and copy-back.
Restart the server
Check for the data. No data will be present for Memory table.

How to repeat:
Please find the attached test case to reproduce the issue.

Test to reproduce the issue

Attachment: mbkp_memory.test (application/octet-stream, text), 2.13 KiB.

Thank you for the report.

> Execute MEB .
> Stop the server, apply-logs and copy-back.
> Restart the server
> Check for the data. No data will be present for Memory table.

According to http://dev.mysql.com/doc/refman/5.1/en/memory-storage-engine.html: "However, when the server shuts down, all rows stored in MEMORY tables are lost. The tables themselves continue to exist because their definitions are stored in .frm files on disk, but they are empty when the server restarts. "

Why do you expect is should contain data in your scenario?

Hi Sveta,

You are right. We discussed the same thing in QA meeting and thought that it will be good to somehow recover the data of memory engine also. the previous backup solution used to store the data of memory storage engine also. Although this is not a high prio bug but can be made as feature request.

Thank you for taking the time to write to us, but this is not a bug. Please double-check the documentation available at http://dev.mysql.com/doc/ and the instructions on
how to report a bug at http://bugs.mysql.com/how-to-report.php