Thanks to the help before about backing up via FTp to Ibackup, seems like a great solution! However I've been messing around with mySQL, creating tables etc, and one thing that has crossed my mind is that the tbales all get created in a directory that has nothing to do with the site. So when you backup a site you would not be backing up the mySQL table? Is that right? If so how do I get it to backup the mySQL tables?

Well, maybe this would fall under the whole system backup? I need to learn more about SQL and find the answer to this one as well. Also, how you'd transfer a site from one machine to another that uses mySQL tables (possibly a non-RaQ machine even).

I'll add that Matt has obviously transfered this site to multiple machines and backed up the SQL db of this site, etc., so he might be at least one person to ask.

We run the following scripts on our MySQL server:

http://perl.apache.org/guide/snippets.html#Mysql_Backup_and_Restore_Scripts

You can set them to run as a cron job. This also allows you to restore them to any server.

Hope this helps

Chicken,

>>Well, maybe this would fall under the whole system backup? I need to learn more about SQL and find the answer to this one as well. Also, how you'd transfer a site from one machine to another that uses mySQL tables (possibly a non-RaQ machine even).<<
Probably, but a pain in the arse to do that just because one use is running mySQL tables

>>I'll add that Matt has obviously transfered this site to multiple machines and backed up the SQL db of this site, etc., so he might be at least one person to ask. <<
No! All the tables I currenlty have are M$ Access which I'm converting/exporting so that mySQL can suck them in.

>>We run the following scripts on our MySQL server:
http://perl.apache.org/guide/snippets.html#Mysql_Backup_and_Restore_Scripts
You can set them to run as a cron job. This also allows you to restore them to any server.<<
Sounds like quite a good idea, but perhaps even better is to ave a cron jobs that exports the data into a protected website directory so that the data gets backed up (in whole) with the site? I suppose it would depend on the size of the tables to an extent...

Perhaps using DBase tables is easier after all, at least they can be stored locally!