| Billing Method |
- Subscription: A subscription instance is an instance that you can subscribe to for a specific period and pay for up front. For long-term use, the subscription billing method is more cost-effective than the pay-as-you-go billing method. You can receive larger discounts for longer subscription periods.
- Pay-As-You-Go: A pay-as-you-go instance is charged per hour based on your actual resource usage. The pay-as-you-go billing method is suitable for short-term use. If you no longer require your pay-as-you-go instance, you can release the instance to reduce costs.
|
| Restore Method |
- By Time: allows you to restore data to a point in time within the specified log retention period. The time is accurate to the second. For more information about how to view or change the log backup retention period, see Back up an ApsaraDB RDS for SQL Server instance.
- By Backup Set: allows you to restore the data from a data backup file.
Note
- The By Time option appears only when the log backup feature is enabled.
- You can restore some or all of the databases that are created on the original RDS instance.
|
| Database |
Specify whether to restore some or all of the databases that are created on the original RDS instance. If you select Part, you must manually enter the names of the databases that you want to restore. In addition, you must separate the database names with commas (,).
Note If you have enabled the snapshot backup feature for the original RDS instance, you can select only
All but not
Part. For more information, see
Snapshot backup.
|
| Edition |
- Basic: The database system consists of only one RDS instance. Computing is separated from storage to increase cost-effectiveness.
- High-availability: The database system consists of one primary RDS instance and one secondary RDS instance. These RDS instances work in the high availability architecture.
- Cluster: The database system consists of one primary RDS instance, one secondary RDS instance, and up to seven read-only RDS instances. You can create read-only RDS instances to scale up the read capability of the database system.
|
| Zone |
A zone is an independent physical location within a region. The Zone of Primary Node parameter specifies the zone to which the primary RDS instance belongs. The Zone of Secondary Node parameter specifies the zone to which the secondary RDS instance belongs. You can select the Single-zone Deployment or Multi-zone Development method.
- Single-zone Deployment: If you select this deployment method, the Zone of Primary Node and the Zone of Secondary Node are the same.
- Multi-zone Development: This is the recommended deployment method. If you select this deployment method, the Zone of Primary Node and the Zone of Secondary Node are different. This allows you to provide zone-level disaster recovery. You must manually specify the Zone of Primary Node and the Zone of Secondary Node.
Note
- After the RDS instance is created, you can view information about the RDS instance and its secondary RDS instance on the Service Availability page.
- If you select the RDS Basic Edition, the database system consists of only one primary RDS instance and supports only the single-zone deployment method.
|
| Instance Type |
- General-purpose (Entry-level): belongs to the general-purpose instance family. A general-purpose instance exclusively occupies the allocated memory and I/O resources. However, it shares CPU and storage resources with the other general-purpose instances that are deployed on the same server.
- Dedicated Instance (Enterprise-level): belongs to the dedicated instance family. A dedicated instance exclusively occupies the allocated CPU, memory, storage, and I/O resources. The dedicated host instance family is the top configuration of the dedicated instance family. A dedicated host instance exclusively occupies all the CPU, memory, storage, and I/O resources of the server where it is deployed.
- Dedicated: A dedicated cluster exclusively occupies all the resources on a VM or physical host. The permissions to manage hosts in a dedicated cluster can be authorized to you. This allows you to create multiple database instances on a host. For more information, see Create hosts.
Note Each instance type supports a specific number of CPU cores, memory capacity, maximum number of connections, and maximum IOPS. For more information, see
Primary ApsaraDB RDS instance types.
|
| Capacity |
The storage capacity that the RDS instance has available to store data files, system files, binary log files, and transaction files. The storage capacity increases in increments of 5 GB.
Note The dedicated instance family supports exclusive allocations of resources. Therefore, the storage capacity of each instance type with local SSDs in this family is fixed. For more information, see
Primary ApsaraDB RDS instance types.
|