On Sunday we had a an update to a MySQL server that broke the connection to the database. After working from 6:30 p.m. until 3:00 a.m. the error was still happening and the restoration was not in sight. Something as simple as a my.ini weighing in at 9k had broke the database connection. This file sets the parameters for mysql and can be manually edited or recreated with a wizard under the bin files in MySQL server. Neither one of these solutions was working. Errors began to crop up with the INNODB settings during its connection with the mysql database and the frm files.
Knowing we had a back up of the data, the frm files (sql), the .sql backup script, the php files and its .ini file along with the web pages and php files for the web server, we began installing and configuring each of the above. Every answer yielded different problems. Ultimately we had to try dozens of things that are not in manuals or in forums.
The fix? Restoring the database to a different folder other than the original backed up folder. This in turn caused the server to restore to the original folder and ignore the folder we created. – Very unconventional and a ton of trying anything while making sure the original data remained protected. Trying anything logical and correcting each other during a long restoration process is the key to your DRP.
The database and the SQL Connector, PHP, IIS, SQL configuration, SQL database, the data files and the SQL Workbench once again living in harmony.
Each solution has to be analyzed and thought out when working with any type of production server. There is no magic button and there isn’t a time when it will be fixed. What’s taking so long? Thinking…lots of thinking and sleep deprivation.