When you create MySQL Server deployments on MySQL Cloud Service, you use the Create MySQL Cloud Service Instance wizard, which steps you through the process of making the choices that create a deployment tailored to your needs. These choices include:
When creating a database deployment on MySQL Cloud Service, you choose the computing power for the associated compute node from a list of supported OCPU (Oracle CPU) and processor RAM combinations. The combinations you can choose from depend on the infrastructure you are creating the deployment in:
In Oracle Cloud Infrastructure:
VM.Standard1.1 - 1.0 OCPU, 7.0 GB RAM
VM.Standard1.2 - 2.0 OCPU, 14.0 GB RAM
VM.Standard1.4 - 4.0 OCPU, 30.0 GB RAM
VM.Standard1.8 - 8.0 OCPU, 56.0 GB RAM
VM.Standard1.16 - 16.0 OCPU, 240.0 GB RAM
VM.Standard2.1 - 1.0 OCPU, 15.0 GB RAM
VM.Standard2.2 - 2.0 OCPU, 30.0 GB RAM
VM.Standard2.4 - 4.0 OCPU, 60.0 GB RAM
VM.Standard2.8 - 8.0 OCPU, 120.0 GB RAM
BM.Standard1.32 - 36.0 OCPU, 256.0 GB RAM
BM.Standard2.52 - 52.0 OCPU, 768.0 GB RAM
In Oracle Cloud Infrastructure Classic:
OC3 - 1 OCPU, 7.5 GB RAM
OC4 - 2 OCPU, 15 GB RAM
OC5 - 4 OCPU, 30 GB RAM
OC6 - 8 OCPU, 60 GB RAM
OC7 - 16 OCPU, 120 GB RAM
OC1M - 1 OCPU, 15 GB RAM
OC2M - 2 OCPU, 30 GB RAM
OC3M - 4 OCPU, 60 GB RAM
OC4M - 8 OCPU, 120 GB RAM
OC5M - 16 OCPU, 240 GB RAM
When creating a database deployment on MySQL Cloud Service, you choose the amount of usable data storage you want for your database in gigabyte (GB) increments up to a maximum of 1 TB (1024 GB).
When creating a new database deployment on MySQL Cloud Service, you choose whether you want automatic backups to be configured for the database. Your choices are:
Both Cloud Storage and Local Storage—30 days' worth of backups are kept, with the 7 most recent days' worth available directly on the compute node’s local storage. This can be changed later.
None—automatic backups are not configured.
Do not use the Oracle Storage Cloud container that you are using to back up MySQL Cloud Service databases to cloud storage for any other purpose. For example, do not also use it to back up Oracle Java Cloud Service instances to cloud storage. Using the container for multiple purposes can result in billing errors.