I'm hoping this will be a simple answer for one of you.
We've got PHP/MySQL running on a single board computer for a product that will be a web-based admin tool. This product will be a 'set it and forget it' application.
One of our concerns (whether or not it's valid) is MySQL table/dbase corruption.
We have processes running continually on this little box that can diagnose the corruption, or catch dbase errors and act accordingly.
We are creating backups regularly via these same processes. Our thought is that if we sense corruption or catch a dbase error, that we'll briefly pause our processes and do a restore of the table from the most recent backup. Our hope is that this will fix the corruption.
The question is: If a MySQL table is corrupted, can we perform a backup restore?
I suppose a follow-up question would be if our logic above is correct. Will a backup restore correct a table corruption issue?
I know this sounds silly, but we're not that familiar with the MySQL backend. Our fear is that if the dbase (or a table) is somehow corrupted, that this will also impede a backup restore.
Can some of you weigh in on this?
Thanks so much.