forked from docs/doc-exports
Zaoxu, Li
305c41bb57
Reviewed-by: Hasko, Vladimir <vladimir.hasko@t-systems.com> Co-authored-by: Zaoxu, Li <lizaoxu@huawei.com> Co-committed-by: Zaoxu, Li <lizaoxu@huawei.com>
23 lines
3.5 KiB
HTML
23 lines
3.5 KiB
HTML
<a name="evs_01_0027"></a><a name="evs_01_0027"></a>
|
|
|
|
<h1 class="topictitle1">Creating an EVS Replication Pair (Deprecated)</h1>
|
|
<div id="body1508295804297"><div class="section" id="evs_01_0027__section5572733817211"><h4 class="sectiontitle">Scenarios</h4><p id="evs_01_0027__p3888899917218">Currently, users need to make API calls to create EVS replication pairs. Each server can have multiple EVS replication pairs. For details, see <strong id="evs_01_0027__b842352706184935">EVS Replication Pair</strong> in the <em id="evs_01_0027__i842352697184946">Elastic Volume Service API Reference</em>.</p>
|
|
<p id="evs_01_0027__p3975123173422">If a production disk needs to be deleted after it has been used together with its DR disk to create an EVS replication pair, delete the EVS replication pair first and then delete the production disk and DR disk. For details, see <strong id="evs_01_0027__b2123108067185348">Deleting an EVS Replication Pair</strong> in the <em id="evs_01_0027__i689404098185348">Elastic Volume Service API Reference</em>.</p>
|
|
<div class="note" id="evs_01_0027__note98481557151510"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="evs_01_0027__evs_01_0020_p883713341981">EVS replication APIs have been deprecated. If you need to use the replication function, see <a href="https://docs.otc.t-systems.com/en-us/usermanual/sdrs/en-us_topic_0125068221.html" target="_blank" rel="noopener noreferrer">Storage Disaster Recovery Service User Guide</a> and <a href="https://docs.otc.t-systems.com/en-us/api/sdrs/sdrs_01_0000.html" target="_blank" rel="noopener noreferrer">Storage Disaster Recovery Service API Reference</a>.</p>
|
|
</div></div>
|
|
</div>
|
|
<div class="section" id="evs_01_0027__section55139435172113"><h4 class="sectiontitle">Procedure</h4><ol id="evs_01_0027__ol25404739172247"><li id="evs_01_0027__li1149065320371"><span>Create an EVS replication pair using the production disk and DR disk.</span><p><p id="evs_01_0027__p6157776420373">For details, see <strong id="evs_01_0027__b389837272">Creating an EVS Replication Pair</strong> in the <em id="evs_01_0027__i872517198">Elastic Volume Service API Reference</em>.</p>
|
|
</p></li><li id="evs_01_0027__li27331409203711"><span>Query the details about the EVS replication pair.</span><p><p id="evs_01_0027__p14492955205026">For details, see <strong id="evs_01_0027__b1945236100">Querying Details About an EVS Replication Pair</strong> in the <em id="evs_01_0027__i1326552039">Elastic Volume Service API Reference</em>.</p>
|
|
<p id="evs_01_0027__p14750063172748">If the EVS replication pair status changes to <strong id="evs_01_0027__b2076608000194835">available</strong>, the creation is successful.</p>
|
|
</p></li><li id="evs_01_0027__li6816516172319"><span>Take note of the production disk ID, DR disk ID, EVS replication pair ID, and the primary site of the EVS replication pair, which is the AZ containing the production disk.</span><p><div class="note" id="evs_01_0027__note32392930152526"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="evs_01_0027__p23100918152526">Two EVS disks form an EVS replication pair. Therefore, the production disk ID, DR disk ID, and EVS replication pair ID can be used to identify disks and the EVS replication pair.</p>
|
|
</div></div>
|
|
</p></li></ol>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="evs_01_0023.html">Managing EVS Replication (Deprecated)</a></div>
|
|
</div>
|
|
</div>
|
|
|