Data Management:Logically back up and restore an ApsaraDB RDS for PostgreSQL database

Usage notes

• Each backup schedule of Data Disaster Recovery can be used to logically back up only a single PostgreSQL database, which can be an ApsaraDB RDS for PostgreSQL database, a PolarDB for PostgreSQL database, or another type of PostgreSQL database. To back up multiple PostgreSQL databases, you must purchase a backup schedule from Data Disaster Recovery for each database.

• Data Disaster Recovery does not support incremental backup for PostgreSQL databases.

Create a backup schedule

For more information, see Create a backup schedule.

Configure a backup schedule

1. Log on to the DMS console V5.0.

2. In the top navigation bar, choose Security and Specifications (DBS) > Data Disaster Recovery (DBS) > Backup Plan.

   Note

   If you use the DMS console in simple mode, move the pointer over the icon in the upper-left corner of the DMS console and choose All Features > Security and Specifications (DBS) > Data Disaster Recovery (DBS) > Backup Plan.

3. On the Backup Schedules page, find the backup schedule that you want to configure and click Configure Backup Schedule in the Actions column.

   

4. In the Configure Backup Source and Destination step, configure the backup source and destination, and then click Next in the lower-right corner of the page.

   

   Section	Parameter	Description
   N/A	Schedule Name	The name of the backup schedule. Data Disaster Recovery automatically generates a backup schedule name. We recommend that you enter a descriptive name that is easy to identify. Backup schedule names do not need to be unique.
   Backup Source Information	Backup Mode	The method that is used to back up data. By default, the backup method that you selected when you purchased the backup schedule is used. In this example, Logical Backup is used.
   	Database Location	RDS Instance
   	Instance Region	The region in which the source database instance resides. Note This parameter is displayed only if you set the Database Location parameter to RDS Instance, PolarDB, ECS-Hosted Database, or No public network IP: Port's self-built database (accessed through the database gateway).
   	RDS Instance ID	The ID of the ApsaraDB RDS for PostgreSQL instance that you want to back up.
   	Database Name	The name of the database that you want to back up. Important Each backup schedule of Data Disaster Recovery can be used to back up only one PostgreSQL database by using logical backup. To back up multiple PostgreSQL databases, you must purchase a backup schedule from Data Disaster Recovery for each database.
   	Database Account	The username of the account that is used to connect to the database that you want to back up. The account must have permissions to back up the database. For more information, see Account permissions. Note For ApsaraDB RDS databases, read-only permissions are required for backup, and read and write permissions are required for backup and restoration.
   	Password	The password of the account that is used to connect to the database that you want to back up. After you enter the username and password of the database account, click Test Connection next to the password to check whether the information about the database that you want to back up is valid. If the specified parameters are valid, the Test Passed message is displayed. If the Test Failed message is displayed, click Check next to Test Failed. Modify the information about the database that you want to back up based on the check results.
   	SSL Encryption	The connection method used to transmit the backup data. This parameter is required to back up a database in the ApsaraDB RDS for PostgreSQL instance. Valid values: Non-encrypted. SSL-encrypted: SSL encrypts network connections at the transport layer to improve the security and integrity of data in transit. However, SSL increases the network connection response time. Note To select SSL-encrypted, you must enable SSL encryption for the ApsaraDB RDS for PostgreSQL instance before you configure the backup schedule. For more information, see SSL encryption.
   	Compliance warranty regarding cross-border data transfers	Read and agree to the statement of compliance.
   Backup Destination Information	Backup Storage Type	The type of storage used to store the backup data. Valid values: DBS Storage (recommended): Backup data is stored in Data Disaster Recovery without the need to create an Object Storage Service (OSS) bucket. You are charged based on the volume of your data that is stored in Data Disaster Recovery. For more information about the billing method, see Pricing. OSS For User: You must create a bucket in the OSS console in advance. For more information, see Create buckets. Note In this example, DBS Storage (recommended) is selected. If you select OSS For User, you must configure the OSS Bucket Name parameter. Only the Standard storage class is supported. If the volume of data to be backed up is large, we recommend that you purchase subscription storage plans to offset fees. Storage plans are more cost-efficient than pay-as-you-go billing.
   	Storage Encryption	The method used to encrypt the stored data. Valid values: Encrypted (recommended): AES-256 is used to encrypt the stored data. The server-side encryption feature is used in OSS. When you upload an object to a bucket for which server-side encryption is enabled, OSS encrypts and stores the object. When you download the encrypted object from OSS, OSS decrypts the object and returns the decrypted object to you. For more information, see Server-side encryption. Non-encrypted: The stored data is not encrypted.

5. In the Edit Backup Objects step, select the database or table that you want to back up in the Available section. Click the right arrow to add the selected database or table to the Selected section. Then, click Next.

   Note

   • If you selected Logical Backup when you purchased a backup schedule, Data Disaster Recovery allows you to use the backup schedule to back up the entire database or a single table in the database during full backups. You can click Select All in the lower-left corner of the page to back up the entire database. For more information about the granularity of logical backup, see Supported database types and features.

   • If you selected Physical Backup when you purchased a backup schedule, you can only use the backup schedule to back up the entire database instance.

6. In the Configure Backup Time step, configure the parameters and click Next in the lower-right corner of the page. The following table describes the parameters.

   Parameter	Description
   Full-scale Backup Frequency	The frequency of the backup schedule. Valid values: Periodic Backup and Single Backup. Note If you select Periodic Backup, you must configure the Full Data Backup Recurrence and Start At parameters.
   Full Data Backup Recurrence	The days of the week on which Data Disaster Recovery runs the backup schedule. You can select one or more days of a week. Select at least one day of the week.
   Start At	The start time of the backup. We recommend that you set a point in time within off-peak hours. Example: 01:00. Note If a previous full data backup is not finished at the start time of the next backup, Data Disaster Recovery skips the next backup.
   Incremental Backup	Data Disaster Recovery does not support incremental backup for PostgreSQL databases.
   Maximum Concurrent Threads for Full Data Backup	The maximum number of concurrent threads available for a full backup. You can set this parameter to adjust the backup speed. For example, you can reduce the number of backup threads to minimize impacts on the database.

7. In the Edit Lifecycle step, configure the lifecycle for a full data backup in the Configure Full Data Backup Lifecycle section.

8. After the configurations are complete, click Precheck in the lower-right corner of the page.

9. If the Precheck Passed message appears, click Start Task.

   Note

   • If the state of the backup schedule changes to Running, the backup schedule takes effect.

   • If an exception or error occurs when you start the backup schedule, troubleshoot the exception or error at the earliest opportunity. For more information, see How do I fix errors for an abnormal backup schedule? If your issue persists after you use the solution provided in the preceding topic, contact technical support in the DingTalk group for Data Disaster Recovery (ID: 35585947).

Restore data