MySQL Bugs: #12182: Empty Backups when Complete Backup checked

Bug #12182	Empty Backups when Complete Backup checked
Submitted:	26 Jul 2005 16:21	Modified:	18 Aug 2005 15:10
Reporter:	Christopher Gonzalez	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Administrator	Severity:	S3 (Non-critical)
Version:	1.1.0 rc	OS:	Windows (Windows Server 2003)
Assigned to:	Vladimir Kolesnikov	CPU Architecture:	Any

Description:
I recently upgraded to the 1.1.0 rc version of Admin, but noticed my scheduled backups all had sizes of 0 KB.  I tried running a few manual backups, but to no avail.  After playing with it for a while, I unchecked the 'complete backup' option and it worked perfectly.

How to repeat:
Create a backup project, with the option 'complete backup' checked.  Execute it, and check whether data was actually captured.

Suggested fix:
Not sure, maybe disable the option?

Hello,

Thank you for the report, but I wasn't able reproduce this behavior.
Please, describe us more detailed what exactly you did, what options were checked etc.

I am having the exact same problem with win 2003 server with sp1, same version.

I had some backup projects set up since 1.0.20, I believe...  Well, they were set up some time ago.  Anyways, they've been working up until I upgraded Admin.  I also checked my backup files to see whether they worked, and after unchecking the 'complete' option, only 5 of 18 actually ended up saving data.  

I'm thinking I'll just scrap those projects and recreate them...

Hi!

I just installed an older version of MA, upgarded it to the most recent one, and I was unable to reproduce the bug that you encountered.

Is there anything else you can tell us, that will help us reproduce this bug ?

Thanks!

I just looked at the server logs and came across this entry:

(several instances of this first line, with different threads)

050728 12:33:29 [ERROR] C:\Program Files\MySQL\MySQL Server 4.1\bin\mysqld-nt: Forcing close of thread 5  user: 'root'

050728 12:34:27  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
050728 12:34:28  InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 4443619.
InnoDB: Doing recovery: scanned up to log sequence number 0 4443619
050728 12:34:28  InnoDB: Flushing modified pages from the buffer pool...
050728 12:34:28  InnoDB: Started; log sequence number 0 4443619
C:\Program Files\MySQL\MySQL Server 4.1\bin\mysqld-nt: ready for connections.
Version: '4.1.13-nt'  socket: ''  port: 3306  Official MySQL binary

Not sure if this will help...

Also, I noticed that if I give each project a manual entry now, they will work fine.  I had to do this as last night's backup did not succeed.  This is after unchecking 'complete'.

I can verify this same behavior, running v 1.1.0 rc on WinXP.  Our MySQL server is 4.1.12a, and is a Win2K Server.  I came to this site to also report the same bug.  I didn't realize that unchecking "Complete Backup" would allow the backup to be created, but I tested this "solution" and it indeed at least allows the backup to proceed.  Otherwise, with the "Complete Backup" checked, the backup will complete instantaneously and will be 0kb in size.

I don't know if this helps at all, but when you do a successful backup, like when you UNCHECK "Complete Backup", then you can immediately browse to that file, like with Windows Explorer and rename/move/delete it, like you would expect to be able to.  When the backup fails, like when you CHECK "Complete Backup", the 0kb file is reported as "in use" by Windows when you try to rename/move/delete it.  It's like it is locked or still trying to be accessed my MySQL Administrator.  Not until you close MySQL Administrator are you actually able to get rid of this file or really do anything with it.  Hope this is useful information somehow to you developer types!

Hi!

Thanks for your bug report.  I was able to reproduce this bug by having the "Complete Backup" option checked.

Thanks!

Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at
    http://www.mysql.com/doc/en/Installing_source_tree.html