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-09-19 10:05:18 +00:00
committed by zuul
parent d78ff45820
commit 1605c388fb
2 changed files with 10 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
docs/drs/umn/drs_03_1118.html
View File

@ -64,7 +64,7 @@
<td class="cellrowborder" valign="top" width="81.71000000000001%" headers="mcps1.3.4.4.2.3.1.2 "><ul id="drs_03_1118__ul548212141879"><li id="drs_03_1118__li448317140710">Objects that have dependencies must be synchronized at the same time to avoid synchronization failure. Common dependencies: tables referenced by views, views referenced by views, views and tables referenced by stored procedures/functions/triggers, and tables referenced by primary and foreign keys</li><li id="drs_03_1118__li144837145717">Only MySQL to MySQL synchronization supports many-to-one synchronization. During table-level many-to-one synchronization, tables without primary keys cannot exist in the source database.</li><li id="drs_03_1118__li3491625415">If the source or destination MySQL database does not support TLS 1.2 or is a self-built database of an earlier version (earlier than 5.6.46 or between 5.7 and 5.7.28), you need to submit an O&amp;M application for testing the SSL connection.</li><li id="drs_03_1118__li144831114472">Resumable upload is supported, but data may be repeatedly inserted into a table that does not have a primary key.</li><li id="drs_03_1118__li17862132392814">The destination table can contain more columns than the source table. However, the following failures must be avoided:<ul id="drs_03_1118__ul17287327103315"><li id="drs_03_1118__li781092416334">Assume that extra columns on the destination cannot be null or have default values. If newly inserted data records are synchronized from the source to the destination, the extra columns will become null, which does not meet the requirements of the destination and will cause the task to fail.</li><li id="drs_03_1118__li2019597173512">Assume that extra columns on the destination must be fixed at a default value and have a unique constraint. If newly inserted data records are synchronized from the source to the destination, the extra columns will contain multiple default values. That does not meet the unique constraint of the destination and will cause the task to fail.</li></ul>
</li><li id="drs_03_1118__li1848310146712">The source database does not support point-in-time recovery (PITR).</li><li id="drs_03_1118__li17484161413714">The destination database cannot be restored to a point in time when a full synchronization was being performed.</li><li id="drs_03_1118__li14483714574">Cascade operations cannot be performed on tables with foreign keys. If the foreign key index of a table is a common index, the table structure may fail to be created. You are advised to use a unique index.</li><li id="drs_03_1118__li119121139976">Binlogs cannot be forcibly deleted. Otherwise, the synchronization task fails.</li><li id="drs_03_1118__li87304497346">The source database does not support the <strong id="drs_03_1118__b875943813216">reset master</strong> or <strong id="drs_03_1118__b1076063862113">reset master to</strong> command, which may cause DRS task failures or data inconsistency.</li><li id="drs_03_1118__li20912103918714">Set the <strong id="drs_03_1118__b30157039573914">expire_log_day</strong> parameter to a proper value to ensure that the binlog does not expire before data transfer resumes. This ensures that services can be recovered after interruption.</li><li id="drs_03_1118__li16483814778">After a task is created, the destination database cannot be set to read-only.</li><li id="drs_03_1118__li39121639277">A real-time synchronization task may fail due to the change of the username and password of the source or destination database. If it happens, rectify the information and then retry the synchronization task on the DRS console. Generally, you are advised not to modify the preceding information during synchronization.</li><li id="drs_03_1118__li169122391974">If the source or destination database port is changed during data synchronization, the synchronization task fails. You can rectify the fault as follows:<ul id="drs_03_1118__ul1491211391570"><li id="drs_03_1118__li11912173914713">If the source database port is wrong, correct the port number on the DRS console and then retry the synchronization task.</li><li id="drs_03_1118__li20912103913715">If the destination database port is wrong, DRS automatically changes the port to the correct one, and then you need to retry the synchronization task.<p id="drs_03_1118__p11912439874"><a name="drs_03_1118__li20912103913715"></a><a name="li20912103913715"></a>Generally, do not modify the port number during synchronization.</p>
</li></ul>
</li><li id="drs_03_1118__li1691212397719">During real-time synchronization, do not change the IP address.</li><li id="drs_03_1118__li169121339371">DDL operations are not supported during full synchronization.</li><li id="drs_03_1118__li13912239279">Data inconsistency may occur when the MyISAM table is modified during a full synchronization.</li><li id="drs_03_1118__li4484114974">In a full plus incremental synchronization task, the source database cannot contain a table with the same name as a table without a primary key in the destination database.</li><li id="drs_03_1118__li169731652101019">For an incremental synchronization task, if the synchronization point is not precise, data inconsistency may occur.</li><li id="drs_03_1118__li139122391373">During table-level incremental synchronization, only DDL operations on tables are allowed.</li><li id="drs_03_1118__li12912123913711">During an incremental synchronization of table-level objects, renaming tables is not recommended.</li><li id="drs_03_1118__li99122391475">For an incremental synchronization task, the start point must be in the standard format. You can run the <strong id="drs_03_1118__b141504832773914">show master status</strong> command in the source database to obtain the start point.<ul id="drs_03_1118__ul109138391471"><li id="drs_03_1118__li691313391372">If GTID mode is disabled, the format of the start point is File:Position (for example, mysql-bin.014734:8937).</li><li id="drs_03_1118__li1891316391275">After the GTID is enabled, the format of the start point is File:Position. Executed_Gtid_Set (for example, mysql-bin.014734:8937;ea352a82-e9a0-11ea-b650-fa163e1e82ed:1-23377228, 8404bb4b-cc96-11ea-ae7f-fa163ead1b99:1-59684135)</li></ul>
</li><li id="drs_03_1118__li1691212397719">During real-time synchronization, do not change the IP address.</li><li id="drs_03_1118__li169121339371">DDL operations are not supported during full synchronization.</li><li id="drs_03_1118__li13912239279">Data inconsistency may occur when the MyISAM table is modified during a full synchronization.</li><li id="drs_03_1118__li4484114974">In a full plus incremental synchronization task, the source database cannot contain a table with the same name as a table without a primary key in the destination database.</li><li id="drs_03_1118__li169731652101019">For an incremental synchronization task, if the synchronization point is not precise, data inconsistency may occur.</li><li id="drs_03_1118__li139122391373">During table-level incremental synchronization, only DDL operations on tables are allowed.</li><li id="drs_03_1118__li12912123913711">During an incremental synchronization of table-level objects, renaming tables is not recommended.</li><li id="drs_03_1118__li99122391475">For an incremental synchronization task, the start point must be in the standard format. You can run the <strong id="drs_03_1118__b141504832773914">show master status</strong> command in the source database to obtain the start point.<ul id="drs_03_1118__ul109138391471"><li id="drs_03_1118__li691313391372">If GTID mode is disabled, the format of the start point is File:Position (for example, mysql-bin.014734:8937).</li><li id="drs_03_1118__li1891316391275">After the GTID is enabled, the format of the start point is File:Position;Executed_Gtid_Set (for example, mysql-bin.014734:8937;ea352a82-e9a0-11ea-b650-fa163e1e82ed:1-23377228, 8404bb4b-cc96-11ea-ae7f-fa163ead1b99:1-59684135)</li></ul>
</li></ul>
</td>
</tr>
@ -290,8 +290,8 @@
<tr id="drs_03_1118__row166170119176"><td class="cellrowborder" valign="top" width="16.1%" headers="mcps1.3.5.2.4.2.1.2.3.1.1 "><p id="drs_03_1118__p9617171110178">Start Point</p>
</td>
<td class="cellrowborder" valign="top" width="83.89999999999999%" headers="mcps1.3.5.2.4.2.1.2.3.1.2 "><p id="drs_03_1118__p86171411121715">The position where the incremental log was created based on the source log. It allows you to perform resumable data transfer.</p>
<p id="drs_03_1118__p1618171121710">For an incremental synchronization task, the start point must be in the standard format. You can run the <strong id="drs_03_1118__b990108542">show master status</strong> command in the source database to obtain the start point.</p>
<ul id="drs_03_1118__ul5618121111713"><li id="drs_03_1118__li261861111173">If GTID mode is disabled, the format of the start point is File:Position (for example, mysql-bin.014734:8937).</li><li id="drs_03_1118__li1561811117179">After the GTID is enabled, the format of the start point is File:Position; Executed_Gtid_Set (for example, mysql-bin.014734:8937;ea352a82-e9a0-11ea-b650-fa163e1e82ed:1-23377228, 8404bb4b-cc96-11ea-ae7f-fa163ead1b99:1-59684135)</li></ul>
<p id="drs_03_1118__p1618171121710">For an incremental synchronization task, the start point must be in the standard format. You can run the <strong id="drs_03_1118__b714873399">show master status</strong> command in the source database to obtain the start point.</p>
<ul id="drs_03_1118__ul5618121111713"><li id="drs_03_1118__li261861111173">If GTID mode is disabled, the format of the start point is File:Position (for example, mysql-bin.014734:8937).</li><li id="drs_03_1118__li1561811117179">After the GTID is enabled, the format of the start point is File:Position;Executed_Gtid_Set (for example, mysql-bin.014734:8937;ea352a82-e9a0-11ea-b650-fa163e1e82ed:1-23377228, 8404bb4b-cc96-11ea-ae7f-fa163ead1b99:1-59684135)</li></ul>
</td>
</tr>
<tr id="drs_03_1118__row1961810114172"><td class="cellrowborder" valign="top" width="16.1%" headers="mcps1.3.5.2.4.2.1.2.3.1.1 "><p id="drs_03_1118__p1361801191720">Synchronization Object</p>

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

@ -8,7 +8,13 @@
</th>
</tr>
</thead>
<tbody><tr id="drs_change_history__row156871943111119"><td class="cellrowborder" valign="top" width="18.459999999999997%" headers="mcps1.3.1.1.3.1.1 "><p id="drs_change_history__p1568784314113">2025-09-09</p>
<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>
</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>
</td>
</tr>
<tr id="drs_change_history__row156871943111119"><td class="cellrowborder" valign="top" width="18.459999999999997%" headers="mcps1.3.1.1.3.1.1 "><p id="drs_change_history__p1568784314113">2025-09-09</p>
</td>
<td class="cellrowborder" valign="top" width="81.54%" headers="mcps1.3.1.1.3.1.2 "><p id="drs_change_history__p12687124317116">This is the twentieth official release.</p>
<p id="drs_change_history__p12911737175117">Added the following content:</p>