Creating a Verification Task
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.
Database Permissions
Database |
Required Permission |
---|---|
MySQL/RDS for MySQL |
SELECT |
TaurusDB |
SELECT |
DDM |
SELECT |
TiDB |
SELECT |
MariaDB |
SELECT |
PostgreSQL/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:
|
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:
|
MongoDB/DDS 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, specify the task name, description, and the verification instance details, and click Create Now.
- Task information
Table 2 Task information Parameter
Description
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
Table 3 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.
IP Address Type
The IP address type of the verification instance. Only IPv4 and IPv4/IPv6 dual stack are supported.
- IP Address Type can be set to IPv4/IPv6 dual stack only when IPv4/IPv6 dual stack is enabled for the selected VPC and subnet.
- If you select IPv4/IPv6 dual stack and the source or destination database is connected by selecting an instance, DRS preferentially uses an IPv4 address to access the 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.
- AZ
Table 4 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.
- Tags
Table 5 Tags Parameter
Description
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 .
If a task fails to be created, DRS retains the task for three days by default. After three days, the task automatically stops.
- Task information
- 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.
- Source database information
Table 6 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.
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
Table 7 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.
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.
- Source database information
- On the Select Objects page, select objects and click Next.
Table 8 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 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 .
- 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.
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.
- 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 .
- 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 .
- 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.
- 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.
- On the Confirm Task page, confirm that the configured information is correct and click Submit to submit the task.
Table 9 Task startup settings Parameter
Description
- 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.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot