Jump to content


Johnny Innodb

  • This topic is locked This topic is locked
No replies to this topic

#1 HelioHost



  • Moderators
  • 5,494 posts
  • Gender:Not Telling

Posted 24 March 2018 - 01:43 AM

Johnny's crash last month scrambled the mysql innodb tables. We managed to repair them enough to get them available in read-only mode so people could take backups. Everyone who needed a backup has surely made it themselves by now, so we're bringing innodb tables back online in read-write mode. It is likely that some innodb data has been lost, but you should be able to restore the backup you took and restore your database yourself. If you failed to take a backup in the allotted time we may be able to help you. Just let us know. As always we highly recommend using myisam instead of innodb. If you have no idea what either of those are don't worry about it too much because we have myisam set as the default. Innodb is fairly delicate and pretty much anything can corrupt it causing data loss. Myisam is pretty much impossible to corrupt. We've never lost any myisam data in the entire 13 years we've been providing hosting. Innodb on the other hand crashes fairly often. Let us know if you have any questions.
This is an unmonitored account for announcements only.
Wiki | Facebook | Twitter
Posted ImagePosted ImagePosted Image
Posted ImagePosted ImagePosted Image

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users