On this page

Show all

Help Center/ Data Replication Service/ Data Verification/ Creating a Verification Task

Creating a Verification Task

Updated on 2025-03-04 GMT+08:00

View PDF

A verification task is used to check consistency between selected objects and data in the source and destination databases.

Supported Database Types

The following table lists the source database and destination database types supported by DRS in data verification.

**Table 1** Supported databases
Source DB Type	Destination DB Type
On-premises MySQL ECS-hosted MySQL Other cloud MySQL RDS for MySQL	RDS for MySQL
	TaurusDB
	RDS for PostgreSQL
	GaussDB Distributed
	GaussDB Centralized
	RDS for MariaDB
RDS for MySQL	On-premises MySQL ECS-hosted MySQL Other cloud MySQL
	CSS/ES
	On-premises Oracle ECS-hosted Oracle
	On-premises MariaDB ECS-hosted MariaDB Other cloud MariaDB
On-premises MySQL ECS-hosted MySQL	CSS/ES
On-premises PostgreSQL ECS-hosted PostgreSQL Other cloud PostgreSQL RDS for PostgreSQL	RDS for PostgreSQL
	GaussDB Centralized
	GaussDB Distributed
RDS for PostgreSQL	On-premises PostgreSQL ECS-hosted PostgreSQL
DDM	RDS for MySQL
	On-premises MySQL ECS-hosted MySQL Other cloud MySQL
	DDM
	On-premises Oracle ECS-hosted Oracle
On-premises Oracle ECS-hosted Oracle	RDS for MySQL
	TaurusDB
	RDS for PostgreSQL
	GaussDB Centralized
	GaussDB Distributed
	DDM
GaussDB Distributed	On-premises MySQL ECS-hosted MySQL Other cloud MySQL RDS for MySQL
	On-premises Oracle ECS-hosted Oracle
	GaussDB Distributed
	GaussDB Centralized
GaussDB Centralized	On-premises MySQL ECS-hosted MySQL Other cloud MySQL RDS for MySQL
	On-premises Oracle ECS-hosted Oracle
	GaussDB Distributed
	GaussDB Centralized
TaurusDB	TaurusDB
	On-premises MySQL ECS-hosted MySQL Other cloud MySQL RDS for MySQL
	CSS/ES
	On-premises Oracle ECS-hosted Oracle
DDS	Self-built MongoDB Other cloud MongoDB
DB2 for LUW	GaussDB Distributed
DB2 for LUW	GaussDB Centralized
TiDB	TaurusDB
-	GaussDB Centralized
	GaussDB Distributed
	Microsoft SQL Server
On-premises MongoDB ECS-hosted MongoDB Other cloud MongoDB DDS	DDS
On-premises MariaDB ECS-hosted MariaDB Other cloud MariaDB	RDS for MariaDB
On-premises MariaDB ECS-hosted MariaDB Other cloud MariaDB	RDS for MySQL
	TaurusDB
RDS for MariaDB	On-premises MariaDB ECS-hosted MariaDB Other cloud MariaDB
Cassandra	GeminiDB Cassandra
DynamoDB on other clouds (web services)	GeminiDB Dynamo NOTE: Only whitelisted users can use this function.
Redis	GenimiDB Redis
GenimiDB Redis	Redis

Database Permissions

**Table 2** Database permissions
Database	Required Permission
MySQL/RDS for MySQL	SELECT
TaurusDB	SELECT
DDM	SELECT
TiDB	SELECT
MariaDB	SELECT
PostgresSQL/RDS for PostgreSQL	CONNECT permission on databases, USAGE permission on schemas, SELECT permission on tables, and SELECT permission on sequences
Oracle	CREATE SESSION and SELECT ANY DICTIONARY permissions; SELECT permission on a single table
GaussDB Centralized	Log in to a Postgres database as the root user or other database users with the sysadmin role. Grant the following permissions to these users: Database-level permission: CONNECT permission on databases SCHEMA-level permission: USAGE permission on schemas Table-level permission: SELECT permission on all tables in schemas
GaussDB Distributed	Log in to a Postgres database as the root user or other database users with the sysadmin role. Grant the following permissions to these users: Database-level permission: CONNECT permission on databases SCHEMA-level permission: USAGE permission on schemas Table-level permission: SELECT permission on all tables in schemas
MongoDB/DDS/AWS DocumentDB	Replica set: The source database user must have the readAnyDatabase permission on the admin database and the read permission on the local database. Single node: The source database user must have the readAnyDatabase permission on the admin database and the read permission on the local database.
Microsoft SQL Server	Sysadmin permission; db_datareader or db_owner permission on a database to be synchronized
DB2 for LUW	The user must have the CONNECT and DATAACCESS permissions. If there is the DB2SECURITYLABEL data in the table structure of the source database, ensure that the user has the read permission on all data in the table.
CSS/ES	The user must have the READ permission.
Cassandra	The user must have the following minimum permissions: SELECT permission on system catalogs system_auth.roles and system_auth.role_permissions and SELECT permission on the tables to be synchronized.

Procedure

This section describes how to create a verification task from a MySQL database to an RDS for MySQL database. To configure tasks of other DB engines, you can refer to the following procedures.

On the Data Verification Management page, click Create Verification Task.

On the Create Verification Instance page, select a region and project, specify the task name, description, and the verification instance details, and click Create Now.

Task information

Figure 1 Verification task information

**Table 3** 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 can contain up to 256 characters and cannot contain special characters !=<>&'\"

Verification instance information

Figure 2 Verification Instance Information

**Table 4** Verification instance information
Parameter	Description
Data Flow	Select To the cloud. The destination database is a database in the current cloud.
Source DB Engine	Select MySQL.
Destination DB Engine	Select MySQL.
Network Type	Public network is used as an example. Available options: Public network, VPC, VPN or Direct Connect VPC is suitable for data verification between cloud databases of the same account in the same region and VPC. Public network is suitable for data verification between on-premises or external cloud databases and the destination database bound with an EIP. VPN or Direct Connect is suitable for data verification between on-premises databases and cloud databases, between cloud databases of different accounts in the same region, or between cloud databases across regions using a VPN, Direct Connect, Cloud Connect, VPCEP, or a VPC peering connection.
Destination DB Instance	The RDS DB instance you created. NOTE: The destination DB instance cannot be a read replica. The source and destination DB instances can be the same DB instance.
Verification Instance Subnet	Select the subnet where the verification 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 verification instance is successfully created, only subnets with DHCP enabled are displayed.
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.

Figure 3 AZ

**Table 5** Task type information
Parameter	Description
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 6** 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 create 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.

NOTE:

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

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

In different data flow scenarios, the source and destination database settings are different. Specify the required parameters based on the GUI.

Source database information

Figure 5 Source database information

**Table 7** Source database settings
Parameter	Description
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 Username	The username for accessing the source database.
Database Password	The password for the database username. You can change the password if necessary. To change the password, perform the following operation after the task is created: If the task is in the Starting, Full synchronization, Incremental synchronization, or Incremental synchronization failed status, in the Connection Information area on the Basic Information tab, click Modify Connection Details. In the displayed dialog box, change the password.
SSL Connection	If SSL connection is required, enable SSL on the source database, ensure that related parameters have been correctly configured, and upload an SSL certificate. NOTE: The maximum size of a single certificate file that can be uploaded is 500 KB. If SSL is disabled, your data may be at risk.

NOTE:

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

Destination database information

Figure 6 Destination database information

**Table 8** Destination database settings
Parameter	Description
DB Instance Name	The RDS DB instance you selected when creating the verification task. This parameter cannot be changed.
Database Username	The username for accessing the destination database.
Database Password	The password for the database username. You can change the password if necessary. To change the password, perform the following operation after the task is created: If the task is in the Starting, Full synchronization, Incremental synchronization, or Incremental synchronization failed status, in the Connection Information area on the Basic Information tab, click Modify Connection Details. In the displayed dialog box, change the password.
SSL Connection	If SSL connection is required, enable SSL on the destination database, ensure that related parameters have been correctly configured, and upload an SSL certificate. NOTE: The maximum size of a single certificate file that can be uploaded is 500 KB. If SSL is disabled, your data may be at risk.

NOTE:

The username and password of the destination database are encrypted and stored in the database and the DRS instance during data verification. After the task is deleted, the username and password are permanently deleted.

On the Select Objects page, select objects and click Next.

Figure 7 Selecting objects

**Table 9** Objects
Parameter	Description
Select Objects	The left pane displays the source database objects, and the right pane displays the selected objects. You can verify tables or import object files based on your service requirements. If the verification objects in source and destination databases have different names, you can map the source object name to the destination one in the right pane. For details, see Changing Object Names (Mapping Object Names). If the database table name contains characters other than letters, digits, and underscores (_), or the mapped database table name contains hyphens (-) and number signs (#), the name length cannot exceed 42 characters. Import an object file. For details, seeImporting 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 verified. 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 object cannot contain spaces.

On the Verification Rules page, configure verification rules.
- If you do not need to configure a verification rule, click Next.
- If data processing is required, select Data Filtering, Additional Columns, or Processing Columns. For details about how to configure related rules, see Processing Data.
Figure 8 Verification rule
On the Check Task page, check the verification 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.
  NOTE:
  
  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.

On the Confirm Task page, specify Send Notifications, SMN Topic, 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 9 Task startup settings

**Table 10** Task startup settings
Parameter	Description
Send Notifications	This parameter is optional. After enabled, select a SMN topic. If the status of the verification 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.
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.

After the task is submitted, you can view and manage it on the Data Verification 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.