| | |
| | You can choose recovery by backup set or by point in time. - Select By backup set, instances can be restored from a specified backup set, the backup set selection range is determined by the backup retention day.
- Select By point in time, instances can be restored to the specified point in time, and the supported recovery time range is affected by the backup retention policy.
|
Backup set or recovery time point | | Select a backup set or a point in time to restore based on the backup method you choose. - If the recovery method is By backup set, you need to select the backup set.
- If the recovery method is By point in time, you need to select the time point where the recovery is expected. Select the required backup set from the drop-down list.
|
| | Set the instance name. The instance name is optional, the default value is <source instance name> _recovery, and when empty, the instance ID is named. Naming rules are as follows: - The length should be between 1 and 128 characters.
- It cannot start with a digit or hyphen (-).
- The name consists of Chinese characters, English letters, digits, underscores (_), and hyphens (-).
|
| | Each specification has corresponding cores, memory, and maximum connections, which you can choose based on your business requirements. tip During restoration, the nodes of the new instance will be configured with the same specifications and availability zones as the primary, standby, and read-only nodes of the source instance by default. The same number of read-only nodes as the source instance will also be selected by default. You may reconfigure these settings based on your business requirements. When setting up, the following requirements must be met: - The specifications of the secondary and primary nodes must be consistent.
- The specification of a read-only node must be greater than or equal to that of the primary node.
- You can add up to 10 read-only nodes.
- Primary, secondary, and read-only nodes can be deployed in different availability zones within the same region.
|
| | Select the storage space for the instance. Storage space includes data space, log space, WAL log space, and transaction file space. The storage space ranges from 20 to 12,000 GB. Select reasonably based on business needs. tip Different specifications have different storage space value ranges. For detailed information on storage space value ranges, refer to Product specifications. |
| | Select the VPC used by the instance. tip - Virtual Private Cloud (VPC), is an isolated network environment with higher security and performance than traditional classical networks. You can create a new private network by clicking Create VPC on the right. For more details, see Creating a VPC.
- Only the virtual private cloud under the project specified in the navigation bar is supported for selection.
|
| | Select the subnets available to the instance in the VPC. tip - A subnet is an IP address block in the VPC. All cloud resources in the VPC must be deployed in subnets, which assign VPC IP addresses to the cloud resources. You can create a new subnet by clicking Create subnet on the right. For more details, see Creating a subnet.
- Only subnets in the availability zone where the instance is located can be selected.
- Subnet and VPC can be classified into different projects. Confirm that the target subnet and the selected VPC belong to the same project, which can be checked in the Project console.
|
| | Click the allowlist text box to go to the Associate allowlist page. Under this page, after checking the allowlist, click OK and go back to Restore to new instance page. The selected allowlist will be displayed in the allowlist text box. tip - On the Associate allowlist page, you can also create a new allowlist. For more information about creating an allowlist, see Creating an allowlist.
- An instance can associate up to 100 allowlists.
- Click the × after the allowlist to remove the allowlist.
- If there is a default allowlist set under the current account, the allowlist will appear in the allowlist text box.
|
| | Confirm the maintenance window for the instance. To modify, click the edit button to enter the maintenance window, set Maintainable day and Maintenance window, then click OK. tip - At least one day and up to seven days per week can be set as maintainable days.
- The maintenance window can only be set from 00:00 to 05:59 (UTC+08:00).
- The minimum duration of the maintenance window is 2 hours and the maximum duration is 6 hours. Cross-day settings are not allowed.
|
| | If TDE encryption is enabled on the original instance, the restored new instance will automatically enable TDE encryption and inherit the key configurations of the original instance. tip TDE encryption cannot be disabled once enabled. |
| | Select the project to which the instance belongs. tip - A project is a virtual concept that includes a set of resources, users, and roles. A project allows you to view and manage a group of resources in a unified manner and control the permissions of users and roles to these resources. For more details, refer to Resource management.
- If you do not select any projects, newly created instances are added to the default project (default).
|
| | Add tag(s) to the instance. Tags are used for the identification and classification of cloud resources. RDS for PostgreSQL supports adding tags to instances. You can classify PostgreSQL instances by tags to facilitate instance search and resource aggregation. For more information, see Tag overview. |
| | RDS for PostgreSQL supports two billing methods: pay-as-you-go and subscription. - Pay-as-you-go: If you plan to use your PostgreSQL instance for a short period of time, choose pay-as-you-go (hourly rate). You can save money by releasing the instance when you no longer need it.
- Subscription: If you plan to use your PostgreSQL instance for a long period of time, select Subscription (one-time payment) and choose the duration of the purchase in the lower left corner of the page. Subscription is more affordable than pay-as-you-go, and the longer you buy, the more discounts you get.
tip You can also create a pay-as-you-go instance first and confirm that the instance meets the requirements before switching to a yearly/monthly subscription. If you choose pay-as-you-go billing, make sure your Volcano Engine account balance is at least 100 CNY. For more information on billing, see Billing overview. |
RDS for PostgreSQL 
Copy page
Download PDF