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
- Log in to the management console.
- Click
in the upper left corner and select a region and a project.
- Click Service List. Under Database, click Relational Database Service.
- On the Instances page, locate the primary instance that you want to stop and choose in the Operation column.
- In the displayed dialog box, click OK.
- Refresh the instance list and view the status of the instance. If the status is Stopped, the instance is stopped successfully.
Parent topic: Instance Lifecycle
- Scenarios
- Constraints
- Procedure