forked from docs/doc-exports
EVS UMN add ESSD V2
Reviewed-by: Hasko, Vladimir <vladimir.hasko@t-systems.com> Co-authored-by: zhangyue <zhangyue164@huawei.com> Co-committed-by: zhangyue <zhangyue164@huawei.com>
This commit is contained in:
parent
f3b09e5d2f
commit
b55a939a8a
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
BIN
docs/evs/umn/en-us_image_0000001327868762.png
Normal file
BIN
docs/evs/umn/en-us_image_0000001327868762.png
Normal file
Binary file not shown.
After Width: | Height: | Size: 36 KiB |
Binary file not shown.
Before Width: | Height: | Size: 24 KiB After Width: | Height: | Size: 160 KiB |
Binary file not shown.
Before Width: | Height: | Size: 92 KiB |
@ -1,19 +1,19 @@
|
||||
<a name="en-us_topic_0014580741"></a><a name="en-us_topic_0014580741"></a>
|
||||
|
||||
<h1 class="topictitle1">What Is EVS?</h1>
|
||||
<div id="body55752527"><div class="section" id="en-us_topic_0014580741__section192781048122611"><h4 class="sectiontitle">Overview</h4><p id="en-us_topic_0014580741__p49925672115020">Elastic Volume Service (EVS) offers scalable block storage for cloud <span id="en-us_topic_0014580741__text679223501111727">servers</span>. With high reliability, high performance, and rich specifications, EVS disks can be used for distributed file systems, development and testing environments, data warehouse applications, and high-performance computing (HPC) scenarios to meet diverse service requirements. Servers that EVS supports include Elastic Cloud Servers (ECSs) and Bare Metal Servers (BMSs).</p>
|
||||
<div id="body55752527"><div class="section" id="en-us_topic_0014580741__section192781048122611"><h4 class="sectiontitle">Overview</h4><p id="en-us_topic_0014580741__p49925672115020">Elastic Volume Service (EVS) offers scalable block storage for cloud <span id="en-us_topic_0014580741__text679223501111727">servers</span>. With high reliability, high performance, and a variety of specifications, EVS disks can be used for distributed file systems, development and test environments, data warehouses, and high-performance computing (HPC) applications. Cloud servers that EVS supports include Elastic Cloud Servers (ECSs) and Bare Metal Servers (BMSs).</p>
|
||||
<p id="en-us_topic_0014580741__p3272865612647">EVS disks are sometimes just referred to as disks in this document.</p>
|
||||
<div class="fignone" id="en-us_topic_0014580741__fig1392425915011"><span class="figcap"><b>Figure 1 </b>EVS architecture</span><br><span><img id="en-us_topic_0014580741__image1092535913016" src="en-us_image_0205523160.png"></span></div>
|
||||
</div>
|
||||
<div class="section" id="en-us_topic_0014580741__section450133172049"><h4 class="sectiontitle">EVS Advantages</h4><p id="en-us_topic_0014580741__p5655566191857">EVS has the following advantages:</p>
|
||||
<ul id="en-us_topic_0014580741__ul14991977101429"><li id="en-us_topic_0014580741__li48575151101429">Various disk types<p id="en-us_topic_0014580741__p29137379164254"><a name="en-us_topic_0014580741__li48575151101429"></a><a name="li48575151101429"></a>EVS provides various disk types for you to choose from, and EVS disks can be used as data disks and system disks for <span id="en-us_topic_0014580741__text18491994152222">servers</span>. You may select the disk type based on your budget and service requirements.</p>
|
||||
</li><li id="en-us_topic_0014580741__li65165360101429">Elastic scalability<p id="en-us_topic_0014580741__p197126269377"><a name="en-us_topic_0014580741__li65165360101429"></a><a name="li65165360101429"></a>The EVS disk capacity ranges from 10 GB to 32 TB. When it no longer meets your needs, you can expand the disk capacity up to 32 TB in increments of 1 GB, without interrupting your applications.</p>
|
||||
<ul id="en-us_topic_0014580741__ul14991977101429"><li id="en-us_topic_0014580741__li48575151101429">Various disk types<p id="en-us_topic_0014580741__p29137379164254"><a name="en-us_topic_0014580741__li48575151101429"></a><a name="li48575151101429"></a>EVS provides a variety of disk types for you to choose from, and EVS disks can be used as data disks and system disks for <span id="en-us_topic_0014580741__text18491994152222">servers</span>s. You can select an appropriate disk type that best suits your budget and service requirements.</p>
|
||||
</li><li id="en-us_topic_0014580741__li65165360101429">Elastic scalability<p id="en-us_topic_0014580741__p197126269377"><a name="en-us_topic_0014580741__li65165360101429"></a><a name="li65165360101429"></a>The EVS disk capacity ranges from 10 GiB to 32 TiB. When it no longer meets your needs, you can expand the disk capacity up to 32 TiB in increments of 1 GiB, without interrupting your applications.</p>
|
||||
<p id="en-us_topic_0014580741__p63823226165650">Besides the disk capacity limit, the additional space you can add cannot exceed the remaining quota. You can increase the quota if the remaining quota is insufficient.</p>
|
||||
</li><li id="en-us_topic_0014580741__li15632957165821">High security and reliability<ul id="en-us_topic_0014580741__ul5525852917154"><li id="en-us_topic_0014580741__li3920285417151">Both system disks and data disks support data encryption to ensure data security.</li><li id="en-us_topic_0014580741__li5591078717157">Data protection functions, such as backups and snapshots, safeguard the disk data, preventing incorrect data caused by application exceptions or attacks.</li></ul>
|
||||
</li><li id="en-us_topic_0014580741__li459714371739">Real-time monitoring<p id="en-us_topic_0014580741__p5447267517455"><a name="en-us_topic_0014580741__li459714371739"></a><a name="li459714371739"></a>On Cloud Eye, you can monitor the disk health and operating status at any time.</p>
|
||||
</li></ul>
|
||||
</div>
|
||||
<div class="section" id="en-us_topic_0014580741__section1930134616571"><h4 class="sectiontitle">Differences Among EVS, SFS, and OBS</h4><p id="en-us_topic_0014580741__p27363381709">Currently, there are three data storage services available for you to choose from: EVS, Scalable File Service (SFS), and Object Storage Service (OBS). The differences are described in the following table.</p>
|
||||
<div class="section" id="en-us_topic_0014580741__section1930134616571"><h4 class="sectiontitle">Differences Among EVS, SFS, and OBS</h4><p id="en-us_topic_0014580741__p27363381709">There are currently three types of storage available for you to choose from: EVS, Scalable File Service (SFS), and Object Storage Service (OBS). See their differences in the following table.</p>
|
||||
|
||||
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="en-us_topic_0014580741__table16325558582" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Differences among EVS, SFS, and OBS</caption><thead align="left"><tr id="en-us_topic_0014580741__row732685175810"><th align="left" class="cellrowborder" valign="top" width="12.121212121212121%" id="mcps1.3.3.3.2.5.1.1"><p id="en-us_topic_0014580741__p1932635165816">Service</p>
|
||||
</th>
|
||||
@ -27,29 +27,29 @@
|
||||
</thead>
|
||||
<tbody><tr id="en-us_topic_0014580741__row432613514586"><td class="cellrowborder" valign="top" width="12.121212121212121%" headers="mcps1.3.3.3.2.5.1.1 "><p id="en-us_topic_0014580741__p532615195814">EVS</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="27.272727272727277%" headers="mcps1.3.3.3.2.5.1.2 "><p id="en-us_topic_0014580741__p1326125145810">EVS provides scalable block storage that features high reliability, high performance, and rich specifications for servers.</p>
|
||||
<td class="cellrowborder" valign="top" width="27.272727272727277%" headers="mcps1.3.3.3.2.5.1.2 "><p id="en-us_topic_0014580741__p1326125145810">EVS provides scalable block storage that features high reliability, high performance, and a variety of specifications for servers.</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="30.303030303030305%" headers="mcps1.3.3.3.2.5.1.3 "><ul id="en-us_topic_0014580741__ul164276131815"><li id="en-us_topic_0014580741__li642186141820">Enterprise office applications</li><li id="en-us_topic_0014580741__li174212616185">Development and testing</li><li id="en-us_topic_0014580741__li194218619180">Enterprise applications, including SAP, Microsoft Exchange, and Microsoft SharePoint</li><li id="en-us_topic_0014580741__li942106171814">Distributed file systems</li><li id="en-us_topic_0014580741__li34212612187">Various databases, including MongoDB, Oracle, SQL Server, MySQL, and PostgreSQL</li></ul>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="30.303030303030305%" headers="mcps1.3.3.3.2.5.1.4 "><p id="en-us_topic_0014580741__p232614595816">EVS disks start at 10 GB and can be expanded as required in 1 GB increments to up to 32 TB.</p>
|
||||
<td class="cellrowborder" valign="top" width="30.303030303030305%" headers="mcps1.3.3.3.2.5.1.4 "><p id="en-us_topic_0014580741__p232614595816">EVS disks start at 10 GiB and can be expanded as required in 1 GiB increments to up to 32 TiB.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="en-us_topic_0014580741__row153268519589"><td class="cellrowborder" valign="top" width="12.121212121212121%" headers="mcps1.3.3.3.2.5.1.1 "><p id="en-us_topic_0014580741__p532617518581">SFS</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="27.272727272727277%" headers="mcps1.3.3.3.2.5.1.2 "><p id="en-us_topic_0014580741__p532625105815">SFS provides completely hosted sharable file storage for ECSs. Compatible with the Network File System (NFS) protocol, SFS is expandable to petabytes and seamlessly handles data-intensive and bandwidth-intensive applications.</p>
|
||||
<td class="cellrowborder" valign="top" width="27.272727272727277%" headers="mcps1.3.3.3.2.5.1.2 "><p id="en-us_topic_0014580741__p532625105815">SFS provides completely hosted shared file storage for cloud servers. Compatible with the Network File System (NFS) protocol, SFS is expandable to petabytes and seamlessly handles data-intensive and bandwidth-intensive applications.</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="30.303030303030305%" headers="mcps1.3.3.3.2.5.1.3 "><ul id="en-us_topic_0014580741__ul95941207219"><li id="en-us_topic_0014580741__li759419205212">HPC scenarios, such as gene sequencing, animation rendering, and CAD/CAE</li><li id="en-us_topic_0014580741__li35941920142115">File sharing</li><li id="en-us_topic_0014580741__li14594112015219">Media processing</li><li id="en-us_topic_0014580741__li8594172010215">Content management and web services</li><li id="en-us_topic_0014580741__li759482072119">Offline file backup</li></ul>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="30.303030303030305%" headers="mcps1.3.3.3.2.5.1.4 "><p id="en-us_topic_0014580741__p123260575818">SFS storage capacity is available on demand and can be expanded to 10 PB at most.</p>
|
||||
<td class="cellrowborder" valign="top" width="30.303030303030305%" headers="mcps1.3.3.3.2.5.1.4 "><p id="en-us_topic_0014580741__p123260575818">SFS storage capacity is available on demand and can be expanded to a maximum of 2 PB.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="en-us_topic_0014580741__row93265515815"><td class="cellrowborder" valign="top" width="12.121212121212121%" headers="mcps1.3.3.3.2.5.1.1 "><p id="en-us_topic_0014580741__p73267575812">OBS</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="27.272727272727277%" headers="mcps1.3.3.3.2.5.1.2 "><p id="en-us_topic_0014580741__p432612565815">OBS provides cloud storage for unstructured data, such as files, pictures, and videos. With multiple options for migration to the cloud, OBS provides low-cost, reliable storage access for massive data and supports online multimedia processing.</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="30.303030303030305%" headers="mcps1.3.3.3.2.5.1.3 "><ul id="en-us_topic_0014580741__ul19707131919259"><li id="en-us_topic_0014580741__li1070731910251">Enterprise backup and archive</li><li id="en-us_topic_0014580741__li0707131912257">Big data analysis</li><li id="en-us_topic_0014580741__li1170719196255">Enterprise cloud box</li><li id="en-us_topic_0014580741__li37077198259">Static website hosting</li><li id="en-us_topic_0014580741__li15707131915257">Native cloud applications</li></ul>
|
||||
<td class="cellrowborder" valign="top" width="30.303030303030305%" headers="mcps1.3.3.3.2.5.1.3 "><ul id="en-us_topic_0014580741__ul19707131919259"><li id="en-us_topic_0014580741__li1070731910251">Enterprise backup and archive</li><li id="en-us_topic_0014580741__li0707131912257">Big data analysis</li><li id="en-us_topic_0014580741__li1170719196255">Enterprise cloud box</li><li id="en-us_topic_0014580741__li37077198259">Static website hosting</li><li id="en-us_topic_0014580741__li15707131915257">Cloud-native applications</li></ul>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="30.303030303030305%" headers="mcps1.3.3.3.2.5.1.4 "><p id="en-us_topic_0014580741__p1532619517588">OBS provides limitless storage capacity, and storage resources are available for linear and nearly infinite expansion.</p>
|
||||
<td class="cellrowborder" valign="top" width="30.303030303030305%" headers="mcps1.3.3.3.2.5.1.4 "><p id="en-us_topic_0014580741__p1532619517588">OBS has limitless storage capacity, and storage resources are available for linear and nearly infinite expansion.</p>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
|
File diff suppressed because it is too large
Load Diff
@ -7,16 +7,17 @@
|
||||
</li><li id="en-us_topic_0017616396__li991285142411">For a data disk:<ul id="en-us_topic_0017616396__ul1454012918248"><li id="en-us_topic_0017616396__li14558134013452">If volume (D:) already exists, you can add the additional space to volume (D:) and use it as a data volume. For details, see <a href="#en-us_topic_0017616396__section20686303192651">Data Disk: Add Additional Space to Volume (D:)</a>.</li><li id="en-us_topic_0017616396__li1541894712411">If volume (D:) already exists, you can create a new volume such as volume (E:) with the additional space and use the new volume as a data volume. For details, see <a href="#en-us_topic_0017616396__section1971024320173">Data Disk: Create New Volume (E:) with Additional Space</a>.</li></ul>
|
||||
</li></ul>
|
||||
</div>
|
||||
<div class="p" id="en-us_topic_0017616396__p59916266192641">The method for allocating the additional space varies with the server OS. This section is used for reference only. For detailed operations and differences, see the corresponding OS documents.<div class="notice" id="en-us_topic_0017616396__evs_01_0109_note14531102154610"><span class="noticetitle"><img src="public_sys-resources/notice_3.0-en-us.png"> </span><div class="noticebody"><p id="en-us_topic_0017616396__p1185312105267">Performing the expansion operations with caution. Misoperation may lead to data loss or exceptions. Therefore, you are advised to back up the disk data using backups or snapshots before expansion. For details about backups, see <a href="evs_01_0110.html">Managing EVS Backup</a>. For details about snapshots, see <a href="en-us_topic_0066615262.html">Creating a Snapshot</a>.</p>
|
||||
<p id="en-us_topic_0017616396__p59916266192641">The method for allocating the additional space varies with the server OS. This section is used for reference only. For detailed operations and differences, see the corresponding OS documents.</p>
|
||||
<div class="p" id="en-us_topic_0017616396__p178283810327"><div class="notice" id="en-us_topic_0017616396__evs_01_0109_note14531102154610"><span class="noticetitle"><img src="public_sys-resources/notice_3.0-en-us.png"> </span><div class="noticebody"><p id="en-us_topic_0017616396__p1185312105267">Performing the expansion operations with caution. Misoperation may lead to data loss or exceptions. Therefore, you are advised to back up the disk data using CBR or snapshots before expansion. For details about using CBR, see <a href="evs_01_0110.html">Managing EVS Backups</a>. For details about using snapshots, see <a href="en-us_topic_0066615262.html">Creating a Snapshot</a>.</p>
|
||||
</div></div>
|
||||
</div>
|
||||
</div>
|
||||
<div class="section" id="en-us_topic_0017616396__section51503350171737"><h4 class="sectiontitle">Prerequisites</h4><ul id="en-us_topic_0017616396__ul28913191171813"><li id="en-us_topic_0017616396__li1233185612427">You have expanded the disk capacity and attached the disk to a <span id="en-us_topic_0017616396__text1252119719467">server</span> on the management console. For details, see <a href="evs_01_0007.html">Expanding Capacity for an In-use EVS Disk</a> or <a href="evs_01_0008.html">Expanding Capacity for an Available EVS Disk</a>.</li><li id="en-us_topic_0017616396__li36962755115557">You have logged in to the <span id="en-us_topic_0017616396__evs_01_0108_text25940422717248">server</span>.<ul id="en-us_topic_0017616396__evs_01_0108_ul6229092211568"><li id="en-us_topic_0017616396__evs_01_0108_li197989548398">For how to log in to an ECS, see the <em id="en-us_topic_0017616396__evs_01_0108_i157642033171941">Elastic Cloud Server User Guide</em>.</li><li id="en-us_topic_0017616396__evs_01_0108_li7220898115452">For how to log in to a BMS, see the <em id="en-us_topic_0017616396__evs_01_0108_i842352697172014">Bare Metal Server User Guide</em>.</li></ul>
|
||||
</li></ul>
|
||||
</div>
|
||||
<div class="section" id="en-us_topic_0017616396__section56589192192644"><a name="en-us_topic_0017616396__section56589192192644"></a><a name="section56589192192644"></a><h4 class="sectiontitle">System Disk: Add Additional Space to Volume (C:)</h4><p id="en-us_topic_0017616396__p1343510431966">In this example, the system disk has 50 GB originally, and 22 GB is added on the management console. The following procedure describes how to add this 22 GB to volume (C:) on the <span id="en-us_topic_0017616396__text5435204313618">server</span>. After the operation is complete, volume (C:) will have 72 GB of capacity and can be used as a system volume.</p>
|
||||
<div class="section" id="en-us_topic_0017616396__section56589192192644"><a name="en-us_topic_0017616396__section56589192192644"></a><a name="section56589192192644"></a><h4 class="sectiontitle">System Disk: Add Additional Space to Volume (C:)</h4><p id="en-us_topic_0017616396__p1343510431966">In this example, the system disk has 50 GiB originally, and 22 GiB is added on the management console. The following procedure describes how to add this 22 GiB to volume (C:) on the <span id="en-us_topic_0017616396__text5435204313618">server</span>. After the operation is complete, volume (C:) will have 72 GiB of capacity and can be used as a system volume.</p>
|
||||
<ol id="en-us_topic_0017616396__ol5496492819287"><li id="en-us_topic_0017616396__li2352354193036"><span>On the desktop of <span id="en-us_topic_0017616396__evs_01_0108_text1022506145191911">the server</span>, right-click <strong id="en-us_topic_0017616396__evs_01_0108_b8423527069913">Computer</strong> and choose <strong id="en-us_topic_0017616396__evs_01_0108_b8423527069917">Manage</strong> from the shortcut menu.</span><p><p id="en-us_topic_0017616396__evs_01_0108_p31139349281">The <strong id="en-us_topic_0017616396__evs_01_0108_b84235270616471">Server Manager</strong> window is displayed.</p>
|
||||
</p></li><li id="en-us_topic_0017616396__li2054728419308"><span>In the navigation tree, choose <strong>Storage</strong> > <strong>Disk Management</strong>.</span><p><p id="en-us_topic_0017616396__p3976828016384">The <strong id="en-us_topic_0017616396__b842352706164914">Disk Management</strong> window is displayed.</p>
|
||||
</p></li><li id="en-us_topic_0017616396__li2054728419308"><span>In the navigation tree, choose <strong id="en-us_topic_0017616396__b1666716537390">Storage</strong> > <strong id="en-us_topic_0017616396__b176671453143913">Disk Management</strong>.</span><p><p id="en-us_topic_0017616396__p3976828016384">The <strong id="en-us_topic_0017616396__b842352706164914">Disk Management</strong> window is displayed.</p>
|
||||
<div class="fignone" id="en-us_topic_0017616396__fig1686908719287"><span class="figcap"><b>Figure 1 </b>Disk Management (system disk)</span><br><span><img id="en-us_topic_0017616396__image5407012619287" src="en-us_image_0090103571.png"></span></div>
|
||||
<div class="note" id="en-us_topic_0017616396__note3512746779"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="en-us_topic_0017616396__p851284617711">If you cannot view the additional space, right-click <strong id="en-us_topic_0017616396__b159939121534">Disk Management</strong> and choose <strong id="en-us_topic_0017616396__b15547542144">Refresh</strong> from the shortcut menu.</p>
|
||||
</div></div>
|
||||
@ -27,36 +28,36 @@
|
||||
</div>
|
||||
</p></li></ol>
|
||||
</div>
|
||||
<div class="section" id="en-us_topic_0017616396__section17412322419"><a name="en-us_topic_0017616396__section17412322419"></a><a name="section17412322419"></a><h4 class="sectiontitle">System Disk: Create New Volume (F:) with Additional Space</h4><p id="en-us_topic_0017616396__p274732746">In this example, the system disk has 40 GB originally, and 60 GB is added on the management console. The following procedure describes how to use this 60 GB to create a new volume, for example volume (F:), on the <span id="en-us_topic_0017616396__text181354510611">server</span>. After the operation is complete, new volume (F:) has 60 GB of capacity and can be used as a data volume.</p>
|
||||
<div class="section" id="en-us_topic_0017616396__section17412322419"><a name="en-us_topic_0017616396__section17412322419"></a><a name="section17412322419"></a><h4 class="sectiontitle">System Disk: Create New Volume (F:) with Additional Space</h4><p id="en-us_topic_0017616396__p274732746">In this example, the system disk has 40 GiB originally, and 60 GiB is added on the management console. The following procedure describes how to use this 60 GiB to create a new volume, for example volume (F:), on the <span id="en-us_topic_0017616396__text181354510611">server</span>. After the operation is complete, new volume (F:) has 60 GiB of capacity and can be used as a data volume.</p>
|
||||
<ol id="en-us_topic_0017616396__ol167413321743"><li id="en-us_topic_0017616396__li197410321447"><span>On the desktop of <span id="en-us_topic_0017616396__evs_01_0108_text1022506145191911_1">the server</span>, right-click <strong id="en-us_topic_0017616396__evs_01_0108_b8423527069913_1">Computer</strong> and choose <strong id="en-us_topic_0017616396__evs_01_0108_b8423527069917_1">Manage</strong> from the shortcut menu.</span><p><p id="en-us_topic_0017616396__evs_01_0108_p31139349281_1">The <strong id="en-us_topic_0017616396__evs_01_0108_b84235270616471_1">Server Manager</strong> window is displayed.</p>
|
||||
</p></li><li id="en-us_topic_0017616396__li157512327412"><span>In the navigation tree, choose <strong id="en-us_topic_0017616396__b103875716104">Storage</strong> > <strong id="en-us_topic_0017616396__b14389177131010">Disk Management</strong>.</span><p><div class="p" id="en-us_topic_0017616396__p19751332541">The <strong id="en-us_topic_0017616396__b128367657">Disk Management</strong> window is displayed.<div class="fignone" id="en-us_topic_0017616396__fig1875632841"><span class="figcap"><b>Figure 6 </b>Refresh (system disk)</span><br><span><img id="en-us_topic_0017616396__image66891953171811" src="en-us_image_0169144806.png"></span></div>
|
||||
</p></li><li id="en-us_topic_0017616396__li157512327412"><span>In the navigation tree, choose <strong id="en-us_topic_0017616396__b103875716104">Storage</strong> > <strong id="en-us_topic_0017616396__b14389177131010">Disk Management</strong>.</span><p><div class="p" id="en-us_topic_0017616396__p19751332541">The <strong id="en-us_topic_0017616396__b1232609127">Disk Management</strong> window is displayed.<div class="fignone" id="en-us_topic_0017616396__fig1875632841"><span class="figcap"><b>Figure 6 </b>Refresh (system disk)</span><br><span><img id="en-us_topic_0017616396__image66891953171811" src="en-us_image_0169144806.png"></span></div>
|
||||
</div>
|
||||
</p></li><li id="en-us_topic_0017616396__li875163214413"><span>If you cannot view the additional space, right-click <strong id="en-us_topic_0017616396__b914219411100">Disk Management</strong> and choose <strong id="en-us_topic_0017616396__b17143124110103">Refresh</strong> from the shortcut menu.</span><p><p id="en-us_topic_0017616396__p16756328415">After the refresh, the additional space is displayed in the right area and is unallocated.</p>
|
||||
<div class="fignone" id="en-us_topic_0017616396__fig107563216410"><span class="figcap"><b>Figure 7 </b>Unallocated disk space (system disk)</span><br><span><img id="en-us_topic_0017616396__image711891321912" src="en-us_image_0169144807.png"></span></div>
|
||||
</p></li><li id="en-us_topic_0017616396__li12766321042"><span>In the <strong id="en-us_topic_0017616396__b842352706135315">Unallocated</strong> area of <strong id="en-us_topic_0017616396__b22613381399">Disk 0</strong>, right-click the blank area and choose <strong id="en-us_topic_0017616396__b842352706135329">New Simple Volume</strong>.</span><p><div class="fignone" id="en-us_topic_0017616396__fig376153211419"><span class="figcap"><b>Figure 8 </b>New Simple Volume (system disk)</span><br><span><img id="en-us_topic_0017616396__image1899174714197" src="en-us_image_0169144808.png"></span></div>
|
||||
</p></li><li id="en-us_topic_0017616396__li6768321412"><span>On the displayed <strong id="en-us_topic_0017616396__b1212334243">New Simple Volume Wizard</strong> window, click <strong id="en-us_topic_0017616396__b256852583">Next</strong>.</span><p><div class="fignone" id="en-us_topic_0017616396__fig57610321448"><span class="figcap"><b>Figure 9 </b>New Simple Volume Wizard (system disk)</span><br><span><img id="en-us_topic_0017616396__image12260121113203" src="en-us_image_0169144809.png"></span></div>
|
||||
</p></li><li id="en-us_topic_0017616396__li6768321412"><span>On the displayed <strong id="en-us_topic_0017616396__b1165276520">New Simple Volume Wizard</strong> window, click <strong id="en-us_topic_0017616396__b222222712">Next</strong>.</span><p><div class="fignone" id="en-us_topic_0017616396__fig57610321448"><span class="figcap"><b>Figure 9 </b>New Simple Volume Wizard (system disk)</span><br><span><img id="en-us_topic_0017616396__image12260121113203" src="en-us_image_0169144809.png"></span></div>
|
||||
</p></li><li id="en-us_topic_0017616396__li4767322042"><span>On the displayed <strong id="en-us_topic_0017616396__b1867164520352">Specify Volume Size</strong> page, set <strong id="en-us_topic_0017616396__b19504446103612">Simple volume size in MB</strong> and click <strong id="en-us_topic_0017616396__b76761448103610">Next</strong>. In this example, the default size is used.</span><p><div class="fignone" id="en-us_topic_0017616396__fig157611321419"><span class="figcap"><b>Figure 10 </b>Specify Volume Size (system disk)</span><br><span><img id="en-us_topic_0017616396__image11550747152110" src="en-us_image_0169144810.png"></span></div>
|
||||
</p></li><li id="en-us_topic_0017616396__li12761232245"><span>On the displayed <strong id="en-us_topic_0017616396__b15944143023716">Assign Drive Letter and Path</strong> page, click <strong id="en-us_topic_0017616396__b555615235389">Assign the following drive letter</strong>, select a drive letter, and click <strong id="en-us_topic_0017616396__b2202328123815">Next</strong>. In this example, drive letter <strong id="en-us_topic_0017616396__b186141931103816">F</strong> is selected.</span><p><div class="fignone" id="en-us_topic_0017616396__fig1576332646"><span class="figcap"><b>Figure 11 </b>Assign Driver Letter or Path (system disk)</span><br><span><img id="en-us_topic_0017616396__image771821910228" src="en-us_image_0169144811.png"></span></div>
|
||||
</p></li><li id="en-us_topic_0017616396__li1377332941"><span>On the displayed <strong id="en-us_topic_0017616396__b1246717517391">Format Partition</strong> page, click <strong id="en-us_topic_0017616396__b842352706114214">Format this volume with the following settings</strong>, set parameters based on the requirements, and select <strong id="en-us_topic_0017616396__b84235270611450">Perform a quick format</strong>. Then, click <strong id="en-us_topic_0017616396__b842352706114350">Next</strong>.</span><p><div class="fignone" id="en-us_topic_0017616396__fig3771732147"><span class="figcap"><b>Figure 12 </b>Format Partition (system disk)</span><br><span><img id="en-us_topic_0017616396__image12212102813254" src="en-us_image_0169144812.png"></span></div>
|
||||
</p></li><li id="en-us_topic_0017616396__li577432249"><span>Click <strong id="en-us_topic_0017616396__b1052073845">Finish</strong>.</span><p><div class="p" id="en-us_topic_0017616396__p207753217416">After the expansion succeeded, new volume (F:) is displayed.<div class="fignone" id="en-us_topic_0017616396__fig16777321443"><span class="figcap"><b>Figure 13 </b>Completing the New Simple Volume Wizard (new volume F:)</span><br><span><img id="en-us_topic_0017616396__image136391820102716" src="en-us_image_0169144813.png"></span></div>
|
||||
</p></li><li id="en-us_topic_0017616396__li577432249"><span>Click <strong id="en-us_topic_0017616396__b782329693">Finish</strong>.</span><p><div class="p" id="en-us_topic_0017616396__p207753217416">After the expansion succeeded, new volume (F:) is displayed.<div class="fignone" id="en-us_topic_0017616396__fig16777321443"><span class="figcap"><b>Figure 13 </b>Completing the New Simple Volume Wizard (new volume F:)</span><br><span><img id="en-us_topic_0017616396__image136391820102716" src="en-us_image_0169144813.png"></span></div>
|
||||
<div class="fignone" id="en-us_topic_0017616396__fig207719321442"><span class="figcap"><b>Figure 14 </b>New Volume (F:)</span><br><span><img id="en-us_topic_0017616396__image7314144315271" src="en-us_image_0169144814.png"></span></div>
|
||||
</div>
|
||||
</p></li></ol>
|
||||
</div>
|
||||
<div class="section" id="en-us_topic_0017616396__section20686303192651"><a name="en-us_topic_0017616396__section20686303192651"></a><a name="section20686303192651"></a><h4 class="sectiontitle">Data Disk: Add Additional Space to Volume (D:)</h4><p id="en-us_topic_0017616396__p669313019125">In this example, the data disk has 100 GB originally, and 50 GB is added on the management console. The following procedure describes how to add this 50 GB to volume (D:) on the <span id="en-us_topic_0017616396__text87851614191716">server</span>. After the operation is complete, volume (D:) has 150 GB of capacity and can be used as a data volume.</p>
|
||||
<div class="section" id="en-us_topic_0017616396__section20686303192651"><a name="en-us_topic_0017616396__section20686303192651"></a><a name="section20686303192651"></a><h4 class="sectiontitle">Data Disk: Add Additional Space to Volume (D:)</h4><p id="en-us_topic_0017616396__p669313019125">In this example, the data disk has 100 GiB originally, and 50 GiB is added on the management console. The following procedure describes how to add this 50 GiB to volume (D:) on the <span id="en-us_topic_0017616396__text87851614191716">server</span>. After the operation is complete, volume (D:) has 150 GiB of capacity and can be used as a data volume.</p>
|
||||
<ol id="en-us_topic_0017616396__ol27623611193332"><li id="en-us_topic_0017616396__li61412975193448"><span>On the desktop of <span id="en-us_topic_0017616396__evs_01_0108_text1022506145191911_2">the server</span>, right-click <strong id="en-us_topic_0017616396__evs_01_0108_b8423527069913_2">Computer</strong> and choose <strong id="en-us_topic_0017616396__evs_01_0108_b8423527069917_2">Manage</strong> from the shortcut menu.</span><p><p id="en-us_topic_0017616396__evs_01_0108_p31139349281_2">The <strong id="en-us_topic_0017616396__evs_01_0108_b84235270616471_2">Server Manager</strong> window is displayed.</p>
|
||||
</p></li><li id="en-us_topic_0017616396__li8446716193448"><span>In the navigation tree, choose <strong>Storage</strong> > <strong>Disk Management</strong>.</span><p><div class="p" id="en-us_topic_0017616396__p035542853018">The <strong id="en-us_topic_0017616396__b167430524">Disk Management</strong> window is displayed.<div class="fignone" id="en-us_topic_0017616396__fig129789723114"><span class="figcap"><b>Figure 15 </b>Disk Management (data disk)</span><br><span><img id="en-us_topic_0017616396__image109782783117" src="en-us_image_0125151939.png"></span></div>
|
||||
</p></li><li id="en-us_topic_0017616396__li8446716193448"><span>In the navigation tree, choose <strong id="en-us_topic_0017616396__b5694953193916">Storage</strong> > <strong id="en-us_topic_0017616396__b18694553173918">Disk Management</strong>.</span><p><div class="p" id="en-us_topic_0017616396__p035542853018">The <strong id="en-us_topic_0017616396__b1050789298">Disk Management</strong> window is displayed.<div class="fignone" id="en-us_topic_0017616396__fig129789723114"><span class="figcap"><b>Figure 15 </b>Disk Management (data disk)</span><br><span><img id="en-us_topic_0017616396__image109782783117" src="en-us_image_0125151939.png"></span></div>
|
||||
<div class="note" id="en-us_topic_0017616396__note476152318"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="en-us_topic_0017616396__p1282015235">If you cannot view the additional space, right-click <strong id="en-us_topic_0017616396__b198761901814">Disk Management</strong> and choose <strong id="en-us_topic_0017616396__b13881319141812">Refresh</strong> from the shortcut menu.</p>
|
||||
</div></div>
|
||||
</div>
|
||||
</p></li><li id="en-us_topic_0017616396__li33918592193332"><span>On the <strong id="en-us_topic_0017616396__b1831513284185">Disk Management</strong> page, select the disk and volume that you want to extend. The current volume size and unallocated space are displayed.</span></li><li id="en-us_topic_0017616396__li62028663193332"><span>Right-click the target volume and choose <strong id="en-us_topic_0017616396__b820573551816">Extend Volume</strong>.</span><p><div class="fignone" id="en-us_topic_0017616396__fig6892073193332"><span class="figcap"><b>Figure 16 </b>Choosing Extend Volume (Windows Server 2008)</span><br><span><img id="en-us_topic_0017616396__image30591947193332" src="en-us_image_0044524713.png"></span></div>
|
||||
</p></li><li id="en-us_topic_0017616396__li62995723193332"><span>On the displayed <strong id="en-us_topic_0017616396__b1982522809">Extend Volume Wizard</strong> window, click <strong id="en-us_topic_0017616396__b200688008">Next</strong>.</span><p><div class="fignone" id="en-us_topic_0017616396__fig21912605193332"><span class="figcap"><b>Figure 17 </b>Extend Volume Wizard (Windows Server 2008)</span><br><span><img id="en-us_topic_0017616396__image54630517193332" src="en-us_image_0044524709.png"></span></div>
|
||||
</p></li><li id="en-us_topic_0017616396__li57253488193332"><span>In the text box to the right of <strong id="en-us_topic_0017616396__b437099005">Select the amount of space in MB</strong>, enter the amount of the additional space and click <strong id="en-us_topic_0017616396__b1349783111">Next</strong>.</span><p><div class="fignone" id="en-us_topic_0017616396__fig58557281193332"><span class="figcap"><b>Figure 18 </b>Selecting space (Windows Server 2008)</span><br><span><img id="en-us_topic_0017616396__image21419445193332" src="en-us_image_0044524739.png"></span></div>
|
||||
</p></li><li id="en-us_topic_0017616396__li4899766193631"><span>Click <strong id="en-us_topic_0017616396__b780091545">Finish</strong>.</span><p><div class="p" id="en-us_topic_0017616396__p14843917193634">After the expansion succeeded, the partition size is larger than the original size.<div class="fignone" id="en-us_topic_0017616396__fig31824203193332"><span class="figcap"><b>Figure 19 </b>Capacity expansion succeeded (Windows Server 2008)</span><br><span><img id="en-us_topic_0017616396__image63188346193332" src="en-us_image_0044524683.png"></span></div>
|
||||
</p></li><li id="en-us_topic_0017616396__li62995723193332"><span>On the displayed <strong id="en-us_topic_0017616396__b818955131">Extend Volume Wizard</strong> window, click <strong id="en-us_topic_0017616396__b295705305">Next</strong>.</span><p><div class="fignone" id="en-us_topic_0017616396__fig21912605193332"><span class="figcap"><b>Figure 17 </b>Extend Volume Wizard (Windows Server 2008)</span><br><span><img id="en-us_topic_0017616396__image54630517193332" src="en-us_image_0044524709.png"></span></div>
|
||||
</p></li><li id="en-us_topic_0017616396__li57253488193332"><span>In the text box to the right of <strong id="en-us_topic_0017616396__b1930261090">Select the amount of space in MB</strong>, enter the amount of the additional space and click <strong id="en-us_topic_0017616396__b1454878046">Next</strong>.</span><p><div class="fignone" id="en-us_topic_0017616396__fig58557281193332"><span class="figcap"><b>Figure 18 </b>Selecting space (Windows Server 2008)</span><br><span><img id="en-us_topic_0017616396__image21419445193332" src="en-us_image_0044524739.png"></span></div>
|
||||
</p></li><li id="en-us_topic_0017616396__li4899766193631"><span>Click <strong id="en-us_topic_0017616396__b879424759">Finish</strong>.</span><p><div class="p" id="en-us_topic_0017616396__p14843917193634">After the expansion succeeded, the partition size is larger than the original size.<div class="fignone" id="en-us_topic_0017616396__fig31824203193332"><span class="figcap"><b>Figure 19 </b>Capacity expansion succeeded (Windows Server 2008)</span><br><span><img id="en-us_topic_0017616396__image63188346193332" src="en-us_image_0044524683.png"></span></div>
|
||||
</div>
|
||||
</p></li></ol>
|
||||
</div>
|
||||
<div class="section" id="en-us_topic_0017616396__section1971024320173"><a name="en-us_topic_0017616396__section1971024320173"></a><a name="section1971024320173"></a><h4 class="sectiontitle">Data Disk: Create New Volume (E:) with Additional Space</h4><p id="en-us_topic_0017616396__p1850844821712">In this example, the data disk has 40 GB originally, and 60 GB is added on the management console. The following procedure describes how to use this 60 GB to create a new volume, for example volume (E:), on the <span id="en-us_topic_0017616396__text15638191515197">server</span>. After the operation is complete, new volume (E:) has 60 GB of capacity and can be used as a data volume.</p>
|
||||
<div class="section" id="en-us_topic_0017616396__section1971024320173"><a name="en-us_topic_0017616396__section1971024320173"></a><a name="section1971024320173"></a><h4 class="sectiontitle">Data Disk: Create New Volume (E:) with Additional Space</h4><p id="en-us_topic_0017616396__p1850844821712">In this example, the data disk has 40 GiB originally, and 60 GiB is added on the management console. The following procedure describes how to use this 60 GiB to create a new volume, for example volume (E:), on the <span id="en-us_topic_0017616396__text15638191515197">server</span>. After the operation is complete, new volume (E:) has 60 GiB of capacity and can be used as a data volume.</p>
|
||||
<ol id="en-us_topic_0017616396__ol75081948131713"><li id="en-us_topic_0017616396__li55081448151714"><span>On the desktop of <span id="en-us_topic_0017616396__evs_01_0108_text1022506145191911_3">the server</span>, right-click <strong id="en-us_topic_0017616396__evs_01_0108_b8423527069913_3">Computer</strong> and choose <strong id="en-us_topic_0017616396__evs_01_0108_b8423527069917_3">Manage</strong> from the shortcut menu.</span><p><p id="en-us_topic_0017616396__evs_01_0108_p31139349281_3">The <strong id="en-us_topic_0017616396__evs_01_0108_b84235270616471_3">Server Manager</strong> window is displayed.</p>
|
||||
</p></li><li id="en-us_topic_0017616396__li18509204881718"><span>In the navigation tree, choose <strong id="en-us_topic_0017616396__b17695134302019">Storage</strong> > <strong id="en-us_topic_0017616396__b669734319201">Disk Management</strong>.</span><p><div class="p" id="en-us_topic_0017616396__p1450914489177">The <strong id="en-us_topic_0017616396__b964012467206">Disk Management</strong> window is displayed.<div class="fignone" id="en-us_topic_0017616396__fig1850964851716"><span class="figcap"><b>Figure 20 </b>Refresh (data disk)</span><br><span><img id="en-us_topic_0017616396__image135431219113117" src="en-us_image_0169138641.png"></span></div>
|
||||
</div>
|
||||
|
File diff suppressed because it is too large
Load Diff
@ -2,12 +2,12 @@
|
||||
|
||||
<h1 class="topictitle1">Shared EVS Disks and Usage Instructions</h1>
|
||||
<div id="body1506325324297"><div class="section" id="en-us_topic_0032860759__section14853146154645"><h4 class="sectiontitle">What Are Shared EVS Disks?</h4><p id="en-us_topic_0032860759__p23931035154645">Shared EVS disks are block storage devices that support concurrent read/write operations and can be attached to multiple <span id="en-us_topic_0032860759__text1202456375165636">servers</span>. Shared EVS disks feature multiple attachments, high-concurrency, high-performance, and high-reliability. They are usually used for enterprise business-critical applications that require cluster deployment. Multiple <span id="en-us_topic_0032860759__text4727122119232">servers</span> can access the same shared EVS disk at the same time.</p>
|
||||
<p id="en-us_topic_0032860759__p34083125112">A shared EVS disk can be attached to a maximum of 16 <span id="en-us_topic_0032860759__text18175184004110">servers</span>. Servers that EVS supports include ECSs and BMSs. To achieve file sharing, you need to deploy a shared file system or a cluster management system, such as Windows MSCS, Veritas VCS, or CFS.</p>
|
||||
<div class="notice" id="en-us_topic_0032860759__note1821913121217"><span class="noticetitle"><img src="public_sys-resources/notice_3.0-en-us.png"> </span><div class="noticebody"><p id="en-us_topic_0032860759__p12821713141210">To use shared EVS disks, you must set up a shared file system or similar cluster management system. If you directly attach EVS disks to multiple <span id="en-us_topic_0032860759__text1428819444147">server</span>s, the EVS disks cannot be shared and data may be overwritten.</p>
|
||||
<p id="en-us_topic_0032860759__p34083125112">A shared EVS disk can be attached to a maximum of 16 <span id="en-us_topic_0032860759__text18175184004110">servers</span>. Servers that EVS supports include ECSs and BMSs. To share files, you need to deploy a shared file system or a cluster management system, such as Windows MSCS, Veritas VCS, or CFS.</p>
|
||||
<div class="notice" id="en-us_topic_0032860759__note1821913121217"><span class="noticetitle"><img src="public_sys-resources/notice_3.0-en-us.png"> </span><div class="noticebody"><p id="en-us_topic_0032860759__p12821713141210">You must set up a shared file system or cluster management system before using shared EVS disks. If you directly attach a disk to multiple <span id="en-us_topic_0032860759__text1888310409388">server</span>s, the sharing function will not work and data may be overwritten.</p>
|
||||
</div></div>
|
||||
</div>
|
||||
<div class="fignone" id="en-us_topic_0032860759__fig186617301262"><span class="figcap"><b>Figure 1 </b>Application scenario of shared EVS disks</span><br><span><img id="en-us_topic_0032860759__image086623019618" src="en-us_image_0197136031.png"></span></div>
|
||||
<div class="section" id="en-us_topic_0032860759__section20091124154758"><h4 class="sectiontitle">Usage Precautions</h4><p id="en-us_topic_0032860759__p680541418427">Most common clusters, such as Windows MSCS and Veritas VCS and CFS, require SCSI reservations. Therefore, you are advised to use shared SCSI EVS disks for clusters. If a SCSI EVS disk is attached to a Xen ECS for use, you must install the driver. For details, see <a href="en-us_topic_0052554220.html">Device Types and Usage Instructions</a>.</p>
|
||||
<div class="section" id="en-us_topic_0032860759__section20091124154758"><h4 class="sectiontitle">Usage Precautions</h4><p id="en-us_topic_0032860759__p680541418427">Because most cluster applications, such as Windows MSCS, Veritas VCS, and Veritas CFS, require SCSI reservations, you are advised to use shared EVS disks with SCSI. If a SCSI EVS disk is attached to a Xen ECS for use, you must install the driver. For details, see <a href="en-us_topic_0052554220.html">Device Types and Usage Instructions</a>.</p>
|
||||
<div class="p" id="en-us_topic_0032860759__p133731412155317">You can create shared VBD disks or shared SCSI disks. It is recommended that you attach the shared disk to the ECSs in the same ECS group to improve service reliability.<ul id="en-us_topic_0032860759__evs_01_0010_ul290254221927"><li id="en-us_topic_0032860759__evs_01_0010_li54944535221927">Shared VBD EVS disks: The device type of a newly created shared EVS disk is VBD by default. Such disks can be used as virtual block storage devices, but do not support SCSI reservations. If SCSI reservations are required for your applications, create shared SCSI EVS disks.</li><li id="en-us_topic_0032860759__evs_01_0010_li59684574221927">Shared SCSI EVS disks: These EVS disks support SCSI reservations.<div class="notice" id="en-us_topic_0032860759__evs_01_0010_note57683778221927"><span class="noticetitle"><img src="public_sys-resources/notice_3.0-en-us.png"> </span><div class="noticebody"><ul id="en-us_topic_0032860759__evs_01_0010_ul8479164912431"><li id="en-us_topic_0032860759__evs_01_0010_li34792499432">To improve data security, you are advised to use SCSI reservations together with the anti-affinity policy of an ECS group. That said, ensure that shared SCSI EVS disks are only attached to ECSs in the same anti-affinity ECS group.</li><li id="en-us_topic_0032860759__evs_01_0010_li67215539435">If an ECS does not belong to any anti-affinity ECS group, you are advised not to attach shared SCSI EVS disks to this ECS. Otherwise, SCSI reservations may not work properly, which may put your data at risk.</li></ul>
|
||||
</div></div>
|
||||
<p id="en-us_topic_0032860759__evs_01_0010_p25421542202933">Concepts of the anti-affinity ECS group and SCSI reservations:</p>
|
||||
@ -16,9 +16,9 @@
|
||||
</li></ul>
|
||||
</div>
|
||||
</div>
|
||||
<div class="section" id="en-us_topic_0032860759__section14238006154818"><h4 class="sectiontitle">Advantages</h4><ul id="en-us_topic_0032860759__ul9580578154818"><li id="en-us_topic_0032860759__li17861603154818">Multiple attachments: A shared EVS disk can be attached to a maximum of 16 <span id="en-us_topic_0032860759__text1908525931165848">servers</span>.</li><li id="en-us_topic_0032860759__li37750119154818">High-performance: When multiple <span id="en-us_topic_0032860759__text631095566165942">servers</span> concurrently access a shared ultra-high I/O EVS disk, random read/write IOPS can reach up to 160,000.</li><li id="en-us_topic_0032860759__li21255070154818">High-reliability: Shared EVS disks support both manual and automatic backup, delivering highly reliable data storage.</li><li id="en-us_topic_0032860759__li62322105154818">Wide application scenarios: Shared EVS disks can be used for Linux RHCS clusters where only VBD EVS disks are needed. Whereas, they can also be used for Windows MSCS and Veritas VCS clusters that require SCSI reservations.</li></ul>
|
||||
<div class="section" id="en-us_topic_0032860759__section14238006154818"><h4 class="sectiontitle">Advantages</h4><ul id="en-us_topic_0032860759__ul9580578154818"><li id="en-us_topic_0032860759__li17861603154818">Multiple attachments: A shared EVS disk can be attached to a maximum of 16 <span id="en-us_topic_0032860759__text1908525931165848">servers</span>.</li><li id="en-us_topic_0032860759__li37750119154818">High-performance: The random read/write IOPS of a shared ultra-high I/O disk can reach up to 160,000.</li><li id="en-us_topic_0032860759__li21255070154818">High-reliability: Shared EVS disks support both manual and automatic backup, delivering highly reliable data storage.</li><li id="en-us_topic_0032860759__li62322105154818">Wide range of use: Shared EVS disks can be used for Linux RHCS clusters where only VBD EVS disks are needed. They can also be used for Windows MSCS and Veritas VCS clusters that require SCSI reservations.</li></ul>
|
||||
</div>
|
||||
<div class="section" id="en-us_topic_0032860759__section2163128202216"><h4 class="sectiontitle">Specifications and Performance</h4><p id="en-us_topic_0032860759__p1779261542215">The specifications and performance of shared EVS disks are the same as those of non-shared EVS disks. For details, see <a href="en-us_topic_0014580744.html">Disk Types and Performance</a>.</p>
|
||||
<div class="section" id="en-us_topic_0032860759__section2163128202216"><h4 class="sectiontitle">Specifications and Performance</h4><p id="en-us_topic_0032860759__p1779261542215">Shared EVS disks have the same specifications and performance as non-shared EVS disks. For details, see <a href="en-us_topic_0014580744.html">Disk Types and Performance</a>.</p>
|
||||
</div>
|
||||
<div class="section" id="en-us_topic_0032860759__section23510620221927"><h4 class="sectiontitle">Data Sharing Principle and Common Usage Mistakes</h4><p id="en-us_topic_0032860759__p3186456916184">A shared EVS disk is essentially the disk that can be attached to multiple <span id="en-us_topic_0032860759__text176062173819384">servers</span> for use, which is similar to a physical disk in that the disk can be attached to multiple physical servers, and each server can read data from and write data into any space on the disk. If the data read/write rules, such as the read/write sequence and meaning, between these servers are not defined, data read/write interference between servers or other unpredictable errors may occur.</p>
|
||||
<p id="en-us_topic_0032860759__p885410333452">Though shared EVS disks are block storage devices that provide shared access for <span id="en-us_topic_0032860759__text1369390954191359">servers</span>, shared EVS disks do not have the cluster management capability. Therefore, you need to deploy a cluster system to manage shared EVS disks. Common cluster management systems include Windows MSCS, Linux RHCS, Veritas VCS, and Veritas CFS.</p>
|
||||
@ -29,7 +29,7 @@
|
||||
</li></ul>
|
||||
</div>
|
||||
<p id="en-us_topic_0032860759__p53108593165417">Before you attach a shared EVS disk to multiple <span id="en-us_topic_0032860759__text183449198819124">servers</span>, the disk device type needs to be determined. The device type can be either VBD or SCSI. Shared SCSI EVS disks support SCSI reservations. Before using SCSI reservations, you need to install a driver in <span id="en-us_topic_0032860759__text885114752191336">the server</span> OS and ensure that the OS image is included in the compatibility list.</p>
|
||||
<p id="en-us_topic_0032860759__p48653461174019">For details about the usages of shared EVS disks, see <a href="evs_01_0010.html">Managing a Shared EVS Disk</a>.</p>
|
||||
<p id="en-us_topic_0032860759__p48653461174019">For details about the usages of shared EVS disks, see <a href="evs_01_0010.html">Managing Shared EVS Disks</a>.</p>
|
||||
<div class="notice" id="en-us_topic_0032860759__note60886722162923"><span class="noticetitle"><img src="public_sys-resources/notice_3.0-en-us.png"> </span><div class="noticebody"><p id="en-us_topic_0032860759__p11109594162923">If you simply attach a shared EVS disk to multiple <span id="en-us_topic_0032860759__text1879706293191451">servers</span>, files cannot be shared between the <span id="en-us_topic_0032860759__text1342408225191536">servers</span> as shared EVS disks do not have the cluster capability. Therefore, build a shared file system or deploy a cluster management system if you need to share files between <span id="en-us_topic_0032860759__text1454148709191822">servers</span>. </p>
|
||||
</div></div>
|
||||
</div>
|
||||
|
@ -5,10 +5,10 @@
|
||||
</div>
|
||||
<p id="en-us_topic_0052554220__p1669516467462">Device type is configured during creation. It cannot be changed after the disk has been created.</p>
|
||||
</div>
|
||||
<div class="section" id="en-us_topic_0052554220__section5554506411"><h4 class="sectiontitle">Common Application Scenarios and Usage Instructions of SCSI EVS Disks</h4><ul id="en-us_topic_0052554220__ul649313366412"><li id="en-us_topic_0052554220__li16493193619415">BMSs support only SCSI EVS disks.</li><li id="en-us_topic_0052554220__li72111959105511">Shared SCSI EVS disks: Shared SCSI EVS disks must be used together with a distributed file system or cluster software. Because most cluster applications, such as Windows MSCS, Veritas VCS, and Veritas CFS, require the usage of SCSI reservations, you are advised to use shared EVS disks with SCSI.<p id="en-us_topic_0052554220__p2086018215561"><a name="en-us_topic_0052554220__li72111959105511"></a><a name="li72111959105511"></a>SCSI reservations take effect only when shared SCSI EVS disks are attached to ECSs in the same ECS group. For more information about shared EVS disks, see <a href="en-us_topic_0032860759.html">Shared EVS Disks and Usage Instructions</a>.</p>
|
||||
<div class="section" id="en-us_topic_0052554220__section5554506411"><h4 class="sectiontitle">Common Application Scenarios and Usage Instructions of SCSI EVS Disks</h4><ul id="en-us_topic_0052554220__ul649313366412"><li id="en-us_topic_0052554220__li16493193619415">BMSs support only SCSI EVS disks.</li><li id="en-us_topic_0052554220__li72111959105511">Shared SCSI EVS disks: Shared SCSI EVS disks must be used together with a distributed file system or cluster software. Because most cluster applications, such as Windows MSCS, Veritas VCS, and Veritas CFS, require SCSI reservations, you are advised to use shared EVS disks with SCSI.<p id="en-us_topic_0052554220__p2086018215561"><a name="en-us_topic_0052554220__li72111959105511"></a><a name="li72111959105511"></a>SCSI reservations take effect only when shared SCSI EVS disks are attached to ECSs in the same ECS group. For more information about shared EVS disks, see <a href="en-us_topic_0032860759.html">Shared EVS Disks and Usage Instructions</a>.</p>
|
||||
</li></ul>
|
||||
</div>
|
||||
<div class="section" id="en-us_topic_0052554220__section1071245115370"><h4 class="sectiontitle">Do I Need to Install a Driver for SCSI EVS Disks?</h4><div class="p" id="en-us_topic_0052554220__p07141451113718">To use SCSI EVS disks, you need to install a driver for certain <span id="en-us_topic_0052554220__text1647481914323">server</span> OSs.<ul id="en-us_topic_0052554220__ul16715115193714"><li id="en-us_topic_0052554220__li1071685113714">BMS<p id="en-us_topic_0052554220__p5219775328"><a name="en-us_topic_0052554220__li1071685113714"></a><a name="li1071685113714"></a>Both the Windows and Linux images for BMSs are pre-installed with the required SDI card driver. Therefore, no driver needs to be installed.</p>
|
||||
<div class="section" id="en-us_topic_0052554220__section1071245115370"><h4 class="sectiontitle">Do I Need to Install a Driver for SCSI EVS Disks?</h4><div class="p" id="en-us_topic_0052554220__p07141451113718">To use SCSI EVS disks, you need to install a driver for certain <span id="en-us_topic_0052554220__text1647481914323">server</span> OSs.<ul id="en-us_topic_0052554220__ul16715115193714"><li id="en-us_topic_0052554220__li1071685113714">Bare Metal Server (BMS)<p id="en-us_topic_0052554220__p5219775328"><a name="en-us_topic_0052554220__li1071685113714"></a><a name="li1071685113714"></a>Both the Windows and Linux images for BMSs are pre-installed with the required SDI card driver. Therefore, no driver needs to be installed.</p>
|
||||
</li><li id="en-us_topic_0052554220__li171965111371">KVM ECS<p id="en-us_topic_0052554220__p3966175719482"><a name="en-us_topic_0052554220__li171965111371"></a><a name="li171965111371"></a>You are advised to use SCSI EVS disks with KVM ECSs. Linux images and Windows images for KVM ECSs already have the required driver. Therefore, no driver needs to be installed for KVM ECSs.</p>
|
||||
<div class="note" id="en-us_topic_0052554220__note159311959182312"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="en-us_topic_0052554220__p1165651172712">ECS virtualization types are categorized into KVM and Xen. For details, see <a href="https://docs.otc.t-systems.com/en-us/usermanual/ecs/en-us_topic_0035470096.html" target="_blank" rel="noopener noreferrer">ECS Types</a>.</p>
|
||||
</div></div>
|
||||
|
@ -3,12 +3,12 @@
|
||||
<h1 class="topictitle1">Creating a Snapshot</h1>
|
||||
<div id="body1500018934274"><div class="section" id="en-us_topic_0066615262__section36690541174716"><h4 class="sectiontitle">Scenarios</h4><p id="en-us_topic_0066615262__p298603411855">You can create an EVS snapshot on the management console to save the EVS disk data at a specific time point.</p>
|
||||
</div>
|
||||
<div class="section" id="en-us_topic_0066615262__section1443474343619"><h4 class="sectiontitle">Constraints</h4><ul id="en-us_topic_0066615262__ul724111588440"><li id="en-us_topic_0066615262__li134680334517">A maximum of 7 snapshots can be created for one disk.</li><li id="en-us_topic_0066615262__li20993169103915">Snapshots can be created for both system disks and data disks.</li></ul>
|
||||
<div class="section" id="en-us_topic_0066615262__section1443474343619"><h4 class="sectiontitle">Constraints</h4><ul id="en-us_topic_0066615262__ul724111588440"><li id="en-us_topic_0066615262__li134680334517">A maximum of 7 snapshots can be created for one disk.</li><li id="en-us_topic_0066615262__li20993169103915">Snapshots can be created for both system disks and data disks.</li><li id="en-us_topic_0066615262__li5921557133820">Snapshots can be created only for available or in-use disks.</li><li id="en-us_topic_0066615262__li424914271392">Snapshots of encrypted disks are stored encrypted, and those of non-encrypted disks are stored non-encrypted.</li><li id="en-us_topic_0066615262__li9950741133015">If a disk is created from a snapshot, the AZ of the disk is the same as that of the snapshot's source disk and cannot be changed.</li></ul>
|
||||
</div>
|
||||
<div class="section" id="en-us_topic_0066615262__section3347385018116"><h4 class="sectiontitle">Creating a Snapshot on the Disks Page</h4><ol id="en-us_topic_0066615262__ol62656275181144"><li id="en-us_topic_0066615262__li15479164262711"><span>Log in to the management console.</span></li><li id="en-us_topic_0066615262__li2935870315121"><span>Click <span><img id="en-us_topic_0066615262__en-us_topic_0021738346_image052111582392" src="en-us_image_0237893718.png"></span> in the upper left corner and select the desired region and project.</span></li><li id="en-us_topic_0066615262__li56612714175539"><span>Under <strong id="en-us_topic_0066615262__b18659293164">Storage</strong>, click <strong id="en-us_topic_0066615262__b16514297169">Elastic Volume Service</strong>.</span><p><p id="en-us_topic_0066615262__p39752386175539">The disk list page is displayed.</p>
|
||||
</p></li><li id="en-us_topic_0066615262__li10641770111825"><span>In the disk list, locate the row that contains the target disk, click <strong id="en-us_topic_0066615262__b842352706151520">More</strong> in the <strong id="en-us_topic_0066615262__b842352706151524">Operation</strong> column, and choose <strong id="en-us_topic_0066615262__b842352706151529">Create Snapshot</strong>.</span><p><p id="en-us_topic_0066615262__p1078258163615">Configure the basic settings for the snapshot according to <a href="#en-us_topic_0066615262__table17584125003610">Table 1</a>.</p>
|
||||
<div class="section" id="en-us_topic_0066615262__section3347385018116"><h4 class="sectiontitle">Creating a Snapshot on the Disks Page</h4><ol id="en-us_topic_0066615262__ol62656275181144"><li id="en-us_topic_0066615262__li5884586202528"><span>Log in to the management console.</span></li><li id="en-us_topic_0066615262__li2935870315121"><span>Click <span><img id="en-us_topic_0066615262__en-us_topic_0021738346_image052111582392" src="en-us_image_0237893718.png"></span> in the upper left corner and select the desired region and project.</span></li><li id="en-us_topic_0066615262__li56612714175539"><span>Under <strong id="en-us_topic_0066615262__b18659293164">Storage</strong>, click <strong id="en-us_topic_0066615262__b16514297169">Elastic Volume Service</strong>.</span><p><p id="en-us_topic_0066615262__p39752386175539">The disk list page is displayed.</p>
|
||||
</p></li><li id="en-us_topic_0066615262__li10641770111825"><span>In the disk list, locate the row that contains the target disk, click <strong id="en-us_topic_0066615262__b484014215497">Create Snapshot</strong> in the <strong id="en-us_topic_0066615262__b842352706151524">Operation</strong> column.</span><p><p id="en-us_topic_0066615262__p1078258163615">Configure the basic settings for the snapshot according to <a href="#en-us_topic_0066615262__table17584125003610">Table 1</a>.</p>
|
||||
|
||||
<div class="tablenoborder"><a name="en-us_topic_0066615262__table17584125003610"></a><a name="table17584125003610"></a><table cellpadding="4" cellspacing="0" summary="" id="en-us_topic_0066615262__table17584125003610" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Parameter description</caption><thead align="left"><tr id="en-us_topic_0066615262__row858695093614"><th align="left" class="cellrowborder" valign="top" width="22.444444444444443%" id="mcps1.3.3.2.4.2.2.2.4.1.1"><p id="en-us_topic_0066615262__p13587450173612">Parameter</p>
|
||||
<div class="tablenoborder"><a name="en-us_topic_0066615262__table17584125003610"></a><a name="table17584125003610"></a><table cellpadding="4" cellspacing="0" summary="" id="en-us_topic_0066615262__table17584125003610" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Snapshot parameter</caption><thead align="left"><tr id="en-us_topic_0066615262__row858695093614"><th align="left" class="cellrowborder" valign="top" width="22.444444444444443%" id="mcps1.3.3.2.4.2.2.2.4.1.1"><p id="en-us_topic_0066615262__p13587450173612">Parameter</p>
|
||||
</th>
|
||||
<th align="left" class="cellrowborder" valign="top" width="44.45454545454545%" id="mcps1.3.3.2.4.2.2.2.4.1.2"><p id="en-us_topic_0066615262__p458865013366">Description</p>
|
||||
</th>
|
||||
@ -27,14 +27,14 @@
|
||||
</tbody>
|
||||
</table>
|
||||
</div>
|
||||
</p></li><li id="en-us_topic_0066615262__li5485942112712"><span>Click <strong id="en-us_topic_0066615262__b2013472941615">Create Now</strong>.</span></li><li id="en-us_topic_0066615262__li114852042172712"><span>Return to the <strong id="en-us_topic_0066615262__b842352706194531">Snapshots</strong> page to view the snapshot creation information.</span><p><p id="en-us_topic_0066615262__p31875125184211">When the snapshot status changes to <strong id="en-us_topic_0066615262__b84235270614382">Available</strong>, the snapshot has been created.</p>
|
||||
</p></li><li id="en-us_topic_0066615262__li5485942112712"><span>Click <strong id="en-us_topic_0066615262__b2013472941615">Create Now</strong>.</span></li><li id="en-us_topic_0066615262__li114852042172712"><span>Go back to the <strong id="en-us_topic_0066615262__b842352706194531">Snapshots</strong> page to view the snapshot creation information.</span><p><p id="en-us_topic_0066615262__p31875125184211">After the snapshot status changes to <strong id="en-us_topic_0066615262__b84235270614382">Available</strong>, the snapshot has been created.</p>
|
||||
</p></li></ol>
|
||||
</div>
|
||||
<div class="section" id="en-us_topic_0066615262__section33181038161610"><h4 class="sectiontitle">Creating a Snapshot on the Snapshots Page</h4><ol id="en-us_topic_0066615262__ol39801624111711"><li id="en-us_topic_0066615262__li99781224111715"><span>Log in to the management console.</span></li><li id="en-us_topic_0066615262__li075714444175"><span>Click <span><img id="en-us_topic_0066615262__en-us_topic_0021738346_image052111582392_1" src="en-us_image_0237893718.png"></span> in the upper left corner and select the desired region and project.</span></li><li id="en-us_topic_0066615262__li1297812419176"><span>Under <strong id="en-us_topic_0066615262__b1285217621">Storage</strong>, click <strong id="en-us_topic_0066615262__b65533593">Elastic Volume Service</strong>.</span><p><p id="en-us_topic_0066615262__p1597810244178">The disk list page is displayed.</p>
|
||||
<div class="section" id="en-us_topic_0066615262__section33181038161610"><h4 class="sectiontitle">Creating a Snapshot on the Snapshots Page</h4><ol id="en-us_topic_0066615262__ol39801624111711"><li id="en-us_topic_0066615262__li99781224111715"><span>Log in to the management console.</span></li><li id="en-us_topic_0066615262__li075714444175"><span>Click <span><img id="en-us_topic_0066615262__en-us_topic_0021738346_image052111582392_1" src="en-us_image_0237893718.png"></span> in the upper left corner and select the desired region and project.</span></li><li id="en-us_topic_0066615262__li1297812419176"><span>Under <strong id="en-us_topic_0066615262__b1489198820">Storage</strong>, click <strong id="en-us_topic_0066615262__b601280940">Elastic Volume Service</strong>.</span><p><p id="en-us_topic_0066615262__p1597810244178">The disk list page is displayed.</p>
|
||||
</p></li><li id="en-us_topic_0066615262__li4979162412178"><span>In the navigation pane on the left, choose <strong id="en-us_topic_0066615262__b09143338235">Elastic Volume Service</strong> > <strong id="en-us_topic_0066615262__b1916113372311">Snapshots</strong>.</span><p><p id="en-us_topic_0066615262__p18978192414173">On the <strong id="en-us_topic_0066615262__b1174411564256">Snapshots</strong> page, click <strong id="en-us_topic_0066615262__b15745145618256">Create Snapshot</strong>.</p>
|
||||
<p id="en-us_topic_0066615262__p169781124171717">Configure the basic settings for the snapshot according to <a href="#en-us_topic_0066615262__table1097922420177">Table 2</a>.</p>
|
||||
|
||||
<div class="tablenoborder"><a name="en-us_topic_0066615262__table1097922420177"></a><a name="table1097922420177"></a><table cellpadding="4" cellspacing="0" summary="" id="en-us_topic_0066615262__table1097922420177" frame="border" border="1" rules="all"><caption><b>Table 2 </b>Parameter description</caption><thead align="left"><tr id="en-us_topic_0066615262__row597952421715"><th align="left" class="cellrowborder" valign="top" width="22.444444444444443%" id="mcps1.3.4.2.4.2.3.2.4.1.1"><p id="en-us_topic_0066615262__p397916243177">Parameter</p>
|
||||
<div class="tablenoborder"><a name="en-us_topic_0066615262__table1097922420177"></a><a name="table1097922420177"></a><table cellpadding="4" cellspacing="0" summary="" id="en-us_topic_0066615262__table1097922420177" frame="border" border="1" rules="all"><caption><b>Table 2 </b>Snapshot parameters</caption><thead align="left"><tr id="en-us_topic_0066615262__row597952421715"><th align="left" class="cellrowborder" valign="top" width="22.444444444444443%" id="mcps1.3.4.2.4.2.3.2.4.1.1"><p id="en-us_topic_0066615262__p397916243177">Parameter</p>
|
||||
</th>
|
||||
<th align="left" class="cellrowborder" valign="top" width="44.45454545454545%" id="mcps1.3.4.2.4.2.3.2.4.1.2"><p id="en-us_topic_0066615262__p1097932411178">Description</p>
|
||||
</th>
|
||||
@ -61,7 +61,7 @@
|
||||
<tr id="en-us_topic_0066615262__row1297917242179"><td class="cellrowborder" valign="top" width="22.444444444444443%" headers="mcps1.3.4.2.4.2.3.2.4.1.1 "><p id="en-us_topic_0066615262__p1097972415179">Select Disk</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="44.45454545454545%" headers="mcps1.3.4.2.4.2.3.2.4.1.2 "><p id="en-us_topic_0066615262__p169791724171713">Mandatory</p>
|
||||
<p id="en-us_topic_0066615262__p497914242177">Select a disk based on which the snapshot is to be created.</p>
|
||||
<p id="en-us_topic_0066615262__p497914242177">Select a disk based on which the snapshot will be created.</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="33.1010101010101%" headers="mcps1.3.4.2.4.2.3.2.4.1.3 "><p id="en-us_topic_0066615262__p29791324181717">volume-01</p>
|
||||
</td>
|
||||
@ -69,13 +69,13 @@
|
||||
</tbody>
|
||||
</table>
|
||||
</div>
|
||||
</p></li><li id="en-us_topic_0066615262__li69803241178"><span>Click <strong id="en-us_topic_0066615262__b849507043">Create Now</strong>.</span></li><li id="en-us_topic_0066615262__li109808244175"><span>Return to the <strong id="en-us_topic_0066615262__b1701868409">Snapshots</strong> page to view the snapshot creation information.</span><p><p id="en-us_topic_0066615262__p398062481715">When the snapshot status changes to <strong id="en-us_topic_0066615262__b16359220173718">Available</strong>, the snapshot has been created.</p>
|
||||
</p></li><li id="en-us_topic_0066615262__li69803241178"><span>Click <strong id="en-us_topic_0066615262__b348254336">Create Now</strong>.</span></li><li id="en-us_topic_0066615262__li109808244175"><span>Go back to the <strong id="en-us_topic_0066615262__b0997171113212">Snapshots</strong> page to view the snapshot creation information.</span><p><p id="en-us_topic_0066615262__p398062481715">After the snapshot status changes to <strong id="en-us_topic_0066615262__b178561417123214">Available</strong>, the snapshot has been created.</p>
|
||||
</p></li></ol>
|
||||
</div>
|
||||
</div>
|
||||
<div>
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="evs_01_0111.html">Managing Snapshots</a></div>
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="evs_01_0111.html">Managing EVS Snapshots</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
@ -14,7 +14,7 @@
|
||||
</li><li id="en-us_topic_0066809008__li28454203192725">Multi-service quick deployment<p id="en-us_topic_0066809008__p28239706192719"><a name="en-us_topic_0066809008__li28454203192725"></a><a name="li28454203192725"></a>You can use a snapshot to create multiple disks containing the same initial data, and these disks can be used as data resources for various services, for example data mining, report query, and development and testing. This method protects the initial data and creates disks rapidly, meeting the diversified service data requirements.</p>
|
||||
</li></ul>
|
||||
</div>
|
||||
<div class="section" id="en-us_topic_0066809008__section27269138163743"><h4 class="sectiontitle">Usage Instructions</h4><p id="en-us_topic_0066809008__p60921580163752">For details about the snapshot usages, see <a href="evs_01_0111.html">Managing Snapshots</a>.</p>
|
||||
<div class="section" id="en-us_topic_0066809008__section27269138163743"><h4 class="sectiontitle">Usage Instructions</h4><p id="en-us_topic_0066809008__p60921580163752">For details about the snapshot usages, see <a href="evs_01_0111.html">Managing EVS Snapshots</a>.</p>
|
||||
</div>
|
||||
</div>
|
||||
<div>
|
||||
|
@ -1,38 +1,43 @@
|
||||
<a name="evs_01_0001"></a><a name="evs_01_0001"></a>
|
||||
|
||||
<h1 class="topictitle1">EVS Disk Encryption</h1>
|
||||
<div id="body1505872566368"><div class="section" id="evs_01_0001__section14109833104132"><h4 class="sectiontitle">What Is EVS Disk Encryption?</h4><p id="evs_01_0001__p5767114314413">In case your services require encryption for the data stored on EVS disks, EVS provides you with the encryption function. You can encrypt newly created EVS disks.</p>
|
||||
<h1 class="topictitle1">EVS Encryption</h1>
|
||||
<div id="body1505872566368"><div class="section" id="evs_01_0001__section14109833104132"><h4 class="sectiontitle">What Is EVS Encryption?</h4><p id="evs_01_0001__p5767114314413">In case your services require encryption for the data stored on EVS disks, EVS provides you with the encryption function. You can encrypt newly created EVS disks.</p>
|
||||
<p id="evs_01_0001__p135522595318">EVS uses the industry-standard XTS-AES-256 encryption algorithm and keys to encrypt EVS disks. Keys used by encrypted EVS disks are provided by the Key Management Service (KMS), which is secure and convenient. Therefore, you do not need to establish and maintain the key management infrastructure. KMS uses the Hardware Security Module (HSM) that complies with FIPS 140-2 level 3 requirements to protect keys. All user keys are protected by the root key in HSM to prevent key exposure.</p>
|
||||
<p id="evs_01_0001__p44532316613"></p>
|
||||
<div class="notice" id="evs_01_0001__note11941219101615"><span class="noticetitle"><img src="public_sys-resources/notice_3.0-en-us.png"> </span><div class="noticebody"><p id="evs_01_0001__p9214171713386">The encryption attribute of a disk cannot be changed after the disk is purchased.</p>
|
||||
<p id="evs_01_0001__p663854212927">For details about how to create an encrypted disk, see <strong id="evs_01_0001__b14955121734816">Getting Started</strong> > <strong id="evs_01_0001__b395921734810">Purchase an EVS Disk</strong> in the <em id="evs_01_0001__i1760420419485">Elastic Volume Service User Guide</em>.</p>
|
||||
</div></div>
|
||||
</div>
|
||||
<div class="section" id="evs_01_0001__section17331463223115"><h4 class="sectiontitle">Keys Used for EVS Disk Encryption</h4><div class="p" id="evs_01_0001__p44297599103525">The keys provided by KMS include a Default Master Key and Customer Master Keys (CMKs).<ul id="evs_01_0001__ul19537237173313"><li id="evs_01_0001__li38741344153312">Default Master Key: A key that is automatically created by EVS through KMS and named <strong id="evs_01_0001__b88421453151910">evs/default</strong>.<p id="evs_01_0001__p5874194483315">The Default Master Key cannot be disabled and does not support scheduled deletion.</p>
|
||||
<div class="section" id="evs_01_0001__section17331463223115"><h4 class="sectiontitle">Keys Used for EVS Encryption</h4><div class="p" id="evs_01_0001__p44297599103525">The keys provided by KMS include a Default Master Key and Customer Master Keys (CMKs).<ul id="evs_01_0001__ul19537237173313"><li id="evs_01_0001__li38741344153312">Default Master Key: A key that is automatically created by EVS through KMS and named <strong id="evs_01_0001__b10486194865213">evs/default</strong>.<p id="evs_01_0001__p5874194483315">The Default Master Key cannot be disabled and does not support scheduled deletion.</p>
|
||||
</li><li id="evs_01_0001__li10901124519340">CMKs: Keys created by users. You may use existing CMKs or create new CMKs to encrypt disks. For details, see <span class="menucascade" id="evs_01_0001__menucascade137031646666"><b><span class="uicontrol" id="evs_01_0001__uicontrol167031461467">Management</span></b> > <b><span class="uicontrol" id="evs_01_0001__uicontrol1270394620614">Creating a CMK</span></b></span> in the <em id="evs_01_0001__i1670311461611">Key Management Service User Guide</em>.</li></ul>
|
||||
</div>
|
||||
<div class="p" id="evs_01_0001__p1747318441415">If disks are encrypted using CMKs and a CMK is then disabled or scheduled for deletion, the disks encrypted by this CMK can no longer be read from or written to and data on these disks may never be restored. See <a href="#evs_01_0001__table15423135384216">Table 1</a> for more information.
|
||||
<div class="tablenoborder"><a name="evs_01_0001__table15423135384216"></a><a name="table15423135384216"></a><table cellpadding="4" cellspacing="0" summary="" id="evs_01_0001__table15423135384216" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Impact of CMK unavailability</caption><thead align="left"><tr id="evs_01_0001__row64230539421"><th align="left" class="cellrowborder" valign="top" width="26.01260126012601%" id="mcps1.3.2.3.2.2.4.1.1"><p id="evs_01_0001__p18423125312425">CMK Status</p>
|
||||
<p id="evs_01_0001__p15626129143114">When an encrypted disk is attached, EVS accesses KMS, and KMS sends the data key (DK) to the host memory for use. The disk uses the DK plaintext to encrypt and decrypt disk I/Os. The DK plaintext is only stored in the memory of the host housing the ECS and is not stored persistently on the media. If the CMK is disabled or deleted in KMS, the disk encrypted using this CMK can still use the DK plaintext stored in the host memory. If this disk is later detached, the DK plaintext will be deleted from the memory, and data cannot be read from or written to the disk. Before you re-attach this encrypted disk, ensure that the CMK is enabled.</p>
|
||||
<div class="p" id="evs_01_0001__p1747318441415">If you use a CMK to encrypt disks and this CMK is then disabled or scheduled for deletion, data cannot be read from or written to these disks or may never be restored. See <a href="#evs_01_0001__table15423135384216">Table 1</a> for more information.
|
||||
<div class="tablenoborder"><a name="evs_01_0001__table15423135384216"></a><a name="table15423135384216"></a><table cellpadding="4" cellspacing="0" summary="" id="evs_01_0001__table15423135384216" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Impact of CMK unavailability</caption><thead align="left"><tr id="evs_01_0001__row64230539421"><th align="left" class="cellrowborder" valign="top" width="21%" id="mcps1.3.2.4.2.2.4.1.1"><p id="evs_01_0001__p18423125312425">CMK Status</p>
|
||||
</th>
|
||||
<th align="left" class="cellrowborder" valign="top" width="39.16391639163916%" id="mcps1.3.2.3.2.2.4.1.2"><p id="evs_01_0001__p15423453154211">Impact</p>
|
||||
<th align="left" class="cellrowborder" valign="top" width="35%" id="mcps1.3.2.4.2.2.4.1.2"><p id="evs_01_0001__p15423453154211">Impact</p>
|
||||
</th>
|
||||
<th align="left" class="cellrowborder" valign="top" width="34.823482348234826%" id="mcps1.3.2.3.2.2.4.1.3"><p id="evs_01_0001__p104231253114218">How to Restore</p>
|
||||
<th align="left" class="cellrowborder" valign="top" width="44%" id="mcps1.3.2.4.2.2.4.1.3"><p id="evs_01_0001__p104231253114218">How to Restore</p>
|
||||
</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody><tr id="evs_01_0001__row114238537426"><td class="cellrowborder" valign="top" width="26.01260126012601%" headers="mcps1.3.2.3.2.2.4.1.1 "><p id="evs_01_0001__p8423155312427">Disabled</p>
|
||||
<tbody><tr id="evs_01_0001__row114238537426"><td class="cellrowborder" valign="top" width="21%" headers="mcps1.3.2.4.2.2.4.1.1 "><p id="evs_01_0001__p8423155312427">Disabled</p>
|
||||
</td>
|
||||
<td class="cellrowborder" rowspan="3" valign="top" width="39.16391639163916%" headers="mcps1.3.2.3.2.2.4.1.2 "><ul id="evs_01_0001__ul7272244174918"><li id="evs_01_0001__li198281331175014">For an encrypted disk already attached:<p id="evs_01_0001__p87692391099"><a name="evs_01_0001__li198281331175014"></a><a name="li198281331175014"></a>The disk cannot be accessed after a period of time, or the disk data can never be restored. If the disk is detached later, it cannot be attached again.</p>
|
||||
</li><li id="evs_01_0001__li92498551281">For an encrypted disk not attached:<p id="evs_01_0001__p0385114218918"><a name="evs_01_0001__li92498551281"></a><a name="li92498551281"></a>The disk cannot be attached anymore.</p>
|
||||
<td class="cellrowborder" rowspan="3" valign="top" width="35%" headers="mcps1.3.2.4.2.2.4.1.2 "><ul id="evs_01_0001__ul7272244174918"><li id="evs_01_0001__li6728453296">For an encrypted disk already attached:<p id="evs_01_0001__p1518106202915"><a name="evs_01_0001__li6728453296"></a><a name="li6728453296"></a>Reads and writes to the disk are normal unless the disk is detached. Once detached, the disk cannot be attached again.</p>
|
||||
</li><li id="evs_01_0001__li139183147294">For an encrypted disk not attached:<p id="evs_01_0001__p139581662917"><a name="evs_01_0001__li139183147294"></a><a name="li139183147294"></a>The disk cannot be attached anymore.</p>
|
||||
</li></ul>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="34.823482348234826%" headers="mcps1.3.2.3.2.2.4.1.3 "><p id="evs_01_0001__p247893525">Enable the CMK. For details, see <strong id="evs_01_0001__b971084618611">Managing CMKs</strong> > <strong id="evs_01_0001__b1871018461661">Enabling One or More CMKs</strong> in the <em id="evs_01_0001__i17102046064">Key Management Service User Guide</em>.</p>
|
||||
<td class="cellrowborder" valign="top" width="44%" headers="mcps1.3.2.4.2.2.4.1.3 "><p id="evs_01_0001__p247893525">Enable the CMK. For details, see <strong id="evs_01_0001__b971084618611">Managing CMKs</strong> > <strong id="evs_01_0001__b1871018461661">Enabling One or More CMKs</strong> in the <em id="evs_01_0001__i17102046064">Key Management Service User Guide</em>.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="evs_01_0001__row194235535421"><td class="cellrowborder" valign="top" headers="mcps1.3.2.3.2.2.4.1.1 "><p id="evs_01_0001__p24231953104211">Scheduled deletion</p>
|
||||
<tr id="evs_01_0001__row194235535421"><td class="cellrowborder" valign="top" headers="mcps1.3.2.4.2.2.4.1.1 "><p id="evs_01_0001__p24231953104211">Scheduled deletion</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" headers="mcps1.3.2.3.2.2.4.1.2 "><p id="evs_01_0001__p1811015185215">Cancel the scheduled deletion for the CMK. For details, see <strong id="evs_01_0001__b20710846167">Managing CMKs</strong> > <strong id="evs_01_0001__b7710246962">Canceling the Scheduled Deletion of One or More CMKs</strong> in the <em id="evs_01_0001__i147103461466">Key Management Service User Guide</em>.</p>
|
||||
<td class="cellrowborder" valign="top" headers="mcps1.3.2.4.2.2.4.1.2 "><p id="evs_01_0001__p1811015185215">Cancel the scheduled deletion for the CMK. For details, see <strong id="evs_01_0001__b20710846167">Managing CMKs</strong> > <strong id="evs_01_0001__b7710246962">Canceling the Scheduled Deletion of One or More CMKs</strong> in the <em id="evs_01_0001__i147103461466">Key Management Service User Guide</em>.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="evs_01_0001__row84234536424"><td class="cellrowborder" valign="top" headers="mcps1.3.2.3.2.2.4.1.1 "><p id="evs_01_0001__p134239539426">Deleted</p>
|
||||
<tr id="evs_01_0001__row84234536424"><td class="cellrowborder" valign="top" headers="mcps1.3.2.4.2.2.4.1.1 "><p id="evs_01_0001__p134239539426">Deleted</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" headers="mcps1.3.2.3.2.2.4.1.2 "><p id="evs_01_0001__p842375394216">Data on the disks can never be restored.</p>
|
||||
<td class="cellrowborder" valign="top" headers="mcps1.3.2.4.2.2.4.1.2 "><p id="evs_01_0001__p842375394216">Data on the disks can never be restored.</p>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
@ -40,22 +45,22 @@
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
<div class="section" id="evs_01_0001__section4401454411508"><h4 class="sectiontitle">Who Can Use the Disk Encryption Function?</h4><ul id="evs_01_0001__ul5757202818847"><li id="evs_01_0001__li4838621118847">The security administrator (having the Security Administrator rights) can grant the KMS access rights to EVS for using the disk encryption function.</li><li id="evs_01_0001__li4139486918847">When a common user who does not have the Security Administrator rights needs to use the disk encryption function, the condition varies depending on whether the user is the first one ever in the current region or project to use this feature.<ul id="evs_01_0001__ul3700950718847"><li id="evs_01_0001__li6465010818847">If the common user is the first one ever in the current region or project to use the feature, the user must contact a user having the Security Administrator rights to grant the KMS access rights to EVS. Then, the common user can use the disk encryption function.</li><li id="evs_01_0001__li4498006718847">If the common user is not the first one ever in the current region or project to use the feature, the common user can use the disk encryption function directly.</li></ul>
|
||||
<div class="section" id="evs_01_0001__section4401454411508"><h4 class="sectiontitle">Who Can Use the Encryption Function?</h4><ul id="evs_01_0001__ul5757202818847"><li id="evs_01_0001__li4838621118847">The security administrator (having Security Administrator permissions) can grant the KMS access rights to EVS for using the encryption function.</li><li id="evs_01_0001__li4139486918847">When a user who does not have the Security Administrator permissions needs to use the encryption function, the condition varies depending on whether the user is the first one ever in the current region or project to use this function.<ul id="evs_01_0001__ul3700950718847"><li id="evs_01_0001__li6465010818847">If the user is the first one ever in the current region or project to use this function, the user must contact a user having the Security Administrator permissions to grant the KMS access rights to EVS. Then, the user can use encryption.</li><li id="evs_01_0001__li4498006718847">If the user is not the first one ever in the current region or project to use this function, the user can use encryption directly.</li></ul>
|
||||
</li></ul>
|
||||
<p id="evs_01_0001__p654719181722">From the perspective of a tenant, as long as the KMS access rights have been granted to EVS in a region, all the users in the same region can directly use the disk encryption function.</p>
|
||||
<p id="evs_01_0001__p654719181722">From the perspective of a tenant, as long as the KMS access rights have been granted to EVS in a region, all the users in the same region can directly use the encryption function.</p>
|
||||
<p id="evs_01_0001__p2327430181628">If there are multiple projects in the current region, the KMS access rights need to be granted to each project in this region.</p>
|
||||
</div>
|
||||
<div class="section" id="evs_01_0001__en-us_topic_0047272493_section30754477152516"><h4 class="sectiontitle">Application Scenarios of EVS Disk Encryption</h4><p id="evs_01_0001__p58279313182146"><a href="#evs_01_0001__fig682110438439">Figure 1</a> shows the user relationships under regions and projects from the perspective of a tenant. The following example uses region B to describe the two application scenarios of the disk encryption function.</p>
|
||||
<div class="section" id="evs_01_0001__en-us_topic_0047272493_section30754477152516"><h4 class="sectiontitle">Application Scenarios of EVS Encryption</h4><p id="evs_01_0001__p58279313182146"><a href="#evs_01_0001__fig682110438439">Figure 1</a> shows the user relationships under regions and projects from the perspective of a tenant. The following example uses region B to describe the two scenarios of using the encryption function.</p>
|
||||
<div class="fignone" id="evs_01_0001__fig682110438439"><a name="evs_01_0001__fig682110438439"></a><a name="fig682110438439"></a><span class="figcap"><b>Figure 1 </b>User relationships</span><br><span><img id="evs_01_0001__image1382164374310" src="en-us_image_0205531351.png"></span></div>
|
||||
<ul id="evs_01_0001__ul50403396182148"><li id="evs_01_0001__li65642929182148">If the security administrator uses the encryption function for the first time ever, the operation process is as follows:<ol id="evs_01_0001__en-us_topic_0047272493_ol5927887417313"><li id="evs_01_0001__en-us_topic_0047272493_li2619460317313">Grant the KMS access rights to EVS.<p id="evs_01_0001__en-us_topic_0047272493_p142911741743"><a name="evs_01_0001__en-us_topic_0047272493_li2619460317313"></a><a name="en-us_topic_0047272493_li2619460317313"></a>After the KMS access rights have been granted, the system automatically creates a Default Master Key and names it <strong id="evs_01_0001__b84235270620131">evs/default</strong>. DMK can be used for disk encryption.</p>
|
||||
<div class="note" id="evs_01_0001__en-us_topic_0047272493_note66790747172045"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="evs_01_0001__en-us_topic_0047272493_p64245811172045">The EVS disk encryption relies on KMS. When the encryption function is used for the first time ever, the KMS access rights need to be granted to EVS. After the KMS access rights have been granted, all users in this region can use the encryption function, without requiring the KMS access rights to be granted again.</p>
|
||||
<ul id="evs_01_0001__ul50403396182148"><li id="evs_01_0001__li65642929182148">If the security administrator uses the encryption function for the first time ever, the operation process is as follows:<ol id="evs_01_0001__en-us_topic_0047272493_ol5927887417313"><li id="evs_01_0001__en-us_topic_0047272493_li2619460317313">Grant the KMS access rights to EVS.<p id="evs_01_0001__en-us_topic_0047272493_p142911741743"><a name="evs_01_0001__en-us_topic_0047272493_li2619460317313"></a><a name="en-us_topic_0047272493_li2619460317313"></a>After the KMS access rights have been granted, the system automatically creates a Default Master Key and names it <strong id="evs_01_0001__b84235270620131">evs/default</strong>. You can use the Default Master Key to encrypt EVS disks.</p>
|
||||
<div class="note" id="evs_01_0001__en-us_topic_0047272493_note66790747172045"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="evs_01_0001__en-us_topic_0047272493_p64245811172045">EVS encryption relies on KMS. When the encryption function is used for the first time ever, the KMS access rights need to be granted to EVS. After the KMS access rights have been granted, all users in this region can use the encryption function, without requiring the KMS access rights to be granted again.</p>
|
||||
</div></div>
|
||||
</li><li id="evs_01_0001__en-us_topic_0047272493_li6551631417410">Select a key.<div class="p" id="evs_01_0001__en-us_topic_0047272493_p6505639317119"><a name="evs_01_0001__en-us_topic_0047272493_li6551631417410"></a><a name="en-us_topic_0047272493_li6551631417410"></a>You can select one of the following keys:<ul id="evs_01_0001__en-us_topic_0047272493_ul66321024171321"><li id="evs_01_0001__en-us_topic_0047272493_li5131522171321">DMK: <strong id="evs_01_0001__b84235270620422">evs/default</strong></li><li id="evs_01_0001__en-us_topic_0047272493_li46377861171321">CMKs: Existing or newly created CMKs. For details, see <strong id="evs_01_0001__b1775099101719">Creating a CMK</strong> in the <em id="evs_01_0001__i677010460620">Key Management Service User Guide</em>.</li></ul>
|
||||
</li><li id="evs_01_0001__en-us_topic_0047272493_li6551631417410">Select a key.<div class="p" id="evs_01_0001__en-us_topic_0047272493_p6505639317119"><a name="evs_01_0001__en-us_topic_0047272493_li6551631417410"></a><a name="en-us_topic_0047272493_li6551631417410"></a>You can select one of the following keys:<ul id="evs_01_0001__en-us_topic_0047272493_ul66321024171321"><li id="evs_01_0001__en-us_topic_0047272493_li5131522171321">Default Master Key: <strong id="evs_01_0001__b84235270620422">evs/default</strong></li><li id="evs_01_0001__en-us_topic_0047272493_li46377861171321">CMKs: Existing or newly created CMKs. For details, see <strong id="evs_01_0001__b1775099101719">Creating a CMK</strong> in the <em id="evs_01_0001__i677010460620">Key Management Service User Guide</em>.</li></ul>
|
||||
</div>
|
||||
</li></ol>
|
||||
<p id="evs_01_0001__en-us_topic_0047272493_p3939960117047">After the security administrator has used the disk encryption function, all users in Region B can directly use the encryption function.</p>
|
||||
</li><li id="evs_01_0001__li20140149182216">If User E (common user) uses the encryption function for the first time ever, the operation process is as follows:<ol id="evs_01_0001__en-us_topic_0047272493_ol47174640161634"><li id="evs_01_0001__en-us_topic_0047272493_li65269179161929">When user E uses the encryption function, and the system prompts a message indicating that the KMS access rights have not been granted to EVS.</li><li id="evs_01_0001__en-us_topic_0047272493_li49571937161634">Contact the security administrator to grant the KMS access rights to EVS.</li></ol>
|
||||
<p id="evs_01_0001__en-us_topic_0047272493_p42882181211720">After the KMS access rights have been granted to EVS, User E as well as all users in Region B can directly use the disk encryption function and do not need to contact the security administrator to grant the KMS access rights to EVS again.</p>
|
||||
<p id="evs_01_0001__en-us_topic_0047272493_p3939960117047">After the security administrator has used the encryption function, all users in Region B can directly use encryption.</p>
|
||||
</li><li id="evs_01_0001__li20140149182216">If User E (common user) uses the encryption function for the first time ever, the operation process is as follows:<ol id="evs_01_0001__en-us_topic_0047272493_ol47174640161634"><li id="evs_01_0001__en-us_topic_0047272493_li65269179161929">When user E uses encryption, and the system prompts a message indicating that the KMS access rights have not been granted to EVS.</li><li id="evs_01_0001__en-us_topic_0047272493_li49571937161634">Contact the security administrator to grant the KMS access rights to EVS.</li></ol>
|
||||
<p id="evs_01_0001__en-us_topic_0047272493_p42882181211720">After the KMS access rights have been granted to EVS, User E as well as all users in Region B can directly use the encryption function and do not need to contact the security administrator to grant the KMS access rights to EVS again.</p>
|
||||
</li></ul>
|
||||
</div>
|
||||
</div>
|
||||
|
@ -2,7 +2,7 @@
|
||||
|
||||
<h1 class="topictitle1">Detaching a System Disk</h1>
|
||||
<div id="body1505899665739"><div class="section" id="evs_01_0003__section21771672164455"><h4 class="sectiontitle">Scenarios</h4><p id="evs_01_0003__p13982123165512">A system disk can only be detached offline, that is, its server must be in the <strong id="evs_01_0003__b10499218195615">Stopped</strong> state before the system disk is detached. Therefore, you need to first stop the <span id="evs_01_0003__text729525586173019">server</span> and then detach the system disk.</p>
|
||||
<div class="p" id="evs_01_0003__p6230616162513">For the system disk attached to <span id="evs_01_0003__text1319644805173132">a server</span>, the disk function is displayed as <strong id="evs_01_0003__b842352706173213">System disk</strong>, and the disk status is displayed as <strong id="evs_01_0003__b842352706173228">In-use</strong> in the disk list. After a system disk is detached from the server, the disk function changes to <strong id="evs_01_0003__b868150400173329">Bootable disk</strong>, and the status changes to <strong id="evs_01_0003__b806098383173329">Available</strong>.<div class="note" id="evs_01_0003__note36300011364"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="evs_01_0003__p56335010364">Bootable disks are the system disks detached from servers. A bootable disk can be re-attached to <span id="evs_01_0003__text132811158203718">a server</span> and be used as a system disk or data disk depending on the device name selected.</p>
|
||||
<div class="p" id="evs_01_0003__p6230616162513">For a system disk attached to <span id="evs_01_0003__text1319644805173132">a server</span>, the disk function is displayed as <strong id="evs_01_0003__b842352706173213">System disk</strong>, and the disk status is displayed as <strong id="evs_01_0003__b842352706173228">In-use</strong> in the disk list. After a system disk is detached from the server, the disk function changes to <strong id="evs_01_0003__b868150400173329">Bootable disk</strong>, and the status changes to <strong id="evs_01_0003__b806098383173329">Available</strong>.<div class="note" id="evs_01_0003__note36300011364"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="evs_01_0003__p56335010364">Bootable disks are the system disks detached from servers. A bootable disk can be re-attached to <span id="evs_01_0003__text132811158203718">a server</span> and be used as a system disk or data disk depending on the device name selected.</p>
|
||||
</div></div>
|
||||
</div>
|
||||
</div>
|
||||
@ -11,7 +11,7 @@
|
||||
</p></li><li id="evs_01_0003__li23677833165924"><span>Click the name of this <span id="evs_01_0003__text139101676495059">server</span>.</span><p><p id="evs_01_0003__p11773906165924">The <span id="evs_01_0003__text772569388144332">server</span> details page is displayed.</p>
|
||||
</p></li><li id="evs_01_0003__li38856291165924"><span>Click the <strong id="evs_01_0003__b842352706142740">Disks</strong> tab to view the system disk attached to <span id="evs_01_0003__text476148145142816">the server</span>.</span></li><li id="evs_01_0003__li14162301165924"><span>Locate the row that contains the system disk and click <strong id="evs_01_0003__b1934511288201">Detach</strong>.</span><p><div class="p" id="evs_01_0003__p40192685165924">The <strong id="evs_01_0003__b842352706213211">Detach Disk</strong> dialog box is displayed, as shown in <a href="#evs_01_0003__fig13846812115521">Figure 1</a>.<div class="fignone" id="evs_01_0003__fig13846812115521"><a name="evs_01_0003__fig13846812115521"></a><a name="fig13846812115521"></a><span class="figcap"><b>Figure 1 </b>Detach Disk (system disk)</span><br><span><img id="evs_01_0003__image2284325320" src="en-us_image_0152756082.png"></span></div>
|
||||
</div>
|
||||
</p></li><li id="evs_01_0003__li2084603315321"><span>Click <strong id="evs_01_0003__b1339121917">Yes</strong> to detach the disk.</span><p><p id="evs_01_0003__p14846173316326">After the operation had succeeded, the detached system disk is no longer displayed under the <strong id="evs_01_0003__b122816814473">Disks</strong> tab.</p>
|
||||
</p></li><li id="evs_01_0003__li2084603315321"><span>Click <strong id="evs_01_0003__b2056864735">Yes</strong> to detach the disk.</span><p><p id="evs_01_0003__p14846173316326">After the operation had succeeded, the detached system disk is no longer displayed under the <strong id="evs_01_0003__b122816814473">Disks</strong> tab.</p>
|
||||
</p></li></ol>
|
||||
</div>
|
||||
<div class="section" id="evs_01_0003__section1980071942010"><h4 class="sectiontitle">Related Operations</h4><p id="evs_01_0003__p5817719112011">For more detachment FAQs, see <a href="evs_01_0079.html">Detachment</a>.</p>
|
||||
|
@ -15,7 +15,7 @@
|
||||
</li><li id="evs_01_0004__li57429915241">Click the <strong id="evs_01_0004__b1086718369221">Attachments</strong> tab to view the server where the target disk has been attached.</li><li id="evs_01_0004__li1601134615241">Click <span><img id="evs_01_0004__image169462381447" src="en-us_image_0238263087.png"></span> to select the server and click <strong id="evs_01_0004__b1462223832211">Detach Disk</strong>.<div class="p" id="evs_01_0004__p26489280112">The <strong id="evs_01_0004__b974413823517">Detach Disk</strong> dialog box is displayed, as shown in <a href="#evs_01_0004__fig146481428813">Figure 1</a>.<div class="fignone" id="evs_01_0004__fig146481428813"><a name="evs_01_0004__fig146481428813"></a><a name="fig146481428813"></a><span class="figcap"><b>Figure 1 </b>Detach Disk</span><br><span><img id="evs_01_0004__image31557617715" src="en-us_image_0163801956.png"></span></div>
|
||||
</div>
|
||||
</li><li id="evs_01_0004__li1228932514152">Click <strong id="evs_01_0004__b158161925174716">Yes</strong> to detach the disk.</li></ol>
|
||||
</li><li id="evs_01_0004__li5205209315241">If you do not need to view the server information, perform the following procedure:<ol type="a" id="evs_01_0004__ol6581565415241"><li id="evs_01_0004__li5546997715241">In the disk list, locate the row that contains the target disk and choose <span class="menucascade" id="evs_01_0004__menucascade66791225115410"><b><span class="uicontrol" id="evs_01_0004__uicontrol1367942511541">More</span></b> > <b><span class="uicontrol" id="evs_01_0004__uicontrol167922535412">Detach</span></b></span> in the <strong id="evs_01_0004__b122501642386">Operation</strong> column.<div class="p" id="evs_01_0004__p6388317815241">The <strong id="evs_01_0004__b1002026105">Detach Disk</strong> dialog box is displayed, as shown in <a href="#evs_01_0004__fig715496815241">Figure 2</a>.<div class="fignone" id="evs_01_0004__fig715496815241"><a name="evs_01_0004__fig715496815241"></a><a name="fig715496815241"></a><span class="figcap"><b>Figure 2 </b>Detach Disk dialog box</span><br><span><img id="evs_01_0004__image10876143421618" src="en-us_image_0152754019.png"></span></div>
|
||||
</li><li id="evs_01_0004__li5205209315241">If you do not need to view the server information, perform the following procedure:<ol type="a" id="evs_01_0004__ol6581565415241"><li id="evs_01_0004__li5546997715241">In the disk list, locate the row that contains the target disk and choose <span class="menucascade" id="evs_01_0004__menucascade4220138115518"><b><span class="uicontrol" id="evs_01_0004__uicontrol22204825517">More</span></b> > <b><span class="uicontrol" id="evs_01_0004__uicontrol1722018825517">Detach</span></b></span> in the <strong id="evs_01_0004__b63418755618">Operation</strong> column.<div class="p" id="evs_01_0004__p6388317815241">The <strong id="evs_01_0004__b158659919">Detach Disk</strong> dialog box is displayed, as shown in <a href="#evs_01_0004__fig715496815241">Figure 2</a>.<div class="fignone" id="evs_01_0004__fig715496815241"><a name="evs_01_0004__fig715496815241"></a><a name="fig715496815241"></a><span class="figcap"><b>Figure 2 </b>Detach Disk dialog box</span><br><span><img id="evs_01_0004__image10876143421618" src="en-us_image_0152754019.png"></span></div>
|
||||
</div>
|
||||
</li><li id="evs_01_0004__li10164172510103">Click <strong id="evs_01_0004__b12628123318476">Yes</strong> to detach the disk.</li></ol>
|
||||
</li></ul>
|
||||
@ -26,10 +26,10 @@
|
||||
<div class="section" id="evs_01_0004__section24629896173058"><h4 class="sectiontitle">Detaching a Shared Disk</h4><ol id="evs_01_0004__ol9647240195926"><li id="evs_01_0004__li1317173144714"><span>Log in to the management console.</span></li><li id="evs_01_0004__li141714319471"><span>Click <span><img id="evs_01_0004__en-us_topic_0021738346_image052111582392_1" src="en-us_image_0237893718.png"></span> in the upper left corner and select the desired region and project.</span></li><li id="evs_01_0004__li308525592029"><span>Under <strong id="evs_01_0004__b20441241164513">Storage</strong>, click <strong id="evs_01_0004__b1944215419459">Elastic Volume Service</strong>.</span><p><p id="evs_01_0004__p92375762029">The disk list page is displayed.</p>
|
||||
</p></li><li id="evs_01_0004__li30547501203454"><span>Determine whether to view <span id="evs_01_0004__text774651735162822">the server</span> information before detaching the disk.</span><p><ul id="evs_01_0004__ul6405871203623"><li id="evs_01_0004__li45035676203623">If you need to view the server information, perform the following procedure:<ol type="a" id="evs_01_0004__ol5146104320552"><li id="evs_01_0004__li44189183205518">In the disk list, click the name of the to-be-detached disk.<p id="evs_01_0004__p62158329205518"><a name="evs_01_0004__li44189183205518"></a><a name="li44189183205518"></a>The disk details page is displayed.</p>
|
||||
</li><li id="evs_01_0004__li22554051205518">Click the <strong id="evs_01_0004__b486173317254">Attachments</strong> tab to view the servers where the target disk has been attached.</li><li id="evs_01_0004__li4681796294534">Click <span><img id="evs_01_0004__image1538360094534" src="en-us_image_0238263087.png"></span> to select <span id="evs_01_0004__text14273884162320">the server</span> and click <strong id="evs_01_0004__b11812121717445">Detach Disk</strong>.<p id="evs_01_0004__p677737194536">Shared EVS disks support batch detachment so that you can select multiple <span id="evs_01_0004__text281883369163033">servers</span> at a time.</p>
|
||||
<div class="p" id="evs_01_0004__p135031424410">The <strong id="evs_01_0004__b396122778">Detach Disk</strong> dialog box is displayed, as shown in <a href="#evs_01_0004__fig10503132745">Figure 3</a>.<div class="fignone" id="evs_01_0004__fig10503132745"><a name="evs_01_0004__fig10503132745"></a><a name="fig10503132745"></a><span class="figcap"><b>Figure 3 </b>Detaching a shared disk</span><br><span><img id="evs_01_0004__image1570210331343" src="en-us_image_0163801385.png"></span></div>
|
||||
<div class="p" id="evs_01_0004__p135031424410">The <strong id="evs_01_0004__b217563333">Detach Disk</strong> dialog box is displayed, as shown in <a href="#evs_01_0004__fig10503132745">Figure 3</a>.<div class="fignone" id="evs_01_0004__fig10503132745"><a name="evs_01_0004__fig10503132745"></a><a name="fig10503132745"></a><span class="figcap"><b>Figure 3 </b>Detaching a shared disk</span><br><span><img id="evs_01_0004__image1570210331343" src="en-us_image_0163801385.png"></span></div>
|
||||
</div>
|
||||
</li><li id="evs_01_0004__li68718326174">Click <strong id="evs_01_0004__b17631842194718">Yes</strong> to detach the disk.</li></ol>
|
||||
</li><li id="evs_01_0004__li64294352203649">If you do not need to view the server information, perform the following procedure:<ol type="a" id="evs_01_0004__ol47897994205959"><li id="evs_01_0004__li28428764205959">In the disk list, locate the row that contains the target disk and choose <span class="menucascade" id="evs_01_0004__menucascade18813169192614"><b><span class="uicontrol" id="evs_01_0004__uicontrol08132919266">More</span></b> > <b><span class="uicontrol" id="evs_01_0004__uicontrol381317915264">Detach</span></b></span> in the <strong id="evs_01_0004__b1617771702617">Operation</strong> column.<div class="p" id="evs_01_0004__p3348449221142">The <strong id="evs_01_0004__b1940067239">Detach Disk</strong> dialog box is displayed, as shown in <a href="#evs_01_0004__fig36494313113211">Figure 4</a>.<div class="fignone" id="evs_01_0004__fig36494313113211"><a name="evs_01_0004__fig36494313113211"></a><a name="fig36494313113211"></a><span class="figcap"><b>Figure 4 </b>Detaching a shared disk dialog box</span><br><span><img id="evs_01_0004__image109903409232" src="en-us_image_0152754508.png"></span></div>
|
||||
</li><li id="evs_01_0004__li64294352203649">If you do not need to view the server information, perform the following procedure:<ol type="a" id="evs_01_0004__ol47897994205959"><li id="evs_01_0004__li28428764205959">In the disk list, locate the row that contains the target disk and choose <span class="menucascade" id="evs_01_0004__menucascade1196311589544"><b><span class="uicontrol" id="evs_01_0004__uicontrol39639586543">More</span></b> > <b><span class="uicontrol" id="evs_01_0004__uicontrol1396365835420">Detach</span></b></span> in the <strong id="evs_01_0004__b1285440142911">Operation</strong> column.<div class="p" id="evs_01_0004__p3348449221142">The <strong id="evs_01_0004__b483434932">Detach Disk</strong> dialog box is displayed, as shown in <a href="#evs_01_0004__fig36494313113211">Figure 4</a>.<div class="fignone" id="evs_01_0004__fig36494313113211"><a name="evs_01_0004__fig36494313113211"></a><a name="fig36494313113211"></a><span class="figcap"><b>Figure 4 </b>Detaching a shared disk dialog box</span><br><span><img id="evs_01_0004__image109903409232" src="en-us_image_0152754508.png"></span></div>
|
||||
</div>
|
||||
</li><li id="evs_01_0004__li1551533362118">Click <span><img id="evs_01_0004__image2051873372112" src="en-us_image_0238263087.png"></span> to select <span id="evs_01_0004__text14518133312217">the server</span>.<p id="evs_01_0004__p680022912210">Shared EVS disks support batch detachment so that you can select multiple <span id="evs_01_0004__text187144103225">servers</span> at a time.</p>
|
||||
</li><li id="evs_01_0004__li12774166192215">Click <strong id="evs_01_0004__b11645374912">Yes</strong> to detach the disk.</li></ol>
|
||||
|
@ -1,6 +1,6 @@
|
||||
<a name="evs_01_0005"></a><a name="evs_01_0005"></a>
|
||||
|
||||
<h1 class="topictitle1">Deleting an EVS Disk</h1>
|
||||
<h1 class="topictitle1">Deleting EVS Disks</h1>
|
||||
<div id="body1505876507180"><div class="section" id="evs_01_0005__section6567565617247"><h4 class="sectiontitle">Scenarios</h4><p id="evs_01_0005__p1591815463261">If an EVS disk is no longer used, you can release the virtual resources by deleting the disk from the system.</p>
|
||||
<ul id="evs_01_0005__ul1141181183314"><li id="evs_01_0005__li124211110334">Before deleting a disk, ensure that the disk status is <strong id="evs_01_0005__b985812257218">Available</strong>, <strong id="evs_01_0005__b7859625162117">Error</strong>, <strong id="evs_01_0005__b148613253213">Expansion failed</strong>, <strong id="evs_01_0005__b168621925102111">Restoration failed</strong>, or <strong id="evs_01_0005__b3862132512215">Rollback failed</strong>.</li><li id="evs_01_0005__li18424153316">Before deleting a shared disk, ensure that the disk has been detached from all its servers.</li></ul>
|
||||
</div>
|
||||
|
@ -2,10 +2,11 @@
|
||||
|
||||
<h1 class="topictitle1">Expansion Overview</h1>
|
||||
<div id="body1505902410872"><div class="section" id="evs_01_0006__section1493121695811"><h4 class="sectiontitle">What Is Capacity Expansion?</h4><p id="evs_01_0006__p17316192517568">If the capacity of an existing disk is insufficient, you can expand the disk capacity to increase the storage space.</p>
|
||||
<p id="evs_01_0006__p177821955155113">Both system disks and data disks can be expanded. Currently, disk capacities can be expanded only. Capacity reduction is not supported.</p>
|
||||
<p id="evs_01_0006__p177821955155113">Both system disks and data disks can be expanded. Disk capacity can be expanded only, but cannot be reduced.</p>
|
||||
</div>
|
||||
<div class="section" id="evs_01_0006__section173511542246"><h4 class="sectiontitle">How to Expand the Disk Capacity?</h4><p id="evs_01_0006__p1115871365619">A capacity expansion operation includes the following steps:</p>
|
||||
<ol id="evs_01_0006__ol284044018564"><li id="evs_01_0006__li19840124005611"><a href="#evs_01_0006__section87622024418">Expand the disk capacity on the management console.</a></li><li id="evs_01_0006__li196492053185615"><a href="#evs_01_0006__section487311389414">Log in to the server and extend the disk partition and file system.</a></li></ol>
|
||||
<p id="evs_01_0006__p1282495515718"></p>
|
||||
<div class="fignone" id="evs_01_0006__fig76833489137"><span class="figcap"><b>Figure 1 </b>Capacity expansion procedure</span><br><span><img id="evs_01_0006__image86835482133" src="en-us_image_0228748662.png"></span></div>
|
||||
</div>
|
||||
<div class="section" id="evs_01_0006__section87622024418"><a name="evs_01_0006__section87622024418"></a><a name="section87622024418"></a><h4 class="sectiontitle">Expand the Disk Capacity on the Management Console</h4><div class="p" id="evs_01_0006__p178891721125">Choose a proper expansion method based on the disk status. <ul id="evs_01_0006__ul14745439216"><li id="evs_01_0006__li492992142913">For an In-use disk:<div class="p" id="evs_01_0006__p34381939102915"><a name="evs_01_0006__li492992142913"></a><a name="li492992142913"></a>The disk has been attached to a <span id="evs_01_0006__text143552203916">server</span>. Check whether the disk can be expanded in the In-use state by referring to <a href="evs_01_0007.html#evs_01_0007__section158147122515">Constraints</a>.<ul id="evs_01_0006__ul15745193825"><li id="evs_01_0006__li174513318219">If yes, expand the disk capacity according to <a href="evs_01_0007.html">Expanding Capacity for an In-use EVS Disk</a>.</li><li id="evs_01_0006__li137456316216">If no, detach the disk. Then, expand the disk capacity according to <a href="evs_01_0008.html">Expanding Capacity for an Available EVS Disk</a>.</li></ul>
|
||||
@ -22,14 +23,14 @@
|
||||
</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody><tr id="evs_01_0006__row15584133410181"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.4.2.3.2.3.1.1 "><p id="evs_01_0006__p20584234101814">Disk capacity ≤ 2 TB</p>
|
||||
<tbody><tr id="evs_01_0006__row15584133410181"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.4.2.3.2.3.1.1 "><p id="evs_01_0006__p20584234101814">Disk capacity ≤ 2 TiB</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.4.2.3.2.3.1.2 "><ul id="evs_01_0006__ul1792564894112"><li id="evs_01_0006__li7925248194119">Windows: <a href="en-us_topic_0017616396.html">Extending Disk Partitions and File Systems (Windows Server 2008)</a></li><li id="evs_01_0006__li1394915252421">Linux: <a href="evs_01_0035.html">Partition and File System Extension Preparations (Linux)</a></li></ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="evs_01_0006__row35841834121815"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.4.2.3.2.3.1.1 "><p id="evs_01_0006__p185841834141811">Disk capacity > 2 TB</p>
|
||||
<tr id="evs_01_0006__row35841834121815"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.4.2.3.2.3.1.1 "><p id="evs_01_0006__p185841834141811">Disk capacity > 2 TiB</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.4.2.3.2.3.1.2 "><ul id="evs_01_0006__ul15171154910427"><li id="evs_01_0006__li5171949154210">GPT partition style: <a href="en-us_topic_0017616396.html">Extending Disk Partitions and File Systems (Windows Server 2008)</a> or <a href="evs_01_0035.html">Partition and File System Extension Preparations (Linux)</a></li><li id="evs_01_0006__li2355174092917">MBR partition style: Not supported<p id="evs_01_0006__p7650194892910"><a name="evs_01_0006__li2355174092917"></a><a name="li2355174092917"></a>The maximum disk capacity that MBR supports is 2 TB, and the disk space exceeding 2 TB cannot be used. If your disk uses MBR and you need to expand the disk capacity to over 2 TB, change the partition style from MBR to GPT. Ensure that the disk data has been backed up before changing the partition style because services will be interrupted and data on the disk will be cleared during this change.</p>
|
||||
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.4.2.3.2.3.1.2 "><ul id="evs_01_0006__ul15171154910427"><li id="evs_01_0006__li5171949154210">GPT partition style: <a href="en-us_topic_0017616396.html">Extending Disk Partitions and File Systems (Windows Server 2008)</a> or <a href="evs_01_0035.html">Partition and File System Extension Preparations (Linux)</a></li><li id="evs_01_0006__li2355174092917">MBR partition style: Not supported<p id="evs_01_0006__p7650194892910"><a name="evs_01_0006__li2355174092917"></a><a name="li2355174092917"></a>The maximum disk capacity that MBR supports is 2 TiB, and the disk space exceeding 2 TiB cannot be used. If your disk uses MBR and you need to expand the disk capacity to over 2 TiB, change the partition style from MBR to GPT. Ensure that the disk data has been backed up before changing the partition style because services will be interrupted and data on the disk will be deleted during this change.</p>
|
||||
</li></ul>
|
||||
</td>
|
||||
</tr>
|
||||
@ -38,7 +39,7 @@
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
<div class="section" id="evs_01_0006__section387117383196"><h4 class="sectiontitle">Related Operations</h4><p id="evs_01_0006__p61181121396">For more expansion FAQs, see <a href="evs_01_0077.html">Capacity Expansion</a>.</p>
|
||||
<div class="section" id="evs_01_0006__section387117383196"><h4 class="sectiontitle">Related Operations</h4><p id="evs_01_0006__p873161293016">For more expansion FAQs, see <a href="https://docs.otc.t-systems.com/en-us/usermanual/evs/evs_01_0077.html" target="_blank" rel="noopener noreferrer">Capacity Expansion</a>.</p>
|
||||
</div>
|
||||
</div>
|
||||
<div>
|
||||
|
@ -6,19 +6,19 @@
|
||||
<div class="section" id="evs_01_0007__section158147122515"><a name="evs_01_0007__section158147122515"></a><a name="section158147122515"></a><h4 class="sectiontitle">Constraints</h4><ul id="evs_01_0007__ul313711473252"><li id="evs_01_0007__li1835020451308">Currently, disk capacities can only be expanded, but cannot be reduced.</li><li id="evs_01_0007__li41271847142514">When expanding an In-use disk, <span id="evs_01_0007__text20127124715253">the server</span> containing this disk must be in the <strong id="evs_01_0007__b84235270616396">Running</strong> or <strong id="evs_01_0007__b84235270616399">Stopped</strong> state.</li><li id="evs_01_0007__li12127134782516">A shared disk cannot be expanded in the <strong id="evs_01_0007__b165043391311">In-use</strong> state. To expand a shared In-use disk, you must detach it from all its <span id="evs_01_0007__text1150593161315">servers</span>, wait until its status changes to <strong id="evs_01_0007__b115057314136">Available</strong>, and then expand its capacity. For more information, see <a href="evs_01_0008.html">Expanding Capacity for an Available EVS Disk</a>.</li><li id="evs_01_0007__li18128184702514">Only some server OSs support capacity expansion of In-use disks. For details, see the official document of the corresponding OS.<p id="evs_01_0007__p1412716472254"><a name="evs_01_0007__li18128184702514"></a><a name="li18128184702514"></a>If the server OS does not support capacity expansion of In-use disks, detach the disk and then expand its capacity. Otherwise, you may need to stop and then start the server after the expansion to make the additional space available.</p>
|
||||
</li></ul>
|
||||
</div>
|
||||
<div class="section" id="evs_01_0007__section5287890203514"><h4 class="sectiontitle">Procedure</h4><ol id="evs_01_0007__ol161515014192"><li id="evs_01_0007__li5884586202528"><span>Log in to the management console.</span></li><li id="evs_01_0007__li153618295518"><span>Click <span><img id="evs_01_0007__en-us_topic_0021738346_image052111582392" src="en-us_image_0237893718.png"></span> in the upper left corner and select the desired region and project.</span></li><li id="evs_01_0007__li308525592029"><span>Under <strong>Storage</strong>, click <strong>Elastic Volume Service</strong>.</span><p><p id="evs_01_0007__p92375762029">The disk list page is displayed.</p>
|
||||
<div class="section" id="evs_01_0007__section5287890203514"><h4 class="sectiontitle">Procedure</h4><ol id="evs_01_0007__ol161515014192"><li id="evs_01_0007__li5884586202528"><span>Log in to the management console.</span></li><li id="evs_01_0007__li153618295518"><span>Click <span><img id="evs_01_0007__en-us_topic_0021738346_image052111582392" src="en-us_image_0237893718.png"></span> in the upper left corner and select the desired region and project.</span></li><li id="evs_01_0007__li308525592029"><span>Under <strong id="evs_01_0007__b18321731174720">Storage</strong>, click <strong id="evs_01_0007__b683263114713">Elastic Volume Service</strong>.</span><p><p id="evs_01_0007__p92375762029">The disk list page is displayed.</p>
|
||||
</p></li><li id="evs_01_0007__li9235666185919"><span>Determine whether to view <span id="evs_01_0007__text1494664922164212">the server</span> information before expanding the disk.</span><p><ul id="evs_01_0007__ul2337357319034"><li id="evs_01_0007__li4710624719034">If you need to view the server information, perform the following procedure:<ol type="a" id="evs_01_0007__ol117729011925"><li id="evs_01_0007__li388472531925">In the disk list, click the name of the to-be-expanded disk.<p class="litext" id="evs_01_0007__p140809631925"><a name="evs_01_0007__li388472531925"></a><a name="li388472531925"></a>The disk details page is displayed.</p>
|
||||
</li><li id="evs_01_0007__li596198081925">Click the <strong id="evs_01_0007__b671507276103239">Attachments</strong> tab to view <span id="evs_01_0007__text179236683911052">the server</span> where the target disk has been attached.</li><li id="evs_01_0007__li1206532719342">Click <strong id="evs_01_0007__b842352706175859">Expand Capacity</strong> in the upper right corner of the page.<p id="evs_01_0007__p4264339219514">The expansion page is displayed.</p>
|
||||
</li></ol>
|
||||
</li><li id="evs_01_0007__li1159117319039">If you do not need to view the server information, perform the following procedure:<ol type="a" id="evs_01_0007__ol202534119445"><li id="evs_01_0007__li22503719445">In the disk list, locate the row that contains the target disk and click <strong id="evs_01_0007__b7225191415186">Expand Capacity</strong> in the <strong id="evs_01_0007__b6225014151820">Operation</strong> column.<p id="evs_01_0007__p1265003919525">The expansion page is displayed.</p>
|
||||
</li><li id="evs_01_0007__li1159117319039">If you do not need to view the server information, perform the following procedure:<ol type="a" id="evs_01_0007__ol202534119445"><li id="evs_01_0007__li22503719445">In the disk list, locate the row that contains the target disk and click <strong id="evs_01_0007__b5506115019278">Expand Capacity</strong> in the <strong id="evs_01_0007__b125065508276">Operation</strong> column.<p id="evs_01_0007__p1265003919525">The expansion page is displayed.</p>
|
||||
</li></ol>
|
||||
</li></ul>
|
||||
</p></li><li id="evs_01_0007__li44271518184926"><span>Set the <strong id="evs_01_0007__b7755153011815">Add Capacity (GB)</strong> parameter and click <strong id="evs_01_0007__b1076183081814">Next</strong>.</span></li><li id="evs_01_0007__li11250997172443"><span>On the <strong id="evs_01_0007__b91115532582">Details</strong> page, check the disk information again.</span><p><ul id="evs_01_0007__ul38915531172443"><li id="evs_01_0007__li14695463172443">If you do not need to modify the specifications, click <strong id="evs_01_0007__b842352706111853">Submit</strong> to start the expansion.</li><li id="evs_01_0007__li65150306172443">If you need to modify the specifications, click <strong id="evs_01_0007__b842352706113037">Previous</strong> to modify parameters.</li></ul>
|
||||
</p></li><li id="evs_01_0007__li44271518184926"><span>Set the <strong id="evs_01_0007__b7755153011815">Add Capacity (GiB)</strong> parameter and click <strong id="evs_01_0007__b1076183081814">Next</strong>.</span></li><li id="evs_01_0007__li11250997172443"><span>On the <strong id="evs_01_0007__b91115532582">Details</strong> page, check the disk details.</span><p><ul id="evs_01_0007__ul38915531172443"><li id="evs_01_0007__li14695463172443">If you do not need to modify the specifications, click <strong id="evs_01_0007__b842352706111853">Submit</strong>.</li><li id="evs_01_0007__li65150306172443">If you need to modify the specifications, click <strong id="evs_01_0007__b842352706113037">Previous</strong>.</li></ul>
|
||||
<p id="evs_01_0007__p4421611218543">After the specifications are submitted, go back to the disk list page.</p>
|
||||
</p></li><li id="evs_01_0007__li40881775173229"><span>In the disk list, view the capacity of the target disk.</span><p><p id="evs_01_0007__p58239715173253">When the disk status changes from <strong id="evs_01_0007__b969092893916">Expanding</strong> to <strong id="evs_01_0007__b18921431103910">In-use</strong> and the disk capacity increases, the expansion has succeeded.</p>
|
||||
<div class="note" id="evs_01_0007__note4822925143235"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="evs_01_0007__p30362042143235">If the expansion fails, technical support personnel will contact you and help you handle this error. Do not perform any operations on the disk before the technical support personnel contact you. If you require that the error be handled as soon as possible, contact our technical support personnel. The disk will no longer be charged after its status changes to <strong id="evs_01_0007__b45225508016832">Expansion failed</strong>.</p>
|
||||
</div></div>
|
||||
</p></li><li id="evs_01_0007__li1821943185531"><span>After a disk has been expanded on the management console, only the disk storage capacity is enlarged, but its additional space cannot be used directly. You must log in to the <span id="evs_01_0007__text528744683218">server</span> and extend the disk partition and file system.</span><p><p id="evs_01_0007__p33539635184033">The operation method varies depending on the server OS.</p>
|
||||
</p></li><li id="evs_01_0007__li1821943185531"><span>After the disk has been expanded on the management console, only the disk storage capacity is enlarged, but its additional space cannot be used directly. You must log in to the <span id="evs_01_0007__text528744683218">server</span> and extend the disk partition and file system.</span><p><p id="evs_01_0007__p33539635184033">The operation method varies depending on the server OS.</p>
|
||||
<ul id="evs_01_0007__ul30073002184039"><li id="evs_01_0007__li66279599184039">In Windows, see <a href="en-us_topic_0017616396.html">Extending Disk Partitions and File Systems (Windows Server 2008)</a>.</li><li id="evs_01_0007__li6324748184232">In Linux, see <a href="evs_01_0035.html">Partition and File System Extension Preparations (Linux)</a>.</li></ul>
|
||||
</p></li></ol>
|
||||
</div>
|
||||
|
@ -6,13 +6,13 @@
|
||||
<div class="section" id="evs_01_0008__section2096213105282"><h4 class="sectiontitle">Constraints</h4><ul id="evs_01_0008__ul29712114175"><li id="evs_01_0008__li1835020451308">Currently, disk capacities can only be expanded, but cannot be reduced.</li><li id="evs_01_0008__li1397413172">A shared disk cannot be expanded in the <strong id="evs_01_0008__b842352706172324">In-use</strong> state. To expand a shared In-use disk, you must detach it from all its <span id="evs_01_0008__text69731310152815">servers</span>, wait until its status changes to <strong id="evs_01_0008__b129812301408">Available</strong>, and then expand its capacity.</li></ul>
|
||||
</div>
|
||||
<div class="section" id="evs_01_0008__section12383539191210"><h4 class="sectiontitle">Procedure</h4><ol id="evs_01_0008__ol63542609191210"><li id="evs_01_0008__li5884586202528"><span>Log in to the management console.</span></li><li id="evs_01_0008__li153618295518"><span>Click <span><img id="evs_01_0008__en-us_topic_0021738346_image052111582392" src="en-us_image_0237893718.png"></span> in the upper left corner and select the desired region and project.</span></li><li id="evs_01_0008__li22800952191210"><span>Under <strong>Storage</strong>, click <strong>Elastic Volume Service</strong>.</span><p><p id="evs_01_0008__p3881978191210">The disk list page is displayed.</p>
|
||||
</p></li><li id="evs_01_0008__li35980963194319"><span>In the disk list, locate the row that contains the target disk and click <strong id="evs_01_0008__evs_01_0007_b7225191415186">Expand Capacity</strong> in the <strong id="evs_01_0008__evs_01_0007_b6225014151820">Operation</strong> column.</span><p><p id="evs_01_0008__evs_01_0007_p1265003919525">The expansion page is displayed.</p>
|
||||
</p></li><li id="evs_01_0008__li40391218194319"><span>Set the <strong id="evs_01_0008__evs_01_0007_b7755153011815">Add Capacity (GB)</strong> parameter and click <strong id="evs_01_0008__evs_01_0007_b1076183081814">Next</strong>.</span></li><li id="evs_01_0008__li27976648194319"><span>On the <strong id="evs_01_0008__evs_01_0007_b91115532582">Details</strong> page, check the disk information again.</span><p><ul id="evs_01_0008__evs_01_0007_ul38915531172443"><li id="evs_01_0008__evs_01_0007_li14695463172443">If you do not need to modify the specifications, click <strong id="evs_01_0008__evs_01_0007_b842352706111853">Submit</strong> to start the expansion.</li><li id="evs_01_0008__evs_01_0007_li65150306172443">If you need to modify the specifications, click <strong id="evs_01_0008__evs_01_0007_b842352706113037">Previous</strong> to modify parameters.</li></ul>
|
||||
</p></li><li id="evs_01_0008__li35980963194319"><span>In the disk list, locate the row that contains the target disk and click <strong id="evs_01_0008__evs_01_0007_b5506115019278">Expand Capacity</strong> in the <strong id="evs_01_0008__evs_01_0007_b125065508276">Operation</strong> column.</span><p><p id="evs_01_0008__evs_01_0007_p1265003919525">The expansion page is displayed.</p>
|
||||
</p></li><li id="evs_01_0008__li40391218194319"><span>Set the <strong id="evs_01_0008__evs_01_0007_b7755153011815">Add Capacity (GiB)</strong> parameter and click <strong id="evs_01_0008__evs_01_0007_b1076183081814">Next</strong>.</span></li><li id="evs_01_0008__li27976648194319"><span>On the <strong id="evs_01_0008__evs_01_0007_b91115532582">Details</strong> page, check the disk details.</span><p><ul id="evs_01_0008__evs_01_0007_ul38915531172443"><li id="evs_01_0008__evs_01_0007_li14695463172443">If you do not need to modify the specifications, click <strong id="evs_01_0008__evs_01_0007_b842352706111853">Submit</strong>.</li><li id="evs_01_0008__evs_01_0007_li65150306172443">If you need to modify the specifications, click <strong id="evs_01_0008__evs_01_0007_b842352706113037">Previous</strong>.</li></ul>
|
||||
<p id="evs_01_0008__evs_01_0007_p4421611218543">After the specifications are submitted, go back to the disk list page.</p>
|
||||
</p></li><li id="evs_01_0008__li36487354194319"><span>In the disk list, view the capacity of the target disk.</span><p><p id="evs_01_0008__p13898914154215">When the disk status changes from <strong id="evs_01_0008__b1944614412416">Expanding</strong> to <strong id="evs_01_0008__b20447174184117">Available</strong> and the disk capacity increases, the expansion has succeeded.</p>
|
||||
<div class="note" id="evs_01_0008__evs_01_0007_note4822925143235"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="evs_01_0008__evs_01_0007_p30362042143235">If the expansion fails, technical support personnel will contact you and help you handle this error. Do not perform any operations on the disk before the technical support personnel contact you. If you require that the error be handled as soon as possible, contact our technical support personnel. The disk will no longer be charged after its status changes to <strong id="evs_01_0008__evs_01_0007_b45225508016832">Expansion failed</strong>.</p>
|
||||
</div></div>
|
||||
</p></li><li id="evs_01_0008__li3598746519434"><span>Attach the disk to <span id="evs_01_0008__text60301618151629">the server</span>. For details, see <a href="evs_01_0107.html">Attach an EVS Disk</a>.</span></li><li id="evs_01_0008__li30869950194349"><span>After a disk has been expanded on the management console, only the disk storage capacity is enlarged, but its additional space cannot be used directly. You must log in to the <span id="evs_01_0008__evs_01_0007_text528744683218">server</span> and extend the disk partition and file system.</span><p><p id="evs_01_0008__evs_01_0007_p33539635184033">The operation method varies depending on the server OS.</p>
|
||||
</p></li><li id="evs_01_0008__li3598746519434"><span>Attach the disk to <span id="evs_01_0008__text60301618151629">the server</span>. For details, see <a href="evs_01_0107.html">Attach an EVS Disk</a>.</span></li><li id="evs_01_0008__li30869950194349"><span>After the disk has been expanded on the management console, only the disk storage capacity is enlarged, but its additional space cannot be used directly. You must log in to the <span id="evs_01_0008__evs_01_0007_text528744683218">server</span> and extend the disk partition and file system.</span><p><p id="evs_01_0008__evs_01_0007_p33539635184033">The operation method varies depending on the server OS.</p>
|
||||
<ul id="evs_01_0008__evs_01_0007_ul30073002184039"><li id="evs_01_0008__evs_01_0007_li66279599184039">In Windows, see <a href="en-us_topic_0017616396.html">Extending Disk Partitions and File Systems (Windows Server 2008)</a>.</li><li id="evs_01_0008__evs_01_0007_li6324748184232">In Linux, see <a href="evs_01_0035.html">Partition and File System Extension Preparations (Linux)</a>.</li></ul>
|
||||
</p></li></ol>
|
||||
</div>
|
||||
|
@ -1,15 +1,15 @@
|
||||
<a name="evs_01_0009"></a><a name="evs_01_0009"></a>
|
||||
|
||||
<h1 class="topictitle1">Managing an Encrypted EVS Disk</h1>
|
||||
<div id="body1505876939205"><div class="section" id="evs_01_0009__section3026922421034"><h4 class="sectiontitle">Relationships Between Encrypted Disks, Backups and Snapshots</h4><div class="p" id="evs_01_0009__p53627097222931">The encryption function can be used to encrypt system disks, data disks, backups and snapshots. The details are as follows:<ul id="evs_01_0009__ul63683928223756"><li id="evs_01_0009__li32044182419">System disk encryption relates to the image that is used to create the <span id="evs_01_0009__text7204121811417">server</span>.<ul id="evs_01_0009__ul172214191047"><li id="evs_01_0009__li43167511223756">If an encrypted image is used to create the <span id="evs_01_0009__text57939293114118">server</span>, encryption is enabled for the system disk by default, and the system disk and image share the same encryption method. For details, see <strong id="evs_01_0009__b9653125193515">Managing Private Images</strong> > <strong id="evs_01_0009__b38871446596">Encrypting Images</strong> in the <em id="evs_01_0009__i1981835010918">Image Management Service User Guide</em>.</li><li id="evs_01_0009__li1783319216510">If a non-encrypted image is used to create the <span id="evs_01_0009__text174501151514">server</span>, determine whether to encrypt the system disk during the <span id="evs_01_0009__text135434094910">server</span> creation. For details, see <strong id="evs_01_0009__b96906559365">Getting Started</strong> > <strong id="evs_01_0009__b84235270618447">Creating an ECS</strong> > <strong id="evs_01_0009__b15950181619127">Step 1: Configure Basic Settings</strong> in the <em id="evs_01_0009__i842352697145957">Elastic Cloud Server User Guide</em>.</li></ul>
|
||||
<h1 class="topictitle1">Managing Encrypted EVS Disks</h1>
|
||||
<div id="body1505876939205"><div class="section" id="evs_01_0009__section3026922421034"><h4 class="sectiontitle">Relationships Between Encrypted Disks, Backups and Snapshots</h4><div class="p" id="evs_01_0009__p53627097222931">The encryption function can be used to encrypt system disks, data disks, backups and snapshots. The details are as follows:<ul id="evs_01_0009__ul63683928223756"><li id="evs_01_0009__li32044182419">System disk encryption relies on the image that is used to create the <span id="evs_01_0009__text7204121811417">server</span>.<ul id="evs_01_0009__ul172214191047"><li id="evs_01_0009__li43167511223756">If an encrypted image is used to create the <span id="evs_01_0009__text57939293114118">server</span>, the system disk will be encrypted by default, and the system disk and image share the same encryption method. For details, see <strong id="evs_01_0009__b1469214216573">Managing Private Images</strong> > <strong id="evs_01_0009__b826442745713">Encrypting Images</strong> in the <em id="evs_01_0009__i4740123216571">Image Management Service User Guide</em>.</li><li id="evs_01_0009__li1783319216510">If a non-encrypted image is used to create the <span id="evs_01_0009__text174501151514">server</span>, you can determine whether to encrypt the system disk during the <span id="evs_01_0009__text135434094910">server</span> creation. For details, see <strong id="evs_01_0009__b96906559365">Getting Started</strong> > <strong id="evs_01_0009__b84235270618447">Creating an ECS</strong> > <strong id="evs_01_0009__b15950181619127">Step 1: Configure Basic Settings</strong> in the <em id="evs_01_0009__i842352697145957">Elastic Cloud Server User Guide</em>.</li></ul>
|
||||
</li><li id="evs_01_0009__li2181036110135">If an empty disk is created, you can determine whether to encrypt the disk or not. The encryption attribute of the disk cannot be changed after the disk has been created.</li><li id="evs_01_0009__li28642658223758">If a disk is created from a snapshot, the encryption attribute of the disk will be the same as that of the snapshot's source disk.</li><li id="evs_01_0009__li1974628922380">If a disk is created from a backup, the encryption attribute of the disk does not need to be the same as that of the backup.</li><li id="evs_01_0009__li15989143514256">If a snapshot is created for a disk, the encryption attribute of the snapshot is the same as that of the disk.</li></ul>
|
||||
</div>
|
||||
</div>
|
||||
<div class="section" id="evs_01_0009__section909365011371"><h4 class="sectiontitle">Creating an Encrypted EVS Disk</h4><p id="evs_01_0009__p146495302155">Before you use the disk encryption function, KMS access rights need to be granted to EVS. If you have the Security Administrator rights, grant the KMS access rights to EVS directly. If you do not have this permission, contact a user with the security administrator rights to grant KMS access rights to EVS, then repeat the preceding operations.</p>
|
||||
<div class="section" id="evs_01_0009__section909365011371"><h4 class="sectiontitle">Creating an Encrypted EVS Disk</h4><p id="evs_01_0009__p146495302155">Before you use the encryption function, KMS access rights need to be granted to EVS. If you have the Security Administrator rights, grant the KMS access rights to EVS directly. If you do not have this permission, contact a user with the security administrator rights to grant KMS access rights to EVS, then repeat the preceding operations.</p>
|
||||
<p id="evs_01_0009__p663854212927">For details about how to create an encrypted disk, see <a href="en-us_topic_0021738346.html">Create an EVS Disk</a>.</p>
|
||||
</div>
|
||||
<div class="section" id="evs_01_0009__section54711302212445"><h4 class="sectiontitle">Detaching an Encrypted EVS Disk</h4><p id="evs_01_0009__p8291130190">Before you detach an EVS disk encrypted by a CMK, check whether the CMK is disabled or scheduled for deletion. If the CMK is unavailable, the disk can still be used, but there is no guarantee how long it will be usable. If the disk is detached, it will not be possible to re-attach it later. In this case, do not detach the disk without a working CMK.</p>
|
||||
<p id="evs_01_0009__p234415151016">The restoration method varies depending on the current CMK status. For details, see <a href="evs_01_0001.html">EVS Disk Encryption</a>.</p>
|
||||
<p id="evs_01_0009__p14415194114592">The restoration method varies depending on the CMK status. For details, see <a href="https://docs.otc.t-systems.com/en-us/usermanual/evs/evs_01_0001.html" target="_blank" rel="noopener noreferrer">EVS Encryption</a>.</p>
|
||||
<p id="evs_01_0009__p135421342171213">If the CMK is available, the disk can be detached and re-attached, and data on the disk will not be lost.</p>
|
||||
<p id="evs_01_0009__p66047626212713">For details about how to detach an encrypted disk, see <a href="evs_01_0004.html">Detaching a Data Disk</a>.</p>
|
||||
</div>
|
||||
|
@ -1,6 +1,6 @@
|
||||
<a name="evs_01_0010"></a><a name="evs_01_0010"></a>
|
||||
|
||||
<h1 class="topictitle1">Managing a Shared EVS Disk</h1>
|
||||
<h1 class="topictitle1">Managing Shared EVS Disks</h1>
|
||||
<div id="body1505876939205"><div class="section" id="evs_01_0010__section22769430202827"><h4 class="sectiontitle">How to Use Shared VBD and SCSI Disks?</h4><div class="p" id="evs_01_0010__p30577766222323">You can create shared VBD disks or shared SCSI disks. It is recommended that you attach the shared disk to the ECSs in the same ECS group to improve service reliability.<ul id="evs_01_0010__ul290254221927"><li id="evs_01_0010__li54944535221927">Shared VBD EVS disks: The device type of a newly created shared EVS disk is VBD by default. Such disks can be used as virtual block storage devices, but do not support SCSI reservations. If SCSI reservations are required for your applications, create shared SCSI EVS disks.</li><li id="evs_01_0010__li59684574221927">Shared SCSI EVS disks: These EVS disks support SCSI reservations.<div class="notice" id="evs_01_0010__note57683778221927"><span class="noticetitle"><img src="public_sys-resources/notice_3.0-en-us.png"> </span><div class="noticebody"><ul id="evs_01_0010__ul8479164912431"><li id="evs_01_0010__li34792499432">To improve data security, you are advised to use SCSI reservations together with the anti-affinity policy of an ECS group. That said, ensure that shared SCSI EVS disks are only attached to ECSs in the same anti-affinity ECS group.</li><li id="evs_01_0010__li67215539435">If an ECS does not belong to any anti-affinity ECS group, you are advised not to attach shared SCSI EVS disks to this ECS. Otherwise, SCSI reservations may not work properly, which may put your data at risk.</li></ul>
|
||||
</div></div>
|
||||
<p id="evs_01_0010__p25421542202933">Concepts of the anti-affinity ECS group and SCSI reservations:</p>
|
||||
@ -13,9 +13,9 @@
|
||||
<p id="evs_01_0010__p49985363203941">For details about how to attach a shared EVS disk, see <a href="evs_01_0037.html">Attaching a Shared Disk</a>.</p>
|
||||
</div>
|
||||
<div class="section" id="evs_01_0010__section30398521204021"><h4 class="sectiontitle">Deleting a Shared EVS Disk</h4><p id="evs_01_0010__p5951849620416">Because a shared EVS disk can be attached to multiple <span id="evs_01_0010__text181532273810375">servers</span>, ensure that the shared EVS disk is detached from all the servers before deletion.</p>
|
||||
<p id="evs_01_0010__p9542931205056">For details about how to delete a shared EVS disk, see <a href="evs_01_0005.html">Deleting an EVS Disk</a>.</p>
|
||||
<p id="evs_01_0010__p9542931205056">For details about how to delete a shared EVS disk, see <a href="evs_01_0005.html">Deleting EVS Disks</a>.</p>
|
||||
</div>
|
||||
<div class="section" id="evs_01_0010__section34685374205131"><h4 class="sectiontitle">Expanding a Shared EVS Disk</h4><p id="evs_01_0010__p28646459205146">Shared EVS disks must be expanded when they are in the <strong id="evs_01_0010__b842352706162124">Available</strong> state. For details, see <a href="evs_01_0008.html">Expanding Capacity for an Available EVS Disk</a>.</p>
|
||||
<div class="section" id="evs_01_0010__section34685374205131"><h4 class="sectiontitle">Expanding a Shared EVS Disk</h4><p id="evs_01_0010__p28646459205146">Shared EVS disks must be expanded when they are in the <strong id="evs_01_0010__b842352706162124">Available</strong> state. For details, see <a href="evs_01_0007.html">Expanding Capacity for an In-use EVS Disk</a>.</p>
|
||||
</div>
|
||||
<div class="section" id="evs_01_0010__section1613519219248"><h4 class="sectiontitle">Related Operations</h4><p id="evs_01_0010__p206431518192410">For more disk sharing FAQs, see <a href="evs_01_0084.html">Sharing</a>.</p>
|
||||
</div>
|
||||
|
@ -5,14 +5,14 @@
|
||||
</div>
|
||||
<div class="section" id="evs_01_0011__section1225517183415"><h4 class="sectiontitle">Constraints</h4><ul id="evs_01_0011__ul18986173348"><li id="evs_01_0011__li79851714341">The snapshot status must be <strong id="evs_01_0011__b364355452811">Available</strong> or <strong id="evs_01_0011__b1643154122818">Error</strong>.</li><li id="evs_01_0011__li1098171713340">If a disk is deleted, all the snapshots created for this disk will also be deleted.</li><li id="evs_01_0011__li17981517183411">If a snapshot is deleted, disks rolled back and created from this snapshot are not affected.</li><li id="evs_01_0011__li163971533289">If you have reinstalled or changed the server OS, snapshots of the system disk are automatically deleted. Snapshots of the data disks can be used as usual.</li></ul>
|
||||
</div>
|
||||
<div class="section" id="evs_01_0011__section63311840155158"><h4 class="sectiontitle">Procedure</h4><ol id="evs_01_0011__evs_01_0111_ol9738844182712"><li id="evs_01_0011__evs_01_0111_li18764747165050"><span>Log in to the management console.</span></li><li id="evs_01_0011__evs_01_0111_li31082985151839"><span>Click <span><img id="evs_01_0011__en-us_topic_0021738346_image052111582392" src="en-us_image_0237893718.png"></span> in the upper left corner and select the desired region and project.</span></li><li id="evs_01_0011__evs_01_0111_li34664997165050"><span>Under <strong>Storage</strong>, click <strong>Elastic Volume Service</strong>.</span></li><li id="evs_01_0011__evs_01_0111_li6217779215198"><span>In the navigation tree on the left, choose <strong id="evs_01_0011__b842352706142731">Elastic Volume Service</strong> > <strong id="evs_01_0011__b842352706142734">Snapshots</strong>.</span><p><p id="evs_01_0011__evs_01_0111_evs_01_0111_p2231505911261">The snapshot list page is displayed.</p>
|
||||
</p></li><li id="evs_01_0011__evs_01_0111_li6663006915254"><span>In the snapshot list, locate the row that contains the target snapshot and click <strong id="evs_01_0011__b842352706203619">Delete</strong> in the <strong id="evs_01_0011__b842352706203623">Operation</strong> column.</span></li><li id="evs_01_0011__evs_01_0111_li23844343154147"><span>(Optional) If multiple snapshots are to be deleted, select <span><img id="evs_01_0011__evs_01_0111_image40687489154147" src="en-us_image_0238263087.png"></span> in front of each snapshot and click <span class="uicontrol" id="evs_01_0011__evs_01_0111_uicontrol30643081154147"><b>Delete</b></span> in the upper area of the list.</span></li><li id="evs_01_0011__li101701301356"><span>In the displayed dialog box, confirm the information and click <span class="uicontrol" id="evs_01_0011__uicontrol1665013449"><b>Yes</b></span>.</span><p><p id="evs_01_0011__p7187221103513">If the snapshot is no longer displayed in the snapshot list, the snapshot is deleted successfully.</p>
|
||||
<div class="section" id="evs_01_0011__section63311840155158"><h4 class="sectiontitle">Procedure</h4><ol id="evs_01_0011__evs_01_0111_ol9738844182712"><li id="evs_01_0011__li5884586202528"><span>Log in to the management console.</span></li><li id="evs_01_0011__evs_01_0111_li31082985151839"><span>Click <span><img id="evs_01_0011__en-us_topic_0021738346_image052111582392" src="en-us_image_0237893718.png"></span> in the upper left corner and select the desired region and project.</span></li><li id="evs_01_0011__evs_01_0111_li34664997165050"><span>Under <strong>Storage</strong>, click <strong>Elastic Volume Service</strong>.</span></li><li id="evs_01_0011__evs_01_0111_li6217779215198"><span>In the navigation pane on the left, choose <strong id="evs_01_0011__b842352706142731">Elastic Volume Service</strong> > <strong id="evs_01_0011__b842352706142734">Snapshots</strong>.</span><p><p id="evs_01_0011__evs_01_0111_evs_01_0111_p2231505911261">The snapshot list page is displayed.</p>
|
||||
</p></li><li id="evs_01_0011__evs_01_0111_li6663006915254"><span>In the snapshot list, locate the row that contains the target snapshot and click <strong id="evs_01_0011__b842352706203619">Delete</strong> in the <strong id="evs_01_0011__b842352706203623">Operation</strong> column.</span></li><li id="evs_01_0011__evs_01_0111_li23844343154147"><span>(Optional) If multiple snapshots are to be deleted, select <span><img id="evs_01_0011__evs_01_0111_image40687489154147" src="en-us_image_0238263087.png"></span> in front of each snapshot and click <span class="uicontrol" id="evs_01_0011__evs_01_0111_uicontrol30643081154147"><b>Delete</b></span> in the upper area of the list.</span></li><li id="evs_01_0011__li101701301356"><span>In the displayed dialog box, confirm the information and click <span class="uicontrol" id="evs_01_0011__uicontrol476887723"><b>Yes</b></span>.</span><p><p id="evs_01_0011__p7187221103513">If the snapshot is no longer displayed in the snapshot list, the snapshot is deleted successfully.</p>
|
||||
</p></li></ol>
|
||||
</div>
|
||||
</div>
|
||||
<div>
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="evs_01_0111.html">Managing Snapshots</a></div>
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="evs_01_0111.html">Managing EVS Snapshots</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
@ -5,13 +5,13 @@
|
||||
</div>
|
||||
<div class="section" id="evs_01_0012__section137571154203410"><h4 class="sectiontitle">Constraints</h4><ul id="evs_01_0012__ul0831654113415"><li id="evs_01_0012__li88311154183410">A snapshot can be rolled back only to its source disk. Rollback to another disk is not possible.</li><li id="evs_01_0012__li283115473420">A snapshot can be rolled back only when the snapshot status is <strong id="evs_01_0012__b842352706202529">Available</strong> and the source disk status is <strong id="evs_01_0012__b842352706202551">Available</strong> (not attached to any <span id="evs_01_0012__text150715355617640">server</span>) or <strong id="evs_01_0012__b842352706202556">Rollback failed</strong>.</li></ul>
|
||||
</div>
|
||||
<div class="section" id="evs_01_0012__section23223906174233"><h4 class="sectiontitle">Procedure</h4><ol id="evs_01_0012__ol46566557174233"><li id="evs_01_0012__li55212373174233"><span>Log in to the management console.</span></li><li id="evs_01_0012__li43017210174233"><span>Click <span><img id="evs_01_0012__en-us_topic_0021738346_image052111582392" src="en-us_image_0237893718.png"></span> in the upper left corner and select the desired region and project.</span></li><li id="evs_01_0012__li51610576174233"><span>Under <strong>Storage</strong>, click <strong>Elastic Volume Service</strong>.</span></li><li id="evs_01_0012__li19707093174233"><span>In the navigation tree on the left, choose <strong id="evs_01_0012__b842352706142731">Elastic Volume Service</strong> > <strong id="evs_01_0012__b842352706142734">Snapshots</strong>.</span><p><p id="evs_01_0012__p61842000174233">The snapshot list page is displayed.</p>
|
||||
<div class="section" id="evs_01_0012__section23223906174233"><h4 class="sectiontitle">Procedure</h4><ol id="evs_01_0012__ol46566557174233"><li id="evs_01_0012__li5884586202528"><span>Log in to the management console.</span></li><li id="evs_01_0012__li43017210174233"><span>Click <span><img id="evs_01_0012__en-us_topic_0021738346_image052111582392" src="en-us_image_0237893718.png"></span> in the upper left corner and select the desired region and project.</span></li><li id="evs_01_0012__li51610576174233"><span>Under <strong>Storage</strong>, click <strong>Elastic Volume Service</strong>.</span></li><li id="evs_01_0012__li19707093174233"><span>In the navigation pane on the left, choose <strong id="evs_01_0012__b842352706142731">Elastic Volume Service</strong> > <strong id="evs_01_0012__b842352706142734">Snapshots</strong>.</span><p><p id="evs_01_0012__p61842000174233">The snapshot list page is displayed.</p>
|
||||
</p></li><li id="evs_01_0012__li43146110174233"><span>In the snapshot list, locate the row that contains the target snapshot and click <strong id="evs_01_0012__b113430685203037">Roll Back Disk</strong> in the <strong id="evs_01_0012__b1381690552203037">Operation</strong> column.</span></li><li id="evs_01_0012__li1432673915373"><span>In the displayed dialog box, click <strong id="evs_01_0012__b842352706143726">Yes</strong>.</span></li><li id="evs_01_0012__li5174061174233"><span>The snapshot list is displayed. After the snapshot status changes from <strong id="evs_01_0012__b28244076020317">Rolling back</strong> to <strong id="evs_01_0012__b202676872820317">Available</strong>, the data rollback is successful.</span></li></ol>
|
||||
</div>
|
||||
</div>
|
||||
<div>
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="evs_01_0111.html">Managing Snapshots</a></div>
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="evs_01_0111.html">Managing EVS Snapshots</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
@ -3,11 +3,11 @@
|
||||
<h1 class="topictitle1">Creating an EVS Disk from a Snapshot</h1>
|
||||
<div id="body1505900308312"><div class="section" id="evs_01_0013__section63311840155158"><h4 class="sectiontitle">Scenarios</h4><p id="evs_01_0013__p176191501212">This section describes how to create an EVS disk on the <strong id="evs_01_0013__b12536174121">Snapshots</strong> page. Besides, you can also create an EVS disk from a snapshot by specifying the <strong id="evs_01_0013__b842352706183711">Create from snapshot</strong> parameter on the disk creation page. For details, see <a href="en-us_topic_0021738346.html">Create an EVS Disk</a>.</p>
|
||||
</div>
|
||||
<div class="section" id="evs_01_0013__section653510274355"><h4 class="sectiontitle">Constraints</h4><ul id="evs_01_0013__ul361122703515"><li id="evs_01_0013__li66117279355">The disk type of the new disk is the same as that of the snapshot's source disk.</li><li id="evs_01_0013__li14611127173510">The device type of the new disk is the same as that of the snapshot's source disk.</li><li id="evs_01_0013__li18611527113519">The encryption attribute of the new disk is the same as that of the snapshot's source disk.</li><li id="evs_01_0013__li36111227123511">A maximum of 128 disks can be created from this snapshot.</li><li id="evs_01_0013__li1061112733518">Batch disk creation is not possible, and the quantity parameter must be set to <strong id="evs_01_0013__b1013145517173">1</strong>.</li></ul>
|
||||
<div class="section" id="evs_01_0013__section653510274355"><h4 class="sectiontitle">Constraints</h4><ul id="evs_01_0013__ul361122703515"><li id="evs_01_0013__li66117279355">The disk type, device type, encryption, and snapshot attributes of the new disk are the same as those of the snapshot's source disk.</li><li id="evs_01_0013__li36111227123511">A maximum of 128 disks can be created from a snapshot.</li><li id="evs_01_0013__li1061112733518">Batch disk creation is not possible, and the quantity parameter must be set to <strong id="evs_01_0013__b1013145517173">1</strong>.</li><li id="evs_01_0013__li11937912163719">If a disk is created from a snapshot, the AZ of the disk is the same as that of the snapshot's source disk and cannot be changed.</li></ul>
|
||||
</div>
|
||||
<div class="section" id="evs_01_0013__section53290500174512"><h4 class="sectiontitle">Procedure</h4><ol id="evs_01_0013__ol5921166174512"><li id="evs_01_0013__li36140935174512"><span>Log in to the management console.</span></li><li id="evs_01_0013__li41734648174512"><span>Click <span><img id="evs_01_0013__en-us_topic_0021738346_image052111582392" src="en-us_image_0237893718.png"></span> in the upper left corner and select the desired region and project.</span></li><li id="evs_01_0013__li40067520174512"><span>Under <strong id="evs_01_0013__b6494132003218">Storage</strong>, click <strong id="evs_01_0013__b1049419203325">Elastic Volume Service</strong>.</span></li><li id="evs_01_0013__li24243707174512"><span>In the navigation tree on the left, choose <strong id="evs_01_0013__b842352706142731">Elastic Volume Service</strong> > <strong id="evs_01_0013__b842352706142734">Snapshots</strong>.</span><p><p id="evs_01_0013__p25063366174512">The snapshot list page is displayed.</p>
|
||||
<div class="section" id="evs_01_0013__section53290500174512"><h4 class="sectiontitle">Procedure</h4><ol id="evs_01_0013__ol5921166174512"><li id="evs_01_0013__li5884586202528"><span>Log in to the management console.</span></li><li id="evs_01_0013__li41734648174512"><span>Click <span><img id="evs_01_0013__en-us_topic_0021738346_image052111582392" src="en-us_image_0237893718.png"></span> in the upper left corner and select the desired region and project.</span></li><li id="evs_01_0013__li40067520174512"><span>Under <strong id="evs_01_0013__b6494132003218">Storage</strong>, click <strong id="evs_01_0013__b1049419203325">Elastic Volume Service</strong>.</span></li><li id="evs_01_0013__li24243707174512"><span>In the navigation pane on the left, choose <strong id="evs_01_0013__b842352706142731">Elastic Volume Service</strong> > <strong id="evs_01_0013__b842352706142734">Snapshots</strong>.</span><p><p id="evs_01_0013__p25063366174512">The snapshot list page is displayed.</p>
|
||||
</p></li><li id="evs_01_0013__li16866776174512"><span>In the snapshot list, locate the row that contains the target snapshot and click <strong id="evs_01_0013__b113430685203037">Create Disk</strong> in the <strong id="evs_01_0013__b1381690552203037">Operation</strong> column.</span></li><li id="evs_01_0013__li23100991165746"><span>Set the EVS disk parameters. For details, see parameter descriptions and operations provided in <a href="en-us_topic_0021738346.html">Create an EVS Disk</a>.</span><p><div class="note" id="evs_01_0013__note59240982165746"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="evs_01_0013__p63406793165746">A maximum of 128 disks can be created from a snapshot.</p>
|
||||
<p id="evs_01_0013__p1091713415143">If you create a disk from a snapshot, the disk capacity must be greater than or equal to the snapshot size. In the condition that you do not specify the disk capacity, if the snapshot size is smaller than 10 GB, the default capacity 10 GB will be used as the disk capacity; if the snapshot size is greater than 10 GB, the disk capacity will be consistent with the snapshot size.</p>
|
||||
<p id="evs_01_0013__p1091713415143">If you create a disk from a snapshot, the disk capacity must be greater than or equal to the snapshot size. In the condition that you do not specify the disk capacity, if the snapshot size is smaller than 10 GiB, the default capacity 10 GiB will be used as the disk capacity; if the snapshot size is greater than 10 GiB, the disk capacity will be consistent with the snapshot size.</p>
|
||||
</div></div>
|
||||
</p></li><li id="evs_01_0013__li32864826174512"><span>Click <strong id="evs_01_0013__b1251142019328">Create Now</strong>.</span></li><li id="evs_01_0013__li17355737221135"><span>Go back to the disk list page and view the disk status.</span><p><p id="evs_01_0013__en-us_topic_0021738346_p58239715173253">When the disk status changes to <strong id="evs_01_0013__en-us_topic_0021738346_b2076608000194835">Available</strong>, the disk is successfully created.</p>
|
||||
</p></li></ol>
|
||||
@ -15,7 +15,7 @@
|
||||
</div>
|
||||
<div>
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="evs_01_0111.html">Managing Snapshots</a></div>
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="evs_01_0111.html">Managing EVS Snapshots</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
@ -1,7 +1,7 @@
|
||||
<a name="evs_01_0014"></a><a name="evs_01_0014"></a>
|
||||
|
||||
<h1 class="topictitle1">Adding a Tag</h1>
|
||||
<div id="body1505876940104"><div class="section" id="evs_01_0014__section35485408221444"><h4 class="sectiontitle">Scenarios</h4><p id="evs_01_0014__p49142995222032">This section is used to guide users to add a tag for an existing EVS disk. You can also add tags during the EVS disk creation. For details, see <a href="en-us_topic_0021738346.html">Create an EVS Disk</a>.</p>
|
||||
<div id="body1505876940104"><div class="section" id="evs_01_0014__section35485408221444"><h4 class="sectiontitle">Scenarios</h4><p id="evs_01_0014__p49142995222032">This section is used to guide users to add a tag for an existing EVS disk. You can also add tags during the disk creation. For details, see <a href="en-us_topic_0021738346.html">Create an EVS Disk</a>.</p>
|
||||
<p id="evs_01_0014__p30708999221554">Tags are used to identify the cloud resources for purposes of easy categorization and quick search.</p>
|
||||
</div>
|
||||
<ul id="evs_01_0014__ul4400966221554"><li id="evs_01_0014__li17231162092">A tag is composed of a key-value pair.<ul id="evs_01_0014__ul122415167919"><li id="evs_01_0014__li812515558919">Key:<ul id="evs_01_0014__ul10797172141011"><li id="evs_01_0014__li5265857497">Must be unique for each resource.</li><li id="evs_01_0014__li101753591999">Can contain a maximum of 36 characters.</li><li id="evs_01_0014__li62561612913">Can contain only digits, letters, hyphens (-), and underscores (_).</li></ul>
|
||||
@ -9,7 +9,7 @@
|
||||
</li></ul>
|
||||
</li><li id="evs_01_0014__li4036983152211">A maximum of 10 tags can be added for an EVS disk.</li></ul>
|
||||
<div class="section" id="evs_01_0014__section40605822221452"><h4 class="sectiontitle">Procedure</h4><ol id="evs_01_0014__ol1977955163311"><li id="evs_01_0014__li2097716553331"><span>Log in to the management console.</span></li><li id="evs_01_0014__li2935870315121"><span>Click <span><img id="evs_01_0014__en-us_topic_0021738346_image052111582392" src="en-us_image_0237893718.png"></span> in the upper left corner and select the desired region and project.</span></li><li id="evs_01_0014__li3843952015053"><span>Under <strong>Storage</strong>, click <strong>Elastic Volume Service</strong>.</span><p><p id="evs_01_0014__p16002076152423">The disk list page is displayed.</p>
|
||||
</p></li><li id="evs_01_0014__li7585973201558"><span>In the disk list, locate the target disk and click the disk name.</span><p><p id="evs_01_0014__p63208682161856">The disk details page is displayed.</p>
|
||||
</p></li><li id="evs_01_0014__li7585973201558"><span>In the disk list, locate the desired disk and click the disk name.</span><p><p id="evs_01_0014__p63208682161856">The disk details page is displayed.</p>
|
||||
</p></li><li id="evs_01_0014__li35882119162654"><span>Click the <strong id="evs_01_0014__b842352706203914">Tags</strong> tab.</span></li><li id="evs_01_0014__li12655052162539"><span>Click <strong id="evs_01_0014__b842352706111832">Add Tag</strong>.</span><p><p id="evs_01_0014__p66848423162054">The <strong id="evs_01_0014__b842352706143936">Add Tag</strong> page is displayed.</p>
|
||||
</p></li><li id="evs_01_0014__li580121211342"><span>Enter a key and a value for a tag and click <strong id="evs_01_0014__b84235270620413">OK</strong>.</span><p><ul id="evs_01_0014__ul33673651151239"><li id="evs_01_0014__li34627407151239"><strong id="evs_01_0014__b842352706201920">Key</strong>: This parameter is mandatory.</li><li id="evs_01_0014__li43211215151239"><strong id="evs_01_0014__b842352706201924">Value</strong>: This parameter is optional.</li></ul>
|
||||
<p id="evs_01_0014__p11140920162241">The <strong id="evs_01_0014__b842352706204125">Tags</strong> tab is displayed, and you can view the newly added tag.</p>
|
||||
|
@ -3,8 +3,8 @@
|
||||
<h1 class="topictitle1">Modifying a Tag</h1>
|
||||
<div id="body1505876940725"><div class="section" id="evs_01_0015__section6439903622216"><h4 class="sectiontitle">Scenarios</h4><p id="evs_01_0015__p50429765162352">You can change the value of a tag for an existing disk, but cannot change the key of a tag.</p>
|
||||
</div>
|
||||
<div class="section" id="evs_01_0015__section24415573222113"><h4 class="sectiontitle">Procedure</h4><ol id="evs_01_0015__ol10576190162450"><li id="evs_01_0015__li18611406162450"><span>Log in to the management console.</span></li><li id="evs_01_0015__li54238507151832"><span>Click <span><img id="evs_01_0015__en-us_topic_0021738346_image052111582392" src="en-us_image_0237893718.png"></span> in the upper left corner and select the desired region and project.</span></li><li id="evs_01_0015__li33284932162450"><span>Under <strong>Storage</strong>, click <strong>Elastic Volume Service</strong>.</span><p><p id="evs_01_0015__p31128940162450">The disk list page is displayed.</p>
|
||||
</p></li><li id="evs_01_0015__li38416186162450"><span>In the disk list, locate the target disk and click on the disk name.</span><p><p id="evs_01_0015__p10201354162450">The disk details page is displayed.</p>
|
||||
<div class="section" id="evs_01_0015__section24415573222113"><h4 class="sectiontitle">Procedure</h4><ol id="evs_01_0015__ol10576190162450"><li id="evs_01_0015__li5884586202528"><span>Log in to the management console.</span></li><li id="evs_01_0015__li54238507151832"><span>Click <span><img id="evs_01_0015__en-us_topic_0021738346_image052111582392" src="en-us_image_0237893718.png"></span> in the upper left corner and select the desired region and project.</span></li><li id="evs_01_0015__li33284932162450"><span>Under <strong>Storage</strong>, click <strong>Elastic Volume Service</strong>.</span><p><p id="evs_01_0015__p31128940162450">The disk list page is displayed.</p>
|
||||
</p></li><li id="evs_01_0015__li38416186162450"><span>In the disk list, locate the desired disk and click the disk name.</span><p><p id="evs_01_0015__p10201354162450">The disk details page is displayed.</p>
|
||||
</p></li><li id="evs_01_0015__li65111262162728"><span>Click the <strong id="evs_01_0015__b842352706203914">Tags</strong> tab.</span></li><li id="evs_01_0015__li24703328162450"><span>Locate the target tag and click <strong id="evs_01_0015__b842352706204331">Edit</strong> in the <strong id="evs_01_0015__b842352706204335">Operation</strong> column.</span><p><p id="evs_01_0015__p21003364162450">The <strong id="evs_01_0015__b842352706143936">Edit Tag</strong> page is displayed.</p>
|
||||
</p></li><li id="evs_01_0015__li54812551162450"><span>Change the value of the tag and click <strong id="evs_01_0015__b842352706204525">OK</strong>.</span><p><p id="evs_01_0015__p23550914162450">Return to the tag list. If the tag value is changed, the modification is complete.</p>
|
||||
</p></li></ol>
|
||||
|
@ -3,10 +3,10 @@
|
||||
<h1 class="topictitle1">Deleting a Tag</h1>
|
||||
<div id="body1505877050393"><div class="section" id="evs_01_0016__section10163781222140"><h4 class="sectiontitle">Scenarios</h4><p id="evs_01_0016__p7253542165050">If an existing tag is no longer needed, you can delete it.</p>
|
||||
</div>
|
||||
<div class="section" id="evs_01_0016__section42910475222150"><h4 class="sectiontitle">Procedure</h4><ol id="evs_01_0016__ol65281882165050"><li id="evs_01_0016__li18764747165050"><span>Log in to the management console.</span></li><li id="evs_01_0016__li2935870315121"><span>Click <span><img id="evs_01_0016__en-us_topic_0021738346_image052111582392" src="en-us_image_0237893718.png"></span> in the upper left corner and select the desired region and project.</span></li><li id="evs_01_0016__li34664997165050"><span>Under <strong>Storage</strong>, click <strong>Elastic Volume Service</strong>.</span><p><p id="evs_01_0016__p43549519165050">The disk list page is displayed.</p>
|
||||
</p></li><li id="evs_01_0016__li37850144165050"><span>In the disk list, locate the target disk and click the disk name.</span><p><p id="evs_01_0016__p5106976165050">The disk details page is displayed.</p>
|
||||
<div class="section" id="evs_01_0016__section42910475222150"><h4 class="sectiontitle">Procedure</h4><ol id="evs_01_0016__ol65281882165050"><li id="evs_01_0016__li5884586202528"><span>Log in to the management console.</span></li><li id="evs_01_0016__li2935870315121"><span>Click <span><img id="evs_01_0016__en-us_topic_0021738346_image052111582392" src="en-us_image_0237893718.png"></span> in the upper left corner and select the desired region and project.</span></li><li id="evs_01_0016__li34664997165050"><span>Under <strong>Storage</strong>, click <strong>Elastic Volume Service</strong>.</span><p><p id="evs_01_0016__p43549519165050">The disk list page is displayed.</p>
|
||||
</p></li><li id="evs_01_0016__li37850144165050"><span>In the disk list, locate the desired disk and click the disk name.</span><p><p id="evs_01_0016__p5106976165050">The disk details page is displayed.</p>
|
||||
</p></li><li id="evs_01_0016__li45962789165050"><span>Click the <strong id="evs_01_0016__b842352706203914">Tags</strong> tab.</span></li><li id="evs_01_0016__li11011918165050"><span>Locate the target tag and click <strong id="evs_01_0016__b842352706204331">Delete</strong> in the <strong id="evs_01_0016__b842352706204335">Operation</strong> column.</span><p><p id="evs_01_0016__p31998406165050">The <strong id="evs_01_0016__b842352706143936">Delete Tag</strong> page is displayed.</p>
|
||||
</p></li><li id="evs_01_0016__li1380765813409"><span>Confirm the information and click <strong id="evs_01_0016__b1648352008">Yes</strong>.</span><p><p id="evs_01_0016__p180935894011">Return to the tag list. If the tag is no longer displayed in the tag list, the deletion is successful.</p>
|
||||
</p></li><li id="evs_01_0016__li1380765813409"><span>Confirm the information and click <strong id="evs_01_0016__b494237038">Yes</strong>.</span><p><p id="evs_01_0016__p180935894011">Return to the tag list. If the tag is no longer displayed in the tag list, the deletion is successful.</p>
|
||||
</p></li></ol>
|
||||
</div>
|
||||
</div>
|
||||
|
@ -3,15 +3,15 @@
|
||||
<h1 class="topictitle1">Extending Partitions and File Systems for SCSI Disks (Linux)</h1>
|
||||
<div id="body1506410165082"><div class="section" id="evs_01_0018__section4385650719406"><h4 class="sectiontitle">Scenarios</h4><p id="evs_01_0018__p2029473616495">After a disk has been expanded on the management console, the disk size is enlarged, but the additional space cannot be used directly.</p>
|
||||
<p id="evs_01_0018__p6821893715">In Linux, you must allocate the additional space to an existing partition or a new partition.</p>
|
||||
<div class="p" id="evs_01_0018__p24596192205637">This section uses CentOS 7.4 64bit as the sample OS to describe how to extend an MBR partition of a SCSI data disk. The method for allocating the additional space varies depending on the server OS. This document is used for reference only. For detailed operations and differences, see the corresponding OS documents.<ul id="evs_01_0018__ul7123597717"><li id="evs_01_0018__li78122016151915"><a href="#evs_01_0018__section12265143819280">Creating a New MBR Partition</a></li><li id="evs_01_0018__li15123599713"><a href="#evs_01_0018__section31113372194023">Extending an Existing MBR Partition</a></li></ul>
|
||||
<div class="p" id="evs_01_0018__p24596192205637">This section uses CentOS 7.4 64bit as the sample OS to describe how to extend an MBR partition of a SCSI data disk. The method for allocating the additional space varies with the server OS. This section is used for reference only. For detailed operations and differences, see the corresponding OS documents.<ul id="evs_01_0018__ul7123597717"><li id="evs_01_0018__li78122016151915"><a href="#evs_01_0018__section12265143819280">Creating a New MBR Partition</a></li><li id="evs_01_0018__li15123599713"><a href="#evs_01_0018__section31113372194023">Extending an Existing MBR Partition</a></li></ul>
|
||||
</div>
|
||||
<div class="notice" id="evs_01_0018__note206209142082"><span class="noticetitle"><img src="public_sys-resources/notice_3.0-en-us.png"> </span><div class="noticebody"><p id="evs_01_0018__en-us_topic_0017616396_p1185312105267">Performing the expansion operations with caution. Misoperation may lead to data loss or exceptions. Therefore, you are advised to back up the disk data using backups or snapshots before expansion. For details about backups, see <a href="evs_01_0110.html">Managing EVS Backup</a>. For details about snapshots, see <a href="en-us_topic_0066615262.html">Creating a Snapshot</a>.</p>
|
||||
<div class="notice" id="evs_01_0018__note206209142082"><span class="noticetitle"><img src="public_sys-resources/notice_3.0-en-us.png"> </span><div class="noticebody"><p id="evs_01_0018__en-us_topic_0017616396_p1185312105267">Performing the expansion operations with caution. Misoperation may lead to data loss or exceptions. Therefore, you are advised to back up the disk data using CBR or snapshots before expansion. For details about using CBR, see <a href="evs_01_0110.html">Managing EVS Backups</a>. For details about using snapshots, see <a href="en-us_topic_0066615262.html">Creating a Snapshot</a>.</p>
|
||||
</div></div>
|
||||
</div>
|
||||
<div class="section" id="evs_01_0018__section19088989195835"><h4 class="sectiontitle">Prerequisites</h4><ul id="evs_01_0018__evs_01_0072_ul28913191171813"><li id="evs_01_0018__evs_01_0072_li1233185612427">You have expanded the disk capacity and attached the disk to a <span id="evs_01_0018__evs_01_0072_text1615511293514">server</span> on the management console. For details, see <a href="evs_01_0007.html">Expanding Capacity for an In-use EVS Disk</a> or <a href="evs_01_0008.html">Expanding Capacity for an Available EVS Disk</a>.</li><li id="evs_01_0018__evs_01_0072_li36962755115557">You have logged in to the <span id="evs_01_0018__evs_01_0072_evs_01_0108_text25940422717248">server</span>.<ul id="evs_01_0018__evs_01_0072_evs_01_0108_ul6229092211568"><li id="evs_01_0018__evs_01_0072_evs_01_0108_li197989548398">For how to log in to an ECS, see the <em id="evs_01_0018__evs_01_0072_evs_01_0108_i157642033171941">Elastic Cloud Server User Guide</em>.</li><li id="evs_01_0018__evs_01_0072_evs_01_0108_li7220898115452">For how to log in to a BMS, see the <em id="evs_01_0018__evs_01_0072_evs_01_0108_i842352697172014">Bare Metal Server User Guide</em>.</li></ul>
|
||||
</li></ul>
|
||||
</div>
|
||||
<div class="section" id="evs_01_0018__section12265143819280"><a name="evs_01_0018__section12265143819280"></a><a name="section12265143819280"></a><h4 class="sectiontitle">Creating a New MBR Partition</h4><p id="evs_01_0018__p20813164219293">Originally, data disk <strong id="evs_01_0018__b0459749123915">/dev/sda</strong> has 50 GB and one partition (<strong id="evs_01_0018__b14592498392">/dev/sda1</strong>), and then 50 GB is added to the disk. The following procedure shows you how to create a new MBR partition <strong id="evs_01_0018__b1532161912400">/dev/sda2</strong> with this 50 GB.</p>
|
||||
<div class="section" id="evs_01_0018__section12265143819280"><a name="evs_01_0018__section12265143819280"></a><a name="section12265143819280"></a><h4 class="sectiontitle">Creating a New MBR Partition</h4><p id="evs_01_0018__p20813164219293">Originally, data disk <strong id="evs_01_0018__b0459749123915">/dev/sda</strong> has 50 GiB and one partition (<strong id="evs_01_0018__b14592498392">/dev/sda1</strong>), and then 50 GiB is added to the disk. The following procedure shows you how to create a new MBR partition <strong id="evs_01_0018__b1532161912400">/dev/sda2</strong> with this 50 GiB.</p>
|
||||
<ol id="evs_01_0018__ol64002072195025"><li id="evs_01_0018__li1253360195025"><span>Run the following command to view the disk partition information:</span><p><p id="evs_01_0018__p5241531195025"><strong id="evs_01_0018__b8038932195025">fdisk -l</strong></p>
|
||||
<div class="p" id="evs_01_0018__p21910876195025">Information similar to the following is displayed:<pre class="screen" id="evs_01_0018__screen16607193113518">[root@ecs-scsi ~]# fdisk -l
|
||||
|
||||
@ -187,7 +187,7 @@ tmpfs tmpfs 104M 0 104M 0% /run/user/0
|
||||
</div>
|
||||
<div class="section" id="evs_01_0018__section31113372194023"><a name="evs_01_0018__section31113372194023"></a><a name="section31113372194023"></a><h4 class="sectiontitle">Extending an Existing MBR Partition</h4><div class="notice" id="evs_01_0018__note136201693912"><span class="noticetitle"><img src="public_sys-resources/notice_3.0-en-us.png"> </span><div class="noticebody"><p id="evs_01_0018__evs_01_0109_p065513114456">If the additional space is allocated to an existing partition, data on the disk will not be cleared but you must use <strong id="evs_01_0018__evs_01_0109_b1814492110326">umount</strong> to unmount the existing partition. In this case, services will be affected.</p>
|
||||
</div></div>
|
||||
<p id="evs_01_0018__p1393412227431">Originally, SCSI data disk <strong id="evs_01_0018__b24141315910">/dev/sda</strong> has 100 GB and two partitions (<strong id="evs_01_0018__b9519138912">/dev/sda1</strong> and <strong id="evs_01_0018__b18610139919">/dev/sda2</strong>), and then 50 GB is added to the disk. The following procedure shows you how to add this 50 GB to the existing MBR partition <strong id="evs_01_0018__b860283619105">/dev/sda2</strong>.</p>
|
||||
<p id="evs_01_0018__p1393412227431">Originally, SCSI data disk <strong id="evs_01_0018__b24141315910">/dev/sda</strong> has 100 GiB and two partitions (<strong id="evs_01_0018__b9519138912">/dev/sda1</strong> and <strong id="evs_01_0018__b18610139919">/dev/sda2</strong>), and then 50 GiB is added to the disk. The following procedure shows you how to add this 50 GiB to the existing MBR partition <strong id="evs_01_0018__b860283619105">/dev/sda2</strong>.</p>
|
||||
<p id="evs_01_0018__p97625416398">During an expansion, the additional space is added to the end of the disk. Therefore, if the disk has multiple partitions, the additional space can only be allocated to the partition at the disk end.</p>
|
||||
<ol id="evs_01_0018__ol1293195319479"><li id="evs_01_0018__li6396237219479"><a name="evs_01_0018__li6396237219479"></a><a name="li6396237219479"></a><span>Run the following command to view the disk partition information:</span><p><p id="evs_01_0018__p1385482419479"><strong id="evs_01_0018__b153942419479">fdisk -l</strong></p>
|
||||
<div class="p" id="evs_01_0018__p3609954819479">Information similar to the following is displayed:<pre class="screen" id="evs_01_0018__screen1589053417329">[root@ecs-scsi ~]# fdisk -l
|
||||
@ -340,7 +340,7 @@ The filesystem on /dev/sda2 is now 26214400 blocks long.</pre>
|
||||
<p id="evs_01_0018__p193525482311">In this example, run the following command to create the <strong id="evs_01_0018__b1277025624113">/mnt/test</strong> mount point:</p>
|
||||
<p id="evs_01_0018__p12353194823113"><strong id="evs_01_0018__b1335317486316">mkdir</strong> <strong id="evs_01_0018__b11353144833114">/mnt/test</strong></p>
|
||||
</li><li id="evs_01_0018__li761184712229">Run the following command to mount the partition:<p id="evs_01_0018__p1161144710226"><a name="evs_01_0018__li761184712229"></a><a name="li761184712229"></a><strong id="evs_01_0018__b107181832162612">mount</strong> <em id="evs_01_0018__i16719153219265">Disk partition</em> <em id="evs_01_0018__i9719832112614">Mount point</em></p>
|
||||
<p id="evs_01_0018__p96114720227">In this example, run the following command to mount the partition <strong id="evs_01_0018__b1100153512262">/dev/sda2</strong> on <strong id="evs_01_0018__b21014350266">/mnt/test</strong>:</p>
|
||||
<p id="evs_01_0018__p96114720227">In this example, run the following command to mount partition <strong id="evs_01_0018__b1100153512262">/dev/sda2</strong> on <strong id="evs_01_0018__b21014350266">/mnt/test</strong>:</p>
|
||||
<p id="evs_01_0018__p36164782213"><strong id="evs_01_0018__b69871321639">mount /dev/sda2 /mnt/test</strong></p>
|
||||
<div class="note" id="evs_01_0018__note1861194782215"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="evs_01_0018__evs_01_0109_p14348212195025_1">If the new partition is mounted on a directory that is not empty, the subdirectories and files in the directory will be hidden. Therefore, you are advised to mount the new partition on an empty directory or a new directory. If the new partition must be mounted on a directory that is not empty, move the subdirectories and files in this directory to another directory temporarily. After the partition is successfully mounted, move the subdirectories and files back.</p>
|
||||
</div></div>
|
||||
@ -350,7 +350,7 @@ The filesystem on /dev/sda2 is now 26214400 blocks long.</pre>
|
||||
<p id="evs_01_0018__evs_01_0109_p12611147172210_1">In this example, run the following command to create the <strong id="evs_01_0018__evs_01_0109_b15799115618383_1">/mnt/test</strong> mount point:</p>
|
||||
<p id="evs_01_0018__evs_01_0109_p1661144710223_1"><strong id="evs_01_0018__evs_01_0109_b4364122213513_1">mkdir</strong> <strong id="evs_01_0018__evs_01_0109_b1365132211351_1">/mnt/test</strong></p>
|
||||
</li><li id="evs_01_0018__li2138532245">Run the following command to mount the partition:<p id="evs_01_0018__evs_01_0018_p1161144710226"><a name="evs_01_0018__li2138532245"></a><a name="li2138532245"></a><strong id="evs_01_0018__evs_01_0018_b107181832162612">mount</strong> <em id="evs_01_0018__evs_01_0018_i16719153219265">Disk partition</em> <em id="evs_01_0018__evs_01_0018_i9719832112614">Mount point</em></p>
|
||||
<p id="evs_01_0018__evs_01_0018_p96114720227">In this example, run the following command to mount the partition <strong id="evs_01_0018__evs_01_0018_b1100153512262">/dev/sda2</strong> on <strong id="evs_01_0018__evs_01_0018_b21014350266">/mnt/test</strong>:</p>
|
||||
<p id="evs_01_0018__evs_01_0018_p96114720227">In this example, run the following command to mount partition <strong id="evs_01_0018__evs_01_0018_b1100153512262">/dev/sda2</strong> on <strong id="evs_01_0018__evs_01_0018_b21014350266">/mnt/test</strong>:</p>
|
||||
<p id="evs_01_0018__evs_01_0018_p36164782213"><strong id="evs_01_0018__evs_01_0018_b69871321639">mount /dev/sda2 /mnt/test</strong></p>
|
||||
<div class="note" id="evs_01_0018__evs_01_0018_note1861194782215"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="evs_01_0018__evs_01_0018_evs_01_0109_p14348212195025">If the new partition is mounted on a directory that is not empty, the subdirectories and files in the directory will be hidden. Therefore, you are advised to mount the new partition on an empty directory or a new directory. If the new partition must be mounted on a directory that is not empty, move the subdirectories and files in this directory to another directory temporarily. After the partition is successfully mounted, move the subdirectories and files back.</p>
|
||||
</div></div>
|
||||
@ -398,8 +398,8 @@ tmpfs tmpfs 104M 0 104M 0% /run/user/0
|
||||
<pre class="screen" id="evs_01_0018__evs_01_0033_screen361091453315">[root@ecs-test-0001 ~]# blkid /dev/vdb1
|
||||
/dev/vdb1: UUID="0b3040e2-1367-4abb-841d-ddb0b92693df" TYPE="ext4"</pre>
|
||||
<p id="evs_01_0018__evs_01_0033_p275684701890">The UUID of the <span class="parmname" id="evs_01_0018__evs_01_0033_parmname860990818858"><b>/dev/vdb1</b></span> partition is displayed.</p>
|
||||
</p></li><li id="evs_01_0018__evs_01_0033_li199421823183318"><span>Run the following command to open the <strong>fstab</strong> file using the vi editor:</span><p><p id="evs_01_0018__evs_01_0033_p9610114153320"><strong id="evs_01_0018__evs_01_0033_b1361031419337">vi /etc/fstab</strong></p>
|
||||
</p></li><li id="evs_01_0018__evs_01_0033_li941511389331"><span>Press <strong>i</strong> to enter the editing mode.</span></li><li id="evs_01_0018__evs_01_0033_li8415123893310"><span>Move the cursor to the end of the file and press <strong id="evs_01_0018__evs_01_0033_b1084837140102256">Enter</strong>. Then, add the following information:</span><p><pre class="screen" id="evs_01_0018__evs_01_0033_screen8133145031318">UUID=0b3040e2-1367-4abb-841d-ddb0b92693df /mnt/sdc ext4 defaults 0 2</pre>
|
||||
</p></li><li id="evs_01_0018__evs_01_0033_li199421823183318"><span>Run the following command to open the <strong id="evs_01_0018__evs_01_0033_b972210581107">fstab</strong> file using the vi editor:</span><p><p id="evs_01_0018__evs_01_0033_p9610114153320"><strong id="evs_01_0018__evs_01_0033_b1361031419337">vi /etc/fstab</strong></p>
|
||||
</p></li><li id="evs_01_0018__evs_01_0033_li941511389331"><span>Press <strong id="evs_01_0018__evs_01_0033_b68180161176">i</strong> to enter editing mode.</span></li><li id="evs_01_0018__evs_01_0033_li8415123893310"><span>Move the cursor to the end of the file and press <strong id="evs_01_0018__evs_01_0033_b1084837140102256">Enter</strong>. Then, add the following information:</span><p><pre class="screen" id="evs_01_0018__evs_01_0033_screen8133145031318">UUID=0b3040e2-1367-4abb-841d-ddb0b92693df /mnt/sdc ext4 defaults 0 2</pre>
|
||||
</p></li><li id="evs_01_0018__evs_01_0033_li841512388338"><span>Press <strong id="evs_01_0018__evs_01_0033_b8348192418548">Esc</strong>, enter <strong id="evs_01_0018__evs_01_0033_b15351152418546">:wq</strong>, and press <strong id="evs_01_0018__evs_01_0033_b7353142416544">Enter</strong>.</span><p><p id="evs_01_0018__evs_01_0033_p1141543813310">The system saves the configurations and exits the vi editor.</p>
|
||||
</p></li><li id="evs_01_0018__evs_01_0033_en-us_topic_0142861223_li17720613102410"><span>Perform the following operations to verify the automatic mounting function:</span><p><ol type="a" id="evs_01_0018__evs_01_0033_en-us_topic_0142861223_ol199891910256"><li id="evs_01_0018__evs_01_0033_en-us_topic_0142861223_li1620791415268">Run the following command to unmount the partition:<p id="evs_01_0018__evs_01_0033_en-us_topic_0142861223_p18208131462618"><a name="evs_01_0018__evs_01_0033_en-us_topic_0142861223_li1620791415268"></a><a name="evs_01_0033_en-us_topic_0142861223_li1620791415268"></a><strong id="evs_01_0018__evs_01_0033_b1708526520162011">umount</strong> <em id="evs_01_0018__evs_01_0033_i1458842329162011">Disk partition</em></p>
|
||||
<p id="evs_01_0018__evs_01_0033_en-us_topic_0142861223_p621161413262">In this example, run the following command:</p>
|
||||
@ -408,7 +408,7 @@ tmpfs tmpfs 104M 0 104M 0% /run/user/0
|
||||
</li><li id="evs_01_0018__evs_01_0033_en-us_topic_0142861223_li9280203710269">Run the following command to query the file system mounting information:<p id="evs_01_0018__evs_01_0033_en-us_topic_0142861223_p3282133715264"><a name="evs_01_0018__evs_01_0033_en-us_topic_0142861223_li9280203710269"></a><a name="evs_01_0033_en-us_topic_0142861223_li9280203710269"></a><strong id="evs_01_0018__evs_01_0033_b1187012852919">mount</strong> <strong id="evs_01_0018__evs_01_0033_b17601123382916">|</strong> <strong id="evs_01_0018__evs_01_0033_b1070716324521">grep</strong> <em id="evs_01_0018__evs_01_0033_en-us_topic_0142861223_i2284337112614">Mount point</em></p>
|
||||
<p id="evs_01_0018__evs_01_0033_en-us_topic_0142861223_p3286437112619">In this example, run the following command:</p>
|
||||
<p id="evs_01_0018__evs_01_0033_en-us_topic_0142861223_p18286123782619"><strong id="evs_01_0018__evs_01_0033_b925094342911">mount</strong> <strong id="evs_01_0018__evs_01_0033_b1725119437291">|</strong> <strong id="evs_01_0018__evs_01_0033_b15324154395212">grep</strong> <strong id="evs_01_0018__evs_01_0033_b1831387417">/mnt/sdc</strong></p>
|
||||
<p id="evs_01_0018__evs_01_0033_en-us_topic_0142861223_p429163752616">If information similar to the following is displayed, the automatic mounting function takes effect:</p>
|
||||
<p id="evs_01_0018__evs_01_0033_en-us_topic_0142861223_p429163752616">If information similar to the following is displayed, automatic mounting has been configured:</p>
|
||||
<pre class="screen" id="evs_01_0018__evs_01_0033_en-us_topic_0142861223_screen429312370265">root@ecs-test-0001 ~]# mount | grep /mnt/sdc
|
||||
/dev/vdb1 on /mnt/sdc type ext4 (rw,relatime,data=ordered)</pre>
|
||||
</li></ol>
|
||||
|
@ -3,7 +3,7 @@
|
||||
<h1 class="topictitle1">Searching Disks by Tags</h1>
|
||||
<div id="body1507810015342"><div class="section" id="evs_01_0019__section35485408221444"><h4 class="sectiontitle">Scenarios</h4><p id="evs_01_0019__p49142995222032">Tags can be used to categorize EVS disks, and users can quickly search for their desired EVS disks by tags. This section is used to guide users to search for EVS disk by existing tags.</p>
|
||||
</div>
|
||||
<div class="section" id="evs_01_0019__section40605822221452"><h4 class="sectiontitle">Procedure</h4><ol id="evs_01_0019__ol1977955163311"><li id="evs_01_0019__li2097716553331"><span>Log in to the management console.</span></li><li id="evs_01_0019__li2935870315121"><span>Click <span><img id="evs_01_0019__en-us_topic_0021738346_image052111582392" src="en-us_image_0237893718.png"></span> in the upper left corner and select the desired region and project.</span></li><li id="evs_01_0019__li3843952015053"><span>Under <strong>Storage</strong>, click <strong>Elastic Volume Service</strong>.</span><p><p id="evs_01_0019__p16002076152423">The disk list page is displayed.</p>
|
||||
<div class="section" id="evs_01_0019__section40605822221452"><h4 class="sectiontitle">Procedure</h4><ol id="evs_01_0019__ol1977955163311"><li id="evs_01_0019__li5884586202528"><span>Log in to the management console.</span></li><li id="evs_01_0019__li2935870315121"><span>Click <span><img id="evs_01_0019__en-us_topic_0021738346_image052111582392" src="en-us_image_0237893718.png"></span> in the upper left corner and select the desired region and project.</span></li><li id="evs_01_0019__li3843952015053"><span>Under <strong>Storage</strong>, click <strong>Elastic Volume Service</strong>.</span><p><p id="evs_01_0019__p16002076152423">The disk list page is displayed.</p>
|
||||
</p></li><li id="evs_01_0019__li7585973201558"><span>In the upper area of the disk list, click <strong id="evs_01_0019__b842352706205612">Search by Tag</strong>.</span><p><p id="evs_01_0019__p63208682161856">The <strong id="evs_01_0019__b977397516153144">Search by Tag</strong> page is displayed.</p>
|
||||
</p></li><li id="evs_01_0019__li1223515433711"><span>Enter or select an existing tag in the text box under <strong id="evs_01_0019__b842352706114657">Search by Tag</strong>.</span></li><li id="evs_01_0019__li35882119162654"><span>(Optional) If disks containing multiple tags need to be queried, click <span><img id="evs_01_0019__image76941156175611" src="en-us_image_0238263232.png"></span> to add tags.</span><p><p id="evs_01_0019__p47612313203717">A maximum of 10 tags can be added at a time.</p>
|
||||
<p id="evs_01_0019__p46265705202925">For the added tags, you can delete them individually or click <strong id="evs_01_0019__b84235270620587">Reset</strong> to clear all of them.</p>
|
||||
|
@ -1,12 +1,12 @@
|
||||
<a name="evs_01_0021"></a><a name="evs_01_0021"></a>
|
||||
|
||||
<h1 class="topictitle1">EVS Backup</h1>
|
||||
<div id="body1508814595022"><div class="section" id="evs_01_0021__section33621696191528"><h4 class="sectiontitle">What Is EVS Backup?</h4><p id="evs_01_0021__p17264112213396">Cloud Disk Backup provided by Cloud Backup and Recovery (CBR) allows you to create backups for your EVS disks while <span id="evs_01_0021__text4264722173917">server</span>s are running. If data loss or damage occurred due to virus invasions, misoperations, or software and hardware faults, you can use backups to restore data, guaranteeing your data integrity and security.</p>
|
||||
<div id="body1508814595022"><div class="section" id="evs_01_0021__section33621696191528"><h4 class="sectiontitle">What Is EVS Backup?</h4><p id="evs_01_0021__p17264112213396">Cloud Disk Backup provided by Cloud Backup and Recovery (CBR) allows you to create backups for your EVS disks while <span id="evs_01_0021__text4264722173917">server</span>s are running. If data loss or damage occurred due to virus invasions, accidental deletions, or software/hardware faults, you can use backups to restore data, guaranteeing your data integrity and security.</p>
|
||||
<p id="evs_01_0021__p2990185943811">For more information, see the <em id="evs_01_0021__i842352697115514">Cloud Backup and Recovery User Guide</em>.</p>
|
||||
</div>
|
||||
<div class="section" id="evs_01_0021__section8885956105220"><h4 class="sectiontitle">Application Scenarios</h4><p id="evs_01_0021__p5353643721277">Create and apply backup policies to schedule periodic backups for your EVS disks. You can use the backup data to create new EVS disks or restore to source disks.</p>
|
||||
</div>
|
||||
<div class="section" id="evs_01_0021__section27269138163743"><h4 class="sectiontitle">Usage Instructions</h4><p id="evs_01_0021__p60921580163752">For how to back up EVS disks, see <a href="evs_01_0110.html">Managing EVS Backup</a> or the <em id="evs_01_0021__i3612121374217">Cloud Backup and Recovery User Guide</em>.</p>
|
||||
<div class="section" id="evs_01_0021__section27269138163743"><h4 class="sectiontitle">Usage Instructions</h4><p id="evs_01_0021__p60921580163752">For how to back up EVS disks, see <a href="evs_01_0110.html">Managing EVS Backups</a> or the <em id="evs_01_0021__i3612121374217">Cloud Backup and Recovery User Guide</em>.</p>
|
||||
</div>
|
||||
</div>
|
||||
<div>
|
||||
|
@ -6,7 +6,7 @@
|
||||
<div class="note" id="evs_01_0024__note98481557151510"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="evs_01_0024__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_0024__section5471394711362"><h4 class="sectiontitle">Procedure</h4><ol id="evs_01_0024__ol4466279511369"><li id="evs_01_0024__li47054889165924"><span>Log in to the management console.</span></li><li id="evs_01_0024__li20840824165924"><span>Click <span><img id="evs_01_0024__en-us_topic_0021738346_image052111582392" src="en-us_image_0237893718.png"></span> in the upper left corner and select the desired region and project.</span></li><li id="evs_01_0024__li10385193165924"><span>Under <strong id="evs_01_0024__b51052945511327">Computing</strong>, click <strong id="evs_01_0024__b61953317211327">Elastic Cloud Server</strong>.</span><p><p id="evs_01_0024__p26357877165924">The <span class="wintitle" id="evs_01_0024__wintitle35894306165924"><b>Elastic Cloud Server</b></span> page is displayed.</p>
|
||||
<div class="section" id="evs_01_0024__section5471394711362"><h4 class="sectiontitle">Procedure</h4><ol id="evs_01_0024__ol4466279511369"><li id="evs_01_0024__li5884586202528"><span>Log in to the management console.</span></li><li id="evs_01_0024__li2935870315121"><span>Click <span><img id="evs_01_0024__en-us_topic_0021738346_image052111582392" src="en-us_image_0237893718.png"></span> in the upper left corner and select the desired region and project.</span></li><li id="evs_01_0024__li10385193165924"><span>Under <strong id="evs_01_0024__b51052945511327">Computing</strong>, click <strong id="evs_01_0024__b61953317211327">Elastic Cloud Server</strong>.</span><p><p id="evs_01_0024__p26357877165924">The <span class="wintitle" id="evs_01_0024__wintitle35894306165924"><b>Elastic Cloud Server</b></span> page is displayed.</p>
|
||||
</p></li><li id="evs_01_0024__li23677833165924"><span>Click the name of the production ECS.</span><p><p id="evs_01_0024__p11773906165924">The ECS details page is displayed.</p>
|
||||
</p></li><li id="evs_01_0024__li3726148311399"><span>Take note of the production ECS information, including the ECS specifications, details of the EVS disks attached to the ECS, private IP address, and security group, as shown in <a href="#evs_01_0024__table8510771171728">Table 1</a>.</span><p><div class="note" id="evs_01_0024__note30319393143536"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="evs_01_0024__p4439085143536">The listed parameter values are for reference only.</p>
|
||||
</div></div>
|
||||
|
@ -9,7 +9,7 @@
|
||||
<div class="section" id="evs_01_0026__section3065738815149"><h4 class="sectiontitle">Prerequisites</h4><p id="evs_01_0026__p39821965151337">You have obtained the VPC, subnet, MAC address, and virtual IP address of the production server. For details, see <a href="evs_01_0025.html">Collecting ECS Information (Deprecated)</a>.</p>
|
||||
</div>
|
||||
<div class="section" id="evs_01_0026__section61097236151453"><h4 class="sectiontitle">Procedure</h4><p id="evs_01_0026__p49929083151453">The following operations are for reference only. For details, see <strong id="evs_01_0026__b842352706211210">Assigning a Virtual IP Address</strong> in the <em id="evs_01_0026__i842352697185425">Virtual Private Cloud User Guide</em>.</p>
|
||||
<ol id="evs_01_0026__ol46708566151453"><li id="evs_01_0026__li17723914151453"><span>Log in to the management console.</span></li><li id="evs_01_0026__li25297505151453"><span>Click <span><img id="evs_01_0026__en-us_topic_0021738346_image052111582392" src="en-us_image_0237893718.png"></span> in the upper left corner and select the desired region and project.</span></li><li id="evs_01_0026__li35832000151453"><span>Under <strong id="evs_01_0026__b51052945511327">Computing</strong>, click <strong id="evs_01_0026__b61953317211327">Elastic Cloud Server</strong>.</span><p><p id="evs_01_0026__p54052547151453">The <span class="wintitle" id="evs_01_0026__wintitle16710876151453"><b>Elastic Cloud Server</b></span> page is displayed.</p>
|
||||
<ol id="evs_01_0026__ol46708566151453"><li id="evs_01_0026__li5884586202528"><span>Log in to the management console.</span></li><li id="evs_01_0026__li2935870315121"><span>Click <span><img id="evs_01_0026__en-us_topic_0021738346_image052111582392" src="en-us_image_0237893718.png"></span> in the upper left corner and select the desired region and project.</span></li><li id="evs_01_0026__li35832000151453"><span>Under <strong id="evs_01_0026__b51052945511327">Computing</strong>, click <strong id="evs_01_0026__b61953317211327">Elastic Cloud Server</strong>.</span><p><p id="evs_01_0026__p54052547151453">The <span class="wintitle" id="evs_01_0026__wintitle16710876151453"><b>Elastic Cloud Server</b></span> page is displayed.</p>
|
||||
</p></li><li id="evs_01_0026__li16180156151453"><span>In the ECS list, locate the production ECS and click the ECS name.</span><p><p id="evs_01_0026__p327822510164">The ECS details page is displayed.</p>
|
||||
</p></li><li id="evs_01_0026__li21850568101640"><span>On the ECS details page, locate the VPC and click the VPC name.</span><p><p id="evs_01_0026__p11178069101641">The <strong id="evs_01_0026__b84235270619547">Virtual Private Cloud</strong> page is displayed.</p>
|
||||
</p></li><li id="evs_01_0026__li617997410171"><span>In the VPC list, locate the VPC of the production ECS and click the VPC name.</span><p><p id="evs_01_0026__p13029411101818">The VPC details page is displayed.</p>
|
||||
@ -19,8 +19,8 @@
|
||||
</li><li id="evs_01_0026__li3919407110419">If no, perform the following operations:<ol type="a" id="evs_01_0026__ol66869471104449"><li id="evs_01_0026__li14886481104449">Click <strong id="evs_01_0026__b842352706155825">Assign Virtual IP Address</strong>.<p id="evs_01_0026__p2259461510455">After the application succeeds, you can view the virtual IP address in the virtual IP address list.</p>
|
||||
<div class="note" id="evs_01_0026__note198012251417"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="evs_01_0026__p1881152261417">When assigning the virtual IP address, you can select the <strong id="evs_01_0026__b842352706211710">Automatic</strong> or <strong id="evs_01_0026__b842352706211714">Manual</strong> mode based on your service requirements.</p>
|
||||
</div></div>
|
||||
</li><li id="evs_01_0026__li30619422104542">Locate the row that contains the virtual IP address and click <strong id="evs_01_0026__b50141567">Bind to Server</strong> in the <strong id="evs_01_0026__b143045398">Operation</strong> column. On the displayed page, bind the virtual IP address to the NIC of the production server.<p id="evs_01_0026__p450514200">After the virtual IP address is bound with the production server, the subnet details page is displayed.</p>
|
||||
</li><li id="evs_01_0026__li18160194104553">Locate the row that contains the virtual IP address and click <strong id="evs_01_0026__b1673794884">Bind to Server</strong> in the <strong id="evs_01_0026__b1484895153">Operation</strong> column. On the displayed page, bind the virtual IP address to the NIC of the DR server.<p id="evs_01_0026__p755911212016">After the virtual IP address is bound with the DR server, the subnet details page is displayed.</p>
|
||||
</li><li id="evs_01_0026__li30619422104542">Locate the row that contains the virtual IP address and click <strong id="evs_01_0026__b1723130978">Bind to Server</strong> in the <strong id="evs_01_0026__b1845664300">Operation</strong> column. On the displayed page, bind the virtual IP address to the NIC of the production server.<p id="evs_01_0026__p450514200">After the virtual IP address is bound with the production server, the subnet details page is displayed.</p>
|
||||
</li><li id="evs_01_0026__li18160194104553">Locate the row that contains the virtual IP address and click <strong id="evs_01_0026__b1662403559">Bind to Server</strong> in the <strong id="evs_01_0026__b76251430">Operation</strong> column. On the displayed page, bind the virtual IP address to the NIC of the DR server.<p id="evs_01_0026__p755911212016">After the virtual IP address is bound with the DR server, the subnet details page is displayed.</p>
|
||||
</li></ol>
|
||||
</li></ul>
|
||||
</p></li><li id="evs_01_0026__li894545421812"><a name="evs_01_0026__li894545421812"></a><a name="li894545421812"></a><span>On the subnet details page, take note of the subnet and the IP address of the server's NIC where the virtual IP address has been bound.</span><p><div class="p" id="evs_01_0026__p17687161810222">An example is provided as follows:<ul id="evs_01_0026__ul2667031192217"><li id="evs_01_0026__li16672031192214">Subnet: 192.168.0.0/24</li><li id="evs_01_0026__li1922121132316">Bound server (NIC): ecs-001 (192.168.0.176)</li></ul>
|
||||
@ -32,7 +32,7 @@
|
||||
<p id="evs_01_0026__p19227728124216">You can obtain the NIC name using the NIC IP address recorded in <a href="#evs_01_0026__li894545421812">9</a>. In this example, the NIC name is <strong id="evs_01_0026__b842352706212644">eth0</strong>.</p>
|
||||
</li><li id="evs_01_0026__li1222792815429">Run the following command to switch to the directory containing NIC configuration files:<p id="evs_01_0026__p1322782814215"><a name="evs_01_0026__li1222792815429"></a><a name="li1222792815429"></a><strong id="evs_01_0026__b18227132813424">cd /etc/sysconfig/network-scripts</strong></p>
|
||||
</li><li id="evs_01_0026__li1759515204363">Run the following command to copy NIC configuration file <strong id="evs_01_0026__b865046205153159">eth0</strong> and change its name to <strong id="evs_01_0026__b842352706153026">eth0:1</strong>:<p id="evs_01_0026__p35961202364"><strong id="evs_01_0026__b1408203419535">cp eth0 eth0:1</strong></p>
|
||||
</li><li id="evs_01_0026__li12253131618547">Perform the following operations to modify the configuration parameters of <strong id="evs_01_0026__b842352706153357">eth0:1</strong> using the vi editor:<ol class="substepthirdol" id="evs_01_0026__ol4254116155417"><li id="evs_01_0026__li17255516175417">Run the following command to open the <strong id="evs_01_0026__b1635410856">ifcfg-eth0:1</strong> file:<p id="evs_01_0026__p1825911616548"><strong id="evs_01_0026__b325951685410">vi ifcfg-<strong id="evs_01_0026__b1834720205616">eth0:1</strong></strong></p>
|
||||
</li><li id="evs_01_0026__li12253131618547">Perform the following operations to modify the configuration parameters of <strong id="evs_01_0026__b842352706153357">eth0:1</strong> using the vi editor:<ol class="substepthirdol" id="evs_01_0026__ol4254116155417"><li id="evs_01_0026__li17255516175417">Run the following command to open the <strong id="evs_01_0026__b1018086604">ifcfg-eth0:1</strong> file:<p id="evs_01_0026__p1825911616548"><strong id="evs_01_0026__b325951685410">vi ifcfg-<strong id="evs_01_0026__b1834720205616">eth0:1</strong></strong></p>
|
||||
</li><li id="evs_01_0026__li125991618542">Press <strong>i</strong> to enter editing mode.</li><li id="evs_01_0026__li11261131665411">Configure the parameters according to the following example:<pre class="screen" id="evs_01_0026__screen6261916145412">BOOTPROTO=static
|
||||
DEVICE=eth0:1
|
||||
NAME=eth0:1
|
||||
@ -41,10 +41,10 @@ TYPE=Ethernet
|
||||
USERCTL=no
|
||||
IPADDR=192.168.0.176
|
||||
NETMASK=255.255.255.0</pre>
|
||||
<div class="p" id="evs_01_0026__p126641619541">Configuration descriptions of the <strong id="evs_01_0026__b210391843">NAME</strong>, <strong id="evs_01_0026__b475609930">IPADDR</strong>, and <strong id="evs_01_0026__b92358401">NETMASK</strong> fields:<ul id="evs_01_0026__ul8268516165420"><li id="evs_01_0026__li182688161543"><strong id="evs_01_0026__b347551522">NAME</strong>: Specifies the NIC name recorded in <a href="#evs_01_0026__li1422712286426">10.b</a>.</li><li id="evs_01_0026__li122691416175410"><strong id="evs_01_0026__b885620431">IPADDR</strong>: Specifies the NIC IP address recorded in <a href="#evs_01_0026__li894545421812">9</a>.</li><li id="evs_01_0026__li12271101610545"><strong id="evs_01_0026__b892210762">NETMASK</strong>: Specifies the subnet recorded in <a href="#evs_01_0026__li894545421812">9</a>.<p id="evs_01_0026__p627511695410">In this example, the subnet mask has 24 bits. Therefore, enter <strong id="evs_01_0026__b979377531">255.255.255.0</strong> for <strong id="evs_01_0026__b1864380269">NETMASK</strong>.</p>
|
||||
<div class="p" id="evs_01_0026__p126641619541">Configuration descriptions of the <strong id="evs_01_0026__b1117529109">NAME</strong>, <strong id="evs_01_0026__b1822649024">IPADDR</strong>, and <strong id="evs_01_0026__b198325186">NETMASK</strong> fields:<ul id="evs_01_0026__ul8268516165420"><li id="evs_01_0026__li182688161543"><strong id="evs_01_0026__b1328530549">NAME</strong>: Specifies the NIC name recorded in <a href="#evs_01_0026__li1422712286426">10.b</a>.</li><li id="evs_01_0026__li122691416175410"><strong id="evs_01_0026__b1147352912">IPADDR</strong>: Specifies the NIC IP address recorded in <a href="#evs_01_0026__li894545421812">9</a>.</li><li id="evs_01_0026__li12271101610545"><strong id="evs_01_0026__b1804424892">NETMASK</strong>: Specifies the subnet recorded in <a href="#evs_01_0026__li894545421812">9</a>.<p id="evs_01_0026__p627511695410">In this example, the subnet mask has 24 bits. Therefore, enter <strong id="evs_01_0026__b661524986">255.255.255.0</strong> for <strong id="evs_01_0026__b875100011">NETMASK</strong>.</p>
|
||||
</li></ul>
|
||||
</div>
|
||||
</li><li id="evs_01_0026__li18275416155412">Press <strong>Esc</strong>, enter <strong id="evs_01_0026__b321061074">:wq</strong>, and press <strong>Enter</strong>.<p id="evs_01_0026__p19277101675410">The system saves the configurations and exits the vi editor.</p>
|
||||
</li><li id="evs_01_0026__li18275416155412">Press <strong>Esc</strong>, enter <strong id="evs_01_0026__b2146780154">:wq</strong>, and press <strong>Enter</strong>.<p id="evs_01_0026__p19277101675410">The system saves the configurations and exits the vi editor.</p>
|
||||
</li></ol>
|
||||
</li><li id="evs_01_0026__li1769912298374">Run the following command to delete unnecessary NIC files from the <strong id="evs_01_0026__b842352706213320">/etc/sysconfig/network-scripts</strong> directory:<p id="evs_01_0026__p13783144014383"><strong id="evs_01_0026__b842352706213337">rm</strong> <em id="evs_01_0026__i1157162078213346">Name of the unnecessary NIC file</em></p>
|
||||
<p id="evs_01_0026__p11256413134018">For example, run the following command:</p>
|
||||
@ -52,18 +52,18 @@ NETMASK=255.255.255.0</pre>
|
||||
<div class="note" id="evs_01_0026__note7203172517406"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="evs_01_0026__p11935165466">Before deleting the unnecessary NIC files, you are advised to back up the files.</p>
|
||||
<p id="evs_01_0026__p320482574011">If multiple unnecessary NIC files exist, delete them individually. Ensure that the <strong id="evs_01_0026__b842352706213536">/etc/sysconfig/network-scripts</strong> directory contains only the in-use NIC file.</p>
|
||||
</div></div>
|
||||
</li><li id="evs_01_0026__li1884218317114">Run the following command to check whether the <strong id="evs_01_0026__b842352706153458">70-persistent-ipoib.rules</strong> file exists in the <strong id="evs_01_0026__b84235270615359">/etc/udev/rules.d/</strong> directory:<div class="p" id="evs_01_0026__p1447732054212"><strong id="evs_01_0026__b17068764414">ls /etc/udev/rules.d/70-persistent-ipoib.rules</strong><ul id="evs_01_0026__ul8449119124211"><li id="evs_01_0026__li16449119134210">If yes, use the vi editor to configure the NIC information, including the NIC name and MAC address, for production and DR servers.<ol class="substepthirdol" id="evs_01_0026__ol17365417125016"><li id="evs_01_0026__li10365191795010">Run the following command to open the <strong id="evs_01_0026__b1921095076">70-persistent-ipoib.rules</strong> file:<p id="evs_01_0026__p13179134495110"><strong id="evs_01_0026__b9375748195111">vi /etc/udev/rules.d/70-persistent-ipoib.rules</strong></p>
|
||||
</li><li id="evs_01_0026__li1884218317114">Run the following command to check whether the <strong id="evs_01_0026__b842352706153458">70-persistent-ipoib.rules</strong> file exists in the <strong id="evs_01_0026__b84235270615359">/etc/udev/rules.d/</strong> directory:<div class="p" id="evs_01_0026__p1447732054212"><strong id="evs_01_0026__b17068764414">ls /etc/udev/rules.d/70-persistent-ipoib.rules</strong><ul id="evs_01_0026__ul8449119124211"><li id="evs_01_0026__li16449119134210">If yes, use the vi editor to configure the NIC information, including the NIC name and MAC address, for production and DR servers.<ol class="substepthirdol" id="evs_01_0026__ol17365417125016"><li id="evs_01_0026__li10365191795010">Run the following command to open the <strong id="evs_01_0026__b1801071536">70-persistent-ipoib.rules</strong> file:<p id="evs_01_0026__p13179134495110"><strong id="evs_01_0026__b9375748195111">vi /etc/udev/rules.d/70-persistent-ipoib.rules</strong></p>
|
||||
</li><li id="evs_01_0026__li7104115320518">Press <strong>i</strong> to enter editing mode.</li><li id="evs_01_0026__li134511318185216">Add NIC information for the DR server based on that of the production server. For details, see the following example:<pre class="screen" id="evs_01_0026__screen645271811526">ACTION=="add", SUBSYSTEM=="net", DRIVERS=="?*", ATTR{type}=="32", ATTR{address}=={mac}, NAME="eth0"
|
||||
ACTION=="add", SUBSYSTEM=="net", DRIVERS=="?*", ATTR{type}=="32", ATTR{address}=={mac}, NAME="eth1"
|
||||
|
||||
ACTION=="add", SUBSYSTEM=="net", DRIVERS=="?*", ATTR{type}=="32", ATTR{address}=={mac}, NAME="eth0"
|
||||
ACTION=="add", SUBSYSTEM=="net", DRIVERS=="?*", ATTR{type}=="32", ATTR{address}=={mac}, NAME="eth1"</pre>
|
||||
<p id="evs_01_0026__p19460151820524">Configuration descriptions of the <strong id="evs_01_0026__b907898383">ATTR{address}</strong> and <strong id="evs_01_0026__b512561589">NAME</strong> fields:</p>
|
||||
<ul id="evs_01_0026__ul182512052145813"><li id="evs_01_0026__li6251952205817"><strong id="evs_01_0026__b842352706154037">ATTR{address}</strong>: specifies the MAC address of server's NIC.</li><li id="evs_01_0026__li18250145218588"><strong id="evs_01_0026__b1401973926">NAME</strong>: Specifies the NIC name recorded in <a href="#evs_01_0026__li1422712286426">10.b</a>.<div class="note" id="evs_01_0026__note155184424711"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="evs_01_0026__p19520542078">a. Ensure that the <strong id="evs_01_0026__b842352706154215">NAME</strong> (NIC name) values of the production and DR servers are consistent. The <strong id="evs_01_0026__b84235270615441">ATTR{address}</strong> (MAC address) value can be obtained in <a href="evs_01_0025.html">Collecting ECS Information (Deprecated)</a>.</p>
|
||||
<p id="evs_01_0026__p19460151820524">Configuration descriptions of the <strong id="evs_01_0026__b1577579411">ATTR{address}</strong> and <strong id="evs_01_0026__b492874808">NAME</strong> fields:</p>
|
||||
<ul id="evs_01_0026__ul182512052145813"><li id="evs_01_0026__li6251952205817"><strong id="evs_01_0026__b842352706154037">ATTR{address}</strong>: specifies the MAC address of server's NIC.</li><li id="evs_01_0026__li18250145218588"><strong id="evs_01_0026__b423473470">NAME</strong>: Specifies the NIC name recorded in <a href="#evs_01_0026__li1422712286426">10.b</a>.<div class="note" id="evs_01_0026__note155184424711"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="evs_01_0026__p19520542078">a. Ensure that the <strong id="evs_01_0026__b842352706154215">NAME</strong> (NIC name) values of the production and DR servers are consistent. The <strong id="evs_01_0026__b84235270615441">ATTR{address}</strong> (MAC address) value can be obtained in <a href="evs_01_0025.html">Collecting ECS Information (Deprecated)</a>.</p>
|
||||
<p id="evs_01_0026__p144632214530">b. Replace <strong id="evs_01_0026__b596910411519">{mac}</strong> with the MAC address during operation.</p>
|
||||
</div></div>
|
||||
</li></ul>
|
||||
</li><li id="evs_01_0026__li3967344267">Press <strong>Esc</strong>, enter <strong id="evs_01_0026__b2141819220">:wq</strong>, and press <strong>Enter</strong>.<p id="evs_01_0026__p49691644563">The system saves the configurations and exits the vi editor.</p>
|
||||
</li><li id="evs_01_0026__li3967344267">Press <strong>Esc</strong>, enter <strong id="evs_01_0026__b1415020526">:wq</strong>, and press <strong>Enter</strong>.<p id="evs_01_0026__p49691644563">The system saves the configurations and exits the vi editor.</p>
|
||||
</li></ol>
|
||||
</li><li id="evs_01_0026__li1144911198420">If no, go to <a href="#evs_01_0026__li145676502016">10.h</a>.</li></ul>
|
||||
</div>
|
||||
|
@ -2,16 +2,16 @@
|
||||
|
||||
<h1 class="topictitle1">Initializing a Linux Data Disk (fdisk)</h1>
|
||||
<div id="body1436260274365"><div class="section" id="evs_01_0033__section31580524185332"><h4 class="sectiontitle">Scenarios</h4><p id="evs_01_0033__p3566739210424">This section uses CentOS 7.4 64bit to describe how to initialize a data disk attached to <span id="evs_01_0033__text1895391527145159">a server</span> running Linux and use fdisk to partition the data disk.</p>
|
||||
<p id="evs_01_0033__p166075410209">The maximum disk capacity supported by MBR is 2 TB, and that supported by GPT is 18 EB. Therefore, use the GPT partition style if your disk capacity is larger than 2 TB. In Linux, if you choose to use the GPT partition style, the fdisk partitioning tool cannot be used. Use the parted partitioning tool instead. For details about disk partition styles, see <a href="evs_01_0038.html">Introduction to Data Disk Initialization Scenarios and Partition Styles</a>.</p>
|
||||
<p id="evs_01_0033__p54551132112014">The maximum partition size that MBR supports is 2 TiB and that GPT supports is 18 EiB. If the disk size you need to partition is greater than 2 TiB, partition the disk using GPT.</p>
|
||||
<p id="evs_01_0033__p12685942161314">The fdisk partitioning tool is suitable only for MBR partitions, and the parted partitioning tool is suitable for both MBR and GPT partitions. For more information, see <a href="evs_01_0038.html">Introduction to Data Disk Initialization Scenarios and Partition Styles</a>.</p>
|
||||
<p id="evs_01_0033__p4699546795037">The method for initializing a disk varies depending on the OS running on the <span id="evs_01_0033__text849922751145419">server</span>. This document is used for reference only. For the detailed operations and differences, see the product documents of the corresponding OS.</p>
|
||||
</div>
|
||||
<div class="section" id="evs_01_0033__section117091356845"><h4 class="sectiontitle">Prerequisites</h4><ul id="evs_01_0033__evs_01_0108_ul28913191171813"><li id="evs_01_0033__evs_01_0108_li20771164724419">A data disk has been attached to <span id="evs_01_0033__evs_01_0108_text184241938124418">a server</span> and has not been initialized.</li><li id="evs_01_0033__evs_01_0108_li36962755115557">You have logged in to the <span id="evs_01_0033__evs_01_0108_text25940422717248">server</span>.<ul id="evs_01_0033__evs_01_0108_ul6229092211568"><li id="evs_01_0033__evs_01_0108_li197989548398">For how to log in to an ECS, see the <em id="evs_01_0033__evs_01_0108_i157642033171941">Elastic Cloud Server User Guide</em>.</li><li id="evs_01_0033__evs_01_0108_li7220898115452">For how to log in to a BMS, see the <em id="evs_01_0033__evs_01_0108_i842352697172014">Bare Metal Server User Guide</em>.</li></ul>
|
||||
</li></ul>
|
||||
</div>
|
||||
<div class="section" id="evs_01_0033__section36039836195351"><h4 class="sectiontitle">Creating and Mounting a Partition</h4><p id="evs_01_0033__p4530289419544">The following example shows you how a new primary partition can be created on a new data disk that has been attached to <span id="evs_01_0033__text2422957163556">a server</span>. The primary partition will be created using fdisk, and MBR is the default partition style. Furthermore, the partition will be formatted using the ext4 file system, mounted on <strong id="evs_01_0033__b84235270611226">/mnt/sdc</strong>, and configured with automatic mounting at system start.</p>
|
||||
<div class="section" id="evs_01_0033__section36039836195351"><h4 class="sectiontitle">Creating and Mounting a Partition</h4><p id="evs_01_0033__p4530289419544">The following example shows you how a new primary partition can be created on a new data disk that has been attached to <span id="evs_01_0033__text2422957163556">a server</span>. The primary partition will be created using fdisk, and MBR will be used. Furthermore, the partition will be formatted using the ext4 file system, mounted on <strong id="evs_01_0033__b84235270611226">/mnt/sdc</strong>, and configured with automatic mounting at system start.</p>
|
||||
</div>
|
||||
<ol id="evs_01_0033__ol1329192162914"><li id="evs_01_0033__li02952152918"><span>Run the following command to query information about the new data disk:</span><p><p id="evs_01_0033__p6233165017299"><strong id="evs_01_0033__b423375018297">fdisk -l</strong></p>
|
||||
<div class="p" id="evs_01_0033__p1861313818316">Information similar to the following is displayed:<pre class="screen" id="evs_01_0033__screen4298194012254">[root@ecs-test-0001 ~]# fdisk -l
|
||||
<ol id="evs_01_0033__ol1329192162914"><li id="evs_01_0033__li02952152918"><span><strong id="evs_01_0033__b423375018297">fdisk -l</strong></span><p><div class="p" id="evs_01_0033__p1861313818316">Information similar to the following is displayed:<pre class="screen" id="evs_01_0033__screen4298194012254">[root@ecs-test-0001 ~]# fdisk -l
|
||||
|
||||
Disk /dev/vda: 42.9 GB, 42949672960 bytes, 83886080 sectors
|
||||
Units = sectors of 1 * 512 = 512 bytes
|
||||
@ -43,7 +43,7 @@ Building a new DOS disklabel with disk identifier 0x38717fc1.
|
||||
|
||||
Command (m for help): </pre>
|
||||
</div>
|
||||
</p></li><li id="evs_01_0033__li125780811321"><span>Enter <strong>n</strong> and press <strong>Enter</strong> to create a new partition.</span><p><div class="p" id="evs_01_0033__p29271455221812">Information similar to the following is displayed:<pre class="screen" id="evs_01_0033__screen552432311275">Command (m for help): n
|
||||
</p></li><li id="evs_01_0033__li125780811321"><span>Enter <strong id="evs_01_0033__b14689258161017">n</strong> and press <strong id="evs_01_0033__b11689658161010">Enter</strong> to create a new partition.</span><p><div class="p" id="evs_01_0033__p29271455221812">Information similar to the following is displayed:<pre class="screen" id="evs_01_0033__screen552432311275">Command (m for help): n
|
||||
Partition type:
|
||||
p primary (0 primary, 0 extended, 4 free)
|
||||
e extended</pre>
|
||||
@ -66,8 +66,8 @@ First sector (2048-209715199, default 2048):</pre>
|
||||
Using default value 2048
|
||||
Last sector, +sectors or +size{K,M,G} (2048-209715199, default 209715199):</pre>
|
||||
</div>
|
||||
<p id="evs_01_0033__p4034033118642"><span class="parmname" id="evs_01_0033__parmname888805909"><b>Last sector</b></span> indicates the end sector. The value ranges from <strong id="evs_01_0033__b600136218">2048</strong> to <strong id="evs_01_0033__b1798151514556">209715199</strong>, and the default value is <strong id="evs_01_0033__b951753599">209715199</strong>.</p>
|
||||
</p></li><li id="evs_01_0033__li657968113217"><span>Select the default end sector <strong id="evs_01_0033__b842352706112515">209715199</strong> and press <strong id="evs_01_0033__b785985218">Enter</strong>.</span><p><p id="evs_01_0033__p1675124661216">The system displays the start and end sectors of the partition's available space. You can customize the value within this range or use the default value. The start sector must be smaller than the partition's end sector.</p>
|
||||
<p id="evs_01_0033__p4034033118642"><span class="parmname" id="evs_01_0033__parmname1352932938"><b>Last sector</b></span> indicates the end sector. The value ranges from <strong id="evs_01_0033__b1409079498">2048</strong> to <strong id="evs_01_0033__b1798151514556">209715199</strong>, and the default value is <strong id="evs_01_0033__b67907826">209715199</strong>.</p>
|
||||
</p></li><li id="evs_01_0033__li657968113217"><span>Select the default end sector <strong id="evs_01_0033__b842352706112515">209715199</strong> and press <strong id="evs_01_0033__b909315080">Enter</strong>.</span><p><p id="evs_01_0033__p1675124661216">The system displays the start and end sectors of the partition's available space. You can customize the value within this range or use the default value. The start sector must be smaller than the partition's end sector.</p>
|
||||
<p id="evs_01_0033__p457918818329">Information similar to the following is displayed:</p>
|
||||
<pre class="screen" id="evs_01_0033__screen116541323132915">Last sector, +sectors or +size{K,M,G} (2048-209715199, default 209715199):
|
||||
Using default value 209715199
|
||||
@ -132,6 +132,8 @@ Writing superblocks and filesystem accounting information: done</pre>
|
||||
</p></li><li id="evs_01_0033__li1758111811323"><span>Run the following command to create a mount point:</span><p><p id="evs_01_0033__p1038930410141"><strong id="evs_01_0033__b185866046992856">mkdir</strong> <em id="evs_01_0033__i214308114392856">Mount point</em></p>
|
||||
<p id="evs_01_0033__p6697580910132">In this example, run the following command to create the <strong id="evs_01_0033__b97471244387">/mnt/sdc</strong> mount point:</p>
|
||||
<p id="evs_01_0033__p9581128153219"><strong id="evs_01_0033__b258111873210">mkdir /mnt/sdc</strong></p>
|
||||
<div class="note" id="evs_01_0033__note1653352162717"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="evs_01_0033__p153319214278">The <strong id="evs_01_0033__b1926517325558">/mnt</strong> directory exists on all Linux systems. If the mount point fails to create, it may be that the <strong id="evs_01_0033__b10608636145619">/mnt</strong> directory has been accidentally deleted. Run the <strong id="evs_01_0033__b1583931719296">mkdir -p /mnt/sdc</strong> command to create the mount point.</p>
|
||||
</div></div>
|
||||
</p></li><li id="evs_01_0033__li62473867152927"><span>Run the following command to mount the new partition on the created mount point:</span><p><p id="evs_01_0033__p1011938710557"><strong id="evs_01_0033__b608287909162747">mount</strong> <em id="evs_01_0033__i2056323561162747">Disk partition</em> <em id="evs_01_0033__i1566529680162747">Mount point</em></p>
|
||||
<p id="evs_01_0033__p2550130210557">In this example, run the following command to mount the new partition <strong id="evs_01_0033__b10604235896">/dev/vdb1</strong> on <strong id="evs_01_0033__b175162410917">/mnt/sdc</strong>:</p>
|
||||
<p id="evs_01_0033__p5169551152959"><strong id="evs_01_0033__b18041179153011">mount /dev/vdb1 /mnt/sdc</strong></p>
|
||||
@ -161,8 +163,8 @@ tmpfs tmpfs 398M 0 398M 0% /run/user/0
|
||||
<pre class="screen" id="evs_01_0033__screen361091453315">[root@ecs-test-0001 ~]# blkid /dev/vdb1
|
||||
/dev/vdb1: UUID="0b3040e2-1367-4abb-841d-ddb0b92693df" TYPE="ext4"</pre>
|
||||
<p id="evs_01_0033__p275684701890">The UUID of the <span class="parmname" id="evs_01_0033__parmname860990818858"><b>/dev/vdb1</b></span> partition is displayed.</p>
|
||||
</p></li><li id="evs_01_0033__li199421823183318"><span>Run the following command to open the <strong>fstab</strong> file using the vi editor:</span><p><p id="evs_01_0033__p9610114153320"><strong id="evs_01_0033__b1361031419337">vi /etc/fstab</strong></p>
|
||||
</p></li><li id="evs_01_0033__li941511389331"><span>Press <strong>i</strong> to enter the editing mode.</span></li><li id="evs_01_0033__li8415123893310"><span>Move the cursor to the end of the file and press <strong id="evs_01_0033__b1084837140102256">Enter</strong>. Then, add the following information:</span><p><pre class="screen" id="evs_01_0033__screen8133145031318">UUID=0b3040e2-1367-4abb-841d-ddb0b92693df /mnt/sdc ext4 defaults 0 2</pre>
|
||||
</p></li><li id="evs_01_0033__li199421823183318"><span>Run the following command to open the <strong id="evs_01_0033__b972210581107">fstab</strong> file using the vi editor:</span><p><p id="evs_01_0033__p9610114153320"><strong id="evs_01_0033__b1361031419337">vi /etc/fstab</strong></p>
|
||||
</p></li><li id="evs_01_0033__li941511389331"><span>Press <strong id="evs_01_0033__b68180161176">i</strong> to enter editing mode.</span></li><li id="evs_01_0033__li8415123893310"><span>Move the cursor to the end of the file and press <strong id="evs_01_0033__b1084837140102256">Enter</strong>. Then, add the following information:</span><p><pre class="screen" id="evs_01_0033__screen8133145031318">UUID=0b3040e2-1367-4abb-841d-ddb0b92693df /mnt/sdc ext4 defaults 0 2</pre>
|
||||
</p></li><li id="evs_01_0033__li841512388338"><span>Press <strong id="evs_01_0033__b8348192418548">Esc</strong>, enter <strong id="evs_01_0033__b15351152418546">:wq</strong>, and press <strong id="evs_01_0033__b7353142416544">Enter</strong>.</span><p><p id="evs_01_0033__p1141543813310">The system saves the configurations and exits the vi editor.</p>
|
||||
</p></li><li id="evs_01_0033__en-us_topic_0142861223_li17720613102410"><span>Perform the following operations to verify the automatic mounting function:</span><p><ol type="a" id="evs_01_0033__en-us_topic_0142861223_ol199891910256"><li id="evs_01_0033__en-us_topic_0142861223_li1620791415268">Run the following command to unmount the partition:<p id="evs_01_0033__en-us_topic_0142861223_p18208131462618"><a name="evs_01_0033__en-us_topic_0142861223_li1620791415268"></a><a name="en-us_topic_0142861223_li1620791415268"></a><strong id="evs_01_0033__b1708526520162011">umount</strong> <em id="evs_01_0033__i1458842329162011">Disk partition</em></p>
|
||||
<p id="evs_01_0033__en-us_topic_0142861223_p621161413262">In this example, run the following command:</p>
|
||||
@ -171,7 +173,7 @@ tmpfs tmpfs 398M 0 398M 0% /run/user/0
|
||||
</li><li id="evs_01_0033__en-us_topic_0142861223_li9280203710269">Run the following command to query the file system mounting information:<p id="evs_01_0033__en-us_topic_0142861223_p3282133715264"><a name="evs_01_0033__en-us_topic_0142861223_li9280203710269"></a><a name="en-us_topic_0142861223_li9280203710269"></a><strong id="evs_01_0033__b1187012852919">mount</strong> <strong id="evs_01_0033__b17601123382916">|</strong> <strong id="evs_01_0033__b1070716324521">grep</strong> <em id="evs_01_0033__en-us_topic_0142861223_i2284337112614">Mount point</em></p>
|
||||
<p id="evs_01_0033__en-us_topic_0142861223_p3286437112619">In this example, run the following command:</p>
|
||||
<p id="evs_01_0033__en-us_topic_0142861223_p18286123782619"><strong id="evs_01_0033__b925094342911">mount</strong> <strong id="evs_01_0033__b1725119437291">|</strong> <strong id="evs_01_0033__b15324154395212">grep</strong> <strong id="evs_01_0033__b1831387417">/mnt/sdc</strong></p>
|
||||
<p id="evs_01_0033__en-us_topic_0142861223_p429163752616">If information similar to the following is displayed, the automatic mounting function takes effect:</p>
|
||||
<p id="evs_01_0033__en-us_topic_0142861223_p429163752616">If information similar to the following is displayed, automatic mounting has been configured:</p>
|
||||
<pre class="screen" id="evs_01_0033__en-us_topic_0142861223_screen429312370265">root@ecs-test-0001 ~]# mount | grep /mnt/sdc
|
||||
/dev/vdb1 on /mnt/sdc type ext4 (rw,relatime,data=ordered)</pre>
|
||||
</li></ol>
|
||||
|
@ -2,13 +2,14 @@
|
||||
|
||||
<h1 class="topictitle1">Initializing a Linux Data Disk (parted)</h1>
|
||||
<div id="body1511319979089"><div class="section" id="evs_01_0034__section31580524185332"><h4 class="sectiontitle">Scenarios</h4><p id="evs_01_0034__p4699546795037">This section uses CentOS 7.4 64bit to describe how to initialize a data disk attached to <span id="evs_01_0034__text1146380502125328">a server</span> running Linux and use parted to partition the data disk.</p>
|
||||
<p id="evs_01_0034__p433451952110">The maximum disk capacity supported by MBR is 2 TB, and that supported by GPT is 18 EB. Therefore, use the GPT partition style if your disk capacity is larger than 2 TB. In Linux, if you choose to use the GPT partition style, the fdisk partitioning tool cannot be used. Use the parted partitioning tool instead. For details about disk partition styles, see <a href="evs_01_0038.html">Introduction to Data Disk Initialization Scenarios and Partition Styles</a>.</p>
|
||||
<p id="evs_01_0034__p1082441621516">The maximum partition size that MBR supports is 2 TiB and that GPT supports is 18 EiB. If the disk size you need to partition is greater than 2 TiB, partition the disk using GPT.</p>
|
||||
<p id="evs_01_0034__p15721831171512">The fdisk partitioning tool is suitable only for MBR partitions, and the parted partitioning tool is suitable for both MBR and GPT partitions. For more information, see <a href="evs_01_0038.html">Introduction to Data Disk Initialization Scenarios and Partition Styles</a>.</p>
|
||||
<p id="evs_01_0034__p4630584010514">The method for initializing a disk varies depending on the OS running on the <span id="evs_01_0034__evs_01_0033_text849922751145419">server</span>. This document is used for reference only. For the detailed operations and differences, see the product documents of the corresponding OS.</p>
|
||||
</div>
|
||||
<div class="section" id="evs_01_0034__section36737034185332"><h4 class="sectiontitle">Prerequisites</h4><ul id="evs_01_0034__evs_01_0108_ul28913191171813"><li id="evs_01_0034__evs_01_0108_li20771164724419">A data disk has been attached to <span id="evs_01_0034__evs_01_0108_text184241938124418">a server</span> and has not been initialized.</li><li id="evs_01_0034__evs_01_0108_li36962755115557">You have logged in to the <span id="evs_01_0034__evs_01_0108_text25940422717248">server</span>.<ul id="evs_01_0034__evs_01_0108_ul6229092211568"><li id="evs_01_0034__evs_01_0108_li197989548398">For how to log in to an ECS, see the <em id="evs_01_0034__evs_01_0108_i157642033171941">Elastic Cloud Server User Guide</em>.</li><li id="evs_01_0034__evs_01_0108_li7220898115452">For how to log in to a BMS, see the <em id="evs_01_0034__evs_01_0108_i842352697172014">Bare Metal Server User Guide</em>.</li></ul>
|
||||
</li></ul>
|
||||
</div>
|
||||
<div class="section" id="evs_01_0034__section36039836195351"><h4 class="sectiontitle">Creating and Mounting a Partition</h4><p id="evs_01_0034__p4530289419544">The following example shows you how a new partition can be created on a new data disk that has been attached to <span id="evs_01_0034__text2422957163556">a server</span>. The partition will be created using parted, and GPT is used as the partition style. Furthermore, the partition will be formatted using the ext4 file system, mounted on <strong id="evs_01_0034__b109171540101711">/mnt/sdc</strong>, and configured automatic mounting at system start.</p>
|
||||
<div class="section" id="evs_01_0034__section36039836195351"><h4 class="sectiontitle">Creating and Mounting a Partition</h4><p id="evs_01_0034__p4530289419544">The following example shows you how a new partition can be created on a new data disk that has been attached to <span id="evs_01_0034__text2422957163556">a server</span>. The partition will be created using parted, and GPT will be used. Furthermore, the partition will be formatted using the ext4 file system, mounted on <strong id="evs_01_0034__b109171540101711">/mnt/sdc</strong>, and configured with automatic mounting at system start.</p>
|
||||
</div>
|
||||
<ol id="evs_01_0034__ol1329192162914"><li id="evs_01_0034__li02952152918"><span>Run the following command to query information about the new data disk:</span><p><p id="evs_01_0034__p6233165017299"><strong id="evs_01_0034__b401898111841">lsblk</strong></p>
|
||||
<div class="p" id="evs_01_0034__p1861313818316">Information similar to the following is displayed:<pre class="screen" id="evs_01_0034__screen841414913434">root@ecs-test-0001 ~]# lsblk
|
||||
@ -40,8 +41,8 @@ Disk Flags:
|
||||
</p></li><li id="evs_01_0034__li51339901112856"><span>Run the following command to set the disk partition style:</span><p><p id="evs_01_0034__p9393560112945"><strong id="evs_01_0034__b1848002532151728">mklabel</strong> <em id="evs_01_0034__i1998704360151728">Disk partition style</em></p>
|
||||
<p id="evs_01_0034__p5919528411302">In this example, run the following command to set the partition style to GPT: (Disk partition styles can be MBR or GPT.)</p>
|
||||
<p id="evs_01_0034__p11418922112925"><strong id="evs_01_0034__b17959944112933">mklabel gpt</strong></p>
|
||||
<div class="notice" id="evs_01_0034__note18848725104723"><span class="noticetitle"><img src="public_sys-resources/notice_3.0-en-us.png"> </span><div class="noticebody"><p id="evs_01_0034__evs_01_0038_p11834286151113">The maximum disk capacity supported by MBR is 2 TB, and that supported by GPT is 18 EB. Because a data disk currently supports up to 32 TB, use the GPT partition style if your disk capacity is larger than 2 TB.</p>
|
||||
<p id="evs_01_0034__evs_01_0038_p612681541585">If you change the disk partition style after the disk has been used, the data on the disk will be cleared. Therefore, select a proper disk partition style when initializing the disk.</p>
|
||||
<div class="notice" id="evs_01_0034__note18848725104723"><span class="noticetitle"><img src="public_sys-resources/notice_3.0-en-us.png"> </span><div class="noticebody"><p id="evs_01_0034__evs_01_0038_p11834286151113">The maximum disk size supported by MBR is 2 TiB, and that supported by GPT is 18 EiB. Because an EVS data disk currently supports up to 32 TiB, use GPT if your disk size is larger than 2 TiB.</p>
|
||||
<p id="evs_01_0034__evs_01_0038_p612681541585">If the partition style is changed after the disk has been used, data on the disk will be cleared. Therefore, select an appropriate partition style when initializing the disk. If you must change the partition style to GPT after a disk has been used, it is recommended that you back up the disk data before the change.</p>
|
||||
</div></div>
|
||||
</p></li><li id="evs_01_0034__li17114528113148"><span>Enter <strong id="evs_01_0034__b1695801853151835">p</strong> and press <strong id="evs_01_0034__b188005457151835">Enter</strong> to view the disk partition style.</span><p><div class="p" id="evs_01_0034__p19813031113148">Information similar to the following is displayed:<pre class="screen" id="evs_01_0034__screen1333873825111">(parted) mklabel gpt
|
||||
(parted) p
|
||||
@ -120,6 +121,8 @@ Writing superblocks and filesystem accounting information: done</pre>
|
||||
</p></li><li id="evs_01_0034__li1910362714149"><span>Run the following command to create a mount point:</span><p><p id="evs_01_0034__p1910382791412"><strong id="evs_01_0034__b1856120194514">mkdir</strong> <em id="evs_01_0034__i956219198512">Mount point</em></p>
|
||||
<p id="evs_01_0034__p810320277141">In this example, run the following command to create the <strong id="evs_01_0034__b2288210513">/mnt/sdc</strong> mount point:</p>
|
||||
<p id="evs_01_0034__p171039270143"><strong id="evs_01_0034__b1110352719144">mkdir /mnt/sdc</strong></p>
|
||||
<div class="note" id="evs_01_0034__note1653352162717"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="evs_01_0034__evs_01_0033_p153319214278">The <strong id="evs_01_0034__evs_01_0033_b1926517325558">/mnt</strong> directory exists on all Linux systems. If the mount point fails to create, it may be that the <strong id="evs_01_0034__evs_01_0033_b10608636145619">/mnt</strong> directory has been accidentally deleted. Run the <strong id="evs_01_0034__evs_01_0033_b1583931719296">mkdir -p /mnt/sdc</strong> command to create the mount point.</p>
|
||||
</div></div>
|
||||
</p></li><li id="evs_01_0034__li17103172711414"><span>Run the following command to mount the new partition on the created mount point:</span><p><p id="evs_01_0034__p31039277141"><strong id="evs_01_0034__b16411837205110">mount</strong> <em id="evs_01_0034__i8642173720513">Disk partition</em> <em id="evs_01_0034__i56430370511">Mount point</em></p>
|
||||
<p id="evs_01_0034__p171037271142">In this example, run the following command to mount the new partition <strong id="evs_01_0034__b970419398517">/dev/vdb1</strong> on <strong id="evs_01_0034__b11705143913515">/mnt/sdc</strong>:</p>
|
||||
<p id="evs_01_0034__p51031027171414"><strong id="evs_01_0034__b5103122710147">mount /dev/vdb1 /mnt/sdc</strong></p>
|
||||
@ -149,8 +152,8 @@ tmpfs tmpfs 398M 0 398M 0% /run/user/0
|
||||
<pre class="screen" id="evs_01_0034__evs_01_0033_screen361091453315">[root@ecs-test-0001 ~]# blkid /dev/vdb1
|
||||
/dev/vdb1: UUID="0b3040e2-1367-4abb-841d-ddb0b92693df" TYPE="ext4"</pre>
|
||||
<p id="evs_01_0034__evs_01_0033_p275684701890">The UUID of the <span class="parmname" id="evs_01_0034__evs_01_0033_parmname860990818858"><b>/dev/vdb1</b></span> partition is displayed.</p>
|
||||
</p></li><li id="evs_01_0034__evs_01_0033_li199421823183318"><span>Run the following command to open the <strong>fstab</strong> file using the vi editor:</span><p><p id="evs_01_0034__evs_01_0033_p9610114153320"><strong id="evs_01_0034__evs_01_0033_b1361031419337">vi /etc/fstab</strong></p>
|
||||
</p></li><li id="evs_01_0034__evs_01_0033_li941511389331"><span>Press <strong>i</strong> to enter the editing mode.</span></li><li id="evs_01_0034__evs_01_0033_li8415123893310"><span>Move the cursor to the end of the file and press <strong id="evs_01_0034__evs_01_0033_b1084837140102256">Enter</strong>. Then, add the following information:</span><p><pre class="screen" id="evs_01_0034__evs_01_0033_screen8133145031318">UUID=0b3040e2-1367-4abb-841d-ddb0b92693df /mnt/sdc ext4 defaults 0 2</pre>
|
||||
</p></li><li id="evs_01_0034__evs_01_0033_li199421823183318"><span>Run the following command to open the <strong id="evs_01_0034__evs_01_0033_b972210581107">fstab</strong> file using the vi editor:</span><p><p id="evs_01_0034__evs_01_0033_p9610114153320"><strong id="evs_01_0034__evs_01_0033_b1361031419337">vi /etc/fstab</strong></p>
|
||||
</p></li><li id="evs_01_0034__evs_01_0033_li941511389331"><span>Press <strong id="evs_01_0034__evs_01_0033_b68180161176">i</strong> to enter editing mode.</span></li><li id="evs_01_0034__evs_01_0033_li8415123893310"><span>Move the cursor to the end of the file and press <strong id="evs_01_0034__evs_01_0033_b1084837140102256">Enter</strong>. Then, add the following information:</span><p><pre class="screen" id="evs_01_0034__evs_01_0033_screen8133145031318">UUID=0b3040e2-1367-4abb-841d-ddb0b92693df /mnt/sdc ext4 defaults 0 2</pre>
|
||||
</p></li><li id="evs_01_0034__evs_01_0033_li841512388338"><span>Press <strong id="evs_01_0034__evs_01_0033_b8348192418548">Esc</strong>, enter <strong id="evs_01_0034__evs_01_0033_b15351152418546">:wq</strong>, and press <strong id="evs_01_0034__evs_01_0033_b7353142416544">Enter</strong>.</span><p><p id="evs_01_0034__evs_01_0033_p1141543813310">The system saves the configurations and exits the vi editor.</p>
|
||||
</p></li><li id="evs_01_0034__evs_01_0033_en-us_topic_0142861223_li17720613102410"><span>Perform the following operations to verify the automatic mounting function:</span><p><ol type="a" id="evs_01_0034__evs_01_0033_en-us_topic_0142861223_ol199891910256"><li id="evs_01_0034__evs_01_0033_en-us_topic_0142861223_li1620791415268">Run the following command to unmount the partition:<p id="evs_01_0034__evs_01_0033_en-us_topic_0142861223_p18208131462618"><a name="evs_01_0034__evs_01_0033_en-us_topic_0142861223_li1620791415268"></a><a name="evs_01_0033_en-us_topic_0142861223_li1620791415268"></a><strong id="evs_01_0034__evs_01_0033_b1708526520162011">umount</strong> <em id="evs_01_0034__evs_01_0033_i1458842329162011">Disk partition</em></p>
|
||||
<p id="evs_01_0034__evs_01_0033_en-us_topic_0142861223_p621161413262">In this example, run the following command:</p>
|
||||
@ -159,7 +162,7 @@ tmpfs tmpfs 398M 0 398M 0% /run/user/0
|
||||
</li><li id="evs_01_0034__evs_01_0033_en-us_topic_0142861223_li9280203710269">Run the following command to query the file system mounting information:<p id="evs_01_0034__evs_01_0033_en-us_topic_0142861223_p3282133715264"><a name="evs_01_0034__evs_01_0033_en-us_topic_0142861223_li9280203710269"></a><a name="evs_01_0033_en-us_topic_0142861223_li9280203710269"></a><strong id="evs_01_0034__evs_01_0033_b1187012852919">mount</strong> <strong id="evs_01_0034__evs_01_0033_b17601123382916">|</strong> <strong id="evs_01_0034__evs_01_0033_b1070716324521">grep</strong> <em id="evs_01_0034__evs_01_0033_en-us_topic_0142861223_i2284337112614">Mount point</em></p>
|
||||
<p id="evs_01_0034__evs_01_0033_en-us_topic_0142861223_p3286437112619">In this example, run the following command:</p>
|
||||
<p id="evs_01_0034__evs_01_0033_en-us_topic_0142861223_p18286123782619"><strong id="evs_01_0034__evs_01_0033_b925094342911">mount</strong> <strong id="evs_01_0034__evs_01_0033_b1725119437291">|</strong> <strong id="evs_01_0034__evs_01_0033_b15324154395212">grep</strong> <strong id="evs_01_0034__evs_01_0033_b1831387417">/mnt/sdc</strong></p>
|
||||
<p id="evs_01_0034__evs_01_0033_en-us_topic_0142861223_p429163752616">If information similar to the following is displayed, the automatic mounting function takes effect:</p>
|
||||
<p id="evs_01_0034__evs_01_0033_en-us_topic_0142861223_p429163752616">If information similar to the following is displayed, automatic mounting has been configured:</p>
|
||||
<pre class="screen" id="evs_01_0034__evs_01_0033_en-us_topic_0142861223_screen429312370265">root@ecs-test-0001 ~]# mount | grep /mnt/sdc
|
||||
/dev/vdb1 on /mnt/sdc type ext4 (rw,relatime,data=ordered)</pre>
|
||||
</li></ol>
|
||||
|
@ -61,8 +61,8 @@
|
||||
</tbody>
|
||||
</table>
|
||||
</div>
|
||||
<div class="note" id="evs_01_0035__note195015215325"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="evs_01_0035__p193802581228">The maximum disk capacity that MBR supports is 2 TB, and the disk space exceeding 2 TB cannot be used.</p>
|
||||
<p id="evs_01_0035__p1538018586221">If your disk uses MBR and you need to expand the disk capacity to over 2 TB, change the partition style from MBR to GPT. Ensure that the disk data has been backed up before changing the partition style because services will be interrupted and data on the disk will be cleared during this change.</p>
|
||||
<div class="note" id="evs_01_0035__note195015215325"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="evs_01_0035__p193802581228">The maximum disk capacity that MBR supports is 2 TiB, and the disk space exceeding 2 TiB cannot be used.</p>
|
||||
<p id="evs_01_0035__p1538018586221">If your disk uses MBR and you need to expand the disk capacity to over 2 TiB, change the partition style from MBR to GPT. Ensure that the disk data has been backed up before changing the partition style because services will be interrupted and data on the disk will be cleared during this change.</p>
|
||||
</div></div>
|
||||
</li></ol>
|
||||
<div class="section" id="evs_01_0035__section45741613172812"><a name="evs_01_0035__section45741613172812"></a><a name="section45741613172812"></a><h4 class="sectiontitle">Method 1: Check Partition Style and File System Format Using fdisk</h4><ol id="evs_01_0035__ol2900319714518"><li id="evs_01_0035__li4640174163019"><a name="evs_01_0035__li4640174163019"></a><a name="li4640174163019"></a><span>Run the following command to view all the disks attached to the <span id="evs_01_0035__text56411141123020">server</span>:</span><p><p id="evs_01_0035__p4641134114308"><strong id="evs_01_0035__b1664118411308">lsblk</strong></p>
|
||||
@ -73,7 +73,7 @@ vda 253:0 0 40G 0 disk
|
||||
vdb 253:16 0 150G 0 disk
|
||||
└─vdb1 253:17 0 100G 0 part /mnt/sdc</pre>
|
||||
</div>
|
||||
<p id="evs_01_0035__p1264117419305">In this example, data disk <strong id="evs_01_0035__b1281718371306">/dev/vdb</strong> already has partition <strong id="evs_01_0035__b04731653113011">/dev/vdb1</strong> before capacity expansion, and the additional 50 GB added has not been allocated yet. Therefore, <strong id="evs_01_0035__b1085184053413">/dev/vdb</strong> has 150 GB, and <strong id="evs_01_0035__b3787740143613">/dev/vdb1</strong> has 100 GB.</p>
|
||||
<p id="evs_01_0035__p1264117419305">In this example, data disk <strong id="evs_01_0035__b1281718371306">/dev/vdb</strong> already has partition <strong id="evs_01_0035__b04731653113011">/dev/vdb1</strong> before capacity expansion, and the additional 50 GiB added has not been allocated yet. Therefore, <strong id="evs_01_0035__b1085184053413">/dev/vdb</strong> has 150 GiB, and <strong id="evs_01_0035__b3787740143613">/dev/vdb1</strong> has 100 GiB.</p>
|
||||
</p></li><li id="evs_01_0035__li5970218814518"><span>Run the following command to view the current disk partition style:</span><p><p id="evs_01_0035__p44878614518"><strong id="evs_01_0035__b403908014518">fdisk -l</strong></p>
|
||||
<div class="p" id="evs_01_0035__p3635172814518">Information similar to the following is displayed:<pre class="screen" id="evs_01_0035__screen107608156108">[root@ecs-test-0001 ~]# fdisk -l
|
||||
|
||||
@ -124,7 +124,7 @@ vda 253:0 0 40G 0 disk
|
||||
vdb 253:16 0 150G 0 disk
|
||||
└─vdb1 253:17 0 100G 0 part /mnt/sdc</pre>
|
||||
</div>
|
||||
<p id="evs_01_0035__p10211121533410">In this example, data disk <strong id="evs_01_0035__b530717142814">/dev/vdb</strong> already has partition <strong id="evs_01_0035__b6308101192814">/dev/vdb1</strong> before capacity expansion, and the additional 50 GB added has not been allocated yet. Therefore, <strong id="evs_01_0035__b43080172820">/dev/vdb</strong> has 150 GB, and <strong id="evs_01_0035__b3309516287">/dev/vdb1</strong> has 100 GB.</p>
|
||||
<p id="evs_01_0035__p10211121533410">In this example, data disk <strong id="evs_01_0035__b530717142814">/dev/vdb</strong> already has partition <strong id="evs_01_0035__b6308101192814">/dev/vdb1</strong> before capacity expansion, and the additional 50 GiB added has not been allocated yet. Therefore, <strong id="evs_01_0035__b43080172820">/dev/vdb</strong> has 150 GiB, and <strong id="evs_01_0035__b3309516287">/dev/vdb1</strong> has 100 GiB.</p>
|
||||
</p></li><li id="evs_01_0035__li1188255724115"><span>Run the following command and enter <strong id="evs_01_0035__b842352706203657">p</strong> to view the disk partition style:</span><p><p id="evs_01_0035__p12882155764115"><strong id="evs_01_0035__b1025693618203712">parted</strong> <em id="evs_01_0035__i1926238006203712">Disk</em></p>
|
||||
<p id="evs_01_0035__p53339869164347">For example, run the following command to view <strong id="evs_01_0035__b842352706203733">/dev/vdb</strong>'s partition style:</p>
|
||||
<p id="evs_01_0035__p10864018164411"><strong id="evs_01_0035__b44426524164414">parted /dev/vdb</strong></p>
|
||||
|
@ -5,14 +5,19 @@
|
||||
<div class="p" id="evs_01_0036__p6230616162513">A system disk must be created during <span id="evs_01_0036__text15181149183311">a server</span> creation and is automatically attached. In the disk list, the function of such disks is displayed as <strong id="evs_01_0036__b842352706155347">System disk</strong>, and the status is displayed as <strong id="evs_01_0036__b84235270615548">In-use</strong>. After a system disk is detached from <span id="evs_01_0036__text20526612155529">a server</span>, the disk function changes to <strong id="evs_01_0036__b868150400173329">Bootable disk</strong>, and the status changes to <strong id="evs_01_0036__b806098383173329">Available</strong>.<div class="note" id="evs_01_0036__note36300011364"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="evs_01_0036__p56335010364">Bootable disks are the system disks detached from servers. A bootable disk can be re-attached to <span id="evs_01_0036__text132811158203718">a server</span> and be used as a system disk or data disk depending on the device name selected. </p>
|
||||
</div></div>
|
||||
</div>
|
||||
<p id="evs_01_0036__p28356136210"></p>
|
||||
<p id="evs_01_0036__p26873194402">This section describes how to attach a non-shared disk. A non-shared disk can be attached to one <span id="evs_01_0036__text36172561712">server</span> only.</p>
|
||||
</div>
|
||||
<div class="section" id="evs_01_0036__section1129213187212"><h4 class="sectiontitle">Constraints</h4><p id="evs_01_0036__p184212339219"><span id="evs_01_0036__ph18448326436">Cloud servers created from ISO images are only used for OS installation. They have limited functions and cannot have EVS disks attached.</span></p>
|
||||
</div>
|
||||
<div class="section" id="evs_01_0036__section47232828202528"><h4 class="sectiontitle">Attaching the Disk on the EVS Console</h4><ol id="evs_01_0036__ol653842202528"><li id="evs_01_0036__li5884586202528"><span>Log in to the management console.</span></li><li id="evs_01_0036__li52961278202528"><span>Click <span><img id="evs_01_0036__en-us_topic_0021738346_image052111582392" src="en-us_image_0237893718.png"></span> in the upper left corner and select the desired region and project.</span></li><li id="evs_01_0036__li62005093202528"><span>Under <strong id="evs_01_0036__b795918113316">Storage</strong>, click <strong id="evs_01_0036__b109591886338">Elastic Volume Service</strong>.</span><p><p id="evs_01_0036__p21174931202528">The disk list page is displayed.</p>
|
||||
</p></li><li id="evs_01_0036__li64980985202528"><span>Locate the target disk in the list and click <strong id="evs_01_0036__b757090249">Attach</strong>.</span><p><div class="p" id="evs_01_0036__p9845184614427">The <strong id="evs_01_0036__b232947649">Attach Disk</strong> dialog box is displayed, as shown in <a href="#evs_01_0036__fig15846164615421">Figure 1</a>.<div class="fignone" id="evs_01_0036__fig15846164615421"><a name="evs_01_0036__fig15846164615421"></a><a name="fig15846164615421"></a><span class="figcap"><b>Figure 1 </b>Attach Disk dialog box</span><br><span><img id="evs_01_0036__image153341344165519" src="en-us_image_0133519241.png"></span></div>
|
||||
</p></li><li id="evs_01_0036__li64980985202528"><span>Locate the target disk in the list and click <strong id="evs_01_0036__b481704062">Attach</strong>.</span><p><div class="p" id="evs_01_0036__p9845184614427">The <strong id="evs_01_0036__b1548550537">Attach Disk</strong> dialog box is displayed.<div class="fignone" id="evs_01_0036__fig15846164615421"><span class="figcap"><b>Figure 1 </b>Attach Disk dialog box</span><br><span><img id="evs_01_0036__image153341344165519" src="en-us_image_0133519241.png"></span></div>
|
||||
</div>
|
||||
</p></li><li id="evs_01_0036__li18457248202528"><span>Select <span id="evs_01_0036__text578532842144143">the server</span> and then select a device name from the drop-down list. Ensure that the disk and server are in the same AZ.</span></li><li id="evs_01_0036__li182283315516"><span>Click <span class="uicontrol" id="evs_01_0036__uicontrol32644714295"><b>OK</b></span> to return to the disk list page. The status of the disk is <strong id="evs_01_0036__b62656710299">Attaching</strong>, indicating that the disk is being attached to the server. When the disk status changes to <strong id="evs_01_0036__b842352706133817">In-use</strong>, the disk is successfully attached.</span></li><li id="evs_01_0036__li24651320202528"><span>Initialize the disk.</span><p><p id="evs_01_0036__p29475574202528">After the disk has been attached to a <span id="evs_01_0036__text153212549117128">server</span>, the disk can be used only after you have initialized it. For details, see <a href="evs_01_0038.html">Introduction to Data Disk Initialization Scenarios and Partition Styles</a>.</p>
|
||||
</p></li></ol>
|
||||
</div>
|
||||
<div class="section" id="evs_01_0036__section12130227144011"><h4 class="sectiontitle">Follow-Up Operations</h4><p id="evs_01_0036__p2977174934812">If you are attaching a new disk, you must then log in to the server and initialize the disk before it can be used. To learn how to initialize disks, see <a href="evs_01_0038.html">Introduction to Data Disk Initialization Scenarios and Partition Styles</a>.</p>
|
||||
</div>
|
||||
</div>
|
||||
<div>
|
||||
<div class="familylinks">
|
||||
|
@ -4,17 +4,19 @@
|
||||
<div id="body13189358"><div class="section" id="evs_01_0037__section33496173164047"><h4 class="sectiontitle">Scenarios</h4><p id="evs_01_0037__p14600164918485">Independently created EVS disks are data disks. In the disk list, the function of such disks is displayed as <strong id="evs_01_0037__evs_01_0036_b842352706172629">Data disk</strong>, and the status is displayed as <strong id="evs_01_0037__evs_01_0036_b842352706172713">Available</strong>. In this case, you need to attach the data disks to <span id="evs_01_0037__evs_01_0036_text1952351350154544">servers</span> for use.</p>
|
||||
<p id="evs_01_0037__p56526659201519">This section describes how to attach a shared disk.</p>
|
||||
</div>
|
||||
<div class="section" id="evs_01_0037__section124341536184120"><h4 class="sectiontitle">Constraints</h4><ul id="evs_01_0037__ul3314195354412"><li id="evs_01_0037__li6314125304417">A shared disk can be attached to a maximum of 16 <span id="evs_01_0037__text18175184004110">servers</span>. These <span id="evs_01_0037__text6234359121018">server</span>s and the shared disk must be in the same AZ within a region.</li><li id="evs_01_0037__li399917404445">If a shared disk is in the <strong id="evs_01_0037__b24748265511">In-use</strong> state, ensure that the maximum number of <span id="evs_01_0037__text1120131723418">server</span>s that the disk can be attached to has not been reached.</li><li id="evs_01_0037__li17802167204516">All the <span id="evs_01_0037__text1926124815411">servers</span> of a shared disk must run either Windows or Linux no matter the disk is attached to them in a batch or individually. <p id="evs_01_0037__p1959710189136">For example, if you attach a shared disk to multiple Windows <span id="evs_01_0037__text6638115184110">servers</span> in a batch and then detach it from all its <span id="evs_01_0037__text107021469311">servers</span>, the disk cannot be attached to Linux <span id="evs_01_0037__text7430155574111">servers</span> later. This is because Windows and Linux support different file systems and cannot identify the original file system on the disk. Improper operations may damage the original file system.</p>
|
||||
<div class="section" id="evs_01_0037__section124341536184120"><h4 class="sectiontitle">Constraints</h4><ul id="evs_01_0037__ul3314195354412"><li id="evs_01_0037__li6314125304417">A shared disk can be attached to a maximum of 16 <span id="evs_01_0037__text18175184004110">servers</span>. These <span id="evs_01_0037__text6234359121018">server</span>s and the shared disk must be in the same AZ within a region.<div class="notice" id="evs_01_0037__note6425181162014"><span class="noticetitle"><img src="public_sys-resources/notice_3.0-en-us.png"> </span><div class="noticebody"><p id="evs_01_0037__p14254114202"><span id="evs_01_0037__ph174380122618">If you simply attach a shared disk to multiple <span id="evs_01_0037__evs_faq_0039_text382154512348">server</span>s, files cannot be shared among them. Because there are no mutually agreed data read/write rules among <span id="evs_01_0037__evs_faq_0039_text61093113231">server</span>s, read and write operations from them may interfere with each other, or unpredictable errors may occur.</span> To share files between <span id="evs_01_0037__text44381821083">servers</span>, set up a shared file system or a clustered management system first.</p>
|
||||
</div></div>
|
||||
</li><li id="evs_01_0037__li399917404445">If a shared disk is in the <strong id="evs_01_0037__b24748265511">In-use</strong> state, ensure that the maximum number of <span id="evs_01_0037__text1120131723418">server</span>s that the disk can be attached to has not been reached.</li><li id="evs_01_0037__li17802167204516">All the <span id="evs_01_0037__text2091725624317">servers</span> attached with a shared disk must run either Windows or Linux.<p id="evs_01_0037__p1959710189136">For example, if you attach a shared disk to multiple Windows <span id="evs_01_0037__text6638115184110">servers</span> and then detach it from these <span id="evs_01_0037__text107021469311">servers</span>, the shared disk cannot be attached to Linux <span id="evs_01_0037__text7430155574111">servers</span> later. This is because Windows and Linux support different file systems and cannot identify the original file system on the disk. Improper operations may damage the original file system.</p>
|
||||
</li></ul>
|
||||
<ul id="evs_01_0037__ul1565516417459"><li id="evs_01_0037__li1265524124514">A shared disk can only be used as a data disk. It cannot be used as a system disk.</li></ul>
|
||||
<ul id="evs_01_0037__ul1565516417459"><li id="evs_01_0037__li1265524124514">A shared disk can only be used as a data disk. It cannot be used as a system disk.</li><li id="evs_01_0037__li35413524595"><span id="evs_01_0037__ph37501425112">Cloud servers created from ISO images are only used for OS installation. They have limited functions and cannot have EVS disks attached.</span></li></ul>
|
||||
</div>
|
||||
<div class="section" id="evs_01_0037__section336317164059"><h4 class="sectiontitle">Attaching the Disk on the EVS Console</h4><ol id="evs_01_0037__ol1977955163311"><li id="evs_01_0037__li5884586202528"><span>Log in to the management console.</span></li><li id="evs_01_0037__li2935870315121"><span>Click <span><img id="evs_01_0037__en-us_topic_0021738346_image052111582392" src="en-us_image_0237893718.png"></span> in the upper left corner and select the desired region and project.</span></li><li id="evs_01_0037__li3843952015053"><span>Under <strong id="evs_01_0037__b2040518365150">Storage</strong>, click <strong id="evs_01_0037__b2040533641517">Elastic Volume Service</strong>.</span><p><p id="evs_01_0037__p16002076152423">The disk list page is displayed.</p>
|
||||
</p></li><li id="evs_01_0037__li36967479201531"><span>Locate the target disk in the list and click <strong id="evs_01_0037__b434296602">Attach</strong>.</span><p><p id="evs_01_0037__p3173688892841">The <strong id="evs_01_0037__b84235270692817">Attach Disk</strong> dialog box is displayed.</p>
|
||||
<div class="p" id="evs_01_0037__p36165504212021">Shared disks support batch attachment so that you can attach a shared disk to multiple <span id="evs_01_0037__text298934965101636">servers</span> at a time. The left area in the <strong id="evs_01_0037__b528665994">Attach Disk</strong> dialog box shows the <span id="evs_01_0037__text14032547">server</span> list. After you select the target <span id="evs_01_0037__text293892000">servers</span>, the selected <span id="evs_01_0037__text1192595690">servers</span> will be displayed in the right area.<div class="fignone" id="evs_01_0037__fig24573759111041"><span class="figcap"><b>Figure 1 </b>Attach Disk</span><br><span><img id="evs_01_0037__image97308310154" src="en-us_image_0152639916.png"></span></div>
|
||||
</p></li><li id="evs_01_0037__li36967479201531"><span>Locate the target disk in the list and click <strong id="evs_01_0037__b148868128">Attach</strong>.</span><p><p id="evs_01_0037__p3173688892841">The <strong id="evs_01_0037__b84235270692817">Attach Disk</strong> dialog box is displayed.</p>
|
||||
<div class="p" id="evs_01_0037__p36165504212021">Shared disks support batch attachment so that you can attach a shared disk to multiple <span id="evs_01_0037__text298934965101636">servers</span>. The left area in the <strong id="evs_01_0037__b460378407">Attach Disk</strong> dialog box shows the <span id="evs_01_0037__text1968660444114236">server</span> list. After you select the target <span id="evs_01_0037__text869171055114243">servers</span>, the selected <span id="evs_01_0037__text14382275114250">servers</span> will be displayed in the right area.<div class="fignone" id="evs_01_0037__fig24573759111041"><span class="figcap"><b>Figure 1 </b>Attach Disk</span><br><span><img id="evs_01_0037__image97308310154" src="en-us_image_0152639916.png"></span></div>
|
||||
</div>
|
||||
</p></li><li id="evs_01_0037__li5120896311315"><span>Select the target <span id="evs_01_0037__text49543241143610">servers</span> and then select a device name from the drop-down list for each server you selected. Ensure that the disk and servers are in the same AZ.</span></li><li id="evs_01_0037__li2439421982"><span>Click <span class="uicontrol" id="evs_01_0037__uicontrol1763812716289"><b>OK</b></span> to return to the disk list page. The status of the disk is <strong id="evs_01_0037__b463819278283">Attaching</strong>, indicating that the disk is being attached to the servers. When the disk status changes to <strong id="evs_01_0037__b76181948122813">In-use</strong>, the disk is successfully attached.</span><p><div class="notice" id="evs_01_0037__note19439728813"><span class="noticetitle"><img src="public_sys-resources/notice_3.0-en-us.png"> </span><div class="noticebody"><p id="evs_01_0037__p174381211815">If you simply attach a shared disk to multiple <span id="evs_01_0037__text2012186988152115">servers</span>, files cannot be shared between the <span id="evs_01_0037__text2033675347152121">servers</span> as shared disks do not have the cluster capability. Therefore, build a shared file system or deploy a cluster management system to share files between <span id="evs_01_0037__text55522919152134">servers</span>.</p>
|
||||
</div></div>
|
||||
</p></li></ol>
|
||||
</p></li><li id="evs_01_0037__li5120896311315"><span>Select the target <span id="evs_01_0037__text49543241143610">servers</span> and then select a device name from the drop-down list for each server you selected. Ensure that the disk and servers are in the same AZ.</span></li><li id="evs_01_0037__li2439421982"><span>Click <span class="uicontrol" id="evs_01_0037__uicontrol1763812716289"><b>OK</b></span> to return to the disk list page. The status of the disk is <strong id="evs_01_0037__b463819278283">Attaching</strong>, indicating that the disk is being attached to the servers. When the disk status changes to <strong id="evs_01_0037__b76181948122813">In-use</strong>, the disk is successfully attached.</span></li></ol>
|
||||
</div>
|
||||
<div class="section" id="evs_01_0037__section17645185215013"><h4 class="sectiontitle">Follow-Up Operations</h4><p id="evs_01_0037__evs_01_0036_p2977174934812">If you are attaching a new disk, you must then log in to the server and initialize the disk before it can be used. To learn how to initialize disks, see <a href="evs_01_0038.html">Introduction to Data Disk Initialization Scenarios and Partition Styles</a>.</p>
|
||||
</div>
|
||||
</div>
|
||||
<div>
|
||||
|
@ -1,54 +1,54 @@
|
||||
<a name="evs_01_0038"></a><a name="evs_01_0038"></a>
|
||||
|
||||
<h1 class="topictitle1">Introduction to Data Disk Initialization Scenarios and Partition Styles</h1>
|
||||
<div id="body1511439994246"><div class="section" id="evs_01_0038__section3495606093050"><h4 class="sectiontitle">Scenarios</h4><div class="p" id="evs_01_0038__p9280836203858">After a disk is attached to a <span id="evs_01_0038__text1184202435812">server</span>, you need to log in to the <span id="evs_01_0038__text10187182485810">server</span> to initialize the disk, that is, format the disk. You must initialize a disk before accessing it.<ul id="evs_01_0038__ul64936880203918"><li id="evs_01_0038__li2272733592439">System disk<p id="evs_01_0038__p6479032162353"><a name="evs_01_0038__li2272733592439"></a><a name="li2272733592439"></a>A system disk does not require manual initialization because it is automatically created and initialized upon <span id="evs_01_0038__text265152549174046">server</span> creation. The default disk partition style is master boot record (MBR).</p>
|
||||
<div id="body1511439994246"><div class="section" id="evs_01_0038__section3495606093050"><h4 class="sectiontitle">Scenarios</h4><div class="p" id="evs_01_0038__p9280836203858">After a disk is attached to a <span id="evs_01_0038__text1184202435812">server</span>, you need to log in to the <span id="evs_01_0038__text10187182485810">server</span> to initialize the disk, that is, format the disk. You must initialize a disk before accessing it.<ul id="evs_01_0038__ul64936880203918"><li id="evs_01_0038__li2272733592439">System disk<p id="evs_01_0038__p6479032162353"><a name="evs_01_0038__li2272733592439"></a><a name="li2272733592439"></a>A system disk does not require manual initialization because it is automatically created and initialized upon <span id="evs_01_0038__text265152549174046">server</span> creation. The default partition style is master boot record (MBR).</p>
|
||||
</li><li id="evs_01_0038__li710858692435">Data disk<ul id="evs_01_0038__ul4509464492449"><li id="evs_01_0038__li1145481992348">If a data disk is created along with <span id="evs_01_0038__text727295939115632">a server</span>, it will be automatically attached to the <span id="evs_01_0038__text626098683212827">server</span>.</li><li id="evs_01_0038__li3483818692348">If a data disk is created separately, you need to manually attach it to <span id="evs_01_0038__text1301337270212932">a server</span>.</li></ul>
|
||||
<p id="evs_01_0038__p4337941192547">In both cases, you must initialize the data disk before using it. Choose a proper disk partition style based on your service plan.</p>
|
||||
<p id="evs_01_0038__p4337941192547">In both cases, you must initialize the data disk before using it. Choose an appropriate partition style based on your service plan.</p>
|
||||
</li></ul>
|
||||
</div>
|
||||
</div>
|
||||
<div class="section" id="evs_01_0038__section9329185781310"><h4 class="sectiontitle">Constraints</h4><p id="evs_01_0038__p1663433861715">A disk created from a data source does not need to be initialized. Such a disk contains the data of the data source in the beginning. Initializing the disk may clear the initial data on this disk.</p>
|
||||
</div>
|
||||
<div class="section" id="evs_01_0038__section216694193534"><h4 class="sectiontitle">Disk Partition Styles</h4><p id="evs_01_0038__p38372208144850"><a href="#evs_01_0038__table2729705994129">Table 1</a> lists the common disk partition styles. In Linux, different disk partition styles require different partitioning tools.</p>
|
||||
<div class="section" id="evs_01_0038__section216694193534"><h4 class="sectiontitle">Disk Partition Styles</h4><div class="notice" id="evs_01_0038__note21633485151134"><span class="noticetitle"><img src="public_sys-resources/notice_3.0-en-us.png"> </span><div class="noticebody"><p id="evs_01_0038__p11834286151113">The maximum disk size supported by MBR is 2 TiB, and that supported by GPT is 18 EiB. Because an EVS data disk currently supports up to 32 TiB, use GPT if your disk size is larger than 2 TiB.</p>
|
||||
<p id="evs_01_0038__p612681541585">If the partition style is changed after the disk has been used, data on the disk will be cleared. Therefore, select an appropriate partition style when initializing the disk. If you must change the partition style to GPT after a disk has been used, it is recommended that you back up the disk data before the change.</p>
|
||||
</div></div>
|
||||
<p id="evs_01_0038__p38372208144850"><a href="#evs_01_0038__table2729705994129">Table 1</a> lists the common disk partition styles. In Linux, different partition styles require different partitioning tools.</p>
|
||||
|
||||
<div class="tablenoborder"><a name="evs_01_0038__table2729705994129"></a><a name="table2729705994129"></a><table cellpadding="4" cellspacing="0" summary="" id="evs_01_0038__table2729705994129" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Disk partition styles</caption><thead align="left"><tr id="evs_01_0038__row2194811894129"><th align="left" class="cellrowborder" valign="top" width="20%" id="mcps1.3.3.3.2.5.1.1"><p id="evs_01_0038__p2826869894129">Disk Partition Style</p>
|
||||
<div class="tablenoborder"><a name="evs_01_0038__table2729705994129"></a><a name="table2729705994129"></a><table cellpadding="4" cellspacing="0" summary="" id="evs_01_0038__table2729705994129" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Disk partition styles</caption><thead align="left"><tr id="evs_01_0038__row2194811894129"><th align="left" class="cellrowborder" valign="top" width="20%" id="mcps1.3.3.4.2.5.1.1"><p id="evs_01_0038__p2826869894129">Disk Partition Style</p>
|
||||
</th>
|
||||
<th align="left" class="cellrowborder" valign="top" width="19%" id="mcps1.3.3.3.2.5.1.2"><p id="evs_01_0038__p806324094129">Maximum Disk Capacity Supported</p>
|
||||
<th align="left" class="cellrowborder" valign="top" width="19%" id="mcps1.3.3.4.2.5.1.2"><p id="evs_01_0038__p806324094129">Maximum Disk Capacity Supported</p>
|
||||
</th>
|
||||
<th align="left" class="cellrowborder" valign="top" width="41%" id="mcps1.3.3.3.2.5.1.3"><p id="evs_01_0038__p4914271494129">Maximum Number of Partitions Supported</p>
|
||||
<th align="left" class="cellrowborder" valign="top" width="41%" id="mcps1.3.3.4.2.5.1.3"><p id="evs_01_0038__p4914271494129">Maximum Number of Partitions Supported</p>
|
||||
</th>
|
||||
<th align="left" class="cellrowborder" valign="top" width="20%" id="mcps1.3.3.3.2.5.1.4"><p id="evs_01_0038__p2113692194129">Linux Partitioning Tool</p>
|
||||
<th align="left" class="cellrowborder" valign="top" width="20%" id="mcps1.3.3.4.2.5.1.4"><p id="evs_01_0038__p2113692194129">Linux Partitioning Tool</p>
|
||||
</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody><tr id="evs_01_0038__row5601456494129"><td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.3.3.2.5.1.1 "><p id="evs_01_0038__p1205045294213">Master Boot Record (MBR)</p>
|
||||
<tbody><tr id="evs_01_0038__row5601456494129"><td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.3.4.2.5.1.1 "><p id="evs_01_0038__p1205045294213">Master Boot Record (MBR)</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="19%" headers="mcps1.3.3.3.2.5.1.2 "><p id="evs_01_0038__p2342140694129">2 TB</p>
|
||||
<td class="cellrowborder" valign="top" width="19%" headers="mcps1.3.3.4.2.5.1.2 "><p id="evs_01_0038__p2342140694129">2 TiB</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="41%" headers="mcps1.3.3.3.2.5.1.3 "><ul id="evs_01_0038__ul21060408163037"><li id="evs_01_0038__li45070926163039">4 primary partitions</li><li id="evs_01_0038__li63482739163037">3 primary partitions and 1 extended partition</li></ul>
|
||||
<div class="p" id="evs_01_0038__p723613328428">With MBR, one may create several primary partitions and an extended partition. An extended partition must be divided into several logical partitions before use. For example, if 6 partitions need to be created, you can create the partitions in the following two ways:<ul id="evs_01_0038__ul6972172517474"><li id="evs_01_0038__li49871396163255">3 primary partitions and 1 extended partition, with the extended partition divided into 3 logical partitions</li><li id="evs_01_0038__li1797352519473">1 primary partition and 1 extended partition, with the extended partition divided into 5 logical partitions</li></ul>
|
||||
<td class="cellrowborder" valign="top" width="41%" headers="mcps1.3.3.4.2.5.1.3 "><ul id="evs_01_0038__ul21060408163037"><li id="evs_01_0038__li45070926163039">4 primary partitions</li><li id="evs_01_0038__li63482739163037">3 primary partitions and 1 extended partition</li></ul>
|
||||
<div class="p" id="evs_01_0038__p723613328428">With MBR, you can create several primary partitions and one extended partition. The extended partition must be divided into logical partitions before use. For example, if 6 partitions need to be created, you can create them in the following two ways:<ul id="evs_01_0038__ul6972172517474"><li id="evs_01_0038__li49871396163255">3 primary partitions and 1 extended partition, with the extended partition divided into 3 logical partitions</li><li id="evs_01_0038__li1797352519473">1 primary partition and 1 extended partition, with the extended partition divided into 5 logical partitions</li></ul>
|
||||
</div>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.3.3.2.5.1.4 "><ul id="evs_01_0038__ul1160282695454"><li id="evs_01_0038__li65968598144219">fdisk</li><li id="evs_01_0038__li6593898795457">parted</li></ul>
|
||||
<td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.3.4.2.5.1.4 "><ul id="evs_01_0038__ul1160282695454"><li id="evs_01_0038__li65968598144219">fdisk</li><li id="evs_01_0038__li6593898795457">parted</li></ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="evs_01_0038__row3114938294129"><td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.3.3.2.5.1.1 "><p id="evs_01_0038__p1278766394216">GUID Partition Table (GPT)</p>
|
||||
<tr id="evs_01_0038__row3114938294129"><td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.3.4.2.5.1.1 "><p id="evs_01_0038__p1278766394216">GUID Partition Table (GPT)</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="19%" headers="mcps1.3.3.3.2.5.1.2 "><p id="evs_01_0038__p2460587094129">18 EB</p>
|
||||
<p id="evs_01_0038__p1993019393474">1 EB = 1048576 TB</p>
|
||||
<td class="cellrowborder" valign="top" width="19%" headers="mcps1.3.3.4.2.5.1.2 "><p id="evs_01_0038__p2460587094129">18 EiB</p>
|
||||
<p id="evs_01_0038__p1993019393474">1 EiB = 1048576 TiB</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="41%" headers="mcps1.3.3.3.2.5.1.3 "><p id="evs_01_0038__p4691841694129">Unlimited</p>
|
||||
<td class="cellrowborder" valign="top" width="41%" headers="mcps1.3.3.4.2.5.1.3 "><p id="evs_01_0038__p4691841694129">Unlimited</p>
|
||||
<p id="evs_01_0038__p12599114794712">Disk partitions created using GPT are not categorized.</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.3.3.2.5.1.4 "><p id="evs_01_0038__p4229536794129">parted</p>
|
||||
<td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.3.4.2.5.1.4 "><p id="evs_01_0038__p4229536794129">parted</p>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
</div>
|
||||
<div class="notice" id="evs_01_0038__note21633485151134"><span class="noticetitle"><img src="public_sys-resources/notice_3.0-en-us.png"> </span><div class="noticebody"><p id="evs_01_0038__p11834286151113">The maximum disk capacity supported by MBR is 2 TB, and that supported by GPT is 18 EB. Because a data disk currently supports up to 32 TB, use the GPT partition style if your disk capacity is larger than 2 TB.</p>
|
||||
<p id="evs_01_0038__p612681541585">If you change the disk partition style after the disk has been used, the data on the disk will be cleared. Therefore, select a proper disk partition style when initializing the disk.</p>
|
||||
</div></div>
|
||||
</div>
|
||||
</div>
|
||||
<div>
|
||||
|
@ -1,11 +1,7 @@
|
||||
<a name="evs_01_0039"></a><a name="evs_01_0039"></a>
|
||||
|
||||
|
||||
<h1 class="topictitle1">Appendix</h1>
|
||||
|
||||
<div id="body1514513325309"><p id="evs_01_0039__p8060118"></p>
|
||||
</div>
|
||||
|
||||
<h1 class="topictitle1">Appendix</h1>
|
||||
<div id="body1514513325309"></div>
|
||||
<div>
|
||||
<ul class="ullinks">
|
||||
<li class="ulchildlink"><strong><a href="evs_01_0040.html">EVS Disk Status</a></strong><br>
|
||||
|
@ -15,7 +15,7 @@
|
||||
<td class="cellrowborder" valign="top" width="52.129999999999995%" headers="mcps1.3.1.2.2.4.1.2 "><p id="evs_01_0040__evs_faq_0013_p8182837191747">The EVS disk is attached to <span id="evs_01_0040__evs_faq_0013_text996094623144624">a server</span> and is in use.</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="29.2%" headers="mcps1.3.1.2.2.4.1.3 "><ul id="evs_01_0040__evs_faq_0013_ul6530119818278"><li id="evs_01_0040__evs_faq_0013_li61717410182711">Detaching</li><li id="evs_01_0040__evs_faq_0013_li1083517918278">Creating backups</li><li id="evs_01_0040__evs_faq_0013_li40196816173">Expanding<div class="note" id="evs_01_0040__evs_faq_0013_note22611728203940"><span class="notetitle"> NOTE: </span><div class="notebody"><p id="evs_01_0040__evs_faq_0013_p2178963203940">If a shared EVS disk is in the <span class="parmname" id="evs_01_0040__evs_faq_0013_parmname16804863221452"><b>In-use</b></span> state, the disk can be attached.</p>
|
||||
<p id="evs_01_0040__evs_faq_0013_p4050480162040">If a shared EVS disk is in the <span class="parmname" id="evs_01_0040__evs_faq_0013_parmname486409167"><b>In-use</b></span> state, the disk cannot be expanded.</p>
|
||||
<p id="evs_01_0040__evs_faq_0013_p4050480162040">If a shared EVS disk is in the <span class="parmname" id="evs_01_0040__evs_faq_0013_parmname815612331618"><b>In-use</b></span> state, the disk cannot be expanded.</p>
|
||||
</div></div>
|
||||
</li></ul>
|
||||
</td>
|
||||
|
@ -2,65 +2,65 @@
|
||||
|
||||
<h1 class="topictitle1">EVS Snapshot Status</h1>
|
||||
<div id="body1514186117726"><div class="p" id="evs_01_0041__p8060118">An EVS snapshot has several statuses. <a href="#evs_01_0041__evs_faq_0018_table64552624191747">Table 1</a> lists the EVS snapshot statuses, the meaning of each status, and the operations a snapshot in each status allows.
|
||||
<div class="tablenoborder"><a name="evs_01_0041__evs_faq_0018_table64552624191747"></a><a name="evs_faq_0018_table64552624191747"></a><table cellpadding="4" cellspacing="0" summary="" id="evs_01_0041__evs_faq_0018_table64552624191747" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Snapshot status details</caption><thead align="left"><tr id="evs_01_0041__evs_faq_0018_row53790844191747"><th align="left" class="cellrowborder" valign="top" width="18.67%" id="mcps1.3.1.2.2.4.1.1"><p id="evs_01_0041__evs_faq_0018_p4696184819180">Snapshot Status</p>
|
||||
<div class="tablenoborder"><a name="evs_01_0041__evs_faq_0018_table64552624191747"></a><a name="evs_faq_0018_table64552624191747"></a><table cellpadding="4" cellspacing="0" summary="" id="evs_01_0041__evs_faq_0018_table64552624191747" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Snapshot status details</caption><thead align="left"><tr id="evs_01_0041__evs_faq_0018_row53790844191747"><th align="left" class="cellrowborder" valign="top" width="20.54%" id="mcps1.3.1.2.2.4.1.1"><p id="evs_01_0041__evs_faq_0018_p4696184819180">Snapshot Status</p>
|
||||
</th>
|
||||
<th align="left" class="cellrowborder" valign="top" width="53.63%" id="mcps1.3.1.2.2.4.1.2"><p id="evs_01_0041__evs_faq_0018_p16533784191747">Description</p>
|
||||
<th align="left" class="cellrowborder" valign="top" width="49.09%" id="mcps1.3.1.2.2.4.1.2"><p id="evs_01_0041__evs_faq_0018_p16533784191747">Description</p>
|
||||
</th>
|
||||
<th align="left" class="cellrowborder" valign="top" width="27.700000000000003%" id="mcps1.3.1.2.2.4.1.3"><p id="evs_01_0041__evs_faq_0018_p44528397191747">Allowed Operation</p>
|
||||
<th align="left" class="cellrowborder" valign="top" width="30.37%" id="mcps1.3.1.2.2.4.1.3"><p id="evs_01_0041__evs_faq_0018_p44528397191747">Allowed Operation</p>
|
||||
</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody><tr id="evs_01_0041__evs_faq_0018_row35291149191747"><td class="cellrowborder" valign="top" width="18.67%" headers="mcps1.3.1.2.2.4.1.1 "><p id="evs_01_0041__evs_faq_0018_p40463785165345">Creating</p>
|
||||
<tbody><tr id="evs_01_0041__evs_faq_0018_row35291149191747"><td class="cellrowborder" valign="top" width="20.54%" headers="mcps1.3.1.2.2.4.1.1 "><p id="evs_01_0041__evs_faq_0018_p40463785165345">Creating</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="53.63%" headers="mcps1.3.1.2.2.4.1.2 "><p id="evs_01_0041__evs_faq_0018_p56341191165345">The snapshot is being created.</p>
|
||||
<td class="cellrowborder" valign="top" width="49.09%" headers="mcps1.3.1.2.2.4.1.2 "><p id="evs_01_0041__evs_faq_0018_p56341191165345">The snapshot is being created.</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="27.700000000000003%" headers="mcps1.3.1.2.2.4.1.3 "><p id="evs_01_0041__evs_faq_0018_p233769165345">No operations are allowed.</p>
|
||||
<td class="cellrowborder" valign="top" width="30.37%" headers="mcps1.3.1.2.2.4.1.3 "><p id="evs_01_0041__evs_faq_0018_p233769165345">No operations are allowed.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="evs_01_0041__evs_faq_0018_row12893053191747"><td class="cellrowborder" valign="top" width="18.67%" headers="mcps1.3.1.2.2.4.1.1 "><p id="evs_01_0041__evs_faq_0018_p2259935191846">Available</p>
|
||||
<tr id="evs_01_0041__evs_faq_0018_row12893053191747"><td class="cellrowborder" valign="top" width="20.54%" headers="mcps1.3.1.2.2.4.1.1 "><p id="evs_01_0041__evs_faq_0018_p2259935191846">Available</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="53.63%" headers="mcps1.3.1.2.2.4.1.2 "><p id="evs_01_0041__evs_faq_0018_p16383851191846">The snapshot is successfully created.</p>
|
||||
<td class="cellrowborder" valign="top" width="49.09%" headers="mcps1.3.1.2.2.4.1.2 "><p id="evs_01_0041__evs_faq_0018_p16383851191846">The snapshot is successfully created.</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="27.700000000000003%" headers="mcps1.3.1.2.2.4.1.3 "><ul id="evs_01_0041__evs_faq_0018_ul62104117182653"><li id="evs_01_0041__evs_faq_0018_li2105104916579">Creating EVS disks using snapshots</li><li id="evs_01_0041__evs_faq_0018_li2261316018270">Deleting snapshots</li><li id="evs_01_0041__evs_faq_0018_li35740388182653">Rolling back snapshots to source EVS disks</li></ul>
|
||||
<td class="cellrowborder" valign="top" width="30.37%" headers="mcps1.3.1.2.2.4.1.3 "><ul id="evs_01_0041__evs_faq_0018_ul62104117182653"><li id="evs_01_0041__evs_faq_0018_li2105104916579">Creating EVS disks using snapshots</li><li id="evs_01_0041__evs_faq_0018_li2261316018270">Deleting snapshots</li><li id="evs_01_0041__evs_faq_0018_li35740388182653">Rolling back snapshots to source EVS disks</li></ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="evs_01_0041__evs_faq_0018_row721621712446"><td class="cellrowborder" valign="top" width="18.67%" headers="mcps1.3.1.2.2.4.1.1 "><p id="evs_01_0041__evs_faq_0018_p3658433212455">Deleting</p>
|
||||
<tr id="evs_01_0041__evs_faq_0018_row721621712446"><td class="cellrowborder" valign="top" width="20.54%" headers="mcps1.3.1.2.2.4.1.1 "><p id="evs_01_0041__evs_faq_0018_p3658433212455">Deleting</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="53.63%" headers="mcps1.3.1.2.2.4.1.2 "><p id="evs_01_0041__evs_faq_0018_p3682527212455">The snapshot is being deleted.</p>
|
||||
<td class="cellrowborder" valign="top" width="49.09%" headers="mcps1.3.1.2.2.4.1.2 "><p id="evs_01_0041__evs_faq_0018_p3682527212455">The snapshot is being deleted.</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="27.700000000000003%" headers="mcps1.3.1.2.2.4.1.3 "><p id="evs_01_0041__evs_faq_0018_p4587262812455">No operations are allowed.</p>
|
||||
<td class="cellrowborder" valign="top" width="30.37%" headers="mcps1.3.1.2.2.4.1.3 "><p id="evs_01_0041__evs_faq_0018_p4587262812455">No operations are allowed.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="evs_01_0041__evs_faq_0018_row57957852194514"><td class="cellrowborder" valign="top" width="18.67%" headers="mcps1.3.1.2.2.4.1.1 "><p id="evs_01_0041__evs_faq_0018_p7460362194521">Error</p>
|
||||
<tr id="evs_01_0041__evs_faq_0018_row57957852194514"><td class="cellrowborder" valign="top" width="20.54%" headers="mcps1.3.1.2.2.4.1.1 "><p id="evs_01_0041__evs_faq_0018_p7460362194521">Error</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="53.63%" headers="mcps1.3.1.2.2.4.1.2 "><p id="evs_01_0041__evs_faq_0018_p526628519467">An error occurs when you try to create a snapshot.</p>
|
||||
<td class="cellrowborder" valign="top" width="49.09%" headers="mcps1.3.1.2.2.4.1.2 "><p id="evs_01_0041__evs_faq_0018_p526628519467">An error occurs when you try to create a snapshot.</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="27.700000000000003%" headers="mcps1.3.1.2.2.4.1.3 "><p id="evs_01_0041__evs_faq_0018_p2242870194521">Deleting</p>
|
||||
<td class="cellrowborder" valign="top" width="30.37%" headers="mcps1.3.1.2.2.4.1.3 "><p id="evs_01_0041__evs_faq_0018_p2242870194521">Deleting</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="evs_01_0041__evs_faq_0018_row51729329191747"><td class="cellrowborder" valign="top" width="18.67%" headers="mcps1.3.1.2.2.4.1.1 "><p id="evs_01_0041__evs_faq_0018_p23982637191747">Deletion failed</p>
|
||||
<tr id="evs_01_0041__evs_faq_0018_row51729329191747"><td class="cellrowborder" valign="top" width="20.54%" headers="mcps1.3.1.2.2.4.1.1 "><p id="evs_01_0041__evs_faq_0018_p23982637191747">Deletion failed</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="53.63%" headers="mcps1.3.1.2.2.4.1.2 "><p id="evs_01_0041__evs_faq_0018_p5387879619469">An error occurs when you try to delete a snapshot.</p>
|
||||
<td class="cellrowborder" valign="top" width="49.09%" headers="mcps1.3.1.2.2.4.1.2 "><p id="evs_01_0041__evs_faq_0018_p5387879619469">An error occurs when you try to delete a snapshot.</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="27.700000000000003%" headers="mcps1.3.1.2.2.4.1.3 "><p id="evs_01_0041__evs_faq_0018_p56250197191747">No operations are allowed.</p>
|
||||
<td class="cellrowborder" valign="top" width="30.37%" headers="mcps1.3.1.2.2.4.1.3 "><p id="evs_01_0041__evs_faq_0018_p56250197191747">No operations are allowed.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="evs_01_0041__evs_faq_0018_row57899957175726"><td class="cellrowborder" valign="top" width="18.67%" headers="mcps1.3.1.2.2.4.1.1 "><p id="evs_01_0041__evs_faq_0018_p51337573175726">Rolling back</p>
|
||||
<tr id="evs_01_0041__evs_faq_0018_row57899957175726"><td class="cellrowborder" valign="top" width="20.54%" headers="mcps1.3.1.2.2.4.1.1 "><p id="evs_01_0041__evs_faq_0018_p51337573175726">Rolling back</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="53.63%" headers="mcps1.3.1.2.2.4.1.2 "><p id="evs_01_0041__evs_faq_0018_p3842076519239">The snapshot is rolling back data.</p>
|
||||
<td class="cellrowborder" valign="top" width="49.09%" headers="mcps1.3.1.2.2.4.1.2 "><p id="evs_01_0041__evs_faq_0018_p3842076519239">The snapshot is rolling back data.</p>
|
||||
<div class="note" id="evs_01_0041__evs_faq_0018_note1024257119239"><span class="notetitle"> NOTE: </span><div class="notebody"><ul id="evs_01_0041__evs_faq_0018_ul2507428319239"><li id="evs_01_0041__evs_faq_0018_li2434195619239">When you roll back a snapshot to an EVS disk, you can only roll back the snapshot to the source EVS disk. Rollback to a specified disk is not supported.</li><li id="evs_01_0041__evs_faq_0018_li1775101719239">You can roll back an EVS disk from a snapshot only when the disk is in the <span class="wintitle" id="evs_01_0041__evs_faq_0018_wintitle355923761181956"><b>Available</b></span> or <span class="wintitle" id="evs_01_0041__evs_faq_0018_wintitle698955377181956"><b>Rollback failed</b></span> state.</li></ul>
|
||||
</div></div>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="27.700000000000003%" headers="mcps1.3.1.2.2.4.1.3 "><p id="evs_01_0041__evs_faq_0018_p6428254175726">No operations are allowed.</p>
|
||||
<td class="cellrowborder" valign="top" width="30.37%" headers="mcps1.3.1.2.2.4.1.3 "><p id="evs_01_0041__evs_faq_0018_p6428254175726">No operations are allowed.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="evs_01_0041__evs_faq_0018_row202341611579"><td class="cellrowborder" valign="top" width="18.67%" headers="mcps1.3.1.2.2.4.1.1 "><p id="evs_01_0041__evs_faq_0018_p283543201579">Backing up</p>
|
||||
<tr id="evs_01_0041__evs_faq_0018_row202341611579"><td class="cellrowborder" valign="top" width="20.54%" headers="mcps1.3.1.2.2.4.1.1 "><p id="evs_01_0041__evs_faq_0018_p283543201579">Backing up</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="53.63%" headers="mcps1.3.1.2.2.4.1.2 "><p id="evs_01_0041__evs_faq_0018_p149985721579">This status is available only to temporary snapshots. When you create a backup for an EVS disk, a temporary snapshot is automatically created. This status indicates that a temporary snapshot is being created during the backup creation.</p>
|
||||
<td class="cellrowborder" valign="top" width="49.09%" headers="mcps1.3.1.2.2.4.1.2 "><p id="evs_01_0041__evs_faq_0018_p149985721579">This status is available only to temporary snapshots. When you create a backup for an EVS disk, a temporary snapshot is automatically created. This status indicates that a temporary snapshot is being created during the backup creation.</p>
|
||||
<div class="note" id="evs_01_0041__evs_faq_0018_note1132117458266"><span class="notetitle"> NOTE: </span><div class="notebody"><p id="evs_01_0041__evs_faq_0018_p1432414455260">Temporary snapshots are created through the CBR service. Do not perform any operation on these snapshots.</p>
|
||||
</div></div>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="27.700000000000003%" headers="mcps1.3.1.2.2.4.1.3 "><p id="evs_01_0041__evs_faq_0018_p69247801579">No operations are allowed.</p>
|
||||
<td class="cellrowborder" valign="top" width="30.37%" headers="mcps1.3.1.2.2.4.1.3 "><p id="evs_01_0041__evs_faq_0018_p69247801579">No operations are allowed.</p>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
|
@ -1,12 +1,12 @@
|
||||
<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>
|
||||
<h1 class="topictitle1">Managing EVS Transfers</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 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.</p>
|
||||
<p id="evs_01_0042__p4981704319174">Users can use disk transfer via API only. For more information, see chapter "EVS 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 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__li1827361512598">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 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 using 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. The transfer ID expires after user B accepts the 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>
|
||||
|
@ -1,7 +1,7 @@
|
||||
<a name="evs_01_0044"></a><a name="evs_01_0044"></a>
|
||||
|
||||
<h1 class="topictitle1">Viewing EVS Monitoring Data</h1>
|
||||
<div id="body1517311904305"><div class="section" id="evs_01_0044__section1745822015166"><h4 class="sectiontitle">Description</h4><p id="evs_01_0044__p1573934061612">This section describes monitored metrics reported by EVS to Cloud Eye as well as their namespaces and dimensions. You can use console or APIs provided by Cloud Eye to query the metrics of the monitored objects and alarms generated for EVS.</p>
|
||||
<div id="body1517311904305"><div class="section" id="evs_01_0044__section1745822015166"><h4 class="sectiontitle">Description</h4><p id="evs_01_0044__p1573934061612">This section describes monitored metrics reported by EVS to Cloud Eye as well as their namespaces and dimensions. You can use the console or APIs provided by Cloud Eye to query the metrics of the monitored objects and alarms generated for EVS. </p>
|
||||
</div>
|
||||
<div class="section" id="evs_01_0044__section13533246161919"><h4 class="sectiontitle">Namespace</h4><p id="evs_01_0044__p158039549191">SYS.EVS</p>
|
||||
</div>
|
||||
@ -16,7 +16,7 @@
|
||||
</th>
|
||||
<th align="left" class="cellrowborder" valign="top" width="14.85148514851485%" id="mcps1.3.3.2.2.7.1.5"><p id="evs_01_0044__p1730013458445">Monitored Object</p>
|
||||
</th>
|
||||
<th align="left" class="cellrowborder" valign="top" width="16.831683168316832%" id="mcps1.3.3.2.2.7.1.6"><p id="evs_01_0044__p1489034132517">Monitoring Period (Raw Data)</p>
|
||||
<th align="left" class="cellrowborder" valign="top" width="16.831683168316832%" id="mcps1.3.3.2.2.7.1.6"><p id="evs_01_0044__p1489034132517">Monitoring Period</p>
|
||||
</th>
|
||||
</tr>
|
||||
</thead>
|
||||
@ -31,7 +31,7 @@
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="14.85148514851485%" headers="mcps1.3.3.2.2.7.1.5 "><p id="evs_01_0044__p75621043204313">EVS disk</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="16.831683168316832%" headers="mcps1.3.3.2.2.7.1.6 "><p id="evs_01_0044__p1233515168516">5 minutes</p>
|
||||
<td class="cellrowborder" valign="top" width="16.831683168316832%" headers="mcps1.3.3.2.2.7.1.6 "><p id="evs_01_0044__p189221619124">5 minutes in average</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="evs_01_0044__row79016514437"><td class="cellrowborder" valign="top" width="11.881188118811881%" headers="mcps1.3.3.2.2.7.1.1 "><p id="evs_01_0044__p9990191819211">disk_device_write_bytes_rate</p>
|
||||
@ -45,7 +45,7 @@
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="14.85148514851485%" headers="mcps1.3.3.2.2.7.1.5 "><p id="evs_01_0044__p1856324311438">EVS disk</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="16.831683168316832%" headers="mcps1.3.3.2.2.7.1.6 "><p id="evs_01_0044__p280714191651">5 minutes</p>
|
||||
<td class="cellrowborder" valign="top" width="16.831683168316832%" headers="mcps1.3.3.2.2.7.1.6 "><p id="evs_01_0044__p7926136121220">5 minutes in average</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="evs_01_0044__row29018554320"><td class="cellrowborder" valign="top" width="11.881188118811881%" headers="mcps1.3.3.2.2.7.1.1 "><p id="evs_01_0044__p1299021822118">disk_device_read_requests_rate</p>
|
||||
@ -59,7 +59,7 @@
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="14.85148514851485%" headers="mcps1.3.3.2.2.7.1.5 "><p id="evs_01_0044__p12567114314431">EVS disk</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="16.831683168316832%" headers="mcps1.3.3.2.2.7.1.6 "><p id="evs_01_0044__p1559402216516">5 minutes</p>
|
||||
<td class="cellrowborder" valign="top" width="16.831683168316832%" headers="mcps1.3.3.2.2.7.1.6 "><p id="evs_01_0044__p69311619126">5 minutes in average</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="evs_01_0044__row17904512439"><td class="cellrowborder" valign="top" width="11.881188118811881%" headers="mcps1.3.3.2.2.7.1.1 "><p id="evs_01_0044__p17990101811218">disk_device_write_requests_rate</p>
|
||||
@ -73,7 +73,7 @@
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="14.85148514851485%" headers="mcps1.3.3.2.2.7.1.5 "><p id="evs_01_0044__p5569243174314">EVS disk</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="16.831683168316832%" headers="mcps1.3.3.2.2.7.1.6 "><p id="evs_01_0044__p1219516251753">5 minutes</p>
|
||||
<td class="cellrowborder" valign="top" width="16.831683168316832%" headers="mcps1.3.3.2.2.7.1.6 "><p id="evs_01_0044__p1893612651217">5 minutes in average</p>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
@ -98,7 +98,7 @@
|
||||
</div>
|
||||
<div class="section" id="evs_01_0044__section54024495194114"><h4 class="sectiontitle">Viewing Monitoring Data</h4><ol id="evs_01_0044__ol13017281194126"><li id="evs_01_0044__li5884586202528"><span>Log in to the management console.</span></li><li id="evs_01_0044__li153618295518"><span>Click <span><img id="evs_01_0044__en-us_topic_0021738346_image052111582392" src="en-us_image_0237893718.png"></span> in the upper left corner and select the desired region and project.</span></li><li id="evs_01_0044__li52470483194128"><span>Under <strong id="evs_01_0044__b1479201620352">Storage</strong>, click <strong id="evs_01_0044__b779261653516">Elastic Volume Service</strong>.</span><p><p id="evs_01_0044__p61452060194159">The disk list page is displayed.</p>
|
||||
</p></li><li id="evs_01_0044__li36170315194129"><span>In the EVS disk list, click the name of the disk you want to view the monitoring data.</span><p><p id="evs_01_0044__p62132127194219">The disk details page is displayed.</p>
|
||||
</p></li><li id="evs_01_0044__li86421646175619"><span>On the <strong id="evs_01_0044__b1392401935">Attachments</strong> tab, locate the row that contains the <span id="evs_01_0044__text279044370162844">server</span> and click <strong id="evs_01_0044__b1108885578">View Monitoring Data</strong> in the <strong id="evs_01_0044__b243879855">Operation</strong> column.</span><p><p id="evs_01_0044__p5644446115612">The monitoring graphs page is displayed.</p>
|
||||
</p></li><li id="evs_01_0044__li86421646175619"><span>On the <strong id="evs_01_0044__b179536907">Attachments</strong> tab, locate the row that contains the <span id="evs_01_0044__text279044370162844">server</span> and click <strong id="evs_01_0044__b1457416396">View Monitoring Data</strong> in the <strong id="evs_01_0044__b2123763785">Operation</strong> column.</span><p><p id="evs_01_0044__p5644446115612">The monitoring graphs page is displayed.</p>
|
||||
</p></li><li id="evs_01_0044__li12540914194542"><span>You can view the disk monitoring data by metric or monitored duration.</span><p><p id="evs_01_0044__p3986979319504">For more information about Cloud Eye, see the <em id="evs_01_0044__i84235269714222_3">Cloud Eye User Guide</em>.</p>
|
||||
</p></li></ol>
|
||||
</div>
|
||||
|
@ -1,8 +1,8 @@
|
||||
<a name="evs_01_0045"></a><a name="evs_01_0045"></a>
|
||||
|
||||
<h1 class="topictitle1">Initializing a Windows Data Disk (Windows Server 2016)</h1>
|
||||
<div id="body1527757629024"><div class="section" id="evs_01_0045__section29374781163839"><h4 class="sectiontitle">Scenarios</h4><p id="evs_01_0045__p12171195813313">This section uses Windows Server 2016 Standard 64bit to describe how to initialize a data disk attached to <span id="evs_01_0045__text1464237810424">a server</span> running Windows.</p>
|
||||
<p id="evs_01_0045__p8817185417191">The maximum disk capacity supported by MBR is 2 TB, and that supported by GPT is 18 EB. Therefore, use the GPT partition style if your disk capacity is larger than 2 TB. For details about disk partition styles, see <a href="evs_01_0038.html">Introduction to Data Disk Initialization Scenarios and Partition Styles</a>.</p>
|
||||
<h1 class="topictitle1">Initializing a Windows Data Disk (Windows Server 2019)</h1>
|
||||
<div id="body1527757629024"><div class="section" id="evs_01_0045__section29374781163839"><h4 class="sectiontitle">Scenarios</h4><p id="evs_01_0045__p12171195813313">This section uses Windows Server 2019 Standard 64bit to describe how to initialize a data disk attached to <span id="evs_01_0045__text1464237810424">a server</span> running Windows.</p>
|
||||
<p id="evs_01_0045__p8817185417191">The maximum disk capacity supported by MBR is 2 TiB, and that supported by GPT is 18 EiB. Therefore, use the GPT partition style if your disk capacity is larger than 2 TiB. To learn more about disk partition styles, see <a href="evs_01_0038.html">Introduction to Data Disk Initialization Scenarios and Partition Styles</a>.</p>
|
||||
<p id="evs_01_0045__p52314842171548">The method for initializing a disk varies depending on the OS running on the <span id="evs_01_0045__evs_01_0033_text849922751145419">server</span>. This document is used for reference only. For the detailed operations and differences, see the product documents of the corresponding OS.</p>
|
||||
</div>
|
||||
<div class="section" id="evs_01_0045__section117091356845"><h4 class="sectiontitle">Prerequisites</h4><ul id="evs_01_0045__evs_01_0108_ul28913191171813"><li id="evs_01_0045__evs_01_0108_li20771164724419">A data disk has been attached to <span id="evs_01_0045__evs_01_0108_text184241938124418">a server</span> and has not been initialized.</li><li id="evs_01_0045__evs_01_0108_li36962755115557">You have logged in to the <span id="evs_01_0045__evs_01_0108_text25940422717248">server</span>.<ul id="evs_01_0045__evs_01_0108_ul6229092211568"><li id="evs_01_0045__evs_01_0108_li197989548398">For how to log in to an ECS, see the <em id="evs_01_0045__evs_01_0108_i157642033171941">Elastic Cloud Server User Guide</em>.</li><li id="evs_01_0045__evs_01_0108_li7220898115452">For how to log in to a BMS, see the <em id="evs_01_0045__evs_01_0108_i842352697172014">Bare Metal Server User Guide</em>.</li></ul>
|
||||
@ -15,27 +15,27 @@
|
||||
<div class="fignone" id="evs_01_0045__fig11577433192617"><span class="figcap"><b>Figure 2 </b>Computer Management</span><br><span><img id="evs_01_0045__image1964185645119" src="en-us_image_0175083503.png"></span></div>
|
||||
</p></li><li id="evs_01_0045__li6229732152512"><span>Choose <strong id="evs_01_0045__b8638466">Storage</strong> > <strong id="evs_01_0045__b10637330">Disk Management</strong>.</span><p><div class="p" id="evs_01_0045__p11760167268">Disks are displayed in the right pane. If there is a disk that is not initialized, the system will prompt you with the <strong id="evs_01_0045__b14334732182418">Initialize Disk</strong> dialog box.<div class="fignone" id="evs_01_0045__fig11358119588"><span class="figcap"><b>Figure 3 </b>Disk list</span><br><span><img id="evs_01_0045__image16521250165416" src="en-us_image_0175083504.png"></span></div>
|
||||
</div>
|
||||
</p></li><li id="evs_01_0045__li2535853320"><span>In the <strong id="evs_01_0045__b20212184910251">Initialize Disk</strong> dialog box, the to-be-initialized disk is selected. Select a disk partition style and click <strong id="evs_01_0045__b11120628113016">OK</strong>. In this example, <strong id="evs_01_0045__b7881113093010">GPT (GUID Partition Table)</strong> is selected.</span><p><div class="p" id="evs_01_0045__p115521330048">The <strong id="evs_01_0045__b256839449">Computer Management</strong> window is displayed.<div class="fignone" id="evs_01_0045__fig68332918241"><span class="figcap"><b>Figure 4 </b>Computer Management (Windows Server 2016)</span><br><span><img id="evs_01_0045__image37491117105518" src="en-us_image_0175083507.png"></span></div>
|
||||
</p></li><li id="evs_01_0045__li2535853320"><span>In the <strong id="evs_01_0045__b20212184910251">Initialize Disk</strong> dialog box, the to-be-initialized disk is selected. Select a disk partition style and click <strong id="evs_01_0045__b11120628113016">OK</strong>. In this example, <strong id="evs_01_0045__b7881113093010">GPT (GUID Partition Table)</strong> is selected.</span><p><div class="p" id="evs_01_0045__p115521330048">The <strong id="evs_01_0045__b2090770041">Computer Management</strong> window is displayed.<div class="fignone" id="evs_01_0045__fig68332918241"><span class="figcap"><b>Figure 4 </b>Computer Management</span><br><span><img id="evs_01_0045__image37491117105518" src="en-us_image_0175083507.png"></span></div>
|
||||
</div>
|
||||
<div class="p" id="evs_01_0045__p16552123015416"><div class="notice" id="evs_01_0045__note9642468151238"><span class="noticetitle"><img src="public_sys-resources/notice_3.0-en-us.png"> </span><div class="noticebody"><p id="evs_01_0045__evs_01_0038_p11834286151113">The maximum disk capacity supported by MBR is 2 TB, and that supported by GPT is 18 EB. Because a data disk currently supports up to 32 TB, use the GPT partition style if your disk capacity is larger than 2 TB.</p>
|
||||
<p id="evs_01_0045__evs_01_0038_p612681541585">If you change the disk partition style after the disk has been used, the data on the disk will be cleared. Therefore, select a proper disk partition style when initializing the disk.</p>
|
||||
<div class="p" id="evs_01_0045__p16552123015416"><div class="notice" id="evs_01_0045__note9642468151238"><span class="noticetitle"><img src="public_sys-resources/notice_3.0-en-us.png"> </span><div class="noticebody"><p id="evs_01_0045__evs_01_0038_p11834286151113">The maximum disk size supported by MBR is 2 TiB, and that supported by GPT is 18 EiB. Because an EVS data disk currently supports up to 32 TiB, use GPT if your disk size is larger than 2 TiB.</p>
|
||||
<p id="evs_01_0045__evs_01_0038_p612681541585">If the partition style is changed after the disk has been used, data on the disk will be cleared. Therefore, select an appropriate partition style when initializing the disk. If you must change the partition style to GPT after a disk has been used, it is recommended that you back up the disk data before the change.</p>
|
||||
</div></div>
|
||||
</div>
|
||||
</p></li><li id="evs_01_0045__li19767114614287"><span>Right-click at the unallocated disk space and choose <strong id="evs_01_0045__b842352706195547">New Simple Volume</strong> from the shortcut menu.</span><p><div class="p" id="evs_01_0045__p1255310301449">The <strong id="evs_01_0045__b03172043153315">New Simple Volume Wizard</strong> window is displayed.<div class="fignone" id="evs_01_0045__fig19509202633615"><span class="figcap"><b>Figure 5 </b>New Simple Volume Wizard (Windows Server 2016)</span><br><span><img id="evs_01_0045__image1713903555519" src="en-us_image_0175083508.png"></span></div>
|
||||
</p></li><li id="evs_01_0045__li19767114614287"><span>Right-click at the unallocated disk space and choose <strong id="evs_01_0045__b842352706195547">New Simple Volume</strong> from the shortcut menu.</span><p><div class="p" id="evs_01_0045__p1255310301449">The <strong id="evs_01_0045__b03172043153315">New Simple Volume Wizard</strong> window is displayed.<div class="fignone" id="evs_01_0045__fig19509202633615"><span class="figcap"><b>Figure 5 </b>New Simple Volume Wizard</span><br><span><img id="evs_01_0045__image1713903555519" src="en-us_image_0175083508.png"></span></div>
|
||||
</div>
|
||||
</p></li><li id="evs_01_0045__li976712461280"><span>Follow the prompts and click <strong id="evs_01_0045__b84235270611281">Next</strong>.</span><p><div class="p" id="evs_01_0045__p1455483016417">The <strong id="evs_01_0045__b8756938999334">Specify Volume Size</strong> page is displayed.<div class="fignone" id="evs_01_0045__fig209619215384"><span class="figcap"><b>Figure 6 </b>Specify Volume Size (Windows Server 2016)</span><br><span><img id="evs_01_0045__image0831159568" src="en-us_image_0175083509.png"></span></div>
|
||||
</p></li><li id="evs_01_0045__li976712461280"><span>Follow the prompts and click <strong id="evs_01_0045__b84235270611281">Next</strong>.</span><p><div class="p" id="evs_01_0045__p1455483016417">The <strong id="evs_01_0045__b8756938999334">Specify Volume Size</strong> page is displayed.<div class="fignone" id="evs_01_0045__fig209619215384"><span class="figcap"><b>Figure 6 </b>Specify Volume Size</span><br><span><img id="evs_01_0045__image0831159568" src="en-us_image_0175083509.png"></span></div>
|
||||
</div>
|
||||
</p></li><li id="evs_01_0045__li19788824102215"><span>Specify the volume size and click <strong id="evs_01_0045__b84235270611316">Next</strong>. The system selects the maximum volume size by default. You can specify the volume size as required. In this example, the default setting is used.</span><p><div class="p" id="evs_01_0045__p655611301746">The <strong id="evs_01_0045__b842352706113458">Assign Drive Letter or Path</strong> page is displayed.<div class="fignone" id="evs_01_0045__fig631143204114"><span class="figcap"><b>Figure 7 </b>Assign Driver Letter or Path (Windows Server 2016)</span><br><span><img id="evs_01_0045__image167451246135619" src="en-us_image_0175083510.png"></span></div>
|
||||
</p></li><li id="evs_01_0045__li19788824102215"><span>Specify the volume size and click <strong id="evs_01_0045__b84235270611316">Next</strong>. The system selects the maximum volume size by default. You can specify the volume size as required. In this example, the default setting is used.</span><p><div class="p" id="evs_01_0045__p655611301746">The <strong id="evs_01_0045__b842352706113458">Assign Drive Letter or Path</strong> page is displayed.<div class="fignone" id="evs_01_0045__fig631143204114"><span class="figcap"><b>Figure 7 </b>Assign Driver Letter or Path</span><br><span><img id="evs_01_0045__image167451246135619" src="en-us_image_0175083510.png"></span></div>
|
||||
</div>
|
||||
</p></li><li id="evs_01_0045__li158075128242"><span>Assign a drive letter or path to your partition and click <strong id="evs_01_0045__b842352706113627">Next</strong>. The system assigns drive letter D by default. In this example, the default setting is used.</span><p><p id="evs_01_0045__p938310313428">The <strong id="evs_01_0045__b842352706195931">Format Partition</strong> page is displayed.</p>
|
||||
<div class="fignone" id="evs_01_0045__fig1400313143015"><span class="figcap"><b>Figure 8 </b>Format Partition (Windows Server 2016)</span><br><span><img id="evs_01_0045__image2067886165717" src="en-us_image_0175083511.png"></span></div>
|
||||
</p></li><li id="evs_01_0045__li61511142132711"><span>Specify format settings and click <strong id="evs_01_0045__b842352706114147">Next</strong>. The system selects the NTFS file system by default. You can specify the file system type as required. In this example, the default setting is used.</span><p><div class="p" id="evs_01_0045__p455803013412">The <strong id="evs_01_0045__b84235270620436">Completing the New Simple Volume Wizard</strong> page is displayed.<div class="fignone" id="evs_01_0045__fig380162213463"><span class="figcap"><b>Figure 9 </b>Completing the New Simple Volume Wizard (Windows Server 2016)</span><br><span><img id="evs_01_0045__image14429112185718" src="en-us_image_0175083512.png"></span></div>
|
||||
<div class="fignone" id="evs_01_0045__fig1400313143015"><span class="figcap"><b>Figure 8 </b>Format Partition</span><br><span><img id="evs_01_0045__image2067886165717" src="en-us_image_0175083511.png"></span></div>
|
||||
</p></li><li id="evs_01_0045__li61511142132711"><span>Specify format settings and click <strong id="evs_01_0045__b842352706114147">Next</strong>. The system selects the NTFS file system by default. You can specify the file system type as required. In this example, the default setting is used.</span><p><div class="p" id="evs_01_0045__p455803013412">The <strong id="evs_01_0045__b84235270620436">Completing the New Simple Volume Wizard</strong> page is displayed.<div class="fignone" id="evs_01_0045__fig380162213463"><span class="figcap"><b>Figure 9 </b>Completing the New Simple Volume Wizard</span><br><span><img id="evs_01_0045__image14429112185718" src="en-us_image_0175083512.png"></span></div>
|
||||
<div class="notice" id="evs_01_0045__note48011122184613"><span class="noticetitle"><img src="public_sys-resources/notice_3.0-en-us.png"> </span><div class="noticebody"><p id="evs_01_0045__evs_01_0108_p262682811243">The partition sizes supported by file systems vary. Therefore, you are advised to choose an appropriate file system based on your service requirements.</p>
|
||||
</div></div>
|
||||
</div>
|
||||
</p></li><li id="evs_01_0045__li688515102488"><span>Click <strong id="evs_01_0045__b1790573793213">Finish</strong>.</span><p><div class="p" id="evs_01_0045__p2559103016416">Wait for the initialization to complete. When the volume status changes to <strong id="evs_01_0045__b84235270618345">Healthy</strong>, the initialization has finished successfully, as shown in <a href="#evs_01_0045__fig14464150329">Figure 10</a>.<div class="fignone" id="evs_01_0045__fig14464150329"><a name="evs_01_0045__fig14464150329"></a><a name="fig14464150329"></a><span class="figcap"><b>Figure 10 </b>Disk initialization succeeded (Windows Server 2016)</span><br><span><img id="evs_01_0045__image1338193812571" src="en-us_image_0175083513.png"></span></div>
|
||||
</p></li><li id="evs_01_0045__li688515102488"><span>Click <strong id="evs_01_0045__b1790573793213">Finish</strong>.</span><p><div class="p" id="evs_01_0045__p2559103016416">Wait for the initialization to complete. When the volume status changes to <strong id="evs_01_0045__b84235270618345">Healthy</strong>, the initialization has finished successfully, as shown in <a href="#evs_01_0045__fig14464150329">Figure 10</a>.<div class="fignone" id="evs_01_0045__fig14464150329"><a name="evs_01_0045__fig14464150329"></a><a name="fig14464150329"></a><span class="figcap"><b>Figure 10 </b>Disk initialized</span><br><span><img id="evs_01_0045__image1338193812571" src="en-us_image_0175083513.png"></span></div>
|
||||
</div>
|
||||
</p></li><li id="evs_01_0045__li2095791384515"><span>After the volume is created, click <span><img id="evs_01_0045__image1277612153182" src="en-us_image_0238263336.png"></span> on the task bar and check whether a new volume appears in <strong id="evs_01_0045__b84235270620259">This PC</strong>. In this example, New Volume (D:) is the new volume.</span><p><div class="p" id="evs_01_0045__p1055911301642">If New Volume (D:) appears, the disk is successfully initialized and no further action is required.<div class="fignone" id="evs_01_0045__fig4958111374510"><span class="figcap"><b>Figure 11 </b>This PC (Windows Server 2016)</span><br><span><img id="evs_01_0045__image73951035587" src="en-us_image_0175083515.png"></span></div>
|
||||
</p></li><li id="evs_01_0045__li2095791384515"><span>After the volume is created, click <span><img id="evs_01_0045__image1277612153182" src="en-us_image_0238263336.png"></span> on the task bar and check whether a new volume appears in <strong id="evs_01_0045__b84235270620259">This PC</strong>. In this example, New Volume (D:) is the new volume.</span><p><div class="p" id="evs_01_0045__p1055911301642">If New Volume (D:) appears, the disk is successfully initialized and no further action is required.<div class="fignone" id="evs_01_0045__fig4958111374510"><span class="figcap"><b>Figure 11 </b>This PC</span><br><span><img id="evs_01_0045__image73951035587" src="en-us_image_0175083515.png"></span></div>
|
||||
</div>
|
||||
</p></li></ol>
|
||||
</div>
|
||||
|
53
docs/evs/umn/evs_01_0046.html
Normal file
53
docs/evs/umn/evs_01_0046.html
Normal file
@ -0,0 +1,53 @@
|
||||
<a name="evs_01_0046"></a><a name="evs_01_0046"></a>
|
||||
|
||||
<h1 class="topictitle1">Auditing</h1>
|
||||
<div id="body1528339420607"><div class="section" id="evs_01_0046__section13152191834518"><h4 class="sectiontitle">Scenarios</h4><p id="evs_01_0046__p1995183614412">EVS supports the recording of EVS operations through CTS. You can query EVS traces and use them for historical operation audits and backtracks.</p>
|
||||
</div>
|
||||
<div class="section" id="evs_01_0046__section122392030164512"><h4 class="sectiontitle">Prerequisites</h4><p id="evs_01_0046__p742013711450">CTS has been enabled.</p>
|
||||
</div>
|
||||
<div class="section" id="evs_01_0046__section1239154914459"><h4 class="sectiontitle">Key EVS Operations Recorded by CTS</h4>
|
||||
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="evs_01_0046__table07491454161719" frame="border" border="1" rules="all"><caption><b>Table 1 </b>EVS operations that can be recorded by CTS</caption><thead align="left"><tr id="evs_01_0046__en-us_topic_0100273731_en-us_topic_0100240354_row29946049155120"><th align="left" class="cellrowborder" valign="top" width="31.633163316331636%" id="mcps1.3.3.2.2.4.1.1"><p id="evs_01_0046__en-us_topic_0100273731_en-us_topic_0100240354_p9710894155120">Operation</p>
|
||||
</th>
|
||||
<th align="left" class="cellrowborder" valign="top" width="29.592959295929592%" id="mcps1.3.3.2.2.4.1.2"><p id="evs_01_0046__en-us_topic_0100273731_en-us_topic_0100240354_p26865353155120">Resource</p>
|
||||
</th>
|
||||
<th align="left" class="cellrowborder" valign="top" width="38.77387738773877%" id="mcps1.3.3.2.2.4.1.3"><p id="evs_01_0046__en-us_topic_0100273731_en-us_topic_0100240354_p28609991155120">Trace</p>
|
||||
</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody><tr id="evs_01_0046__en-us_topic_0100273731_en-us_topic_0100240354_row35707974155120"><td class="cellrowborder" valign="top" width="31.633163316331636%" headers="mcps1.3.3.2.2.4.1.1 "><p id="evs_01_0046__en-us_topic_0100273731_en-us_topic_0100240354_p6664814155120">Create disk</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="29.592959295929592%" headers="mcps1.3.3.2.2.4.1.2 "><p id="evs_01_0046__en-us_topic_0100273731_en-us_topic_0100240354_p39976150155120">evs</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="38.77387738773877%" headers="mcps1.3.3.2.2.4.1.3 "><p id="evs_01_0046__en-us_topic_0100273731_en-us_topic_0100240354_p16842727155120">createVolume</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="evs_01_0046__en-us_topic_0100273731_en-us_topic_0100240354_row17366819155120"><td class="cellrowborder" valign="top" width="31.633163316331636%" headers="mcps1.3.3.2.2.4.1.1 "><p id="evs_01_0046__en-us_topic_0100273731_en-us_topic_0100240354_p64535112155120">Update disk</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="29.592959295929592%" headers="mcps1.3.3.2.2.4.1.2 "><p id="evs_01_0046__en-us_topic_0100273731_en-us_topic_0100240354_p25048919155120">evs</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="38.77387738773877%" headers="mcps1.3.3.2.2.4.1.3 "><p id="evs_01_0046__en-us_topic_0100273731_en-us_topic_0100240354_p15696529155120">updateVolume</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="evs_01_0046__en-us_topic_0100273731_en-us_topic_0100240354_row7051035155120"><td class="cellrowborder" valign="top" width="31.633163316331636%" headers="mcps1.3.3.2.2.4.1.1 "><p id="evs_01_0046__en-us_topic_0100273731_en-us_topic_0100240354_p34262967155120">Expand disk capacity</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="29.592959295929592%" headers="mcps1.3.3.2.2.4.1.2 "><p id="evs_01_0046__en-us_topic_0100273731_en-us_topic_0100240354_p51743936155120">evs</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="38.77387738773877%" headers="mcps1.3.3.2.2.4.1.3 "><p id="evs_01_0046__en-us_topic_0100273731_en-us_topic_0100240354_p30509310155120">extendVolume</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="evs_01_0046__en-us_topic_0100273731_en-us_topic_0100240354_row6148335155120"><td class="cellrowborder" valign="top" width="31.633163316331636%" headers="mcps1.3.3.2.2.4.1.1 "><p id="evs_01_0046__en-us_topic_0100273731_en-us_topic_0100240354_p28253132155120">Delete disk</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="29.592959295929592%" headers="mcps1.3.3.2.2.4.1.2 "><p id="evs_01_0046__en-us_topic_0100273731_en-us_topic_0100240354_p14121412155120">evs</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="38.77387738773877%" headers="mcps1.3.3.2.2.4.1.3 "><p id="evs_01_0046__en-us_topic_0100273731_en-us_topic_0100240354_p2983727155120">deleteVolume</p>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
</div>
|
||||
</div>
|
||||
<div class="section" id="evs_01_0046__section134359321462"><h4 class="sectiontitle">Viewing Traces</h4><p id="evs_01_0046__p19665192813433">To view audit logs, see <a href="https://docs.otc.t-systems.com/en-us/usermanual/cts/en-us_topic_0030598499.html" target="_blank" rel="noopener noreferrer">Querying Traces on the CTS Console</a>.</p>
|
||||
</div>
|
||||
</div>
|
||||
<div></div>
|
||||
|
@ -1,9 +1,9 @@
|
||||
<a name="evs_01_0048"></a><a name="evs_01_0048"></a>
|
||||
|
||||
<h1 class="topictitle1">Differences Between EVS Disk Backup and EVS Snapshot</h1>
|
||||
<div id="body1529484694805"><p id="evs_01_0048__p16832356194847">Both EVS disk backup and EVS snapshot provide redundancies for the EVS disk data to improve reliability. <a href="#evs_01_0048__table8676102116384">Table 1</a> lists the differences between them.</p>
|
||||
<h1 class="topictitle1">Differences Between EVS Backups and EVS Snapshots</h1>
|
||||
<div id="body1529484694805"><p id="evs_01_0048__p16832356194847">Both EVS backups and EVS snapshots provide redundancies for improved disk data reliability. <a href="#evs_01_0048__table8676102116384">Table 1</a> lists the differences between them.</p>
|
||||
|
||||
<div class="tablenoborder"><a name="evs_01_0048__table8676102116384"></a><a name="table8676102116384"></a><table cellpadding="4" cellspacing="0" summary="" id="evs_01_0048__table8676102116384" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Differences between backups and snapshots</caption><thead align="left"><tr id="evs_01_0048__en-us_topic_0160754745_row15865513185044"><th align="left" class="cellrowborder" valign="top" width="17.37%" id="mcps1.3.2.2.6.1.1"><p id="evs_01_0048__en-us_topic_0160754745_p23234826185044">Item</p>
|
||||
<div class="tablenoborder"><a name="evs_01_0048__table8676102116384"></a><a name="table8676102116384"></a><table cellpadding="4" cellspacing="0" summary="" id="evs_01_0048__table8676102116384" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Differences between backups and snapshots</caption><thead align="left"><tr id="evs_01_0048__en-us_topic_0160754745_row15865513185044"><th align="left" class="cellrowborder" valign="top" width="17.37%" id="mcps1.3.2.2.6.1.1"><p id="evs_01_0048__en-us_topic_0160754745_p23234826185044">Metric</p>
|
||||
</th>
|
||||
<th align="left" class="cellrowborder" valign="top" width="22.63%" id="mcps1.3.2.2.6.1.2"><p id="evs_01_0048__en-us_topic_0160754745_p2972717185044">Storage Solution</p>
|
||||
</th>
|
||||
@ -17,26 +17,26 @@
|
||||
</thead>
|
||||
<tbody><tr id="evs_01_0048__en-us_topic_0160754745_row62809202185044"><td class="cellrowborder" valign="top" width="17.37%" headers="mcps1.3.2.2.6.1.1 "><p id="evs_01_0048__en-us_topic_0160754745_p54380567185044">Backup</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="22.63%" headers="mcps1.3.2.2.6.1.2 "><p id="evs_01_0048__en-us_topic_0160754745_p42749784185044">Backup data is stored in OBS, instead of disks. This ensures data restoration upon disk data loss or corruption.</p>
|
||||
<td class="cellrowborder" valign="top" width="22.63%" headers="mcps1.3.2.2.6.1.2 "><p id="evs_01_0048__en-us_topic_0160754745_p42749784185044">Backups are stored in OBS, instead of disks. This ensures data restoration upon disk loss or corruption.</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.2.2.6.1.3 "><p id="evs_01_0048__en-us_topic_0160754745_p36687371185155">A backup is the data copy of a disk at a given point in time. CBR supports automatic backup by configuring backup policies. Deleting a disk will not clear its backups.</p>
|
||||
<td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.2.2.6.1.3 "><p id="evs_01_0048__en-us_topic_0160754745_p36687371185155">A backup is a copy of a disk at a given point of time and is stored in a different location. Automatic backup can be performed based on backup policies. Deleting a disk will not delete its backups.</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.2.2.6.1.4 "><p id="evs_01_0048__en-us_topic_0160754745_p33395921185044">A backup and its source disk reside in the same AZ.</p>
|
||||
<td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.2.2.6.1.4 "><p id="evs_01_0048__en-us_topic_0160754745_p33395921185044">A backup and its source disk reside in different AZs.</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.2.2.6.1.5 "><p id="evs_01_0048__en-us_topic_0160754745_p55913259185228">Data can be recovered and services can be restored by restoring the backup data to original disks or creating new disks from backups, ensuring excellent data reliability.</p>
|
||||
<td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.2.2.6.1.5 "><p id="evs_01_0048__en-us_topic_0160754745_p55913259185228">To restore data and recover services, you can restore the backups to their original disks or create new disks from the backups.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="evs_01_0048__en-us_topic_0160754745_row52218143185044"><td class="cellrowborder" valign="top" width="17.37%" headers="mcps1.3.2.2.6.1.1 "><p id="evs_01_0048__en-us_topic_0160754745_p1811200185044">Snapshot</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="22.63%" headers="mcps1.3.2.2.6.1.2 "><p id="evs_01_0048__en-us_topic_0160754745_p4522786718532">Snapshot data is stored with disk data.</p>
|
||||
<div class="note" id="evs_01_0048__en-us_topic_0160754745_note439761918532"><span class="notetitle"> NOTE: </span><div class="notebody"><p id="evs_01_0048__en-us_topic_0160754745_p3957857618532">Creating a backup requires a certain amount of time because data needs to be transferred. Therefore, creating or rolling back a snapshot consumes less time than creating a backup.</p>
|
||||
<td class="cellrowborder" valign="top" width="22.63%" headers="mcps1.3.2.2.6.1.2 "><p id="evs_01_0048__en-us_topic_0160754745_p4522786718532">Snapshots are stored on the same disk as the original data.</p>
|
||||
<div class="note" id="evs_01_0048__en-us_topic_0160754745_note439761918532"><span class="notetitle"> NOTE: </span><div class="notebody"><p id="evs_01_0048__en-us_topic_0160754745_p3957857618532">Creating a backup requires a certain amount of time because data needs to be transferred to OBS. Creating or rolling back a snapshot consumes less time than creating a backup.</p>
|
||||
</div></div>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.2.2.6.1.3 "><p id="evs_01_0048__en-us_topic_0160754745_p5975691185310">A snapshot is the state of a disk at a specific point in time. If a disk is deleted, all the snapshots created for this disk will also be deleted. If you have reinstalled or changed the server OS, snapshots of the system disk are automatically deleted. Snapshots of the data disks can be used as usual.</p>
|
||||
<td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.2.2.6.1.3 "><p id="evs_01_0048__en-us_topic_0160754745_p5975691185310">A snapshot is the state of a disk at a specific point in time and is stored on the same disk. If the disk is deleted, all its snapshots will also be deleted. For example, if you reinstalled or changed the server OS, snapshots of the system disk were also automatically deleted. Snapshots of the data disks can be used as usual.</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.2.2.6.1.4 "><p id="evs_01_0048__en-us_topic_0160754745_p63972361185316">A snapshot and its source disk reside in the same AZ.</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.2.2.6.1.5 "><p id="evs_01_0048__en-us_topic_0160754745_p1833826517212">You can use a snapshot to roll back its original disk or create a disk for data restoration and service recovery.</p>
|
||||
<td class="cellrowborder" valign="top" width="20%" headers="mcps1.3.2.2.6.1.5 "><p id="evs_01_0048__en-us_topic_0160754745_p1833826517212">You can use a snapshot to roll back its original disk or create a disk from the snapshot.</p>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
|
@ -1,15 +1,14 @@
|
||||
<a name="evs_01_0058"></a><a name="evs_01_0058"></a>
|
||||
|
||||
<h1 class="topictitle1">Initialize an EVS Data Disk</h1>
|
||||
<div id="body1536224488216"><p id="evs_01_0058__p8060118"></p>
|
||||
</div>
|
||||
<div id="body1536224488216"></div>
|
||||
<div>
|
||||
<ul class="ullinks">
|
||||
<li class="ulchildlink"><strong><a href="evs_01_0038.html">Introduction to Data Disk Initialization Scenarios and Partition Styles</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="evs_01_0108.html">Initializing a Windows Data Disk (Windows Server 2008)</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="evs_01_0045.html">Initializing a Windows Data Disk (Windows Server 2016)</a></strong><br>
|
||||
<li class="ulchildlink"><strong><a href="evs_01_0045.html">Initializing a Windows Data Disk (Windows Server 2019)</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="evs_01_0033.html">Initializing a Linux Data Disk (fdisk)</a></strong><br>
|
||||
</li>
|
||||
|
File diff suppressed because it is too large
Load Diff
@ -1,20 +1,25 @@
|
||||
<a name="evs_01_0077"></a><a name="evs_01_0077"></a>
|
||||
|
||||
<h1 class="topictitle1">Capacity Expansion</h1>
|
||||
<div id="body1555575597900"><p id="evs_01_0077__p8060118"></p>
|
||||
</div>
|
||||
<div id="body1555575597900"></div>
|
||||
<div>
|
||||
<ul class="ullinks">
|
||||
<li class="ulchildlink"><strong><a href="evs_faq_0026.html">Can I Reduce or Temporarily Expand the Disk Capacity?</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="evs_faq_0075.html">What Are the Differences Between Expanding Capacity by Expanding an EVS Disk and Creating a New EVS Disk?</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="evs_faq_0044.html">Will My Disk Data Be Lost After I Expand the Disk Capacity?</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="evs_faq_0042.html">Do I Need to Restart the Server After Expanding the Disk Capacity?</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="evs_faq_0028.html">Do I Need to Detach an EVS Disk Before Expanding Its Capacity?</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="evs_faq_0024.html">What Should I Do If My Disk Capacity Exceeds 2 TB After Expansion?</a></strong><br>
|
||||
<li class="ulchildlink"><strong><a href="evs_faq_0024.html">What Should I Do If My Disk Capacity Exceeds 2 TiB After Expansion?</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="evs_faq_0027.html">Why Did My Disk Capacity Remain Unchanged on the Server After Capacity Expansion?</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="evs_faq_0073.html">How Do I Extend the File System of an Unpartitioned Data Disk in Linux?</a></strong><br>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<div class="familylinks">
|
||||
|
Some files were not shown because too many files have changed in this diff Show More
Loading…
x
Reference in New Issue
Block a user