Another Linux lie: we have a DB server

Truth is: you don't.

Imagine that you run MySQL on a device that does not have luxury of hypervisors or VM snapshots, such as Raspberry PI or a smart TV or whatnot, anything that is not as bloated as a Windows/Linux server. Everything is fine until your device decides to crash.

No problem, says you and whip out the DB recovery page from Oracle. It tells you to restore DB from backup, as the most straightforward recovery path, something along the lines of mysql -u user -p password dbname < backup.sql. Not so fast!

Your server crashed, damaged the DB, and now it does not start, so nothing is listening on port 3306, and the above command does not work. Should it have occurred to the genius FOSS developers of MySQL that this situation is possible? You would have thunk it should but it has not.

The only way to restore BAU for a crashed MySQL instance that FUBARed its DB is to uninstall, blow away the data folder, and reinstall. Genius is as genius does: usually as a degenerate. I pity any organization that runs on MySQL and will NEVER take a job for one of them.

Now, let us think about this situation from an ordinary, reasonable person's POV: should the server refuse to come up because it's DB is damaged? Fuck, no! The server should come up regardless, to allow the recovery commands to be run. But this simple thought does not occur to geniuses, sadly.

Posted by: LinuxLies at 07:52 AM | No Comments | Add Comment
Post contains 264 words, total size 1 kb.