Setting up a MySQL fail over Master-Master replication system is something one can find many guides for.
However, monitoring and recovering from a failure of the system is not as well documented, according to a quick Google search.
The top items from that search were:

Something called: MYSQL master-master replication monitor shell script that mainly included the following [...]

 ::  (Read the rest of this)

When managing a large number of servers, it is most likely that you will come across a server that makes use of a RAID controller, and as such you will need to know the status of the disks and the disk array.
As these are usually proprietary controllers, normal tools like ipmiutil, lshw, lspci, etc. aren’t [...]

1 comment  ::  (Read the rest of this)

Not getting into the whole which engine is the best debacle, since obviously, like most important questions in life the answer is: “It depends.”

In addition, most of what is written here can be used to convert from any engine to any engine, and thus answering any specific needs your might have.
I needed to convert MyISAM to InnoDB so here it is.

Without further ado…

As far as I know, there are two basic ways to accomplish this:

1.  ALTER TABLE 'tablename' ENGINE = InnoDB

   For each table in the database.

2. Dump the table, edit the dump file where it says “CREATE TABLE” and fix to the preferred engine, and then reload the data back into the DB

Obviously, these methods are ok when you are dealing with a few tables, however a while ago we had a client with a huge database with over 50 tables, so of course, a script was in place.

2 comments  ::  (Read the rest of this)

The point of this blog is to share all kinds of scripts and little programs I wrote on various occasions, to solve all kinds of issues.
Hopefully they will be of use to others, as I know many a time I wished for a simple something to Google->Copy->Paste and get on with my life.

 ::  (Read the rest of this)