yexinru/doc-exports
1
0
Fork 0
forked from docs/doc-exports
Code Pull Requests Activity

drs_umn

Browse Source 
Reviewed-by: Wagner, Fabian <fabian.wagner@t-systems.com>
Co-authored-by: wangdengke2 <wangdengke2@huawei.com>
Co-committed-by: wangdengke2 <wangdengke2@huawei.com>
This commit is contained in:
Wang , Deng Ke
2025-11-27 11:39:26 +00:00
committed by zuul
parent 07a013e6d2
commit fa1c18873d
9 changed files with 815 additions and 748 deletions
Download Patch File Download Diff File Expand all files Collapse all files

523
docs/drs/umn/ALL_META.TXT.json
View File

File diff suppressed because it is too large Load Diff

989
docs/drs/umn/CLASS.TXT.json
View File

File diff suppressed because it is too large Load Diff

2
docs/drs/umn/drs_03_0008.html
View File

@ -24,6 +24,8 @@
</li>
<li class="ulchildlink"><strong><a href="drs_03_0109.html">Pausing a Migration Task</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="drs_03_1136.html">Cloning a Migration Task</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="drs_03_0004.html">Stopping a Migration Task</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="drs_03_0005.html">Deleting a Migration Task</a></strong><br>

22
docs/drs/umn/drs_03_1136.html Normal file
View File

@ -0,0 +1,22 @@
<a name="drs_03_1136"></a><a name="drs_03_1136"></a>
<h1 class="topictitle1">Cloning a Migration Task</h1>
<div id="body0000001265848833"><p id="drs_03_1136__p1111851913611">DRS allows you to quickly clone the configuration of an existing migration task. However, tasks in the following status cannot be cloned:</p>
<ul id="drs_03_1136__ul15198123744419"><li id="drs_03_1136__li17199937104416">Creating</li><li id="drs_03_1136__li115834114410">Creation failed</li><li id="drs_03_1136__li5581441448">Configuration</li><li id="drs_03_1136__li85994124418">Pending start</li><li id="drs_03_1136__li55964194414">Starting</li><li id="drs_03_1136__li45918494418">Deleted</li></ul>
<p id="drs_03_1136__p58391735152420">You can clone the following migration tasks:</p>
<ul id="drs_03_1136__ul672911951510"><li id="drs_03_1136__li572916910150">To the cloud<ul id="drs_03_1136__ul2390200151"><li id="drs_03_1136__li697195811474">MongoDB -&gt; DDS</li></ul>
</li><li id="drs_03_1136__li1415725521515">Out of the cloud<ul id="drs_03_1136__ul176001932204218"><li id="drs_03_1136__li1757522654210">DDS -&gt; MongoDB</li></ul>
</li></ul>
<div class="note" id="drs_03_1136__note3148134811446"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="drs_03_1136__ul114449567214"><li id="drs_03_1136__li844415613219">When a task is cloned, the source and destination database passwords are not cloned. You need to enter the passwords again for the new task.</li><li id="drs_03_1136__li139828554326">After a clone task is created, the EIP and private IP address of the new task are different from those of the original task. You may need to configure the network to ensure that the new task can communicate with the source and destination databases.</li></ul>
</div></div>
<div class="section" id="drs_03_1136__section16256919193311"><h4 class="sectiontitle">Prerequisites</h4><ul id="drs_03_1136__ul268371811469"><li id="drs_03_1136__li10683111894614">You have logged in to the DRS console.</li><li id="drs_03_1136__li1876513216463">A migration task has been created.</li></ul>
</div>
<div class="section" id="drs_03_1136__section5903121119423"><h4 class="sectiontitle">Procedure</h4><ol id="drs_03_1136__ol689710531239"><li id="drs_03_1136__li40673153184036"><span>On the <strong id="drs_03_1136__b129671233245">Online Migration Management</strong> page, select the task to be cloned and click <strong id="drs_03_1136__b896910331844">Clone</strong> in the <strong id="drs_03_1136__b7971333349">Operation</strong> column.</span></li><li id="drs_03_1136__li138719589414"><span>In the displayed dialog box, confirm the new task name and click <strong id="drs_03_1136__b78211617517">OK</strong>.</span></li><li id="drs_03_1136__li0217115918496"><span>After the task is submitted and the task clone is complete, the task status changes to <strong id="drs_03_1136__b1714792110520">Configuration</strong>. You can click <strong id="drs_03_1136__b1815417211519">Edit</strong> in the <strong id="drs_03_1136__b21595211515">Operation</strong> column, enter the source and destination database passwords again, and edit and start the task.</span></li></ol>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="drs_03_0008.html">Task Life Cycle</a></div>
</div>
</div>

2
docs/drs/umn/drs_04_0508.html
View File

@ -398,7 +398,7 @@
</p></li><li id="drs_04_0508__li6318165233313"><span>On the <span class="uicontrol" id="drs_04_0508__en-us_topic_0141892586_uicontrol1368378894334"><b>Check Task</b></span> page, check the synchronization task.</span><p><ul id="drs_04_0508__en-us_topic_0141892586_ul4927900994415"><li id="drs_04_0508__li1463713714211">If any check fails, review the cause and rectify the fault. After the fault is rectified, click <strong id="drs_04_0508__en-us_topic_0000001089538759_b51770582543246">Check Again</strong>.</li><li id="drs_04_0508__en-us_topic_0141892586_li103321694719">If all check items are successful, click <span class="uicontrol" id="drs_04_0508__uicontrol198478198043246"><b>Next</b></span>.<div class="note" id="drs_04_0508__en-us_topic_0141892586_note9331116184719"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="drs_04_0508__en-us_topic_0141892586_p1934716174711">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.</p>
</div></div>
</li></ul>
</p></li><li id="drs_04_0508__li147691849373"><span>On the displayed page, specify <strong id="drs_04_0508__en-us_topic_0000001089538759_b189538328555">Start Time</strong>, confirm that the configured information is correct, and click <strong id="drs_04_0508__en-us_topic_0000001089538759_b495593217550">Submit</strong> to submit the task.</span><p><p id="drs_04_0508__en-us_topic_0000001089538759_p123191471513"></p>
</p></li><li id="drs_04_0508__li147691849373"><span>On the displayed page, specify <strong id="drs_04_0508__en-us_topic_0000001089538759_b2148164642217">Start Time</strong>, confirm that the configured information is correct, and click <strong id="drs_04_0508__en-us_topic_0000001089538759_b15148104642217">Submit</strong> to submit the task.</span><p><p id="drs_04_0508__en-us_topic_0000001089538759_p123191471513"></p>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="drs_04_0508__en-us_topic_0000001089538759_table179101030984" frame="border" border="1" rules="all"><caption><b>Table 12 </b>Task startup settings</caption><thead align="left"><tr id="drs_04_0508__en-us_topic_0000001089538759_row1391043015814"><th align="left" class="cellrowborder" valign="top" width="18.42%" id="mcps1.3.6.3.6.2.2.2.3.1.1"><p id="drs_04_0508__en-us_topic_0000001089538759_p1391015304812">Parameter</p>
</th>

2
docs/drs/umn/drs_10_0015.html
View File

@ -1,7 +1,7 @@
<a name="drs_10_0015"></a><a name="drs_10_0015"></a>
<h1 class="topictitle1">Changing Object Names (Mapping Object Names)</h1>
<div id="body1547707660667"><p id="drs_10_0015__p829785120459">Data synchronization allows you to synchronize objects (including databases, schemas and tables) in a sources database to the corresponding objects in a destination database. If the synchronization objects in source and destination databases have different names, you can map the source object name to the destination one by changing the object name. The objects that can be changed or mapped include databases, schemas, and tables.</p>
<div id="body1547707660667"><p id="drs_10_0015__p829785120459">Data synchronization allows you to synchronize objects (including databases, schemas and tables) in a source database to the corresponding objects in a destination database. If the synchronization objects in source and destination databases have different names, you can map the source object name to the destination one by changing the object name. The objects that can be changed or mapped include databases, schemas, and tables.</p>
<p id="drs_10_0015__p2017318341974">Object name mapping can be used only in the following scenarios:</p>
<ul id="drs_10_0015__ul1538619581675"><li id="drs_10_0015__li0243185718477">For the first time you select synchronization objects for a data synchronization task.</li><li id="drs_10_0015__li73861158479">For the first time you add or delete the synchronization object which is not in a mapping relationship.</li></ul>
<div class="note" id="drs_10_0015__note13867172517405"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="drs_10_0015__ul205844152106"><li id="drs_10_0015__li1758411571019">If the destination DB is a type of PostgreSQL, the destination schema name cannot start with <strong id="drs_10_0015__b9120737125612">pg_</strong>. Otherwise, the migration fails.</li></ul>

4
docs/drs/umn/drs_11_0009.html
View File

@ -20,7 +20,7 @@
<p id="drs_11_0009__en-us_topic_0000001160307886_p1356112538492">Handling suggestions: Grant the source database user the corresponding permissions.</p>
</td>
</tr>
<tr id="drs_11_0009__en-us_topic_0000001160307886_row14785522193637"><td class="cellrowborder" valign="top" headers="mcps1.3.1.2.2.3.3.1 "><p id="drs_11_0009__en-us_topic_0000001160307886_p3296941154916">Failure cause: In an incremental migration, the source database user must have the following permissions: SELECT, SHOW VIEW, EVENT, LOCK TABLES, REPLICATION SLAVE, REPLICATION CLIENT, In the DR scenario, the following permissions are required: CREATE, ALTER, DROP, DELETE, INSERT, UPDATE, and INDEX.</p>
<tr id="drs_11_0009__en-us_topic_0000001160307886_row14785522193637"><td class="cellrowborder" valign="top" headers="mcps1.3.1.2.2.3.3.1 "><p id="drs_11_0009__en-us_topic_0000001160307886_p3296941154916">Failure cause: In an incremental migration, the source database user must have the following permissions: SELECT, SHOW VIEW, EVENT, LOCK TABLES, REPLICATION SLAVE, and REPLICATION CLIENT. In the DR scenario, the following permissions are required: CREATE, ALTER, DROP, DELETE, INSERT, UPDATE, and INDEX.</p>
<p id="drs_11_0009__en-us_topic_0000001160307886_p6534733124915">Handling suggestions: Grant the source database user the corresponding permissions.</p>
</td>
</tr>
@ -47,7 +47,7 @@
<tr id="drs_11_0009__en-us_topic_0000001160307886_row424719914399"><th class="firstcol" valign="top" width="11%" id="mcps1.3.2.2.2.3.2.1"><p id="drs_11_0009__en-us_topic_0000001160307886_p5262199193919">Description</p>
</th>
<td class="cellrowborder" valign="top" width="89%" headers="mcps1.3.2.2.2.3.2.1 "><p id="drs_11_0009__p18309175715473">Different types of synchronization tasks require different permissions.</p>
<ul id="drs_11_0009__ul11716145910348"><li id="drs_11_0009__li10716115923412"><strong id="drs_11_0009__b192816610396">Full synchornization:</strong> The CONNECT permission for databases, the USAGE permission for schemas, the SELECT permission for tables, the SELECT permission for sequences, and the SELECT permission for system table <strong id="drs_11_0009__b184115515387">catalog pg_catalog.pg_authid</strong> (used for synchronizing user passwords)</li></ul>
<ul id="drs_11_0009__ul11716145910348"><li id="drs_11_0009__li10716115923412"><strong id="drs_11_0009__b192816610396">Full synchronization:</strong> The CONNECT permission for databases, the USAGE permission for schemas, the SELECT permission for tables, the SELECT permission for sequences, and the SELECT permission for system table <strong id="drs_11_0009__b184115515387">catalog pg_catalog.pg_authid</strong> (used for synchronizing user passwords)</li></ul>
<ul id="drs_11_0009__ul10671554359"><li id="drs_11_0009__li96785143518"><strong id="drs_11_0009__b797246133910">Full+incremental synchronization</strong>: The CONNECT permission for databases, the USAGE permission for schemas, the SELECT permission for tables, the SELECT permission for sequences, the SELECT permission for system table <strong id="drs_11_0009__b5733838193919">pg_catalog.pg_authid</strong> (used for synchronizing user passwords), the UPDATE, DELETE, and TRUNCATE permissions for tables that do not have primary keys, and the permission to create a replication connection.</li></ul>
<p id="drs_11_0009__en-us_topic_0000001160307886_p092101110618">If the permissions are insufficient, the migration will fail.</p>
</td>

3
docs/drs/umn/drs_11_0462.html
View File

@ -4,8 +4,7 @@
<div id="body0000001257094277"><p id="drs_11_0462__p8060118">DRS allows you to clone the configuration of existing synchronization tasks. However, tasks in the following status cannot be cloned:</p>
<ul id="drs_11_0462__ul204972884913"><li id="drs_11_0462__li1849712818490">Creating</li><li id="drs_11_0462__li115834114410">Creation failed</li><li id="drs_11_0462__li5581441448">Configuration</li><li id="drs_11_0462__li85994124418">Pending start</li><li id="drs_11_0462__li55964194414">Starting</li><li id="drs_11_0462__li45918494418">Deleted</li></ul>
<p id="drs_11_0462__p58391735152420">You can clone the following data flow types:</p>
<ul id="drs_11_0462__ul277841415255"><li id="drs_11_0462__li10956857134318">To the cloud<ul id="drs_11_0462__ul185706254414"><li id="drs_11_0462__li61761939442">MySQL-&gt;MySQL</li></ul>
</li><li id="drs_11_0462__li20946165185019">From the cloud<ul id="drs_11_0462__ul1347962275013"><li id="drs_11_0462__li76449341509">MySQL-&gt;MySQL</li></ul>
<ul id="drs_11_0462__ul277841415255"><li id="drs_11_0462__li20946165185019">Out of the cloud<ul id="drs_11_0462__ul1347962275013"><li id="drs_11_0462__li84355180232">DDS -&gt; MongoDB</li></ul>
</li></ul>
<div class="note" id="drs_11_0462__note3148134811446"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="drs_11_0462__ul114449567214"><li id="drs_11_0462__li844415613219">When a task is cloned, the source and destination database passwords are not cloned. You need to enter the passwords again for the new task.</li><li id="drs_11_0462__li6731134594718">When you clone a task, the advanced settings for data filtering are not cloned. You need to set the advanced settings for the cloned task again.</li><li id="drs_11_0462__li106555581325">Many-to-one task cloning is not supported.</li><li id="drs_11_0462__li10998104743016">When you clone a task that is being changed, if the change information has been saved to the database, the clone task configuration is the same as the changed configuration.</li><li id="drs_11_0462__li139828554326">After a clone task is created, the EIP and private IP address of the new task are different from those of the original task. You may need to configure the network to ensure that the new task can communicate with the source and destination databases.</li></ul>
</div></div>

16
docs/drs/umn/drs_change_history.html
View File

@ -8,7 +8,21 @@
</th>
</tr>
</thead>
<tbody><tr id="drs_change_history__row16261182471919"><td class="cellrowborder" valign="top" width="18.459999999999997%" headers="mcps1.3.1.1.3.1.1 "><p id="drs_change_history__p92621524111919">2025-09-16</p>
<tbody><tr id="drs_change_history__row153662161994"><td class="cellrowborder" valign="top" width="18.459999999999997%" headers="mcps1.3.1.1.3.1.1 "><p id="drs_change_history__p936731611918">2025-11-21</p>
</td>
<td class="cellrowborder" valign="top" width="81.54%" headers="mcps1.3.1.1.3.1.2 "><p id="drs_change_history__p217213281092">This is the twenty-third official release.</p>
<ul id="drs_change_history__ul78993476910"><li id="drs_change_history__li789914475918">Removed unsupported clone tasks from real-time migration. Only the tasks from MongoDB to DDS and from DDS to MongoDB are retained.</li><li id="drs_change_history__li28994471598">Removed unsupported clone tasks from real-time synchronization. Only the task from DDS to MongoDB is retained.</li></ul>
</td>
</tr>
<tr id="drs_change_history__row866122716545"><td class="cellrowborder" valign="top" width="18.459999999999997%" headers="mcps1.3.1.1.3.1.1 "><p id="drs_change_history__p7661127165411">2025-11-04</p>
</td>
<td class="cellrowborder" valign="top" width="81.54%" headers="mcps1.3.1.1.3.1.2 "><p id="drs_change_history__p176612276546">This is the twenty-second official release.</p>
<p id="drs_change_history__p6982175918547">Added the following content:</p>
<ul id="drs_change_history__ul12157131925712"><li id="drs_change_history__li61579192576">Added the scenarios in cloning migration tasks in real-time migration.</li><li id="drs_change_history__li19230132585718">Added the following supported scenarios in cloning synchronization tasks in real-time synchronization:<ul id="drs_change_history__ul2415153185710"><li id="drs_change_history__li1815731965716">To the cloud: MySQL -&gt; GaussDB Distributed, MySQL -&gt; TaurusDB, Oracle -&gt; PostgreSQL, DDM - &gt;MySQL, DDM -&gt; DDM, PostgreSQL -&gt; PostgreSQL</li><li id="drs_change_history__li16455937165811">Out of the cloud: MySQL -&gt; Kafka, DDS -&gt; MongoDB, DDM -&gt; MySQL, GaussDB Distributed -&gt; Oracle, GaussDB Distributed -&gt; Kafka, PostgreSQL -&gt; PostgreSQL</li><li id="drs_change_history__li140161865913">Self-built to self-built: MySQL -&gt; MySQL</li></ul>
</li></ul>
</td>
</tr>
<tr id="drs_change_history__row16261182471919"><td class="cellrowborder" valign="top" width="18.459999999999997%" headers="mcps1.3.1.1.3.1.1 "><p id="drs_change_history__p92621524111919">2025-09-16</p>
</td>
<td class="cellrowborder" valign="top" width="81.54%" headers="mcps1.3.1.1.3.1.2 "><p id="drs_change_history__p1326212246197">This is the twenty-first official release.</p>
<p id="drs_change_history__p1340971916206">Updated the start point format from <strong id="drs_change_history__b20748182504710">File:Position. Executed_Gtid_Set</strong> to <strong id="drs_change_history__b1579410344479">File:Position;Executed_Gtid_Set</strong> in "Real-Time Synchronization" &gt; "Between Self-built Databases" &gt; "From MySQL to MySQL".</p>