Bug #66769 Config Wizards places InnoDB Tx log files and data files in different places
Submitted: 11 Sep 2012 15:20 Modified: 31 Mar 2014 8:39
Reporter: Anders Karlsson Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Config Wizard Severity:S3 (Non-critical)
Version:5.5.27 OS:Microsoft Windows (Windows 7)
Assigned to: CPU Architecture:Any
Triage: Needs Triage: D3 (Medium)

[11 Sep 2012 15:20] Anders Karlsson
Description:
When running the MySQL Configuration Wizard, and you choose a different directory for the InnoDB data files than the default, then only the datafiles are placed in this directory, not the transaction log files. If you then upgrade, then you may choose a different data directory for the data files, but the other files that make up the database, including the InnoDB logfiles, remains where they were. When you upgrade or reinstall MySQL, you get the option to move the InnoDB data files whereever you want, but as the logfiles remains where they were, you can end up with the old logfiles and a new datafiles, which seems like a dangerous situation.

Also, if you don't really look at the results and trust the installer, and install the InnoDB datafiles on, say, a SAN disk or some trusted RAID device, and trust that the transaction logfiles are also there, you are in for a surprise when the InnoDB logfiles are in the C:\ProgramData folder.

How to repeat:
Run the MySQL configuration Wizard, change the location of the InnoDB data files, and note that the InnoDB logfiles are still in the ProgramData folder.
[11 Sep 2012 16:55] Miguel Solorzano
Thank you for the bug report.
[31 Mar 2014 8:38] Yngve Svendsen
Posted by developer:
 
Thank you for the bug report. We are closing this report now since the original config wizard is no longer the focus of Windows deployment efforts. For recent MySQL Server versions, the config wizard is also no longer available, and the MySQL Installer for Windows is the recommended way to install MySQL Server on Windows.