Quote:
Originally Posted by teh ghey
my social site has had 3 huge database (mysql) crashes in the past month. Everything gone, I had to restore from backup.
It just happened again tonight and I've been up the past 6 hours watching it.
Im really a nervous wreck, its 5:30am and im afraid to sleep or it might crash again lol.
anyways, whats a good setup to make sure that when something crashes its brought back the best way?
I mean right now I just wait for it to crash and then write to my website host to restore the database from a backup. They do and it still isnt right so I ask them to do a full stire restore, and then its all back with a few minor glitches.
is that the best way to do it, or is there a more professional way?
also I use phpmyadmin. is there something better I should use?
And how do you guys run a testing server? Is there something like microsoft site server but for freebsd, so I can test things and then publish to the site?
right now when I test things theyre live and its so amateurish to do that lol.
thanks for any advice
|
sounds like a bloated script with to many sql queries. the problem with social scripts is the creators rarely test them with real world people on the serve.
you can use a program like Mytop to monitor slow queries in real time on your server or you can turn slow query log dumping if you have access to you mysql conf file. I'm betting it's probably a lot of miss used Left Join, and not properly closing the database after each connection