Ok, I am using a pretty old MYSQL "mysql-5.0.27-win32" and the file and the structure maybe different from the latest Mysql (mysql 7).
Here is the current structure of of
In "mysql-5.0.27-win32" folder: bin data Docs Embedded examples include lib mysql-test scripts share sql-bench my-huge.ini my-innodb-heavy-4G.ini my-large.ini my-medium.ini my-small.ini
In "data" folder: mysql mydatabase ...some other databases that I don't touch.... my-PC.err my-PC.pid ib_logfile0 ---> this is a file, not a folder ib_logfile1 ---> this is a file, not a folder ibdata1 ---> this is a file, not a folder
the "mydatabase" folder has file such as .frm, .MYD, .MYI for each of its table, "mydatabase" also has "db.opt"
Ok, here is the scenarios. I finished developing my WebApp using
mysql-5.0.27-win32in my Local Desktop PC. Now it is a time to deploy my app.
To deploy, I copy the whole
mysql-5.0.27-win32 folder (which contains the current DB structure + some basic data) into Virtual Server.
So, there will be 2 same folders the original
mysql-5.0.27-win32 in the Local PC & the copy
mysql-5.0.27-win32 in the Virtual Server. At the beginning, these 2 folders are exactly the same. They have the same DB structures (ie same number of tables & columns in the tables) & same data stored in the tables.
From now on, my website will store user data directly to the copy
mysql-5.0.27-win32 folder in Virtual Server (VPS). But if the VPS got shutdown then I will lose all data.
Thus I want to back up daily the "mydatabase" from the copy
So which file in the "MySQL-5.0.27-win32" folder do i need to backup so that when I put them into the original
mysql-5.0.27-win32, then I can have exactly the same info as I have in the copy