The following table lists the limits for the Data Disaster Recovery (DBS) sandbox feature.
| Limit | Value | Notes |
|---|---|---|
| Supported database types | ApsaraDB RDS for MySQL instances that use local SSDs, self-managed MySQL databases, and self-managed Oracle databases | — |
| Backup type | Physical backup | — |
| Supported regions | China (Hangzhou), China (Shanghai), China (Shenzhen), China (Heyuan), China (Chengdu), China (Beijing), China (Zhangjiakou), China (Hohhot), China (Ulanqab), China (Hong Kong), Singapore, Malaysia (Kuala Lumpur), Indonesia (Jakarta), Japan (Tokyo), Germany (Frankfurt), US (Silicon Valley), US (Virginia), and China East 1 Finance | — |
| Maximum number of snapshots | Capacity Edition: limited by sandbox storage capacity. Performance Edition: limited by snapshot creation frequency | — |
| Snapshot creation frequency | Maximum interval: 10 minutes | If the interval between two consecutive incremental logs exceeds 10 minutes, DBS generates snapshots at maximum capacity and the actual interval may exceed 10 minutes. |
| Supported snapshot types | Full backup and incremental backup | — |
| Maximum sandbox storage capacity | Capacity Edition: 8 TB. Performance Edition: not limited | — |
| CPU cores per sandbox instance | 1–8 (exclusive CPU resources) | — |
| Maximum number of sandbox instances | 1,000 | — |
| Maximum duration of a single sandbox instance | Not limited | — |
What's next
To restore an ApsaraDB RDS for MySQL instance in an emergency, see Use the emergency recovery feature for an ApsaraDB RDS for MySQL instance.
To restore a self-managed MySQL database in an emergency, see Use the emergency recovery feature for a self-managed MySQL database.
For answers to common questions about sandbox instances, see the FAQ.