From PostgreSQL to PostgreSQL

Supported Source and Destination Databases

Database Account Permission Requirements

To start a synchronization task, the source and destination database users must meet the requirements in the following table. Different types of synchronization tasks require different permissions. For details, see Table 2. DRS automatically checks the database account permissions in the pre-check phase and provides handling suggestions.

• You are advised to create an independent database account for DRS task connection to prevent task failures caused by database account password modification.
• After changing the account passwords for the source and destination databases, modify the connection information of the DRS task by referring to Modifying Connection Information to prevent automatic retry after a task failure. Automatic retry will lock the database accounts.

Supported Synchronization Objects

Table 3 lists the objects that can be synchronized in different scenarios. DRS will automatically check the objects you selected before the synchronization.

Precautions

To ensure tasks can run normally, DRS provides automatic pre-check. Before starting a DRS task, DRS checks the configurations and conditions of the source and destination databases. For details about the main check items and handling suggestions, see Pre-check Items. In addition to the pre-check items, you need to pay attention to the items listed in Table 4.

Procedure

This section uses to-the-cloud synchronization from PostgreSQL to PostgreSQL as an example to describe how to configure a real-time synchronization task in the VPC network scenario.

1. On the Data Synchronization Management page, click Create Synchronization Task.
2. On the Create Synchronization Instance page, select a region and project, specify the task name, description, and the synchronization instance details, and click Create Now.
   • Task information description
     Figure 1 Synchronization task information
     

     Table 5 Task information

     Parameter	Description
     Region	The region where the replication instance is deployed. You can change the region.
     Project	The project corresponds to the current region and can be changed.
     Task Name	The task name must start with a letter and consist of 4 to 50 characters. It can contain only letters, digits, hyphens (-), and underscores (_).
     Description	The description consists of a maximum of 256 characters and cannot contain special characters !=<>'&"\

   • Synchronization instance information
     Figure 2 Synchronization instance information
     

     Table 6 Synchronization instance settings

     Parameter	Description
     Data Flow	Select To the cloud.
     Source DB Engine	Select PostgreSQL.
     Destination DB Engine	Select PostgreSQL.
     Network Type	Available options: VPC, Public network and VPN or Direct Connect. VPC is used as an example. VPC is suitable for data synchronization between cloud databases of the same account in the same region and VPC. Public network is suitable for data synchronization from on-premises or external cloud databases to the destination databases bound with an EIP. VPN or Direct Connect is suitable for data synchronization from on-premises databases to cloud databases, between databases of different accounts in the same region on the cloud, or between databases across regions on the cloud using a VPN, Direct Connect, Cloud Connect, VPCEP, or a VPC peering connection.
     Destination DB Instance	The RDS for PostgreSQL DB instance.
     Synchronization Instance Subnet	Select the subnet where the synchronization instance is located. You can also click View Subnets to go to the network console to view the subnet where the instance resides. By default, the DRS instance and the destination DB instance are in the same subnet. You need to select the subnet where the DRS instance resides, and there are available IP addresses for the subnet. To ensure that the synchronization instance is successfully created, only subnets with DHCP enabled are displayed.
     Synchronization Mode	The synchronization mode supported by a DRS task. Full+Incremental is used as an example. For details about the underlying working principles for full or incremental synchronization, see Product Architecture and Function Principles. Full+Incremental This synchronization mode allows you to synchronize data in real time. After a full synchronization initializes the destination database, an incremental synchronization parses logs to ensure data consistency between the source and destination databases. Full All objects and data in non-system databases are synchronized to the destination database at a time. This mode is applicable to scenarios where service interruption is acceptable. Incremental Through log parsing, incremental data generated on the source database is synchronized to the destination database.
     Specify EIP	This parameter is available when you select Public network for Network Type. Select an EIP to be bound to the DRS instance. DRS will automatically bind the specified EIP to the DRS instance and unbind the EIP after the task is complete. For details about the data transfer fee generated using a public network, see EIP Price Calculator.

   • Task type
     Figure 3 Task type
     

     Table 7 Task type information

     Parameter	Description
     Specifications	DRS instance specifications. Different specifications have different performance upper limits. For details, see Real-Time Synchronization. NOTE: DRS allows you to upgrade specifications only for single-AZ synchronization tasks. Task specifications cannot be downgraded. For details, see Changing Specifications.
     AZ	Select the AZ where you want to create the DRS task. Selecting the one housing the source or destination database can provide better performance.

   • Enterprise Project and Tags
     Figure 4 Enterprise Project and Tags
     

     Table 8 Enterprise Project and Tags

     Parameter	Description
     Enterprise Project	An enterprise project you would like to use to centrally manage your cloud resources and members. Select an enterprise project from the drop-down list. The default project is default. For more information about enterprise project, see Enterprise Management User Guide. To customize an enterprise project, click Enterprise in the upper right corner of the console. The Enterprise Project Management Service page is displayed. For details, see Creating an Enterprise Project in Enterprise Management User Guide.
     Tags	Tags a task. This configuration is optional. Adding tags helps you better identify and manage your tasks. Each task can have up to 20 tags. If your organization has configured tag policies for DRS, add tags to tasks based on the policies. If a tag does not comply with the policies, task creation may fail. Contact your organization administrator to learn more about tag policies. After a task is created, you can view its tag details on the Tags tab. For details, see Tag Management.

   

   If a task fails to be created, DRS retains the task for three days by default. After three days, the task automatically stops.

3. On the Configure Source and Destination Databases page, wait until the synchronization instance is created. Then, specify source and destination database information and click Test Connection for both the source and destination databases to check whether they have been connected to the synchronization instance. After the connection tests are successful, select the check box before the agreement and click Next.

   Establish the connectivity between the DRS instance and the source and destination databases.

   • Network connectivity: Ensure that the source and destination databases accept connections from the IP address of the DRS instance. To access databases over a public network, configure the database to accept connections from the EIP of the DRS instance. To access databases over a VPC, VPN, or Direct Connect network, configure the database to accept connections from the private IP address of the DRS instance.For details, see Network Preparations.
   • Account connectivity: Ensure that the source and destination databases allows connections from the DRS instance using the username and password.
   

   The source database can be an ECS database or an RDS instance. Configure parameters based on the database type.

   • Scenario 1: Databases on an ECS - source database configuration
     Figure 5 Self-build on ECS - source database information
     

     Table 9 Self-build on ECS - source database information

     Parameter	Description
     Database Type	Select Self-built on ECS.
     VPC	A dedicated virtual network in which the source database is located. It isolates networks for different services. You can select an existing VPC or create a VPC.
     Subnet	A subnet provides dedicated network resources that are isolated from other networks, improving network security. The subnet must be in the AZ where the source database resides. You need to enable DHCP for creating the source database subnet.
     IP Address or Domain Name	The IP address or domain name of the source database.
     Port	The port of the source database. Range: 1 – 65535
     Database Name	Indicates whether to specify a database. If this option is enabled, enter the database name.
     Database Username	The username for accessing the source database.
     Database Password	The password for the database username.
     SSL Connection	SSL encrypts the connections between the source and destination databases.

     

     The IP address, domain name, username, and password of the source database are encrypted and stored in DRS, and will be cleared after the task is deleted.

   • Scenario 2: RDS DB instance - source database configuration
     Figure 6 RDS DB instance - source database information
     

     Table 10 RDS DB instance - source database information

     Parameter	Description
     Database Type	Select an RDS DB instance.
     DB Instance Name	Select the RDS PostgreSQL instance to be synchronized as the source DB instance.
     Database Username	The username for accessing the source database.
     Database Password	The password for the database username.

   Figure 7 Destination database information
   

   Table 11 Destination database settings

   Parameter	Description
   DB Instance Name	The RDS PostgreSQL instance you selected when creating the migration task and cannot be changed.
   Database Username	The username for accessing the destination database.
   Database Password	The password for the database username.

   

   The username and password of the source and destination databases are encrypted and stored in the databases and the synchronization instance during the synchronization. After the task is deleted, the username and password are permanently deleted.

4. On the Set Synchronization Task page, select the synchronization objects and accounts and click Next.
   Figure 8 Synchronization Object
   

   Table 12 Synchronization Object

   Parameter	Description
   Flow Control	You can choose whether to control the flow. Flow Control takes effect in the full phase only. Yes You can customize the maximum synchronization speed. During the full synchronization, the synchronization speed of each task (or each subtask in multi-task mode) does not exceed the value of this parameter. In addition, you can set the time range based on your service requirements. The traffic rate setting usually includes setting of a rate limiting time period and a traffic rate value. Flow can be controlled all day or during specific time ranges. The default value is Always. A maximum of 10 time ranges can be set, and they cannot overlap. The flow rate must be set based on the service scenario and cannot exceed 9,999 MB/s. Figure 9 Flow control No The synchronization speed is not limited and the outbound bandwidth of the source database is maximally used, which will increase the read burden on the source database. For example, if the outbound bandwidth of the source database is 100 MB/s and 80% bandwidth is used, the I/O consumption on the source database is 80 MB/s. NOTE: The flow control mode takes effect only in the full synchronization phase. You can also change the flow control mode after creating a task. For details, see Modifying the Flow Control Mode.
   Incremental Conflict Policy	The conflict policy refers to the conflict handling policy during incremental synchronization. By default, conflicts in the full synchronization phase are ignored. Select any of the following conflict policies: Ignore The system will skip the conflicting data and continue the subsequent synchronization process. If you select Ignore, data in the source database may be inconsistent with that in the destination database. Report error The synchronization task will be stopped and fail. Overwrite Conflicting data will be overwritten. If the synchronized data conflicts with the existing data in the destination database, selecting Ignore cannot ensure data consistency. To ensure data consistency, select Overwrite.
   Synchronize	Available options: Normal index, Incremental DDLs, and Populate materialized views during the full synchronization phase Populate materialized views during the full synchronization phase: This option takes effect only for materialized views that was populated in the source database. This operation affects the full synchronization performance. You perform this operation after the full synchronization is complete.
   Synchronize DML	Select the DML operations to be synchronized. By default, all DML operations are selected. If you do not select Delete, DELETE statements in the incremental data of the source database will not be synchronized, which may cause a data inconsistency. As a result, there may be a data conflict or the task may fail.
   Source Database Replication Slot Name	You can choose whether to specify the replication slot of the source database. This parameter is available for incremental tasks. After replication slot is enabled, enter the replication slot name. The name can contain a maximum of 63 characters and cannot start with a digit. Only lowercase letters, digits, and underscores (_) are allowed.
   Take Snapshot	If you perform a full+incremental migration, you can take a snapshot for your databases. Exporting data in snapshot mode in the full export phase can effectively improve the data synchronization efficiency in the full+incremental export scenario. However, the snapshot mechanism of PostgreSQL prevents historical data in the database from being reclaimed during the export, which may cause space expansion. You are advised to use this method when the full or incremental data volume is large and the source database disk space is sufficient.
   Concurrent Full Export Threads	Number of threads for exporting objects and data during full synchronization.
   Concurrent Full Import Threads	Number of threads for importing objects and data during full synchronization.
   Synchronization Object	The left pane displays the source database objects, and the right pane displays the selected objects. You can select Tables, Import object file, or Databases for Synchronization Object as required. Database-level synchronization: In full synchronization, the selected databases and the inventory data of the database objects are synchronized. In incremental synchronization, the DML and some DDL statements of all tables except unlogged tables and temporary tables are synchronized. Table-level synchronization: In full synchronization, the inventory data of the selected tables, sequences, views, or materialized views is synchronized. In incremental synchronization, the DML and some DDL statements of the selected tables are synchronized. If the synchronization objects in source and destination databases have different names, you can map the source object name to the destination one. For details, see Changing Object Names (Mapping Object Names). When a schema name or table name is mapped, to prevent conflicts between indexes and constraint names, the original index name in the table is changed to the following format after synchronization: i_+hash value+original index name (which may be truncated)+_key The hash value is calculated based on the original schema name_original table name_original index name. Similarly, after the synchronization, the original constraint name on the table is changed to c_ + hash value + original constraint name (which may be truncated) + _key. For details about how to import an object file, see Importing Synchronization Objects. NOTE: To quickly select the desired database objects, you can use the search function. If there are changes made to the source databases or objects, click in the upper right corner to update the objects to be synchronized. If an object name contains spaces, the spaces before and after the object name are not displayed. If there are two or more consecutive spaces in the middle of the object name, only one space is displayed. The name of the selected synchronization object cannot contain spaces.
   Synchronize Account	During the synchronization, you can synchronize accounts based on your service requirements. For details, see Table 13.

   Figure 10 Synchronize Account
   

   Table 13 Accounts and permissions to be synchronized

   Parameter	Description
   Account	Account name of the source database.
   Whether to Support Synchronization	Whether the account can be synchronized. There are accounts that can be synchronized and accounts that cannot be synchronized. For an account that cannot be synchronized, the specific reason is displayed in View in the Remarks column.
   Parent Account	Parent account.
   Parent Account That Cannot Be Synchronized	The parent account that cannot be synchronized.
   Account Attribute	Attributes of the source database account.
   Account Attribute That Cannot Be Synchronized	The account attributes that cannot be synchronized due to insufficient permissions of the destination database user.
   Remarks	Description of the parent account and account attributes that cannot be synchronized. You can go to the next step only after confirming all remarks.
   Synchronize object permissions	Whether to synchronize permissions corresponding to the account.

5. On the Check Task page, check the synchronization task.
   • If any check fails, review the cause and rectify the fault. After the fault is rectified, click Check Again.

     For details about how to handle check failures, see Solutions to Failed Check Items in Data Replication Service User Guide.

   • If all check items are successful, click Next.
     

     You can proceed to the next step only when all checks are successful. If there are any items that require confirmation, view and confirm the details first before proceeding to the next step.

6. On the displayed page, specify Start Time, Send Notifications, SMN Topic, Delay Threshold (s), and Stop Abnormal Tasks After, confirm that the configured information is correct, select the check box before the agreement, and click Submit to submit the task.
   Figure 11 Task startup settings
   

   Table 14 Task startup settings

   Parameter	Description
   Start Time	Set Start Time to Start upon task creation or Start at a specified time based on site requirements. NOTE: After a synchronization task is started, the performance of the source and destination databases may be affected. You are advised to start a synchronization task during off-peak hours.
   Send Notifications	This parameter is optional. After enabled, select a SMN topic. If the status, latency metric, or data of the migration task is abnormal, DRS will send you a notification.
   SMN Topic	This parameter is available only after you enable Send Notifications and create a topic on the SMN console and add a subscriber. For details, see Simple Message Notification User Guide.
   Delay Threshold (s)	During an incremental synchronization, a synchronization delay indicates a time difference (in seconds) of synchronization between the source and destination database. If the synchronization delay exceeds the threshold you specify, DRS will send alarms to the specified recipients. The value ranges from 0 to 3,600. To avoid repeated alarms caused by the fluctuation of delay, an alarm is sent only after the delay has exceeded the threshold for six minutes. NOTE: If the delay threshold is set to 0, no notifications will be sent to the recipient. In the early stages of an incremental synchronization, the synchronization delay is long because a large quantity of data is awaiting synchronization. In this case, no notifications will be sent. Before setting the delay threshold, enable Send Notifications.
   Data Exception Notification	This parameter is optional. After enabled, DRS will send a notification if the task data is abnormal.
   Stop Abnormal Tasks After	Number of days after which an abnormal task is automatically stopped. The value must range from 14 to 100. The default value is 14. NOTE: You can set this parameter only for pay-per-use tasks. Tasks in the abnormal state are still charged. If tasks remain in the abnormal state for a long time, they cannot be resumed. Abnormal tasks run longer than the period you set (unit: day) will automatically stop to avoid unnecessary fees.

7. After the task is submitted, you can view and manage it on the Data Synchronization Management page.
   • You can view the task status. For more information about task status, see Task Statuses.
   • You can click in the upper right corner to view the latest task status.
   • By default, DRS retains a task in the Configuration state for three days. After three days, DRS automatically deletes background resources, but the task status remains unchanged. When you configure the task again, DRS applies for resources for the task again. In this case, the IP address of the DRS instance changes.
   • For a public network task, DRS needs to delete background resources after you stop the task. The EIP bound to the task cannot be restored to the Unbound state until background resources are deleted.