You can create a backup schedule on either of the following pages:
The following performance test results are for reference only and shall not be used to evaluate SLA performance.
This section tests the backup and recovery performance of multiple instance types. The results are intended as a reference for your decision making.
- Type: DBS supports multiple instance types, which offer different performance based on the CPU, memory, and network bandwidth settings of the backup server.
- RPS: Represents the number of record changes on the source database in every minute during backup and recovery. These record changes are caused by data modification operations such as insert, update, and delete. If one SQL statement involves operations on multiple data rows, multiple record changes are noted. If repeated operations are performed on the same record, multiple record changes are noted. Each commit operation is also seen as one record change.
Test procedure:Create an ApsaraDB for MySQL instance as the test database. Create a backup plan and enable full backup and incremental backup. Backup the test database and store backup sets in OSS. Use backup sets to restore the test database.
|Type||Common ApsaraDB for RDS instance|
- Database size: 102 GB
- Total number of records: 150 million
- Size of each record: 100~1K
- Number of fields: 3 to 22 columns
- Field types: Basic MySQL data types
Note: If the backup source database contains too many tables, table structure recovery could take a long time. We recommend that you keep a maximum of 10,000 tables in each database. If the backup source database contains tables without a primary key, or tables with a string type primary key or composite key, this could also slow down the backup process.
|Instance type||RPS(Record Per Second)||MBPS(MByte Per Second)|
Note: If the target database contains too many tables, table structure recovery could take a long time. We recommend that you keep a maximum of 10,000 tables in each database.