Timeline for Database migration - Simply change connection string?
Current License: CC BY-SA 3.0
10 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Sep 11, 2015 at 17:34 | vote | accept | rinogo | ||
Sep 11, 2015 at 0:48 | comment | added | rinogo | Everything seems to have gone smoothly with the transition - thanks for your advice, Rolando! Hopefully some of this helps someone else in the future! | |
Sep 10, 2015 at 22:08 | comment | added | RolandoMySQLDBA | If the original Master is still in use, then Yes. | |
Sep 10, 2015 at 22:05 | comment | added | rinogo |
Since read_only was set to 1 on the original master (web server), isn't that where we'd want to run SET GLOBAL read_only = 0; ?
|
|
Sep 10, 2015 at 21:58 | comment | added | RolandoMySQLDBA |
You need to run on the new Master SELECT @@global.read_only; . If it comes back 0, you're OK. If not, then run SET GLOBAL read_only = 0; .
|
|
Sep 10, 2015 at 21:55 | comment | added | rinogo |
Ok, final question - We're actually only migrating some of the databases to the database server. Smaller databases used by cPanel/WHM/etc on the web server will not be migrated. In order to not leave the web server's database in a read-only state, can we simply execute SET GLOBAL read_only = 0; on master (the web server) at the end of this entire process?
|
|
Sep 10, 2015 at 21:55 | comment | added | RolandoMySQLDBA |
Yes, SHOW SLAVE STATUS\G is to be run on the Slave. It should return Empty set (0.00 sec) .
|
|
Sep 10, 2015 at 21:53 | comment | added | rinogo |
Also, I'm assuming that SHOW SLAVE STATUS\G is to also be executed on the slave (new database server), correct?
|
|
Sep 10, 2015 at 21:52 | comment | added | rinogo | Awesome! I'll give it a shot. Is this not the typical way to move a live, production database to another server? This seems like the "bread and butter" of a DBA. I'm surprised I couldn't find more documentation about this online! | |
Sep 10, 2015 at 21:47 | history | answered | RolandoMySQLDBA | CC BY-SA 3.0 |