vpruthi/doc-exports
1
0
Fork 0
forked from docs/doc-exports
Code Pull Requests Activity
doc-exports/docs/rds/umn/rds_pg_stop.html
Wang , Deng Ke 79b1bc1455 RDS UMN 20221101 version 
Reviewed-by: Hasko, Vladimir <vladimir.hasko@t-systems.com>
Co-authored-by: Wang , Deng Ke <wangdengke2@huawei.com>
Co-committed-by: Wang , Deng Ke <wangdengke2@huawei.com>
2023-01-09 10:26:58 +00:00

4.5 KiB
Raw Permalink Blame History

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 seven days.

Constraints

  • If you stop a primary instance, read replicas (if there are any) will also be stopped. They are stopped for up to seven days. You cannot stop a read replica without stopping the primary instance.
  • A stopped instance will not be moved to the recycle bin after being deleted.
  • If you do not manually start your stopped DB instance after seven 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 a DB instance, see Starting an Instance.
  • After a DB instance is stopped, billing for instance usage duration will stop.

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. The RDS console is displayed.
  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 Yes.
  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