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

Md. Mokit H. · Reviewed about 1 year ago

Dalia B. · Reviewed about 1 year ago

not working

Satish Vithal C. · Reviewed about 1 year ago

Vinit G. · Reviewed about 1 year ago

Si-Gwang J. · Reviewed about 1 year ago

Dacruz N. · Reviewed about 1 year ago

Si-Gwang J. · Reviewed about 1 year ago

I did the training but tasks 2 and onwards are not completed even though I was able to do the migration jobs and see that the bases are correct.

Carlos Alexandre J. · Reviewed about 1 year ago

João F. · Reviewed about 1 year ago

Parasram K. · Reviewed about 1 year ago

robert n. · Reviewed about 1 year ago

Marcelo d. · Reviewed about 1 year ago

me costo el promote por que se tarda mucho

Norma Estela L. · Reviewed about 1 year ago

Lab does not properly respect service networking API

Jason B. · Reviewed about 1 year ago

Margie J. · Reviewed about 1 year ago

Shrikant m. · Reviewed about 1 year ago

srinivas m. · Reviewed about 1 year ago

Oksana K. · Reviewed about 1 year ago

Oksana K. · Reviewed about 1 year ago

Rao c. · Reviewed about 1 year ago

Adriano D. · Reviewed about 1 year ago

Juan Jose S. · Reviewed about 1 year ago

OLEKSANDR S. · Reviewed about 1 year ago

Nirmala R. · Reviewed about 1 year ago

All steps except for the first one keeps failing for absolutely no reason. I tried following the instructions to the T, and when I gave up I tried using settings from previous labs such as mysql 5.7 instead of 8.0, but still all steps fail! The Cloud SQL instances EXIST and contain all data from the VM DB properly. Absolutely no reason to fail yet somehow your checks always fail. Please perform checks for EVERYTHING and provide exact errors to why it failed: Is it in the wrong region/zone? Is it the wrong configuration of instance? is data missing? wrong name of instance? wrong password? WHAT? WHAT IS WRONG?! EDIT: Thank you to the people in the comments here that shared the missing link - the migration job's name must be identical to the Cloud SQL instance name (provided by the lab). Finally managed to do this.

Yaron K. · Reviewed about 1 year ago