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 https://www.digitalocean.com/customers/ghost/ 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.
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?
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.×