Parameter | Description |
Product Type | The billing method of the backup schedule that you want to purchase. Select Backup Instance. Note You cannot create a pay-as-you-go backup schedule in the DBS console. |
Region for Backup Instance | The region in which you want to store the backup data. Note Backup in the same region: Select the region in which the database to be backed up resides. Geo-redundancy: Select a region different from that of the database to be backed up. This method provides a better disaster recovery capability but may charge you additional fees. For example, if you want to back up a database from the China (Beijing) region to DBS in the China (Shanghai) region, select the China (Shanghai) region. For more information, see Overview.
|
Data Source Type | The data source type of the database to be backed up. Note If the data source is an ApsaraDB RDS for MySQL instance, a self-managed MySQL database, or a PolarDB for MySQL cluster, select MySQL. For more information about how to select a data source type, see Database engines and features. |
Specification | The backup schedule specifications that you want to use. Higher specifications offer higher backup and restoration performance. DBS supports the following backup schedule specifications: micro, small, medium, large, and xlarge. The xlarge specification type provides extra large specifications without an upper limit on the amount of backup data. To ensure fast backup and restoration of specific database instances, such as database instances in the production environment, we recommend that you select the xlarge or large specification type. If you do not require high backup and restoration performance, you can select the most cost-effective backup schedule specifications based on your business requirements. For more information, see Select a backup schedule type. If the databases and tables that you want to back up involve issues such as unreasonable table schemas, large tables, or large fields, and you select a low-specification backup schedule type, the resources of the backup schedule may be insufficient to back up the databases or tables. In this case, backup exceptions occur. To prevent backup exceptions, we recommend that you select a high-specification backup schedule type.
|
Backup Method | The backup method that you want to use. Valid values: Physical Backup: You can perform a physical backup only on self-managed databases, but not ApsaraDB RDS instances. You can use this method to back up database files in the operating system. In most cases, physical backup and restoration are faster than logical backup and restoration. You can also use a sandbox instance for emergency disaster recovery. For more information, see Use the emergency recovery feature for a self-managed MySQL database. Logical Backup: You can perform a logical backup on ApsaraDB RDS instances, self-managed databases in data centers, and self-managed databases hosted on Elastic Compute Service (ECS) instances. You can use this method to back up database objects, including tables, indexes, and stored procedures. DBS allows you to back up specified databases and tables in a fine-grained way. For more information, see Restore data by database or table.
|
Storage Size | The storage capacity of the backup schedule that you want to purchase. You do not need to specify the storage capacity when you purchase a backup schedule. You are charged for the amount of your data that is stored in DBS. Note If you back up a large amount of data, we recommend that you purchase a backup instance storage plan provided by DBS to offset the storage fees of built-in DBS storage for the backup schedule. For more information about how to purchase a storage plan, see the FAQ section of this topic. For information about fees that may be incurred for a backup schedule, see Billing FAQ.
|
Resource Group | The resource group that is used by the backup schedule. You can select the default resource group or a custom resource group to facilitate backup schedule management. |
Quantity | The number of backup schedules that you want to purchase. Note A backup schedule can be used to back up only one database instance. To back up multiple database instances, you must purchase multiple backup schedules. For example, if you want to back up ApsaraDB RDS for MySQL Instance A and ApsaraDB RDS for MySQL Instance B, you must purchase two backup schedules. A backup schedule can be used to back up only one type of database. To back up multiple types of databases, you must purchase multiple backup schedules. For example, if you want to back up a self-managed SQL Server database and a self-managed MySQL database, you must purchase two backup schedules.
|
Subscription Duration | The subscription duration for the backup schedule that you want to purchase. |