Stopping an Instance

Scenarios

If you use DB instances only for routine development, you can temporarily stop pay-per-use instances to save money. You can stop an instance for up to 15 days.

Billing

After a DB instance is stopped, the VM where the DB instance is located is no longer billed. Other resources, including EIPs, storage resources, and backups, are still billed.

Constraints

• Only cloud SSD and extreme SSD pay-per-use instances can be stopped. RDS instances in a DCC cannot be stopped.
• If you stop a primary instance, read replicas (if there are any) will also be stopped. They are stopped for up to 15 days by default. You cannot stop a read replica without stopping the primary instance.
• A stopped instance cannot be deleted through the console.
• Stopping a DB instance will also stop its automated backups. After the DB instance is started, a full backup is automatically triggered.
• If you do not manually start your DB instance within 15 days after it is stopped, the instance will automatically start during the next maintenance window. For details about the maintenance window, see Changing the Maintenance Window. To start an instance, see Starting an Instance.
• A stopped pay-per-use instance may fail to start due to insufficient ECS resources. If this happens, try again later. If you need assistance, submit a service ticket.

Procedure

1. Log in to the RDS console.
2. Click in the upper left corner and select a region.
3. On the Instances page, locate the primary instance that you want to stop and choose More > Stop in the Operation column.
4. In the displayed dialog box, enter YES and click OK.
   Figure 1 Stopping an instance
   

5. Refresh the instance list and view the status of the instance. If the status is Stopped, the instance is stopped successfully.