diff --git a/docs/evs/umn/ALL_META.TXT.json b/docs/evs/umn/ALL_META.TXT.json index 0fb3f8a6..1de7f759 100644 --- a/docs/evs/umn/ALL_META.TXT.json +++ b/docs/evs/umn/ALL_META.TXT.json @@ -13,7 +13,7 @@ "uri":"en-us_topic_0014580741.html", "product_code":"evs", "code":"2", - "des":"Elastic Volume Service (EVS) offers scalable block storage for cloud servers. With high reliability, high performance, and rich specifications, EVS disks can be used for ", + "des":"Elastic Volume Service (EVS) offers scalable block storage for cloud servers. With high reliability, high performance, and a variety of specifications, EVS disks can be u", "doc_type":"usermanual", "kw":"What Is EVS?,Overview,User Guide", "title":"What Is EVS?", @@ -55,8 +55,8 @@ "code":"6", "des":"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.EVS uses", "doc_type":"usermanual", - "kw":"EVS Disk Encryption,Overview,User Guide", - "title":"EVS Disk Encryption", + "kw":"EVS Encryption,Overview,User Guide", + "title":"EVS Encryption", "githuburl":"" }, { @@ -83,10 +83,10 @@ "uri":"evs_01_0048.html", "product_code":"evs", "code":"9", - "des":"Both EVS disk backup and EVS snapshot provide redundancies for the EVS disk data to improve reliability. Table 1 lists the differences between them.", + "des":"Both EVS backups and EVS snapshots provide redundancies for improved disk data reliability. Table 1 lists the differences between them.", "doc_type":"usermanual", - "kw":"Differences Between EVS Disk Backup and EVS Snapshot,Overview,User Guide", - "title":"Differences Between EVS Disk Backup and EVS Snapshot", + "kw":"Differences Between EVS Backups and EVS Snapshots,Overview,User Guide", + "title":"Differences Between EVS Backups and EVS Snapshots", "githuburl":"" }, { @@ -155,7 +155,7 @@ "code":"16", "des":"Figure 1 shows the basic EVS operation procedure.Basic operation procedure", "doc_type":"usermanual", - "kw":"购买磁盘,购买块存储,购买数据盘,使用云硬盘,使用磁盘,挂载云硬盘,挂载磁盘,初始化数据盘,初始化磁盘,格式化磁盘,格式化云硬盘,Basic Operation Procedure,Getting S", + "kw":"Basic Operation Procedure,Getting Started,User Guide", "title":"Basic Operation Procedure", "githuburl":"" }, @@ -163,9 +163,9 @@ "uri":"en-us_topic_0021738346.html", "product_code":"evs", "code":"17", - "des":"EVS disks can be used as system disks or data disks for servers.When a server is created, a system disk is automatically created and attached. You cannot create a system ", + "des":"EVS disks can be used as system disks or data disks for servers.System disks can only be created together with servers and are automatically attached.A system disk can ha", "doc_type":"usermanual", - "kw":"购买磁盘,购买块存储,购买数据盘,Create an EVS Disk,Getting Started,User Guide", + "kw":"Create an EVS Disk,Getting Started,User Guide", "title":"Create an EVS Disk", "githuburl":"" }, @@ -175,7 +175,7 @@ "code":"18", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", - "kw":"挂载云硬盘,挂载磁盘", + "kw":"Attach an EVS Disk", "title":"Attach an EVS Disk", "githuburl":"" }, @@ -185,7 +185,7 @@ "code":"19", "des":"Independently created EVS disks are data disks. In the disk list, the function of such disks is displayed as Data disk, and the status is displayed as Available. In this ", "doc_type":"usermanual", - "kw":"挂载云硬盘,挂载磁盘,挂载非共享盘,挂载非共享磁盘,Attaching a Non-Shared Disk,Attach an EVS Disk,User Guide", + "kw":"Attaching a Non-Shared Disk,Attach an EVS Disk,User Guide", "title":"Attaching a Non-Shared Disk", "githuburl":"" }, @@ -195,7 +195,7 @@ "code":"20", "des":"Independently created EVS disks are data disks. In the disk list, the function of such disks is displayed as Data disk, and the status is displayed as Available. In this ", "doc_type":"usermanual", - "kw":"挂载云硬盘,挂载磁盘,挂载共享盘,挂载共享磁盘,Attaching a Shared Disk,Attach an EVS Disk,User Guide", + "kw":"Attaching a Shared Disk,Attach an EVS Disk,User Guide", "title":"Attaching a Shared Disk", "githuburl":"" }, @@ -205,7 +205,7 @@ "code":"21", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", - "kw":"初始化数据盘,初始化磁盘,格式化磁盘,格式化云硬盘", + "kw":"Initialize an EVS Data Disk", "title":"Initialize an EVS Data Disk", "githuburl":"" }, @@ -215,7 +215,7 @@ "code":"22", "des":"After a disk is attached to a server, you need to log in to the server to initialize the disk, that is, format the disk. You must initialize a disk before accessing it.Sy", "doc_type":"usermanual", - "kw":"初始化数据盘,初始化磁盘,格式化磁盘,格式化云硬盘,分区形式,GPT,MBR,更换分区形式,Introduction to Data Disk Initialization Scenarios and", + "kw":"Introduction to Data Disk Initialization Scenarios and Partition Styles,Initialize an EVS Data Disk,", "title":"Introduction to Data Disk Initialization Scenarios and Partition Styles", "githuburl":"" }, @@ -225,7 +225,7 @@ "code":"23", "des":"This section uses Windows Server 2008 R2 Enterprise 64bit to describe how to initialize a data disk attached to a server running Windows.The maximum disk capacity support", "doc_type":"usermanual", - "kw":"初始化数据盘,初始化磁盘,格式化磁盘,格式化云硬盘,Initializing a Windows Data Disk (Windows Server 2008),Initialize an EVS D", + "kw":"Initializing a Windows Data Disk (Windows Server 2008),Initialize an EVS Data Disk,User Guide", "title":"Initializing a Windows Data Disk (Windows Server 2008)", "githuburl":"" }, @@ -233,19 +233,19 @@ "uri":"evs_01_0045.html", "product_code":"evs", "code":"24", - "des":"This section uses Windows Server 2016 Standard 64bit to describe how to initialize a data disk attached to a server running Windows.The maximum disk capacity supported by", + "des":"This section uses Windows Server 2019 Standard 64bit to describe how to initialize a data disk attached to a server running Windows.The maximum disk capacity supported by", "doc_type":"usermanual", - "kw":"初始化数据盘,初始化磁盘,格式化磁盘,格式化云硬盘,Initializing a Windows Data Disk (Windows Server 2016),Initialize an EVS D", - "title":"Initializing a Windows Data Disk (Windows Server 2016)", + "kw":"Initializing a Windows Data Disk (Windows Server 2019),Initialize an EVS Data Disk,User Guide", + "title":"Initializing a Windows Data Disk (Windows Server 2019)", "githuburl":"" }, { "uri":"evs_01_0033.html", "product_code":"evs", "code":"25", - "des":"This section uses CentOS 7.4 64bit to describe how to initialize a data disk attached to a server running Linux and use fdisk to partition the data disk.The maximum disk ", + "des":"This section uses CentOS 7.4 64bit to describe how to initialize a data disk attached to a server running Linux and use fdisk to partition the data disk.The maximum parti", "doc_type":"usermanual", - "kw":"初始化数据盘,初始化磁盘,格式化磁盘,格式化云硬盘,Initializing a Linux Data Disk (fdisk),Initialize an EVS Data Disk,User Gu", + "kw":"Initializing a Linux Data Disk (fdisk),Initialize an EVS Data Disk,User Guide", "title":"Initializing a Linux Data Disk (fdisk)", "githuburl":"" }, @@ -253,9 +253,9 @@ "uri":"evs_01_0034.html", "product_code":"evs", "code":"26", - "des":"This section uses CentOS 7.4 64bit to describe how to initialize a data disk attached to a server running Linux and use parted to partition the data disk.The maximum disk", + "des":"This section uses CentOS 7.4 64bit to describe how to initialize a data disk attached to a server running Linux and use parted to partition the data disk.The maximum part", "doc_type":"usermanual", - "kw":"初始化数据盘,初始化磁盘,格式化磁盘,格式化云硬盘,Initializing a Linux Data Disk (parted),Initialize an EVS Data Disk,User G", + "kw":"Initializing a Linux Data Disk (parted),Initialize an EVS Data Disk,User Guide", "title":"Initializing a Linux Data Disk (parted)", "githuburl":"" }, @@ -295,7 +295,7 @@ "code":"30", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", - "kw":"扩容云硬盘,扩容磁盘,磁盘空间不足,磁盘容量不足", + "kw":"Disk Capacity Expansion", "title":"Disk Capacity Expansion", "githuburl":"" }, @@ -303,9 +303,9 @@ "uri":"evs_01_0006.html", "product_code":"evs", "code":"31", - "des":"If the capacity of an existing disk is insufficient, you can expand the disk capacity to increase the storage space.Both system disks and data disks can be expanded. Curr", + "des":"If the capacity of an existing disk is insufficient, you can expand the disk capacity to increase the storage space.Both system disks and data disks can be expanded. Disk", "doc_type":"usermanual", - "kw":"扩容云硬盘,扩容磁盘,磁盘空间不足,磁盘容量不足,扩容磁盘流程,磁盘扩容流程,在线扩容,不卸载磁盘扩容,离线扩容,卸载磁盘扩容,扩容数据盘,扩容系统盘,Expansion Overview,Disk ", + "kw":"Expansion Overview,Disk Capacity Expansion,User Guide", "title":"Expansion Overview", "githuburl":"" }, @@ -315,7 +315,7 @@ "code":"32", "des":"This section describes how to expand the capacity of an In-use EVS disk on the management console. The In-use status indicates that the disk has been attached to a server", "doc_type":"usermanual", - "kw":"扩容云硬盘,扩容磁盘,磁盘空间不足,磁盘容量不足,在线扩容,不卸载磁盘扩容,扩容数据盘,扩容系统盘,Expanding Capacity for an In-use EVS Disk,Disk Cap", + "kw":"Expanding Capacity for an In-use EVS Disk,Disk Capacity Expansion,User Guide", "title":"Expanding Capacity for an In-use EVS Disk", "githuburl":"" }, @@ -325,7 +325,7 @@ "code":"33", "des":"This section describes how to expand the capacity of an Available EVS disk on the management console. The Available status indicates that the disk has not been attached t", "doc_type":"usermanual", - "kw":"扩容云硬盘,扩容磁盘,磁盘空间不足,磁盘容量不足,离线扩容,卸载磁盘扩容,扩容数据盘,扩容系统盘,Expanding Capacity for an Available EVS Disk,Disk C", + "kw":"Expanding Capacity for an Available EVS Disk,Disk Capacity Expansion,User Guide", "title":"Expanding Capacity for an Available EVS Disk", "githuburl":"" }, @@ -335,7 +335,7 @@ "code":"34", "des":"After a disk has been expanded on the management console, the disk size is enlarged, but the additional space cannot be used directly.In Windows, you must allocate the ad", "doc_type":"usermanual", - "kw":"扩容云硬盘,扩容磁盘,磁盘空间不足,磁盘容量不足,扩容windows系统盘,扩容windows数据盘,Extending Disk Partitions and File Systems (Windo", + "kw":"Extending Disk Partitions and File Systems (Windows Server 2008),Disk Capacity Expansion,User Guide", "title":"Extending Disk Partitions and File Systems (Windows Server 2008)", "githuburl":"" }, @@ -345,7 +345,7 @@ "code":"35", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", - "kw":"扩容云硬盘,扩容磁盘,磁盘空间不足,磁盘容量不足,扩容linux数据盘,扩容linux系统盘", + "kw":"Extending Disk Partitions and File Systems (Linux)", "title":"Extending Disk Partitions and File Systems (Linux)", "githuburl":"" }, @@ -355,7 +355,7 @@ "code":"36", "des":"Before extending the disk partition and file system, you must check the disk partition style and file system format, and then select the appropriate operation accordingly", "doc_type":"usermanual", - "kw":"扩容云硬盘,扩容磁盘,磁盘空间不足,磁盘容量不足,扩容linux数据盘,扩容linux系统盘,Partition and File System Extension Preparations (Lin", + "kw":"Partition and File System Extension Preparations (Linux),Extending Disk Partitions and File Systems ", "title":"Partition and File System Extension Preparations (Linux)", "githuburl":"" }, @@ -365,7 +365,7 @@ "code":"37", "des":"After a disk has been expanded on the management console, the disk size is enlarged, but the additional space cannot be used directly.In Linux, you must allocate the addi", "doc_type":"usermanual", - "kw":"扩容云硬盘,扩容磁盘,磁盘空间不足,磁盘容量不足,扩容linux系统盘,Extending Partitions and File Systems for System Disks (Linux),E", + "kw":"Extending Partitions and File Systems for System Disks (Linux),Extending Disk Partitions and File Sy", "title":"Extending Partitions and File Systems for System Disks (Linux)", "githuburl":"" }, @@ -375,7 +375,7 @@ "code":"38", "des":"After a disk has been expanded on the management console, the disk size is enlarged, but the additional space cannot be used directly.In Linux, you must allocate the addi", "doc_type":"usermanual", - "kw":"扩容云硬盘,扩容磁盘,磁盘空间不足,磁盘容量不足,扩容linux数据盘,Extending Partitions and File Systems for Data Disks (Linux),Ext", + "kw":"Extending Partitions and File Systems for Data Disks (Linux),Extending Disk Partitions and File Syst", "title":"Extending Partitions and File Systems for Data Disks (Linux)", "githuburl":"" }, @@ -385,7 +385,7 @@ "code":"39", "des":"After a disk has been expanded on the management console, the disk size is enlarged, but the additional space cannot be used directly.In Linux, you must allocate the addi", "doc_type":"usermanual", - "kw":"扩容云硬盘,扩容磁盘,磁盘空间不足,磁盘容量不足,扩容SCSI磁盘,扩容SCSI数据盘,扩容SCSI云硬盘,扩容linux数据盘,Extending Partitions and File Syste", + "kw":"Extending Partitions and File Systems for SCSI Disks (Linux),Extending Disk Partitions and File Syst", "title":"Extending Partitions and File Systems for SCSI Disks (Linux)", "githuburl":"" }, @@ -395,7 +395,7 @@ "code":"40", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", - "kw":"卸载磁盘", + "kw":"Detaching an EVS Disk", "title":"Detaching an EVS Disk", "githuburl":"" }, @@ -405,7 +405,7 @@ "code":"41", "des":"A system disk can only be detached offline, that is, its server must be in the Stopped state before the system disk is detached. Therefore, you need to first stop the ser", "doc_type":"usermanual", - "kw":"卸载磁盘,离线卸载,Detaching a System Disk,Detaching an EVS Disk,User Guide", + "kw":"Detaching a System Disk,Detaching an EVS Disk,User Guide", "title":"Detaching a System Disk", "githuburl":"" }, @@ -415,7 +415,7 @@ "code":"42", "des":"Data disks can be detached online or offline, which means that the server containing the to-be-detached data disk can either be in the Running or Stopped state.ECSDetach ", "doc_type":"usermanual", - "kw":"卸载磁盘,在线卸载,离线卸载,Detaching a Data Disk,Detaching an EVS Disk,User Guide", + "kw":"Detaching a Data Disk,Detaching an EVS Disk,User Guide", "title":"Detaching a Data Disk", "githuburl":"" }, @@ -425,18 +425,18 @@ "code":"43", "des":"If an EVS disk is no longer used, you can release the virtual resources by deleting the disk from the system.Before deleting a disk, ensure that the disk status is Availa", "doc_type":"usermanual", - "kw":"删除磁盘,Deleting an EVS Disk,User Guide", - "title":"Deleting an EVS Disk", + "kw":"Deleting EVS Disks,User Guide", + "title":"Deleting EVS Disks", "githuburl":"" }, { "uri":"evs_01_0009.html", "product_code":"evs", "code":"44", - "des":"The encryption function can be used to encrypt system disks, data disks, backups and snapshots. The details are as follows:System disk encryption relates to the image tha", + "des":"The encryption function can be used to encrypt system disks, data disks, backups and snapshots. The details are as follows:System disk encryption relies on the image that", "doc_type":"usermanual", - "kw":"Managing an Encrypted EVS Disk,User Guide", - "title":"Managing an Encrypted EVS Disk", + "kw":"Managing Encrypted EVS Disks,User Guide", + "title":"Managing Encrypted EVS Disks", "githuburl":"" }, { @@ -445,18 +445,18 @@ "code":"45", "des":"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.S", "doc_type":"usermanual", - "kw":"Managing a Shared EVS Disk,User Guide", - "title":"Managing a Shared EVS Disk", + "kw":"Managing Shared EVS Disks,User Guide", + "title":"Managing Shared EVS Disks", "githuburl":"" }, { "uri":"evs_01_0110.html", "product_code":"evs", "code":"46", - "des":"EVS disk backups are created using the CBR service. For details, see Creating a Disk Backup Vault in the Cloud Backup and Recovery User Guide.This section describes how t", + "des":"EVS backups are created using the CBR service. For details, see Creating a Cloud Disk Backup in the Cloud Backup and Recovery User Guide.This section describes how to con", "doc_type":"usermanual", - "kw":"Managing EVS Backup,User Guide", - "title":"Managing EVS Backup", + "kw":"Managing EVS Backups,User Guide", + "title":"Managing EVS Backups", "githuburl":"" }, { @@ -465,8 +465,8 @@ "code":"47", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", - "kw":"Managing Snapshots", - "title":"Managing Snapshots", + "kw":"Managing EVS Snapshots", + "title":"Managing EVS Snapshots", "githuburl":"" }, { @@ -475,7 +475,7 @@ "code":"48", "des":"EVS allows you to create snapshots for disks on the management console or by making API calls. An EVS snapshot is a complete copy or image of the disk data at a specific ", "doc_type":"usermanual", - "kw":"Snapshot Overview,Managing Snapshots,User Guide", + "kw":"Snapshot Overview,Managing EVS Snapshots,User Guide", "title":"Snapshot Overview", "githuburl":"" }, @@ -485,7 +485,7 @@ "code":"49", "des":"You can create an EVS snapshot on the management console to save the EVS disk data at a specific time point.A maximum of 7 snapshots can be created for one disk.Snapshots", "doc_type":"usermanual", - "kw":"Creating a Snapshot,Managing Snapshots,User Guide", + "kw":"Creating a Snapshot,Managing EVS Snapshots,User Guide", "title":"Creating a Snapshot", "githuburl":"" }, @@ -495,7 +495,7 @@ "code":"50", "des":"If a snapshot is no longer needed, you can delete the snapshot to release the virtual resources. Snapshot deletion has the following constraints:The snapshot status must ", "doc_type":"usermanual", - "kw":"Deleting a Snapshot,Managing Snapshots,User Guide", + "kw":"Deleting a Snapshot,Managing EVS Snapshots,User Guide", "title":"Deleting a Snapshot", "githuburl":"" }, @@ -505,7 +505,7 @@ "code":"51", "des":"If the data on an EVS disk is incorrect or damaged, you can roll back the data from a snapshot to the source disk to restore data. Snapshot rollback has the following con", "doc_type":"usermanual", - "kw":"Rolling Back Data from a Snapshot,Managing Snapshots,User Guide", + "kw":"Rolling Back Data from a Snapshot,Managing EVS Snapshots,User Guide", "title":"Rolling Back Data from a Snapshot", "githuburl":"" }, @@ -515,7 +515,7 @@ "code":"52", "des":"This section describes how to create an EVS disk on the Snapshots page. Besides, you can also create an EVS disk from a snapshot by specifying the Create from snapshot pa", "doc_type":"usermanual", - "kw":"Creating an EVS Disk from a Snapshot,Managing Snapshots,User Guide", + "kw":"Creating an EVS Disk from a Snapshot,Managing EVS Snapshots,User Guide", "title":"Creating an EVS Disk from a Snapshot", "githuburl":"" }, @@ -643,10 +643,10 @@ "uri":"evs_01_0042.html", "product_code":"evs", "code":"65", - "des":"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 acc", + "des":"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 ", "doc_type":"usermanual", - "kw":"Managing EVS Disk Transfer,User Guide", - "title":"Managing EVS Disk Transfer", + "kw":"Managing EVS Transfers,User Guide", + "title":"Managing EVS Transfers", "githuburl":"" }, { @@ -673,7 +673,7 @@ "uri":"evs_01_0014.html", "product_code":"evs", "code":"68", - "des":"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 Create an EVS Disk.Tags ar", + "des":"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 Create an EVS Disk.Tags are us", "doc_type":"usermanual", "kw":"Adding a Tag,Managing a Tag,User Guide", "title":"Adding a Tag", @@ -713,16 +713,26 @@ "uri":"evs_01_0044.html", "product_code":"evs", "code":"72", - "des":"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 que", + "des":"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", "doc_type":"usermanual", "kw":"Viewing EVS Monitoring Data,User Guide", "title":"Viewing EVS Monitoring Data", "githuburl":"" }, { - "uri":"evs_faq_0001.html", + "uri":"evs_01_0046.html", "product_code":"evs", "code":"73", + "des":"EVS supports the recording of EVS operations through CTS. You can query EVS traces and use them for historical operation audits and backtracks.CTS has been enabled.To vie", + "doc_type":"usermanual", + "kw":"Auditing,User Guide", + "title":"Auditing", + "githuburl":"" + }, + { + "uri":"evs_faq_0001.html", + "product_code":"evs", + "code":"74", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"FAQ", @@ -732,27 +742,57 @@ { "uri":"evs_01_0081.html", "product_code":"evs", - "code":"74", + "code":"75", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"General", "title":"General", "githuburl":"" }, + { + "uri":"evs_faq_0033.html", + "product_code":"evs", + "code":"76", + "des":"A newly purchased disk must be attached to a server and then initialized in the server operating system before you can use it.", + "doc_type":"usermanual", + "kw":"How Do I Start Using a Newly Purchased Disk?,General,User Guide", + "title":"How Do I Start Using a Newly Purchased Disk?", + "githuburl":"" + }, + { + "uri":"evs_faq_0065.html", + "product_code":"evs", + "code":"77", + "des":"No.EVS disks must be attached to cloud servers before use. You cannot use EVS disks alone to store data.", + "doc_type":"usermanual", + "kw":"Can EVS Disks Be Used Directly for Storage?,General,User Guide", + "title":"Can EVS Disks Be Used Directly for Storage?", + "githuburl":"" + }, { "uri":"evs_faq_0054.html", "product_code":"evs", - "code":"75", + "code":"78", "des":"No.EVS disks must be attached to servers before you can use them.", "doc_type":"usermanual", "kw":"Can EVS Disks Be Used Alone?,General,User Guide", "title":"Can EVS Disks Be Used Alone?", "githuburl":"" }, + { + "uri":"evs_faq_0066.html", + "product_code":"evs", + "code":"79", + "des":"To do so, perform the following operations:The disk list page is displayed.View more information on the Summary tab.", + "doc_type":"usermanual", + "kw":"How Can I View My Disk Details?,General,User Guide", + "title":"How Can I View My Disk Details?", + "githuburl":"" + }, { "uri":"evs_faq_0048.html", "product_code":"evs", - "code":"76", + "code":"80", "des":"No.The AZ of a disk cannot be changed after you have created the disk. If you want to change the AZ, delete the disk and create a new one.", "doc_type":"usermanual", "kw":"Can I Change the AZ of My Disk?,General,User Guide", @@ -762,7 +802,7 @@ { "uri":"evs_faq_0014.html", "product_code":"evs", - "code":"77", + "code":"81", "des":"If an error occurs, the disk may show one of the states listed in the following table. Take the measures described in the table to handle the exceptions.", "doc_type":"usermanual", "kw":"What Should I Do If an Error Occurs on My EVS Disk?,General,User Guide", @@ -772,7 +812,7 @@ { "uri":"evs_faq_0021.html", "product_code":"evs", - "code":"78", + "code":"82", "des":"EVS disks have two device types: VBD and SCSI. WWNs are used as the unique identifiers for SCSI EVS disks, and VBD EVS disks do not have WWNs.You can view the WWN of a SC", "doc_type":"usermanual", "kw":"Why Do Some of My EVS Disks Not Have WWN Information?,General,User Guide", @@ -782,17 +822,57 @@ { "uri":"evs_faq_0020.html", "product_code":"evs", - "code":"79", + "code":"83", "des":"If the system displays a message indicating insufficient quota during an EVS replication pair creation or a replication consistency group creation or update, contact the ", "doc_type":"usermanual", "kw":"What Should I Do If My EVS Replication Quotas Are Insufficient? (Deprecated),General,User Guide", "title":"What Should I Do If My EVS Replication Quotas Are Insufficient? (Deprecated)", "githuburl":"" }, + { + "uri":"evs_faq_0084.html", + "product_code":"evs", + "code":"84", + "des":"A system disk runs the server operating system. It is like drive C in a PC.When a server is created, a system disk is automatically created and attached. You cannot creat", + "doc_type":"usermanual", + "kw":"What Are the Differences Between System Disks and Data Disks?,General,User Guide", + "title":"What Are the Differences Between System Disks and Data Disks?", + "githuburl":"" + }, + { + "uri":"evs_faq_0087.html", + "product_code":"evs", + "code":"85", + "des":"EVS disk data cannot be directly saved to a local PC. It is recommended that you use a third-party tool, such as FTP, to download the data.", + "doc_type":"usermanual", + "kw":"How Can I Download My EVS Disk Data to a Local PC?,General,User Guide", + "title":"How Can I Download My EVS Disk Data to a Local PC?", + "githuburl":"" + }, + { + "uri":"evs_faq_0091.html", + "product_code":"evs", + "code":"86", + "des":"Solution:Install the ntfsprogs software to enable Linux to access the NTFS file system.yum install ntfsprogsyum install ntfsprogsView the data disks previously attached t", + "doc_type":"usermanual", + "kw":"How Can I Export the Original Data After I Changed My Server OS from Windows to CentOS?,General,User", + "title":"How Can I Export the Original Data After I Changed My Server OS from Windows to CentOS?", + "githuburl":"" + }, + { + "uri":"evs_faq_0092.html", + "product_code":"evs", + "code":"87", + "des":"Table 1 lists the common disk partition styles. In Linux, different partition styles require different partitioning tools.The maximum disk size supported by MBR is 2 TiB,", + "doc_type":"usermanual", + "kw":"What Are the Differences Between MBR and GPT Partition Styles?,General,User Guide", + "title":"What Are the Differences Between MBR and GPT Partition Styles?", + "githuburl":"" + }, { "uri":"evs_01_0077.html", "product_code":"evs", - "code":"80", + "code":"88", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Capacity Expansion", @@ -802,17 +882,37 @@ { "uri":"evs_faq_0026.html", "product_code":"evs", - "code":"81", + "code":"89", "des":"No. The disk capacity can only be expanded, and temporary capacity expansion is not supported.", "doc_type":"usermanual", "kw":"Can I Reduce or Temporarily Expand the Disk Capacity?,Capacity Expansion,User Guide", "title":"Can I Reduce or Temporarily Expand the Disk Capacity?", "githuburl":"" }, + { + "uri":"evs_faq_0075.html", + "product_code":"evs", + "code":"90", + "des":"The differences are as follows:Expanding an EVS disk is when you expand the capacity of an existing EVS disk. Some systems let you expand the capacity of EVS disks in use", + "doc_type":"usermanual", + "kw":"What Are the Differences Between Expanding Capacity by Expanding an EVS Disk and Creating a New EVS ", + "title":"What Are the Differences Between Expanding Capacity by Expanding an EVS Disk and Creating a New EVS Disk?", + "githuburl":"" + }, + { + "uri":"evs_faq_0044.html", + "product_code":"evs", + "code":"91", + "des":"Data will not be deleted during a system disk or data disk capacity expansion. However, misoperations during an expansion may result in data loss or exceptions. Exercise ", + "doc_type":"usermanual", + "kw":"Will My Disk Data Be Lost After I Expand the Disk Capacity?,Capacity Expansion,User Guide", + "title":"Will My Disk Data Be Lost After I Expand the Disk Capacity?", + "githuburl":"" + }, { "uri":"evs_faq_0042.html", "product_code":"evs", - "code":"82", + "code":"92", "des":"An EVS disk can be expanded either in the Available or In-use state. Expanding the disk capacity on the management console enlarges the disk capacity, but you still need ", "doc_type":"usermanual", "kw":"Do I Need to Restart the Server After Expanding the Disk Capacity?,Capacity Expansion,User Guide", @@ -822,7 +922,7 @@ { "uri":"evs_faq_0028.html", "product_code":"evs", - "code":"83", + "code":"93", "des":"An expansion consists of two phases:Expand the disk capacity on the management console.A shared, in-use disk cannot be expanded. You must detach the shared disk from all ", "doc_type":"usermanual", "kw":"Do I Need to Detach an EVS Disk Before Expanding Its Capacity?,Capacity Expansion,User Guide", @@ -832,37 +932,57 @@ { "uri":"evs_faq_0024.html", "product_code":"evs", - "code":"84", - "des":"An EVS system disk can be as large as 1 TB (1024 GB). You can expand the capacity of a system disk to up to 1 TB.An EVS data disk can be as large as 32 TB (32768 GB).With", + "code":"94", + "des":"An EVS system disk can be as large as 1 TiB (1,024 GiB). You can expand the capacity of a system disk to up to 1 TiB.An EVS data disk can be as large as 32 TiB (32,768 Gi", "doc_type":"usermanual", - "kw":"What Should I Do If My Disk Capacity Exceeds 2 TB After Expansion?,Capacity Expansion,User Guide", - "title":"What Should I Do If My Disk Capacity Exceeds 2 TB After Expansion?", + "kw":"What Should I Do If My Disk Capacity Exceeds 2 TiB After Expansion?,Capacity Expansion,User Guide", + "title":"What Should I Do If My Disk Capacity Exceeds 2 TiB After Expansion?", "githuburl":"" }, { "uri":"evs_faq_0027.html", "product_code":"evs", - "code":"85", + "code":"95", "des":"After expanding disk capacity on the management console, you must log in to the server and extend the disk partition and file system for the extra capacity to become avai", "doc_type":"usermanual", "kw":"Why Did My Disk Capacity Remain Unchanged on the Server After Capacity Expansion?,Capacity Expansion", "title":"Why Did My Disk Capacity Remain Unchanged on the Server After Capacity Expansion?", "githuburl":"" }, + { + "uri":"evs_faq_0073.html", + "product_code":"evs", + "code":"96", + "des":"If no partition but only a file system is created on a data disk, extend the file system according to the following operations:Run the lsblk command. Information similar ", + "doc_type":"usermanual", + "kw":"How Do I Extend the File System of an Unpartitioned Data Disk in Linux?,Capacity Expansion,User Guid", + "title":"How Do I Extend the File System of an Unpartitioned Data Disk in Linux?", + "githuburl":"" + }, { "uri":"evs_01_0078.html", "product_code":"evs", - "code":"86", + "code":"97", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Attachment", "title":"Attachment", "githuburl":"" }, + { + "uri":"evs_faq_0022.html", + "product_code":"evs", + "code":"98", + "des":"Symptom: A data disk has been attached to a Linux server on the management console, but the disk cannot be viewed on the server.Run df -TH to view the disk information. C", + "doc_type":"usermanual", + "kw":"Why Can't I View the Attached Data Disk on the Server?,Attachment,User Guide", + "title":"Why Can't I View the Attached Data Disk on the Server?", + "githuburl":"" + }, { "uri":"evs_faq_0006.html", "product_code":"evs", - "code":"87", + "code":"99", "des":"A non-shared disk can only be attached to one server.A shared disk can be attached to up to 16 servers. Shared disks are a type of EVS disks that can be attached to multi", "doc_type":"usermanual", "kw":"Can I Attach a Disk to Multiple Servers?,Attachment,User Guide", @@ -872,37 +992,47 @@ { "uri":"evs_faq_0036.html", "product_code":"evs", - "code":"88", + "code":"100", "des":"No.Disks and the servers you attach the disks to must be in the same AZ. The same is true for shared disks. Shared disks can only be attached to the servers in the same A", "doc_type":"usermanual", "kw":"Can I Attach a Disk to a Server in Another AZ?,Attachment,User Guide", "title":"Can I Attach a Disk to a Server in Another AZ?", "githuburl":"" }, - { - "uri":"evs_faq_0022.html", - "product_code":"evs", - "code":"89", - "des":"Symptom: A data disk has been attached to a Windows server on the management console, but the disk cannot be viewed on the server. For example, Volume (D:) was not shown ", - "doc_type":"usermanual", - "kw":"Why Can't I View the Attached Data Disk on the Server?,Attachment,User Guide", - "title":"Why Can't I View the Attached Data Disk on the Server?", - "githuburl":"" - }, { "uri":"evs_faq_0043.html", "product_code":"evs", - "code":"90", + "code":"101", "des":"Data disks can be created during or after the server creation. If you create data disks during the server creation, the system will automatically attach the data disks to", "doc_type":"usermanual", "kw":"How Can I Add a Data Disk to an Existing Server?,Attachment,User Guide", "title":"How Can I Add a Data Disk to an Existing Server?", "githuburl":"" }, + { + "uri":"evs_faq_0055.html", + "product_code":"evs", + "code":"102", + "des":"Yes. Different types of EVS disks can be attached to the same server. You only need to make sure that these disks and the server are in the same AZ.", + "doc_type":"usermanual", + "kw":"Can I Attach Different Types of Disks to the Same Server?,Attachment,User Guide", + "title":"Can I Attach Different Types of Disks to the Same Server?", + "githuburl":"" + }, + { + "uri":"evs_faq_0076.html", + "product_code":"evs", + "code":"103", + "des":"You are not advised to attach a Linux EVS disk to a Windows server or attach a Windows EVS disk to a Linux server.The disk information may fail to be displayed due to the", + "doc_type":"usermanual", + "kw":"What Should I Do If a Linux EVS Disk Is Attached to a Windows Server?,Attachment,User Guide", + "title":"What Should I Do If a Linux EVS Disk Is Attached to a Windows Server?", + "githuburl":"" + }, { "uri":"evs_01_0079.html", "product_code":"evs", - "code":"91", + "code":"104", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Detachment", @@ -912,17 +1042,17 @@ { "uri":"evs_faq_0012.html", "product_code":"evs", - "code":"92", + "code":"105", "des":"It depends on if the disk is encrypted or not.EncryptedCMK is disabled or scheduled for deletion.Before you detach an EVS disk encrypted by a CMK, check whether the CMK i", "doc_type":"usermanual", - "kw":"If I Detach a Disk Will I Lose the Data on My Disk?,Detachment,User Guide", - "title":"If I Detach a Disk Will I Lose the Data on My Disk?", + "kw":"If I Detach a Disk, Will I Lose the Data on My Disk?,Detachment,User Guide", + "title":"If I Detach a Disk, Will I Lose the Data on My Disk?", "githuburl":"" }, { "uri":"evs_faq_0056.html", "product_code":"evs", - "code":"93", + "code":"106", "des":"EVS disks can be used as system disks or data disks, but the way you detach each one is different.System disks: A system disk can only be detached offline. You must first", "doc_type":"usermanual", "kw":"Why Can't I Detach My Disk?,Detachment,User Guide", @@ -932,7 +1062,7 @@ { "uri":"evs_01_0082.html", "product_code":"evs", - "code":"94", + "code":"107", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Capacity", @@ -942,8 +1072,8 @@ { "uri":"evs_faq_0031.html", "product_code":"evs", - "code":"95", - "des":"The maximum capacity supported for a system disk is 1024 GB.The maximum capacity supported for a data disk is 32768 GB.", + "code":"108", + "des":"The maximum capacity supported for a system disk is 1024 GiB.The maximum capacity supported for a data disk is 32768 GiB.", "doc_type":"usermanual", "kw":"What Is the Maximum Capacity Supported for the System and Data Disks?,Capacity,User Guide", "title":"What Is the Maximum Capacity Supported for the System and Data Disks?", @@ -952,7 +1082,7 @@ { "uri":"evs_faq_0032.html", "product_code":"evs", - "code":"96", + "code":"109", "des":"If your disk space starts to fill up, you can:Create a new disk and attach it to the server.Expand the capacity of the existing disk. Both system disks and data disks can", "doc_type":"usermanual", "kw":"What Should I Do If My Disk Starts to Run Out of Space?,Capacity,User Guide", @@ -962,7 +1092,7 @@ { "uri":"evs_faq_0035.html", "product_code":"evs", - "code":"97", + "code":"110", "des":"If your disk capacity is greater than 2 TB, do not use fdisk to partition the disk. Or any space in excess of 2 TB will be unable to be displayed after the disk is partit", "doc_type":"usermanual", "kw":"What Should I Do If I Use fdisk to Initialize a Disk Larger Than 2 TB and Then the Space in Excess o", @@ -972,8 +1102,8 @@ { "uri":"evs_faq_0053.html", "product_code":"evs", - "code":"98", - "des":"You can view your disk usages in either of the following ways:Install Agent to View Disk UsageView disk usages manually.The details depend on the OS. This FAQ uses Window", + "code":"111", + "des":"You can view your disk usages in either of the following ways:View disk usages manually.The details depend on the OS. This FAQ uses Windows Server 2008, Windows Server 20", "doc_type":"usermanual", "kw":"How Can I View My Disk Usage?,Capacity,User Guide", "title":"How Can I View My Disk Usage?", @@ -982,7 +1112,7 @@ { "uri":"evs_01_0084.html", "product_code":"evs", - "code":"99", + "code":"112", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Sharing", @@ -992,8 +1122,8 @@ { "uri":"evs_faq_0039.html", "product_code":"evs", - "code":"100", - "des":"Yes.If you simply attach a shared disk to multiple servers, files cannot be shared between the servers. If the rules for reading and writing data are not mutually agreed ", + "code":"113", + "des":"Yes.If you simply attach a shared disk to multiple servers, files cannot be shared among them. Because there are no mutually agreed data read/write rules among servers, r", "doc_type":"usermanual", "kw":"Do I Have to Deploy a Cluster to Use Shared Disks?,Sharing,User Guide", "title":"Do I Have to Deploy a Cluster to Use Shared Disks?", @@ -1002,17 +1132,47 @@ { "uri":"evs_faq_0037.html", "product_code":"evs", - "code":"101", + "code":"114", "des":"A shared disk can be attached to up to 16 servers.", "doc_type":"usermanual", "kw":"How Many Servers Can I Attach a Shared Disk to?,Sharing,User Guide", "title":"How Many Servers Can I Attach a Shared Disk to?", "githuburl":"" }, + { + "uri":"evs_faq_0038.html", + "product_code":"evs", + "code":"115", + "des":"A shared disk can be attached to multiple servers on the management console. You can choose to attach it to servers one by one or in a batch.", + "doc_type":"usermanual", + "kw":"How Can I Attach a Shared Disk to Multiple Servers?,Sharing,User Guide", + "title":"How Can I Attach a Shared Disk to Multiple Servers?", + "githuburl":"" + }, + { + "uri":"evs_faq_0068.html", + "product_code":"evs", + "code":"116", + "des":"No. A Shared disk can only be attached to servers that belong to the same account and are in the same AZ.", + "doc_type":"usermanual", + "kw":"Can a Shared Disk Be Attached to Servers That Belong to Different Accounts?,Sharing,User Guide", + "title":"Can a Shared Disk Be Attached to Servers That Belong to Different Accounts?", + "githuburl":"" + }, + { + "uri":"evs_faq_0083.html", + "product_code":"evs", + "code":"117", + "des":"It is recommended that you do not simultaneously attach a shared disk to servers running Linux and Windows.If a shared disk is attached to servers running different versi", + "doc_type":"usermanual", + "kw":"Can I Attach a Shared Disk to Servers Running Different OSs?,Sharing,User Guide", + "title":"Can I Attach a Shared Disk to Servers Running Different OSs?", + "githuburl":"" + }, { "uri":"evs_01_0039.html", "product_code":"evs", - "code":"102", + "code":"118", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Appendix", @@ -1022,7 +1182,7 @@ { "uri":"evs_01_0040.html", "product_code":"evs", - "code":"103", + "code":"119", "des":"An EVS disk has several statuses. Table 1 lists the EVS disk statuses, the meaning of each status, and the operations a disk in each status allows.Disk status detailsEVS ", "doc_type":"usermanual", "kw":"EVS Disk Status,Appendix,User Guide", @@ -1032,7 +1192,7 @@ { "uri":"evs_01_0041.html", "product_code":"evs", - "code":"104", + "code":"120", "des":"An EVS snapshot has several statuses. Table 1 lists the EVS snapshot statuses, the meaning of each status, and the operations a snapshot in each status allows.Snapshot st", "doc_type":"usermanual", "kw":"EVS Snapshot Status,Appendix,User Guide", @@ -1042,7 +1202,7 @@ { "uri":"evs_01_0114.html", "product_code":"evs", - "code":"105", + "code":"121", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Change History,User Guide", @@ -1052,7 +1212,7 @@ { "uri":"evs_01_0115.html", "product_code":"evs", - "code":"106", + "code":"122", "des":"For details about the terms involved in this document, see Glossary.", "doc_type":"usermanual", "kw":"Glossary,User Guide", diff --git a/docs/evs/umn/CLASS.TXT.json b/docs/evs/umn/CLASS.TXT.json index a6c7a539..caeb3659 100644 --- a/docs/evs/umn/CLASS.TXT.json +++ b/docs/evs/umn/CLASS.TXT.json @@ -9,7 +9,7 @@ "code":"1" }, { - "desc":"Elastic Volume Service (EVS) offers scalable block storage for cloud servers. With high reliability, high performance, and rich specifications, EVS disks can be used for ", + "desc":"Elastic Volume Service (EVS) offers scalable block storage for cloud servers. With high reliability, high performance, and a variety of specifications, EVS disks can be u", "product_code":"evs", "title":"What Is EVS?", "uri":"en-us_topic_0014580741.html", @@ -47,7 +47,7 @@ { "desc":"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.EVS uses", "product_code":"evs", - "title":"EVS Disk Encryption", + "title":"EVS Encryption", "uri":"evs_01_0001.html", "doc_type":"usermanual", "p_code":"1", @@ -72,9 +72,9 @@ "code":"8" }, { - "desc":"Both EVS disk backup and EVS snapshot provide redundancies for the EVS disk data to improve reliability. Table 1 lists the differences between them.", + "desc":"Both EVS backups and EVS snapshots provide redundancies for improved disk data reliability. Table 1 lists the differences between them.", "product_code":"evs", - "title":"Differences Between EVS Disk Backup and EVS Snapshot", + "title":"Differences Between EVS Backups and EVS Snapshots", "uri":"evs_01_0048.html", "doc_type":"usermanual", "p_code":"1", @@ -144,7 +144,7 @@ "code":"16" }, { - "desc":"EVS disks can be used as system disks or data disks for servers.When a server is created, a system disk is automatically created and attached. You cannot create a system ", + "desc":"EVS disks can be used as system disks or data disks for servers.System disks can only be created together with servers and are automatically attached.A system disk can ha", "product_code":"evs", "title":"Create an EVS Disk", "uri":"en-us_topic_0021738346.html", @@ -207,16 +207,16 @@ "code":"23" }, { - "desc":"This section uses Windows Server 2016 Standard 64bit to describe how to initialize a data disk attached to a server running Windows.The maximum disk capacity supported by", + "desc":"This section uses Windows Server 2019 Standard 64bit to describe how to initialize a data disk attached to a server running Windows.The maximum disk capacity supported by", "product_code":"evs", - "title":"Initializing a Windows Data Disk (Windows Server 2016)", + "title":"Initializing a Windows Data Disk (Windows Server 2019)", "uri":"evs_01_0045.html", "doc_type":"usermanual", "p_code":"21", "code":"24" }, { - "desc":"This section uses CentOS 7.4 64bit to describe how to initialize a data disk attached to a server running Linux and use fdisk to partition the data disk.The maximum disk ", + "desc":"This section uses CentOS 7.4 64bit to describe how to initialize a data disk attached to a server running Linux and use fdisk to partition the data disk.The maximum parti", "product_code":"evs", "title":"Initializing a Linux Data Disk (fdisk)", "uri":"evs_01_0033.html", @@ -225,7 +225,7 @@ "code":"25" }, { - "desc":"This section uses CentOS 7.4 64bit to describe how to initialize a data disk attached to a server running Linux and use parted to partition the data disk.The maximum disk", + "desc":"This section uses CentOS 7.4 64bit to describe how to initialize a data disk attached to a server running Linux and use parted to partition the data disk.The maximum part", "product_code":"evs", "title":"Initializing a Linux Data Disk (parted)", "uri":"evs_01_0034.html", @@ -270,7 +270,7 @@ "code":"30" }, { - "desc":"If the capacity of an existing disk is insufficient, you can expand the disk capacity to increase the storage space.Both system disks and data disks can be expanded. Curr", + "desc":"If the capacity of an existing disk is insufficient, you can expand the disk capacity to increase the storage space.Both system disks and data disks can be expanded. Disk", "product_code":"evs", "title":"Expansion Overview", "uri":"evs_01_0006.html", @@ -380,16 +380,16 @@ { "desc":"If an EVS disk is no longer used, you can release the virtual resources by deleting the disk from the system.Before deleting a disk, ensure that the disk status is Availa", "product_code":"evs", - "title":"Deleting an EVS Disk", + "title":"Deleting EVS Disks", "uri":"evs_01_0005.html", "doc_type":"usermanual", "p_code":"", "code":"43" }, { - "desc":"The encryption function can be used to encrypt system disks, data disks, backups and snapshots. The details are as follows:System disk encryption relates to the image tha", + "desc":"The encryption function can be used to encrypt system disks, data disks, backups and snapshots. The details are as follows:System disk encryption relies on the image that", "product_code":"evs", - "title":"Managing an Encrypted EVS Disk", + "title":"Managing Encrypted EVS Disks", "uri":"evs_01_0009.html", "doc_type":"usermanual", "p_code":"", @@ -398,16 +398,16 @@ { "desc":"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.S", "product_code":"evs", - "title":"Managing a Shared EVS Disk", + "title":"Managing Shared EVS Disks", "uri":"evs_01_0010.html", "doc_type":"usermanual", "p_code":"", "code":"45" }, { - "desc":"EVS disk backups are created using the CBR service. For details, see Creating a Disk Backup Vault in the Cloud Backup and Recovery User Guide.This section describes how t", + "desc":"EVS backups are created using the CBR service. For details, see Creating a Cloud Disk Backup in the Cloud Backup and Recovery User Guide.This section describes how to con", "product_code":"evs", - "title":"Managing EVS Backup", + "title":"Managing EVS Backups", "uri":"evs_01_0110.html", "doc_type":"usermanual", "p_code":"", @@ -416,7 +416,7 @@ { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "product_code":"evs", - "title":"Managing Snapshots", + "title":"Managing EVS Snapshots", "uri":"evs_01_0111.html", "doc_type":"usermanual", "p_code":"", @@ -576,9 +576,9 @@ "code":"64" }, { - "desc":"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 acc", + "desc":"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 ", "product_code":"evs", - "title":"Managing EVS Disk Transfer", + "title":"Managing EVS Transfers", "uri":"evs_01_0042.html", "doc_type":"usermanual", "p_code":"", @@ -603,7 +603,7 @@ "code":"67" }, { - "desc":"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 Create an EVS Disk.Tags ar", + "desc":"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 Create an EVS Disk.Tags are us", "product_code":"evs", "title":"Adding a Tag", "uri":"evs_01_0014.html", @@ -639,7 +639,7 @@ "code":"71" }, { - "desc":"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 que", + "desc":"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", "product_code":"evs", "title":"Viewing EVS Monitoring Data", "uri":"evs_01_0044.html", @@ -648,22 +648,49 @@ "code":"72" }, { - "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "desc":"EVS supports the recording of EVS operations through CTS. You can query EVS traces and use them for historical operation audits and backtracks.CTS has been enabled.To vie", "product_code":"evs", - "title":"FAQ", - "uri":"evs_faq_0001.html", + "title":"Auditing", + "uri":"evs_01_0046.html", "doc_type":"usermanual", "p_code":"", "code":"73" }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"evs", + "title":"FAQ", + "uri":"evs_faq_0001.html", + "doc_type":"usermanual", + "p_code":"", + "code":"74" + }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "product_code":"evs", "title":"General", "uri":"evs_01_0081.html", "doc_type":"usermanual", - "p_code":"73", - "code":"74" + "p_code":"74", + "code":"75" + }, + { + "desc":"A newly purchased disk must be attached to a server and then initialized in the server operating system before you can use it.", + "product_code":"evs", + "title":"How Do I Start Using a Newly Purchased Disk?", + "uri":"evs_faq_0033.html", + "doc_type":"usermanual", + "p_code":"75", + "code":"76" + }, + { + "desc":"No.EVS disks must be attached to cloud servers before use. You cannot use EVS disks alone to store data.", + "product_code":"evs", + "title":"Can EVS Disks Be Used Directly for Storage?", + "uri":"evs_faq_0065.html", + "doc_type":"usermanual", + "p_code":"75", + "code":"77" }, { "desc":"No.EVS disks must be attached to servers before you can use them.", @@ -671,8 +698,17 @@ "title":"Can EVS Disks Be Used Alone?", "uri":"evs_faq_0054.html", "doc_type":"usermanual", - "p_code":"74", - "code":"75" + "p_code":"75", + "code":"78" + }, + { + "desc":"To do so, perform the following operations:The disk list page is displayed.View more information on the Summary tab.", + "product_code":"evs", + "title":"How Can I View My Disk Details?", + "uri":"evs_faq_0066.html", + "doc_type":"usermanual", + "p_code":"75", + "code":"79" }, { "desc":"No.The AZ of a disk cannot be changed after you have created the disk. If you want to change the AZ, delete the disk and create a new one.", @@ -680,8 +716,8 @@ "title":"Can I Change the AZ of My Disk?", "uri":"evs_faq_0048.html", "doc_type":"usermanual", - "p_code":"74", - "code":"76" + "p_code":"75", + "code":"80" }, { "desc":"If an error occurs, the disk may show one of the states listed in the following table. Take the measures described in the table to handle the exceptions.", @@ -689,8 +725,8 @@ "title":"What Should I Do If an Error Occurs on My EVS Disk?", "uri":"evs_faq_0014.html", "doc_type":"usermanual", - "p_code":"74", - "code":"77" + "p_code":"75", + "code":"81" }, { "desc":"EVS disks have two device types: VBD and SCSI. WWNs are used as the unique identifiers for SCSI EVS disks, and VBD EVS disks do not have WWNs.You can view the WWN of a SC", @@ -698,8 +734,8 @@ "title":"Why Do Some of My EVS Disks Not Have WWN Information?", "uri":"evs_faq_0021.html", "doc_type":"usermanual", - "p_code":"74", - "code":"78" + "p_code":"75", + "code":"82" }, { "desc":"If the system displays a message indicating insufficient quota during an EVS replication pair creation or a replication consistency group creation or update, contact the ", @@ -707,8 +743,44 @@ "title":"What Should I Do If My EVS Replication Quotas Are Insufficient? (Deprecated)", "uri":"evs_faq_0020.html", "doc_type":"usermanual", - "p_code":"74", - "code":"79" + "p_code":"75", + "code":"83" + }, + { + "desc":"A system disk runs the server operating system. It is like drive C in a PC.When a server is created, a system disk is automatically created and attached. You cannot creat", + "product_code":"evs", + "title":"What Are the Differences Between System Disks and Data Disks?", + "uri":"evs_faq_0084.html", + "doc_type":"usermanual", + "p_code":"75", + "code":"84" + }, + { + "desc":"EVS disk data cannot be directly saved to a local PC. It is recommended that you use a third-party tool, such as FTP, to download the data.", + "product_code":"evs", + "title":"How Can I Download My EVS Disk Data to a Local PC?", + "uri":"evs_faq_0087.html", + "doc_type":"usermanual", + "p_code":"75", + "code":"85" + }, + { + "desc":"Solution:Install the ntfsprogs software to enable Linux to access the NTFS file system.yum install ntfsprogsyum install ntfsprogsView the data disks previously attached t", + "product_code":"evs", + "title":"How Can I Export the Original Data After I Changed My Server OS from Windows to CentOS?", + "uri":"evs_faq_0091.html", + "doc_type":"usermanual", + "p_code":"75", + "code":"86" + }, + { + "desc":"Table 1 lists the common disk partition styles. In Linux, different partition styles require different partitioning tools.The maximum disk size supported by MBR is 2 TiB,", + "product_code":"evs", + "title":"What Are the Differences Between MBR and GPT Partition Styles?", + "uri":"evs_faq_0092.html", + "doc_type":"usermanual", + "p_code":"75", + "code":"87" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -716,8 +788,8 @@ "title":"Capacity Expansion", "uri":"evs_01_0077.html", "doc_type":"usermanual", - "p_code":"73", - "code":"80" + "p_code":"74", + "code":"88" }, { "desc":"No. The disk capacity can only be expanded, and temporary capacity expansion is not supported.", @@ -725,8 +797,26 @@ "title":"Can I Reduce or Temporarily Expand the Disk Capacity?", "uri":"evs_faq_0026.html", "doc_type":"usermanual", - "p_code":"80", - "code":"81" + "p_code":"88", + "code":"89" + }, + { + "desc":"The differences are as follows:Expanding an EVS disk is when you expand the capacity of an existing EVS disk. Some systems let you expand the capacity of EVS disks in use", + "product_code":"evs", + "title":"What Are the Differences Between Expanding Capacity by Expanding an EVS Disk and Creating a New EVS Disk?", + "uri":"evs_faq_0075.html", + "doc_type":"usermanual", + "p_code":"88", + "code":"90" + }, + { + "desc":"Data will not be deleted during a system disk or data disk capacity expansion. However, misoperations during an expansion may result in data loss or exceptions. Exercise ", + "product_code":"evs", + "title":"Will My Disk Data Be Lost After I Expand the Disk Capacity?", + "uri":"evs_faq_0044.html", + "doc_type":"usermanual", + "p_code":"88", + "code":"91" }, { "desc":"An EVS disk can be expanded either in the Available or In-use state. Expanding the disk capacity on the management console enlarges the disk capacity, but you still need ", @@ -734,8 +824,8 @@ "title":"Do I Need to Restart the Server After Expanding the Disk Capacity?", "uri":"evs_faq_0042.html", "doc_type":"usermanual", - "p_code":"80", - "code":"82" + "p_code":"88", + "code":"92" }, { "desc":"An expansion consists of two phases:Expand the disk capacity on the management console.A shared, in-use disk cannot be expanded. You must detach the shared disk from all ", @@ -743,17 +833,17 @@ "title":"Do I Need to Detach an EVS Disk Before Expanding Its Capacity?", "uri":"evs_faq_0028.html", "doc_type":"usermanual", - "p_code":"80", - "code":"83" + "p_code":"88", + "code":"93" }, { - "desc":"An EVS system disk can be as large as 1 TB (1024 GB). You can expand the capacity of a system disk to up to 1 TB.An EVS data disk can be as large as 32 TB (32768 GB).With", + "desc":"An EVS system disk can be as large as 1 TiB (1,024 GiB). You can expand the capacity of a system disk to up to 1 TiB.An EVS data disk can be as large as 32 TiB (32,768 Gi", "product_code":"evs", - "title":"What Should I Do If My Disk Capacity Exceeds 2 TB After Expansion?", + "title":"What Should I Do If My Disk Capacity Exceeds 2 TiB After Expansion?", "uri":"evs_faq_0024.html", "doc_type":"usermanual", - "p_code":"80", - "code":"84" + "p_code":"88", + "code":"94" }, { "desc":"After expanding disk capacity on the management console, you must log in to the server and extend the disk partition and file system for the extra capacity to become avai", @@ -761,8 +851,17 @@ "title":"Why Did My Disk Capacity Remain Unchanged on the Server After Capacity Expansion?", "uri":"evs_faq_0027.html", "doc_type":"usermanual", - "p_code":"80", - "code":"85" + "p_code":"88", + "code":"95" + }, + { + "desc":"If no partition but only a file system is created on a data disk, extend the file system according to the following operations:Run the lsblk command. Information similar ", + "product_code":"evs", + "title":"How Do I Extend the File System of an Unpartitioned Data Disk in Linux?", + "uri":"evs_faq_0073.html", + "doc_type":"usermanual", + "p_code":"88", + "code":"96" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -770,8 +869,17 @@ "title":"Attachment", "uri":"evs_01_0078.html", "doc_type":"usermanual", - "p_code":"73", - "code":"86" + "p_code":"74", + "code":"97" + }, + { + "desc":"Symptom: A data disk has been attached to a Linux server on the management console, but the disk cannot be viewed on the server.Run df -TH to view the disk information. C", + "product_code":"evs", + "title":"Why Can't I View the Attached Data Disk on the Server?", + "uri":"evs_faq_0022.html", + "doc_type":"usermanual", + "p_code":"97", + "code":"98" }, { "desc":"A non-shared disk can only be attached to one server.A shared disk can be attached to up to 16 servers. Shared disks are a type of EVS disks that can be attached to multi", @@ -779,8 +887,8 @@ "title":"Can I Attach a Disk to Multiple Servers?", "uri":"evs_faq_0006.html", "doc_type":"usermanual", - "p_code":"86", - "code":"87" + "p_code":"97", + "code":"99" }, { "desc":"No.Disks and the servers you attach the disks to must be in the same AZ. The same is true for shared disks. Shared disks can only be attached to the servers in the same A", @@ -788,17 +896,8 @@ "title":"Can I Attach a Disk to a Server in Another AZ?", "uri":"evs_faq_0036.html", "doc_type":"usermanual", - "p_code":"86", - "code":"88" - }, - { - "desc":"Symptom: A data disk has been attached to a Windows server on the management console, but the disk cannot be viewed on the server. For example, Volume (D:) was not shown ", - "product_code":"evs", - "title":"Why Can't I View the Attached Data Disk on the Server?", - "uri":"evs_faq_0022.html", - "doc_type":"usermanual", - "p_code":"86", - "code":"89" + "p_code":"97", + "code":"100" }, { "desc":"Data disks can be created during or after the server creation. If you create data disks during the server creation, the system will automatically attach the data disks to", @@ -806,8 +905,26 @@ "title":"How Can I Add a Data Disk to an Existing Server?", "uri":"evs_faq_0043.html", "doc_type":"usermanual", - "p_code":"86", - "code":"90" + "p_code":"97", + "code":"101" + }, + { + "desc":"Yes. Different types of EVS disks can be attached to the same server. You only need to make sure that these disks and the server are in the same AZ.", + "product_code":"evs", + "title":"Can I Attach Different Types of Disks to the Same Server?", + "uri":"evs_faq_0055.html", + "doc_type":"usermanual", + "p_code":"97", + "code":"102" + }, + { + "desc":"You are not advised to attach a Linux EVS disk to a Windows server or attach a Windows EVS disk to a Linux server.The disk information may fail to be displayed due to the", + "product_code":"evs", + "title":"What Should I Do If a Linux EVS Disk Is Attached to a Windows Server?", + "uri":"evs_faq_0076.html", + "doc_type":"usermanual", + "p_code":"97", + "code":"103" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -815,17 +932,17 @@ "title":"Detachment", "uri":"evs_01_0079.html", "doc_type":"usermanual", - "p_code":"73", - "code":"91" + "p_code":"74", + "code":"104" }, { "desc":"It depends on if the disk is encrypted or not.EncryptedCMK is disabled or scheduled for deletion.Before you detach an EVS disk encrypted by a CMK, check whether the CMK i", "product_code":"evs", - "title":"If I Detach a Disk Will I Lose the Data on My Disk?", + "title":"If I Detach a Disk, Will I Lose the Data on My Disk?", "uri":"evs_faq_0012.html", "doc_type":"usermanual", - "p_code":"91", - "code":"92" + "p_code":"104", + "code":"105" }, { "desc":"EVS disks can be used as system disks or data disks, but the way you detach each one is different.System disks: A system disk can only be detached offline. You must first", @@ -833,8 +950,8 @@ "title":"Why Can't I Detach My Disk?", "uri":"evs_faq_0056.html", "doc_type":"usermanual", - "p_code":"91", - "code":"93" + "p_code":"104", + "code":"106" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -842,17 +959,17 @@ "title":"Capacity", "uri":"evs_01_0082.html", "doc_type":"usermanual", - "p_code":"73", - "code":"94" + "p_code":"74", + "code":"107" }, { - "desc":"The maximum capacity supported for a system disk is 1024 GB.The maximum capacity supported for a data disk is 32768 GB.", + "desc":"The maximum capacity supported for a system disk is 1024 GiB.The maximum capacity supported for a data disk is 32768 GiB.", "product_code":"evs", "title":"What Is the Maximum Capacity Supported for the System and Data Disks?", "uri":"evs_faq_0031.html", "doc_type":"usermanual", - "p_code":"94", - "code":"95" + "p_code":"107", + "code":"108" }, { "desc":"If your disk space starts to fill up, you can:Create a new disk and attach it to the server.Expand the capacity of the existing disk. Both system disks and data disks can", @@ -860,8 +977,8 @@ "title":"What Should I Do If My Disk Starts to Run Out of Space?", "uri":"evs_faq_0032.html", "doc_type":"usermanual", - "p_code":"94", - "code":"96" + "p_code":"107", + "code":"109" }, { "desc":"If your disk capacity is greater than 2 TB, do not use fdisk to partition the disk. Or any space in excess of 2 TB will be unable to be displayed after the disk is partit", @@ -869,17 +986,17 @@ "title":"What Should I Do If I Use fdisk to Initialize a Disk Larger Than 2 TB and Then the Space in Excess of 2 TB Cannot Be Displayed?", "uri":"evs_faq_0035.html", "doc_type":"usermanual", - "p_code":"94", - "code":"97" + "p_code":"107", + "code":"110" }, { - "desc":"You can view your disk usages in either of the following ways:Install Agent to View Disk UsageView disk usages manually.The details depend on the OS. This FAQ uses Window", + "desc":"You can view your disk usages in either of the following ways:View disk usages manually.The details depend on the OS. This FAQ uses Windows Server 2008, Windows Server 20", "product_code":"evs", "title":"How Can I View My Disk Usage?", "uri":"evs_faq_0053.html", "doc_type":"usermanual", - "p_code":"94", - "code":"98" + "p_code":"107", + "code":"111" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -887,17 +1004,17 @@ "title":"Sharing", "uri":"evs_01_0084.html", "doc_type":"usermanual", - "p_code":"73", - "code":"99" + "p_code":"74", + "code":"112" }, { - "desc":"Yes.If you simply attach a shared disk to multiple servers, files cannot be shared between the servers. If the rules for reading and writing data are not mutually agreed ", + "desc":"Yes.If you simply attach a shared disk to multiple servers, files cannot be shared among them. Because there are no mutually agreed data read/write rules among servers, r", "product_code":"evs", "title":"Do I Have to Deploy a Cluster to Use Shared Disks?", "uri":"evs_faq_0039.html", "doc_type":"usermanual", - "p_code":"99", - "code":"100" + "p_code":"112", + "code":"113" }, { "desc":"A shared disk can be attached to up to 16 servers.", @@ -905,8 +1022,35 @@ "title":"How Many Servers Can I Attach a Shared Disk to?", "uri":"evs_faq_0037.html", "doc_type":"usermanual", - "p_code":"99", - "code":"101" + "p_code":"112", + "code":"114" + }, + { + "desc":"A shared disk can be attached to multiple servers on the management console. You can choose to attach it to servers one by one or in a batch.", + "product_code":"evs", + "title":"How Can I Attach a Shared Disk to Multiple Servers?", + "uri":"evs_faq_0038.html", + "doc_type":"usermanual", + "p_code":"112", + "code":"115" + }, + { + "desc":"No. A Shared disk can only be attached to servers that belong to the same account and are in the same AZ.", + "product_code":"evs", + "title":"Can a Shared Disk Be Attached to Servers That Belong to Different Accounts?", + "uri":"evs_faq_0068.html", + "doc_type":"usermanual", + "p_code":"112", + "code":"116" + }, + { + "desc":"It is recommended that you do not simultaneously attach a shared disk to servers running Linux and Windows.If a shared disk is attached to servers running different versi", + "product_code":"evs", + "title":"Can I Attach a Shared Disk to Servers Running Different OSs?", + "uri":"evs_faq_0083.html", + "doc_type":"usermanual", + "p_code":"112", + "code":"117" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -915,7 +1059,7 @@ "uri":"evs_01_0039.html", "doc_type":"usermanual", "p_code":"", - "code":"102" + "code":"118" }, { "desc":"An EVS disk has several statuses. Table 1 lists the EVS disk statuses, the meaning of each status, and the operations a disk in each status allows.Disk status detailsEVS ", @@ -923,8 +1067,8 @@ "title":"EVS Disk Status", "uri":"evs_01_0040.html", "doc_type":"usermanual", - "p_code":"102", - "code":"103" + "p_code":"118", + "code":"119" }, { "desc":"An EVS snapshot has several statuses. Table 1 lists the EVS snapshot statuses, the meaning of each status, and the operations a snapshot in each status allows.Snapshot st", @@ -932,8 +1076,8 @@ "title":"EVS Snapshot Status", "uri":"evs_01_0041.html", "doc_type":"usermanual", - "p_code":"102", - "code":"104" + "p_code":"118", + "code":"120" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -942,7 +1086,7 @@ "uri":"evs_01_0114.html", "doc_type":"usermanual", "p_code":"", - "code":"105" + "code":"121" }, { "desc":"For details about the terms involved in this document, see Glossary.", @@ -951,6 +1095,6 @@ "uri":"evs_01_0115.html", "doc_type":"usermanual", "p_code":"", - "code":"106" + "code":"122" } ] \ No newline at end of file diff --git a/docs/evs/umn/en-us_image_0000001327868762.png b/docs/evs/umn/en-us_image_0000001327868762.png new file mode 100644 index 00000000..434d8d8b Binary files /dev/null and b/docs/evs/umn/en-us_image_0000001327868762.png differ diff --git a/docs/evs/umn/en-us_image_0228748662.png b/docs/evs/umn/en-us_image_0228748662.png index 36e6d323..b57ec44a 100644 Binary files a/docs/evs/umn/en-us_image_0228748662.png and b/docs/evs/umn/en-us_image_0228748662.png differ diff --git a/docs/evs/umn/en-us_image_0238302626.png b/docs/evs/umn/en-us_image_0238302626.png deleted file mode 100644 index 4e7be6a7..00000000 Binary files a/docs/evs/umn/en-us_image_0238302626.png and /dev/null differ diff --git a/docs/evs/umn/en-us_topic_0014580741.html b/docs/evs/umn/en-us_topic_0014580741.html index 9e6c0e03..5d493f1d 100644 --- a/docs/evs/umn/en-us_topic_0014580741.html +++ b/docs/evs/umn/en-us_topic_0014580741.html @@ -1,19 +1,19 @@

What Is EVS?

-

Overview

Elastic Volume Service (EVS) offers scalable block storage for cloud servers. 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).

+

Overview

Elastic Volume Service (EVS) offers scalable block storage for cloud servers. 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).

EVS disks are sometimes just referred to as disks in this document.

Figure 1 EVS architecture

EVS Advantages

EVS has the following advantages:

-
  • Various disk types

    EVS provides various disk types for you to choose from, and EVS disks can be used as data disks and system disks for servers. You may select the disk type based on your budget and service requirements.

    -
  • Elastic scalability

    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.

    +
    • Various disk types

      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 serverss. You can select an appropriate disk type that best suits your budget and service requirements.

      +
    • Elastic scalability

      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.

      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.

    • High security and reliability
      • Both system disks and data disks support data encryption to ensure data security.
      • Data protection functions, such as backups and snapshots, safeguard the disk data, preventing incorrect data caused by application exceptions or attacks.
    • Real-time monitoring

      On Cloud Eye, you can monitor the disk health and operating status at any time.

-

Differences Among EVS, SFS, and OBS

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.

+

Differences Among EVS, SFS, and OBS

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.

@@ -27,29 +27,29 @@ - - - - - - diff --git a/docs/evs/umn/en-us_topic_0014580744.html b/docs/evs/umn/en-us_topic_0014580744.html index f3a44816..46313d41 100644 --- a/docs/evs/umn/en-us_topic_0014580744.html +++ b/docs/evs/umn/en-us_topic_0014580744.html @@ -2,106 +2,120 @@

Disk Types and Performance

EVS disks are classified based on the disk I/O performance. EVS disks differ in performance and price. Choose the disk type most appropriate for your applications.

-

Application Scenarios

  • Common I/O: EVS disks of this type deliver a maximum of 1,000 IOPS. This disk type is suitable for application scenarios that require large capacity, a medium read/write speed, and fewer transactions, such as enterprise office applications and small-scale testing.
  • High I/O: EVS disks of this type deliver a maximum of 3,000 IOPS and a minimum of 6 ms read/write latency. This disk type is designed to meet the needs of mainstream high-performance, high-reliability application scenarios, such as enterprise applications, large-scale development and testing, and web server logs.
  • Ultra-high I/O: EVS disks of this type deliver a maximum of 20,000 IOPS and a minimum of 1 ms read/write latency. This disk type is excellent for ultra-high I/O, ultra-high bandwidth, and read/write-intensive application scenarios, such as distributed file systems in HPC scenarios or NoSQL/relational databases in I/O-intensive scenarios.
  • High I/O (Performance optimized I): EVS disks of this type deliver a maximum of 550 MB/s throughput, which is higher than high I/O EVS disks. They are cost-effective and provide higher performance, optimizing both IOPS and bandwidth. Such disks are particularly suitable for hybrid load scenarios consisting of online analytical processing (OLAP) and online transaction processing (OLTP) or consisting of large and small HPC files.
  • Ultra-high I/O (Latency optimized): EVS disks of this type deliver a maximum of 1 GB/s throughput and a minimum of 1 ms read/write latency. They can be used for enterprise key services, such as SAP HANA.

    Currently, high I/O (performance optimized I) and ultra-high I/O (latency optimized) EVS disks can be attached to SAP HANA ECSs or HL1 ECSs only.

    +

    Application Scenarios

    • Common I/O: This type of EVS disks delivers a maximum of 1,000 IOPS. They are suitable for applications that require large capacity, a medium read/write speed, and fewer transactions, such as enterprise office applications and small-scale test environments.
    • High I/O: This type of EVS disks delivers a maximum of 3,000 IOPS and a minimum of 6 ms read/write latency. They are designed to meet the needs of mainstream high-performance, high-reliability applications, such as enterprise applications, large-scale development and test environments, and web server logs.
    • Ultra-high I/O: This type of EVS disks delivers a maximum of 20,000 IOPS and a minimum of 1 ms read/write latency. They are excellent for read/write-intensive applications that require super-high I/O and bandwidth, such as distributed file systems in HPC scenarios or NoSQL/relational databases in I/O-intensive scenarios.
    • High I/O (Performance optimized I): This type of EVS disks delivers a maximum of 550 MiB/s throughput, which is higher than high I/O EVS disks. They are cost-effective and provide higher performance, optimizing both IOPS and bandwidth. Such disks are particularly suitable for mixed load scenarios consisting of online analytical processing (OLAP) and online transaction processing (OLTP) or consisting of large and small HPC files.
    • Ultra-high I/O (Latency optimized): This type of EVS disks delivers a maximum of 1 GiB/s throughput and a minimum of 1 ms read/write latency. They can be used for enterprise mission-critical applications, such as SAP HANA.
    • Extreme SSD: This type of EVS disks delivers a maximum of 128,000 IOPS. They are designed for workloads demanding super-high bandwidth and super-low latency, such as Oracle databases and AI applications.
      • High I/O (performance optimized I) and ultra-high I/O (latency optimized) EVS disks can only be attached to SAP HANA ECSs or HL1 ECSs.
      • If an Extreme SSD disk is attached to a BMS, it can reach a maximum IOPS of 128,000. If it is attached to an ECS, it can reach a maximum IOPS of 100,000 due to I/O queue limitations.
    -

    EVS Disk Performance

    EVS disk performance metrics include:
    • IOPS: Number of read/write operations performed by an EVS disk per second
    • Throughput: Amount of data read from and written into an EVS disk per second
    • Read/write I/O latency: Minimum interval between two consecutive read/write operations on an EVS disk
    +

    EVS Performance

    EVS performance metrics include:
    • IOPS: Number of read/write operations performed by an EVS disk per second
    • Throughput: Amount of data read from and written into an EVS disk per second
    • Read/write I/O latency: Minimum interval between two consecutive read/write operations on an EVS disk

    -
Table 1 Differences among EVS, SFS, and OBS

Service

EVS

EVS provides scalable block storage that features high reliability, high performance, and rich specifications for servers.

+

EVS provides scalable block storage that features high reliability, high performance, and a variety of specifications for servers.

  • Enterprise office applications
  • Development and testing
  • Enterprise applications, including SAP, Microsoft Exchange, and Microsoft SharePoint
  • Distributed file systems
  • Various databases, including MongoDB, Oracle, SQL Server, MySQL, and PostgreSQL

EVS disks start at 10 GB and can be expanded as required in 1 GB increments to up to 32 TB.

+

EVS disks start at 10 GiB and can be expanded as required in 1 GiB increments to up to 32 TiB.

SFS

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.

+

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.

  • HPC scenarios, such as gene sequencing, animation rendering, and CAD/CAE
  • File sharing
  • Media processing
  • Content management and web services
  • Offline file backup

SFS storage capacity is available on demand and can be expanded to 10 PB at most.

+

SFS storage capacity is available on demand and can be expanded to a maximum of 2 PB.

OBS

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.

  • Enterprise backup and archive
  • Big data analysis
  • Enterprise cloud box
  • Static website hosting
  • Native cloud applications
+
  • Enterprise backup and archive
  • Big data analysis
  • Enterprise cloud box
  • Static website hosting
  • Cloud-native applications

OBS provides limitless storage capacity, and storage resources are available for linear and nearly infinite expansion.

+

OBS has limitless storage capacity, and storage resources are available for linear and nearly infinite expansion.

Table 1 EVS disk performance data

Parameter

+
- - - - - + - - - - - - + - - - - - - + - - - - - - + - - - - - - + - - - - - - + - - - - - - + diff --git a/docs/evs/umn/en-us_topic_0017616396.html b/docs/evs/umn/en-us_topic_0017616396.html index f8f2943c..bbe57aa0 100644 --- a/docs/evs/umn/en-us_topic_0017616396.html +++ b/docs/evs/umn/en-us_topic_0017616396.html @@ -7,16 +7,17 @@
  • For a 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.

    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 Managing EVS Backup. For details about snapshots, see Creating a Snapshot.

    +

    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.

    +

    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 Managing EVS Backups. For details about using snapshots, see Creating a Snapshot.

    Prerequisites

    -

    System Disk: Add Additional Space to Volume (C:)

    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 server. After the operation is complete, volume (C:) will have 72 GB of capacity and can be used as a system volume.

    +

    System Disk: Add Additional Space to Volume (C:)

    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 server. After the operation is complete, volume (C:) will have 72 GiB of capacity and can be used as a system volume.

    1. On the desktop of the server, right-click Computer and choose Manage from the shortcut menu.

      The Server Manager window is displayed.

      -

    2. In the navigation tree, choose Storage > Disk Management.

      The Disk Management window is displayed.

      +

    3. In the navigation tree, choose Storage > Disk Management.

      The Disk Management window is displayed.

      Figure 1 Disk Management (system disk)

      If you cannot view the additional space, right-click Disk Management and choose Refresh from the shortcut menu.

      @@ -27,36 +28,36 @@

    -

    System Disk: Create New Volume (F:) with Additional Space

    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 server. After the operation is complete, new volume (F:) has 60 GB of capacity and can be used as a data volume.

    +

    System Disk: Create New Volume (F:) with Additional Space

    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 server. After the operation is complete, new volume (F:) has 60 GiB of capacity and can be used as a data volume.

    1. On the desktop of the server, right-click Computer and choose Manage from the shortcut menu.

      The Server Manager window is displayed.

      -

    2. In the navigation tree, choose Storage > Disk Management.

      The Disk Management window is displayed.
      Figure 6 Refresh (system disk)
      +

    3. In the navigation tree, choose Storage > Disk Management.

      The Disk Management window is displayed.
      Figure 6 Refresh (system disk)

    4. If you cannot view the additional space, right-click Disk Management and choose Refresh from the shortcut menu.

      After the refresh, the additional space is displayed in the right area and is unallocated.

      Figure 7 Unallocated disk space (system disk)

    5. In the Unallocated area of Disk 0, right-click the blank area and choose New Simple Volume.

      Figure 8 New Simple Volume (system disk)
      -

    6. On the displayed New Simple Volume Wizard window, click Next.

      Figure 9 New Simple Volume Wizard (system disk)
      +

    7. On the displayed New Simple Volume Wizard window, click Next.

      Figure 9 New Simple Volume Wizard (system disk)

    8. On the displayed Specify Volume Size page, set Simple volume size in MB and click Next. In this example, the default size is used.

      Figure 10 Specify Volume Size (system disk)

    9. On the displayed Assign Drive Letter and Path page, click Assign the following drive letter, select a drive letter, and click Next. In this example, drive letter F is selected.

      Figure 11 Assign Driver Letter or Path (system disk)

    10. On the displayed Format Partition page, click Format this volume with the following settings, set parameters based on the requirements, and select Perform a quick format. Then, click Next.

      Figure 12 Format Partition (system disk)
      -

    11. Click Finish.

      After the expansion succeeded, new volume (F:) is displayed.
      Figure 13 Completing the New Simple Volume Wizard (new volume F:)
      +

    12. Click Finish.

      After the expansion succeeded, new volume (F:) is displayed.
      Figure 13 Completing the New Simple Volume Wizard (new volume F:)
      Figure 14 New Volume (F:)

    -

    Data Disk: Add Additional Space to Volume (D:)

    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 server. After the operation is complete, volume (D:) has 150 GB of capacity and can be used as a data volume.

    +

    Data Disk: Add Additional Space to Volume (D:)

    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 server. After the operation is complete, volume (D:) has 150 GiB of capacity and can be used as a data volume.

    1. On the desktop of the server, right-click Computer and choose Manage from the shortcut menu.

      The Server Manager window is displayed.

      -

    2. In the navigation tree, choose Storage > Disk Management.

      The Disk Management window is displayed.
      Figure 15 Disk Management (data disk)
      +

    3. In the navigation tree, choose Storage > Disk Management.

      The Disk Management window is displayed.
      Figure 15 Disk Management (data disk)

      If you cannot view the additional space, right-click Disk Management and choose Refresh from the shortcut menu.

    4. On the Disk Management page, select the disk and volume that you want to extend. The current volume size and unallocated space are displayed.
    5. Right-click the target volume and choose Extend Volume.

      Figure 16 Choosing Extend Volume (Windows Server 2008)
      -

    6. On the displayed Extend Volume Wizard window, click Next.

      Figure 17 Extend Volume Wizard (Windows Server 2008)
      -

    7. In the text box to the right of Select the amount of space in MB, enter the amount of the additional space and click Next.

      Figure 18 Selecting space (Windows Server 2008)
      -

    8. Click Finish.

      After the expansion succeeded, the partition size is larger than the original size.
      Figure 19 Capacity expansion succeeded (Windows Server 2008)
      +

    9. On the displayed Extend Volume Wizard window, click Next.

      Figure 17 Extend Volume Wizard (Windows Server 2008)
      +

    10. In the text box to the right of Select the amount of space in MB, enter the amount of the additional space and click Next.

      Figure 18 Selecting space (Windows Server 2008)
      +

    11. Click Finish.

      After the expansion succeeded, the partition size is larger than the original size.
      Figure 19 Capacity expansion succeeded (Windows Server 2008)

    -

    Data Disk: Create New Volume (E:) with Additional Space

    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 server. After the operation is complete, new volume (E:) has 60 GB of capacity and can be used as a data volume.

    +

    Data Disk: Create New Volume (E:) with Additional Space

    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 server. After the operation is complete, new volume (E:) has 60 GiB of capacity and can be used as a data volume.

    1. On the desktop of the server, right-click Computer and choose Manage from the shortcut menu.

      The Server Manager window is displayed.

    2. In the navigation tree, choose Storage > Disk Management.

      The Disk Management window is displayed.
      Figure 20 Refresh (data disk)
      diff --git a/docs/evs/umn/en-us_topic_0021738346.html b/docs/evs/umn/en-us_topic_0021738346.html index 15893f65..baf407ce 100644 --- a/docs/evs/umn/en-us_topic_0021738346.html +++ b/docs/evs/umn/en-us_topic_0021738346.html @@ -2,7 +2,7 @@

      Create an EVS Disk

      Scenarios

      EVS disks can be used as system disks or data disks for servers.

      -
      • When a server is created, a system disk is automatically created and attached. You cannot create a system disk separately. The maximum size of a system disk is 1024 GB.
      • Data disks can be created during or after the server creation. If you create data disks during the server creation, the system will automatically attach the data disks to the server. If you create data disks after the server creation, you need to manually attach the data disks. The maximum size of a data disk is 32768 GB.
      +
      • System disks can only be created together with servers and are automatically attached.
      • A system disk can have a maximum of 1,024 GiB, and a data disk 32,768 GiB.
      • Data disks that created together with servers are automatically attached.
      • After servers are created, any data disks added on the cloud server console are automatically attached.
      • After servers are created, any data disks added on the EVS console need to be manually attached.

      This section describes how to separately create disks on the EVS console.

      Procedure

      1. Log in to the management console.
      2. Click in the upper left corner and select the desired region and project.
      3. Under Storage, click Elastic Volume Service.

        The disk list page is displayed.

        @@ -10,7 +10,7 @@
      4. Figure 2 shows the parameter setting of encrypted disks.
        Figure 2 Encrypted disks
      5. Configure basic disk information according to Table 1.

        -

    Table 1 EVS performance data

    Parameter

    Common I/O

    +

    Common I/O

    High I/O

    +

    High I/O

    Ultra-high I/O

    +

    Ultra-high I/O

    High I/O (Performance optimized I)

    +

    High I/O (Performance optimized I)

    Ultra-high I/O (Latency optimized)

    +

    Ultra-high I/O (Latency optimized)

    +

    Extreme SSD

    IOPS per GB/EVS disk

    +

    IOPS per GiB/EVS disk

    1

    +

    1

    3

    +

    2

    50

    +

    50

    3

    +

    6

    50

    +

    50

    +

    50

    Min. IOPS/EVS disk

    +

    Min. IOPS/EVS disk

    100

    +

    100

    100

    +

    100

    100

    +

    100

    100

    +

    1,200

    100

    +

    1,500

    +

    1,800

    Max. IOPS/EVS disk

    +

    Max. IOPS/EVS disk

    1,000

    +

    1,000

    3,000

    +

    3,000

    20,000

    +

    20,000

    3,000

    +

    5,000

    30,000

    +

    33,000

    +

    128,000

    IOPS burst limit/EVS disk

    +

    IOPS burst limit/EVS disk

    1,000

    +

    1,000

    3,000

    +

    3,000

    10,000

    +

    10,000

    3,000

    +

    5,000

    15,000

    +

    16,000

    +

    64,000

    Max. throughput

    +

    Max. throughput

    40 MB/s

    +

    90 MiB/s

    120 MB/s

    +

    150 MiB/s

    320 MB/s

    +

    350 MiB/s

    550 MB/s

    +

    550 MiB/s

    1 GB/s

    +

    1 GiB/s

    +

    1,000 MiB/s

    Read/write I/O latency

    -
    NOTE:

    This parameter specifies the single-queue access latencies of EVS disks.

    +

    Read/write I/O latency

    +
    NOTE:

    This parameter specifies the single-queue access latencies of EVS disks.

    10 ms to 15 ms

    +

    10 ms to 15 ms

    6 ms to 10 ms

    +

    6 ms to 10 ms

    1 ms to 3 ms

    +

    1 ms to 3 ms

    6 ms to 10 ms

    +

    6 ms to 10 ms

    1 ms

    +

    1 ms

    +

    Sub-millisecond

    Table 1 Parameter description

    Parameter

    +
    @@ -29,7 +29,7 @@ @@ -39,30 +39,30 @@ - - @@ -73,7 +73,7 @@ -
    Table 1 Disk parameters

    Parameter

    Description

    AZ

    Mandatory

    -

    Specifies the availability zone (AZ) where you want to create the disk.

    +

    The availability zone (AZ) where you want to create the disk.

    NOTE:
    • Disks can only be attached to the servers in the same AZ.
    • The AZ of a disk cannot be changed after the disk has been created.

    Disk Type

    Mandatory

    -
    • Common I/O
    • High I/O
    • Ultra-high I/O
    • High I/O (Performance optimized I)
    • Ultra-high I/O (Latency optimized)
    +
    • Common I/O
    • High I/O
    • Ultra-high I/O
    • High I/O (Performance optimized I)
    • Ultra-high I/O (Latency optimized)
    • Extreme SSD
    NOTE:
    • When disks are created from backups:

      If the disk type of the backup's source disk is common I/O, high I/O, or ultra-high I/O, you can create disks of any of these types.

      If the disk type of the backup's source disk is high I/O (performance optimized I) or ultra-high I/O (latency optimized), you can create disks of any of the two types.

      -
    • When a disk is created from a snapshot, the disk type of the newly created disk will be consistent with that of the snapshot's source disk.
    • For details about disk types, see Disk Types and Performance.
    +
  • When a disk is created from a snapshot, the disk type of the new disk will be consistent with that of the snapshot's source disk.
  • For more information about disk types, see Disk Types and Performance.
  • Common I/O

    Capacity (GB)

    +

    Disk Size (GiB)

    Mandatory

    -

    Specifies the disk size. Only data disks can be created on the current page, and the disk capacity ranges from 10 GB to 32768 GB.

    -
    NOTE:
    • When you use a backup to create a disk, the disk capacity must be greater than or equal to the backup size. In the condition that you do not specify the disk capacity, if the backup size is smaller than 10 GB, the default capacity 10 GB will be used as the disk capacity; if the backup size is greater than 10 GB, the disk capacity will be consistent with the backup size.
    • When you use a snapshot to create a disk, 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.
    +

    The disk size. Only data disks can be created on the current page, and the disk size ranges from 10 GiB to 32,768 GiB.

    +
    NOTE:
    • When you use a backup to create a disk, the disk capacity must be greater than or equal to the backup size. In the condition that you do not specify the disk capacity, if the backup size is smaller than 10 GiB, the default capacity 10 GiB will be used as the disk capacity; if the backup size is greater than 10 GiB, the disk capacity will be consistent with the backup size.
    • When you use a snapshot to create a disk, 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.

    20 GB

    +

    20 GiB

    Create from backup

    Optional

    Specifies to create the disk from a backup.

    -

    Click Select Data Source and choose Create from backup. On the displayed page, select the target backup and click OK.

    +

    Click Select Data Source and choose Create from backup. On the displayed page, select the target backup and click OK.

    NOTE:
    • You can select a backup created by the current tenant or shared with the current tenant by another tenant.
    • One backup cannot be used for concurrent disk creation operations at the same time. For example, if you are creating disk A from a backup, this backup can be used to create another disk only after disk A has been created.
    • If a disk is created from a backup of a system disk, the new disk can be used as a data disk only.

    Optional

    Specifies to create the disk from a snapshot.

    -

    Click Select Data Source and choose Create from snapshot. On the displayed page, select the target snapshot and click OK.

    +

    Click Select Data Source and choose Create from snapshot. On the displayed page, select the target snapshot and click OK.

    NOTE:
    • The disk type of the new disk is the same as that of the snapshot's source disk.
    • The device type of the new disk is the same as that of the snapshot's source disk.
    • The encryption attribute of the new disk is the same as that of the snapshot's source disk.

    For details about the disk creation from snapshots, see Creating an EVS Disk from a Snapshot.

    @@ -84,9 +84,9 @@

    Auto Backup

    Optional

    -

    If auto backup is enabled, the system automatically creates backups for the disk data at specified time points and deletes outdated backups according to the configured backup policy.

    +

    If auto backup is enabled, the system automatically creates backups for the disk at specified time points and deletes outdated backups according to the configured backup policy.

    When Enable is selected, a backup policy must be configured. You can either use the default backup policy or customize the policy based on your service requirements.

    -
    NOTE:

    For details about the backup policy, see Managing EVS Backup.

    +
    NOTE:

    For details about the backup policy, see Managing EVS Backups.

    -

    @@ -95,10 +95,10 @@

    Share

    Optional

    -
    • If Share is not selected, a common disk is created.
    • If Share is selected, a shared disk is created, and the shared disk can be attached to multiple servers.
    -

    If both SCSI and Share are selected, a shared SCSI disk is created.

    +
    • If Share is not selected, a common disk is created.
    • If Share is selected, a shared disk is created, and the shared disk can be attached to multiple servers.
    +

    If both SCSI and Share are selected, a shared SCSI disk is created.

    NOTE:

    The sharing attribute of a disk cannot be changed after the disk has been created.

    -

    For details about shared EVS disks, see Managing a Shared EVS Disk.

    +

    For details about shared EVS disks, see Managing Shared EVS Disks.

    -

    @@ -107,7 +107,7 @@

    SCSI

    Optional

    -
    • If SCSI is not selected, a VBD disk is created. VBD is the default device type of EVS disks.
    • If SCSI is selected, a SCSI disk is created. Such disks allow the server OS to directly access the underlying storage media and send SCSI commands to the disks.
    +
    • If you do not select SCSI, a VBD disk is created. VBD is the default device type of EVS disks.
    • If you select SCSI, a SCSI disk is created. Such disks allow the server OS to directly access the underlying storage media and send SCSI commands to the disks.
    NOTE:

    The device type of a disk cannot be changed after the disk has been created.

    For details about the ECS types, OSs, and ECS software supported by SCSI EVS disks, see Device Types and Usage Instructions.

    @@ -118,7 +118,7 @@

    Encryption

    Optional

    -

    Disk encryption is used for data disk encryption only. For system disk encryption, see the Image Management Service User Guide.

    +

    Disk encryption is used for data disk encryption only. System disk encryption relies on the image. For details, see the Image Management Service User Guide.

    To use the disk encryption function, select Encryption. The displayed dialog box contains the following parameters:

    • Create Agency

      An agency is a trust relationship between two tenants or services. A tenant can create an agency to grant resource access rights to another tenant or service. If the KMS access rights are not granted to EVS, the Create Agency dialog box will be displayed. Otherwise, it will not be displayed.

      Click Yes to grant the KMS access rights to EVS. After the rights have been granted, EVS can obtain KMS keys to encrypt or decrypt EVS disks.

      @@ -126,11 +126,11 @@
    • KMS Key Name
      NOTE:

      KMS Key Name is displayed only after the KMS access rights have been granted. For details, see "Create Agency" above.

      -
      KMS Key Name is the identifier of the key, and you can use KMS Key Name to specify the KMS key that is to be used for encryption. One of the following keys can be used:
      • Default Master Key: After the KMS access rights have been granted to EVS, the system automatically creates a Default Master Key and names it evs/default.
      • CMKs: Existing or newly created CMKs. For details, see Management > Creating a CMK in the Key Management Service User Guide.
      +
      KMS Key Name is the identifier of the key, and you can use KMS Key Name to specify the KMS key that is to be used for encryption. One of the following keys can be used:
      • Default Master Key: After the KMS access rights have been granted to EVS, the system automatically creates a Default Master Key and names it evs/default.
      • CMKs: Existing or newly created CMKs. For details, see Management > Creating a CMK in the Key Management Service User Guide.
    -
    NOTE:
    • Before you use the EVS disk encryption function, KMS access rights need to be granted to EVS. If you have the right to grant the permission, 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.
    • The encryption attribute of a disk cannot be changed after the disk has been created.
    -

    For details, see EVS Disk Encryption.

    +
    NOTE:
    • Before you use the encryption function, KMS access rights need to be granted to EVS. If you have the right to grant the permission, 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.
    • The encryption attribute of a disk cannot be changed after the disk has been created.
    +

    For details, see EVS Encryption.

    -

    @@ -158,14 +158,14 @@
  • If you create disks in a batch, this parameter value is used as the prefix of disk names, and one disk name will be composed of this parameter value and a four-digit number.

    The name can contain a maximum of 59 characters.

  • For example, if you create two disks and set volume for Disk Name, the EVS disk names will be volume-0001 and volume-0002.

    +

    For example, if you create two disks and set volume for Disk Name, the EVS disk names will be volume-0001 and volume-0002.

    Quantity

    Optional

    -

    Specifies the number of disks to be created. The default value is set to 1, which means only one disk is created. Currently, you can create up to 100 disks at a time.

    -
    NOTE:
    • If the disk is created from a backup, batch creation is not possible, and this parameter must be set to 1.
    • If the disk is created from a snapshot, batch creation is not possible, and this parameter must be set to 1.
    +

    The number of disks to be created. The default value is set to 1, which means only one disk is created. Currently, you can create up to 100 disks at a time.

    +
    NOTE:
    • If the disk is created from a backup, batch creation is not possible, and this parameter must be set to 1.
    • If the disk is created from a snapshot, batch creation is not possible, and this parameter must be set to 1.

    1

    @@ -174,7 +174,7 @@
    -

  • Click Create Now.
  • On the Details page, check the disk details.

    • If you do not need to modify the specifications, click Submit to start the creation.
    • If you need to modify the specifications, click Previous to modify parameters.
    +

  • Click Create Now.
  • On the Details page, check the disk details.

    • If you do not need to modify the specifications, click Submit.
    • If you need to modify the specifications, click Previous.

  • Go back to the disk list page and view the disk status.

    When the disk status changes to Available, the disk is successfully created.

  • diff --git a/docs/evs/umn/en-us_topic_0032860759.html b/docs/evs/umn/en-us_topic_0032860759.html index 4bf098ae..45addc7d 100644 --- a/docs/evs/umn/en-us_topic_0032860759.html +++ b/docs/evs/umn/en-us_topic_0032860759.html @@ -2,12 +2,12 @@

    Shared EVS Disks and Usage Instructions

    What Are Shared EVS Disks?

    Shared EVS disks are block storage devices that support concurrent read/write operations and can be attached to multiple servers. 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 servers can access the same shared EVS disk at the same time.

    -

    A shared EVS disk can be attached to a maximum of 16 servers. 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.

    -

    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 servers, the EVS disks cannot be shared and data may be overwritten.

    +

    A shared EVS disk can be attached to a maximum of 16 servers. 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.

    +

    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 servers, the sharing function will not work and data may be overwritten.

    Figure 1 Application scenario of shared EVS disks
    -

    Usage Precautions

    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 Device Types and Usage Instructions.

    +

    Usage Precautions

    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 Device Types and Usage Instructions.

    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.
    • 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.
    • Shared SCSI EVS disks: These EVS disks support SCSI reservations.
      • 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.
      • 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.

      Concepts of the anti-affinity ECS group and SCSI reservations:

      @@ -16,9 +16,9 @@
    -

    Advantages

    • Multiple attachments: A shared EVS disk can be attached to a maximum of 16 servers.
    • High-performance: When multiple servers concurrently access a shared ultra-high I/O EVS disk, random read/write IOPS can reach up to 160,000.
    • High-reliability: Shared EVS disks support both manual and automatic backup, delivering highly reliable data storage.
    • 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.
    +

    Advantages

    • Multiple attachments: A shared EVS disk can be attached to a maximum of 16 servers.
    • High-performance: The random read/write IOPS of a shared ultra-high I/O disk can reach up to 160,000.
    • High-reliability: Shared EVS disks support both manual and automatic backup, delivering highly reliable data storage.
    • 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.
    -

    Specifications and Performance

    The specifications and performance of shared EVS disks are the same as those of non-shared EVS disks. For details, see Disk Types and Performance.

    +

    Specifications and Performance

    Shared EVS disks have the same specifications and performance as non-shared EVS disks. For details, see Disk Types and Performance.

    Data Sharing Principle and Common Usage Mistakes

    A shared EVS disk is essentially the disk that can be attached to multiple servers 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.

    Though shared EVS disks are block storage devices that provide shared access for servers, 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.

    @@ -29,7 +29,7 @@

    Before you attach a shared EVS disk to multiple servers, 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 the server OS and ensure that the OS image is included in the compatibility list.

    -

    For details about the usages of shared EVS disks, see Managing a Shared EVS Disk.

    +

    For details about the usages of shared EVS disks, see Managing Shared EVS Disks.

    If you simply attach a shared EVS disk to multiple servers, files cannot be shared between the servers 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 servers.

    diff --git a/docs/evs/umn/en-us_topic_0052554220.html b/docs/evs/umn/en-us_topic_0052554220.html index 5338b1ea..71b2b8dd 100644 --- a/docs/evs/umn/en-us_topic_0052554220.html +++ b/docs/evs/umn/en-us_topic_0052554220.html @@ -5,10 +5,10 @@

    Device type is configured during creation. It cannot be changed after the disk has been created.

    -

    Common Application Scenarios and Usage Instructions of SCSI EVS Disks

    • BMSs support only SCSI EVS disks.
    • 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.

      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 Shared EVS Disks and Usage Instructions.

      +

      Common Application Scenarios and Usage Instructions of SCSI EVS Disks

      • BMSs support only SCSI EVS disks.
      • 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.

        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 Shared EVS Disks and Usage Instructions.

      -

      Do I Need to Install a Driver for SCSI EVS Disks?

      To use SCSI EVS disks, you need to install a driver for certain server OSs.
      • BMS

        Both the Windows and Linux images for BMSs are pre-installed with the required SDI card driver. Therefore, no driver needs to be installed.

        +

        Do I Need to Install a Driver for SCSI EVS Disks?

        To use SCSI EVS disks, you need to install a driver for certain server OSs.
        • Bare Metal Server (BMS)

          Both the Windows and Linux images for BMSs are pre-installed with the required SDI card driver. Therefore, no driver needs to be installed.

        • KVM ECS

          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.

          ECS virtualization types are categorized into KVM and Xen. For details, see ECS Types.

          diff --git a/docs/evs/umn/en-us_topic_0066615262.html b/docs/evs/umn/en-us_topic_0066615262.html index 8f7758df..a5000a50 100644 --- a/docs/evs/umn/en-us_topic_0066615262.html +++ b/docs/evs/umn/en-us_topic_0066615262.html @@ -3,12 +3,12 @@

          Creating a Snapshot

          Scenarios

          You can create an EVS snapshot on the management console to save the EVS disk data at a specific time point.

          -

          Constraints

          • A maximum of 7 snapshots can be created for one disk.
          • Snapshots can be created for both system disks and data disks.
          +

          Constraints

          • A maximum of 7 snapshots can be created for one disk.
          • Snapshots can be created for both system disks and data disks.
          • Snapshots can be created only for available or in-use disks.
          • Snapshots of encrypted disks are stored encrypted, and those of non-encrypted disks are stored non-encrypted.
          • 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.
          -

          Creating a Snapshot on the Disks Page

          1. Log in to the management console.
          2. Click in the upper left corner and select the desired region and project.
          3. Under Storage, click Elastic Volume Service.

            The disk list page is displayed.

            -

          4. In the disk list, locate the row that contains the target disk, click More in the Operation column, and choose Create Snapshot.

            Configure the basic settings for the snapshot according to Table 1.

            +

            Creating a Snapshot on the Disks Page

            1. Log in to the management console.
            2. Click in the upper left corner and select the desired region and project.
            3. Under Storage, click Elastic Volume Service.

              The disk list page is displayed.

              +

            4. In the disk list, locate the row that contains the target disk, click Create Snapshot in the Operation column.

              Configure the basic settings for the snapshot according to Table 1.

              -
              Table 1 Parameter description

              Parameter

              +
              @@ -27,14 +27,14 @@
              Table 1 Snapshot parameter

              Parameter

              Description

              -

            5. Click Create Now.
            6. Return to the Snapshots page to view the snapshot creation information.

              When the snapshot status changes to Available, the snapshot has been created.

              +

            7. Click Create Now.
            8. Go back to the Snapshots page to view the snapshot creation information.

              After the snapshot status changes to Available, the snapshot has been created.

            9. -

              Creating a Snapshot on the Snapshots Page

              1. Log in to the management console.
              2. Click in the upper left corner and select the desired region and project.
              3. Under Storage, click Elastic Volume Service.

                The disk list page is displayed.

                +

                Creating a Snapshot on the Snapshots Page

                1. Log in to the management console.
                2. Click in the upper left corner and select the desired region and project.
                3. Under Storage, click Elastic Volume Service.

                  The disk list page is displayed.

                4. In the navigation pane on the left, choose Elastic Volume Service > Snapshots.

                  On the Snapshots page, click Create Snapshot.

                  Configure the basic settings for the snapshot according to Table 2.

                  -
                  Table 2 Parameter description

                  Parameter

                  +
                  @@ -61,7 +61,7 @@ @@ -69,13 +69,13 @@
                  Table 2 Snapshot parameters

                  Parameter

                  Description

                  Select Disk

                  Mandatory

                  -

                  Select a disk based on which the snapshot is to be created.

                  +

                  Select a disk based on which the snapshot will be created.

                  volume-01

                  -

                5. Click Create Now.
                6. Return to the Snapshots page to view the snapshot creation information.

                  When the snapshot status changes to Available, the snapshot has been created.

                  +

                7. Click Create Now.
                8. Go back to the Snapshots page to view the snapshot creation information.

                  After the snapshot status changes to Available, the snapshot has been created.

                9. diff --git a/docs/evs/umn/en-us_topic_0066809008.html b/docs/evs/umn/en-us_topic_0066809008.html index fd205fcc..fcf808cb 100644 --- a/docs/evs/umn/en-us_topic_0066809008.html +++ b/docs/evs/umn/en-us_topic_0066809008.html @@ -14,7 +14,7 @@
                10. Multi-service quick deployment

                  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.

                11. -

                  Usage Instructions

                  For details about the snapshot usages, see Managing Snapshots.

                  +

                  Usage Instructions

                  For details about the snapshot usages, see Managing EVS Snapshots.

                  diff --git a/docs/evs/umn/evs_01_0001.html b/docs/evs/umn/evs_01_0001.html index 670f3a6b..fa7c9ca7 100644 --- a/docs/evs/umn/evs_01_0001.html +++ b/docs/evs/umn/evs_01_0001.html @@ -1,38 +1,43 @@ -

                  EVS Disk Encryption

                  -

                  What Is EVS Disk Encryption?

                  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.

                  +

                  EVS Encryption

                  +

                  What Is EVS Encryption?

                  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.

                  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.

                  +

                  +

                  The encryption attribute of a disk cannot be changed after the disk is purchased.

                  +

                  For details about how to create an encrypted disk, see Getting Started > Purchase an EVS Disk in the Elastic Volume Service User Guide.

                  +
                  -

                  Keys Used for EVS Disk Encryption

                  The keys provided by KMS include a Default Master Key and Customer Master Keys (CMKs).
                  • Default Master Key: A key that is automatically created by EVS through KMS and named evs/default.

                    The Default Master Key cannot be disabled and does not support scheduled deletion.

                    +

                    Keys Used for EVS Encryption

                    The keys provided by KMS include a Default Master Key and Customer Master Keys (CMKs).
                    • Default Master Key: A key that is automatically created by EVS through KMS and named evs/default.

                      The Default Master Key cannot be disabled and does not support scheduled deletion.

                    • CMKs: Keys created by users. You may use existing CMKs or create new CMKs to encrypt disks. For details, see Management > Creating a CMK in the Key Management Service User Guide.
                    -
                    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 Table 1 for more information. -
                    Table 1 Impact of CMK unavailability

                    CMK Status

                    +

                    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.

                    +
                    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 Table 1 for more information. +
                    - - - - - - - - - @@ -40,22 +45,22 @@ -

                    Who Can Use the Disk Encryption Function?

                    • The security administrator (having the Security Administrator rights) can grant the KMS access rights to EVS for using the disk encryption function.
                    • 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.
                      • 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.
                      • 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.
                      +

                      Who Can Use the Encryption Function?

                      • The security administrator (having Security Administrator permissions) can grant the KMS access rights to EVS for using the encryption function.
                      • 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.
                        • 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.
                        • 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.
                      -

                      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.

                      +

                      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.

                      If there are multiple projects in the current region, the KMS access rights need to be granted to each project in this region.

                      -

                      Application Scenarios of EVS Disk Encryption

                      Figure 1 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.

                      +

                      Application Scenarios of EVS Encryption

                      Figure 1 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.

                      Figure 1 User relationships
                      -
                      • If the security administrator uses the encryption function for the first time ever, the operation process is as follows:
                        1. Grant the KMS access rights to EVS.

                          After the KMS access rights have been granted, the system automatically creates a Default Master Key and names it evs/default. DMK can be used for disk encryption.

                          -

                          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.

                          +
                          • If the security administrator uses the encryption function for the first time ever, the operation process is as follows:
                            1. Grant the KMS access rights to EVS.

                              After the KMS access rights have been granted, the system automatically creates a Default Master Key and names it evs/default. You can use the Default Master Key to encrypt EVS disks.

                              +

                              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.

                              -
                            2. Select a key.
                              You can select one of the following keys:
                              • DMK: evs/default
                              • CMKs: Existing or newly created CMKs. For details, see Creating a CMK in the Key Management Service User Guide.
                              +
                            3. Select a key.
                              You can select one of the following keys:
                              • Default Master Key: evs/default
                              • CMKs: Existing or newly created CMKs. For details, see Creating a CMK in the Key Management Service User Guide.
                            -

                            After the security administrator has used the disk encryption function, all users in Region B can directly use the encryption function.

                            -
                          • If User E (common user) uses the encryption function for the first time ever, the operation process is as follows:
                            1. 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.
                            2. Contact the security administrator to grant the KMS access rights to EVS.
                            -

                            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.

                            +

                            After the security administrator has used the encryption function, all users in Region B can directly use encryption.

                            +
                          • If User E (common user) uses the encryption function for the first time ever, the operation process is as follows:
                            1. When user E uses encryption, and the system prompts a message indicating that the KMS access rights have not been granted to EVS.
                            2. Contact the security administrator to grant the KMS access rights to EVS.
                            +

                            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.

                          diff --git a/docs/evs/umn/evs_01_0003.html b/docs/evs/umn/evs_01_0003.html index 8267fd3b..9a10b4e1 100644 --- a/docs/evs/umn/evs_01_0003.html +++ b/docs/evs/umn/evs_01_0003.html @@ -2,7 +2,7 @@

                          Detaching a System Disk

                          Scenarios

                          A system disk can only be detached offline, that is, its server must be in the Stopped state before the system disk is detached. Therefore, you need to first stop the server and then detach the system disk.

                          -
                          For the system disk attached to a server, the disk function is displayed as System disk, and the disk status is displayed as In-use in the disk list. After a system disk is detached from the server, the disk function changes to Bootable disk, and the status changes to Available.

                          Bootable disks are the system disks detached from servers. A bootable disk can be re-attached to a server and be used as a system disk or data disk depending on the device name selected.

                          +
                          For a system disk attached to a server, the disk function is displayed as System disk, and the disk status is displayed as In-use in the disk list. After a system disk is detached from the server, the disk function changes to Bootable disk, and the status changes to Available.

                          Bootable disks are the system disks detached from servers. A bootable disk can be re-attached to a server and be used as a system disk or data disk depending on the device name selected.

                          @@ -11,7 +11,7 @@

                        2. Click the name of this server.

                          The server details page is displayed.

                        3. Click the Disks tab to view the system disk attached to the server.
                        4. Locate the row that contains the system disk and click Detach.

                          The Detach Disk dialog box is displayed, as shown in Figure 1.
                          Figure 1 Detach Disk (system disk)
                          -

                        5. Click Yes to detach the disk.

                          After the operation had succeeded, the detached system disk is no longer displayed under the Disks tab.

                          +

                        6. Click Yes to detach the disk.

                          After the operation had succeeded, the detached system disk is no longer displayed under the Disks tab.

                      Related Operations

                      For more detachment FAQs, see Detachment.

                      diff --git a/docs/evs/umn/evs_01_0004.html b/docs/evs/umn/evs_01_0004.html index a1fc6d3b..12d60142 100644 --- a/docs/evs/umn/evs_01_0004.html +++ b/docs/evs/umn/evs_01_0004.html @@ -15,7 +15,7 @@
                    • Click the Attachments tab to view the server where the target disk has been attached.
                    • Click to select the server and click Detach Disk.
                      The Detach Disk dialog box is displayed, as shown in Figure 1.
                      Figure 1 Detach Disk
                    • Click Yes to detach the disk.
                    • -
                    • If you do not need to view the server information, perform the following procedure:
                      1. In the disk list, locate the row that contains the target disk and choose More > Detach in the Operation column.
                        The Detach Disk dialog box is displayed, as shown in Figure 2.
                        Figure 2 Detach Disk dialog box
                        +
                      2. If you do not need to view the server information, perform the following procedure:
                        1. In the disk list, locate the row that contains the target disk and choose More > Detach in the Operation column.
                          The Detach Disk dialog box is displayed, as shown in Figure 2.
                          Figure 2 Detach Disk dialog box
                        2. Click Yes to detach the disk.
                    @@ -26,10 +26,10 @@

                    Detaching a Shared Disk

                    1. Log in to the management console.
                    2. Click in the upper left corner and select the desired region and project.
                    3. Under Storage, click Elastic Volume Service.

                      The disk list page is displayed.

                    4. Determine whether to view the server information before detaching the disk.

                      • If you need to view the server information, perform the following procedure:
                        1. In the disk list, click the name of the to-be-detached disk.

                          The disk details page is displayed.

                        2. Click the Attachments tab to view the servers where the target disk has been attached.
                        3. Click to select the server and click Detach Disk.

                          Shared EVS disks support batch detachment so that you can select multiple servers at a time.

                          -
                          The Detach Disk dialog box is displayed, as shown in Figure 3.
                          Figure 3 Detaching a shared disk
                          +
                          The Detach Disk dialog box is displayed, as shown in Figure 3.
                          Figure 3 Detaching a shared disk
                        4. Click Yes to detach the disk.
                        -
                      • If you do not need to view the server information, perform the following procedure:
                        1. In the disk list, locate the row that contains the target disk and choose More > Detach in the Operation column.
                          The Detach Disk dialog box is displayed, as shown in Figure 4.
                          Figure 4 Detaching a shared disk dialog box
                          +
                        2. If you do not need to view the server information, perform the following procedure:
                          1. In the disk list, locate the row that contains the target disk and choose More > Detach in the Operation column.
                            The Detach Disk dialog box is displayed, as shown in Figure 4.
                            Figure 4 Detaching a shared disk dialog box
                          2. Click to select the server.

                            Shared EVS disks support batch detachment so that you can select multiple servers at a time.

                          3. Click Yes to detach the disk.
                          diff --git a/docs/evs/umn/evs_01_0005.html b/docs/evs/umn/evs_01_0005.html index d406b4c9..a51d3598 100644 --- a/docs/evs/umn/evs_01_0005.html +++ b/docs/evs/umn/evs_01_0005.html @@ -1,6 +1,6 @@ -

                          Deleting an EVS Disk

                          +

                          Deleting EVS Disks

                          Scenarios

                          If an EVS disk is no longer used, you can release the virtual resources by deleting the disk from the system.

                          • Before deleting a disk, ensure that the disk status is Available, Error, Expansion failed, Restoration failed, or Rollback failed.
                          • Before deleting a shared disk, ensure that the disk has been detached from all its servers.
                          diff --git a/docs/evs/umn/evs_01_0006.html b/docs/evs/umn/evs_01_0006.html index 553c6781..7b1c6c68 100644 --- a/docs/evs/umn/evs_01_0006.html +++ b/docs/evs/umn/evs_01_0006.html @@ -2,10 +2,11 @@

                          Expansion Overview

                          What Is Capacity Expansion?

                          If the capacity of an existing disk is insufficient, you can expand the disk capacity to increase the storage space.

                          -

                          Both system disks and data disks can be expanded. Currently, disk capacities can be expanded only. Capacity reduction is not supported.

                          +

                          Both system disks and data disks can be expanded. Disk capacity can be expanded only, but cannot be reduced.

                          How to Expand the Disk Capacity?

                          A capacity expansion operation includes the following steps:

                          1. Expand the disk capacity on the management console.
                          2. Log in to the server and extend the disk partition and file system.
                          +

                          Figure 1 Capacity expansion procedure

                          Expand the Disk Capacity on the Management Console

                          Choose a proper expansion method based on the disk status.
                    - - @@ -38,7 +39,7 @@ -

                    Related Operations

                    For more expansion FAQs, see Capacity Expansion.

                    +

                    Related Operations

                    For more expansion FAQs, see Capacity Expansion.

                    diff --git a/docs/evs/umn/evs_01_0007.html b/docs/evs/umn/evs_01_0007.html index 0d897c53..9188125b 100644 --- a/docs/evs/umn/evs_01_0007.html +++ b/docs/evs/umn/evs_01_0007.html @@ -6,19 +6,19 @@

                    Constraints

                    • Currently, disk capacities can only be expanded, but cannot be reduced.
                    • When expanding an In-use disk, the server containing this disk must be in the Running or Stopped state.
                    • A shared disk cannot be expanded in the In-use state. To expand a shared In-use disk, you must detach it from all its servers, wait until its status changes to Available, and then expand its capacity. For more information, see Expanding Capacity for an Available EVS Disk.
                    • Only some server OSs support capacity expansion of In-use disks. For details, see the official document of the corresponding OS.

                      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.

                    -

                    Procedure

                    1. Log in to the management console.
                    2. Click in the upper left corner and select the desired region and project.
                    3. Under Storage, click Elastic Volume Service.

                      The disk list page is displayed.

                      +

                      Procedure

                      1. Log in to the management console.
                      2. Click in the upper left corner and select the desired region and project.
                      3. Under Storage, click Elastic Volume Service.

                        The disk list page is displayed.

                      4. Determine whether to view the server information before expanding the disk.

                        • If you need to view the server information, perform the following procedure:
                          1. In the disk list, click the name of the to-be-expanded disk.

                            The disk details page is displayed.

                          2. Click the Attachments tab to view the server where the target disk has been attached.
                          3. Click Expand Capacity in the upper right corner of the page.

                            The expansion page is displayed.

                          -
                        • If you do not need to view the server information, perform the following procedure:
                          1. In the disk list, locate the row that contains the target disk and click Expand Capacity in the Operation column.

                            The expansion page is displayed.

                            +
                          2. If you do not need to view the server information, perform the following procedure:
                            1. In the disk list, locate the row that contains the target disk and click Expand Capacity in the Operation column.

                              The expansion page is displayed.

                        -

                      5. Set the Add Capacity (GB) parameter and click Next.
                      6. On the Details page, check the disk information again.

                        • If you do not need to modify the specifications, click Submit to start the expansion.
                        • If you need to modify the specifications, click Previous to modify parameters.
                        +

                      7. Set the Add Capacity (GiB) parameter and click Next.
                      8. On the Details page, check the disk details.

                        • If you do not need to modify the specifications, click Submit.
                        • If you need to modify the specifications, click Previous.

                        After the specifications are submitted, go back to the disk list page.

                      9. In the disk list, view the capacity of the target disk.

                        When the disk status changes from Expanding to In-use and the disk capacity increases, the expansion has succeeded.

                        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 Expansion failed.

                        -

                      10. 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 server and extend the disk partition and file system.

                        The operation method varies depending on the server OS.

                        +

                      11. 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 server and extend the disk partition and file system.

                        The operation method varies depending on the server OS.

                      diff --git a/docs/evs/umn/evs_01_0008.html b/docs/evs/umn/evs_01_0008.html index 1cffd747..530650a3 100644 --- a/docs/evs/umn/evs_01_0008.html +++ b/docs/evs/umn/evs_01_0008.html @@ -6,13 +6,13 @@

                      Constraints

                      • Currently, disk capacities can only be expanded, but cannot be reduced.
                      • A shared disk cannot be expanded in the In-use state. To expand a shared In-use disk, you must detach it from all its servers, wait until its status changes to Available, and then expand its capacity.

                      Procedure

                      1. Log in to the management console.
                      2. Click in the upper left corner and select the desired region and project.
                      3. Under Storage, click Elastic Volume Service.

                        The disk list page is displayed.

                        -

                      4. In the disk list, locate the row that contains the target disk and click Expand Capacity in the Operation column.

                        The expansion page is displayed.

                        -

                      5. Set the Add Capacity (GB) parameter and click Next.
                      6. On the Details page, check the disk information again.

                        • If you do not need to modify the specifications, click Submit to start the expansion.
                        • If you need to modify the specifications, click Previous to modify parameters.
                        +

                      7. In the disk list, locate the row that contains the target disk and click Expand Capacity in the Operation column.

                        The expansion page is displayed.

                        +

                      8. Set the Add Capacity (GiB) parameter and click Next.
                      9. On the Details page, check the disk details.

                        • If you do not need to modify the specifications, click Submit.
                        • If you need to modify the specifications, click Previous.

                        After the specifications are submitted, go back to the disk list page.

                      10. In the disk list, view the capacity of the target disk.

                        When the disk status changes from Expanding to Available and the disk capacity increases, the expansion has succeeded.

                        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 Expansion failed.

                        -

                      11. Attach the disk to the server. For details, see Attach an EVS Disk.
                      12. 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 server and extend the disk partition and file system.

                        The operation method varies depending on the server OS.

                        +

                      13. Attach the disk to the server. For details, see Attach an EVS Disk.
                      14. 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 server and extend the disk partition and file system.

                        The operation method varies depending on the server OS.

                      diff --git a/docs/evs/umn/evs_01_0009.html b/docs/evs/umn/evs_01_0009.html index 6d4dcbd8..3586cbe3 100644 --- a/docs/evs/umn/evs_01_0009.html +++ b/docs/evs/umn/evs_01_0009.html @@ -1,15 +1,15 @@ -

                      Managing an Encrypted EVS Disk

                      -

                      Relationships Between Encrypted Disks, Backups and Snapshots

                      The encryption function can be used to encrypt system disks, data disks, backups and snapshots. The details are as follows:
                      • System disk encryption relates to the image that is used to create the server.
                        • If an encrypted image is used to create the server, encryption is enabled for the system disk by default, and the system disk and image share the same encryption method. For details, see Managing Private Images > Encrypting Images in the Image Management Service User Guide.
                        • If a non-encrypted image is used to create the server, determine whether to encrypt the system disk during the server creation. For details, see Getting Started > Creating an ECS > Step 1: Configure Basic Settings in the Elastic Cloud Server User Guide.
                        +

                        Managing Encrypted EVS Disks

                        +

                        Relationships Between Encrypted Disks, Backups and Snapshots

                        The encryption function can be used to encrypt system disks, data disks, backups and snapshots. The details are as follows:
                        • System disk encryption relies on the image that is used to create the server.
                          • If an encrypted image is used to create the server, the system disk will be encrypted by default, and the system disk and image share the same encryption method. For details, see Managing Private Images > Encrypting Images in the Image Management Service User Guide.
                          • If a non-encrypted image is used to create the server, you can determine whether to encrypt the system disk during the server creation. For details, see Getting Started > Creating an ECS > Step 1: Configure Basic Settings in the Elastic Cloud Server User Guide.
                        • 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.
                        • 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.
                        • 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.
                        • If a snapshot is created for a disk, the encryption attribute of the snapshot is the same as that of the disk.
                        -

                        Creating an Encrypted EVS Disk

                        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.

                        +

                        Creating an Encrypted EVS Disk

                        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.

                        For details about how to create an encrypted disk, see Create an EVS Disk.

                        Detaching an Encrypted EVS Disk

                        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.

                        -

                        The restoration method varies depending on the current CMK status. For details, see EVS Disk Encryption.

                        +

                        The restoration method varies depending on the CMK status. For details, see EVS Encryption.

                        If the CMK is available, the disk can be detached and re-attached, and data on the disk will not be lost.

                        For details about how to detach an encrypted disk, see Detaching a Data Disk.

                        diff --git a/docs/evs/umn/evs_01_0010.html b/docs/evs/umn/evs_01_0010.html index 71f9eac2..52a19974 100644 --- a/docs/evs/umn/evs_01_0010.html +++ b/docs/evs/umn/evs_01_0010.html @@ -1,6 +1,6 @@ -

                        Managing a Shared EVS Disk

                        +

                        Managing Shared EVS Disks

                        How to Use Shared VBD and SCSI Disks?

                        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.
                        • 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.
                        • Shared SCSI EVS disks: These EVS disks support SCSI reservations.
                          • 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.
                          • 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.

                          Concepts of the anti-affinity ECS group and SCSI reservations:

                          @@ -13,9 +13,9 @@

                          For details about how to attach a shared EVS disk, see Attaching a Shared Disk.

                        Deleting a Shared EVS Disk

                        Because a shared EVS disk can be attached to multiple servers, ensure that the shared EVS disk is detached from all the servers before deletion.

                        -

                        For details about how to delete a shared EVS disk, see Deleting an EVS Disk.

                        +

                        For details about how to delete a shared EVS disk, see Deleting EVS Disks.

                        -

                        Expanding a Shared EVS Disk

                        Shared EVS disks must be expanded when they are in the Available state. For details, see Expanding Capacity for an Available EVS Disk.

                        +

                        Expanding a Shared EVS Disk

                        Shared EVS disks must be expanded when they are in the Available state. For details, see Expanding Capacity for an In-use EVS Disk.

                        Related Operations

                        For more disk sharing FAQs, see Sharing.

                        diff --git a/docs/evs/umn/evs_01_0011.html b/docs/evs/umn/evs_01_0011.html index f95e35fa..85d30c14 100644 --- a/docs/evs/umn/evs_01_0011.html +++ b/docs/evs/umn/evs_01_0011.html @@ -5,14 +5,14 @@

                        Constraints

                        • The snapshot status must be Available or Error.
                        • If a disk is deleted, all the snapshots created for this disk will also be deleted.
                        • If a snapshot is deleted, disks rolled back and created from this snapshot are not affected.
                        • 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.
                        -

                        Procedure

                        1. Log in to the management console.
                        2. Click in the upper left corner and select the desired region and project.
                        3. Under Storage, click Elastic Volume Service.
                        4. In the navigation tree on the left, choose Elastic Volume Service > Snapshots.

                          The snapshot list page is displayed.

                          -

                        5. In the snapshot list, locate the row that contains the target snapshot and click Delete in the Operation column.
                        6. (Optional) If multiple snapshots are to be deleted, select in front of each snapshot and click Delete in the upper area of the list.
                        7. In the displayed dialog box, confirm the information and click Yes.

                          If the snapshot is no longer displayed in the snapshot list, the snapshot is deleted successfully.

                          +

                          Procedure

                          1. Log in to the management console.
                          2. Click in the upper left corner and select the desired region and project.
                          3. Under Storage, click Elastic Volume Service.
                          4. In the navigation pane on the left, choose Elastic Volume Service > Snapshots.

                            The snapshot list page is displayed.

                            +

                          5. In the snapshot list, locate the row that contains the target snapshot and click Delete in the Operation column.
                          6. (Optional) If multiple snapshots are to be deleted, select in front of each snapshot and click Delete in the upper area of the list.
                          7. In the displayed dialog box, confirm the information and click Yes.

                            If the snapshot is no longer displayed in the snapshot list, the snapshot is deleted successfully.

                        diff --git a/docs/evs/umn/evs_01_0012.html b/docs/evs/umn/evs_01_0012.html index 28e86bbb..b05dfe73 100644 --- a/docs/evs/umn/evs_01_0012.html +++ b/docs/evs/umn/evs_01_0012.html @@ -5,13 +5,13 @@

                        Constraints

                        • A snapshot can be rolled back only to its source disk. Rollback to another disk is not possible.
                        • A snapshot can be rolled back only when the snapshot status is Available and the source disk status is Available (not attached to any server) or Rollback failed.
                        -

                        Procedure

                        1. Log in to the management console.
                        2. Click in the upper left corner and select the desired region and project.
                        3. Under Storage, click Elastic Volume Service.
                        4. In the navigation tree on the left, choose Elastic Volume Service > Snapshots.

                          The snapshot list page is displayed.

                          +

                          Procedure

                          1. Log in to the management console.
                          2. Click in the upper left corner and select the desired region and project.
                          3. Under Storage, click Elastic Volume Service.
                          4. In the navigation pane on the left, choose Elastic Volume Service > Snapshots.

                            The snapshot list page is displayed.

                          5. In the snapshot list, locate the row that contains the target snapshot and click Roll Back Disk in the Operation column.
                          6. In the displayed dialog box, click Yes.
                          7. The snapshot list is displayed. After the snapshot status changes from Rolling back to Available, the data rollback is successful.
                        diff --git a/docs/evs/umn/evs_01_0013.html b/docs/evs/umn/evs_01_0013.html index fa7b1326..d44f1941 100644 --- a/docs/evs/umn/evs_01_0013.html +++ b/docs/evs/umn/evs_01_0013.html @@ -3,11 +3,11 @@

                        Creating an EVS Disk from a Snapshot

                        Scenarios

                        This section describes how to create an EVS disk on the Snapshots page. Besides, you can also create an EVS disk from a snapshot by specifying the Create from snapshot parameter on the disk creation page. For details, see Create an EVS Disk.

                        -

                        Constraints

                        • The disk type of the new disk is the same as that of the snapshot's source disk.
                        • The device type of the new disk is the same as that of the snapshot's source disk.
                        • The encryption attribute of the new disk is the same as that of the snapshot's source disk.
                        • A maximum of 128 disks can be created from this snapshot.
                        • Batch disk creation is not possible, and the quantity parameter must be set to 1.
                        +

                        Constraints

                        • The disk type, device type, encryption, and snapshot attributes of the new disk are the same as those of the snapshot's source disk.
                        • A maximum of 128 disks can be created from a snapshot.
                        • Batch disk creation is not possible, and the quantity parameter must be set to 1.
                        • 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.
                        -

                        Procedure

                        1. Log in to the management console.
                        2. Click in the upper left corner and select the desired region and project.
                        3. Under Storage, click Elastic Volume Service.
                        4. In the navigation tree on the left, choose Elastic Volume Service > Snapshots.

                          The snapshot list page is displayed.

                          +

                          Procedure

                          1. Log in to the management console.
                          2. Click in the upper left corner and select the desired region and project.
                          3. Under Storage, click Elastic Volume Service.
                          4. In the navigation pane on the left, choose Elastic Volume Service > Snapshots.

                            The snapshot list page is displayed.

                          5. In the snapshot list, locate the row that contains the target snapshot and click Create Disk in the Operation column.
                          6. Set the EVS disk parameters. For details, see parameter descriptions and operations provided in Create an EVS Disk.

                            A maximum of 128 disks can be created from a snapshot.

                            -

                            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.

                            +

                            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.

                          7. Click Create Now.
                          8. Go back to the disk list page and view the disk status.

                            When the disk status changes to Available, the disk is successfully created.

                          @@ -15,7 +15,7 @@
                          diff --git a/docs/evs/umn/evs_01_0014.html b/docs/evs/umn/evs_01_0014.html index 21c041aa..0238cc2b 100644 --- a/docs/evs/umn/evs_01_0014.html +++ b/docs/evs/umn/evs_01_0014.html @@ -1,7 +1,7 @@

                          Adding a Tag

                          -

                          Scenarios

                          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 Create an EVS Disk.

                          +

                          Scenarios

                          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 Create an EVS Disk.

                          Tags are used to identify the cloud resources for purposes of easy categorization and quick search.

                          • A tag is composed of a key-value pair.
                            • Key:
                              • Must be unique for each resource.
                              • Can contain a maximum of 36 characters.
                              • Can contain only digits, letters, hyphens (-), and underscores (_).
                              @@ -9,7 +9,7 @@
                          • A maximum of 10 tags can be added for an EVS disk.

                          Procedure

                          1. Log in to the management console.
                          2. Click in the upper left corner and select the desired region and project.
                          3. Under Storage, click Elastic Volume Service.

                            The disk list page is displayed.

                            -

                          4. In the disk list, locate the target disk and click the disk name.

                            The disk details page is displayed.

                            +

                          5. In the disk list, locate the desired disk and click the disk name.

                            The disk details page is displayed.

                          6. Click the Tags tab.
                          7. Click Add Tag.

                            The Add Tag page is displayed.

                          8. Enter a key and a value for a tag and click OK.

                            • Key: This parameter is mandatory.
                            • Value: This parameter is optional.

                            The Tags tab is displayed, and you can view the newly added tag.

                            diff --git a/docs/evs/umn/evs_01_0015.html b/docs/evs/umn/evs_01_0015.html index d666d6a7..66d060cf 100644 --- a/docs/evs/umn/evs_01_0015.html +++ b/docs/evs/umn/evs_01_0015.html @@ -3,8 +3,8 @@

                            Modifying a Tag

                            Scenarios

                            You can change the value of a tag for an existing disk, but cannot change the key of a tag.

                            -

                            Procedure

                            1. Log in to the management console.
                            2. Click in the upper left corner and select the desired region and project.
                            3. Under Storage, click Elastic Volume Service.

                              The disk list page is displayed.

                              -

                            4. In the disk list, locate the target disk and click on the disk name.

                              The disk details page is displayed.

                              +

                              Procedure

                              1. Log in to the management console.
                              2. Click in the upper left corner and select the desired region and project.
                              3. Under Storage, click Elastic Volume Service.

                                The disk list page is displayed.

                                +

                              4. In the disk list, locate the desired disk and click the disk name.

                                The disk details page is displayed.

                              5. Click the Tags tab.
                              6. Locate the target tag and click Edit in the Operation column.

                                The Edit Tag page is displayed.

                              7. Change the value of the tag and click OK.

                                Return to the tag list. If the tag value is changed, the modification is complete.

                              diff --git a/docs/evs/umn/evs_01_0016.html b/docs/evs/umn/evs_01_0016.html index a2cd11e0..589fa691 100644 --- a/docs/evs/umn/evs_01_0016.html +++ b/docs/evs/umn/evs_01_0016.html @@ -3,10 +3,10 @@

                              Deleting a Tag

                              Scenarios

                              If an existing tag is no longer needed, you can delete it.

                              -

                              Procedure

                              1. Log in to the management console.
                              2. Click in the upper left corner and select the desired region and project.
                              3. Under Storage, click Elastic Volume Service.

                                The disk list page is displayed.

                                -

                              4. In the disk list, locate the target disk and click the disk name.

                                The disk details page is displayed.

                                +

                                Procedure

                                1. Log in to the management console.
                                2. Click in the upper left corner and select the desired region and project.
                                3. Under Storage, click Elastic Volume Service.

                                  The disk list page is displayed.

                                  +

                                4. In the disk list, locate the desired disk and click the disk name.

                                  The disk details page is displayed.

                                5. Click the Tags tab.
                                6. Locate the target tag and click Delete in the Operation column.

                                  The Delete Tag page is displayed.

                                  -

                                7. Confirm the information and click Yes.

                                  Return to the tag list. If the tag is no longer displayed in the tag list, the deletion is successful.

                                  +

                                8. Confirm the information and click Yes.

                                  Return to the tag list. If the tag is no longer displayed in the tag list, the deletion is successful.

                              diff --git a/docs/evs/umn/evs_01_0018.html b/docs/evs/umn/evs_01_0018.html index e0936391..e6f5dd56 100644 --- a/docs/evs/umn/evs_01_0018.html +++ b/docs/evs/umn/evs_01_0018.html @@ -3,15 +3,15 @@

                              Extending Partitions and File Systems for SCSI Disks (Linux)

                              Scenarios

                              After a disk has been expanded on the management console, the disk size is enlarged, but the additional space cannot be used directly.

                              In Linux, you must allocate the additional space to an existing partition or a new partition.

                              -
                              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. +
                              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.
                              -

                              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 Managing EVS Backup. For details about snapshots, see Creating a Snapshot.

                              +

                              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 Managing EVS Backups. For details about using snapshots, see Creating a Snapshot.

                              Prerequisites

                              -

                              Creating a New MBR Partition

                              Originally, data disk /dev/sda has 50 GB and one partition (/dev/sda1), and then 50 GB is added to the disk. The following procedure shows you how to create a new MBR partition /dev/sda2 with this 50 GB.

                              +

                              Creating a New MBR Partition

                              Originally, data disk /dev/sda has 50 GiB and one partition (/dev/sda1), and then 50 GiB is added to the disk. The following procedure shows you how to create a new MBR partition /dev/sda2 with this 50 GiB.

                              1. Run the following command to view the disk partition information:

                                fdisk -l

                                Information similar to the following is displayed:
                                [root@ecs-scsi ~]# fdisk -l
                                 
                                @@ -187,7 +187,7 @@ tmpfs          tmpfs     104M     0  104M   0% /run/user/0
                                 

                                Extending an Existing MBR Partition

                                If the additional space is allocated to an existing partition, data on the disk will not be cleared but you must use umount to unmount the existing partition. In this case, services will be affected.

                                -

                                Originally, SCSI data disk /dev/sda has 100 GB and two partitions (/dev/sda1 and /dev/sda2), 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 /dev/sda2.

                                +

                                Originally, SCSI data disk /dev/sda has 100 GiB and two partitions (/dev/sda1 and /dev/sda2), 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 /dev/sda2.

                                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.

                                1. Run the following command to view the disk partition information:

                                  fdisk -l

                                  Information similar to the following is displayed:
                                  [root@ecs-scsi ~]# fdisk -l
                                  @@ -340,7 +340,7 @@ The filesystem on /dev/sda2 is now 26214400 blocks long.

                                  In this example, run the following command to create the /mnt/test mount point:

                                  mkdir /mnt/test

                                2. Run the following command to mount the partition:

                                  mount Disk partition Mount point

                                  -

                                  In this example, run the following command to mount the partition /dev/sda2 on /mnt/test:

                                  +

                                  In this example, run the following command to mount partition /dev/sda2 on /mnt/test:

                                  mount /dev/sda2 /mnt/test

                                  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.

                                  @@ -350,7 +350,7 @@ The filesystem on /dev/sda2 is now 26214400 blocks long.

                                  In this example, run the following command to create the /mnt/test mount point:

                                  mkdir /mnt/test

                                3. Run the following command to mount the partition:

                                  mount Disk partition Mount point

                                  -

                                  In this example, run the following command to mount the partition /dev/sda2 on /mnt/test:

                                  +

                                  In this example, run the following command to mount partition /dev/sda2 on /mnt/test:

                                  mount /dev/sda2 /mnt/test

                                  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.

                                  @@ -398,8 +398,8 @@ tmpfs tmpfs 104M 0 104M 0% /run/user/0
                                  [root@ecs-test-0001 ~]# blkid /dev/vdb1
                                   /dev/vdb1: UUID="0b3040e2-1367-4abb-841d-ddb0b92693df" TYPE="ext4"

                                  The UUID of the /dev/vdb1 partition is displayed.

                                  -

                                4. Run the following command to open the fstab file using the vi editor:

                                  vi /etc/fstab

                                  -

                                5. Press i to enter the editing mode.
                                6. Move the cursor to the end of the file and press Enter. Then, add the following information:

                                  UUID=0b3040e2-1367-4abb-841d-ddb0b92693df /mnt/sdc                ext4    defaults        0 2
                                  +

                                7. Run the following command to open the fstab file using the vi editor:

                                  vi /etc/fstab

                                  +

                                8. Press i to enter editing mode.
                                9. Move the cursor to the end of the file and press Enter. Then, add the following information:

                                  UUID=0b3040e2-1367-4abb-841d-ddb0b92693df /mnt/sdc                ext4    defaults        0 2

                                10. Press Esc, enter :wq, and press Enter.

                                  The system saves the configurations and exits the vi editor.

                                11. Perform the following operations to verify the automatic mounting function:

                                  1. Run the following command to unmount the partition:

                                    umount Disk partition

                                    In this example, run the following command:

                                    @@ -408,7 +408,7 @@ tmpfs tmpfs 104M 0 104M 0% /run/user/0
                                  2. Run the following command to query the file system mounting information:

                                    mount | grep Mount point

                                    In this example, run the following command:

                                    mount | grep /mnt/sdc

                                    -

                                    If information similar to the following is displayed, the automatic mounting function takes effect:

                                    +

                                    If information similar to the following is displayed, automatic mounting has been configured:

                                    root@ecs-test-0001 ~]# mount | grep /mnt/sdc
                                     /dev/vdb1 on /mnt/sdc type ext4 (rw,relatime,data=ordered)
                                  diff --git a/docs/evs/umn/evs_01_0019.html b/docs/evs/umn/evs_01_0019.html index e1efc3a4..fb9a6118 100644 --- a/docs/evs/umn/evs_01_0019.html +++ b/docs/evs/umn/evs_01_0019.html @@ -3,7 +3,7 @@

                                  Searching Disks by Tags

                                  Scenarios

                                  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.

                                  -

                                  Procedure

                                  1. Log in to the management console.
                                  2. Click in the upper left corner and select the desired region and project.
                                  3. Under Storage, click Elastic Volume Service.

                                    The disk list page is displayed.

                                    +

                                    Procedure

                                    1. Log in to the management console.
                                    2. Click in the upper left corner and select the desired region and project.
                                    3. Under Storage, click Elastic Volume Service.

                                      The disk list page is displayed.

                                    4. In the upper area of the disk list, click Search by Tag.

                                      The Search by Tag page is displayed.

                                    5. Enter or select an existing tag in the text box under Search by Tag.
                                    6. (Optional) If disks containing multiple tags need to be queried, click to add tags.

                                      A maximum of 10 tags can be added at a time.

                                      For the added tags, you can delete them individually or click Reset to clear all of them.

                                      diff --git a/docs/evs/umn/evs_01_0021.html b/docs/evs/umn/evs_01_0021.html index e45afe36..e10185a2 100644 --- a/docs/evs/umn/evs_01_0021.html +++ b/docs/evs/umn/evs_01_0021.html @@ -1,12 +1,12 @@

                                      EVS Backup

                                      -

                                      What Is EVS Backup?

                                      Cloud Disk Backup provided by Cloud Backup and Recovery (CBR) allows you to create backups for your EVS disks while servers 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.

                                      +

                                      What Is EVS Backup?

                                      Cloud Disk Backup provided by Cloud Backup and Recovery (CBR) allows you to create backups for your EVS disks while servers 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.

                                      For more information, see the Cloud Backup and Recovery User Guide.

                                      Application Scenarios

                                      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.

                                      -

                                      Usage Instructions

                                      For how to back up EVS disks, see Managing EVS Backup or the Cloud Backup and Recovery User Guide.

                                      +

                                      Usage Instructions

                                      For how to back up EVS disks, see Managing EVS Backups or the Cloud Backup and Recovery User Guide.

                                      diff --git a/docs/evs/umn/evs_01_0024.html b/docs/evs/umn/evs_01_0024.html index 28fb68b1..961cb640 100644 --- a/docs/evs/umn/evs_01_0024.html +++ b/docs/evs/umn/evs_01_0024.html @@ -6,7 +6,7 @@

                                      EVS replication APIs have been deprecated. If you need to use the replication function, see Storage Disaster Recovery Service User Guide and Storage Disaster Recovery Service API Reference.

                                      -

                                      Procedure

                                      1. Log in to the management console.
                                      2. Click in the upper left corner and select the desired region and project.
                                      3. Under Computing, click Elastic Cloud Server.

                                        The Elastic Cloud Server page is displayed.

                                        +

                                        Procedure

                                        1. Log in to the management console.
                                        2. Click in the upper left corner and select the desired region and project.
                                        3. Under Computing, click Elastic Cloud Server.

                                          The Elastic Cloud Server page is displayed.

                                        4. Click the name of the production ECS.

                                          The ECS details page is displayed.

                                        5. 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 Table 1.

                                          The listed parameter values are for reference only.

                                          diff --git a/docs/evs/umn/evs_01_0026.html b/docs/evs/umn/evs_01_0026.html index d4848f1f..24d4d95b 100644 --- a/docs/evs/umn/evs_01_0026.html +++ b/docs/evs/umn/evs_01_0026.html @@ -9,7 +9,7 @@

                                          Prerequisites

                                          You have obtained the VPC, subnet, MAC address, and virtual IP address of the production server. For details, see Collecting ECS Information (Deprecated).

                                          Procedure

                                          The following operations are for reference only. For details, see Assigning a Virtual IP Address in the Virtual Private Cloud User Guide.

                                          -
                                          1. Log in to the management console.
                                          2. Click in the upper left corner and select the desired region and project.
                                          3. Under Computing, click Elastic Cloud Server.

                                            The Elastic Cloud Server page is displayed.

                                            +
                                            1. Log in to the management console.
                                            2. Click in the upper left corner and select the desired region and project.
                                            3. Under Computing, click Elastic Cloud Server.

                                              The Elastic Cloud Server page is displayed.

                                            4. In the ECS list, locate the production ECS and click the ECS name.

                                              The ECS details page is displayed.

                                            5. On the ECS details page, locate the VPC and click the VPC name.

                                              The Virtual Private Cloud page is displayed.

                                            6. In the VPC list, locate the VPC of the production ECS and click the VPC name.

                                              The VPC details page is displayed.

                                              @@ -19,8 +19,8 @@
                                            7. If no, perform the following operations:
                                              1. Click Assign Virtual IP Address.

                                                After the application succeeds, you can view the virtual IP address in the virtual IP address list.

                                                When assigning the virtual IP address, you can select the Automatic or Manual mode based on your service requirements.

                                                -
                                              2. Locate the row that contains the virtual IP address and click Bind to Server in the Operation column. On the displayed page, bind the virtual IP address to the NIC of the production server.

                                                After the virtual IP address is bound with the production server, the subnet details page is displayed.

                                                -
                                              3. Locate the row that contains the virtual IP address and click Bind to Server in the Operation column. On the displayed page, bind the virtual IP address to the NIC of the DR server.

                                                After the virtual IP address is bound with the DR server, the subnet details page is displayed.

                                                +
                                              4. Locate the row that contains the virtual IP address and click Bind to Server in the Operation column. On the displayed page, bind the virtual IP address to the NIC of the production server.

                                                After the virtual IP address is bound with the production server, the subnet details page is displayed.

                                                +
                                              5. Locate the row that contains the virtual IP address and click Bind to Server in the Operation column. On the displayed page, bind the virtual IP address to the NIC of the DR server.

                                                After the virtual IP address is bound with the DR server, the subnet details page is displayed.

                    4. 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.

                      An example is provided as follows:
                      • Subnet: 192.168.0.0/24
                      • Bound server (NIC): ecs-001 (192.168.0.176)
                      @@ -32,7 +32,7 @@

                      You can obtain the NIC name using the NIC IP address recorded in 9. In this example, the NIC name is eth0.

                    5. Run the following command to switch to the directory containing NIC configuration files:

                      cd /etc/sysconfig/network-scripts

                    6. Run the following command to copy NIC configuration file eth0 and change its name to eth0:1:

                      cp eth0 eth0:1

                      -
                    7. Perform the following operations to modify the configuration parameters of eth0:1 using the vi editor:
                      1. Run the following command to open the ifcfg-eth0:1 file:

                        vi ifcfg-eth0:1

                        +
                      2. Perform the following operations to modify the configuration parameters of eth0:1 using the vi editor:
                        1. Run the following command to open the ifcfg-eth0:1 file:

                          vi ifcfg-eth0:1

                        2. Press i to enter editing mode.
                        3. Configure the parameters according to the following example:
                          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
                          -
                          Configuration descriptions of the NAME, IPADDR, and NETMASK fields:
                          • NAME: Specifies the NIC name recorded in 10.b.
                          • IPADDR: Specifies the NIC IP address recorded in 9.
                          • NETMASK: Specifies the subnet recorded in 9.

                            In this example, the subnet mask has 24 bits. Therefore, enter 255.255.255.0 for NETMASK.

                            +
                            Configuration descriptions of the NAME, IPADDR, and NETMASK fields:
                            • NAME: Specifies the NIC name recorded in 10.b.
                            • IPADDR: Specifies the NIC IP address recorded in 9.
                            • NETMASK: Specifies the subnet recorded in 9.

                              In this example, the subnet mask has 24 bits. Therefore, enter 255.255.255.0 for NETMASK.

                            -
                          • Press Esc, enter :wq, and press Enter.

                            The system saves the configurations and exits the vi editor.

                            +
                          • Press Esc, enter :wq, and press Enter.

                            The system saves the configurations and exits the vi editor.

                      3. Run the following command to delete unnecessary NIC files from the /etc/sysconfig/network-scripts directory:

                        rm Name of the unnecessary NIC file

                        For example, run the following command:

                        @@ -52,18 +52,18 @@ NETMASK=255.255.255.0

                        Before deleting the unnecessary NIC files, you are advised to back up the files.

                        If multiple unnecessary NIC files exist, delete them individually. Ensure that the /etc/sysconfig/network-scripts directory contains only the in-use NIC file.

                        -
                      4. Run the following command to check whether the 70-persistent-ipoib.rules file exists in the /etc/udev/rules.d/ directory:
                        ls /etc/udev/rules.d/70-persistent-ipoib.rules
                        • If yes, use the vi editor to configure the NIC information, including the NIC name and MAC address, for production and DR servers.
                          1. Run the following command to open the 70-persistent-ipoib.rules file:

                            vi /etc/udev/rules.d/70-persistent-ipoib.rules

                            +
                          2. Run the following command to check whether the 70-persistent-ipoib.rules file exists in the /etc/udev/rules.d/ directory:
                            ls /etc/udev/rules.d/70-persistent-ipoib.rules
                            • If yes, use the vi editor to configure the NIC information, including the NIC name and MAC address, for production and DR servers.
                              1. Run the following command to open the 70-persistent-ipoib.rules file:

                                vi /etc/udev/rules.d/70-persistent-ipoib.rules

                              2. Press i to enter editing mode.
                              3. Add NIC information for the DR server based on that of the production server. For details, see the following example:
                                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"
                                -

                                Configuration descriptions of the ATTR{address} and NAME fields:

                                -
                                • ATTR{address}: specifies the MAC address of server's NIC.
                                • NAME: Specifies the NIC name recorded in 10.b.

                                  a. Ensure that the NAME (NIC name) values of the production and DR servers are consistent. The ATTR{address} (MAC address) value can be obtained in Collecting ECS Information (Deprecated).

                                  +

                                  Configuration descriptions of the ATTR{address} and NAME fields:

                                  +
                                  • ATTR{address}: specifies the MAC address of server's NIC.
                                  • NAME: Specifies the NIC name recorded in 10.b.

                                    a. Ensure that the NAME (NIC name) values of the production and DR servers are consistent. The ATTR{address} (MAC address) value can be obtained in Collecting ECS Information (Deprecated).

                                    b. Replace {mac} with the MAC address during operation.

                                  -
                                • Press Esc, enter :wq, and press Enter.

                                  The system saves the configurations and exits the vi editor.

                                  +
                                • Press Esc, enter :wq, and press Enter.

                                  The system saves the configurations and exits the vi editor.

                            • If no, go to 10.h.
                            diff --git a/docs/evs/umn/evs_01_0033.html b/docs/evs/umn/evs_01_0033.html index b268d1fc..86bb6477 100644 --- a/docs/evs/umn/evs_01_0033.html +++ b/docs/evs/umn/evs_01_0033.html @@ -2,16 +2,16 @@

                            Initializing a Linux Data Disk (fdisk)

                            Scenarios

                            This section uses CentOS 7.4 64bit to describe how to initialize a data disk attached to a server running Linux and use fdisk to partition the data disk.

                            -

                            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 Introduction to Data Disk Initialization Scenarios and Partition Styles.

                            +

                            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.

                            +

                            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 Introduction to Data Disk Initialization Scenarios and Partition Styles.

                            The method for initializing a disk varies depending on the OS running on the server. This document is used for reference only. For the detailed operations and differences, see the product documents of the corresponding OS.

                            Prerequisites

                            • A data disk has been attached to a server and has not been initialized.
                            • You have logged in to the server.
                              • For how to log in to an ECS, see the Elastic Cloud Server User Guide.
                              • For how to log in to a BMS, see the Bare Metal Server User Guide.
                            -

                            Creating and Mounting a Partition

                            The following example shows you how a new primary partition can be created on a new data disk that has been attached to a server. 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 /mnt/sdc, and configured with automatic mounting at system start.

                            +

                            Creating and Mounting a Partition

                            The following example shows you how a new primary partition can be created on a new data disk that has been attached to a server. 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 /mnt/sdc, and configured with automatic mounting at system start.

                            -
                            1. Run the following command to query information about the new data disk:

                              fdisk -l

                              -
                              Information similar to the following is displayed:
                              [root@ecs-test-0001 ~]# fdisk -l
                              +
                              1. fdisk -l

                                Information similar to the following is displayed:
                                [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): 
                                -

                              2. Enter n and press Enter to create a new partition.

                                Information similar to the following is displayed:
                                Command (m for help): n
                                +

                              3. Enter n and press Enter to create a new partition.

                                Information similar to the following is displayed:
                                Command (m for help): n
                                 Partition type:
                                    p   primary (0 primary, 0 extended, 4 free)
                                    e   extended
                                @@ -66,8 +66,8 @@ First sector (2048-209715199, default 2048):
                              Using default value 2048 Last sector, +sectors or +size{K,M,G} (2048-209715199, default 209715199):
                              -

                              Last sector indicates the end sector. The value ranges from 2048 to 209715199, and the default value is 209715199.

                              -

                            2. Select the default end sector 209715199 and press Enter.

                              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.

                              +

                              Last sector indicates the end sector. The value ranges from 2048 to 209715199, and the default value is 209715199.

                              +

                            3. Select the default end sector 209715199 and press Enter.

                              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.

                              Information similar to the following is displayed:

                              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

                            4. Run the following command to create a mount point:

                              mkdir Mount point

                              In this example, run the following command to create the /mnt/sdc mount point:

                              mkdir /mnt/sdc

                              +

                              The /mnt directory exists on all Linux systems. If the mount point fails to create, it may be that the /mnt directory has been accidentally deleted. Run the mkdir -p /mnt/sdc command to create the mount point.

                              +

                            5. Run the following command to mount the new partition on the created mount point:

                              mount Disk partition Mount point

                              In this example, run the following command to mount the new partition /dev/vdb1 on /mnt/sdc:

                              mount /dev/vdb1 /mnt/sdc

                              @@ -161,8 +163,8 @@ tmpfs tmpfs 398M 0 398M 0% /run/user/0
                              [root@ecs-test-0001 ~]# blkid /dev/vdb1
                               /dev/vdb1: UUID="0b3040e2-1367-4abb-841d-ddb0b92693df" TYPE="ext4"

                              The UUID of the /dev/vdb1 partition is displayed.

                              -

                            6. Run the following command to open the fstab file using the vi editor:

                              vi /etc/fstab

                              -

                            7. Press i to enter the editing mode.
                            8. Move the cursor to the end of the file and press Enter. Then, add the following information:

                              UUID=0b3040e2-1367-4abb-841d-ddb0b92693df /mnt/sdc                ext4    defaults        0 2
                              +

                            9. Run the following command to open the fstab file using the vi editor:

                              vi /etc/fstab

                              +

                            10. Press i to enter editing mode.
                            11. Move the cursor to the end of the file and press Enter. Then, add the following information:

                              UUID=0b3040e2-1367-4abb-841d-ddb0b92693df /mnt/sdc                ext4    defaults        0 2

                            12. Press Esc, enter :wq, and press Enter.

                              The system saves the configurations and exits the vi editor.

                            13. Perform the following operations to verify the automatic mounting function:

                              1. Run the following command to unmount the partition:

                                umount Disk partition

                                In this example, run the following command:

                                @@ -171,7 +173,7 @@ tmpfs tmpfs 398M 0 398M 0% /run/user/0
                              2. Run the following command to query the file system mounting information:

                                mount | grep Mount point

                                In this example, run the following command:

                                mount | grep /mnt/sdc

                                -

                                If information similar to the following is displayed, the automatic mounting function takes effect:

                                +

                                If information similar to the following is displayed, automatic mounting has been configured:

                                root@ecs-test-0001 ~]# mount | grep /mnt/sdc
                                 /dev/vdb1 on /mnt/sdc type ext4 (rw,relatime,data=ordered)
                              diff --git a/docs/evs/umn/evs_01_0034.html b/docs/evs/umn/evs_01_0034.html index 11a37c74..a493a72a 100644 --- a/docs/evs/umn/evs_01_0034.html +++ b/docs/evs/umn/evs_01_0034.html @@ -2,13 +2,14 @@

                              Initializing a Linux Data Disk (parted)

                              Scenarios

                              This section uses CentOS 7.4 64bit to describe how to initialize a data disk attached to a server running Linux and use parted to partition the data disk.

                              -

                              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 Introduction to Data Disk Initialization Scenarios and Partition Styles.

                              +

                              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.

                              +

                              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 Introduction to Data Disk Initialization Scenarios and Partition Styles.

                              The method for initializing a disk varies depending on the OS running on the server. This document is used for reference only. For the detailed operations and differences, see the product documents of the corresponding OS.

                              Prerequisites

                              • A data disk has been attached to a server and has not been initialized.
                              • You have logged in to the server.
                                • For how to log in to an ECS, see the Elastic Cloud Server User Guide.
                                • For how to log in to a BMS, see the Bare Metal Server User Guide.
                              -

                              Creating and Mounting a Partition

                              The following example shows you how a new partition can be created on a new data disk that has been attached to a server. 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 /mnt/sdc, and configured automatic mounting at system start.

                              +

                              Creating and Mounting a Partition

                              The following example shows you how a new partition can be created on a new data disk that has been attached to a server. 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 /mnt/sdc, and configured with automatic mounting at system start.

                              1. Run the following command to query information about the new data disk:

                                lsblk

                                Information similar to the following is displayed:
                                root@ecs-test-0001 ~]# lsblk
                                @@ -40,8 +41,8 @@ Disk Flags:
                                 

                              2. Run the following command to set the disk partition style:

                                mklabel Disk partition style

                                In this example, run the following command to set the partition style to GPT: (Disk partition styles can be MBR or GPT.)

                                mklabel gpt

                                -

                                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.

                                -

                                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.

                                +

                                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.

                                +

                                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.

                              3. Enter p and press Enter to view the disk partition style.

                                Information similar to the following is displayed:
                                (parted) mklabel gpt
                                 (parted) p
                                @@ -120,6 +121,8 @@ Writing superblocks and filesystem accounting information: done

                              4. Run the following command to create a mount point:

                                mkdir Mount point

                                In this example, run the following command to create the /mnt/sdc mount point:

                                mkdir /mnt/sdc

                                +

                                The /mnt directory exists on all Linux systems. If the mount point fails to create, it may be that the /mnt directory has been accidentally deleted. Run the mkdir -p /mnt/sdc command to create the mount point.

                                +

                              5. Run the following command to mount the new partition on the created mount point:

                                mount Disk partition Mount point

                                In this example, run the following command to mount the new partition /dev/vdb1 on /mnt/sdc:

                                mount /dev/vdb1 /mnt/sdc

                                @@ -149,8 +152,8 @@ tmpfs tmpfs 398M 0 398M 0% /run/user/0
                                [root@ecs-test-0001 ~]# blkid /dev/vdb1
                                 /dev/vdb1: UUID="0b3040e2-1367-4abb-841d-ddb0b92693df" TYPE="ext4"

                                The UUID of the /dev/vdb1 partition is displayed.

                                -

                              6. Run the following command to open the fstab file using the vi editor:

                                vi /etc/fstab

                                -

                              7. Press i to enter the editing mode.
                              8. Move the cursor to the end of the file and press Enter. Then, add the following information:

                                UUID=0b3040e2-1367-4abb-841d-ddb0b92693df /mnt/sdc                ext4    defaults        0 2
                                +

                              9. Run the following command to open the fstab file using the vi editor:

                                vi /etc/fstab

                                +

                              10. Press i to enter editing mode.
                              11. Move the cursor to the end of the file and press Enter. Then, add the following information:

                                UUID=0b3040e2-1367-4abb-841d-ddb0b92693df /mnt/sdc                ext4    defaults        0 2

                              12. Press Esc, enter :wq, and press Enter.

                                The system saves the configurations and exits the vi editor.

                              13. Perform the following operations to verify the automatic mounting function:

                                1. Run the following command to unmount the partition:

                                  umount Disk partition

                                  In this example, run the following command:

                                  @@ -159,7 +162,7 @@ tmpfs tmpfs 398M 0 398M 0% /run/user/0
                                2. Run the following command to query the file system mounting information:

                                  mount | grep Mount point

                                  In this example, run the following command:

                                  mount | grep /mnt/sdc

                                  -

                                  If information similar to the following is displayed, the automatic mounting function takes effect:

                                  +

                                  If information similar to the following is displayed, automatic mounting has been configured:

                                  root@ecs-test-0001 ~]# mount | grep /mnt/sdc
                                   /dev/vdb1 on /mnt/sdc type ext4 (rw,relatime,data=ordered)
                                diff --git a/docs/evs/umn/evs_01_0035.html b/docs/evs/umn/evs_01_0035.html index 0974fb4b..62367144 100644 --- a/docs/evs/umn/evs_01_0035.html +++ b/docs/evs/umn/evs_01_0035.html @@ -61,8 +61,8 @@
                    Table 1 Impact of CMK unavailability

                    CMK Status

                    Impact

                    +

                    Impact

                    How to Restore

                    +

                    How to Restore

                    Disabled

                    +

                    Disabled

                    • For an encrypted disk already attached:

                      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.

                      -
                    • For an encrypted disk not attached:

                      The disk cannot be attached anymore.

                      +
                    • For an encrypted disk already attached:

                      Reads and writes to the disk are normal unless the disk is detached. Once detached, the disk cannot be attached again.

                      +
                    • For an encrypted disk not attached:

                      The disk cannot be attached anymore.

                    Enable the CMK. For details, see Managing CMKs > Enabling One or More CMKs in the Key Management Service User Guide.

                    +

                    Enable the CMK. For details, see Managing CMKs > Enabling One or More CMKs in the Key Management Service User Guide.

                    Scheduled deletion

                    +

                    Scheduled deletion

                    Cancel the scheduled deletion for the CMK. For details, see Managing CMKs > Canceling the Scheduled Deletion of One or More CMKs in the Key Management Service User Guide.

                    +

                    Cancel the scheduled deletion for the CMK. For details, see Managing CMKs > Canceling the Scheduled Deletion of One or More CMKs in the Key Management Service User Guide.

                    Deleted

                    +

                    Deleted

                    Data on the disks can never be restored.

                    +

                    Data on the disks can never be restored.

                    Disk capacity ≤ 2 TB

                    +

                    Disk capacity ≤ 2 TiB

                    Disk capacity > 2 TB

                    +

                    Disk capacity > 2 TiB

                    -

                    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.

                    +

                    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 cleared during this change.

                    Method 1: Check Partition Style and File System Format Using fdisk

                    1. Run the following command to view all the disks attached to the server:

                      lsblk

                      @@ -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
                    -

                    In this example, data disk /dev/vdb already has partition /dev/vdb1 before capacity expansion, and the additional 50 GB added has not been allocated yet. Therefore, /dev/vdb has 150 GB, and /dev/vdb1 has 100 GB.

                    +

                    In this example, data disk /dev/vdb already has partition /dev/vdb1 before capacity expansion, and the additional 50 GiB added has not been allocated yet. Therefore, /dev/vdb has 150 GiB, and /dev/vdb1 has 100 GiB.

                  • Run the following command to view the current disk partition style:

                    fdisk -l

                    Information similar to the following is displayed:
                    [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
                    -

                    In this example, data disk /dev/vdb already has partition /dev/vdb1 before capacity expansion, and the additional 50 GB added has not been allocated yet. Therefore, /dev/vdb has 150 GB, and /dev/vdb1 has 100 GB.

                    +

                    In this example, data disk /dev/vdb already has partition /dev/vdb1 before capacity expansion, and the additional 50 GiB added has not been allocated yet. Therefore, /dev/vdb has 150 GiB, and /dev/vdb1 has 100 GiB.

                  • Run the following command and enter p to view the disk partition style:

                    parted Disk

                    For example, run the following command to view /dev/vdb's partition style:

                    parted /dev/vdb

                    diff --git a/docs/evs/umn/evs_01_0036.html b/docs/evs/umn/evs_01_0036.html index 584ca285..8fa877d8 100644 --- a/docs/evs/umn/evs_01_0036.html +++ b/docs/evs/umn/evs_01_0036.html @@ -5,14 +5,19 @@
                    A system disk must be created during a server creation and is automatically attached. In the disk list, the function of such disks is displayed as System disk, and the status is displayed as In-use. After a system disk is detached from a server, the disk function changes to Bootable disk, and the status changes to Available.

                    Bootable disks are the system disks detached from servers. A bootable disk can be re-attached to a server and be used as a system disk or data disk depending on the device name selected.

                    +

                    This section describes how to attach a non-shared disk. A non-shared disk can be attached to one server only.

                  • +

                    Constraints

                    Cloud servers created from ISO images are only used for OS installation. They have limited functions and cannot have EVS disks attached.

                    +

                    Attaching the Disk on the EVS Console

                    1. Log in to the management console.
                    2. Click in the upper left corner and select the desired region and project.
                    3. Under Storage, click Elastic Volume Service.

                      The disk list page is displayed.

                      -

                    4. Locate the target disk in the list and click Attach.

                      The Attach Disk dialog box is displayed, as shown in Figure 1.
                      Figure 1 Attach Disk dialog box
                      +

                    5. Locate the target disk in the list and click Attach.

                      The Attach Disk dialog box is displayed.
                      Figure 1 Attach Disk dialog box

                    6. Select the server and then select a device name from the drop-down list. Ensure that the disk and server are in the same AZ.
                    7. Click OK to return to the disk list page. The status of the disk is Attaching, indicating that the disk is being attached to the server. When the disk status changes to In-use, the disk is successfully attached.
                    8. Initialize the disk.

                      After the disk has been attached to a server, the disk can be used only after you have initialized it. For details, see Introduction to Data Disk Initialization Scenarios and Partition Styles.

                    +

                    Follow-Up Operations

                    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 Introduction to Data Disk Initialization Scenarios and Partition Styles.

                    +