Hi Prabhat, FYI
On Thu, Sep 15, 2011 at 10:33 AM, Suresh Kuna <sureshkumar...@gmail.com>wrote: > If the hardware on master and slave, version of mysql server, configuration > and memory allocations are same then you can do a clean shutdown of mysql on > slave and copy the files to master. Check if any memories needs to be > adjusted and start mysql adding the innodb_file_per_table option on master > server. So the table created in future also take the advantage of per table > option. > > > On Thu, Sep 15, 2011 at 1:41 AM, Reindl Harald <h.rei...@thelounge.net>wrote: > >> >> >> Am 14.09.2011 22:06, schrieb Prabhat Kumar: >> > Hi, >> > >> > I have 2 machine. Master and a slave replication. >> > >> > few days back I have switched slave machine (innodb_file_per_table) from >> single >> > innodb file to one per file table. >> > >> > Now I want to do for Master. >> > >> > Now question, >> > >> > Is it recommendable this method, stop MYSQL services on both and copy >> mysql >> > file's at system level (using scp or rync) form slave machine to master >> > (after deleting ibdata1 and ib_log). update the variable >> innodb_file_per_table >> > to switch master to one per file table. and start master.. >> > >> > or I can go with usual process.. export and import >> >> if you have a consistent mysql-server which can be stopped and the whole >> datadir >> copied whereever you want this was and will always be the best solution >> >> said this independent of the software becasue the only interesting fact is >> if the can data migrated 100% consistent, every sort of export/import >> is per design complexer, slower and maybe unsafer >> >> >> > > > -- > Thanks > Suresh Kuna > MySQL DBA > -- Thanks Suresh Kuna MySQL DBA
