MySQL Database Unfairly Shutdown by Dreamhost Automatically. WTF Dreamhost?

I’m on the MySQL VPS plan as we use it to store data for our business and need it to be up and running all the time.

Overnight, our databases were archived by the admins because our database was over 3GB. It’s been over 3GB for a long time (around 30GB last time I checked). As I understand it, the storage should be “unlimited” as per Dreamhost’s page (

It’s now been 12 hours and we’ve had to apologise to everyone and shut down for the day, losing a days work and business because we relied heavily on that database to do our work.

I’m not in the US so I can’t get a callback, there’s no number to call for issues like this. The chat with an agent isn’t working on Zopim. So I’m left with nothing but to rant here.

After much swearing and angry air punching, I get that my issue isn’t going to be resolved anytime soon, thanks for the loss of money and work. But I do want to achieve at least 2 things with this post -

  1. This is not the first time this has happened to me, when it happened the first time, I was not aware there were storage limitations, hence we upgraded to MySQL VPS under the promise that storage was unlimited. If it is not unlimited, please stop advertising it as unlimited.

  2. If you, Dreamhost admins are going to archive a large database, please please please for the love of god, give me some notice, not an email at 2am in the morning (my time) telling me that the archive is in progress. I’m sure I’m not the only one in the world whose livelihoods depend on Dreamhost keeping up their side of the deal. Like I said, we were at 30GB last time I checked, so we were over this 3GB threshold a long time ago. A warning, an email 72 hours out, anything would be great so I know I need to either delete or archive some tables myself. Now I just have some 6GB gzip file that I have no idea what to do with. I can’t unzip a 30GB+ file and upload it in phpMyAdmin.


1 Like

Sorry to read about this issue, I’d be very annoyed too. I checked with my colleagues at Support and they confirmed they addressed your concerns in your private ticket. I’ll join my colleague in asking the database admins to make sure issues like this won’t happen again.