Stopping, Starting and Restarting

From the MySQL Cloud Service console, you can stop, start and restart the compute nodes associated with a MySQL Server deployment on MySQL Cloud Service.

Topics

About Stopping, Starting and Restarting a MySQL Server Deployment

About Stopping a Database Deployment

When you stop MySQL Cloud Service, no access is possible and you cannot perform management operations on it except to start it or to delete it.

Stopping a MySQL Server deployment is similar to turning off your personal computer; it has no computing capabilities because the CPU and RAM have no power, but all its other resources—disk drives and the data they contain, static IP reservations, and so on—remain and are ready to be put back into use when power is restored.

When MySQL Server deployment is stopped, its CPU and RAM (an Oracle Compute Cloud Service instance) are stopped. As a consequence, it consumes no OCPU or memory resources and so metering and billing of these resources stop. However, all the other resources of the database deployment continue to exist and so continue to be metered and billed, including:

Oracle Compute Cloud Service resources such as storage volumes and IP address reservations
Oracle Storage Cloud Service storage space used by the database deployment’s backups to the Oracle Cloud (if the MySQL Server deployment was being backed up to cloud storage)

Additionally, when MySQL Server deployment is stopped, backups are not performed.

About Starting a Stopped MySQL Server Deployment

When you start a stopped MySQL Cloud Service database deployment, access becomes possible again and you can perform management operations on it such as scaling and patching.

Starting a stopped database deployment is similar to turning your personal computer back on: its computing capabilities are restored because the CPU and RAM again have power, and all its other resources are put back into use.

When a database deployment is started:

An Oracle Compute Cloud Service instance of the appropriate compute shape (OCPU and memory) is allocated to it.
All other Compute Cloud Service resources associated with it when it was created or as the result of a scaling operation are reattached to it.
The allocated Oracle Compute Cloud Service instance is started.

After these steps complete, the MySQL Server deployment is running and available.

Because the MySQL Server deployment again consumes OCPU and memory resources, metering and billing of these resources resume.

About Restarting a MySQL Server Deployment

When you restart a MySQL Cloud Service database deployment, it is stopped and then immediately started again. Thus, the information about what happens when stopping and starting a database deployment applies to restarting a database deployment as well, just in immediate succession.

Stopping a MySQL Server Deployment

In general, you stop a MySQL Cloud Service database deployment for one of these reasons:

To prohibit access to it.
To reduce its cost of operation, especially if its billing frequency is hourly.

Before You Begin

To learn what happens when you stop a MySQL Cloud Service database deployment, review About Stopping, Starting and Restarting a MySQL Server Deployment.

Procedure

To stop a database deployment:

Open the MySQL Cloud Service console.

For detailed instructions, see Accessing MySQL Cloud Service Console.
In the list of deployments, click the name of the database deployment you want to stop.

The MySQL Cloud Service Overview page is displayed.
From the menu for the database deployment’s compute node, select Stop, and then confirm the action.

The deployment first has a status of Maintenance and then Stopped in the MySQL Cloud Service console.

Note:
It is not possible to scale a stopped deployment.

Starting a Stopped MySQL Server Deployment

Before You Begin

To learn what happens when you start a stopped MySQL Cloud Service deployment, review About Stopping, Starting and Restarting a MySQL Server Deployment.

Procedure

To start a stopped MySQL Server deployment:

Open the MySQL Cloud Service console.

For detailed instructions, see Accessing MySQL Cloud Service Console.
In the list of deployments, click the name of the stopped MySQL Server deployment you want to start.

The MySQL Cloud Service Overview page is displayed.
From the menu for the MySQL Server deployment’s compute node, select Start, and then confirm the action.

The deployment has a status of Maintenance in the MySQL Cloud Service console until it is fully started.

Restarting a MySQL Server Deployment

Note:

Restarting a MySQL Server deployment is different from rebooting a compute node of a MySQL Server deployment. Rebooting a compute node, as described in Rebooting a Compute Node, does not restart the MySQL Server deployment. It simply reboots the compute node.

Before You Begin

To learn what happens when you restart a MySQL Cloud Service deployment, review About Stopping, Starting and Restarting a MySQL Server Deployment.

Procedure

To restart a MySQL Server deployment:

Open the MySQL Cloud Service console.

For detailed instructions, see Accessing MySQL Cloud Service Console.
In the list of deployments, click the name of the MySQL Server deployment you want to restart.

The MySQL Cloud Service Overview page is displayed.
From the menu for the MySQL Server deployment’s compute node, select Restart, and then confirm the action.

The deployment has a status of Maintenance in the MySQL Cloud Service console until it is fully restarted.

Viewing Past Stop, Start and Restart Activity

You can see information about past stop, start and restart activity by viewing the activity log:

Open the MySQL Cloud Service console.

For detailed instructions, see Accessing MySQL Cloud Service Console.
In the list, click the name of the MySQL Server deployment whose past activity you want to view.

The MySQL Cloud Service Overview page is displayed.
Click the triangle icon to the left of the Activity title to expand the activity log.

The activity log shows information about past operations performed on the MySQL Server deployment, with the most recent activity first.
Click the icon next to a particular operation to see details about that operation.

If an operation failed, the details include information about why it failed.