Digital Ocean Disk IOPS abuse when restoring very large database

I am looking to migrate a very large MySQL database (500GB) to another host. I was considering DigitalOcean but am concerned about potentially being flagged as an abusive customer as I would be hitting the disk IO very hard for the initial migration and for some steps following (rebuilding of indexes and the like).

I noticed that Ghost migrated over and they presumably have a very large database that needed to be migrated as well, however they may have had a special deal to achieve this.

In short.

Will my instances be stopped/deleted or flagged as being abusive for a move like this? How is it suggested to make a move like this?

Submit an answer
Answer a question...

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Accepted Answer

@boyter - Contact DO directly to migrate your system at little to no cost.

@gndo The migration isn’t the issue. Its the expected disk hammering. I did take your advice however and they said there should not be any issues other then network bandwidth and to keep that below 200mbit.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.