forked from docs/doc-exports
Zheng, Xiu
5b5876528a
Reviewed-by: Pruthi, Vineet <vineet.pruthi@t-systems.com> Co-authored-by: Zheng, Xiu <zhengxiu@huawei.com> Co-committed-by: Zheng, Xiu <zhengxiu@huawei.com>
22 lines
5.1 KiB
HTML
22 lines
5.1 KiB
HTML
<a name="css_01_0040"></a><a name="css_01_0040"></a>
|
|
|
|
<h1 class="topictitle1">Migrating Cluster Data</h1>
|
|
<div id="body0000001334739189"><p id="css_01_0040__p1388414942">You can migrate data from one cluster to another. In certain scenarios, for example, if you cannot get sufficient capacity by changing the specifications of the current cluster, you can create a cluster of higher specifications and migrate all data of the current cluster to the new one. Alternatively, you can merge indices in two clusters to one cluster to meet your business needs. <span id="css_01_0040__text123942081042">CSS</span> enables you to migrate cluster data by using the index backup and restoration function, specifically, by restoring the snapshot of a cluster to the target cluster.</p>
|
|
<div class="section" id="css_01_0040__section3129114518368"><h4 class="sectiontitle">Prerequisites</h4><ul id="css_01_0040__ul1731191414373"><li id="css_01_0040__li3311181414370">The source and target clusters are in the same region.</li><li id="css_01_0040__li775891953719">The version of the target cluster is the same as or later than that of the source cluster.</li><li id="css_01_0040__li4380192453712">The number of nodes in the target cluster must be greater than half of the number of nodes in the source cluster.</li></ul>
|
|
</div>
|
|
<div class="section" id="css_01_0040__section18998141277"><h4 class="sectiontitle">Suggestions</h4><ul id="css_01_0040__ul173281516272"><li id="css_01_0040__li155182181380">The number of nodes in the target cluster should be no less than the number of replicas in the source cluster.</li><li id="css_01_0040__li14163616162713">The CPU, memory, and disk configurations of the target cluster should be no less than those of the source cluster. This will minimize service loss after migration.</li></ul>
|
|
</div>
|
|
<p id="css_01_0040__p55571487450">In this section, assume that data of cluster <span class="parmname" id="css_01_0040__parmname387402189135847"><b>Es-1</b></span> is migrated to cluster <span class="parmname" id="css_01_0040__parmname1357640787135851"><b>Es-2</b></span>. Cluster <span class="parmname" id="css_01_0040__parmname102297251973"><b>Es-2</b></span> runs a version later than that of cluster <span class="parmname" id="css_01_0040__parmname112294253712"><b>Es-1</b></span> and the number of nodes in cluster <span class="parmname" id="css_01_0040__parmname451451525311"><b>Es-2</b></span> is greater than half of that in cluster <span class="parmname" id="css_01_0040__parmname42295256716"><b>Es-1</b></span>.</p>
|
|
<div class="section" id="css_01_0040__section339824743111"><h4 class="sectiontitle">Procedure</h4><ol id="css_01_0040__ol119181710193211"><li id="css_01_0040__li1691871014323">On the <strong id="css_01_0040__b842352706135948">Clusters</strong> page, click <span class="parmvalue" id="css_01_0040__parmvalue334615753114655"><b>Es-1</b></span>. On the displayed page, click <span class="parmname" id="css_01_0040__parmname61088115336"><b>Cluster Snapshots</b></span>.</li><li id="css_01_0040__li357514343420">Click <span class="uicontrol" id="css_01_0040__uicontrol2057633173418"><b>Create Snapshot</b></span> to manually create a snapshot. In the displayed dialog box, enter the snapshot name and click <span class="uicontrol" id="css_01_0040__uicontrol15138165414344"><b>OK</b></span>.<p id="css_01_0040__p15741433418">If you use the index backup and restoration function for the first time, you need to perform basic configurations first. For more details, see <a href="css_01_0033.html#css_01_0033__section43906502025">Manually Creating a Snapshot</a>.</p>
|
|
</li><li id="css_01_0040__li1470891763718">In the snapshot list, locate the row that contains the target snapshot and click <span class="uicontrol" id="css_01_0040__uicontrol12708717113716"><b>Restore</b></span> in the <strong id="css_01_0040__b84235270614229">Operation</strong> column to restore data to cluster <strong id="css_01_0040__b84235270614233">Es-2</strong>.<ul id="css_01_0040__ul165644811396"><li id="css_01_0040__li556416810396">Leave the <span class="parmname" id="css_01_0040__parmname19061915331"><b>Index</b></span> option blank (default setting), indicating that you want to restore data of all indices in cluster <span class="parmname" id="css_01_0040__parmname1290817143310"><b>Es-1</b></span>.</li><li id="css_01_0040__li1156410873915">From the <span class="parmname" id="css_01_0040__parmname148094791814318"><b>Cluster</b></span> drop-down list, select <span class="parmvalue" id="css_01_0040__parmvalue172345045214323"><b>Es-2</b></span>.</li></ul>
|
|
<p id="css_01_0040__p777024033818">Click <span class="uicontrol" id="css_01_0040__uicontrol127843639314335"><b>OK</b></span>. You can also rename the restored index.</p>
|
|
</li><li id="css_01_0040__li6183045404">After restoration is complete, data in cluster <span class="parmname" id="css_01_0040__parmname16723637381449"><b>Es-1</b></span> will be migrated to cluster <span class="parmname" id="css_01_0040__parmname165705345314413"><b>Es-2</b></span>.</li></ol>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="css_01_0009.html">Managing Elasticsearch Clusters</a></div>
|
|
</div>
|
|
</div>
|
|
|