I then started looking at alternatives and wondered if it was possible to simple create a database and then copy the .opt, .frm, .MYD and .MYI files into the directory of the other database, set chown for all those files to mysql.mysql and work with that.
Now I actually tested this by creating 2 new databases and in one a table with just a few id's and names. I then copied the files, changed ownership and went into PHPMyAdmin and so far so good, it seems to work.
Right, I believe that I have found a solid way and less stressing way of copying/backing up a database this way, but is it??
When I was running vB in an intranet and had direct access to both servers I would do this all the time. Just be sure to shut down everything mysql, apache, etc. so that nothing can touch the files. Then they're just files.
It wasn't until I started my own public vb site that I learned that I couldn't do this anymore. And then had to learn to deal with phpmyadmin and other such tools.
03-06-2011, 05:04 AM
And then had to learn to deal with phpmyadmin and other such tools.
Threaded Mode