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

DCS UMN 20240705 version

Browse Source 
Reviewed-by: Mützel, Andrea <andrea.muetzel@t-systems.com>
Co-authored-by: chenjunjie <chenjunjie@huawei.com>
Co-committed-by: chenjunjie <chenjunjie@huawei.com>
This commit is contained in:
Chen, Junjie
2025-02-26 10:24:22 +00:00
committed by zuul
parent 843c771689
commit ab5f2db011
202 changed files with 10686 additions and 5075 deletions
Download Patch File Download Diff File Expand all files Collapse all files

65
docs/dcs/umn/dcs-migration-190703003.html
View File

@ -1,62 +1,61 @@
<a name="dcs-migration-190703003"></a><a name="dcs-migration-190703003"></a>
<h1 class="topictitle1">Online Migration of Self-Hosted Redis</h1>
<div id="body1562138749036"><div class="section" id="dcs-migration-190703003__section113421435300"><h4 class="sectiontitle">Application Scenarios</h4><p id="dcs-migration-190703003__p1244713381103">If the source and target instances are interconnected and the <strong id="dcs-migration-190703003__b18112161719418">SYNC</strong> and <strong id="dcs-migration-190703003__b01122172041">PSYNC</strong> commands are supported by the source instance, data can be migrated online in full or incrementally from the source to the target.</p>
<div class="caution" id="dcs-migration-190703003__note8576142111415"><span class="cautiontitle"><img src="public_sys-resources/caution_3.0-en-us.png"> </span><div class="cautionbody"><ul id="dcs-migration-190703003__ul12488164523510"><li id="dcs-migration-190703003__li3488545193514">If the <strong id="dcs-migration-190703003__b18144137133010">SYNC</strong> and <strong id="dcs-migration-190703003__b11144475309">PSYNC</strong> commands are disabled on the source Redis instance, enable them before performing online migration. Otherwise, the migration fails. If you use a DCS Redis instance for online migration, the <strong id="dcs-migration-190703003__b814416793016">SYNC</strong> command is automatically enabled.</li><li id="dcs-migration-190703003__li10440349183519">You cannot use public networks for online migration.</li><li id="dcs-migration-190703003__li14846184712514">During online migration, you are advised to set <strong id="dcs-migration-190703003__b9548141910176">repl-timeout</strong> on the source instance to 300s and <strong id="dcs-migration-190703003__b16885030121716">client-output-buffer-limit</strong> to 20% of the maximum memory of the instance.</li><li id="dcs-migration-190703003__li665420105315">The source must be Redis 3.0 or later.</li></ul>
<h1 class="topictitle1">Migrating Self-Built Redis Online</h1>
<div id="body1562138749036"><p id="dcs-migration-190703003__p1244713381103">If the source self-host and target instances are interconnected and the <strong id="dcs-migration-190703003__b18112161719418">SYNC</strong> and <strong id="dcs-migration-190703003__b01122172041">PSYNC</strong> commands are supported by the source instance, data can be migrated online in full or incrementally from the source to the target DCS.</p>
<div class="note" id="dcs-migration-190703003__note163110283525"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="dcs-migration-190703003__p4701259102114">During online migration, data is essentially synchronized in full to a new replica. Therefore, perform online migration during low-demand hours. Otherwise, source instance CPU usage may surge and latency may increase.</p>
</div></div>
<div class="section" id="dcs-migration-190703003__section77251317153217"><h4 class="sectiontitle">Notes and Constraints</h4><ul id="dcs-migration-190703003__ul14396317163019"><li id="dcs-migration-190703003__li1657415321689">If the <strong id="dcs-migration-190703003__b1255891994619">SYNC</strong> and <strong id="dcs-migration-190703003__b655815190465">PSYNC</strong> commands are disabled by the source instance, enable them before migrating data. Otherwise, the migration fails.</li><li id="dcs-migration-190703003__li15396117163010">You cannot use public networks for online migration.</li><li id="dcs-migration-190703003__li03966171308">During online migration, you are advised to set <strong id="dcs-migration-190703003__en-us_topic_0292880550_dcs-migration-190703003_b9548141910176">repl-timeout</strong> on the source instance to 300s and <strong id="dcs-migration-190703003__en-us_topic_0292880550_dcs-migration-190703003_b16885030121716">client-output-buffer-slave-hard-limit</strong> and <strong id="dcs-migration-190703003__b143014479573">client-output-buffer-slave-soft-limit</strong> to 20% of the maximum memory of the source instance.</li><li id="dcs-migration-190703003__li13961317153011">The source must be Redis 3.0 or later.</li><li id="dcs-migration-190703003__li18051932613">For earlier instances whose passwords contain single quotation marks ('), modify the password for online migration or try other methods.</li><li id="dcs-migration-190703003__li773103010264">To migrate to an instance with SSL enabled, disable the SSL setting first. For details, see <a href="dcs-ug-023129.html">Transmitting DCS Redis Data with Encryption Using SSL</a>.</li></ul>
</div>
<div class="section" id="dcs-migration-190703003__section77251317153217"><h4 class="sectiontitle">Impacts on Services</h4><p id="dcs-migration-190703003__p5721132883218">During online migration, data is essentially synchronized in full to a new replica. Therefore, perform online migration during low-demand hours.</p>
<div class="section" id="dcs-migration-190703003__section15790816165711"><h4 class="sectiontitle">Prerequisites</h4><ul id="dcs-migration-190703003__ul56215114194"><li id="dcs-migration-190703003__li963201191917">Before migrating data, read through <a href="dcs-migration-090626002.html">Migration Tools and Schemes</a> to learn about the DCS data migration function and select an appropriate target instance.</li><li id="dcs-migration-190703003__li2988793125">By default, a cluster instance has only one DB (DB0). Before you migrate data from a multi-DB single-node or master/standby instance to a Redis Cluster instance, check whether any data exists on databases other than DB0. To ensure that the migration succeeds, move all data to DB0 by referring to <a href="dcs-migration-090626001_0.html">Online Migration with Rump</a>.</li><li id="dcs-migration-190703003__li139861312152218">The IP address and port of the source Redis instance has been obtained.</li><li id="dcs-migration-190703003__li1527810451382">If a target DCS Redis instance is not available, create one first. For details, see <a href="dcs-ug-0312003.html">Creating a DCS Redis Instance</a>.</li><li id="dcs-migration-190703003__li5270324091">If you already have a DCS Redis instance, you do not need to create one again. For comparing migration data and reserving sufficient memory, you are advised to clear the instance data before the migration. For details, see <a href="dcs-ug-0312018.html">Clearing DCS Instance Data</a>. If any data exists on the target instance, duplicate data between the source and target is overwritten. If the data exists only on the target instance, the data will be retained.</li></ul>
</div>
<div class="section" id="dcs-migration-190703003__section15790816165711"><h4 class="sectiontitle">Prerequisites</h4><ul id="dcs-migration-190703003__ul56215114194"><li id="dcs-migration-190703003__li963201191917">Before migrating data, read through <a href="dcs-migration-090626002.html">Migration Tools and Schemes</a> to learn about the DCS data migration function and select an appropriate target instance.</li><li id="dcs-migration-190703003__li2988793125">By default, a cluster instance has only one DB (DB0). Before you migrate data from a multi-DB single-node or master/standby instance to a Redis Cluster instance, check whether any data exists on databases other than DB0. To ensure that the migration succeeds, move all data to DB0 by referring to <a href="dcs-migration-090626001_0.html">Online Migration with Rump</a>.</li></ul>
</div>
<div class="section" id="dcs-migration-190703003__section760319488490"><h4 class="sectiontitle">Step 1: Obtain the Source Redis Address</h4><p id="dcs-migration-190703003__p136671818181819">Obtain the IP address/domain name and port number of the source Redis instance.</p>
</div>
<div class="section" id="dcs-migration-190703003__section1128152020384"><h4 class="sectiontitle">Step 2: Prepare the Target DCS Redis Instance</h4><ul id="dcs-migration-190703003__ul727834515383"><li id="dcs-migration-190703003__li1527810451382">If a target DCS Redis instance is not available, create one first. For details, see <a href="dcs-ug-0312003.html">Creating a DCS Redis Instance</a>.</li><li id="dcs-migration-190703003__li5270324091">If you already have a DCS Redis instance, you do not need to create one again, but you need to clear the instance data before the migration. For details, see <a href="dcs-ug-0312018.html">Clearing DCS Instance Data</a>.<p id="dcs-migration-190703003__p49291961936">If the target instance data is not cleared before the migration and the source and target instances contain the same key, the key in the target instance will be overwritten by the key in the source instance after the migration.</p>
</li></ul>
</div>
<div class="section" id="dcs-migration-190703003__section84284075116"><h4 class="sectiontitle">Step 3: Check the Network</h4><ol id="dcs-migration-190703003__ol1260417035216"><li id="dcs-migration-190703003__li16049019525"><span>Check whether the source Redis instance, the target Redis instance, and the migration task are configured with the same VPC.</span><p><p id="dcs-migration-190703003__p188021330165115">If yes, go to <a href="#dcs-migration-190703003__section157769524519">Step 4: Create an Online Migration Task</a>. If no, go to <a href="#dcs-migration-190703003__li160420185217">2</a>.</p>
</p></li><li id="dcs-migration-190703003__li160420185217"><a name="dcs-migration-190703003__li160420185217"></a><a name="li160420185217"></a><span>Check whether the VPCs configured for the source Redis instance, the target Redis instance, and the migration task are connected to ensure that the VM resource of the migration task can access the source and target Redis instances.</span><p><p id="dcs-migration-190703003__p1480253095111">If yes, go to <a href="#dcs-migration-190703003__section157769524519">Step 4: Create an Online Migration Task</a>. If no, go to <a href="#dcs-migration-190703003__li423483319412">3</a>.</p>
</p></li><li id="dcs-migration-190703003__li423483319412"><a name="dcs-migration-190703003__li423483319412"></a><a name="li423483319412"></a><span>Perform the following operations to establish the network.</span><p><ul id="dcs-migration-190703003__ul17325432414"><li id="dcs-migration-190703003__li7271615152516">If the source and target Redis instances are <span id="dcs-migration-190703003__ph749662795514">in the same DCS region</span>, create a VPC peering connection by referring to "VPC Peering Connection" in the <em id="dcs-migration-190703003__i4602173825519">Virtual Private Cloud User Guide</em>.</li><li id="dcs-migration-190703003__li1073215431842">If the source and target Redis instances are on different clouds or in different regions, create a connection by referring to the <em id="dcs-migration-190703003__i22974405618">Direct Connect User Guide</em>.</li></ul>
</p></li></ol>
</div>
<div class="section" id="dcs-migration-190703003__section157769524519"><a name="dcs-migration-190703003__section157769524519"></a><a name="section157769524519"></a><h4 class="sectiontitle">Step 4: Create an Online Migration Task</h4><ol id="dcs-migration-190703003__ol81391154144716"><li id="dcs-migration-190703003__li390016374490"><span>Log in to the DCS console.</span></li><li id="dcs-migration-190703003__li16119587498"><span>In the navigation pane, choose <strong id="dcs-migration-190703003__b11427641642634">Data Migration</strong>.</span></li><li id="dcs-migration-190703003__li67372014165120"><span>Click <strong id="dcs-migration-190703003__b61157650142634">Create Online Migration Task</strong>.</span></li><li id="dcs-migration-190703003__li1381824764611"><span>Enter the task name and description.</span></li><li id="dcs-migration-190703003__li114411588467"><span>Configure the VPC, subnet, and security group for the migration task.</span><p><p id="dcs-migration-190703003__p473111475510">The VPC, subnet, and security group facilitate the migration. Ensure that the migration resources can access the source and target Redis instances.</p>
<div class="note" id="dcs-migration-190703003__note8226825195811"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="dcs-migration-190703003__ul12308184119132"><li id="dcs-migration-190703003__li13308204111130">The online migration task uses a tenant IP address (<strong id="dcs-migration-190703003__b197811218123710">Migration ECS</strong> displayed on the <strong id="dcs-migration-190703003__b167811718103719">Basic Information</strong> page of the task.) If a whitelist is configured for the source or target instance, add the migration IP address to the whitelist or disable the whitelist.</li><li id="dcs-migration-190703003__li18308441171318">To allow the VM used by the migration task to access the source and target instances, set an outbound rule for the task's security group to allow traffic through the IP addresses and ports of the source and target instances. By default, all outbound traffic is allowed.</li></ul>
<div class="section" id="dcs-migration-190703003__section157769524519"><a name="dcs-migration-190703003__section157769524519"></a><a name="section157769524519"></a><h4 class="sectiontitle">Creating an Online Migration Task</h4><ol id="dcs-migration-190703003__ol81391154144716"><li id="dcs-migration-190703003__li390016374490"><span>Log in to the DCS console using the account of the target DCS Redis instance.</span></li><li id="dcs-migration-190703003__li1830151005519"><span>Click <span><img id="dcs-migration-190703003__image07790385177" src="en-us_image_0143929918.png"></span> in the upper left corner of the console and select the region where your target instance is located.</span></li><li id="dcs-migration-190703003__li16119587498"><span>In the navigation pane, choose <strong id="dcs-migration-190703003__en-us_topic_0292880550_dcs-migration-190703003_b11427641642634">Data Migration</strong>.</span></li><li id="dcs-migration-190703003__li67372014165120"><span>Click <strong id="dcs-migration-190703003__b61157650142634">Create Online Migration Task</strong>.</span></li><li id="dcs-migration-190703003__li1381824764611"><span>Enter the task name and description.</span><p><p id="dcs-migration-190703003__p15524526705">The task name must start with a letter, contain 4 to 64 characters, and contain only letters, digits, hyphens (-), and underscores (_).</p>
</p></li><li id="dcs-migration-190703003__li114411588467"><span>Configure the VPC, subnet, and security group for the migration task.</span><p><div class="note" id="dcs-migration-190703003__note8226825195811"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="dcs-migration-190703003__ul12308184119132"><li id="dcs-migration-190703003__li1539920123575"><strong id="dcs-migration-190703003__b10615958205517">Select the same VPC as the target Redis. Ensure that the migration resource can access the target Redis instance.</strong></li><li id="dcs-migration-190703003__li13308204111130">The online migration task uses a tenant IP address (<strong id="dcs-migration-190703003__en-us_topic_0292880550_dcs-migration-190703003_b197811218123710">Migration ECS</strong> displayed on the <strong id="dcs-migration-190703003__en-us_topic_0292880550_dcs-migration-190703003_b167811718103719">Basic Information</strong> page of the task.) If a whitelist is configured for the source or target instance, add the migration IP address to the whitelist or disable the whitelist.</li><li id="dcs-migration-190703003__li18308441171318">To allow the VM used by the migration task to access the source and target instances, set an outbound rule for the task's security group to allow traffic through the IP addresses and ports of the source and target instances. By default, all outbound traffic is allowed.</li></ul>
</div></div>
</p></li></ol>
</div>
<div class="section" id="dcs-migration-190703003__section14919536272"><h4 class="sectiontitle">Step 5: Configure the Online Migration Task</h4><ol id="dcs-migration-190703003__ol20242048298"><li id="dcs-migration-190703003__li187884091914"><span>On the <strong id="dcs-migration-190703003__b8239202416317">Online Migration</strong> tab page, click <strong id="dcs-migration-190703003__b983115204312">Configure</strong> in the row containing the online migration task you just created.</span></li><li id="dcs-migration-190703003__li18777171715209"><span>Select a migration type.</span><p><p id="dcs-migration-190703003__p72342811211">Supported migration types are <strong id="dcs-migration-190703003__b7961135591712">Full</strong> and <strong id="dcs-migration-190703003__b1096125531711">Full + Incremental</strong>, which are described in <a href="#dcs-migration-190703003__table55653322215">Table 1</a>.</p>
<div class="section" id="dcs-migration-190703003__section117920569559"><h4 class="sectiontitle">Checking the Network</h4><ol id="dcs-migration-190703003__ol1260417035216"><li id="dcs-migration-190703003__li16049019525"><span>Check whether the source Redis instance, the target Redis instance, and the migration task are configured with the same VPC.</span><p><p id="dcs-migration-190703003__p188021330165115">If yes, go to <a href="#dcs-migration-190703003__section157769524519">Creating an Online Migration Task</a>. If no, go to <a href="#dcs-migration-190703003__li160420185217">2</a>.</p>
</p></li><li id="dcs-migration-190703003__li160420185217"><a name="dcs-migration-190703003__li160420185217"></a><a name="li160420185217"></a><span>Check whether the VPCs configured for the source Redis instance, the target Redis instance, and the migration task are connected to ensure that the VM resource of the migration task can access the source and target Redis instances.</span><p><p id="dcs-migration-190703003__p1480253095111">If yes, go to <a href="#dcs-migration-190703003__section14919536272">Configuring the Online Migration Task</a>. If no, go to <a href="#dcs-migration-190703003__li423483319412">3</a>.</p>
</p></li><li id="dcs-migration-190703003__li423483319412"><a name="dcs-migration-190703003__li423483319412"></a><a name="li423483319412"></a><span>Perform the following operations to establish the network.</span><p><ul id="dcs-migration-190703003__ul17325432414"><li id="dcs-migration-190703003__li7271615152516">If the VPC of the source and target Redis instances are of the same cloud vendor and in the same region, create a VPC peering connection by referring to "VPC Peering Connection" in the <em id="dcs-migration-190703003__i4602173825519">Virtual Private Cloud User Guide</em>.</li><li id="dcs-migration-190703003__li1073215431842">If the source and target Redis instances are on different clouds or in different regions, create a connection using only Direct Connect. For details, see the <em id="dcs-migration-190703003__i22974405618">Direct Connect User Guide</em>.</li></ul>
</p></li></ol>
</div>
<div class="section" id="dcs-migration-190703003__section14919536272"><a name="dcs-migration-190703003__section14919536272"></a><a name="section14919536272"></a><h4 class="sectiontitle">Configuring the Online Migration Task</h4><ol id="dcs-migration-190703003__ol20242048298"><li id="dcs-migration-190703003__li187884091914"><span>On the <strong id="dcs-migration-190703003__b787651612226">Online Migration</strong> tab page, click <strong id="dcs-migration-190703003__b208765165228">Configure</strong> in the row containing the online migration task you just created.</span></li><li id="dcs-migration-190703003__li18777171715209"><span>Select a migration type.</span><p><p id="dcs-migration-190703003__p72342811211">Supported migration types are <strong id="dcs-migration-190703003__b7961135591712">Full</strong> and <strong id="dcs-migration-190703003__b1096125531711">Full + Incremental</strong>, which are described in <a href="#dcs-migration-190703003__table55653322215">Table 1</a>.</p>
<div class="tablenoborder"><a name="dcs-migration-190703003__table55653322215"></a><a name="table55653322215"></a><table cellpadding="4" cellspacing="0" summary="" id="dcs-migration-190703003__table55653322215" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Migration type description</caption><thead align="left"><tr id="dcs-migration-190703003__row5587330229"><th align="left" class="cellrowborder" valign="top" width="27.47%" id="mcps1.3.8.2.2.2.2.2.3.1.1"><p id="dcs-migration-190703003__p758103372214">Migration Type</p>
<div class="tablenoborder"><a name="dcs-migration-190703003__table55653322215"></a><a name="table55653322215"></a><table cellpadding="4" cellspacing="0" summary="" id="dcs-migration-190703003__table55653322215" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Migration type description</caption><thead align="left"><tr id="dcs-migration-190703003__row5587330229"><th align="left" class="cellrowborder" valign="top" width="27.47%" id="mcps1.3.7.2.2.2.2.2.3.1.1"><p id="dcs-migration-190703003__p758103372214">Migration Type</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="72.53%" id="mcps1.3.8.2.2.2.2.2.3.1.2"><p id="dcs-migration-190703003__p1058153311225">Description</p>
<th align="left" class="cellrowborder" valign="top" width="72.53%" id="mcps1.3.7.2.2.2.2.2.3.1.2"><p id="dcs-migration-190703003__p1058153311225">Description</p>
</th>
</tr>
</thead>
<tbody><tr id="dcs-migration-190703003__row1958203312220"><td class="cellrowborder" valign="top" width="27.47%" headers="mcps1.3.8.2.2.2.2.2.3.1.1 "><p id="dcs-migration-190703003__p458153332210">Full</p>
<tbody><tr id="dcs-migration-190703003__row1958203312220"><td class="cellrowborder" valign="top" width="27.47%" headers="mcps1.3.7.2.2.2.2.2.3.1.1 "><p id="dcs-migration-190703003__p458153332210">Full</p>
</td>
<td class="cellrowborder" valign="top" width="72.53%" headers="mcps1.3.8.2.2.2.2.2.3.1.2 "><p id="dcs-migration-190703003__p125833322217">Suitable for scenarios where services can be interrupted. Data is migrated at one time. <strong id="dcs-migration-190703003__b2535184111510">Source instance data updated during the migration will not be migrated to the target instance.</strong></p>
<td class="cellrowborder" valign="top" width="72.53%" headers="mcps1.3.7.2.2.2.2.2.3.1.2 "><p id="dcs-migration-190703003__p125833322217">Suitable for scenarios where services can be interrupted. Data is migrated at one time. <strong id="dcs-migration-190703003__b2535184111510">Source instance data updated during the migration will not be migrated to the target instance.</strong></p>
</td>
</tr>
<tr id="dcs-migration-190703003__row205815338228"><td class="cellrowborder" valign="top" width="27.47%" headers="mcps1.3.8.2.2.2.2.2.3.1.1 "><p id="dcs-migration-190703003__p85863316221">Full + incremental</p>
<tr id="dcs-migration-190703003__row205815338228"><td class="cellrowborder" valign="top" width="27.47%" headers="mcps1.3.7.2.2.2.2.2.3.1.1 "><p id="dcs-migration-190703003__p85863316221">Full + incremental</p>
</td>
<td class="cellrowborder" valign="top" width="72.53%" headers="mcps1.3.8.2.2.2.2.2.3.1.2 "><p id="dcs-migration-190703003__p858103352214">Suitable for scenarios requiring minimal service downtime. The incremental migration parses logs to ensure data consistency between the source and target instances.</p>
<p id="dcs-migration-190703003__p110411470116">Once the migration starts, it remains <strong id="dcs-migration-190703003__b16552211111311">Migrating</strong> until you click <strong id="dcs-migration-190703003__b65201171131">Stop</strong> in the <strong id="dcs-migration-190703003__b5355163610593">Operation</strong> column. After the migration is stopped, data in the source instance will not be lost, but data will not be written to the target instance. When the transmission network is stable, the delay of incremental migration is within seconds. The actual delay depends on the transmission quality of the network link.</p>
<td class="cellrowborder" valign="top" width="72.53%" headers="mcps1.3.7.2.2.2.2.2.3.1.2 "><p id="dcs-migration-190703003__p858103352214">Suitable for scenarios requiring minimal service downtime. The incremental migration parses logs to ensure data consistency between the source and target instances.</p>
<p id="dcs-migration-190703003__p110411470116">Once the migration starts, it remains <strong id="dcs-migration-190703003__b1239633218259">Migrating</strong> until you click <strong id="dcs-migration-190703003__b43962323258">Stop</strong> in the <strong id="dcs-migration-190703003__b13961832182514">Operation</strong> column. After the migration is stopped, data in the source instance will not be lost, but data will not be written to the target instance. When the transmission network is stable, the delay of incremental migration is within seconds. The actual delay depends on the transmission quality of the network link.</p>
</td>
</tr>
</tbody>
</table>
</div>
<div class="fignone" id="dcs-migration-190703003__fig23511729101218"><span class="figcap"><b>Figure 1 </b>Selecting the migration type</span><br><span><img id="dcs-migration-190703003__image2036555461718" src="en-us_image_0291862872.png"></span></div>
</p></li><li id="dcs-migration-190703003__li974533414185"><span>Configure source Redis and target Redis.</span><p><ol type="a" id="dcs-migration-190703003__ol128193366190"><li id="dcs-migration-190703003__li5121433171911">The Redis type can be <strong id="dcs-migration-190703003__b1093945910">Redis in the cloud</strong> or <strong id="dcs-migration-190703003__b431181211911">Self-hosted Redis</strong> as required.<ul id="dcs-migration-190703003__ul445012114211"><li id="dcs-migration-190703003__li184511719217"><strong id="dcs-migration-190703003__b3442183942010">Redis in the cloud</strong>: a DCS Redis instance (source or target) that is in the same VPC as the migration task. If you select this option, specify a DCS Redis instance.</li><li id="dcs-migration-190703003__li127821877221"><strong id="dcs-migration-190703003__b1967218566215">Self-hosted Redis</strong>: a DCS Redis instance, Redis in another cloud, or self-hosted Redis. If you select this option, enter Redis addresses.</li></ul>
</li><li id="dcs-migration-190703003__li13145145319231">If the instance is password-protected, click <strong id="dcs-migration-190703003__b164631019236">Test Connection</strong> to check whether the instance password is correct and whether the network is connected. If the instance is not password-protected, click <strong id="dcs-migration-190703003__b54195135235">Test Connection</strong> directly.</li></ol>
</p></li><li id="dcs-migration-190703003__li1348442114911"><span>Click <strong id="dcs-migration-190703003__b13194159102331">Next</strong>.</span></li><li id="dcs-migration-190703003__li3625202214190"><span>Confirm the migration task details and click <strong id="dcs-migration-190703003__b46184816117">Submit</strong>.</span><p><p id="dcs-migration-190703003__p9625422141910">Go back to the data migration task list. After the migration is successful, the task status changes to <strong id="dcs-migration-190703003__b15447174915118">Successful</strong>.</p>
<div class="note" id="dcs-migration-190703003__note4427420124517"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="dcs-migration-190703003__ul4321452125415"><li id="dcs-migration-190703003__li3321952195412">Once incremental migration starts, it remains <strong id="dcs-migration-190703003__b12386152711">Migrating</strong> until you click <strong id="dcs-migration-190703003__b0238101515715">Stop</strong>.</li><li id="dcs-migration-190703003__li23211252175420">To stop a migration task, select the check box on the left of the migration task and click <strong id="dcs-migration-190703003__b230619112814">Stop</strong> above the instance list.</li><li id="dcs-migration-190703003__li1912563853615">After data migration, duplicate keys will be overwritten.</li></ul>
</p></li><li id="dcs-migration-190703003__li76295537920"><span>Only if <strong id="dcs-migration-190703003__b49878456252">Migration Type</strong> is set to <strong id="dcs-migration-190703003__b29879457251">Full + Incremental</strong>, you can specify a bandwidth limit.</span><p><p id="dcs-migration-190703003__p197736619241">The data synchronization rate can be kept around the bandwidth limit.</p>
</p></li><li id="dcs-migration-190703003__li13649906333"><span>Specify <strong id="dcs-migration-190703003__b34193412271">Auto-Reconnect</strong>. If this option is enabled, automatic reconnections will be performed indefinitely in the case of a network exception.</span><p><p id="dcs-migration-190703003__p67501140810">Full synchronization will be triggered and requires more bandwidth if incremental synchronization becomes unavailable. Exercise caution when enabling this option.</p>
</p></li><li id="dcs-migration-190703003__li974533414185"><span>Configure <strong id="dcs-migration-190703003__b3314825122811">Source Redis</strong> and <strong id="dcs-migration-190703003__b1891962917288">Target Redis</strong>.</span><p><ol type="a" id="dcs-migration-190703003__ol128193366190"><li id="dcs-migration-190703003__li177581938192613">Configure <strong id="dcs-migration-190703003__b14997237598">Source Redis Type</strong> and <strong id="dcs-migration-190703003__b17991823185915">Source Redis Instance</strong>:<p id="dcs-migration-190703003__p18861540172614">Set <strong id="dcs-migration-190703003__b127826526216">Redis in the cloud</strong> for <strong id="dcs-migration-190703003__b103661355922">Source Redis Type</strong> and add <strong id="dcs-migration-190703003__b106521571529">Source Redis Instance</strong>.</p>
<p id="dcs-migration-190703003__p2086611152814">If the source Redis is a Redis Cluster, enter the IP addresses and ports of all masters in the cluster and separate multiple addresses with commas (,). For example: <strong id="dcs-migration-190703003__b1739855782510">192.168.1.1:6379,192.168.0.0:6379</strong></p>
</li><li id="dcs-migration-190703003__li9907815183313">Configure <strong id="dcs-migration-190703003__b993755923719">Target Redis Type</strong> and <strong id="dcs-migration-190703003__b1582032133811">Target Redis Instance</strong>:<p id="dcs-migration-190703003__p1765351142813">Set <strong id="dcs-migration-190703003__b113540431316">Redis in the cloud</strong> for <strong id="dcs-migration-190703003__b142121046732">Target Redis Type</strong> and add <strong id="dcs-migration-190703003__b14980352338">Target Redis Instance</strong>.</p>
</li><li id="dcs-migration-190703003__li13145145319231">Configure <strong id="dcs-migration-190703003__b19707205817319">Source Redis Instance Password</strong> and <strong id="dcs-migration-190703003__b1770711584313">Target Redis Instance Password</strong>: If the instance is password-protected, click <strong id="dcs-migration-190703003__b6707258236">Test Connection</strong> to check whether the instance password is correct and whether the network is connected. If the instance is not password-protected, click <strong id="dcs-migration-190703003__en-us_topic_0292880550_dcs-migration-190703003_b54195135235">Test Connection</strong> directly. If the test fails, check whether the password is correct, and whether the migration task network is connected.<p id="dcs-migration-190703003__p1992114918157">If a DCS Redis instance is used, the users created in <a href="dcs-ug-221220.html">Managing Users</a> are currently unavailable.</p>
</li></ol>
</p></li><li id="dcs-migration-190703003__li1348442114911"><span>Click <strong id="dcs-migration-190703003__b13194159102331">Next</strong>.</span></li><li id="dcs-migration-190703003__li3625202214190"><span>Confirm the migration task details and click <strong id="dcs-migration-190703003__b46184816117">Submit</strong>.</span><p><p id="dcs-migration-190703003__p9625422141910">Go back to the data migration task list. After the migration is successful, the task status changes to <strong id="dcs-migration-190703003__en-us_topic_0292880550_dcs-migration-190703003_b15447174915118">Successful</strong>.</p>
<p id="dcs-migration-190703003__en-us_topic_0292880550_dcs-migration-190703003_p4880126112412">If the migration fails, click the migration task and check the log on the <strong id="dcs-migration-190703003__b335084213548">Migration Logs</strong> page.</p>
<div class="note" id="dcs-migration-190703003__note4427420124517"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="dcs-migration-190703003__ul4321452125415"><li id="dcs-migration-190703003__li1037218318491">Once incremental migration starts, it remains <strong id="dcs-migration-190703003__b5271257515">Migrating</strong> after full migration.</li><li id="dcs-migration-190703003__li23211252175420">To manually stop a migration task, select the check box on the left of the migration task and click <strong id="dcs-migration-190703003__b15871442195617">Stop</strong> above the migration task.</li></ul>
</div></div>
<p id="dcs-migration-190703003__p4880126112412">If the migration fails, click the migration task and check the log on the <strong id="dcs-migration-190703003__b1024662118283">Migration Logs</strong> page.</p>
</p></li></ol>
</div>
<div class="section" id="dcs-migration-190703003__section3718231268"><h4 class="sectiontitle">Verifying the Migration</h4><p id="dcs-migration-190703003__p1571161034711">After the migration is complete, use redis-cli to connect the source and target Redis instances to check data integrity.</p>
<ol id="dcs-migration-190703003__ol11257313194715"><li id="dcs-migration-190703003__li94593118471">Connect to the source Redis and the target Redis.</li><li id="dcs-migration-190703003__li10257713154717">Run the <strong id="dcs-migration-190703003__b5674145372816">info keyspace</strong> command to check the values of <strong id="dcs-migration-190703003__b6780111112291">keys</strong> and <strong id="dcs-migration-190703003__b20825181414299">expires</strong>.<p id="dcs-migration-190703003__p203461224529"><span><img id="dcs-migration-190703003__image152912031408" src="en-us_image_0293255709.png"></span></p>
<div class="section" id="dcs-migration-190703003__section3718231268"><h4 class="sectiontitle">Verifying the Migration</h4><p id="dcs-migration-190703003__en-us_topic_0292880550_dcs-migration-190703003_p1571161034711">Before data migration, if the target Redis has no data, check data integrity after the migration is complete in the following way:</p>
<ol id="dcs-migration-190703003__ol1116739195110"><li id="dcs-migration-190703003__en-us_topic_0292880550_dcs-migration-190703003_li94593118471">Connect to the source Redis and the target Redis. Connect to Redis by referring to <a href="dcs-ug-0326009.html">Accessing a DCS Redis Instance Through redis-cli</a>.</li><li id="dcs-migration-190703003__li10257713154717">Run the <strong id="dcs-migration-190703003__en-us_topic_0292880550_dcs-migration-190703003_b5674145372816">info keyspace</strong> command to check the values of <strong id="dcs-migration-190703003__en-us_topic_0292880550_dcs-migration-190703003_b6780111112291">keys</strong> and <strong id="dcs-migration-190703003__en-us_topic_0292880550_dcs-migration-190703003_b20825181414299">expires</strong>.<p id="dcs-migration-190703003__p203461224529"><span><img id="dcs-migration-190703003__image152912031408" src="en-us_image_0293255709.png"></span></p>
</li><li id="dcs-migration-190703003__li1878042516480">Calculate the differences between the values of <strong id="dcs-migration-190703003__b7585046192918">keys</strong> and <strong id="dcs-migration-190703003__b2585204614294">expires</strong> of the source Redis and the target Redis. If the differences are the same, the data is complete and the migration is successful.</li></ol>
<p id="dcs-migration-190703003__p68531049182811">During full migration, source Redis data updated during the migration will not be migrated to the target instance.</p>
</div>