Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am using Mediatemple's Grid Hosting (GS) platform to host a wordpress site. The DB tables are using the MyISAM engine.

I had noticed that a previous article had disappeared from the site. At first I thought it was a user mistake so I took a look at the DB backup that I had made soon after the article was posted and I noticed that the article had an ID of 11300 (auto_increment) and there were autosaves that had an ID all the way to 11307. When I checked the database, the ID of 11300 was occupied by a newer post which means that the value got re-set.

I did a diff of the database dump between the one taken just before the article disappeared and today. There was no content change other than the standard for some new posts and comments being added.

Mediatemple says it is a security vulnerability and that there is nothing wrong on their end. They suggested that I imported data (which I definitely didn't do) or a 3rd party doing it without my knowledge. But why would anyone go through the trouble of re-importing the database without adding any exploits or backdoors?

So my question is, is there any other possible explanation for this? Botched replication or some other oddity? I am not so much concerned about getting my data back but very concerned about future losses.

share|improve this question
By any chance, are you using HyperDB Plugin ??? – RolandoMySQLDBA Mar 6 '12 at 3:41
I'm not sure, can I find out using PhpMyadmin? – Mishari Mar 6 '12 at 10:42
up vote 0 down vote accepted

If you are using external DB Hosting, you should expect some intermittency due to the hosting. There are no native MySQL mechanisms in play. I have seen happen while evaluating XEROUND.

When I signed up for the 30-day trial, I was given two public IPs to access the MySQL Database. I loaded a lot of data on it. I was able to access it from one East-coast based public IP and the data was not immediately manifested from the West-coast based public IP till minutes later.

You have find out from Mediatemple if you can look into using their Reboot and Repair Utilities. You may also need to make sure data is being coalesced fast enough for snapsots to be reasonably replicated.

There is one major concern. Under the FAQ section I just saw something very, very disturbing for Mediatemple's Grid Hosting:

Which versions of LAMP software comes with my (gs)? The (gs) Grid-Service currently features the following versions of software:

PHP 5 (click for specific version)

Perl v5.8.4

Python v2.4.4

Apache 2.0.54

MySQL 5.1.26

I really hope that is a misprint. Why?

The first GA release of MySQL 5.1 is 5.1.30. Mediatemple is offering MySQL 5.1.26.

Why on God's green earth would someone offer a Pre-GA version of MySQL 5.1?

Please, make sure you are using MySQL 5.5.21 (or 5.1.61 if you have to have MySQL 5.1)

UPDATE 2012-03-05 22:51 EST

You should setup MySQL Replication is addition as a secondary form of redundancy to an outside hosting service (such as Amazon EC2) for a while. That way, any missing rows should at the very least show up in the binary logs on the Master and the relay logs on the Slave.

If your data is missing in MediaTemplate but is present and accounted for on the Slave, I would consider switching out of MediaTemplate Grid Services. If it happens more than once, switch out immediately.

If the data on the Slave is exactly the same, you can rule out Database Replication at all levels. From here it is time for a deep dive into WordPress configuration. You can also look through the binary logs to see the data you had was once there at one point disappears at another point.

share|improve this answer
The problem doesn't seem to indicate lag but somehow the disappearance of several rows of inserted data including auto_increments. I'm not so much concerned about getting the data back but more about preventing future losses. The MySQL version in use at Mediatemple is 5.1.55-rel12.6 – Mishari Mar 6 '12 at 2:46

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.