yexinru/doc-exports
1
0
Fork 0
forked from docs/doc-exports
Code Pull Requests Activity
Files
ac787f42f1e2d2e611f07a75624c4380a68149aa
doc-exports/docs/rds/umn/rds_mssql_stop.html
wangdengke2 64672e58fb rds_umn 
Reviewed-by: Wagner, Fabian <fabian.wagner@t-systems.com>
Co-authored-by: wangdengke2 <wangdengke2@huawei.com>
Co-committed-by: wangdengke2 <wangdengke2@huawei.com>
2025-09-19 08:45:25 +00:00

3.9 KiB
Raw Blame History

Stopping a DB Instance

Scenarios

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

Billing

After a DB instance is stopped, the vm related to the DB instance is no longer billed. Other resources, including EIPs, storage resources, and backups, are still billed.

Constraints

  • If you stop a primary instance, read replicas (if there are any) will also be stopped. They are stopped for up to 15 days. You cannot stop a read replica without stopping the primary instance.
  • A stopped instance cannot be deleted through the console.
  • Automated backups will not be created if a DB instance is in Stopped state. After the DB instance is started, a full backup is automatically triggered.
  • If you do not manually start your stopped DB instance after 15 days, your DB instance is automatically started during the next maintenance window. For details about the maintenance window, see Changing the Maintenance Window. To start an instance, see Starting a DB Instance.

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.
Parent topic: Instance Lifecycle