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 больше 2 лет ago

quite hard

Dodzi A. · Reviewed больше 2 лет ago

Mariana A. · Reviewed больше 2 лет ago

Anrie S. · Reviewed больше 2 лет ago

Vinicius S. · Reviewed больше 2 лет ago

Felipe S. · Reviewed больше 2 лет ago

Lab is broken!

Ossie B. · Reviewed больше 2 лет ago

Soumen C. · Reviewed больше 2 лет ago

Avisek K. · Reviewed больше 2 лет ago

Monika G. · Reviewed больше 2 лет ago

Rohan P. · Reviewed больше 2 лет ago

Soumen C. · Reviewed больше 2 лет ago

Avisek K. · Reviewed больше 2 лет ago

Artur K. · Reviewed больше 2 лет ago

Gustavo Alberto V. · Reviewed больше 2 лет ago

Artur K. · Reviewed больше 2 лет ago

Vakcharla R. · Reviewed больше 2 лет ago

Beth D. · Reviewed больше 2 лет ago

Juan Alejandro O. · Reviewed больше 2 лет ago

OK

Jarosław K. · Reviewed больше 2 лет 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 больше 2 лет 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 больше 2 лет ago

Santhosh Kumar M. · Reviewed больше 2 лет ago

Yuriy L. · Reviewed больше 2 лет ago

Jean-Luc A. · Reviewed больше 2 лет ago