GoFuckYourself.com - Adult Webmaster Forum - Whats the smart way to have a database and testing server for a social site?

- Fucking Around & Business Discussion (https://gfy.com/forumdisplay.php?f=26)

Whats the smart way to have a database and testing server for a social site?

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

Why not find out what is causing MySQL to crash?

Quote:

Originally Posted by drocd (Post 15608008)

Why not find out what is causing MySQL to crash?

The maker of the software is taking his sweet time doing it. he acts like its my fault the database is crashing

there are easier ways to backup/restore database than with phpMyAdmin
for example from root:

Backup database

Code:

mysqldump db_name -r file_name.sql

Import database

Code:

mysql -uUSER -pPASS DB_NAME < FILE.SQL

this is much faster and easier way to backup and specially to restore a database

Quote:

Originally Posted by teh ghey (Post 15607420)

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

as for running a test server, just create a second domain and test all you stuff on that before moving it to your live site.

a test site is also good especially if you hire programmers to help out or need users to test things.