Stop an ApsaraDB RDS for SQL Server instance to release its computing resources and suspend the instance type fee. Storage and backup fees continue to apply while the instance is stopped.
Prerequisites
The instance must meet all of the following conditions:
| Condition | Requirement |
|---|---|
| Instance status | Running |
| Billing method | Pay-as-you-go or Serverless |
| Storage type | Enterprise SSD (ESSD) |
| Instance family | Dedicated or general-purpose |
| Network type | VPC. Classic network is not supported. To change the network type, see Change the network type. |
| Instance role | Primary instance with no read-only instances. A primary instance that has read-only instances cannot be stopped, nor can its read-only instances. |
| SQL Server version | This feature is not supported for instances that run SQL Server 2008 R2 and use local disks. To use this feature, first upgrade from SQL Server 2008 R2. |
Subscription instances must first change their billing method to pay-as-you-go before they can be stopped.
Stop an instance
The instance status transitions from Running to Stopping to Stopped.
The console label for this action is Pause To Use. Clicking it opens a dialog titled Stop Instance.
-
Log on to the ApsaraDB RDS console.
-
In the left-side navigation pane, click Instances.
-
In the top navigation bar, select the region of the instance.
-
Find the target instance and choose in the Actions column.
-
In the Stop Instance dialog box, click OK.
-
On the Instances page, verify that the instance status changes to Stopped.
Start an instance
The instance status transitions from Stopped to Starting to Running. The transition from Starting to Running takes about 3 to 5 minutes.
-
Log on to the ApsaraDB RDS console.
-
In the left-side navigation pane, click Instances.
-
In the top navigation bar, select the region of the instance.
-
Find the target instance and choose in the Actions column.
-
In the Start Instance dialog box, click OK.
-
On the Instances page, verify that the instance status changes to Running.
A primary/secondary failover may occur during startup. This can cause the primary and secondary zones to switch.
Billing impact
|
Instance status |
Instance type fee |
Storage space fee |
Backup set retention fee |
|
Running |
Charged |
Charged |
Charged |
|
Paused |
Charged |
Charged |
Charged |
|
Stopped |
Not charged |
Charged |
Charged |
|
Starting |
Not charged |
Charged |
Charged |
After an instance is stopped, the instance type fee stops. Storage space and backup set retention fees continue to accrue.
What happens when an instance is stopped
Retained
-
Endpoints: Internal and public endpoints are preserved. They become usable again after the instance restarts.
-
Storage data: All data on disk is retained.
-
Latest full backup: The most recent full backup is always kept, regardless of the retention period.
-
Monitoring data: Historical monitoring data remains accessible.
-
Pending events: Scheduled events such as zone migrations or specification changes in a maintenance window are not removed.
Released or cleared
-
Computing resources: CPU and memory are released. Because resources are released, the instance may fail to restart due to insufficient inventory. If this occurs, try again later or use a full backup to restore SQL Server data.
-
In-memory data: All data in memory is cleared.
Unavailable while stopped
-
Connections: Instance connections are unavailable while the instance is stopped.
-
Backups: Backup features are unavailable while the instance is stopped. Existing full and incremental backups continue to expire per the retention period. The backup retention period does not pause while the instance is stopped.
-
O&M operations: Specification changes, zone migrations, and manual restarts are blocked.
After a backup expires, you cannot use it to restore data to the corresponding point in time. Alibaba Cloud is not liable for any data loss or other consequences caused by backup expiration.
FAQ
After I start a stopped instance, do I need to restore data or perform additional setup?
No. The instance resumes with its previous configuration and data intact. No restore or reconfiguration is required.
Does the backup retention period pause while the instance is stopped?
No. Backups continue to expire on schedule per the backup policy. However, the system always retains the most recent full backup, even if it exceeds the retention period.
Can a stopped instance restart on a different primary zone?
Yes. A primary/secondary failover may occur when the instance starts, which can cause the primary and secondary zones to switch.