Dress4Win has asked you for advice on how to migrate their on-premises MySQL deployment to the cloud. They want to minimize downtime and performance impact to their on-premises solution during the migration. Which approach should you recommend?
A.
Create a dump of the on-premises MySQL master server, and then shut it down, upload it to the cloud environment, and load into a new MySQL cluster.
B.
Setup a MySQL replica server/slave in the cloud environment, and configure it for asynchronous replication from the MySQL master server on-premises until cutover.
C.
Create a new MySQL cluster in the cloud, configure applications to begin writing to both on premises and cloud MySQL masters, and destroy the original cluster at cutover.
D.
Create a dump of the MySQL replica server into the cloud environment, load it into: Google Cloud Datastore, and configure applications to read/write to Cloud Datastore at cutover.
I think D it can't be, because you want to load a dump in a Cloud Datastore. If it were a Cloud Storage, it could be, but a Cloud datastore is a nosql.
It's true that you hace to use a dump, but to create a replica server/slave to promote to Cloud SLQ. So I think it is B.
IMPORTANT: Dress4Win is not anymore part of the officially listed case studies: https://cloud.google.com/certification/guides/professional-cloud-architect
B. Setup a MySQL replica server/slave in the cloud environment, and configure it for asynchronous replication from the MySQL master server on-premises until cutover.
If a database SLA or other requirements do not allow for an export-based migration, you should consider creating a replica of the database in which the replica database is in the Google cloud. This configuration is referred to as primary/replica or leader/follower , and in general it is the preferred migration method. Whenever there is a change to the primary or leader, the same change is made to the replica or follower instance. Once the database has synchronized the data, database applications can be configured to point to the cloud database.
Answer B
I will go with answer B, because this will avoid any downtime and performance impact. And post cutover this database can be used a master.
A -> Will cause downtime.
B -> Right choice
C -> Business impact, incosistency in data.
D -> Cloud DataStore is NoSQL DB
B is correct answer.
Datastore is no SQL database. And when we create a dupm and upload it we might lose some data during this process time that was served in the promiss site
It's B.
There's a similar question in the Linux Academy practice exam:
"Dress4Win is ready to migrate their on-premises MySQL deployment to the cloud. They want to reduce downtime and performance impact to their on-premises solution during the migration. What should they do?"
Answer: "Set up a MySQL replica/slave in Google Cloud using Cloud SQL and configure it for asynchronous replication from the MySQL master server on-premises until cutover."
Correct Answer is (B):
Please, stop to confuse the people with crazy ideas.
Every migration we should try to smooth or near zero downtime in DB cases.
The question clearly mention move MySQL to the cloud, minimize downtime and performance impact.
How you can recommend "D" to accomplish the previous premises?
Then if you setup a MySQL replica server/slave will be easy the cutover, just shut down the replica to on-premise and change the role for replica server from slave to primary. That is all! No impact, no service disruption, almost near zero downtime.
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
chiar
Highly Voted 5 years agoAD2AD4
Highly Voted 4 years, 6 months agojabrrJ68w02ond1
Most Recent 2 years, 1 month agoPime13
10 months, 3 weeks agoalexandercamachop
2 years, 3 months agojoe2211
3 years agovictory108
3 years, 5 months agoMamthaSJ
3 years, 5 months agoAusias18
3 years, 8 months agolynx256
3 years, 8 months agobnlcnd
3 years, 10 months agookixavi
4 years agoChulbul_Pandey
4 years agoHjameel
4 years agoAdityaGupta
4 years, 1 month agohomer_simpson
4 years, 1 month agobidibidiiii
4 years, 2 months agoESP_SAP
4 years, 3 months ago