After a server issue, my client has restored the MySQL files before their issue, but MySQL is having problems bringing their database back up. (i'm waiting for more information as the exact nature of the issue)
I have the ibdata1 ib_logfile0, and ib_logfile1files, and all the .frm and .ibd files for all the tables. I can open the database using Navicat, but when trying to open individual tables the first attempt shuts down the MySQL service and after restarting it, table access attempts returns a message that the table doesn't exist.
I've uploaded the section of the error log from my last attempt to access the database.
I've contacted percona and am aware of their tools, and services, but was hoping someone could give me a little more insight to my issue, and if there is a way to restore this database that isn't a major time consuming pain in the b**t. )
Thanks,
Server issue specifics
The server crash was the result of a power surge, which took out the SATA and RAID controllers. It also completely damaged one drive (there were 2 drives mirrored in RAID1 as dynamic disks). The other drive was only partially damaged, and it is from this drive that we extracted the files that we have from the mysql data directory (that is the "afriplexqms" directory you're seeing).
However, we also have a manual backup set, which is in the root of the D\IRENE\TLM folder (in the form of 342 .sql files).
When the DB was "restored," Did the user restore from the filesystem backups?
If you have the SQL files dumps, you should try restoring that data on a separate system where you can install MYSQL if not installed and restore them from the sql dumps,
Hopefully, you have the DB/table create as part of the SQLs and the sql backups are recent enough.
The only time a filesystem mysql backup will be valid is when mysql is not running when the backup is taken/made/created. If you have no opportunity to do recovering files that way, then I can advise to try to take MySql Recovery Toolbox and restore file using this tool and think you will be able to save your base. http//
You can still read this resource for more information on your issue.
https://
If you suspect any corruption to the backups then I would sugest that the .sql files are you best course of action.
Use those to recreate any tables populate them and then recreate any idexes (it should all be automatic). You should be able to do this on a new installation of MySQL (on a new test server) so have nothing to lose.
Thank you guys for your feedback and help. Sorry, that long time did not respond. This is because the issue was solved and I forgot to tell.) Thank you!
