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>
20 lines
5.6 KiB
HTML
20 lines
5.6 KiB
HTML
<a name="evs_01_0042"></a><a name="evs_01_0042"></a>
|
|
|
|
<h1 class="topictitle1">Managing EVS Disk Transfer</h1>
|
|
<div id="body1516262005961"><div class="section" id="evs_01_0042__section2078706916510"><h4 class="sectiontitle">Scenarios</h4><p id="evs_01_0042__p5096591219834">Through EVS disk transfer, EVS disks can be transferred from one account to another. After the transfer succeeds, the ownerships of the EVS disks belong to the target account only. Currently, only data disks can be transferred.</p>
|
|
<p id="evs_01_0042__p4981704319174">Currently, users can use the disk transfer function via API only. For details, see chapter "EVS Disk Transfer" in the <em id="evs_01_0042__i84235269711125">Elastic Volume Service API Reference</em>.</p>
|
|
</div>
|
|
<div class="section" id="evs_01_0042__section3505785917301"><h4 class="sectiontitle">Constraints</h4><ul id="evs_01_0042__en-us_topic_0092887872_ul15490115496"><li id="evs_01_0042__en-us_topic_0092887872_li171556610508">Encrypted EVS disks cannot be transferred.</li><li id="evs_01_0042__en-us_topic_0092887872_li4567911125014">EVS disks with backups and snapshots available cannot be transferred.</li><li id="evs_01_0042__en-us_topic_0092887872_li780416329501">EVS disks associated with backup policies cannot be transferred.</li><li id="evs_01_0042__en-us_topic_0092887872_li678162410505">EVS disks used as system disks cannot be transferred.</li><li id="evs_01_0042__en-us_topic_0092887872_li7697829115010">EVS disks in EVS replication pairs cannot be transferred.</li></ul>
|
|
</div>
|
|
<div class="section" id="evs_01_0042__section4128178173158"><h4 class="sectiontitle">Procedure</h4><div class="p" id="evs_01_0042__p5974051191339">The following example shows you how to transfer an EVS disk from account A to account B. User A belongs to account A, and user B belongs to account B. User A creates the transfer. User B accepts the transfer through the transfer ID (<strong id="evs_01_0042__b1642902110511">transfer_id</strong>) and authentication key (<strong id="evs_01_0042__b454082425119">auth_key</strong>). After the transfer has been accepted, the transfer is complete. <a href="#evs_01_0042__fig86501415163119">Figure 1</a> shows the basic transfer process.<div class="note" id="evs_01_0042__note885554917314"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="evs_01_0042__ul98555492312"><li id="evs_01_0042__li13855124911312"><strong id="evs_01_0042__b376974644114">transfer_id</strong> specifies the disk transfer ID. Each EVS disk transfer has a transfer ID, and user B uses this ID to accept the disk transfer.</li><li id="evs_01_0042__li158551049153115"><strong id="evs_01_0042__b10414185416419">auth_key</strong> specifies the identity authentication key of the disk transfer. Each EVS disk transfer has an authentication key, and user B uses this key for authentication when accepting the disk transfer.</li></ul>
|
|
</div></div>
|
|
<div class="fignone" id="evs_01_0042__fig86501415163119"><a name="evs_01_0042__fig86501415163119"></a><a name="fig86501415163119"></a><span class="figcap"><b>Figure 1 </b>EVS disk transfer process</span><br><span><img id="evs_01_0042__image146501015143113" src="en-us_image_0000001119238510.png"></span></div>
|
|
</div>
|
|
<ol id="evs_01_0042__ol755981173317"><li id="evs_01_0042__li6803832173317"><span>User A creates the transfer. For details, see "Creating a Disk Transfer" in the <em id="evs_01_0042__i84235269715318">Elastic Volume Service API Reference</em>.</span><p><p id="evs_01_0042__p36632843016">After the transfer is successfully created, <strong id="evs_01_0042__b965531715436">transfer_id</strong> and <strong id="evs_01_0042__b7665171713433">auth_key</strong> are returned.</p>
|
|
</p></li><li id="evs_01_0042__li650655391268"><span>(Optional) User A views the disk transfer. For details, see "Querying Details of a Disk Transfer" in the <em id="evs_01_0042__i842352697165156">Elastic Volume Service API Reference</em>. If multiple disk transfers have been created, user A can query all disk transfers. For details, see "Querying All Disk Transfers" or "Querying Details of All Disk Transfers" in the <em id="evs_01_0042__i244212406165446">Elastic Volume Service API Reference</em>.</span></li><li id="evs_01_0042__li14239489173317"><span>User A delivers the returned <strong id="evs_01_0042__b84235270615420">transfer_id</strong> and <strong id="evs_01_0042__b84235270615423">auth_key</strong> to user B.</span></li><li id="evs_01_0042__li4645498512658"><span>Check whether user B is going to accept the disk transfer.</span><p><ul id="evs_01_0042__ul3215745012752"><li id="evs_01_0042__li6577963012752">If yes, go to <a href="#evs_01_0042__li61046537173317">5</a>.</li><li id="evs_01_0042__li60682936121146">If no, no further action is required.<p id="evs_01_0042__p1061104353618"><a name="evs_01_0042__li60682936121146"></a><a name="li60682936121146"></a>User A can delete the unaccepted disk transfer. For details, see "Deleting a Disk Transfer" in the <em id="evs_01_0042__i78801037144">Elastic Volume Service API Reference</em>.</p>
|
|
</li></ul>
|
|
</p></li><li id="evs_01_0042__li61046537173317"><a name="evs_01_0042__li61046537173317"></a><a name="li61046537173317"></a><span>User B accepts <strong id="evs_01_0042__b84235270615440">transfer_id</strong> and <strong id="evs_01_0042__b84235270615443">auth_key</strong>.</span></li><li id="evs_01_0042__li16121122716324"><span>User B accepts the transfer through <strong id="evs_01_0042__b145358531146">transfer_id</strong> and <strong id="evs_01_0042__b1953515331416">auth_key</strong>. For details, see "Accepting a Disk Transfer" in the <em id="evs_01_0042__i1553612539149">Elastic Volume Service API Reference</em>.</span></li></ol>
|
|
</div>
|
|
</div>
|
|
|