MySQL Replication Across Environments
Looking for ideas or best practices in this situation.
We have a client where everything is internal to their network. There are three different environments, Production, Pre-Production, and Dev. Currently the MySQL database is 1TB and there is no syncing between environments. When we want the latest production database in Dev for testing or troubleshooting, we have to take the last good backup, move the 1+TB mysqldump to the Dev server, then start the import which takes 3+ days.
We will have a chance to rearchitect these environments coming up and want to a solution in place that makes sense. It is feasible to have the production database replicated to the other environments so they are up to date. Then if they need to be used, we can break the replication, use them as a standalone for testing, then join back to the production database and have the data for testing be overwritten by the sync to production?
Is there any other way that this can be accomplished that I am just not thinking of?
Subject
Views
Written By
Posted
MySQL Replication Across Environments
2665
May 07, 2015 07:43AM
1328
May 07, 2015 07:49AM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.