This topic describes the limits on the sandbox feature provided by Database Backup (DBS).
Item | Limit |
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, Australia (Sydney) Closing Down, Malaysia (Kuala Lumpur), Indonesia (Jakarta), Japan (Tokyo), Germany (Frankfurt), US (Silicon Valley), US (Virginia), and China East 1 Finance. |
Maximum number of snapshots |
|
Snapshot creation frequency | Maximum snapshot interval: 10 minutes. If the interval between two consecutive incremental logs is more than 10 minutes, DBS generates sandbox snapshots at the maximum capacity. In this case, the snapshot interval may not be 10 minutes. |
Supported snapshot types | Full backup and incremental backup. |
Maximum capacity of sandbox storage |
|
Number of CPU cores of a sandbox instance | One to eight CPU cores. A sandbox instance uses exclusive CPU resources. |
Maximum number of sandbox instances | 1,000. |
Maximum duration of a single sandbox instance | Not limited. |
References
For more information about how to restore an ApsaraDB RDS for MySQL instance or a self-managed MySQL database in an emergency based on the DBS sandbox feature, see Use the emergency recovery feature for an ApsaraDB RDS for MySQL instance or Use the emergency recovery feature for a self-managed MySQL database.
For more information about the issues that you may encounter when you use the DBS sandbox feature, see FAQ.