Files
doc-exports/docs/drs/umn/drs_04_0100.html
2023-08-15 09:57:48 +00:00

359 lines
56 KiB
HTML

<a name="drs_04_0100"></a><a name="drs_04_0100"></a>
<h1 class="topictitle1">From MySQL to MySQL</h1>
<div id="body0000001089099209"><div class="section" id="drs_04_0100__section972219465132"><h4 class="sectiontitle">Supported Source and Destination Databases</h4>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="drs_04_0100__table98082311144" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Supported databases</caption><thead align="left"><tr id="drs_04_0100__row18172361412"><th align="left" class="cellrowborder" valign="top" width="50%" id="mcps1.3.1.2.2.3.1.1"><p id="drs_04_0100__p1281723171412">Source DB</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="50%" id="mcps1.3.1.2.2.3.1.2"><p id="drs_04_0100__p78192351414">Destination DB</p>
</th>
</tr>
</thead>
<tbody><tr id="drs_04_0100__row98172391416"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.1.2.2.3.1.1 "><ul id="drs_04_0100__ul35041538125820"><li id="drs_04_0100__li11504133855820">RDS for MySQL (5.5, 5.6, 5.7, 8.0)</li></ul>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.1.2.2.3.1.2 "><ul id="drs_04_0100__ul1981618228235"><li id="drs_04_0100__li48161622112310">On-premises databases (MySQL 5.5, 5.6, 5.7, and 8.0)</li><li id="drs_04_0100__li7816122162319">ECS databases (MySQL 5.5, 5.6, 5.7, and 8.0)</li><li id="drs_04_0100__li18816162219237">Other cloud databases (MySQL 5.5, 5.6, 5.7, and 8.0)</li><li id="drs_04_0100__li9816192215233">RDS for MySQL (5.5, 5.6, 5.7, 8.0)<div class="note" id="drs_04_0100__note1841273541416"><span class="notetitle"> NOTE: </span><div class="notebody"><p id="drs_04_0100__p1256681085419">The destination database version must be the same as or later than the source database version.</p>
</div></div>
</li></ul>
</td>
</tr>
</tbody>
</table>
</div>
</div>
<div class="section" id="drs_04_0100__section113301422955"><h4 class="sectiontitle">Database Account Permission Requirements</h4><p id="drs_04_0100__p136546175215">To start a migration task, the source and destination database users must have permissions listed in the following table. Different types of migration tasks require different permissions. For details, see <a href="#drs_04_0100__table68938710614">Table 2</a>. DRS automatically checks the database account permissions in the pre-check phase and provides handling suggestions.</p>
<div class="tablenoborder"><a name="drs_04_0100__table68938710614"></a><a name="table68938710614"></a><table cellpadding="4" cellspacing="0" summary="" id="drs_04_0100__table68938710614" frame="border" border="1" rules="all"><caption><b>Table 2 </b>Database account permission</caption><thead align="left"><tr id="drs_04_0100__row889316711618"><th align="left" class="cellrowborder" valign="top" width="18%" id="mcps1.3.2.3.2.4.1.1"><p id="drs_04_0100__p118931971365">Type</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="30%" id="mcps1.3.2.3.2.4.1.2"><p id="drs_04_0100__p108939716614">Full Migration</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="52%" id="mcps1.3.2.3.2.4.1.3"><p id="drs_04_0100__p95914417819">Full+Incremental Migration</p>
</th>
</tr>
</thead>
<tbody><tr id="drs_04_0100__row10893671662"><td class="cellrowborder" valign="top" width="18%" headers="mcps1.3.2.3.2.4.1.1 "><p id="drs_04_0100__p15894167462">Source database user</p>
</td>
<td class="cellrowborder" valign="top" width="30%" headers="mcps1.3.2.3.2.4.1.2 "><p id="drs_04_0100__p15174171471510">The user must have the following minimum permissions:</p>
<p id="drs_04_0100__p108841442183514">SELECT, SHOW VIEW, and EVENT</p>
<p id="drs_04_0100__p116001620171716">During user migration, the user must have the SELECT permission for mysql.user.</p>
</td>
<td class="cellrowborder" valign="top" width="52%" headers="mcps1.3.2.3.2.4.1.3 "><p id="drs_04_0100__p15834173161">The user must have the following minimum permissions:</p>
<p id="drs_04_0100__p7405201710429">SELECT, SHOW VIEW, EVENT, LOCK TABLES, REPLICATION SLAVE, and REPLICATION CLIENT</p>
<p id="drs_04_0100__p1447483010182">During user migration, the user must have the SELECT permission for mysql.user.</p>
</td>
</tr>
<tr id="drs_04_0100__row2142181212117"><td class="cellrowborder" valign="top" headers="mcps1.3.2.3.2.4.1.1 "><p id="drs_04_0100__p9143512131110">Destination database user</p>
</td>
<td class="cellrowborder" colspan="2" valign="top" headers="mcps1.3.2.3.2.4.1.2 mcps1.3.2.3.2.4.1.3 "><p id="drs_04_0100__p17835151531318">The user must have the following minimum permissions:</p>
<p id="drs_04_0100__p1494841071318">SELECT, CREATE, ALTER, DROP, DELETE, INSERT, UPDATE, INDEX, EVENT, CREATE VIEW, CREATE ROUTINE, TRIGGER, REFERENCES, and WITH GRANT OPTION. If the destination database version is in the range 8.0.14 to 8.0.18, the SESSION_VARIABLES_ADMIN permission is required.</p>
<p id="drs_04_0100__p467803741810">To migrate data, you must have the SELECT, INSERT, UPDATE, and DELETE permissions for the MySQL database.</p>
</td>
</tr>
</tbody>
</table>
</div>
</div>
<div class="section" id="drs_04_0100__section1891412810322"><a name="drs_04_0100__section1891412810322"></a><a name="section1891412810322"></a><h4 class="sectiontitle">Suggestions</h4><div class="caution" id="drs_04_0100__drs_04_0088_note148711074311"><span class="cautiontitle"><img src="public_sys-resources/caution_3.0-en-us.png"> </span><div class="cautionbody"><ul id="drs_04_0100__drs_04_0088_ul131861088439"><li id="drs_04_0100__drs_04_0088_li21868804311">When a task is being started or in the full migration phase, do not perform DDL operations on the source database. Otherwise, the task may be abnormal.</li><li id="drs_04_0100__drs_04_0088_li1684814724618">To maintain data consistency before and after the migration, do not write data to the source and destination databases in the full migration mode. In the full+incremental migration mode, you can continue the migration while data is still being written to the source database.</li></ul>
</div></div>
<ul id="drs_04_0100__drs_04_0088_ul5521539113519"><li id="drs_04_0100__drs_04_0088_li1452113914356">The success of migration depends on environment and manual operations. You can run a migration test before you start the full-scale migration to help you detect and resolve problems in advance.</li><li id="drs_04_0100__drs_04_0088_li176076214115">Start your migration task during off-peak hours. A less active database is easier to migrate successfully. If the data is fairly static, there is less likely to be any severe performance impacts during the migration. If you have to migrate data during peak hours, you can select <span class="uicontrol" id="drs_04_0100__drs_04_0088_uicontrol140019134328"><b>Yes</b></span> for <span class="uicontrol" id="drs_04_0100__drs_04_0088_uicontrol144011113183218"><b>Flow Control</b></span> to adjust the migration speed.<ul id="drs_04_0100__drs_04_0088_ul17192054114"><li id="drs_04_0100__drs_04_0088_li1771917024115">If network bandwidth is not limited, the query rate of the source database increases by about 50 MB/s during full migration, and two to four CPUs are occupied.</li></ul>
<ul id="drs_04_0100__drs_04_0088_ul52891812383"><li id="drs_04_0100__drs_04_0088_li2036966133319">To ensure data consistency, tables to be migrated without a primary key may be locked for 3s.</li><li id="drs_04_0100__drs_04_0088_li1369963336">The data being migrated may be locked by other transactions for a long period of time, resulting in read timeout.</li><li id="drs_04_0100__drs_04_0088_li5370186103317">Due to the inherent characteristics of MySQL, in some scenarios the performance may be negatively affected. For example, if the CPU resources are insufficient and the storage engine is TokuDB, the read speed on tables may be decreased by 10%.</li><li id="drs_04_0100__drs_04_0088_li5370136143311">If DRS concurrently reads data from a database, it will use about 6 to 10 sessions. The impact of the connections on services must be considered.</li><li id="drs_04_0100__drs_04_0088_li12289715380">If you read a table, especially a large table, during the full migration, the exclusive lock on that table may be blocked.</li></ul>
</li><li id="drs_04_0100__drs_04_0088_li16745522135020">Data-level comparison<p id="drs_04_0100__drs_04_0088_p2725192712531"><a name="drs_04_0100__drs_04_0088_li16745522135020"></a><a name="drs_04_0088_li16745522135020"></a>To obtain accurate comparison results, compare data at a specified time point during off-peak hours. If it is needed, select <strong id="drs_04_0100__drs_04_0088_b32068041214">Start at a specified time</strong> for <strong id="drs_04_0100__drs_04_0088_b1120813016126">Comparison Time</strong>. Due to slight time difference and continuous operations on data, inconsistent comparison results may be generated, reducing the reliability and validity of the results.</p>
</li></ul>
</div>
<div class="section" id="drs_04_0100__section182303625619"><a name="drs_04_0100__section182303625619"></a><a name="section182303625619"></a><h4 class="sectiontitle">Precautions</h4><p id="drs_04_0100__p2095783645012">The full+incremental migration process consists of four phases: task startup, full synchronization, incremental synchronization, and task completion. A single full migration task contains three phases. To ensure smooth migration, read the following precautions before creating a migration task.</p>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="drs_04_0100__table4442125818552" frame="border" border="1" rules="all"><caption><b>Table 3 </b>Precautions</caption><thead align="left"><tr id="drs_04_0100__row124421758145516"><th align="left" class="cellrowborder" valign="top" width="18.35%" id="mcps1.3.4.3.2.3.1.1"><p id="drs_04_0100__p1144412589553">Type</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="81.65%" id="mcps1.3.4.3.2.3.1.2"><p id="drs_04_0100__p24441358185515">Restrictions</p>
</th>
</tr>
</thead>
<tbody><tr id="drs_04_0100__row1144485815518"><td class="cellrowborder" valign="top" width="18.35%" headers="mcps1.3.4.3.2.3.1.1 "><p id="drs_04_0100__p14444135855518">Starting a task</p>
</td>
<td class="cellrowborder" valign="top" width="81.65%" headers="mcps1.3.4.3.2.3.1.2 "><ul id="drs_04_0100__ul19445165845518"><li id="drs_04_0100__li344516583554"><strong id="drs_04_0100__b38583450297">Source database requirements:</strong><ul id="drs_04_0100__ul840714945213"><li id="drs_04_0100__li26414134344">The binlog of the source database must be enabled and use the row-based format during incremental migration.</li></ul>
<ul id="drs_04_0100__ul9445115812556"><li id="drs_04_0100__li196511130341">If the storage space is sufficient, store the source database binlogs for as long as possible. The recommended retention period is three days.</li><li id="drs_04_0100__li1654131345">If the <strong id="drs_04_0100__drs_04_0088_b10037234028027">expire_logs_days</strong> value of the source database is set to <strong id="drs_04_0100__drs_04_0088_b4963576908027">0</strong>, the migration may fail. Set <strong id="drs_04_0100__drs_04_0088_b1150685523118">expire_logs_day</strong> 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_04_0100__li176521311349">During an incremental migration, the <strong id="drs_04_0100__drs_04_0088_b11460683848027">server_id</strong> value of the MySQL source database must be set. If the source database version is MySQL 5.6 or earlier, the <strong id="drs_04_0100__drs_04_0088_b9088996658027">server_id</strong> value ranges from <strong id="drs_04_0100__drs_04_0088_b15528341468027">2</strong> to <strong id="drs_04_0100__drs_04_0088_b15979271768027">4294967296</strong>. If the source database is MySQL 5.7 or later, the <strong id="drs_04_0100__drs_04_0088_b2363484028027">server_id</strong> value ranges from <strong id="drs_04_0100__drs_04_0088_b15731162528027">1</strong> to <strong id="drs_04_0100__drs_04_0088_b19304862168027">4294967296</strong>.</li><li id="drs_04_0100__li46511313344">Enable <strong id="drs_04_0100__drs_04_0088_b4144704588027">skip-name-resolve</strong> for the source database to reduce the possibility of connection timeout.</li><li id="drs_04_0100__li1665171312348">Enable GTID for the source database. If GTID is not enabled for the source database, primary/standby switchover is not supported. DRS tasks will be interrupted and cannot be restored during a switchover.</li><li id="drs_04_0100__li26541317348">The <strong id="drs_04_0100__drs_04_0088_b5218442368027">log_slave_updates</strong> parameter of the source database must be enabled. Otherwise, the migration fails.</li><li id="drs_04_0100__li126591318344">The <strong id="drs_04_0100__drs_04_0088_b16274536148027">binlog_row_image</strong> parameter value of the source database must be <strong id="drs_04_0100__drs_04_0088_b18751020768027">FULL</strong>. Otherwise, the migration fails.</li></ul>
</li></ul>
<ul id="drs_04_0100__ul44471358175516"><li id="drs_04_0100__li1544710582556"><strong id="drs_04_0100__b1096115148388">Source database object requirements:</strong><ul id="drs_04_0100__ul1144813584554"><li id="drs_04_0100__li492718447913">The source database does not support the <strong id="drs_04_0100__drs_04_0088_b157388511421">mysql binlog dump</strong> command.</li><li id="drs_04_0100__li1416114611560">The source database does not support the <strong id="drs_04_0100__drs_04_0088_b124533592211">reset master</strong> or <strong id="drs_04_0100__drs_04_0088_b919417613313">reset master to</strong> command, which may cause DRS task failures or data inconsistency.</li><li id="drs_04_0100__li20448195855517">Associated objects must be migrated at the same time to avoid migration failure caused by missing associated objects.</li><li id="drs_04_0100__li13448458145520">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_04_0100__li744955825514">Due to the MySQL constraints, if the one-time event triggering time of the source database is earlier than the migration start time, the event will not be migrated to the destination database.</li></ul>
</li><li id="drs_04_0100__li1444955819557"><strong id="drs_04_0100__b19150541133914">Destination database parameter requirements:</strong><ul id="drs_04_0100__ul74491958155520"><li id="drs_04_0100__li14449158125510">The destination DB instance is running properly.</li><li id="drs_04_0100__li644911583553">The destination DB instance must have sufficient storage space.</li><li id="drs_04_0100__li1450135825514">You are advised to use the row-based binlog in the destination database. Otherwise, an error may occur during an incremental migration.</li><li id="drs_04_0100__li1145019588556">The destination database isolation level must be set to at least read committed.</li><li id="drs_04_0100__li1045045805519">During migration, a large amount of data is written to the destination database. If the value of the <strong id="drs_04_0100__drs_04_0088_b1665215972816">max_allowed_packet</strong> parameter of the destination database is too small, data cannot be written. You are advised to set the <strong id="drs_04_0100__drs_04_0088_b16654959122813">max_allowed_packet</strong> parameter to a value greater than 100 MB.</li><li id="drs_04_0100__li64505583551">Enable GTID of the destination database.</li><li id="drs_04_0100__li17450258185519">The character sets of the source and destination databases must be the same. Otherwise, the migration fails.</li><li id="drs_04_0100__li94504589551">The <strong id="drs_04_0100__drs_04_0088_b18293019228027">log_bin_trust_function_creators</strong> parameter value of the destination database must be set to <strong id="drs_04_0100__drs_04_0088_b20188824638027">on</strong>. Otherwise, the migration fails.</li><li id="drs_04_0100__li445117584559">The value of <strong id="drs_04_0100__drs_04_0088_b19202341459">server_uuid</strong> of the destination database must be the same as that of the source database. Otherwise, the incremental migration fails.</li><li id="drs_04_0100__li164511158115513">The <strong id="drs_04_0100__drs_04_0088_b10903411676">collation_server</strong> values of the destination database and source database must be the same. Otherwise, the migration may fail.</li><li id="drs_04_0100__li1045185895516">The value of <strong id="drs_04_0100__drs_04_0088_b6417921474">time_zone</strong> of the destination database must be the same as that of the source database. Otherwise, the migration may fail.</li><li id="drs_04_0100__li15451185825520">The <strong id="drs_04_0100__drs_04_0088_b1557316291974">sql_mode</strong> values of the destination database and source database must be the same. Otherwise, the migration may fail.</li><li id="drs_04_0100__li44511858155511">The <strong id="drs_04_0100__drs_04_0088_b315011231597">innodb_strict_mode</strong> values of the destination database and source database must be the same. Otherwise, the migration may fail.</li><li id="drs_04_0100__li14511858185513">The <strong id="drs_04_0100__drs_04_0088_b18845439628027">lower_case_table_names</strong> values of the source and destination databases must be the same. Otherwise, the migration fails.</li></ul>
</li><li id="drs_04_0100__li74511658165510"><strong id="drs_04_0100__b3929910415">Destination database object requirements:</strong><ul id="drs_04_0100__ul545111582551"><li id="drs_04_0100__li7451135817559">The destination DB instance cannot contain databases with the same name as the source databases (except the MySQL system database).</li></ul>
</li><li id="drs_04_0100__li4452175818551"><strong id="drs_04_0100__b157367516504">Other notes:</strong>
<ul id="drs_04_0100__ul0452145815555"><li id="drs_04_0100__li1245205815551">The table without a primary key lacks a unique identifier for rows. When the network is unstable, you may need to retry the task several times, or data inconsistency may occur.</li><li id="drs_04_0100__li945255875516">The destination database cannot be restored to a point in time when a full migration was being performed.</li><li id="drs_04_0100__li845295817556">If the source DB instance is an RDS for MySQL instance, tables encrypted using Transparent Data Encryption (TDE) cannot be synchronized.</li><li id="drs_04_0100__li18660184119720">If the 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></ul>
</li></ul>
</td>
</tr>
<tr id="drs_04_0100__row18453135813553"><td class="cellrowborder" valign="top" width="18.35%" headers="mcps1.3.4.3.2.3.1.1 "><p id="drs_04_0100__p204532587552">Full migration</p>
</td>
<td class="cellrowborder" valign="top" width="81.65%" headers="mcps1.3.4.3.2.3.1.2 "><ul id="drs_04_0100__ul13453558135514"><li id="drs_04_0100__li54224217541">During task startup and full migration, do not perform DDL operations on the source database. Otherwise, the task may be abnormal.</li><li id="drs_04_0100__li88214287545">During migration, do not modify or delete the usernames, passwords, permissions, or ports of the source and destination databases.</li><li id="drs_04_0100__li4777103615111">During migration, do not modify the destination database (including but not limited to DDL and DML operations) that is being migrated.</li><li id="drs_04_0100__li106347193161">During migration, do not write the statement-based binlog into the source database.</li><li id="drs_04_0100__li7206162310550">During migration, do not clear the binlog in the source database.</li><li id="drs_04_0100__li22061523115514">During migration, do not create a database named <strong id="drs_04_0100__drs_04_0088_b12194254708027">ib_logfile</strong> in the source database.</li></ul>
</td>
</tr>
<tr id="drs_04_0100__row947065815559"><td class="cellrowborder" valign="top" width="18.35%" headers="mcps1.3.4.3.2.3.1.1 "><p id="drs_04_0100__p16470125818553">Incremental migration</p>
</td>
<td class="cellrowborder" valign="top" width="81.65%" headers="mcps1.3.4.3.2.3.1.2 "><ul id="drs_04_0100__ul12470165885517"><li id="drs_04_0100__li1331154125615">During migration, do not modify or delete the usernames, passwords, permissions, or ports of the source and destination databases.</li><li id="drs_04_0100__li113317419566">During migration, do not modify the destination database (including but not limited to DDL and DML operations) that is being migrated.</li><li id="drs_04_0100__li161431358171616">During migration, do not write the statement-based binlog into the source database.</li><li id="drs_04_0100__li17331134155614">During migration, do not clear the binlog in the source database.</li><li id="drs_04_0100__li10331641145610">During migration, do not create a database named <strong id="drs_04_0100__drs_04_0088_b877122519914">ib_logfile</strong> on the source side.</li><li id="drs_04_0100__li1470417519562">During an incremental migration of table-level objects, renaming tables is not supported.</li><li id="drs_04_0100__li1071313515577">During an incremental migration, do not perform the point-in-time recovery (PITR) operation on the source database.</li><li id="drs_04_0100__li1871315145712">During an incremental migration, resumable upload is supported. However, data may be repeatedly inserted into a non-transactional table that does not have a primary key when the server system breaks down.</li><li id="drs_04_0100__li18259436151715">DDL statements are supported in the incremental migration phase.</li></ul>
</td>
</tr>
<tr id="drs_04_0100__row1348005865513"><td class="cellrowborder" valign="top" width="18.35%" headers="mcps1.3.4.3.2.3.1.1 "><p id="drs_04_0100__p448185825515">Stopping a task</p>
</td>
<td class="cellrowborder" valign="top" width="81.65%" headers="mcps1.3.4.3.2.3.1.2 "><ul id="drs_04_0100__ul14811758185512"><li id="drs_04_0100__li12481105814556"><strong id="drs_04_0100__b69474501811">Stop a task normally.</strong><ul id="drs_04_0100__ul948115584554"><li id="drs_04_0100__li2048110581558">The selected events and triggers are migrated while the migration task proceeds to the final stage. Before a task is completed, ensure that the source and destination databases are connected and pay attention to the migration status reported by the migration log.</li></ul>
</li><li id="drs_04_0100__li12482125818559"><strong id="drs_04_0100__b12540332821">Forcibly stop a task.</strong><ul id="drs_04_0100__ul194828588557"><li id="drs_04_0100__li1748220587552">If you forcibly stop a task, DRS resources will be released and triggers and events will not be migrated. You need to <a href="drs_14_0006.html">manually migrate triggers, events, and events</a>. If you want DRS to migrate triggers and events, restore the DRS task first. After the task status becomes normal, stop the task.</li></ul>
</li></ul>
</td>
</tr>
</tbody>
</table>
</div>
</div>
<div class="section" id="drs_04_0100__section5231148112320"><h4 class="sectiontitle">Prerequisites</h4><ul id="drs_04_0100__ul1210173484610"><li id="drs_04_0100__drs_04_0088_li18901124413250">You have logged in to the DRS console.</li><li id="drs_04_0100__drs_04_0088_li8902144442514">For details about the DB types and versions supported by real-time migration, see <a href="drs_01_0301.html">Real-Time Migration</a>.</li></ul>
<ul id="drs_04_0100__ul107011886427"><li id="drs_04_0100__li1170198124219">You have read <a href="#drs_04_0100__section1891412810322">Suggestions</a> and <a href="#drs_04_0100__section182303625619">Precautions</a>.</li></ul>
</div>
<div class="section" id="drs_04_0100__section196005561909"><h4 class="sectiontitle">Procedure</h4><p id="drs_04_0100__p1857344910108">This section uses the migration from an RDS MySQL database to a MySQL database on an ECS as an example to describe how to configure a migration task in a VPC network on the DRS management console.</p>
<ol id="drs_04_0100__ol10043287141752"><li id="drs_04_0100__li683704772120"><span>On the <span class="uicontrol" id="drs_04_0100__drs_04_0088_uicontrol62413042233311"><b>Online Migration Management</b></span> page, click <span class="uicontrol" id="drs_04_0100__drs_04_0088_uicontrol19976703433311"><b>Create Migration Task</b></span>.</span></li><li id="drs_04_0100__li4516889420249"><span>On the <strong id="drs_04_0100__b35684750655620">Create Replication Instance</strong> page, configure task details, description, and the replication instance, and click <strong id="drs_04_0100__b178926802655620">Next</strong>.</span><p><ul id="drs_04_0100__ul1212463813112"><li id="drs_04_0100__li1244316653910">Task information description
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="drs_04_0100__drs_04_0088_table04451801456" frame="border" border="1" rules="all"><caption><b>Table 4 </b>Task information</caption><thead align="left"><tr id="drs_04_0100__drs_04_0088_row15445408456"><th align="left" class="cellrowborder" valign="top" width="18.42%" id="mcps1.3.6.3.2.2.1.1.1.2.3.1.1"><p id="drs_04_0100__drs_04_0088_p174481064514">Parameter</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="81.58%" id="mcps1.3.6.3.2.2.1.1.1.2.3.1.2"><p id="drs_04_0100__drs_04_0088_p9448180134513">Description</p>
</th>
</tr>
</thead>
<tbody><tr id="drs_04_0100__drs_04_0088_row18448809453"><td class="cellrowborder" valign="top" width="18.42%" headers="mcps1.3.6.3.2.2.1.1.1.2.3.1.1 "><p id="drs_04_0100__drs_04_0088_p154483074514">Region</p>
</td>
<td class="cellrowborder" valign="top" width="81.58%" headers="mcps1.3.6.3.2.2.1.1.1.2.3.1.2 "><p id="drs_04_0100__drs_04_0088_p12449150184517">The region where the replication instance is deployed. You can change the region. To reduce latency and improve access speed, select the region closest to your services.</p>
</td>
</tr>
<tr id="drs_04_0100__drs_04_0088_row124507014515"><td class="cellrowborder" valign="top" width="18.42%" headers="mcps1.3.6.3.2.2.1.1.1.2.3.1.1 "><p id="drs_04_0100__drs_04_0088_p154501501453">Project</p>
</td>
<td class="cellrowborder" valign="top" width="81.58%" headers="mcps1.3.6.3.2.2.1.1.1.2.3.1.2 "><p id="drs_04_0100__drs_04_0088_p1145013018452">The project corresponds to the current region and can be changed.</p>
</td>
</tr>
<tr id="drs_04_0100__drs_04_0088_row17450700457"><td class="cellrowborder" valign="top" width="18.42%" headers="mcps1.3.6.3.2.2.1.1.1.2.3.1.1 "><p id="drs_04_0100__drs_04_0088_p645000104517">Task Name</p>
</td>
<td class="cellrowborder" valign="top" width="81.58%" headers="mcps1.3.6.3.2.2.1.1.1.2.3.1.2 "><p id="drs_04_0100__drs_04_0088_p1145013054517">The task name must start with a letter and consist of 4 to 50 characters. It can contain only letters, digits, hyphens (-), and underscores (_).</p>
</td>
</tr>
<tr id="drs_04_0100__drs_04_0088_row1745116015452"><td class="cellrowborder" valign="top" width="18.42%" headers="mcps1.3.6.3.2.2.1.1.1.2.3.1.1 "><p id="drs_04_0100__drs_04_0088_p145112014514">Description</p>
</td>
<td class="cellrowborder" valign="top" width="81.58%" headers="mcps1.3.6.3.2.2.1.1.1.2.3.1.2 "><p id="drs_04_0100__drs_04_0088_p8451140124517">The description consists of a maximum of 256 characters and cannot contain special characters !=&lt;&gt;'&amp;"\</p>
</td>
</tr>
</tbody>
</table>
</div>
</li><li id="drs_04_0100__li1525065719111">Replication instance information
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="drs_04_0100__table2444111441218" frame="border" border="1" rules="all"><caption><b>Table 5 </b>Replication instance settings</caption><thead align="left"><tr id="drs_04_0100__row1144411146126"><th align="left" class="cellrowborder" valign="top" width="23.87%" id="mcps1.3.6.3.2.2.1.2.1.2.3.1.1"><p id="drs_04_0100__p1444431451211">Parameter</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="76.13%" id="mcps1.3.6.3.2.2.1.2.1.2.3.1.2"><p id="drs_04_0100__p844431411128">Description</p>
</th>
</tr>
</thead>
<tbody><tr id="drs_04_0100__row12444171413125"><td class="cellrowborder" valign="top" width="23.87%" headers="mcps1.3.6.3.2.2.1.2.1.2.3.1.1 "><p id="drs_04_0100__p13445161413128">Data Flow</p>
</td>
<td class="cellrowborder" valign="top" width="76.13%" headers="mcps1.3.6.3.2.2.1.2.1.2.3.1.2 "><p id="drs_04_0100__p1144571416121">Select <strong id="drs_04_0100__b27118028755620">Out of the cloud</strong>.</p>
<p id="drs_04_0100__p12445111451214">The source database is a database on the current cloud.</p>
</td>
</tr>
<tr id="drs_04_0100__row14445214171219"><td class="cellrowborder" valign="top" width="23.87%" headers="mcps1.3.6.3.2.2.1.2.1.2.3.1.1 "><p id="drs_04_0100__p84451314181216">Source DB Engine</p>
</td>
<td class="cellrowborder" valign="top" width="76.13%" headers="mcps1.3.6.3.2.2.1.2.1.2.3.1.2 "><p id="drs_04_0100__p1244517144121">Select <strong id="drs_04_0100__b842352706143130">MySQL</strong>.</p>
</td>
</tr>
<tr id="drs_04_0100__row134451814141212"><td class="cellrowborder" valign="top" width="23.87%" headers="mcps1.3.6.3.2.2.1.2.1.2.3.1.1 "><p id="drs_04_0100__p15445314141213">Destination DB Engine</p>
</td>
<td class="cellrowborder" valign="top" width="76.13%" headers="mcps1.3.6.3.2.2.1.2.1.2.3.1.2 "><p id="drs_04_0100__p1445201421211">Select <strong id="drs_04_0100__b977693758">MySQL</strong>.</p>
</td>
</tr>
<tr id="drs_04_0100__row15445181415124"><td class="cellrowborder" valign="top" width="23.87%" headers="mcps1.3.6.3.2.2.1.2.1.2.3.1.1 "><p id="drs_04_0100__p444571481213">Network Type</p>
</td>
<td class="cellrowborder" valign="top" width="76.13%" headers="mcps1.3.6.3.2.2.1.2.1.2.3.1.2 "><p id="drs_04_0100__p844518148124">Available options: <strong id="drs_04_0100__b13591135218014">Public network</strong>, <strong id="drs_04_0100__b660405213013">VPC</strong>, <strong id="drs_04_0100__b196076523013">VPN or Direct Connect</strong></p>
<ul id="drs_04_0100__ul204451014111215"><li id="drs_04_0100__li8445314171216">VPC is suitable for migrations of cloud databases in the same region.</li><li id="drs_04_0100__li7445201451210">VPN and Direct Connect are suitable for migrations from on-premises databases to cloud databases or between cloud databases across regions.</li><li id="drs_04_0100__li15445171421216">Public network is suitable for migrations from on-premises databases or external cloud databases to destination databases.</li></ul>
</td>
</tr>
<tr id="drs_04_0100__row154450149123"><td class="cellrowborder" valign="top" width="23.87%" headers="mcps1.3.6.3.2.2.1.2.1.2.3.1.1 "><p id="drs_04_0100__p74451914191219">Source DB Instance</p>
</td>
<td class="cellrowborder" valign="top" width="76.13%" headers="mcps1.3.6.3.2.2.1.2.1.2.3.1.2 "><p id="drs_04_0100__p444631441218">Select the DB instance whose data is to be migrated out of the cloud.</p>
</td>
</tr>
<tr id="drs_04_0100__row10446171461213"><td class="cellrowborder" valign="top" width="23.87%" headers="mcps1.3.6.3.2.2.1.2.1.2.3.1.1 "><p id="drs_04_0100__p84462014101215">Replication Instance Subnet</p>
</td>
<td class="cellrowborder" valign="top" width="76.13%" headers="mcps1.3.6.3.2.2.1.2.1.2.3.1.2 "><p id="drs_04_0100__p12708230277">The subnet where the replication instance resides. You can also click <strong id="drs_04_0100__drs_04_0088_b19718231183614">View Subnet</strong> to go to the network console to view the subnet where the instance resides. </p>
<p id="drs_04_0100__p1870192312710">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 replication instance is successfully created, only subnets with DHCP enabled are displayed.</p>
</td>
</tr>
<tr id="drs_04_0100__row844611143122"><td class="cellrowborder" valign="top" width="23.87%" headers="mcps1.3.6.3.2.2.1.2.1.2.3.1.1 "><p id="drs_04_0100__p74461814121220">Migration Type</p>
</td>
<td class="cellrowborder" valign="top" width="76.13%" headers="mcps1.3.6.3.2.2.1.2.1.2.3.1.2 "><ul id="drs_04_0100__ul1244651401217"><li id="drs_04_0100__li1644615147125"><strong id="drs_04_0100__b115701325833311">Full</strong>: This <span class="keyword" id="drs_04_0100__keyword66995738333311">migration</span> type is suitable for scenarios where service interruption is acceptable. All objects and data in non-system databases are migrated to the destination database at one time. The objects include tables, views, and stored procedures.<div class="note" id="drs_04_0100__note174461414171220"><span class="notetitle"> NOTE: </span><div class="notebody"><p id="drs_04_0100__p2044611412126">If you are performing a full migration, do not perform operations on the source database. Otherwise, data generated in the source database during the migration will not be synchronized to the destination database.</p>
</div></div>
</li><li id="drs_04_0100__li154461914101216"><strong id="drs_04_0100__b88163434833311">Full+Incremental</strong>: This migration type allows you to migrate data without interrupting services. After a full migration initializes the destination database, an incremental migration initiates and parses logs to ensure data consistency between the source and destination databases.</li></ul>
<div class="note" id="drs_04_0100__note24468148125"><span class="notetitle"> NOTE: </span><div class="notebody"><p id="drs_04_0100__p3446214131219">If you select <span class="uicontrol" id="drs_04_0100__uicontrol08701615124515"><b>Full+Incremental</b></span>, data generated during the full migration will be continuously synchronized to the destination database, and the source remains accessible.</p>
</div></div>
</td>
</tr>
</tbody>
</table>
</div>
</li></ul>
<div class="note" id="drs_04_0100__note5776816295"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="drs_04_0100__drs_04_0088_p96226362518">If a task fails to be created, DRS retains the task for three days by default. After three days, the task automatically ends.</p>
</div></div>
</p></li><li id="drs_04_0100__li4138496142747"><span>On the <span class="uicontrol" id="drs_04_0100__uicontrol488224453717"><b>Configure Source and Destination Databases</b></span> page, wait until the replication instance is created. Then, specify source and destination database information and click <span class="uicontrol" id="drs_04_0100__uicontrol8882644153717"><b>Test Connection</b></span> for both the source and destination databases to check whether they have been connected to the replication instance. After the connection tests are successful, select the check box before the agreement and click <span class="uicontrol" id="drs_04_0100__uicontrol19882134483717"><b>Next</b></span>.</span><p>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="drs_04_0100__table1289965016299" frame="border" border="1" rules="all"><caption><b>Table 6 </b>Source database settings</caption><thead align="left"><tr id="drs_04_0100__row1689805018297"><th align="left" class="cellrowborder" valign="top" width="23%" id="mcps1.3.6.3.3.2.1.2.3.1.1"><p id="drs_04_0100__p10898145014294">Parameter</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="77%" id="mcps1.3.6.3.3.2.1.2.3.1.2"><p id="drs_04_0100__p1789812506295">Description</p>
</th>
</tr>
</thead>
<tbody><tr id="drs_04_0100__row1189815082911"><td class="cellrowborder" valign="top" width="23%" headers="mcps1.3.6.3.3.2.1.2.3.1.1 "><p id="drs_04_0100__p16898125022917">DB Instance Name</p>
</td>
<td class="cellrowborder" valign="top" width="77%" headers="mcps1.3.6.3.3.2.1.2.3.1.2 "><p id="drs_04_0100__p38989501298">The RDS DB instance selected during migration task creation. This parameter cannot be changed.</p>
</td>
</tr>
<tr id="drs_04_0100__row3898165072918"><td class="cellrowborder" valign="top" width="23%" headers="mcps1.3.6.3.3.2.1.2.3.1.1 "><p id="drs_04_0100__p1589805012291">Database Username</p>
</td>
<td class="cellrowborder" valign="top" width="77%" headers="mcps1.3.6.3.3.2.1.2.3.1.2 "><p id="drs_04_0100__p2898650102913">Enter the username of the source database.</p>
</td>
</tr>
<tr id="drs_04_0100__row208991850122919"><td class="cellrowborder" valign="top" width="23%" headers="mcps1.3.6.3.3.2.1.2.3.1.1 "><p id="drs_04_0100__p10899850182916">Database Password</p>
</td>
<td class="cellrowborder" valign="top" width="77%" headers="mcps1.3.6.3.3.2.1.2.3.1.2 "><p id="drs_04_0100__p2320944105918">The password for the database username.</p>
<p id="drs_04_0100__p1320104405914">If the task is in the <strong id="drs_04_0100__b14116905055620">Starting</strong>, <strong id="drs_04_0100__b184684388755620">Full migration</strong>, <strong id="drs_04_0100__b134320520555620">Incremental migration</strong>, or <strong id="drs_04_0100__b54433457755620">Incremental migration failed</strong> status, in the <strong id="drs_04_0100__b201849693255620">Migration Information</strong> area on the <strong id="drs_04_0100__b85346832355620">Basic Information</strong> page, click <strong id="drs_04_0100__b52891255455620">Update Password</strong> next to the <strong id="drs_04_0100__b81891321755620">Source Database Password</strong> field. In the displayed dialog box, change the password. This action only updates DRS with the changed password.</p>
</td>
</tr>
</tbody>
</table>
</div>
<div class="note" id="drs_04_0100__note16757973536"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="drs_04_0100__p575713713532">The username and password of the source database are encrypted and stored in the database and the replication instance during the migration. After the task is deleted, the username and password are permanently deleted.</p>
</div></div>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="drs_04_0100__table8902125032918" frame="border" border="1" rules="all"><caption><b>Table 7 </b>Destination database settings</caption><thead align="left"><tr id="drs_04_0100__row1790025018293"><th align="left" class="cellrowborder" valign="top" width="23.29%" id="mcps1.3.6.3.3.2.3.2.3.1.1"><p id="drs_04_0100__p1889911501294">Parameter</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="76.71%" id="mcps1.3.6.3.3.2.3.2.3.1.2"><p id="drs_04_0100__p189965082912">Description</p>
</th>
</tr>
</thead>
<tbody><tr id="drs_04_0100__row39001750142919"><td class="cellrowborder" valign="top" width="23.29%" headers="mcps1.3.6.3.3.2.3.2.3.1.1 "><p id="drs_04_0100__p39007509297">VPC</p>
</td>
<td class="cellrowborder" valign="top" width="76.71%" headers="mcps1.3.6.3.3.2.3.2.3.1.2 "><p id="drs_04_0100__p490095016294">A dedicated virtual network in which the destination database is located. It isolates networks for different services.</p>
</td>
</tr>
<tr id="drs_04_0100__row49001650142920"><td class="cellrowborder" valign="top" width="23.29%" headers="mcps1.3.6.3.3.2.3.2.3.1.1 "><p id="drs_04_0100__p1190075018294">Subnet</p>
</td>
<td class="cellrowborder" valign="top" width="76.71%" headers="mcps1.3.6.3.3.2.3.2.3.1.2 "><p id="drs_04_0100__p14900125022911">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.</p>
</td>
</tr>
<tr id="drs_04_0100__row6901195032913"><td class="cellrowborder" valign="top" width="23.29%" headers="mcps1.3.6.3.3.2.3.2.3.1.1 "><p id="drs_04_0100__p1190013502293">IP Address or Domain Name</p>
</td>
<td class="cellrowborder" valign="top" width="76.71%" headers="mcps1.3.6.3.3.2.3.2.3.1.2 "><p id="drs_04_0100__p139002050172919">Enter the IP address or domain name of the destination database.</p>
</td>
</tr>
<tr id="drs_04_0100__row20901115002915"><td class="cellrowborder" valign="top" width="23.29%" headers="mcps1.3.6.3.3.2.3.2.3.1.1 "><p id="drs_04_0100__p15901125011299">Port</p>
</td>
<td class="cellrowborder" valign="top" width="76.71%" headers="mcps1.3.6.3.3.2.3.2.3.1.2 "><p id="drs_04_0100__p790195012914">The port of the destination database. Range: 1 - 65535</p>
</td>
</tr>
<tr id="drs_04_0100__row16901155042918"><td class="cellrowborder" valign="top" width="23.29%" headers="mcps1.3.6.3.3.2.3.2.3.1.1 "><p id="drs_04_0100__p20901150152913">Database Username</p>
</td>
<td class="cellrowborder" valign="top" width="76.71%" headers="mcps1.3.6.3.3.2.3.2.3.1.2 "><p id="drs_04_0100__p13901350122917">The username for accessing the destination database.</p>
</td>
</tr>
<tr id="drs_04_0100__row5901195012912"><td class="cellrowborder" valign="top" width="23.29%" headers="mcps1.3.6.3.3.2.3.2.3.1.1 "><p id="drs_04_0100__p18901850152916">Database Password</p>
</td>
<td class="cellrowborder" valign="top" width="76.71%" headers="mcps1.3.6.3.3.2.3.2.3.1.2 "><p id="drs_04_0100__p6901155012296">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:</p>
<p id="drs_04_0100__p1266014514718">If the task is in the <strong id="drs_04_0100__b23952983855620">Starting</strong>, <strong id="drs_04_0100__b142130549155620">Full migration</strong>, <strong id="drs_04_0100__b15012510555620">Incremental migration</strong>, or <strong id="drs_04_0100__b92570282755620">Incremental migration failed</strong> status, in the <strong id="drs_04_0100__b23761273555620">Migration Information</strong> area on the <strong id="drs_04_0100__b164035023155620">Basic Information</strong> page, click <strong id="drs_04_0100__b208848874855620">Update Password</strong> next to the <strong id="drs_04_0100__b59326317855620">Destination Database Password</strong> field. In the displayed dialog box, change the password. This action only updates DRS with the changed password.</p>
</td>
</tr>
<tr id="drs_04_0100__row8901105010294"><td class="cellrowborder" valign="top" width="23.29%" headers="mcps1.3.6.3.3.2.3.2.3.1.1 "><p id="drs_04_0100__p190145082911">SSL Connection</p>
</td>
<td class="cellrowborder" valign="top" width="76.71%" headers="mcps1.3.6.3.3.2.3.2.3.1.2 "><p id="drs_04_0100__p1790120506297">SSL encrypts the connections between the source and destination databases. If SSL is enabled, upload the SSL CA root certificate.</p>
<div class="note" id="drs_04_0100__note20901150112914"><span class="notetitle"> NOTE: </span><div class="notebody"><ul id="drs_04_0100__ul6901750142918"><li id="drs_04_0100__li1090105018290">The maximum size of a single certificate file that can be uploaded is 500 KB.</li><li id="drs_04_0100__li99012501296">If the SSL certificate is not used, your data may be at risk.</li></ul>
</div></div>
</td>
</tr>
<tr id="drs_04_0100__row1902125002914"><td class="cellrowborder" valign="top" width="23.29%" headers="mcps1.3.6.3.3.2.3.2.3.1.1 "><p id="drs_04_0100__p1690114501294">Migrate Definer to User</p>
</td>
<td class="cellrowborder" valign="top" width="76.71%" headers="mcps1.3.6.3.3.2.3.2.3.1.2 "><ul id="drs_04_0100__ul177872795310"><li id="drs_04_0100__li13778202785311"><strong id="drs_04_0100__b8256210350">Yes</strong><p id="drs_04_0100__p1451713113499">The Definers of all source database objects will be migrated to the user. Other users do not have permissions for database objects unless these users are authorized. For details on authorization, see <a href="drs_16_0003.html">How Do I Maintain the Original Service User Permission System After Definer Is Forcibly Converted During MySQL Migration?</a></p>
</li><li id="drs_04_0100__li277962735319"><strong id="drs_04_0100__b0794754153411">No</strong><p id="drs_04_0100__p4779202745318">The Definers of all source database objects will not be changed. You need to migrate all accounts and permissions of the source database in the next step.</p>
</li></ul>
</td>
</tr>
</tbody>
</table>
</div>
<div class="note" id="drs_04_0100__note159021550162918"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="drs_04_0100__p91391921102311">The IP address, port, username, and password of the destination database are encrypted and stored in the database and the replication instance, and will be cleared after the task is deleted.</p>
</div></div>
</p></li><li id="drs_04_0100__li5256421162420"><span>On the <span class="uicontrol" id="drs_04_0100__uicontrol57278214255620"><b>Set Task</b></span> page, set migration accounts and objects, and click <strong id="drs_04_0100__b42160535755620">Next</strong>.</span><p>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="drs_04_0100__en-us_topic_0078078071_table165921932111919" frame="border" border="1" rules="all"><caption><b>Table 8 </b>Migration types and objects</caption><thead align="left"><tr id="drs_04_0100__en-us_topic_0078078071_row165921632141911"><th align="left" class="cellrowborder" valign="top" width="16.1%" id="mcps1.3.6.3.4.2.1.2.3.1.1"><p id="drs_04_0100__en-us_topic_0078078071_p1759233261916">Parameter</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="83.89999999999999%" id="mcps1.3.6.3.4.2.1.2.3.1.2"><p id="drs_04_0100__en-us_topic_0078078071_p159273271920">Description</p>
</th>
</tr>
</thead>
<tbody><tr id="drs_04_0100__row829913579409"><td class="cellrowborder" valign="top" width="16.1%" headers="mcps1.3.6.3.4.2.1.2.3.1.1 "><p id="drs_04_0100__p172891713429">Flow Control</p>
</td>
<td class="cellrowborder" valign="top" width="83.89999999999999%" headers="mcps1.3.6.3.4.2.1.2.3.1.2 "><p id="drs_04_0100__p6265105163918">You can choose whether to control the flow.</p>
<ul id="drs_04_0100__ul142651151123918"><li id="drs_04_0100__drs_04_0088_li3265651133915"><strong id="drs_04_0100__drs_04_0088_b241213492720">Yes</strong><p id="drs_04_0100__drs_04_0088_p1026565110390">You can customize the maximum migration speed.</p>
<p id="drs_04_0100__drs_04_0088_p9266851103914">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 <strong id="drs_04_0100__drs_04_0088_b18787830374">All day</strong>. A maximum of three time ranges can be set, and they cannot overlap.</p>
<p id="drs_04_0100__drs_04_0088_p1826625163912">The flow rate must be set based on the service scenario and cannot exceed 9,999 MB/s.</p>
</li><li id="drs_04_0100__drs_04_0088_li1626685110394"><strong id="drs_04_0100__drs_04_0088_b48151782720">No</strong><div class="p" id="drs_04_0100__drs_04_0088_p112664518395">The migration 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.<div class="note" id="drs_04_0100__drs_04_0088_note1426618512396"><span class="notetitle"> NOTE: </span><div class="notebody"><ul id="drs_04_0100__drs_04_0088_ul4267135143911"><li id="drs_04_0100__drs_04_0088_li16267105123915">Flow control mode takes effect only during a full migration.</li><li id="drs_04_0100__drs_04_0088_li726765183919">You can also change the flow control mode after creating a task. For details, see <a href="drs_03_0046.html">Modifying the Flow Control Mode</a>.</li></ul>
</div></div>
</div>
</li></ul>
</td>
</tr>
<tr id="drs_04_0100__row16154113519117"><td class="cellrowborder" valign="top" width="16.1%" headers="mcps1.3.6.3.4.2.1.2.3.1.1 "><p id="drs_04_0100__p0476133152016">Filter DROP DATABASE</p>
</td>
<td class="cellrowborder" valign="top" width="83.89999999999999%" headers="mcps1.3.6.3.4.2.1.2.3.1.2 "><p id="drs_04_0100__p137371904213">During an incremental migration, executing DDL operations on the source database may affect the data migration performance to some extent. To reduce data migration risks, DRS allows you to filter out DDL operations.</p>
<p id="drs_04_0100__p1820615910137">The database deletion operation can be filtered out by default.</p>
<ul id="drs_04_0100__ul611316391419"><li id="drs_04_0100__li666251201417">If you select <strong id="drs_04_0100__b163658384755620">Yes</strong>, any database deletion operations performed on the source database are not synchronized during data migration.</li><li id="drs_04_0100__li10113133191414">If you select <strong id="drs_04_0100__b66067901455620">No</strong>, related operations are synchronized to the destination database during data migration.<div class="note" id="drs_04_0100__en-us_topic_0135097933_en-us_topic_0078078071_note8823203716512"><span class="notetitle"> NOTE: </span><div class="notebody"><p id="drs_04_0100__en-us_topic_0135097933_p48942034155220">Currently, only the full plus incremental migrations from RDS MySQL to MySQL are supported.</p>
</div></div>
</li></ul>
</td>
</tr>
<tr id="drs_04_0100__en-us_topic_0078078071_row2592193212194"><td class="cellrowborder" valign="top" width="16.1%" headers="mcps1.3.6.3.4.2.1.2.3.1.1 "><p id="drs_04_0100__en-us_topic_0078078071_p7592232201911">Migrate Account</p>
</td>
<td class="cellrowborder" valign="top" width="83.89999999999999%" headers="mcps1.3.6.3.4.2.1.2.3.1.2 "><p id="drs_04_0100__p11670239171013">During a database migration, accounts need to be migrated separately.</p>
<div class="p" id="drs_04_0100__p106411111205412">There are accounts that can be migrated completely, accounts whose permissions need to be reduced, and accounts that cannot be migrated. You can choose whether to migrate the accounts based on service requirements.<ul id="drs_04_0100__ul52489455107"><li id="drs_04_0100__li52487450107"><strong id="drs_04_0100__b414892110107">Yes</strong><p id="drs_04_0100__p1299113715370">If you need to migrate accounts, see <a href="drs_09_0017.html">Migrating Accounts</a>.</p>
</li></ul>
</div>
<ul id="drs_04_0100__ul4685852174011"><li id="drs_04_0100__li0685352164019"><strong id="drs_04_0100__b1245955861016">No</strong><p id="drs_04_0100__p18685145210400">During the migration, accounts, permissions, and passwords are not migrated.</p>
</li></ul>
</td>
</tr>
<tr id="drs_04_0100__en-us_topic_0078078071_row559273214193"><td class="cellrowborder" valign="top" width="16.1%" headers="mcps1.3.6.3.4.2.1.2.3.1.1 "><p id="drs_04_0100__en-us_topic_0078078071_p14592132171916">Migrate Object</p>
</td>
<td class="cellrowborder" valign="top" width="83.89999999999999%" headers="mcps1.3.6.3.4.2.1.2.3.1.2 "><p id="drs_04_0100__en-us_topic_0135097933_en-us_topic_0078078071_p1384592151414">You can choose to migrate all objects, tables, or databases based on your service requirements.</p>
<ul id="drs_04_0100__en-us_topic_0135097933_en-us_topic_0078078071_ul78601316141810"><li id="drs_04_0100__en-us_topic_0135097933_en-us_topic_0078078071_li1486001601818"><strong id="drs_04_0100__b1437618103812">All</strong>: All objects in the source database are migrated to the destination database. After the migration, the object names will remain the same as those in the source database and cannot be modified.</li><li id="drs_04_0100__en-us_topic_0135097933_li156818580599"><strong id="drs_04_0100__b14439158381">Tables</strong>: The selected table-level objects will be migrated.</li><li id="drs_04_0100__en-us_topic_0135097933_li165086239593"><strong id="drs_04_0100__b21461518123810">Databases</strong>: The selected database-level objects will be migrated.</li></ul>
<p id="drs_04_0100__en-us_topic_0135097933_p759715540459">If the source database is changed, click <span><img id="drs_04_0100__en-us_topic_0135097933_image959917843110" src="en-us_image_0000001341094436.png"></span> in the upper right corner before selecting migration objects to ensure that the objects to be selected are from the changed source database.</p>
<div class="note" id="drs_04_0100__note127225415467"><span class="notetitle"> NOTE: </span><div class="notebody"><ul id="drs_04_0100__drs_04_0088_en-us_topic_0135097933_ul19601624657"><li id="drs_04_0100__drs_04_0088_en-us_topic_0135097933_li1960112416510">If you choose not to migrate all of the databases, the migration may fail because the objects, such as stored procedures and views, in the databases to be migrated may have dependencies on other objects that are not migrated. To prevent migration failure, migrate all of the databases.</li><li id="drs_04_0100__drs_04_0088_li1650961216398">If the object name contains spaces, the spaces before and after the object name are not displayed. If there are multiple spaces between the object name and the object name, only one space is displayed.</li><li id="drs_04_0100__drs_04_0088_li95123124391">The name of the selected migration object cannot contain spaces.</li><li id="drs_04_0100__drs_04_0088_en-us_topic_0135097933_li01376524218">To quickly select the desired database objects, you can use the search function.</li></ul>
</div></div>
</td>
</tr>
</tbody>
</table>
</div>
</p></li><li id="drs_04_0100__li3038258151520"><span>On the <span class="uicontrol" id="drs_04_0100__drs_04_0088_uicontrol497752321414"><b>Check Task</b></span> page, check the migration task.</span><p><ul id="drs_04_0100__drs_04_0088_ul14147195310462"><li id="drs_04_0100__drs_04_0088_li12147653194618">If any check fails, review the cause and rectify the fault. After the fault is rectified, click <strong id="drs_04_0100__drs_04_0088_b152762027181410">Check Again</strong>.<p id="drs_04_0100__drs_04_0088_p51471553104615">For details about how to handle check items that fail to pass the pre-check, see <a href="drs_11_0001.html">Solutions to Failed Check Items</a>.</p>
</li></ul>
<ul id="drs_04_0100__drs_04_0088_ul1414805314617"><li id="drs_04_0100__drs_04_0088_li214845364613">If the check is complete and the check success rate is 100%, click <span class="uicontrol" id="drs_04_0100__drs_04_0088_uicontrol189181752191711"><b>Next</b></span>.<div class="note" id="drs_04_0100__drs_04_0088_note1114835319465"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="drs_04_0100__drs_04_0088_p1414815531460">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_0100__li13665155542813"><span>On the displayed page, specify <strong id="drs_04_0100__drs_04_0088_b13281317141218">Start Time</strong> and confirm that the configured information is correct and click <strong id="drs_04_0100__drs_04_0088_b102831640121316">Submit</strong> to submit the task.</span><p>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="drs_04_0100__drs_04_0088_table179101030984" frame="border" border="1" rules="all"><caption><b>Table 9 </b>Task startup settings</caption><thead align="left"><tr id="drs_04_0100__drs_04_0088_row1391043015814"><th align="left" class="cellrowborder" valign="top" width="18.42%" id="mcps1.3.6.3.6.2.1.2.3.1.1"><p id="drs_04_0100__drs_04_0088_p1391015304812">Parameter</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="81.58%" id="mcps1.3.6.3.6.2.1.2.3.1.2"><p id="drs_04_0100__drs_04_0088_p1911203019815">Description</p>
</th>
</tr>
</thead>
<tbody><tr id="drs_04_0100__drs_04_0088_row2091163011811"><td class="cellrowborder" valign="top" width="18.42%" headers="mcps1.3.6.3.6.2.1.2.3.1.1 "><p id="drs_04_0100__drs_04_0088_p129112301888">Started Time</p>
</td>
<td class="cellrowborder" valign="top" width="81.58%" headers="mcps1.3.6.3.6.2.1.2.3.1.2 "><p id="drs_04_0100__drs_04_0088_p2471555115">Set <strong id="drs_04_0100__drs_04_0088_b7427427153">Start Time</strong> to <strong id="drs_04_0100__drs_04_0088_b15428152716513">Start upon task creation</strong> or <strong id="drs_04_0100__drs_04_0088_b242919276510">Start at a specified time</strong> based on site requirements. The <strong id="drs_04_0100__drs_04_0088_b786524410472">Start at a specified time</strong> option is recommended.</p>
<div class="note" id="drs_04_0100__drs_04_0088_note139210501215"><span class="notetitle"> NOTE: </span><div class="notebody"><p id="drs_04_0100__drs_04_0088_p347165513114">The migration task may affect the performance of the source and destination databases. You are advised to start the task in off-peak hours and reserve two to three days for data verification.</p>
</div></div>
</td>
</tr>
</tbody>
</table>
</div>
</p></li><li id="drs_04_0100__li44061116144511"><span>After the task is submitted, view and manage it on the <span class="uicontrol" id="drs_04_0100__drs_04_0088_en-us_topic_0135097933_en-us_topic_0078078071_uicontrol2841808711922"><b>Online Migration Management</b></span> page.</span><p><ul id="drs_04_0100__drs_04_0088_en-us_topic_0135097933_en-us_topic_0078078071_ul46880011174414"><li id="drs_04_0100__drs_04_0088_li155061840145018">You can view the task status. For more information about task status, see <a href="drs_03_0001.html">Task Statuses</a>.</li><li id="drs_04_0100__drs_04_0088_en-us_topic_0135097933_en-us_topic_0078078071_li56201830174851">You can click <span><img id="drs_04_0100__drs_04_0088_image9514202614340" src="en-us_image_0000001391694113.png"></span> in the upper right corner to view the latest task status.</li></ul>
</p></li></ol>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="drs_02_0031.html">Out of the Cloud</a></div>
</div>
</div>