nav-img
Advanced

Stopping an Instance

Scenarios

If you use DB instances only for routine development, you can temporarily stop pay-per-use instances to save money.

Constraints

  • A stopped instance will not be moved to the recycle bin after being deleted.
  • Stopping a DB instance will also stop its automated backups. After the DB instance is started, a full backup is automatically triggered.
  • If you stop a primary instance, read replicas (if there are any) will also be stopped. Both the primary instance and read replicas can be stopped for up to 15 days. You cannot stop a read replica without stopping the primary instance.
  • A stopped instance may fail to start due to insufficient ECS resources. If this happens, try again later or restore data from the latest backups by referring to Restoring a DB Instance from Backups.

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service.
  4. On the Instances page, locate the primary instance that you want to stop and choose More > Stop in the Operation column.
  5. In the displayed dialog box, click OK.
  6. Refresh the instance list and view the status of the instance. If the status is Stopped, the instance is stopped successfully.