cirisme
Wed 5th Nov '03, 4:57pm
Erwin has talked about his backup method of copying the MySQL files directly and copying them to get a full backup.
Well, this is looking very appealing to me. Cpanel's backups always cause the server load to jump well above 150... sometimes even to 300, and MySQL's dump utility gives out about 100 megs before it's complete.(watchdog kills any processes that go longer than 5 minutes which is why)
I was wondering what was required to make this work without corrupting the files and getting the safest backup.
I'm guessing the script would shut down apache(to prevent the vb database emails), and mysql, copy the files, then start mysql then apache. If mysql doesn't want to start, how can you prevent Apache so you don't get thousands of emails from vb?
If any generous soul wants to share their scripts, that would be great! ;)
Well, this is looking very appealing to me. Cpanel's backups always cause the server load to jump well above 150... sometimes even to 300, and MySQL's dump utility gives out about 100 megs before it's complete.(watchdog kills any processes that go longer than 5 minutes which is why)
I was wondering what was required to make this work without corrupting the files and getting the safest backup.
I'm guessing the script would shut down apache(to prevent the vb database emails), and mysql, copy the files, then start mysql then apache. If mysql doesn't want to start, how can you prevent Apache so you don't get thousands of emails from vb?
If any generous soul wants to share their scripts, that would be great! ;)