mysql abandoned, need to figure it out in a hurry

anon091 · 04-25-2014, 11:11 AM

That's a good idea, maybe i'll load up a CentOS vm and install MySQL. That way I can't blow up my machine haha.

szboardstretcher · 04-25-2014, 11:13 AM

I work with Mysql and our DB's a lot. So I actually have my VM's mysql set up as a read slave that is constantly updated with replication. If I want to test something I break replication and check it out. When I am finished I run my re-replication script.

It's a good way to always have good data to work with, while not having to wait for dumps/imports.

jpollard · 04-27-2014, 07:53 AM

One final suggestion: Keep detailed notes... This can save you future pain.

And roughly once/twice a week review the notes - transcribe it into a "recovery" document as a prototype for the next guy that has to deal with things.

anon091 · 04-28-2014, 01:38 PM

Good tip. I'm not sure why that wasn't already done by the prior guy.

I'm going to try to do a backup of the database in the morning. I'm loading a CentOS virtual machine now, that with any luck, I'll be able to restore the backup into, then I can try those truncate commands.

Thanks again everyone. I'll update this post, hopefully with some good news, as soon as I can.

anon091 · 04-28-2014, 02:20 PM

One thing I forgot, is webmin is running on this server, and it has a MySQL part that I never really noticed before. Looking there, it does look like those three things I found after "truncate" in the notes I dug through are table names (show as green folders in webmin when I click on the database).