forked from docs/doc-exports
gtema
28ee660433
Reviewed-by: Goncharov, Artem <artem.goncharov@t-systems.com> Co-authored-by: gtema <artem.goncharov@gmail.com> Co-committed-by: gtema <artem.goncharov@gmail.com>
26 lines
4.8 KiB
HTML
26 lines
4.8 KiB
HTML
<a name="sdrs_06_0404"></a><a name="sdrs_06_0404"></a>
|
|
|
|
<h1 class="topictitle1">What Can I Do If hostname of the Production Site Server and DR Site Server Are Different After a Planned Failover or Failover?</h1>
|
|
<div id="body1560821721889"><div class="section" id="sdrs_06_0404__section37204431987"><h4 class="sectiontitle">Symptom</h4><p id="sdrs_06_0404__p46037471784">Users have changed <strong id="sdrs_06_0404__b916751020582">hostname</strong> of the production site server before they perform a planned failover or failover for the first time. After the planned failover or failover, users start the DR site server and find that <strong id="sdrs_06_0404__b17932115885818">hostname</strong> of the DR site server is not updated accordingly.</p>
|
|
</div>
|
|
<div class="section" id="sdrs_06_0404__section11269131061117"><h4 class="sectiontitle"><strong id="sdrs_06_0404__b1666416541068">Possible Causes</strong></h4><p id="sdrs_06_0404__p8622141219116">For Linux servers, if you have changed <strong id="sdrs_06_0404__b12854624195716">hostname</strong> of the production site server before you perform a planned failover or failover for the first time, this modification will not synchronize to the DR site server.</p>
|
|
</div>
|
|
<div class="section" id="sdrs_06_0404__section2084985454913"><h4 class="sectiontitle"><strong id="sdrs_06_0404__en-us_topic_0040236005_en-us_topic_0035268496_b842352706102921">Prerequisites</strong></h4><ul id="sdrs_06_0404__ul378213355020"><li id="sdrs_06_0404__li278212305013">The production site server is a Linux server with Cloud-Init installed.</li><li id="sdrs_06_0404__li861091335011"><strong id="sdrs_06_0404__b164870341720">hostname</strong> of the production site server has been changed.</li></ul>
|
|
</div>
|
|
<div class="section" id="sdrs_06_0404__section183011437149"><h4 class="sectiontitle">Solution 1 (If You Have Not Performed a Planned Failover or Failover)</h4><p id="sdrs_06_0404__p4458154574718">Set <span class="parmvalue" id="sdrs_06_0404__parmvalue15303175791819"><b>preserve_hostname: false</b></span> to <span class="parmvalue" id="sdrs_06_0404__parmvalue2303155701814"><b>preserve_hostname: true</b></span> in the Cloud-Init configuration file <strong id="sdrs_06_0404__b1290015442310">/etc/cloud/cloud.cfg</strong> to ensure that <strong id="sdrs_06_0404__b51851045132418">hostname</strong> of the production site server and DR site server are the same after you enable protection.</p>
|
|
<p id="sdrs_06_0404__p767874541420">The procedure is as follows:</p>
|
|
</div>
|
|
<ol id="sdrs_06_0404__ol16293105113237"><li id="sdrs_06_0404__li1329311519231">Log in to the production site server.</li><li id="sdrs_06_0404__li1282121102419">Run the following command to edit the <strong id="sdrs_06_0404__b842352706192723">/etc/cloud/cloud.cfg</strong> configuration file:<p id="sdrs_06_0404__p1515233122417"><strong id="sdrs_06_0404__b27741446202410">sudo vim /etc/cloud/cloud.cfg</strong></p>
|
|
</li><li id="sdrs_06_0404__li134135462410">Modify <strong id="sdrs_06_0404__b1841672862611">preserve_hostname</strong>.<ul id="sdrs_06_0404__ul1342852572614"><li id="sdrs_06_0404__li14429182510265">If <strong id="sdrs_06_0404__b842352706192827">preserve_hostname: false</strong> is already available in the <strong id="sdrs_06_0404__b842352706192837">/etc/cloud/cloud.cfg</strong> configuration file, change it to <strong id="sdrs_06_0404__b842352706192851">preserve_hostname: true</strong>.</li><li id="sdrs_06_0404__li64291925192615">If <strong id="sdrs_06_0404__b154393914193010">preserve_hostname: false</strong> is unavailable in the <strong id="sdrs_06_0404__b842352706193047">/etc/cloud/cloud.cfg</strong> configuration file, add <strong id="sdrs_06_0404__b198044657219342">preserve_hostname: true</strong> before <strong id="sdrs_06_0404__b84235270619312">cloud_init_modules</strong>.</li></ul>
|
|
</li><li id="sdrs_06_0404__li143771326102713">Perform a planned failover or failover.<p id="sdrs_06_0404__p6341386508"><a name="sdrs_06_0404__li143771326102713"></a><a name="li143771326102713"></a>After the planned failover or failover, <strong id="sdrs_06_0404__b1011410116286">hostname</strong> of the DR site server and production site server are the same.</p>
|
|
</li></ol>
|
|
<div class="section" id="sdrs_06_0404__section2538238204516"><h4 class="sectiontitle">Solution 2 (If You Have Performed a Planned Failover or Failover)</h4><p id="sdrs_06_0404__p457484134517">If you have not modified configuration file <strong id="sdrs_06_0404__b913112455334">/etc/cloud/cloud.cfg</strong> before the planned failover or failover, log in to the DR site server and manually change <strong id="sdrs_06_0404__b139865919368">hostname</strong> of the DR site server to that of the production site server.</p>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="sdrs_06_0400.html">FAQs</a></div>
|
|
</div>
|
|
</div>
|
|
|