Migrate MySQL Data to Cloud SQL using Database Migration Service: Challenge Lab avaliações

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

Oskar K. · Revisado há over 2 years

quite hard

Dodzi A. · Revisado há over 2 years

Mariana A. · Revisado há over 2 years

Anrie S. · Revisado há over 2 years

Vinicius S. · Revisado há over 2 years

Felipe S. · Revisado há over 2 years

Lab is broken!

Ossie B. · Revisado há over 2 years

Soumen C. · Revisado há over 2 years

Avisek K. · Revisado há over 2 years

Monika G. · Revisado há over 2 years

Rohan P. · Revisado há over 2 years

Soumen C. · Revisado há over 2 years

Avisek K. · Revisado há over 2 years

Artur K. · Revisado há over 2 years

Gustavo Alberto V. · Revisado há over 2 years

Artur K. · Revisado há over 2 years

Vakcharla R. · Revisado há over 2 years

Beth D. · Revisado há over 2 years

Juan Alejandro O. · Revisado há over 2 years

OK

Jarosław K. · Revisado há over 2 years

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. · Revisado há over 2 years

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. · Revisado há over 2 years

Santhosh Kumar M. · Revisado há over 2 years

Yuriy L. · Revisado há over 2 years

Jean-Luc A. · Revisado há over 2 years