Migrate MySQL Data to Cloud SQL using Database Migration Service: Challenge Lab Reviews

lab issues when migration job / connection profiles names are different than source/target instances

Oskar K. · Reviewed over 2 years ago

quite hard

Dodzi A. · Reviewed over 2 years ago

Mariana A. · Reviewed over 2 years ago

Anrie S. · Reviewed over 2 years ago

Vinicius S. · Reviewed over 2 years ago

Felipe S. · Reviewed over 2 years ago

Lab is broken!

Ossie B. · Reviewed over 2 years ago

Soumen C. · Reviewed over 2 years ago

Avisek K. · Reviewed over 2 years ago

Monika G. · Reviewed over 2 years ago

Rohan P. · Reviewed over 2 years ago

Soumen C. · Reviewed over 2 years ago

Avisek K. · Reviewed over 2 years ago

Artur K. · Reviewed over 2 years ago

Gustavo Alberto V. · Reviewed over 2 years ago

Artur K. · Reviewed over 2 years ago

Vakcharla R. · Reviewed over 2 years ago

Beth D. · Reviewed over 2 years ago

Juan Alejandro O. · Reviewed over 2 years ago

OK

Jarosław K. · Reviewed over 2 years ago

I migrade 2x my stand alone to Cloud SQl sadly unable to positive check it. Name of migration job need to be that same as creating instance with is not written in task.

Mateusz K. · Reviewed over 2 years ago

Task 1 EXPLICITLY mentioned using the EXTERNAL IP Address of the VM Instance. I followed this instruction for two attempts that failed. Every other lab with a similar setup used the INTERNAL IP address instead. I used it in this last attempt and the lab finally completed.

Jose Alfron B. · Reviewed over 2 years ago

Santhosh Kumar M. · Reviewed over 2 years ago

Yuriy L. · Reviewed over 2 years ago

Jean-Luc A. · Reviewed over 2 years ago