Stop an ApsaraDB RDS for SQL Server instance - ApsaraDB RDS

If you do not need to use an ApsaraDB RDS for SQL Server instance for a specified period of time, you can stop the RDS instance. After the RDS instance is stopped, the computing resources of the RDS instance are released, and you are no longer charged for the computing resources.

Background information

When you use an RDS instance, you may encounter the following situations:

You want to stop the RDS instance but you want to retain data.
For O&M and production purposes, you want to stop the RDS instance to check and monitor the business status.
You want to stop the RDS instance to resolve other issues that require instance suspension.

Prerequisites

Your RDS instance uses the pay-as-you-go billing method. If your RDS instance uses the subscription billing method, you must change the billing method to pay-as-you-go. For more information, see Switch an ApsaraDB RDS for MySQL instance from subscription to pay-as-you-go.
Your RDS instance uses standard SSDs or enhanced SSDs (ESSDs).
Note You cannot stop an RDS instance that runs SQL Server 2008 R2 and uses local SSDs. Before you can stop the RDS instance, you must upgrade the RDS instance to SQL Server 2012 or SQL Server 2016. For more information, see Upgrade an ApsaraDB RDS for SQL Server instance with local SSDs from SQL Server 2008 R2 to SQL Server 2012 or SQL Server 2016.
Your RDS instance belongs to the dedicated instance family or the general-purpose instance family. For more information, see Instance families.
Your RDS instance is a primary RDS instance and no read-only RDS instances are attached to the primary RDS instance.
Your RDS instance is in the Running state.

Limits

You cannot stop an RDS instance that resides in the classic network. For more information about how to change the network type of an RDS instance, see Change the network type of an ApsaraDB RDS for SQL Server instance.
You cannot stop an RDS instance that belongs to a shared instance family.
If read-only RDS instances are attached to the primary RDS instance, you cannot stop the primary RDS instance or read-only RDS instances. For more information, see Create a read-only ApsaraDB RDS for SQL Server instance.

Billing rules

The following table describes the billing rules when the RDS instance is in different states.


Instance state	Instance type fee	Storage capacity fee	Backup storage fee
Running	Charged	Charged	Charged
Suspending	Charged	Charged	Charged
Suspended	Free of charge	Charged	Charged
Starting	Free of charge	Charged	Charged

Note After an RDS instance is stopped, the computing resources of the RDS instance are released, and no fees are generated for computing resources. You are charged for storage capacity and backup storage. For more information, see Billable items, billing methods, and pricing.

Stop an RDS instance

Usage notes

After you stop an RDS instance, the original internal and public endpoints of the RDS instance remain unchanged. After you start the RDS instance, you can still use the endpoints to connect to the RDS instance.
When you stop an RDS instance, the status of the RDS instance changes from Running to Stopping. After the RDS instance is stopped, the status changes to Stopped.
Note After an RDS instance is stopped, you can restart the RDS instance only by performing the following operations: Choose More > Start Instance in the Actions column of the RDS instance. For more information, see Start an RDS instance.
After an RDS instance is stopped, only the data that is stored in the storage of the RDS instance is retained. The data that is stored in the memory is deleted.
After an RDS instance is stopped, you cannot perform O&M operations, such as configuration change, zone migration, and instance restart. The unhandled events are not deleted.
After an RDS instance is stopped, all features such as instance connection, backup, and specification change become unavailable. We recommend that you take appropriate measures before you stop the RDS instance.
After an RDS instance is stopped, the system retains the most recent full backup file. Other backup files including full and incremental backup files expire after the retention period elapses.
Warning If a backup file expires, you cannot restore data to a specific point in time by using the backup file. Alibaba Cloud is not responsible for data loss or the consequences caused by the expiration of backup files.
After an RDS instance is stopped, the computing resources of the RDS instance are recycled, and the RDS instance may fail to restart due to insufficient resources. You can try again later or restore the data to another RDS instance by using the full backup method. For more information, see Restore the data of an ApsaraDB RDS for SQL Server instance.

Procedure

Log on to the ApsaraDB RDS console. In the left-side navigation pane, click Instances. In the top navigation bar, select the region in which your RDS instance resides.
Find the RDS instance that you want to stop and choose More > Pause to use in the Actions column.
In the Stop Instance dialog box, click OK.
Wait until Stopped is displayed in the Instance Status column of the RDS instance on the Instances page.

Start an RDS instance

Log on to the ApsaraDB RDS console. In the left-side navigation pane, click Instances. In the top navigation bar, select the region in which your RDS instance resides.
Find the RDS instance that you want to start and choose More > Start Instance in the Actions column.
In the Start Instance message, click OK.
Wait until Running is displayed in the Instance Status column of the RDS instance on the Instances page.
Note
- When you start the RDS instance, the status of the RDS instance changes from Stopped to Starting. After the RDS instance is started, the status changes to Running.
- Approximately 3 to 5 minutes are required for the instance status to change from Starting to Running.

FAQ

Do I need to restart or restore my RDS instance after I start the RDS instance?
No, you do not need to restart or restore your RDS instance after you start the RDS instance. After you start a stopped RDS instance, no additional operations are required. For more information about how to start a stopped RDS instance, see Start an RDS instance.
Is the historical monitoring data of an RDS instance retained after the RDS instance is stopped?
Yes, the historical monitoring data of an RDS instance is retained after the RDS instance is stopped.
Is the data in the memory of an RDS instance retained after the RDS instance is stopped?
No, the data in the memory of an RDS instance is not retained after the RDS instance is stopped. Only the data that is stored in the storage is retained after the RDS instance is stopped.
Are the unhandled events deleted after an RDS instance is stopped?
No, the unhandled events are not deleted after an RDS instance is stopped. O&M operations, such as configuration change, zone migration, and instance restart, cannot be performed after an RDS instance is stopped.
Does the backup retention period of an RDS instance cover the period of time during which the RDS instance is stopped?
No, the backup retention period of an RDS instance does not cover the period of time during which the RDS instance is stopped. The backup retention period that is specified in the backup policy applies to the backup files that are generated after the RDS instance is stopped. The most recent full backup file of the RDS instance is retained even if the specified backup retention period elapses.
If an RDS instance is deployed in the multi-zone method, is a switchover between the zones of the primary and secondary RDS instances performed after the RDS instance is started?
Yes, a switchover between the zones of the primary and secondary RDS instances may be performed instance after the RDS instance is started.