Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

I configured the existing mysql db on the current droplet with a user with full permissions and allowed external connections to the db. Then went through the “set up migration” steps on the Managed DB page (entered host name, db name, un/pass) and clicked “Test Connection”. The connection worked just fine and prompted me to start the migration.
As soon as I clicked Start Migration, an “Unknown error occurred” messaged showed up with no other indication of the problem. In google DevTools the start migration api call returned {"id": "Internal Server Error", "message": "Server Error" }. After closing the popup and/or refreshing the page, the Managed DB screen doesn’t show that there is any ongoing migration happening.
There definitely is though because when connecting to the DB itself via a separate tool, the tables are being created and populated. However; it appears to be a one-off transfer and not an ongoing logical replication as the migration tool suggests it will be. I need the ongoing replication so there isn’t downtime when transitioning the app from using the original db to the new managed db.
hbarnard
keneucker
keneucker
rich
santoshpatil
Aspiresoftserv
Yakin
Thejaswini-Rao-U
775c69c916d345a7a367d867078ccb
mayricoak
ndam
bc2f52583874402a988f587c00195d