diff --git a/docs/evs/umn/ALL_META.TXT.json b/docs/evs/umn/ALL_META.TXT.json index 3851cc081..2083fb647 100644 --- a/docs/evs/umn/ALL_META.TXT.json +++ b/docs/evs/umn/ALL_META.TXT.json @@ -5,18 +5,15 @@ { "uri":"evs_01_0119.html", "node_id":"evs_01_0119.xml", - "product_code":"evs", + "product_code":"", "code":"1", "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", + "doc_type":"", "kw":"Overview", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"Overview", @@ -25,18 +22,15 @@ { "uri":"en-us_topic_0014580741.html", "node_id":"en-us_topic_0014580741.xml", - "product_code":"evs", + "product_code":"", "code":"2", - "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", + "des":"Elastic Volume Service (EVS) offers scalable block storage for cloud servers. EVS disks provide high reliability, high performance, and come with a variety of disk types.", + "doc_type":"", "kw":"What Is EVS?,Overview,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"What Is EVS?", @@ -45,199 +39,189 @@ { "uri":"en-us_topic_0014580744.html", "node_id":"en-us_topic_0014580744.xml", - "product_code":"evs", + "product_code":"", "code":"3", - "des":"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.Common ", - "doc_type":"usermanual", + "des":"EVS disks are classified based on the disk I/O performance. EVS disks differ in performance and price. You can choose whichever disk type that is the best fit for your ap", + "doc_type":"", "kw":"Disk Types and Performance,Overview,User Guide", "search_title":"", "metedata":[ { - "IsMulti":"Yes", - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"Disk Types and Performance", "githuburl":"" }, { - "uri":"en-us_topic_0052554220.html", - "node_id":"en-us_topic_0052554220.xml", + "uri":"evs_01_1137.html", + "node_id":"evs_01_1137.xml", "product_code":"evs", "code":"4", - "des":"There are two EVS device types: Virtual Block Device (VBD) and Small Computer System Interface (SCSI).VBD is the default EVS device type. VBD EVS disks support only basic", + "des":"General Purpose SSD V2 is a next-generation General Purpose SSD disk type. You can buy General Purpose SSD V2 disks of a given capacity with the IOPS and throughput tailo", "doc_type":"usermanual", - "kw":"Device Types and Usage Instructions,Overview,User Guide", + "kw":"General Purpose SSD V2 Disks,Overview,User Guide", "search_title":"", "metedata":[ { "prodname":"evs", + "opensource":"false;true", "documenttype":"usermanual", - "opensource":"true", + "IsMulti":"Yes", "IsBot":"Yes" } ], - "title":"Device Types and Usage Instructions", + "title":"General Purpose SSD V2 Disks", + "githuburl":"" + }, + { + "uri":"en-us_topic_0052554220.html", + "node_id":"en-us_topic_0052554220.xml", + "product_code":"", + "code":"5", + "des":"There are two EVS device types: Virtual Block Device (VBD) and Small Computer System Interface (SCSI).VBD is the default EVS device type. VBD EVS disks support only basic", + "doc_type":"", + "kw":"Device Types,Overview,User Guide", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"Device Types", "githuburl":"" }, { "uri":"en-us_topic_0032860759.html", "node_id":"en-us_topic_0032860759.xml", - "product_code":"evs", - "code":"5", - "des":"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 attach", - "doc_type":"usermanual", - "kw":"Shared EVS Disks and Usage Instructions,Overview,User Guide", + "product_code":"", + "code":"6", + "des":"Disk sharing allows you to create shared EVS disks. Shared EVS disks are block storage devices that support concurrent read/write operations and can be attached to multip", + "doc_type":"", + "kw":"Disk Sharing,Overview,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], - "title":"Shared EVS Disks and Usage Instructions", + "title":"Disk Sharing", "githuburl":"" }, { "uri":"evs_01_0001.html", "node_id":"evs_01_0001.xml", - "product_code":"evs", - "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 Encryption,Overview,User Guide", + "product_code":"", + "code":"7", + "des":"EVS enables you to encrypt data on newly created disks as required.It uses the industry-standard XTS-AES-256 cryptographic algorithm and keys to encrypt EVS disks. Keys u", + "doc_type":"", + "kw":"Disk Encryption,Overview,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], - "title":"EVS Encryption", + "title":"Disk Encryption", "githuburl":"" }, { "uri":"evs_01_0021.html", "node_id":"evs_01_0021.xml", - "product_code":"evs", - "code":"7", + "product_code":"", + "code":"8", "des":"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 d", - "doc_type":"usermanual", - "kw":"EVS Backup,Overview,User Guide", + "doc_type":"", + "kw":"Disk Backup,Overview,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], - "title":"EVS Backup", + "title":"Disk Backup", "githuburl":"" }, { - "uri":"en-us_topic_0066809008.html", - "node_id":"en-us_topic_0066809008.xml", - "product_code":"evs", - "code":"8", - "des":"An EVS snapshot is a complete copy or image of the disk data at a specific point in time. Snapshots can be used as a disaster recovery (DR) approach, and you can use snap", - "doc_type":"usermanual", - "kw":"EVS Snapshot,Overview,User Guide", + "uri":"evs_01_2722.html", + "node_id":"evs_01_2722.xml", + "product_code":"", + "code":"9", + "des":"A snapshot is a complete copy or image of the disk data taken at a specific time. Snapshot is a major DR approach, and you can use a snapshot to restore disk data to the ", + "doc_type":"", + "kw":"Disk Snapshot,Overview,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], - "title":"EVS Snapshot", + "title":"Disk Snapshot", "githuburl":"" }, { "uri":"evs_01_0048.html", "node_id":"evs_01_0048.xml", - "product_code":"evs", - "code":"9", - "des":"Both EVS backups and EVS snapshots provide redundancies for improved disk data reliability. Table 1 lists the differences between them.", - "doc_type":"usermanual", + "product_code":"", + "code":"10", + "des":"Both disk backups and disk snapshots provide redundancies for improved disk data reliability. Table 1 lists the differences between them.", + "doc_type":"", "kw":"Differences Between EVS Backups and EVS Snapshots,Overview,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"Differences Between EVS Backups and EVS Snapshots", "githuburl":"" }, - { - "uri":"evs_01_0020.html", - "node_id":"evs_01_0020.xml", - "product_code":"evs", - "code":"10", - "des":"If your services or disk data demands high reliability, you can use the cross-AZ replication feature provided by EVS. You can create a disaster recovery (DR) disk for a p", - "doc_type":"usermanual", - "kw":"EVS Replication (Deprecated),Overview,User Guide", - "search_title":"", - "metedata":[ - { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" - } - ], - "title":"EVS Replication (Deprecated)", - "githuburl":"" - }, { "uri":"evs_01_0056.html", "node_id":"evs_01_0056.xml", - "product_code":"evs", + "product_code":"", "code":"11", "des":"The backend storage system of EVS employs three-copy redundancy to guarantee data reliability. With this mechanism, one piece of data is by default divided into multiple ", - "doc_type":"usermanual", + "doc_type":"", "kw":"EVS Three-Copy Redundancy,Overview,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"EVS Three-Copy Redundancy", "githuburl":"" }, + { + "uri":"evs_01_0020.html", + "node_id":"evs_01_0020.xml", + "product_code":"", + "code":"12", + "des":"If your services or disk data demands high reliability, you can use the cross-AZ replication feature provided by EVS. You can create a disaster recovery (DR) disk for a p", + "doc_type":"", + "kw":"EVS Replication (Deprecated),Overview,User Guide", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"EVS Replication (Deprecated)", + "githuburl":"" + }, { "uri":"evs_01_0086.html", "node_id":"evs_01_0086.xml", - "product_code":"evs", - "code":"12", + "product_code":"", + "code":"13", "des":"If you need to assign different permissions to employees in your enterprise to access your EVS resources, IAM is a good choice for fine-grained permissions management. IA", - "doc_type":"usermanual", + "doc_type":"", "kw":"Permissions,Overview,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"Permissions", @@ -246,38 +230,32 @@ { "uri":"evs_01_0085.html", "node_id":"evs_01_0085.xml", - "product_code":"evs", - "code":"13", - "des":"This section describes the constraints on using EVS.", - "doc_type":"usermanual", - "kw":"Constraints,Overview,User Guide", + "product_code":"", + "code":"14", + "des":"This section describes the constraints on using EVS.You can log in to the console to view default quotas. You can to apply for a larger quota if needed.", + "doc_type":"", + "kw":"Notes and Constraints,Overview,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], - "title":"Constraints", + "title":"Notes and Constraints", "githuburl":"" }, { "uri":"evs_01_0106.html", "node_id":"evs_01_0106.xml", - "product_code":"evs", - "code":"14", + "product_code":"", + "code":"15", "des":"Figure 1 shows the relationships between EVS and other services.Relationships between EVS and other services", - "doc_type":"usermanual", + "doc_type":"", "kw":"EVS and Other Services,Overview,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"EVS and Other Services", @@ -286,18 +264,15 @@ { "uri":"evs_01_0101.html", "node_id":"evs_01_0101.xml", - "product_code":"evs", - "code":"15", + "product_code":"", + "code":"16", "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", + "doc_type":"", "kw":"Basic Concepts", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"Basic Concepts", @@ -306,18 +281,15 @@ { "uri":"evs_01_0102.html", "node_id":"evs_01_0102.xml", - "product_code":"evs", - "code":"16", + "product_code":"", + "code":"17", "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", + "doc_type":"", "kw":"EVS Concepts,Basic Concepts,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"EVS Concepts", @@ -326,18 +298,15 @@ { "uri":"evs_01_0097.html", "node_id":"evs_01_0097.xml", - "product_code":"evs", - "code":"17", + "product_code":"", + "code":"18", "des":"A region and availability zone (AZ) identify the location of a data center. You can create resources in a specific region and AZ.A region is a physical data center, which", - "doc_type":"usermanual", + "doc_type":"", "kw":"Region and AZ,Basic Concepts,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"Region and AZ", @@ -346,38 +315,32 @@ { "uri":"evs_01_0120.html", "node_id":"evs_01_0120.xml", - "product_code":"evs", - "code":"18", + "product_code":"", + "code":"19", "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", + "doc_type":"", "kw":"Getting Started", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"Getting Started", "githuburl":"" }, { - "uri":"evs_01_0057.html", - "node_id":"evs_01_0057.xml", - "product_code":"evs", - "code":"19", - "des":"Figure 1 shows the EVS process overview.Process overviewEVS disks can be attached to servers and be used as system disks or data disks. For details, see Table 1.Method of", - "doc_type":"usermanual", + "uri":"evs_01_0201.html", + "node_id":"evs_01_0201.xml", + "product_code":"", + "code":"20", + "des":"Figure 1 shows the process for using EVS.Process overviewEVS disks can be attached to servers to be used as system disks or data disks. For details, see Table 1.Method of", + "doc_type":"", "kw":"Process Overview,Getting Started,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"Process Overview", @@ -386,38 +349,32 @@ { "uri":"en-us_topic_0021738346.html", "node_id":"en-us_topic_0021738346.xml", - "product_code":"evs", - "code":"20", - "des":"EVS disks can be used as system disks or data disks for servers. You can create data disks on the EVS console, or create them together with system disks on the ECS consol", - "doc_type":"usermanual", - "kw":"Create an EVS Disk,Getting Started,User Guide", + "product_code":"", + "code":"21", + "des":"You can use EVS disks as system disks or data disks for servers. You can create data disks on the EVS console, or create them together with system disks on the cloud serv", + "doc_type":"", + "kw":"Creating an EVS Disk,Getting Started,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], - "title":"Create an EVS Disk", + "title":"Creating an EVS Disk", "githuburl":"" }, { "uri":"evs_01_0107.html", "node_id":"evs_01_0107.xml", - "product_code":"evs", - "code":"21", + "product_code":"", + "code":"22", "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", + "doc_type":"", "kw":"Attach an EVS Disk", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"Attach an EVS Disk", @@ -426,18 +383,15 @@ { "uri":"evs_01_0036.html", "node_id":"evs_01_0036.xml", - "product_code":"evs", - "code":"22", + "product_code":"", + "code":"23", "des":"Separately 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 cas", - "doc_type":"usermanual", + "doc_type":"", "kw":"Attaching a Non-Shared Disk,Attach an EVS Disk,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"Attaching a Non-Shared Disk", @@ -446,18 +400,15 @@ { "uri":"evs_01_0037.html", "node_id":"evs_01_0037.xml", - "product_code":"evs", - "code":"23", + "product_code":"", + "code":"24", "des":"Separately created shared EVS disks are data disks. In the disk list, the function of such a disk is displayed as Data disk, and the status is displayed as Available. In ", - "doc_type":"usermanual", + "doc_type":"", "kw":"Attaching a Shared Disk,Attach an EVS Disk,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"Attaching a Shared Disk", @@ -466,17 +417,15 @@ { "uri":"evs_01_0058.html", "node_id":"evs_01_0058.xml", - "product_code":"evs", - "code":"24", + "product_code":"", + "code":"25", "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", + "doc_type":"", "kw":"Initialize an EVS Data Disk", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "IsBot":"Yes" + } ], "title":"Initialize an EVS Data Disk", @@ -485,18 +434,15 @@ { "uri":"evs_01_0038.html", "node_id":"evs_01_0038.xml", - "product_code":"evs", - "code":"25", + "product_code":"", + "code":"26", "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", + "doc_type":"", "kw":"Introduction to Data Disk Initialization Scenarios and Partition Styles,Initialize an EVS Data Disk,", "search_title":"", "metedata":[ { - "prodname":"evs", - "opensource":"true", - "documenttype":"usermanual", - "IsBot":"Yes" + } ], "title":"Introduction to Data Disk Initialization Scenarios and Partition Styles", @@ -505,18 +451,15 @@ { "uri":"evs_01_0108.html", "node_id":"evs_01_0108.xml", - "product_code":"evs", - "code":"26", + "product_code":"", + "code":"27", "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", + "doc_type":"", "kw":"Initializing a Windows Data Disk (Windows Server 2008),Initialize an EVS Data Disk,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "opensource":"true", - "documenttype":"usermanual", - "IsBot":"Yes" + } ], "title":"Initializing a Windows Data Disk (Windows Server 2008)", @@ -525,18 +468,15 @@ { "uri":"evs_01_0045.html", "node_id":"evs_01_0045.xml", - "product_code":"evs", - "code":"27", + "product_code":"", + "code":"28", "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", + "doc_type":"", "kw":"Initializing a Windows Data Disk (Windows Server 2019),Initialize an EVS Data Disk,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "opensource":"true", - "documenttype":"usermanual", - "IsBot":"Yes" + } ], "title":"Initializing a Windows Data Disk (Windows Server 2019)", @@ -545,18 +485,15 @@ { "uri":"evs_01_0033.html", "node_id":"evs_01_0033.xml", - "product_code":"evs", - "code":"28", + "product_code":"", + "code":"29", "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", + "doc_type":"", "kw":"Initializing a Linux Data Disk (fdisk),Initialize an EVS Data Disk,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "opensource":"true", - "documenttype":"usermanual", - "IsBot":"Yes" + } ], "title":"Initializing a Linux Data Disk (fdisk)", @@ -565,18 +502,15 @@ { "uri":"evs_01_0034.html", "node_id":"evs_01_0034.xml", - "product_code":"evs", - "code":"29", + "product_code":"", + "code":"30", "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", + "doc_type":"", "kw":"Initializing a Linux Data Disk (parted),Initialize an EVS Data Disk,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "opensource":"true", - "documenttype":"usermanual", - "IsBot":"Yes" + } ], "title":"Initializing a Linux Data Disk (parted)", @@ -585,18 +519,15 @@ { "uri":"evs_01_0087.html", "node_id":"evs_01_0087.xml", - "product_code":"evs", - "code":"30", + "product_code":"", + "code":"31", "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", + "doc_type":"", "kw":"Permissions Management", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"Permissions Management", @@ -605,18 +536,15 @@ { "uri":"evs_01_0089.html", "node_id":"evs_01_0089.xml", - "product_code":"evs", - "code":"31", - "des":"You can use IAM for fine-grained permissions control for your EVS resources. With IAM, you can:Create IAM users for workforce based on your enterprise's organizational st", - "doc_type":"usermanual", + "product_code":"", + "code":"32", + "des":"You can use IAM for fine-grained permissions control for your EVS resources. With IAM, you can:Create IAM users for personnel based on your enterprise's organizational st", + "doc_type":"", "kw":"Creating a User and Granting EVS Permissions,Permissions Management,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"Creating a User and Granting EVS Permissions", @@ -625,36 +553,32 @@ { "uri":"evs_01_0090.html", "node_id":"evs_01_0090.xml", - "product_code":"evs", - "code":"32", + "product_code":"", + "code":"33", "des":"You can create custom policies to supplement the system-defined policies of EVS. For the actions supported for custom policies, see section \"Permissions Policies and Supp", - "doc_type":"usermanual", + "doc_type":"", "kw":"EVS Custom Policies,Permissions Management,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"EVS Custom Policies", "githuburl":"" }, { - "uri":"evs_01_0201.html", - "node_id":"evs_01_0201.xml", - "product_code":"evs", - "code":"33", - "des":"Figure 1 shows the basic EVS operation process.Process overviewEVS disks can be attached to servers and be used as system disks or data disks. For details, see Table 1.Me", - "doc_type":"usermanual", + "uri":"evs_01_0057.html", + "node_id":"evs_01_0057.xml", + "product_code":"", + "code":"34", + "des":"Figure 1 shows the process for using EVS.Process of using EVSEVS disks can be attached to servers to be used as system disks or data disks. For details, see Table 1.Metho", + "doc_type":"", "kw":"Creating and Using an EVS Disk,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual" + } ], "title":"Creating and Using an EVS Disk", @@ -663,38 +587,32 @@ { "uri":"evs_01_0073.html", "node_id":"evs_01_0073.xml", - "product_code":"evs", - "code":"34", + "product_code":"", + "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":"Attaching an Existing Disk", + "doc_type":"", + "kw":"Attaching an Existing EVS Disk", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], - "title":"Attaching an Existing Disk", + "title":"Attaching an Existing EVS Disk", "githuburl":"" }, { "uri":"evs_01_0074.html", "node_id":"evs_01_0074.xml", - "product_code":"evs", - "code":"35", + "product_code":"", + "code":"36", "des":"This section describes how to attach an existing system disk.System disks can only be attached offline, which means that the server must be in the Stopped state.You can v", - "doc_type":"usermanual", - "kw":"Attaching an Existing System Disk,Attaching an Existing Disk,User Guide", + "doc_type":"", + "kw":"Attaching an Existing System Disk,Attaching an Existing EVS Disk,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"Attaching an Existing System Disk", @@ -703,18 +621,15 @@ { "uri":"evs_01_0075.html", "node_id":"evs_01_0075.xml", - "product_code":"evs", - "code":"36", - "des":"This section describes how to attach an existing non-shared disk to a server and use it as a data disk. A non-shared disk can be attached to one server only.You can view ", - "doc_type":"usermanual", - "kw":"Attaching an Existing Non-Shared Disk,Attaching an Existing Disk,User Guide", + "product_code":"", + "code":"37", + "des":"This section describes how to attach an existing non-shared disk to a server to be used as a data disk. A non-shared disk can be attached to one server only.You can view ", + "doc_type":"", + "kw":"Attaching an Existing Non-Shared Disk,Attaching an Existing EVS Disk,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"Attaching an Existing Non-Shared Disk", @@ -723,18 +638,15 @@ { "uri":"evs_01_0076.html", "node_id":"evs_01_0076.xml", - "product_code":"evs", - "code":"37", - "des":"This section describes how to attach an existing shared disk to a server and use it as a data disk.You can view the disk information in the disk list. A shared disk can b", - "doc_type":"usermanual", - "kw":"Attaching an Existing Shared Disk,Attaching an Existing Disk,User Guide", + "product_code":"", + "code":"38", + "des":"This section describes how to attach an existing shared disk to a server to be used as a data disk.You can view the disk information in the disk list. A shared disk can b", + "doc_type":"", + "kw":"Attaching an Existing Shared Disk,Attaching an Existing EVS Disk,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"Attaching an Existing Shared Disk", @@ -743,57 +655,70 @@ { "uri":"evs_01_0093.html", "node_id":"evs_01_0093.xml", - "product_code":"evs", - "code":"38", - "des":"This section describes how to view disk details, including the disk status and specifications. You can view disk details:From the EVS ConsoleFrom the Cloud Server Console", - "doc_type":"usermanual", + "product_code":"", + "code":"39", + "des":"This section describes how to view disk details, including the disk status and specifications. Two methods are as follows:Viewing Disk Details from the EVS ConsoleViewing", + "doc_type":"", "kw":"Viewing EVS Disk Details,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"Viewing EVS Disk Details", "githuburl":"" }, { - "uri":"evs_01_0059.html", - "node_id":"evs_01_0059.xml", + "uri":"evs_01_0062.html", + "node_id":"evs_01_0062.xml", "product_code":"evs", - "code":"39", - "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.", + "code":"40", + "des":"If the performance of an existing disk no longer meets your service requirements, you can change the disk type to improve the disk performance.The following table shows t", "doc_type":"usermanual", - "kw":"Disk Capacity Expansion", + "kw":"Changing the EVS Disk Type,User Guide", "search_title":"", "metedata":[ { "prodname":"evs", + "opensource":"false;true", "documenttype":"usermanual", + "IsMulti":"Yes", "IsBot":"Yes" } ], - "title":"Disk Capacity Expansion", + "title":"Changing the EVS Disk Type", + "githuburl":"" + }, + { + "uri":"evs_01_0059.html", + "node_id":"evs_01_0059.xml", + "product_code":"", + "code":"41", + "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":"", + "kw":"Expanding EVS Disk Capacity", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"Expanding EVS Disk Capacity", "githuburl":"" }, { "uri":"evs_01_0006.html", "node_id":"evs_01_0006.xml", - "product_code":"evs", - "code":"40", + "product_code":"", + "code":"42", "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. A sy", - "doc_type":"usermanual", - "kw":"Expansion Overview,Disk Capacity Expansion,User Guide", + "doc_type":"", + "kw":"Expansion Overview,Expanding EVS Disk Capacity,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "opensource":"true", - "documenttype":"usermanual", - "IsBot":"Yes" + } ], "title":"Expansion Overview", @@ -802,18 +727,15 @@ { "uri":"evs_01_0007.html", "node_id":"evs_01_0007.xml", - "product_code":"evs", - "code":"41", + "product_code":"", + "code":"43", "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 Capacity Expansion,User Guide", + "doc_type":"", + "kw":"Expanding Capacity for an In-use EVS Disk,Expanding EVS Disk Capacity,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "opensource":"true", - "documenttype":"usermanual", - "IsBot":"Yes" + } ], "title":"Expanding Capacity for an In-use EVS Disk", @@ -822,18 +744,15 @@ { "uri":"evs_01_0008.html", "node_id":"evs_01_0008.xml", - "product_code":"evs", - "code":"42", + "product_code":"", + "code":"44", "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 Capacity Expansion,User Guide", + "doc_type":"", + "kw":"Expanding Capacity for an Available EVS Disk,Expanding EVS Disk Capacity,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "opensource":"true", - "documenttype":"usermanual", - "IsBot":"Yes" + } ], "title":"Expanding Capacity for an Available EVS Disk", @@ -842,19 +761,15 @@ { "uri":"en-us_topic_0017616396.html", "node_id":"en-us_topic_0017616396.xml", - "product_code":"evs", - "code":"43", + "product_code":"", + "code":"45", "des":"After a disk is expanded on the management console, the disk size is enlarged, but the additional space cannot be used directly.In Windows, you must allocate the addition", - "doc_type":"usermanual", - "kw":"Extending Disk Partitions and File Systems (Windows Server 2008),Disk Capacity Expansion,User Guide", + "doc_type":"", + "kw":"Extending Disk Partitions and File Systems (Windows Server 2008),Expanding EVS Disk Capacity,User Gu", "search_title":"", "metedata":[ { - "prodname":"evs", - "opensource":"true", - "documenttype":"usermanual", - "IsMulti":"Yes", - "IsBot":"Yes" + } ], "title":"Extending Disk Partitions and File Systems (Windows Server 2008)", @@ -863,19 +778,15 @@ { "uri":"evs_01_0126.html", "node_id":"evs_01_0126.xml", - "product_code":"evs", - "code":"44", + "product_code":"", + "code":"46", "des":"After a disk is expanded on the management console, the disk size is enlarged, but the additional space cannot be used directly.In Windows, you must allocate the addition", - "doc_type":"usermanual", - "kw":"Extending Disk Partitions and File Systems (Windows Server 2016),Disk Capacity Expansion,User Guide", + "doc_type":"", + "kw":"Extending Disk Partitions and File Systems (Windows Server 2016),Expanding EVS Disk Capacity,User Gu", "search_title":"", "metedata":[ { - "prodname":"evs", - "opensource":"true", - "documenttype":"usermanual", - "IsMulti":"Yes", - "IsBot":"Yes" + } ], "title":"Extending Disk Partitions and File Systems (Windows Server 2016)", @@ -884,19 +795,15 @@ { "uri":"evs_01_0094.html", "node_id":"evs_01_0094.xml", - "product_code":"evs", - "code":"45", + "product_code":"", + "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", + "doc_type":"", "kw":"Extending Disk Partitions and File Systems (Linux)", "search_title":"", "metedata":[ { - "prodname":"evs", - "opensource":"true", - "documenttype":"usermanual", - "IsMulti":"Yes", - "IsBot":"Yes" + } ], "title":"Extending Disk Partitions and File Systems (Linux)", @@ -905,19 +812,15 @@ { "uri":"evs_01_0035.html", "node_id":"evs_01_0035.xml", - "product_code":"evs", - "code":"46", + "product_code":"", + "code":"48", "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", + "doc_type":"", "kw":"Partition and File System Extension Preparations (Linux),Extending Disk Partitions and File Systems ", "search_title":"", "metedata":[ { - "prodname":"evs", - "opensource":"true", - "documenttype":"usermanual", - "IsMulti":"Yes", - "IsBot":"Yes" + } ], "title":"Partition and File System Extension Preparations (Linux)", @@ -926,19 +829,15 @@ { "uri":"evs_01_0072.html", "node_id":"evs_01_0072.xml", - "product_code":"evs", - "code":"47", + "product_code":"", + "code":"49", "des":"After a disk is 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", - "doc_type":"usermanual", + "doc_type":"", "kw":"Extending Partitions and File Systems for System Disks (Linux),Extending Disk Partitions and File Sy", "search_title":"", "metedata":[ { - "prodname":"evs", - "opensource":"true", - "documenttype":"usermanual", - "IsMulti":"Yes", - "IsBot":"Yes" + } ], "title":"Extending Partitions and File Systems for System Disks (Linux)", @@ -947,19 +846,15 @@ { "uri":"evs_01_0109.html", "node_id":"evs_01_0109.xml", - "product_code":"evs", - "code":"48", + "product_code":"", + "code":"50", "des":"After a disk is 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", - "doc_type":"usermanual", + "doc_type":"", "kw":"Extending Partitions and File Systems for Data Disks (Linux),Extending Disk Partitions and File Syst", "search_title":"", "metedata":[ { - "prodname":"evs", - "opensource":"true", - "documenttype":"usermanual", - "IsMulti":"Yes", - "IsBot":"Yes" + } ], "title":"Extending Partitions and File Systems for Data Disks (Linux)", @@ -968,19 +863,15 @@ { "uri":"evs_01_0018.html", "node_id":"evs_01_0018.xml", - "product_code":"evs", - "code":"49", + "product_code":"", + "code":"51", "des":"After a disk is 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", - "doc_type":"usermanual", + "doc_type":"", "kw":"Extending Partitions and File Systems for SCSI Disks (Linux),Extending Disk Partitions and File Syst", "search_title":"", "metedata":[ { - "prodname":"evs", - "opensource":"true", - "documenttype":"usermanual", - "IsMulti":"Yes", - "IsBot":"Yes" + } ], "title":"Extending Partitions and File Systems for SCSI Disks (Linux)", @@ -989,88 +880,59 @@ { "uri":"evs_01_0002.html", "node_id":"evs_01_0002.xml", - "product_code":"evs", - "code":"50", + "product_code":"", + "code":"52", "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":"Detaching and Releasing an EVS Disk", + "doc_type":"", + "kw":"Detaching and Deleting an EVS Disk", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], - "title":"Detaching and Releasing an EVS Disk", + "title":"Detaching and Deleting an EVS Disk", "githuburl":"" }, { "uri":"evs_01_0003.html", "node_id":"evs_01_0003.xml", - "product_code":"evs", - "code":"51", - "des":"If the file system on your system disk is damaged and your server cannot be started, you can detach the system disk and attach it to another server as a data disk. After ", - "doc_type":"usermanual", - "kw":"Detaching a System Disk,Detaching and Releasing an EVS Disk,User Guide", + "product_code":"", + "code":"53", + "des":"For an attached system disk, the disk function is displayed as System disk, and the disk status is displayed as In-use in the disk list. After the system disk is detached", + "doc_type":"", + "kw":"Detaching an EVS Disk,Detaching and Deleting an EVS Disk,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], - "title":"Detaching a System Disk", - "githuburl":"" - }, - { - "uri":"evs_01_0004.html", - "node_id":"evs_01_0004.xml", - "product_code":"evs", - "code":"52", - "des":"If you want to use a data disk on another server in the same region and AZ, you can detach the data disk and then attach it to that server.If a data disk is no longer req", - "doc_type":"usermanual", - "kw":"Detaching a Data Disk,Detaching and Releasing an EVS Disk,User Guide", - "search_title":"", - "metedata":[ - { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" - } - ], - "title":"Detaching a Data Disk", + "title":"Detaching an EVS Disk", "githuburl":"" }, { "uri":"evs_01_0005.html", "node_id":"evs_01_0005.xml", - "product_code":"evs", - "code":"53", - "des":"If an EVS disk is no longer used, you can release the virtual resources by deleting it.The disk status is Available, Error, Expansion failed, Restoration failed, or Rollb", - "doc_type":"usermanual", - "kw":"Deleting EVS Disks,Detaching and Releasing an EVS Disk,User Guide", + "product_code":"", + "code":"54", + "des":"If an EVS disk is no longer used, you can delete the disk to release the virtual resources. When a disk is deleted, EVS immediately destroys the metadata to ensure that d", + "doc_type":"", + "kw":"Deleting an EVS Disk,Detaching and Deleting an EVS Disk,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], - "title":"Deleting EVS Disks", + "title":"Deleting an EVS Disk", "githuburl":"" }, { "uri":"evs_01_0111.html", "node_id":"evs_01_0111.xml", "product_code":"evs", - "code":"54", + "code":"55", "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 EVS Snapshots", @@ -1078,8 +940,9 @@ "metedata":[ { "prodname":"evs", + "opensource":"false;true", "documenttype":"usermanual", - "opensource":"true", + "IsMulti":"Yes", "IsBot":"Yes" } ], @@ -1090,80 +953,63 @@ "uri":"evs_01_0098.html", "node_id":"evs_01_0098.xml", "product_code":"evs", - "code":"55", - "des":"An EVS snapshot is a complete copy or image of the disk data at a specific point in time. Snapshots can be used as a disaster recovery (DR) approach, and you can use snap", - "doc_type":"usermanual", - "kw":"Snapshot Overview,Managing EVS Snapshots,User Guide", - "search_title":"", - "metedata":[ - { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" - } - ], - "title":"Snapshot Overview", - "githuburl":"" - }, - { - "uri":"en-us_topic_0066615262.html", - "node_id":"en-us_topic_0066615262.xml", - "product_code":"evs", "code":"56", - "des":"You can create an EVS snapshot on the management console to save the EVS disk data at a specific time point.Creating snapshots does not affect the performance of the disk", + "des":"An EVS snapshot is a complete copy or image of the disk data taken at a specific time. Snapshot is a major disaster recovery (DR) approach, and you can use a snapshot to ", "doc_type":"usermanual", - "kw":"Creating a Snapshot,Managing EVS Snapshots,User Guide", + "kw":"EVS Snapshot Overview,Managing EVS Snapshots,User Guide", "search_title":"", "metedata":[ { "prodname":"evs", + "opensource":"false;true", "documenttype":"usermanual", - "opensource":"true", + "IsMulti":"Yes", "IsBot":"Yes" } ], - "title":"Creating a Snapshot", + "title":"EVS Snapshot Overview", "githuburl":"" }, { - "uri":"evs_01_0011.html", - "node_id":"evs_01_0011.xml", + "uri":"evs_01_2720.html", + "node_id":"evs_01_2720.xml", "product_code":"evs", "code":"57", - "des":"If a snapshot is no longer needed, you can delete it to release the virtual resources.The snapshot status must be Available or Error.If a disk is deleted, all the snapsho", + "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":"Deleting a Snapshot,Managing EVS Snapshots,User Guide", + "kw":"Using EVS Snapshots", "search_title":"", "metedata":[ { "prodname":"evs", + "opensource":"false;true", "documenttype":"usermanual", - "opensource":"true", + "IsMulti":"Yes", "IsBot":"Yes" } ], - "title":"Deleting a Snapshot", + "title":"Using EVS Snapshots", "githuburl":"" }, { - "uri":"evs_01_0122.html", - "node_id":"evs_01_0122.xml", + "uri":"evs_01_2721.html", + "node_id":"evs_01_2721.xml", "product_code":"evs", "code":"58", - "des":"This section describes how to view the details of a snapshot.The snapshot list page is displayed.On the details page, view the snapshot information, such as the snapshot ", + "des":"You can create EVS snapshots to save disk data at specific time points. Before you perform any critical operation, such as a data rollback, software upgrade, or data migr", "doc_type":"usermanual", - "kw":"Viewing Details of a Snapshot,Managing EVS Snapshots,User Guide", + "kw":"Creating an EVS Snapshot,Using EVS Snapshots,User Guide", "search_title":"", "metedata":[ { "prodname":"evs", + "opensource":"false;true", "documenttype":"usermanual", - "opensource":"true", + "IsMulti":"Yes", "IsBot":"Yes" } ], - "title":"Viewing Details of a Snapshot", + "title":"Creating an EVS Snapshot", "githuburl":"" }, { @@ -1171,19 +1017,20 @@ "node_id":"evs_01_0012.xml", "product_code":"evs", "code":"59", - "des":"If data on an EVS disk is incorrect or damaged, you can roll back data from a snapshot to the source disk.Data of a snapshot can be rolled back only to its source disk. R", + "des":"If data on an EVS disk is incorrect or damaged, you can roll back data from a snapshot to the source disk.Snapshot data can only be rolled back to source EVS disks. Rollb", "doc_type":"usermanual", - "kw":"Rolling Back Data from a Snapshot,Managing EVS Snapshots,User Guide", + "kw":"Rolling Back Disk Data from a Snapshot,Using EVS Snapshots,User Guide", "search_title":"", "metedata":[ { "prodname":"evs", + "opensource":"false;true", "documenttype":"usermanual", - "opensource":"true", + "IsMulti":"Yes", "IsBot":"Yes" } ], - "title":"Rolling Back Data from a Snapshot", + "title":"Rolling Back Disk Data from a Snapshot", "githuburl":"" }, { @@ -1191,36 +1038,76 @@ "node_id":"evs_01_0013.xml", "product_code":"evs", "code":"60", - "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", + "des":"This section describes how to create an EVS disk on the Snapshots page. You can also create an EVS disk from a snapshot by specifying the Create from snapshot parameter o", "doc_type":"usermanual", - "kw":"Creating an EVS Disk from a Snapshot,Managing EVS Snapshots,User Guide", + "kw":"Creating a Disk from a Snapshot,Using EVS Snapshots,User Guide", "search_title":"", "metedata":[ { "prodname":"evs", + "opensource":"false;true", "documenttype":"usermanual", - "opensource":"true", + "IsMulti":"Yes", "IsBot":"Yes" } ], - "title":"Creating an EVS Disk from a Snapshot", + "title":"Creating a Disk from a Snapshot", + "githuburl":"" + }, + { + "uri":"evs_01_0122.html", + "node_id":"evs_01_0122.xml", + "product_code":"evs", + "code":"61", + "des":"You can check the snapshot details, including the region and AZ, source disk information, and tags.The Snapshots page is displayed.Select the snapshot and check the snaps", + "doc_type":"usermanual", + "kw":"Checking EVS Snapshot Details,Using EVS Snapshots,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"evs", + "opensource":"false;true", + "documenttype":"usermanual", + "IsMulti":"Yes", + "IsBot":"Yes" + } + ], + "title":"Checking EVS Snapshot Details", + "githuburl":"" + }, + { + "uri":"evs_01_0011.html", + "node_id":"evs_01_0011.xml", + "product_code":"evs", + "code":"62", + "des":"If you no longer require certain snapshots or the snapshot quantity reaches the maximum allowed, you can delete the snapshots.The snapshot status must be Available or Err", + "doc_type":"usermanual", + "kw":"Deleting an EVS Snapshot,Using EVS Snapshots,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"evs", + "opensource":"false;true", + "documenttype":"usermanual", + "IsMulti":"Yes", + "IsBot":"Yes" + } + ], + "title":"Deleting an EVS Snapshot", "githuburl":"" }, { "uri":"evs_01_0009.html", "node_id":"evs_01_0009.xml", - "product_code":"evs", - "code":"61", - "des":"System disk encryptionSystem disks are created along with servers and cannot be created separately. So whether a system disk is encrypted or not depends on the image sele", - "doc_type":"usermanual", + "product_code":"", + "code":"63", + "des":"EVS enables you to encrypt data on newly created disks as required.It uses the industry-standard XTS-AES-256 cryptographic algorithm and keys to encrypt EVS disks. Keys u", + "doc_type":"", "kw":"Managing Encrypted EVS Disks,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"Managing Encrypted EVS Disks", @@ -1229,18 +1116,15 @@ { "uri":"evs_01_0010.html", "node_id":"evs_01_0010.xml", - "product_code":"evs", - "code":"62", - "des":"You can create shared VBD disks or shared SCSI disks. It is recommended that you attach a shared disk to the ECSs in the same ECS group to improve service reliability.Sha", - "doc_type":"usermanual", + "product_code":"", + "code":"64", + "des":"Disk sharing allows you to create shared EVS disks. Shared EVS disks are block storage devices that support concurrent read/write operations and can be attached to multip", + "doc_type":"", "kw":"Managing Shared EVS Disks,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"Managing Shared EVS Disks", @@ -1249,38 +1133,32 @@ { "uri":"evs_01_0110.html", "node_id":"evs_01_0110.xml", - "product_code":"evs", - "code":"63", - "des":"EVS disk backups are created using the CBR service. For details, see Creating a Cloud Disk Backup in the Cloud Backup and Recovery User Guide.You can configure a backup p", - "doc_type":"usermanual", - "kw":"Managing EVS Backups,User Guide", + "product_code":"", + "code":"65", + "des":"EVS disk backups are created using the CBR service. For details, see section \"Creating a Cloud Disk Backup\" in the Cloud Backup and Recovery User Guide.You can configure ", + "doc_type":"", + "kw":"Managing EVS Disk Backups,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], - "title":"Managing EVS Backups", + "title":"Managing EVS Disk Backups", "githuburl":"" }, { "uri":"evs_01_0042.html", "node_id":"evs_01_0042.xml", - "product_code":"evs", - "code":"64", + "product_code":"", + "code":"66", "des":"EVS transfer allows you to transfer disks from one account to another. After a transfer succeeds, the ownership of the disk belongs to the target account only.Users can u", - "doc_type":"usermanual", + "doc_type":"", "kw":"Managing EVS Transfers,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"Managing EVS Transfers", @@ -1289,38 +1167,32 @@ { "uri":"evs_01_0112.html", "node_id":"evs_01_0112.xml", - "product_code":"evs", - "code":"65", + "product_code":"", + "code":"67", "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":"Manage EVS Tags", + "doc_type":"", + "kw":"Managing EVS Tags", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], - "title":"Manage EVS Tags", + "title":"Managing EVS Tags", "githuburl":"" }, { "uri":"evs_01_0099.html", "node_id":"evs_01_0099.xml", - "product_code":"evs", - "code":"66", + "product_code":"", + "code":"68", "des":"Tags identify EVS resources for purposes of easy categorization and quick search.", - "doc_type":"usermanual", - "kw":"Tag Overview,Manage EVS Tags,User Guide", + "doc_type":"", + "kw":"Tag Overview,Managing EVS Tags,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"Tag Overview", @@ -1329,18 +1201,15 @@ { "uri":"evs_01_0014.html", "node_id":"evs_01_0014.xml", - "product_code":"evs", - "code":"67", - "des":"You can add a tag for an existing EVS disk. You can also add tags during the disk creation. For details, see Create an EVS Disk.A tag is composed of a key-value pair.Key:", - "doc_type":"usermanual", - "kw":"Adding a Tag,Manage EVS Tags,User Guide", + "product_code":"", + "code":"69", + "des":"You can add a tag for an existing EVS disk. You can also add tags when creating a disk. For details, see Creating an EVS Disk.A tag consists of a tag key and a tag value.", + "doc_type":"", + "kw":"Adding a Tag,Managing EVS Tags,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"Adding a Tag", @@ -1349,18 +1218,15 @@ { "uri":"evs_01_0015.html", "node_id":"evs_01_0015.xml", - "product_code":"evs", - "code":"68", - "des":"You can change the value of a tag for an existing disk, but cannot change the key of a tag.The disk list page is displayed.The disk details page is displayed.The Edit Tag", - "doc_type":"usermanual", - "kw":"Modifying a Tag,Manage EVS Tags,User Guide", + "product_code":"", + "code":"70", + "des":"You can change the value of a tag for an existing disk, but cannot change the key of a tag.A tag consists of a tag key and a tag value. Tag rules are described as follows", + "doc_type":"", + "kw":"Modifying a Tag,Managing EVS Tags,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"Modifying a Tag", @@ -1369,18 +1235,15 @@ { "uri":"evs_01_0016.html", "node_id":"evs_01_0016.xml", - "product_code":"evs", - "code":"69", - "des":"If an existing tag is no longer needed, you can delete it.The disk list page is displayed.The disk details page is displayed.The Delete Tag page is displayed.The tag is d", - "doc_type":"usermanual", - "kw":"Deleting a Tag,Manage EVS Tags,User Guide", + "product_code":"", + "code":"71", + "des":"If an existing tag is no longer needed, you can delete it.The Elastic Volume Service page is displayed.The disk details page is displayed.The Delete Tag page is displayed", + "doc_type":"", + "kw":"Deleting a Tag,Managing EVS Tags,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"Deleting a Tag", @@ -1389,18 +1252,15 @@ { "uri":"evs_01_0019.html", "node_id":"evs_01_0019.xml", - "product_code":"evs", - "code":"70", + "product_code":"", + "code":"72", "des":"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 ", - "doc_type":"usermanual", - "kw":"Searching for Disks by Tag,Manage EVS Tags,User Guide", + "doc_type":"", + "kw":"Searching for Disks by Tag,Managing EVS Tags,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"Searching for Disks by Tag", @@ -1409,18 +1269,15 @@ { "uri":"evs_01_0023.html", "node_id":"evs_01_0023.xml", - "product_code":"evs", - "code":"71", + "product_code":"", + "code":"73", "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", + "doc_type":"", "kw":"Managing EVS Replication (Deprecated)", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"Managing EVS Replication (Deprecated)", @@ -1429,18 +1286,15 @@ { "uri":"evs_01_0060.html", "node_id":"evs_01_0060.xml", - "product_code":"evs", - "code":"72", + "product_code":"", + "code":"74", "des":"For the EVS replication concepts, see EVS Replication (Deprecated). This chapter describes the basic functions and operations of EVS replication. Figure 1 shows the opera", - "doc_type":"usermanual", + "doc_type":"", "kw":"EVS Replication Operation Procedure (Deprecated),Managing EVS Replication (Deprecated),User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"EVS Replication Operation Procedure (Deprecated)", @@ -1449,18 +1303,15 @@ { "uri":"evs_01_0024.html", "node_id":"evs_01_0024.xml", - "product_code":"evs", - "code":"73", + "product_code":"", + "code":"75", "des":"Before you create an EVS replication pair, create a DR ECS in the secondary AZ for the production ECS. The DR ECS parameters must be consistent with those of the producti", - "doc_type":"usermanual", + "doc_type":"", "kw":"Creating a DR ECS (Deprecated),Managing EVS Replication (Deprecated),User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"Creating a DR ECS (Deprecated)", @@ -1469,18 +1320,15 @@ { "uri":"evs_01_0026.html", "node_id":"evs_01_0026.xml", - "product_code":"evs", - "code":"74", + "product_code":"", + "code":"76", "des":"Before you use EVS replication, bind a virtual IP address to the production server and DR server, respectively. Then configure the virtual IP address as the static IP add", - "doc_type":"usermanual", + "doc_type":"", "kw":"Configuring a Virtual IP Address for the Server (Deprecated),Managing EVS Replication (Deprecated),U", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"Configuring a Virtual IP Address for the Server (Deprecated)", @@ -1489,18 +1337,15 @@ { "uri":"evs_01_0025.html", "node_id":"evs_01_0025.xml", - "product_code":"evs", - "code":"75", + "product_code":"", + "code":"77", "des":"This section is used to guide users to collect the production ECS and DR ECS information, including the ECS IDs and the IDs of the EVS disks attached the ECSs.Two EVS dis", - "doc_type":"usermanual", + "doc_type":"", "kw":"Collecting ECS Information (Deprecated),Managing EVS Replication (Deprecated),User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"Collecting ECS Information (Deprecated)", @@ -1509,18 +1354,15 @@ { "uri":"evs_01_0027.html", "node_id":"evs_01_0027.xml", - "product_code":"evs", - "code":"76", + "product_code":"", + "code":"78", "des":"Currently, users need to make API calls to create EVS replication pairs. Each server can have multiple EVS replication pairs. For details, see EVS Replication Pair in the", - "doc_type":"usermanual", + "doc_type":"", "kw":"Creating an EVS Replication Pair (Deprecated),Managing EVS Replication (Deprecated),User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"Creating an EVS Replication Pair (Deprecated)", @@ -1529,18 +1371,15 @@ { "uri":"evs_01_0028.html", "node_id":"evs_01_0028.xml", - "product_code":"evs", - "code":"77", + "product_code":"", + "code":"79", "des":"Currently, users need to make API calls to create replication consistency groups and add EVS replication pairs to the groups. For details, see Replication Consistency Gro", - "doc_type":"usermanual", + "doc_type":"", "kw":"Creating a Replication Consistency Group (Deprecated),Managing EVS Replication (Deprecated),User Gui", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"Creating a Replication Consistency Group (Deprecated)", @@ -1549,18 +1388,15 @@ { "uri":"evs_01_0029.html", "node_id":"evs_01_0029.xml", - "product_code":"evs", - "code":"78", + "product_code":"", + "code":"80", "des":"Currently, EVS replication pairs can be added to or removed from replication consistency groups through APIs only. For details, see Updating a Replication Consistency Gro", - "doc_type":"usermanual", + "doc_type":"", "kw":"Updating a Replication Consistency Group (Deprecated),Managing EVS Replication (Deprecated),User Gui", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"Updating a Replication Consistency Group (Deprecated)", @@ -1569,18 +1405,15 @@ { "uri":"evs_01_0030.html", "node_id":"evs_01_0030.xml", - "product_code":"evs", - "code":"79", + "product_code":"", + "code":"81", "des":"Production servers and production disks belong to the primary AZ, and DR servers and DR disks belong to the secondary AZ. Users can make API calls to perform a planned mi", - "doc_type":"usermanual", + "doc_type":"", "kw":"Planned Migration (Deprecated),Managing EVS Replication (Deprecated),User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"Planned Migration (Deprecated)", @@ -1589,18 +1422,15 @@ { "uri":"evs_01_0031.html", "node_id":"evs_01_0031.xml", - "product_code":"evs", - "code":"80", + "product_code":"", + "code":"82", "des":"When the production servers and disks in the primary AZ become faulty due to force majeure, users can make API calls to perform a failover for the replication consistency", - "doc_type":"usermanual", + "doc_type":"", "kw":"Failover (Deprecated),Managing EVS Replication (Deprecated),User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"Failover (Deprecated)", @@ -1609,18 +1439,15 @@ { "uri":"evs_01_0032.html", "node_id":"evs_01_0032.xml", - "product_code":"evs", - "code":"81", + "product_code":"", + "code":"83", "des":"When the production servers and disks in the primary AZ become faulty due to force majeure and a failover has been performed, enable the DR servers and disks to provide s", - "doc_type":"usermanual", + "doc_type":"", "kw":"Reprotection (Deprecated),Managing EVS Replication (Deprecated),User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"Reprotection (Deprecated)", @@ -1629,18 +1456,15 @@ { "uri":"evs_01_0043.html", "node_id":"evs_01_0043.xml", - "product_code":"evs", - "code":"82", + "product_code":"", + "code":"84", "des":"Users can make an API call to expand the EVS disks in one or multiple EVS replication pairs of a replication consistency group. In such an expansion operation, two EVS di", - "doc_type":"usermanual", + "doc_type":"", "kw":"Expanding EVS Disks in a Replication Consistency Group (Deprecated),Managing EVS Replication (Deprec", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"Expanding EVS Disks in a Replication Consistency Group (Deprecated)", @@ -1649,38 +1473,32 @@ { "uri":"evs_01_0069.html", "node_id":"evs_01_0069.xml", - "product_code":"evs", - "code":"83", + "product_code":"", + "code":"85", "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":"Manage EVS Quotas", + "doc_type":"", + "kw":"Managing EVS Quotas", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], - "title":"Manage EVS Quotas", + "title":"Managing EVS Quotas", "githuburl":"" }, { "uri":"evs_01_0070.html", "node_id":"evs_01_0070.xml", - "product_code":"evs", - "code":"84", + "product_code":"", + "code":"86", "des":"Quotas are enforced for service resources on the platform to prevent unforeseen spikes in resource usage. Quotas can limit the number or amount of resources available to ", - "doc_type":"usermanual", - "kw":"Querying EVS Resource Quotas,Manage EVS Quotas,User Guide", + "doc_type":"", + "kw":"Querying EVS Resource Quotas,Managing EVS Quotas,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"Querying EVS Resource Quotas", @@ -1689,18 +1507,15 @@ { "uri":"evs_01_0071.html", "node_id":"evs_01_0071.xml", - "product_code":"evs", - "code":"85", + "product_code":"", + "code":"87", "des":"If any resource quota no longer meets your service requirements, you can apply for a higher quota.The system does not support online quota adjustment. If you need to adju", - "doc_type":"usermanual", - "kw":"Increasing EVS Resource Quotas,Manage EVS Quotas,User Guide", + "doc_type":"", + "kw":"Increasing EVS Resource Quotas,Managing EVS Quotas,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"Increasing EVS Resource Quotas", @@ -1709,76 +1524,66 @@ { "uri":"evs_01_2704.html", "node_id":"evs_01_2704.xml", - "product_code":"evs", - "code":"86", + "product_code":"", + "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":"Managing EVS Monitoring Data", + "doc_type":"", + "kw":"Cloud Eye Monitoring", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual" + } ], - "title":"Managing EVS Monitoring Data", + "title":"Cloud Eye Monitoring", "githuburl":"" }, { "uri":"evs_01_0044.html", "node_id":"evs_01_0044.xml", - "product_code":"evs", - "code":"87", + "product_code":"", + "code":"89", "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,Managing EVS Monitoring Data,User Guide", + "doc_type":"", + "kw":"Viewing Basic EVS Monitoring Data,Cloud Eye Monitoring,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], - "title":"Viewing EVS Monitoring Data", + "title":"Viewing Basic EVS Monitoring Data", "githuburl":"" }, { "uri":"evs_01_0046.html", "node_id":"evs_01_0046.xml", - "product_code":"evs", - "code":"88", + "product_code":"", + "code":"90", "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 EVS Operation Records,User Guide", + "doc_type":"", + "kw":"Recording EVS Operations Using CTS,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], - "title":"Auditing EVS Operation Records", + "title":"Recording EVS Operations Using CTS", "githuburl":"" }, { "uri":"evs_faq_0001.html", "node_id":"evs_faq_0001.xml", - "product_code":"evs", - "code":"89", + "product_code":"", + "code":"91", "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", + "doc_type":"", "kw":"FAQ", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"FAQ", @@ -1787,18 +1592,15 @@ { "uri":"evs_01_0096.html", "node_id":"evs_01_0096.xml", - "product_code":"evs", - "code":"90", + "product_code":"", + "code":"92", "des":"How Do I Start Using a Newly Created Disk?Can EVS Disks Be Used Directly for Storage?Can EVS Disks Be Used Alone?Can I Change the AZ of My Disk?Can I Change the Disk Type", - "doc_type":"usermanual", + "doc_type":"", "kw":"Summary,FAQ,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"Summary", @@ -1807,18 +1609,15 @@ { "uri":"evs_01_0081.html", "node_id":"evs_01_0081.xml", - "product_code":"evs", - "code":"91", + "product_code":"", + "code":"93", "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", + "doc_type":"", "kw":"General", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"General", @@ -1827,18 +1626,15 @@ { "uri":"evs_faq_0033.html", "node_id":"evs_faq_0033.xml", - "product_code":"evs", - "code":"92", - "des":"A newly created disk must be attached to a server and then initialized in the server OS before you can use it.For more information, see Process Overview.", - "doc_type":"usermanual", + "product_code":"", + "code":"94", + "des":"A newly created disk must be attached to a server and then initialized in the server OS before you can use it.For more information, see Getting Started.", + "doc_type":"", "kw":"How Do I Start Using a Newly Created Disk?,General,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"How Do I Start Using a Newly Created Disk?", @@ -1847,18 +1643,15 @@ { "uri":"evs_faq_0065.html", "node_id":"evs_faq_0065.xml", - "product_code":"evs", - "code":"93", + "product_code":"", + "code":"95", "des":"No.EVS disks must be attached to cloud servers before use. You cannot use EVS disks alone to store data.", - "doc_type":"usermanual", + "doc_type":"", "kw":"Can EVS Disks Be Used Directly for Storage?,General,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"Can EVS Disks Be Used Directly for Storage?", @@ -1867,18 +1660,15 @@ { "uri":"evs_faq_0054.html", "node_id":"evs_faq_0054.xml", - "product_code":"evs", - "code":"94", + "product_code":"", + "code":"96", "des":"No.EVS disks must be attached to servers before you can use them.", - "doc_type":"usermanual", + "doc_type":"", "kw":"Can EVS Disks Be Used Alone?,General,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"Can EVS Disks Be Used Alone?", @@ -1887,18 +1677,15 @@ { "uri":"evs_faq_0066.html", "node_id":"evs_faq_0066.xml", - "product_code":"evs", - "code":"95", + "product_code":"", + "code":"97", "des":"To do so, perform the following operations:The disk list page is displayed.View more information on the Summary tab.", - "doc_type":"usermanual", + "doc_type":"", "kw":"How Can I View My Disk Details?,General,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"How Can I View My Disk Details?", @@ -1907,18 +1694,15 @@ { "uri":"evs_01_0061.html", "node_id":"evs_01_0061.xml", - "product_code":"evs", - "code":"96", + "product_code":"", + "code":"98", "des":"Disk names are used to identify disks. After a disk is created, you can perform operations in this section to change the disk name if needed.The disk list page is display", - "doc_type":"usermanual", + "doc_type":"", "kw":"How Do I Change the Name of My Disk?,General,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"How Do I Change the Name of My Disk?", @@ -1927,18 +1711,15 @@ { "uri":"evs_faq_0048.html", "node_id":"evs_faq_0048.xml", - "product_code":"evs", - "code":"97", + "product_code":"", + "code":"99", "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", + "doc_type":"", "kw":"Can I Change the AZ of My Disk?,General,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"Can I Change the AZ of My Disk?", @@ -1947,18 +1728,15 @@ { "uri":"evs_faq_0045.html", "node_id":"evs_faq_0045.xml", - "product_code":"evs", - "code":"98", + "product_code":"", + "code":"100", "des":"The following table describes whether the disk type, device type, sharing, and encryption attributes of a disk can be changed.However, you can:Create a backup for the dis", - "doc_type":"usermanual", + "doc_type":"", "kw":"Can I Change the Disk Type, Device Type, or Sharing Attribute of My Disk?,General,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"Can I Change the Disk Type, Device Type, or Sharing Attribute of My Disk?", @@ -1967,18 +1745,15 @@ { "uri":"evs_faq_0014.html", "node_id":"evs_faq_0014.xml", - "product_code":"evs", - "code":"99", + "product_code":"", + "code":"101", "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", + "doc_type":"", "kw":"What Should I Do If an Error Occurs on My EVS Disk?,General,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"What Should I Do If an Error Occurs on My EVS Disk?", @@ -1987,18 +1762,15 @@ { "uri":"evs_faq_0021.html", "node_id":"evs_faq_0021.xml", - "product_code":"evs", - "code":"100", + "product_code":"", + "code":"102", "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", + "doc_type":"", "kw":"Why Do Some of My EVS Disks Not Have WWN Information?,General,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"Why Do Some of My EVS Disks Not Have WWN Information?", @@ -2007,18 +1779,15 @@ { "uri":"evs_faq_0020.html", "node_id":"evs_faq_0020.xml", - "product_code":"evs", - "code":"101", + "product_code":"", + "code":"103", "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", + "doc_type":"", "kw":"What Should I Do If My EVS Replication Quotas Are Insufficient? (Deprecated),General,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"What Should I Do If My EVS Replication Quotas Are Insufficient? (Deprecated)", @@ -2027,18 +1796,15 @@ { "uri":"evs_faq_0059.html", "node_id":"evs_faq_0059.xml", - "product_code":"evs", - "code":"102", + "product_code":"", + "code":"104", "des":"Data migration involves the following scenarios:Cross-AZ data migration: Disk data can be migrated from one AZ to another through disk backups. You can create backups for", - "doc_type":"usermanual", + "doc_type":"", "kw":"How Can I Migrate Data from an EVS Disk?,General,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"How Can I Migrate Data from an EVS Disk?", @@ -2047,56 +1813,32 @@ { "uri":"evs_faq_0084.html", "node_id":"evs_faq_0084.xml", - "product_code":"evs", - "code":"103", + "product_code":"", + "code":"105", "des":"A system disk runs the server OS. It is like drive C in a PC.When a server is created, a system disk is automatically created and attached. You cannot create a system dis", - "doc_type":"usermanual", + "doc_type":"", "kw":"What Are the Differences Between System Disks and Data Disks?,General,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "opensource":"true", - "documenttype":"usermanual", - "IsBot":"Yes" + } ], "title":"What Are the Differences Between System Disks and Data Disks?", "githuburl":"" }, - { - "uri":"evs_faq_0087.html", - "node_id":"evs_faq_0087.xml", - "product_code":"evs", - "code":"104", - "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", - "search_title":"", - "metedata":[ - { - "prodname":"evs", - "documenttype":"usermanual" - } - ], - "title":"How Can I Download My EVS Disk Data to a Local PC?", - "githuburl":"" - }, { "uri":"evs_faq_0091.html", "node_id":"evs_faq_0091.xml", - "product_code":"evs", - "code":"105", + "product_code":"", + "code":"106", "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", + "doc_type":"", "kw":"How Can I Export the Original Data After I Changed My Server OS from Windows to CentOS?,General,User", "search_title":"", "metedata":[ { - "prodname":"evs", - "opensource":"true", - "documenttype":"usermanual", - "IsBot":"Yes" + } ], "title":"How Can I Export the Original Data After I Changed My Server OS from Windows to CentOS?", @@ -2105,18 +1847,15 @@ { "uri":"evs_faq_0092.html", "node_id":"evs_faq_0092.xml", - "product_code":"evs", - "code":"106", + "product_code":"", + "code":"107", "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", + "doc_type":"", "kw":"What Are the Differences Between MBR and GPT Partition Styles?,General,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "opensource":"true", - "documenttype":"usermanual", - "IsBot":"Yes" + } ], "title":"What Are the Differences Between MBR and GPT Partition Styles?", @@ -2125,34 +1864,49 @@ { "uri":"evs_faq_0095.html", "node_id":"evs_faq_0095.xml", - "product_code":"evs", - "code":"107", + "product_code":"", + "code":"108", "des":"Before an EVS disk is attached, the system will call the reserveVolume EVS API to check whether the disk can be attached. If it can be attached, the system then changes t", - "doc_type":"usermanual", + "doc_type":"", "kw":"What Does the \"reserveVolume\" Trace Mean in CTS?,General,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual" + } ], "title":"What Does the \"reserveVolume\" Trace Mean in CTS?", "githuburl":"" }, + { + "uri":"evs_faq_0087.html", + "node_id":"evs_faq_0087.xml", + "product_code":"", + "code":"109", + "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":"", + "kw":"How Can I Download My EVS Disk Data to a Local PC?,General,User Guide", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"How Can I Download My EVS Disk Data to a Local PC?", + "githuburl":"" + }, { "uri":"evs_faq_0096.html", "node_id":"evs_faq_0096.xml", - "product_code":"evs", - "code":"108", + "product_code":"", + "code":"110", "des":"EVS disks must be attached to servers before you can use them. For how to upload files, see section \"How Do I Upload Files to My ECS?\" in the Elastic Cloud Server FAQs.", - "doc_type":"usermanual", + "doc_type":"", "kw":"How Can I Upload Files to My EVS Disk?,General,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual" + } ], "title":"How Can I Upload Files to My EVS Disk?", @@ -2161,18 +1915,15 @@ { "uri":"evs_01_0078.html", "node_id":"evs_01_0078.xml", - "product_code":"evs", - "code":"109", + "product_code":"", + "code":"111", "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", + "doc_type":"", "kw":"Attachment", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"Attachment", @@ -2181,18 +1932,15 @@ { "uri":"evs_faq_0022.html", "node_id":"evs_faq_0022.xml", - "product_code":"evs", - "code":"110", + "product_code":"", + "code":"112", "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", + "doc_type":"", "kw":"Why Can't I View the Attached Data Disk on the Server?,Attachment,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"Why Can't I View the Attached Data Disk on the Server?", @@ -2201,18 +1949,15 @@ { "uri":"evs_faq_0025.html", "node_id":"evs_faq_0025.xml", - "product_code":"evs", - "code":"111", + "product_code":"", + "code":"113", "des":"My disk cannot be attached to a server.Possible causes are listed here in order of their probability.If the fault persists after you have ruled out one cause, move on to ", - "doc_type":"usermanual", + "doc_type":"", "kw":"Why Can't I Attach My Disk to a Server?,Attachment,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"Why Can't I Attach My Disk to a Server?", @@ -2221,18 +1966,15 @@ { "uri":"evs_faq_0006.html", "node_id":"evs_faq_0006.xml", - "product_code":"evs", - "code":"112", + "product_code":"", + "code":"114", "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", + "doc_type":"", "kw":"Can I Attach a Disk to Multiple Servers?,Attachment,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"Can I Attach a Disk to Multiple Servers?", @@ -2241,38 +1983,32 @@ { "uri":"evs_faq_0036.html", "node_id":"evs_faq_0036.xml", - "product_code":"evs", - "code":"113", - "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", + "product_code":"", + "code":"115", + "des":"No.Disks and the server you attach the disks to must be in the same AZ. The same is true for shared disks. A shared disk can only be attached to the servers in the same A", + "doc_type":"", + "kw":"Can I Attach a Disk to a Server in a Different AZ?,Attachment,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], - "title":"Can I Attach a Disk to a Server in Another AZ?", + "title":"Can I Attach a Disk to a Server in a Different AZ?", "githuburl":"" }, { "uri":"evs_faq_0043.html", "node_id":"evs_faq_0043.xml", - "product_code":"evs", - "code":"114", + "product_code":"", + "code":"116", "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", + "doc_type":"", "kw":"How Can I Add a Data Disk to an Existing Server?,Attachment,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"How Can I Add a Data Disk to an Existing Server?", @@ -2281,18 +2017,15 @@ { "uri":"evs_faq_0055.html", "node_id":"evs_faq_0055.xml", - "product_code":"evs", - "code":"115", + "product_code":"", + "code":"117", "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", + "doc_type":"", "kw":"Can I Attach Different Types of Disks to the Same Server?,Attachment,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"Can I Attach Different Types of Disks to the Same Server?", @@ -2301,18 +2034,15 @@ { "uri":"evs_faq_0076.html", "node_id":"evs_faq_0076.xml", - "product_code":"evs", - "code":"116", + "product_code":"", + "code":"118", "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", + "doc_type":"", "kw":"What Should I Do If a Linux EVS Disk Is Attached to a Windows Server?,Attachment,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"What Should I Do If a Linux EVS Disk Is Attached to a Windows Server?", @@ -2321,18 +2051,15 @@ { "uri":"evs_faq_0078.html", "node_id":"evs_faq_0078.xml", - "product_code":"evs", - "code":"117", + "product_code":"", + "code":"119", "des":"This section describes how to change the function of a disk on the original server.System disk created along with a server: You can detach the system disk and then re-att", - "doc_type":"usermanual", + "doc_type":"", "kw":"Can I Change the Function of a System Disk or Data Disk Created Along with a Server?,Attachment,User", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"Can I Change the Function of a System Disk or Data Disk Created Along with a Server?", @@ -2341,16 +2068,15 @@ { "uri":"evs_faq_0094.html", "node_id":"evs_faq_0094.xml", - "product_code":"evs", - "code":"118", + "product_code":"", + "code":"120", "des":"You find that the device name displayed in the ECS OS is different from that displayed on the management console and you cannot determine which disk name is correct. This", - "doc_type":"usermanual", + "doc_type":"", "kw":"How Do I Obtain My Disk Device Name in the ECS OS Using the Device Identifier Provided on the Consol", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual" + } ], "title":"How Do I Obtain My Disk Device Name in the ECS OS Using the Device Identifier Provided on the Console?", @@ -2359,18 +2085,15 @@ { "uri":"evs_01_0077.html", "node_id":"evs_01_0077.xml", - "product_code":"evs", - "code":"119", + "product_code":"", + "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", + "doc_type":"", "kw":"Capacity Expansion", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"Capacity Expansion", @@ -2379,18 +2102,15 @@ { "uri":"evs_faq_0026.html", "node_id":"evs_faq_0026.xml", - "product_code":"evs", - "code":"120", + "product_code":"", + "code":"122", "des":"No. The disk capacity can only be expanded, and temporary capacity expansion is not supported.", - "doc_type":"usermanual", + "doc_type":"", "kw":"Can I Reduce or Temporarily Expand the Disk Capacity?,Capacity Expansion,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"Can I Reduce or Temporarily Expand the Disk Capacity?", @@ -2399,18 +2119,15 @@ { "uri":"evs_faq_0075.html", "node_id":"evs_faq_0075.xml", - "product_code":"evs", - "code":"121", + "product_code":"", + "code":"123", "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", + "doc_type":"", "kw":"What Are the Differences Between Expanding Capacity by Expanding an EVS Disk and Creating a New EVS ", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"What Are the Differences Between Expanding Capacity by Expanding an EVS Disk and Creating a New EVS Disk?", @@ -2419,18 +2136,15 @@ { "uri":"evs_faq_0044.html", "node_id":"evs_faq_0044.xml", - "product_code":"evs", - "code":"122", - "des":"Data will not be deleted during a system disk or data disk capacity expansion. However, incorrect operations during an expansion may result in data loss or exceptions. Ex", - "doc_type":"usermanual", + "product_code":"", + "code":"124", + "des":"Data will not be deleted during a system disk or data disk capacity expansion. However, incorrect operations during an expansion may result in data loss or exceptions. Yo", + "doc_type":"", "kw":"Will My Disk Data Be Lost After I Expand the Disk Capacity?,Capacity Expansion,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"Will My Disk Data Be Lost After I Expand the Disk Capacity?", @@ -2439,18 +2153,15 @@ { "uri":"evs_faq_0023.html", "node_id":"evs_faq_0023.xml", - "product_code":"evs", - "code":"123", + "product_code":"", + "code":"125", "des":"Yes. If backups or snapshots have been created for disks before capacity was expanded, you can restore your disk data from these backups or snapshots after the capacity i", - "doc_type":"usermanual", + "doc_type":"", "kw":"Can I Use Backups or Snapshots Created Before Capacity Expansion to Restore Data on Expanded Disks?,", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"Can I Use Backups or Snapshots Created Before Capacity Expansion to Restore Data on Expanded Disks?", @@ -2459,18 +2170,15 @@ { "uri":"evs_faq_0042.html", "node_id":"evs_faq_0042.xml", - "product_code":"evs", - "code":"124", + "product_code":"", + "code":"126", "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", + "doc_type":"", "kw":"Do I Need to Restart the Server After Expanding the Disk Capacity?,Capacity Expansion,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"Do I Need to Restart the Server After Expanding the Disk Capacity?", @@ -2479,18 +2187,15 @@ { "uri":"evs_faq_0028.html", "node_id":"evs_faq_0028.xml", - "product_code":"evs", - "code":"125", + "product_code":"", + "code":"127", "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", + "doc_type":"", "kw":"Do I Need to Detach an EVS Disk Before Expanding Its Capacity?,Capacity Expansion,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"Do I Need to Detach an EVS Disk Before Expanding Its Capacity?", @@ -2499,18 +2204,15 @@ { "uri":"evs_faq_0024.html", "node_id":"evs_faq_0024.xml", - "product_code":"evs", - "code":"126", + "product_code":"", + "code":"128", "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", + "doc_type":"", "kw":"What Should I Do If My Disk Capacity Exceeds 2 TiB After Expansion?,Capacity Expansion,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"What Should I Do If My Disk Capacity Exceeds 2 TiB After Expansion?", @@ -2519,18 +2221,15 @@ { "uri":"evs_faq_0029.html", "node_id":"evs_faq_0029.xml", - "product_code":"evs", - "code":"127", - "des":"In Windows, if you already have a D drive and want to add an E drive, refer to the following:The System Disk: Add Additional Capacity to New Volume (F:) and Data Disk: Ad", - "doc_type":"usermanual", + "product_code":"", + "code":"129", + "des":"In Windows, if you already have a D drive and want to add an E drive, refer to the following:The System Disk: Create a New Volume with the Additional Space and Data Disk:", + "doc_type":"", "kw":"How Can I Allocate Newly Added Space to a New Partition?,Capacity Expansion,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"How Can I Allocate Newly Added Space to a New Partition?", @@ -2539,18 +2238,15 @@ { "uri":"evs_faq_0030.html", "node_id":"evs_faq_0030.xml", - "product_code":"evs", - "code":"128", - "des":"In Windows, if your disk already has, for example, a D: drive and you want to add space to this volume, refer to the following:The System Disk: Add Additional Capacity to", - "doc_type":"usermanual", + "product_code":"", + "code":"130", + "des":"In Windows, if your disk already has, for example, a D drive and you want to add space to this drive, refer to the following:The System Disk: Add the Additional Space to ", + "doc_type":"", "kw":"How Can I Allocate Newly Added Space to an Existing Partition?,Capacity Expansion,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"How Can I Allocate Newly Added Space to an Existing Partition?", @@ -2559,18 +2255,15 @@ { "uri":"evs_faq_0027.html", "node_id":"evs_faq_0027.xml", - "product_code":"evs", - "code":"129", + "product_code":"", + "code":"131", "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", + "doc_type":"", "kw":"Why Did My Disk Capacity Remain Unchanged on the Server After Capacity Expansion?,Capacity Expansion", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"Why Did My Disk Capacity Remain Unchanged on the Server After Capacity Expansion?", @@ -2579,18 +2272,15 @@ { "uri":"evs_faq_0074.html", "node_id":"evs_faq_0074.xml", - "product_code":"evs", - "code":"130", + "product_code":"", + "code":"132", "des":"Capacity expansion is not allowed for the disk.Possible causes are listed here in order of their probability.If the fault persists after you have ruled out one cause, mov", - "doc_type":"usermanual", + "doc_type":"", "kw":"Why Can't I Expand Capacity for My Disk?,Capacity Expansion,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"Why Can't I Expand Capacity for My Disk?", @@ -2599,18 +2289,15 @@ { "uri":"evs_faq_0073.html", "node_id":"evs_faq_0073.xml", - "product_code":"evs", - "code":"131", + "product_code":"", + "code":"133", "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", + "doc_type":"", "kw":"How Do I Extend the File System of an Unpartitioned Data Disk in Linux?,Capacity Expansion,User Guid", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"How Do I Extend the File System of an Unpartitioned Data Disk in Linux?", @@ -2619,18 +2306,15 @@ { "uri":"evs_faq_0082.html", "node_id":"evs_faq_0082.xml", - "product_code":"evs", - "code":"132", + "product_code":"", + "code":"134", "des":"If the root partition of your quickly provisioned BMS is too small, extend the root partition by referring to the following procedure.This example uses CentOS 7.3 and sys", - "doc_type":"usermanual", + "doc_type":"", "kw":"How Do I Extend the Root Partition of a Quickly Provisioned BMS?,Capacity Expansion,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"How Do I Extend the Root Partition of a Quickly Provisioned BMS?", @@ -2639,19 +2323,15 @@ { "uri":"evs_faq_0131.html", "node_id":"evs_faq_0131.xml", - "product_code":"evs", - "code":"133", + "product_code":"", + "code":"135", "des":"You can use either fdisk or parted to view the disk partition style.Method 1: Check Partition Style and File System Format Using fdiskMethod 2: Check Partition Style and ", - "doc_type":"usermanual", + "doc_type":"", "kw":"How Do I View the Disk Partition Style in Linux?,Capacity Expansion,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "opensource":"true", - "documenttype":"usermanual", - "IsMulti":"Yes", - "IsBot":"Yes" + } ], "title":"How Do I View the Disk Partition Style in Linux?", @@ -2660,18 +2340,15 @@ { "uri":"evs_01_0079.html", "node_id":"evs_01_0079.xml", - "product_code":"evs", - "code":"134", + "product_code":"", + "code":"136", "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", + "doc_type":"", "kw":"Detachment", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"Detachment", @@ -2680,18 +2357,15 @@ { "uri":"evs_faq_0012.html", "node_id":"evs_faq_0012.xml", - "product_code":"evs", - "code":"135", + "product_code":"", + "code":"137", "des":"It depends on if the disk is encrypted or not.EncryptedThe CMK is disabled or scheduled for deletion.The disk can still be used, but there is no guarantee for how long it", - "doc_type":"usermanual", + "doc_type":"", "kw":"If I Detach a Disk, Will I Lose the Data on My Disk?,Detachment,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"If I Detach a Disk, Will I Lose the Data on My Disk?", @@ -2700,18 +2374,15 @@ { "uri":"evs_faq_0056.html", "node_id":"evs_faq_0056.xml", - "product_code":"evs", - "code":"136", - "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", + "product_code":"", + "code":"138", + "des":"EVS disks can be used as system disks or data disks, but the way you detach each one is different.In Linux, a system disk is typically mounted on /dev/vda. In Windows, a ", + "doc_type":"", "kw":"Why Can't I Detach My Disk?,Detachment,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"Why Can't I Detach My Disk?", @@ -2720,18 +2391,15 @@ { "uri":"evs_01_0083.html", "node_id":"evs_01_0083.xml", - "product_code":"evs", - "code":"137", + "product_code":"", + "code":"139", "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", + "doc_type":"", "kw":"Deletion", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"Deletion", @@ -2740,18 +2408,15 @@ { "uri":"evs_faq_0079.html", "node_id":"evs_faq_0079.xml", - "product_code":"evs", - "code":"138", + "product_code":"", + "code":"140", "des":"Check whether the disk has any snapshots or backups created.If there are, use a snapshot or backup to restore the disk data to the state when the snapshot or backup was c", - "doc_type":"usermanual", + "doc_type":"", "kw":"How Can I Recover Data from a Disk That Was Accidentally Deleted?,Deletion,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"How Can I Recover Data from a Disk That Was Accidentally Deleted?", @@ -2760,18 +2425,15 @@ { "uri":"evs_01_0082.html", "node_id":"evs_01_0082.xml", - "product_code":"evs", - "code":"139", + "product_code":"", + "code":"141", "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", + "doc_type":"", "kw":"Capacity", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"Capacity", @@ -2780,18 +2442,15 @@ { "uri":"evs_faq_0031.html", "node_id":"evs_faq_0031.xml", - "product_code":"evs", - "code":"140", + "product_code":"", + "code":"142", "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", + "doc_type":"", "kw":"What Is the Maximum Capacity Supported for the System and Data Disks?,Capacity,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"What Is the Maximum Capacity Supported for the System and Data Disks?", @@ -2800,38 +2459,49 @@ { "uri":"evs_faq_0032.html", "node_id":"evs_faq_0032.xml", - "product_code":"evs", - "code":"141", - "des":"If your disk space starts to fill up, you can:Create a new disk and attach it to the server. For details, see Create an EVS Disk.Expand the capacity of the existing disk.", - "doc_type":"usermanual", + "product_code":"", + "code":"143", + "des":"If your disk space starts to fill up, you can:Create a new disk and attach it to the server. For details, see Creating an EVS Disk.Expand the capacity of the existing dis", + "doc_type":"", "kw":"What Should I Do If My Disk Starts to Run Out of Space?,Capacity,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"What Should I Do If My Disk Starts to Run Out of Space?", "githuburl":"" }, + { + "uri":"evs_02_0010.html", + "node_id":"evs_02_0010.xml", + "product_code":"", + "code":"144", + "des":"When the EVS disk space on a server is insufficient, the server running speed will be affected, which will further affect user experience. You can clean up the disk space", + "doc_type":"", + "kw":"How Do I Clean Up My Disk Space on a Windows Server?,Capacity,User Guide", + "search_title":"", + "metedata":[ + { + + } + ], + "title":"How Do I Clean Up My Disk Space on a Windows Server?", + "githuburl":"" + }, { "uri":"evs_faq_0069.html", "node_id":"evs_faq_0069.xml", - "product_code":"evs", - "code":"142", + "product_code":"", + "code":"145", "des":"The capacity of a single disk can be expanded to up to 32 TiB. If this still fails to meet your needs, it is recommended that you create RAID arrays with EVS disks or man", - "doc_type":"usermanual", + "doc_type":"", "kw":"What Can I Do If the Capacity of My Disk Reaches the Maximum But I Still Need More Space?,Capacity,U", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"What Can I Do If the Capacity of My Disk Reaches the Maximum But I Still Need More Space?", @@ -2840,18 +2510,15 @@ { "uri":"evs_faq_0035.html", "node_id":"evs_faq_0035.xml", - "product_code":"evs", - "code":"143", + "product_code":"", + "code":"146", "des":"If your disk capacity is greater than 2 TiB, do not use fdisk to partition the disk. Or any space in excess of 2 TiB will be unable to show up after the disk is partition", - "doc_type":"usermanual", + "doc_type":"", "kw":"What Should I Do If I Use fdisk to Initialize a Disk Larger Than 2 TiB and Then the Space in Excess ", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"What Should I Do If I Use fdisk to Initialize a Disk Larger Than 2 TiB and Then the Space in Excess of 2 TiB Cannot Be Displayed?", @@ -2860,18 +2527,15 @@ { "uri":"evs_faq_0053.html", "node_id":"evs_faq_0053.xml", - "product_code":"evs", - "code":"144", + "product_code":"", + "code":"147", "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", + "doc_type":"", "kw":"How Can I View My Disk Usage?,Capacity,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"How Can I View My Disk Usage?", @@ -2880,18 +2544,15 @@ { "uri":"evs_faq_0061.html", "node_id":"evs_faq_0061.xml", - "product_code":"evs", - "code":"145", + "product_code":"", + "code":"148", "des":"Sorry, you cannot.Currently, the capacity of an EVS disk cannot be transferred to another disk. Multiple EVS disks cannot be combined into a single, larger disk, either.C", - "doc_type":"usermanual", + "doc_type":"", "kw":"Can I Transfer the Data Disk Capacity to a System Disk?,Capacity,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"Can I Transfer the Data Disk Capacity to a System Disk?", @@ -2900,18 +2561,15 @@ { "uri":"evs_faq_280807.html", "node_id":"evs_faq_280807.xml", - "product_code":"evs", - "code":"146", + "product_code":"", + "code":"149", "des":"Troubleshoot this issue by performing the following steps:Check whether the disk partition usage is 100% or almost 100%.df -hChecking the partition usageIn this example, ", - "doc_type":"usermanual", + "doc_type":"", "kw":"Why the Space of My New Disk Is Full After I Uploaded Only 500 MB of Files to the Disk?,Capacity,Use", "search_title":"", "metedata":[ { - "prodname":"evs", - "opensource":"true", - "documenttype":"usermanual", - "IsBot":"Yes" + } ], "title":"Why the Space of My New Disk Is Full After I Uploaded Only 500 MB of Files to the Disk?", @@ -2920,18 +2578,15 @@ { "uri":"evs_01_0092.html", "node_id":"evs_01_0092.xml", - "product_code":"evs", - "code":"147", + "product_code":"", + "code":"150", "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", + "doc_type":"", "kw":"Snapshot", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"Snapshot", @@ -2940,18 +2595,15 @@ { "uri":"evs_faq_0046.html", "node_id":"evs_faq_0046.xml", - "product_code":"evs", - "code":"148", + "product_code":"", + "code":"151", "des":"A snapshot creation will fail if its source disk is in an intermediate state, such as Attaching and Expanding, or an abnormal state, such as Error and Restoration failed.", - "doc_type":"usermanual", + "doc_type":"", "kw":"What Are the Typical Causes of a Snapshot Creation Failure?,Snapshot,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"What Are the Typical Causes of a Snapshot Creation Failure?", @@ -2960,18 +2612,15 @@ { "uri":"evs_faq_0051.html", "node_id":"evs_faq_0051.xml", - "product_code":"evs", - "code":"149", + "product_code":"", + "code":"152", "des":"No, but you can develop a program to periodically create snapshots through APIs. Alternatively, you may use the CBR service and enable auto backup to create backups perio", - "doc_type":"usermanual", + "doc_type":"", "kw":"Does EVS Support Automatic Snapshot Creation?,Snapshot,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"Does EVS Support Automatic Snapshot Creation?", @@ -2980,18 +2629,15 @@ { "uri":"evs_faq_0070.html", "node_id":"evs_faq_0070.xml", - "product_code":"evs", - "code":"150", - "des":"No.Snapshots cannot be created for multiple disks at the same time. You must create snapshots for disks one by one.", - "doc_type":"usermanual", + "product_code":"", + "code":"153", + "des":"No. Snapshots cannot be created for multiple disks at the same time. You must create snapshots for disks one by one.", + "doc_type":"", "kw":"Can I Create Snapshots for Multiple Disks at a Time?,Snapshot,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"Can I Create Snapshots for Multiple Disks at a Time?", @@ -3000,18 +2646,15 @@ { "uri":"evs_faq_0057.html", "node_id":"evs_faq_0057.xml", - "product_code":"evs", - "code":"151", + "product_code":"", + "code":"154", "des":"There are two types of snapshots: manual snapshots you create on-demand and automatic snapshots created by the system.Manual snapshots: You may manually create snapshots ", - "doc_type":"usermanual", + "doc_type":"", "kw":"How Is a Snapshot Created for My Disk?,Snapshot,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"How Is a Snapshot Created for My Disk?", @@ -3020,18 +2663,15 @@ { "uri":"evs_faq_0058.html", "node_id":"evs_faq_0058.xml", - "product_code":"evs", - "code":"152", - "des":"Possible causes are as follows:Snapshot data can be rolled back only when the status of the snapshot's source disk is Available or Rollback failed. If the snapshot's sour", - "doc_type":"usermanual", + "product_code":"", + "code":"155", + "des":"Possible causes are as follows:Snapshot data can only be rolled back when the status of the snapshot's source disk is Available or Rollback failed. If the snapshot's sour", + "doc_type":"", "kw":"Why Can't I Roll Back My Disk Data from a Snapshot?,Snapshot,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"Why Can't I Roll Back My Disk Data from a Snapshot?", @@ -3040,38 +2680,32 @@ { "uri":"evs_faq_0062.html", "node_id":"evs_faq_0062.xml", - "product_code":"evs", - "code":"153", - "des":"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.If you have for", - "doc_type":"usermanual", - "kw":"Can I Roll Back the Data from a Snapshot After Reinstalling the OS or Formatting the Disk?,Snapshot,", + "product_code":"", + "code":"156", + "des":"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.If you have for", + "doc_type":"", + "kw":"Can I Roll Back Data from a Snapshot After Reinstalling the OS or Formatting the Disk?,Snapshot,User", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], - "title":"Can I Roll Back the Data from a Snapshot After Reinstalling the OS or Formatting the Disk?", + "title":"Can I Roll Back Data from a Snapshot After Reinstalling the OS or Formatting the Disk?", "githuburl":"" }, { "uri":"evs_faq_0063.html", "node_id":"evs_faq_0063.xml", - "product_code":"evs", - "code":"154", - "des":"When you create a snapshot for a disk for the first time, the snapshot is a full snapshot, and its size is the same as the disk size. Subsequent snapshots created for the", - "doc_type":"usermanual", + "product_code":"", + "code":"157", + "des":"The first snapshot is a full snapshot, which backs up all data (data blocks) on the EVS disk at the time of the snapshot. Subsequent snapshots are incremental snapshots, ", + "doc_type":"", "kw":"How Is the Snapshot Size Calculated?,Snapshot,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"How Is the Snapshot Size Calculated?", @@ -3080,18 +2714,15 @@ { "uri":"evs_faq_0064.html", "node_id":"evs_faq_0064.xml", - "product_code":"evs", - "code":"155", + "product_code":"", + "code":"158", "des":"No.Snapshots are stored on the physical disks that provide storage resources for EVS disks. Therefore, snapshots do not use the EVS disk space.", - "doc_type":"usermanual", + "doc_type":"", "kw":"Do Snapshots Take Space on the Disk?,Snapshot,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"Do Snapshots Take Space on the Disk?", @@ -3100,16 +2731,15 @@ { "uri":"evs_faq_0088.html", "node_id":"evs_faq_0088.xml", - "product_code":"evs", - "code":"156", - "des":"Yes. You can roll back a snapshot to the source disk multiple times as needed.", - "doc_type":"usermanual", + "product_code":"", + "code":"159", + "des":"Yes. You can use a snapshot to roll back data to the source disk multiple times as needed.", + "doc_type":"", "kw":"Can I Perform Multiple Rollback Operations for a Snapshot?,Snapshot,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual" + } ], "title":"Can I Perform Multiple Rollback Operations for a Snapshot?", @@ -3118,16 +2748,15 @@ { "uri":"evs_faq_0089.html", "node_id":"evs_faq_0089.xml", - "product_code":"evs", - "code":"157", + "product_code":"", + "code":"160", "des":"No. Snapshots cannot be replicated to other regions or accounts.", - "doc_type":"usermanual", + "doc_type":"", "kw":"Can I Replicate Snapshots to Other Regions or Accounts?,Snapshot,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual" + } ], "title":"Can I Replicate Snapshots to Other Regions or Accounts?", @@ -3136,16 +2765,15 @@ { "uri":"evs_faq_0102.html", "node_id":"evs_faq_0102.xml", - "product_code":"evs", - "code":"158", - "des":"Possible causes are:You have manually deleted the snapshot.You have deleted the disk based on which the snapshot was created. If a disk is deleted, all the snapshots crea", - "doc_type":"usermanual", + "product_code":"", + "code":"161", + "des":"Possible causes are:You have manually deleted the snapshot.You have deleted the snapshot's source disk. Then, all the snapshots created for this disk will be automaticall", + "doc_type":"", "kw":"Why Can't I Find My Snapshot?,Snapshot,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual" + } ], "title":"Why Can't I Find My Snapshot?", @@ -3154,16 +2782,15 @@ { "uri":"evs_faq_281112.html", "node_id":"evs_faq_281112.xml", - "product_code":"evs", - "code":"159", + "product_code":"", + "code":"162", "des":"The following two scenarios are supported:You can first use a snapshot to create a disk and then use the snapshot to roll back data of its source disk.You can first use a", - "doc_type":"usermanual", + "doc_type":"", "kw":"Can I Use a Snapshot to Create a Disk and Roll Back Disk Data at Almost the Same Time?,Snapshot,User", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual" + } ], "title":"Can I Use a Snapshot to Create a Disk and Roll Back Disk Data at Almost the Same Time?", @@ -3172,18 +2799,15 @@ { "uri":"evs_01_0080.html", "node_id":"evs_01_0080.xml", - "product_code":"evs", - "code":"160", + "product_code":"", + "code":"163", "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", + "doc_type":"", "kw":"Performance", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"Performance", @@ -3192,38 +2816,32 @@ { "uri":"evs_faq_0019.html", "node_id":"evs_faq_0019.xml", - "product_code":"evs", - "code":"161", + "product_code":"", + "code":"164", "des":"In the disk performance test, if the start sector number is not 4-KiB aligned, the disk performance will be greatly affected. Ensure that the start sector number is 4-KiB", - "doc_type":"usermanual", - "kw":"How Can I Test My Disk Performance?,Performance,User Guide", + "doc_type":"", + "kw":"How Do I Test My Disk Performance?,Performance,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], - "title":"How Can I Test My Disk Performance?", + "title":"How Do I Test My Disk Performance?", "githuburl":"" }, { "uri":"evs_faq_0080.html", "node_id":"evs_faq_0080.xml", - "product_code":"evs", - "code":"162", + "product_code":"", + "code":"165", "des":"You have followed the test performance method, but the test results do not meet expectations.During a disk performance test, the disk and stress test conditions play an i", - "doc_type":"usermanual", + "doc_type":"", "kw":"Why Does My Disk Performance Test Using Fio Have Incorrect Results?,Performance,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"Why Does My Disk Performance Test Using Fio Have Incorrect Results?", @@ -3232,18 +2850,15 @@ { "uri":"evs_faq_0081.html", "node_id":"evs_faq_0081.xml", - "product_code":"evs", - "code":"163", + "product_code":"", + "code":"166", "des":"SymptomIf you are aware of a service slowdown, depending on if you are examining a Windows or Linux server, you can take the following actions:Windows: Open Task Manager ", - "doc_type":"usermanual", + "doc_type":"", "kw":"How Can I Handle a Slowdown in Disk Read/Write Speed or Increased I/Os?,Performance,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"How Can I Handle a Slowdown in Disk Read/Write Speed or Increased I/Os?", @@ -3252,16 +2867,15 @@ { "uri":"evs_faq_280905.html", "node_id":"evs_faq_280905.xml", - "product_code":"evs", - "code":"164", + "product_code":"", + "code":"167", "des":"SymptomA 500 GiB ultra-high I/O disk had an I/O usage of 99.94%, but it only had 12,000 IOPS.Description100% disk I/O usage does not mean that the disk IOPS reaches the m", - "doc_type":"usermanual", + "doc_type":"", "kw":"Why My Disk's Read IOPS Can't Reach the Theoretical Maximum IOPS When the Disk I/O Usage Is Almost 1", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual" + } ], "title":"Why My Disk's Read IOPS Can't Reach the Theoretical Maximum IOPS When the Disk I/O Usage Is Almost 100%?", @@ -3270,18 +2884,15 @@ { "uri":"evs_01_0084.html", "node_id":"evs_01_0084.xml", - "product_code":"evs", - "code":"165", + "product_code":"", + "code":"168", "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", + "doc_type":"", "kw":"Sharing", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"Sharing", @@ -3290,18 +2901,15 @@ { "uri":"evs_faq_0039.html", "node_id":"evs_faq_0039.xml", - "product_code":"evs", - "code":"166", + "product_code":"", + "code":"169", "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", + "doc_type":"", "kw":"Do I Have to Deploy a Cluster to Use Shared Disks?,Sharing,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"Do I Have to Deploy a Cluster to Use Shared Disks?", @@ -3310,18 +2918,15 @@ { "uri":"evs_faq_0037.html", "node_id":"evs_faq_0037.xml", - "product_code":"evs", - "code":"167", + "product_code":"", + "code":"170", "des":"A shared disk can be attached to up to 16 servers.", - "doc_type":"usermanual", + "doc_type":"", "kw":"How Many Servers Can I Attach a Shared Disk to?,Sharing,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"How Many Servers Can I Attach a Shared Disk to?", @@ -3330,18 +2935,15 @@ { "uri":"evs_faq_0038.html", "node_id":"evs_faq_0038.xml", - "product_code":"evs", - "code":"168", + "product_code":"", + "code":"171", "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.For details, see Attaching a ", - "doc_type":"usermanual", + "doc_type":"", "kw":"How Can I Attach a Shared Disk to Multiple Servers?,Sharing,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"How Can I Attach a Shared Disk to Multiple Servers?", @@ -3350,18 +2952,15 @@ { "uri":"evs_faq_0068.html", "node_id":"evs_faq_0068.xml", - "product_code":"evs", - "code":"169", + "product_code":"", + "code":"172", "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", + "doc_type":"", "kw":"Can a Shared Disk Be Attached to Servers That Belong to Different Accounts?,Sharing,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"Can a Shared Disk Be Attached to Servers That Belong to Different Accounts?", @@ -3370,18 +2969,15 @@ { "uri":"evs_faq_0083.html", "node_id":"evs_faq_0083.xml", - "product_code":"evs", - "code":"170", + "product_code":"", + "code":"173", "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", + "doc_type":"", "kw":"Can I Attach a Shared Disk to Servers Running Different OSs?,Sharing,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"Can I Attach a Shared Disk to Servers Running Different OSs?", @@ -3390,16 +2986,15 @@ { "uri":"evs_faq_0098.html", "node_id":"evs_faq_0098.xml", - "product_code":"evs", - "code":"171", + "product_code":"", + "code":"174", "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", + "doc_type":"", "kw":"Backup", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual" + } ], "title":"Backup", @@ -3408,16 +3003,15 @@ { "uri":"evs_faq_0097.html", "node_id":"evs_faq_0097.xml", - "product_code":"evs", - "code":"172", + "product_code":"", + "code":"175", "des":"No. You can back up disks when the server is in use. When a server is running, data is written into disks on the server, and some newly generated data is cached in the se", - "doc_type":"usermanual", + "doc_type":"", "kw":"Do I Need to Stop the Server Before Performing a Disk Backup?,Backup,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual" + } ], "title":"Do I Need to Stop the Server Before Performing a Disk Backup?", @@ -3426,18 +3020,15 @@ { "uri":"evs_01_0039.html", "node_id":"evs_01_0039.xml", - "product_code":"evs", - "code":"173", + "product_code":"", + "code":"176", "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", + "doc_type":"", "kw":"Appendix", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"Appendix", @@ -3446,57 +3037,32 @@ { "uri":"evs_01_0040.html", "node_id":"evs_01_0040.xml", - "product_code":"evs", - "code":"174", + "product_code":"", + "code":"177", "des":"An EVS disk has several statuses. Table 1 lists EVS disk statuses, the meaning of each status, and the operations a disk in each status allows.Disk status detailsEVS Disk", - "doc_type":"usermanual", + "doc_type":"", "kw":"EVS Disk Status,Appendix,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"EVS Disk Status", "githuburl":"" }, - { - "uri":"evs_01_0041.html", - "node_id":"evs_01_0041.xml", - "product_code":"evs", - "code":"175", - "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", - "search_title":"", - "metedata":[ - { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" - } - ], - "title":"EVS Snapshot Status", - "githuburl":"" - }, { "uri":"evs_01_0114.html", "node_id":"evs_01_0114.xml", - "product_code":"evs", - "code":"176", + "product_code":"", + "code":"178", "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", + "doc_type":"", "kw":"Change History,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "opensource":"true", - "documenttype":"usermanual" + } ], "title":"Change History", @@ -3505,18 +3071,15 @@ { "uri":"evs_01_0115.html", "node_id":"evs_01_0115.xml", - "product_code":"evs", - "code":"177", + "product_code":"", + "code":"179", "des":"For details about the terms involved in this document, see Glossary.", - "doc_type":"usermanual", + "doc_type":"", "kw":"Glossary,User Guide", "search_title":"", "metedata":[ { - "prodname":"evs", - "documenttype":"usermanual", - "opensource":"true", - "IsBot":"Yes" + } ], "title":"Glossary", diff --git a/docs/evs/umn/CLASS.TXT.json b/docs/evs/umn/CLASS.TXT.json index 759ef8f48..d9f3c6d2d 100644 --- a/docs/evs/umn/CLASS.TXT.json +++ b/docs/evs/umn/CLASS.TXT.json @@ -1,481 +1,490 @@ [ { "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", + "product_code":"", "title":"Overview", "uri":"evs_01_0119.html", - "doc_type":"usermanual", + "doc_type":"", "p_code":"", "code":"1" }, { - "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", + "desc":"Elastic Volume Service (EVS) offers scalable block storage for cloud servers. EVS disks provide high reliability, high performance, and come with a variety of disk types.", + "product_code":"", "title":"What Is EVS?", "uri":"en-us_topic_0014580741.html", - "doc_type":"usermanual", + "doc_type":"", "p_code":"1", "code":"2" }, { - "desc":"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.Common ", - "product_code":"evs", + "desc":"EVS disks are classified based on the disk I/O performance. EVS disks differ in performance and price. You can choose whichever disk type that is the best fit for your ap", + "product_code":"", "title":"Disk Types and Performance", "uri":"en-us_topic_0014580744.html", - "doc_type":"usermanual", + "doc_type":"", "p_code":"1", "code":"3" }, { - "desc":"There are two EVS device types: Virtual Block Device (VBD) and Small Computer System Interface (SCSI).VBD is the default EVS device type. VBD EVS disks support only basic", + "desc":"General Purpose SSD V2 is a next-generation General Purpose SSD disk type. You can buy General Purpose SSD V2 disks of a given capacity with the IOPS and throughput tailo", "product_code":"evs", - "title":"Device Types and Usage Instructions", - "uri":"en-us_topic_0052554220.html", + "title":"General Purpose SSD V2 Disks", + "uri":"evs_01_1137.html", "doc_type":"usermanual", "p_code":"1", "code":"4" }, { - "desc":"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 attach", - "product_code":"evs", - "title":"Shared EVS Disks and Usage Instructions", - "uri":"en-us_topic_0032860759.html", - "doc_type":"usermanual", + "desc":"There are two EVS device types: Virtual Block Device (VBD) and Small Computer System Interface (SCSI).VBD is the default EVS device type. VBD EVS disks support only basic", + "product_code":"", + "title":"Device Types", + "uri":"en-us_topic_0052554220.html", + "doc_type":"", "p_code":"1", "code":"5" }, { - "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 Encryption", - "uri":"evs_01_0001.html", - "doc_type":"usermanual", + "desc":"Disk sharing allows you to create shared EVS disks. Shared EVS disks are block storage devices that support concurrent read/write operations and can be attached to multip", + "product_code":"", + "title":"Disk Sharing", + "uri":"en-us_topic_0032860759.html", + "doc_type":"", "p_code":"1", "code":"6" }, { - "desc":"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 d", - "product_code":"evs", - "title":"EVS Backup", - "uri":"evs_01_0021.html", - "doc_type":"usermanual", + "desc":"EVS enables you to encrypt data on newly created disks as required.It uses the industry-standard XTS-AES-256 cryptographic algorithm and keys to encrypt EVS disks. Keys u", + "product_code":"", + "title":"Disk Encryption", + "uri":"evs_01_0001.html", + "doc_type":"", "p_code":"1", "code":"7" }, { - "desc":"An EVS snapshot is a complete copy or image of the disk data at a specific point in time. Snapshots can be used as a disaster recovery (DR) approach, and you can use snap", - "product_code":"evs", - "title":"EVS Snapshot", - "uri":"en-us_topic_0066809008.html", - "doc_type":"usermanual", + "desc":"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 d", + "product_code":"", + "title":"Disk Backup", + "uri":"evs_01_0021.html", + "doc_type":"", "p_code":"1", "code":"8" }, { - "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 Backups and EVS Snapshots", - "uri":"evs_01_0048.html", - "doc_type":"usermanual", + "desc":"A snapshot is a complete copy or image of the disk data taken at a specific time. Snapshot is a major DR approach, and you can use a snapshot to restore disk data to the ", + "product_code":"", + "title":"Disk Snapshot", + "uri":"evs_01_2722.html", + "doc_type":"", "p_code":"1", "code":"9" }, { - "desc":"If your services or disk data demands high reliability, you can use the cross-AZ replication feature provided by EVS. You can create a disaster recovery (DR) disk for a p", - "product_code":"evs", - "title":"EVS Replication (Deprecated)", - "uri":"evs_01_0020.html", - "doc_type":"usermanual", + "desc":"Both disk backups and disk snapshots provide redundancies for improved disk data reliability. Table 1 lists the differences between them.", + "product_code":"", + "title":"Differences Between EVS Backups and EVS Snapshots", + "uri":"evs_01_0048.html", + "doc_type":"", "p_code":"1", "code":"10" }, { "desc":"The backend storage system of EVS employs three-copy redundancy to guarantee data reliability. With this mechanism, one piece of data is by default divided into multiple ", - "product_code":"evs", + "product_code":"", "title":"EVS Three-Copy Redundancy", "uri":"evs_01_0056.html", - "doc_type":"usermanual", + "doc_type":"", "p_code":"1", "code":"11" }, { - "desc":"If you need to assign different permissions to employees in your enterprise to access your EVS resources, IAM is a good choice for fine-grained permissions management. IA", - "product_code":"evs", - "title":"Permissions", - "uri":"evs_01_0086.html", - "doc_type":"usermanual", + "desc":"If your services or disk data demands high reliability, you can use the cross-AZ replication feature provided by EVS. You can create a disaster recovery (DR) disk for a p", + "product_code":"", + "title":"EVS Replication (Deprecated)", + "uri":"evs_01_0020.html", + "doc_type":"", "p_code":"1", "code":"12" }, { - "desc":"This section describes the constraints on using EVS.", - "product_code":"evs", - "title":"Constraints", - "uri":"evs_01_0085.html", - "doc_type":"usermanual", + "desc":"If you need to assign different permissions to employees in your enterprise to access your EVS resources, IAM is a good choice for fine-grained permissions management. IA", + "product_code":"", + "title":"Permissions", + "uri":"evs_01_0086.html", + "doc_type":"", "p_code":"1", "code":"13" }, { - "desc":"Figure 1 shows the relationships between EVS and other services.Relationships between EVS and other services", - "product_code":"evs", - "title":"EVS and Other Services", - "uri":"evs_01_0106.html", - "doc_type":"usermanual", + "desc":"This section describes the constraints on using EVS.You can log in to the console to view default quotas. You can to apply for a larger quota if needed.", + "product_code":"", + "title":"Notes and Constraints", + "uri":"evs_01_0085.html", + "doc_type":"", "p_code":"1", "code":"14" }, { - "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":"Basic Concepts", - "uri":"evs_01_0101.html", - "doc_type":"usermanual", + "desc":"Figure 1 shows the relationships between EVS and other services.Relationships between EVS and other services", + "product_code":"", + "title":"EVS and Other Services", + "uri":"evs_01_0106.html", + "doc_type":"", "p_code":"1", "code":"15" }, { "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":"EVS Concepts", - "uri":"evs_01_0102.html", - "doc_type":"usermanual", - "p_code":"15", + "product_code":"", + "title":"Basic Concepts", + "uri":"evs_01_0101.html", + "doc_type":"", + "p_code":"1", "code":"16" }, { - "desc":"A region and availability zone (AZ) identify the location of a data center. You can create resources in a specific region and AZ.A region is a physical data center, which", - "product_code":"evs", - "title":"Region and AZ", - "uri":"evs_01_0097.html", - "doc_type":"usermanual", - "p_code":"15", + "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":"", + "title":"EVS Concepts", + "uri":"evs_01_0102.html", + "doc_type":"", + "p_code":"16", "code":"17" }, { - "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":"Getting Started", - "uri":"evs_01_0120.html", - "doc_type":"usermanual", - "p_code":"", + "desc":"A region and availability zone (AZ) identify the location of a data center. You can create resources in a specific region and AZ.A region is a physical data center, which", + "product_code":"", + "title":"Region and AZ", + "uri":"evs_01_0097.html", + "doc_type":"", + "p_code":"16", "code":"18" }, { - "desc":"Figure 1 shows the EVS process overview.Process overviewEVS disks can be attached to servers and be used as system disks or data disks. For details, see Table 1.Method of", - "product_code":"evs", - "title":"Process Overview", - "uri":"evs_01_0057.html", - "doc_type":"usermanual", - "p_code":"18", + "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":"", + "title":"Getting Started", + "uri":"evs_01_0120.html", + "doc_type":"", + "p_code":"", "code":"19" }, { - "desc":"EVS disks can be used as system disks or data disks for servers. You can create data disks on the EVS console, or create them together with system disks on the ECS consol", - "product_code":"evs", - "title":"Create an EVS Disk", - "uri":"en-us_topic_0021738346.html", - "doc_type":"usermanual", - "p_code":"18", + "desc":"Figure 1 shows the process for using EVS.Process overviewEVS disks can be attached to servers to be used as system disks or data disks. For details, see Table 1.Method of", + "product_code":"", + "title":"Process Overview", + "uri":"evs_01_0201.html", + "doc_type":"", + "p_code":"19", "code":"20" }, { - "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":"Attach an EVS Disk", - "uri":"evs_01_0107.html", - "doc_type":"usermanual", - "p_code":"18", + "desc":"You can use EVS disks as system disks or data disks for servers. You can create data disks on the EVS console, or create them together with system disks on the cloud serv", + "product_code":"", + "title":"Creating an EVS Disk", + "uri":"en-us_topic_0021738346.html", + "doc_type":"", + "p_code":"19", "code":"21" }, { - "desc":"Separately 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 cas", - "product_code":"evs", - "title":"Attaching a Non-Shared Disk", - "uri":"evs_01_0036.html", - "doc_type":"usermanual", - "p_code":"21", + "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":"", + "title":"Attach an EVS Disk", + "uri":"evs_01_0107.html", + "doc_type":"", + "p_code":"19", "code":"22" }, { - "desc":"Separately created shared EVS disks are data disks. In the disk list, the function of such a disk is displayed as Data disk, and the status is displayed as Available. In ", - "product_code":"evs", - "title":"Attaching a Shared Disk", - "uri":"evs_01_0037.html", - "doc_type":"usermanual", - "p_code":"21", + "desc":"Separately 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 cas", + "product_code":"", + "title":"Attaching a Non-Shared Disk", + "uri":"evs_01_0036.html", + "doc_type":"", + "p_code":"22", "code":"23" }, { - "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":"Initialize an EVS Data Disk", - "uri":"evs_01_0058.html", - "doc_type":"usermanual", - "p_code":"18", + "desc":"Separately created shared EVS disks are data disks. In the disk list, the function of such a disk is displayed as Data disk, and the status is displayed as Available. In ", + "product_code":"", + "title":"Attaching a Shared Disk", + "uri":"evs_01_0037.html", + "doc_type":"", + "p_code":"22", "code":"24" }, { - "desc":"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", - "product_code":"evs", - "title":"Introduction to Data Disk Initialization Scenarios and Partition Styles", - "uri":"evs_01_0038.html", - "doc_type":"usermanual", - "p_code":"24", + "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":"", + "title":"Initialize an EVS Data Disk", + "uri":"evs_01_0058.html", + "doc_type":"", + "p_code":"19", "code":"25" }, { - "desc":"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", - "product_code":"evs", - "title":"Initializing a Windows Data Disk (Windows Server 2008)", - "uri":"evs_01_0108.html", - "doc_type":"usermanual", - "p_code":"24", + "desc":"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", + "product_code":"", + "title":"Introduction to Data Disk Initialization Scenarios and Partition Styles", + "uri":"evs_01_0038.html", + "doc_type":"", + "p_code":"25", "code":"26" }, { - "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 2019)", - "uri":"evs_01_0045.html", - "doc_type":"usermanual", - "p_code":"24", + "desc":"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", + "product_code":"", + "title":"Initializing a Windows Data Disk (Windows Server 2008)", + "uri":"evs_01_0108.html", + "doc_type":"", + "p_code":"25", "code":"27" }, { - "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", - "doc_type":"usermanual", - "p_code":"24", + "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":"", + "title":"Initializing a Windows Data Disk (Windows Server 2019)", + "uri":"evs_01_0045.html", + "doc_type":"", + "p_code":"25", "code":"28" }, { - "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", - "doc_type":"usermanual", - "p_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 parti", + "product_code":"", + "title":"Initializing a Linux Data Disk (fdisk)", + "uri":"evs_01_0033.html", + "doc_type":"", + "p_code":"25", "code":"29" }, { - "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":"Permissions Management", - "uri":"evs_01_0087.html", - "doc_type":"usermanual", - "p_code":"", + "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":"", + "title":"Initializing a Linux Data Disk (parted)", + "uri":"evs_01_0034.html", + "doc_type":"", + "p_code":"25", "code":"30" }, { - "desc":"You can use IAM for fine-grained permissions control for your EVS resources. With IAM, you can:Create IAM users for workforce based on your enterprise's organizational st", - "product_code":"evs", - "title":"Creating a User and Granting EVS Permissions", - "uri":"evs_01_0089.html", - "doc_type":"usermanual", - "p_code":"30", + "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":"", + "title":"Permissions Management", + "uri":"evs_01_0087.html", + "doc_type":"", + "p_code":"", "code":"31" }, { - "desc":"You can create custom policies to supplement the system-defined policies of EVS. For the actions supported for custom policies, see section \"Permissions Policies and Supp", - "product_code":"evs", - "title":"EVS Custom Policies", - "uri":"evs_01_0090.html", - "doc_type":"usermanual", - "p_code":"30", + "desc":"You can use IAM for fine-grained permissions control for your EVS resources. With IAM, you can:Create IAM users for personnel based on your enterprise's organizational st", + "product_code":"", + "title":"Creating a User and Granting EVS Permissions", + "uri":"evs_01_0089.html", + "doc_type":"", + "p_code":"31", "code":"32" }, { - "desc":"Figure 1 shows the basic EVS operation process.Process overviewEVS disks can be attached to servers and be used as system disks or data disks. For details, see Table 1.Me", - "product_code":"evs", - "title":"Creating and Using an EVS Disk", - "uri":"evs_01_0201.html", - "doc_type":"usermanual", - "p_code":"", + "desc":"You can create custom policies to supplement the system-defined policies of EVS. For the actions supported for custom policies, see section \"Permissions Policies and Supp", + "product_code":"", + "title":"EVS Custom Policies", + "uri":"evs_01_0090.html", + "doc_type":"", + "p_code":"31", "code":"33" }, { - "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":"Attaching an Existing Disk", - "uri":"evs_01_0073.html", - "doc_type":"usermanual", + "desc":"Figure 1 shows the process for using EVS.Process of using EVSEVS disks can be attached to servers to be used as system disks or data disks. For details, see Table 1.Metho", + "product_code":"", + "title":"Creating and Using an EVS Disk", + "uri":"evs_01_0057.html", + "doc_type":"", "p_code":"", "code":"34" }, { - "desc":"This section describes how to attach an existing system disk.System disks can only be attached offline, which means that the server must be in the Stopped state.You can v", - "product_code":"evs", - "title":"Attaching an Existing System Disk", - "uri":"evs_01_0074.html", - "doc_type":"usermanual", - "p_code":"34", + "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":"", + "title":"Attaching an Existing EVS Disk", + "uri":"evs_01_0073.html", + "doc_type":"", + "p_code":"", "code":"35" }, { - "desc":"This section describes how to attach an existing non-shared disk to a server and use it as a data disk. A non-shared disk can be attached to one server only.You can view ", - "product_code":"evs", - "title":"Attaching an Existing Non-Shared Disk", - "uri":"evs_01_0075.html", - "doc_type":"usermanual", - "p_code":"34", + "desc":"This section describes how to attach an existing system disk.System disks can only be attached offline, which means that the server must be in the Stopped state.You can v", + "product_code":"", + "title":"Attaching an Existing System Disk", + "uri":"evs_01_0074.html", + "doc_type":"", + "p_code":"35", "code":"36" }, { - "desc":"This section describes how to attach an existing shared disk to a server and use it as a data disk.You can view the disk information in the disk list. A shared disk can b", - "product_code":"evs", - "title":"Attaching an Existing Shared Disk", - "uri":"evs_01_0076.html", - "doc_type":"usermanual", - "p_code":"34", + "desc":"This section describes how to attach an existing non-shared disk to a server to be used as a data disk. A non-shared disk can be attached to one server only.You can view ", + "product_code":"", + "title":"Attaching an Existing Non-Shared Disk", + "uri":"evs_01_0075.html", + "doc_type":"", + "p_code":"35", "code":"37" }, { - "desc":"This section describes how to view disk details, including the disk status and specifications. You can view disk details:From the EVS ConsoleFrom the Cloud Server Console", - "product_code":"evs", - "title":"Viewing EVS Disk Details", - "uri":"evs_01_0093.html", - "doc_type":"usermanual", - "p_code":"", + "desc":"This section describes how to attach an existing shared disk to a server to be used as a data disk.You can view the disk information in the disk list. A shared disk can b", + "product_code":"", + "title":"Attaching an Existing Shared Disk", + "uri":"evs_01_0076.html", + "doc_type":"", + "p_code":"35", "code":"38" }, { - "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":"Disk Capacity Expansion", - "uri":"evs_01_0059.html", - "doc_type":"usermanual", + "desc":"This section describes how to view disk details, including the disk status and specifications. Two methods are as follows:Viewing Disk Details from the EVS ConsoleViewing", + "product_code":"", + "title":"Viewing EVS Disk Details", + "uri":"evs_01_0093.html", + "doc_type":"", "p_code":"", "code":"39" }, { - "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. A sy", + "desc":"If the performance of an existing disk no longer meets your service requirements, you can change the disk type to improve the disk performance.The following table shows t", "product_code":"evs", - "title":"Expansion Overview", - "uri":"evs_01_0006.html", + "title":"Changing the EVS Disk Type", + "uri":"evs_01_0062.html", "doc_type":"usermanual", - "p_code":"39", + "p_code":"", "code":"40" }, { - "desc":"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", - "product_code":"evs", - "title":"Expanding Capacity for an In-use EVS Disk", - "uri":"evs_01_0007.html", - "doc_type":"usermanual", - "p_code":"39", + "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":"", + "title":"Expanding EVS Disk Capacity", + "uri":"evs_01_0059.html", + "doc_type":"", + "p_code":"", "code":"41" }, { - "desc":"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", - "product_code":"evs", - "title":"Expanding Capacity for an Available EVS Disk", - "uri":"evs_01_0008.html", - "doc_type":"usermanual", - "p_code":"39", + "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. A sy", + "product_code":"", + "title":"Expansion Overview", + "uri":"evs_01_0006.html", + "doc_type":"", + "p_code":"41", "code":"42" }, { - "desc":"After a disk is expanded on the management console, the disk size is enlarged, but the additional space cannot be used directly.In Windows, you must allocate the addition", - "product_code":"evs", - "title":"Extending Disk Partitions and File Systems (Windows Server 2008)", - "uri":"en-us_topic_0017616396.html", - "doc_type":"usermanual", - "p_code":"39", + "desc":"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", + "product_code":"", + "title":"Expanding Capacity for an In-use EVS Disk", + "uri":"evs_01_0007.html", + "doc_type":"", + "p_code":"41", "code":"43" }, { - "desc":"After a disk is expanded on the management console, the disk size is enlarged, but the additional space cannot be used directly.In Windows, you must allocate the addition", - "product_code":"evs", - "title":"Extending Disk Partitions and File Systems (Windows Server 2016)", - "uri":"evs_01_0126.html", - "doc_type":"usermanual", - "p_code":"39", + "desc":"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", + "product_code":"", + "title":"Expanding Capacity for an Available EVS Disk", + "uri":"evs_01_0008.html", + "doc_type":"", + "p_code":"41", "code":"44" }, { - "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":"Extending Disk Partitions and File Systems (Linux)", - "uri":"evs_01_0094.html", - "doc_type":"usermanual", - "p_code":"39", + "desc":"After a disk is expanded on the management console, the disk size is enlarged, but the additional space cannot be used directly.In Windows, you must allocate the addition", + "product_code":"", + "title":"Extending Disk Partitions and File Systems (Windows Server 2008)", + "uri":"en-us_topic_0017616396.html", + "doc_type":"", + "p_code":"41", "code":"45" }, { - "desc":"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", - "product_code":"evs", - "title":"Partition and File System Extension Preparations (Linux)", - "uri":"evs_01_0035.html", - "doc_type":"usermanual", - "p_code":"45", + "desc":"After a disk is expanded on the management console, the disk size is enlarged, but the additional space cannot be used directly.In Windows, you must allocate the addition", + "product_code":"", + "title":"Extending Disk Partitions and File Systems (Windows Server 2016)", + "uri":"evs_01_0126.html", + "doc_type":"", + "p_code":"41", "code":"46" }, { - "desc":"After a disk is 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", - "product_code":"evs", - "title":"Extending Partitions and File Systems for System Disks (Linux)", - "uri":"evs_01_0072.html", - "doc_type":"usermanual", - "p_code":"45", + "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":"", + "title":"Extending Disk Partitions and File Systems (Linux)", + "uri":"evs_01_0094.html", + "doc_type":"", + "p_code":"41", "code":"47" }, { - "desc":"After a disk is 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", - "product_code":"evs", - "title":"Extending Partitions and File Systems for Data Disks (Linux)", - "uri":"evs_01_0109.html", - "doc_type":"usermanual", - "p_code":"45", + "desc":"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", + "product_code":"", + "title":"Partition and File System Extension Preparations (Linux)", + "uri":"evs_01_0035.html", + "doc_type":"", + "p_code":"47", "code":"48" }, { "desc":"After a disk is 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", - "product_code":"evs", - "title":"Extending Partitions and File Systems for SCSI Disks (Linux)", - "uri":"evs_01_0018.html", - "doc_type":"usermanual", - "p_code":"45", + "product_code":"", + "title":"Extending Partitions and File Systems for System Disks (Linux)", + "uri":"evs_01_0072.html", + "doc_type":"", + "p_code":"47", "code":"49" }, { - "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":"Detaching and Releasing an EVS Disk", - "uri":"evs_01_0002.html", - "doc_type":"usermanual", - "p_code":"", + "desc":"After a disk is 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", + "product_code":"", + "title":"Extending Partitions and File Systems for Data Disks (Linux)", + "uri":"evs_01_0109.html", + "doc_type":"", + "p_code":"47", "code":"50" }, { - "desc":"If the file system on your system disk is damaged and your server cannot be started, you can detach the system disk and attach it to another server as a data disk. After ", - "product_code":"evs", - "title":"Detaching a System Disk", - "uri":"evs_01_0003.html", - "doc_type":"usermanual", - "p_code":"50", + "desc":"After a disk is 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", + "product_code":"", + "title":"Extending Partitions and File Systems for SCSI Disks (Linux)", + "uri":"evs_01_0018.html", + "doc_type":"", + "p_code":"47", "code":"51" }, { - "desc":"If you want to use a data disk on another server in the same region and AZ, you can detach the data disk and then attach it to that server.If a data disk is no longer req", - "product_code":"evs", - "title":"Detaching a Data Disk", - "uri":"evs_01_0004.html", - "doc_type":"usermanual", - "p_code":"50", + "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":"", + "title":"Detaching and Deleting an EVS Disk", + "uri":"evs_01_0002.html", + "doc_type":"", + "p_code":"", "code":"52" }, { - "desc":"If an EVS disk is no longer used, you can release the virtual resources by deleting it.The disk status is Available, Error, Expansion failed, Restoration failed, or Rollb", - "product_code":"evs", - "title":"Deleting EVS Disks", - "uri":"evs_01_0005.html", - "doc_type":"usermanual", - "p_code":"50", + "desc":"For an attached system disk, the disk function is displayed as System disk, and the disk status is displayed as In-use in the disk list. After the system disk is detached", + "product_code":"", + "title":"Detaching an EVS Disk", + "uri":"evs_01_0003.html", + "doc_type":"", + "p_code":"52", "code":"53" }, + { + "desc":"If an EVS disk is no longer used, you can delete the disk to release the virtual resources. When a disk is deleted, EVS immediately destroys the metadata to ensure that d", + "product_code":"", + "title":"Deleting an EVS Disk", + "uri":"evs_01_0005.html", + "doc_type":"", + "p_code":"52", + "code":"54" + }, { "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", @@ -483,1113 +492,1122 @@ "uri":"evs_01_0111.html", "doc_type":"usermanual", "p_code":"", - "code":"54" - }, - { - "desc":"An EVS snapshot is a complete copy or image of the disk data at a specific point in time. Snapshots can be used as a disaster recovery (DR) approach, and you can use snap", - "product_code":"evs", - "title":"Snapshot Overview", - "uri":"evs_01_0098.html", - "doc_type":"usermanual", - "p_code":"54", "code":"55" }, { - "desc":"You can create an EVS snapshot on the management console to save the EVS disk data at a specific time point.Creating snapshots does not affect the performance of the disk", + "desc":"An EVS snapshot is a complete copy or image of the disk data taken at a specific time. Snapshot is a major disaster recovery (DR) approach, and you can use a snapshot to ", "product_code":"evs", - "title":"Creating a Snapshot", - "uri":"en-us_topic_0066615262.html", + "title":"EVS Snapshot Overview", + "uri":"evs_01_0098.html", "doc_type":"usermanual", - "p_code":"54", + "p_code":"55", "code":"56" }, { - "desc":"If a snapshot is no longer needed, you can delete it to release the virtual resources.The snapshot status must be Available or Error.If a disk is deleted, all the snapsho", + "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":"Deleting a Snapshot", - "uri":"evs_01_0011.html", + "title":"Using EVS Snapshots", + "uri":"evs_01_2720.html", "doc_type":"usermanual", - "p_code":"54", + "p_code":"55", "code":"57" }, { - "desc":"This section describes how to view the details of a snapshot.The snapshot list page is displayed.On the details page, view the snapshot information, such as the snapshot ", + "desc":"You can create EVS snapshots to save disk data at specific time points. Before you perform any critical operation, such as a data rollback, software upgrade, or data migr", "product_code":"evs", - "title":"Viewing Details of a Snapshot", - "uri":"evs_01_0122.html", + "title":"Creating an EVS Snapshot", + "uri":"evs_01_2721.html", "doc_type":"usermanual", - "p_code":"54", + "p_code":"57", "code":"58" }, { - "desc":"If data on an EVS disk is incorrect or damaged, you can roll back data from a snapshot to the source disk.Data of a snapshot can be rolled back only to its source disk. R", + "desc":"If data on an EVS disk is incorrect or damaged, you can roll back data from a snapshot to the source disk.Snapshot data can only be rolled back to source EVS disks. Rollb", "product_code":"evs", - "title":"Rolling Back Data from a Snapshot", + "title":"Rolling Back Disk Data from a Snapshot", "uri":"evs_01_0012.html", "doc_type":"usermanual", - "p_code":"54", + "p_code":"57", "code":"59" }, { - "desc":"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", + "desc":"This section describes how to create an EVS disk on the Snapshots page. You can also create an EVS disk from a snapshot by specifying the Create from snapshot parameter o", "product_code":"evs", - "title":"Creating an EVS Disk from a Snapshot", + "title":"Creating a Disk from a Snapshot", "uri":"evs_01_0013.html", "doc_type":"usermanual", - "p_code":"54", + "p_code":"57", "code":"60" }, { - "desc":"System disk encryptionSystem disks are created along with servers and cannot be created separately. So whether a system disk is encrypted or not depends on the image sele", + "desc":"You can check the snapshot details, including the region and AZ, source disk information, and tags.The Snapshots page is displayed.Select the snapshot and check the snaps", "product_code":"evs", - "title":"Managing Encrypted EVS Disks", - "uri":"evs_01_0009.html", + "title":"Checking EVS Snapshot Details", + "uri":"evs_01_0122.html", "doc_type":"usermanual", - "p_code":"", + "p_code":"57", "code":"61" }, { - "desc":"You can create shared VBD disks or shared SCSI disks. It is recommended that you attach a shared disk to the ECSs in the same ECS group to improve service reliability.Sha", + "desc":"If you no longer require certain snapshots or the snapshot quantity reaches the maximum allowed, you can delete the snapshots.The snapshot status must be Available or Err", "product_code":"evs", - "title":"Managing Shared EVS Disks", - "uri":"evs_01_0010.html", + "title":"Deleting an EVS Snapshot", + "uri":"evs_01_0011.html", "doc_type":"usermanual", - "p_code":"", + "p_code":"57", "code":"62" }, { - "desc":"EVS disk backups are created using the CBR service. For details, see Creating a Cloud Disk Backup in the Cloud Backup and Recovery User Guide.You can configure a backup p", - "product_code":"evs", - "title":"Managing EVS Backups", - "uri":"evs_01_0110.html", - "doc_type":"usermanual", + "desc":"EVS enables you to encrypt data on newly created disks as required.It uses the industry-standard XTS-AES-256 cryptographic algorithm and keys to encrypt EVS disks. Keys u", + "product_code":"", + "title":"Managing Encrypted EVS Disks", + "uri":"evs_01_0009.html", + "doc_type":"", "p_code":"", "code":"63" }, { - "desc":"EVS transfer allows you to transfer disks from one account to another. After a transfer succeeds, the ownership of the disk belongs to the target account only.Users can u", - "product_code":"evs", - "title":"Managing EVS Transfers", - "uri":"evs_01_0042.html", - "doc_type":"usermanual", + "desc":"Disk sharing allows you to create shared EVS disks. Shared EVS disks are block storage devices that support concurrent read/write operations and can be attached to multip", + "product_code":"", + "title":"Managing Shared EVS Disks", + "uri":"evs_01_0010.html", + "doc_type":"", "p_code":"", "code":"64" }, { - "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":"Manage EVS Tags", - "uri":"evs_01_0112.html", - "doc_type":"usermanual", + "desc":"EVS disk backups are created using the CBR service. For details, see section \"Creating a Cloud Disk Backup\" in the Cloud Backup and Recovery User Guide.You can configure ", + "product_code":"", + "title":"Managing EVS Disk Backups", + "uri":"evs_01_0110.html", + "doc_type":"", "p_code":"", "code":"65" }, { - "desc":"Tags identify EVS resources for purposes of easy categorization and quick search.", - "product_code":"evs", - "title":"Tag Overview", - "uri":"evs_01_0099.html", - "doc_type":"usermanual", - "p_code":"65", + "desc":"EVS transfer allows you to transfer disks from one account to another. After a transfer succeeds, the ownership of the disk belongs to the target account only.Users can u", + "product_code":"", + "title":"Managing EVS Transfers", + "uri":"evs_01_0042.html", + "doc_type":"", + "p_code":"", "code":"66" }, { - "desc":"You can add a tag for an existing EVS disk. You can also add tags during the disk creation. For details, see Create an EVS Disk.A tag is composed of a key-value pair.Key:", - "product_code":"evs", - "title":"Adding a Tag", - "uri":"evs_01_0014.html", - "doc_type":"usermanual", - "p_code":"65", + "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":"", + "title":"Managing EVS Tags", + "uri":"evs_01_0112.html", + "doc_type":"", + "p_code":"", "code":"67" }, { - "desc":"You can change the value of a tag for an existing disk, but cannot change the key of a tag.The disk list page is displayed.The disk details page is displayed.The Edit Tag", - "product_code":"evs", - "title":"Modifying a Tag", - "uri":"evs_01_0015.html", - "doc_type":"usermanual", - "p_code":"65", + "desc":"Tags identify EVS resources for purposes of easy categorization and quick search.", + "product_code":"", + "title":"Tag Overview", + "uri":"evs_01_0099.html", + "doc_type":"", + "p_code":"67", "code":"68" }, { - "desc":"If an existing tag is no longer needed, you can delete it.The disk list page is displayed.The disk details page is displayed.The Delete Tag page is displayed.The tag is d", - "product_code":"evs", - "title":"Deleting a Tag", - "uri":"evs_01_0016.html", - "doc_type":"usermanual", - "p_code":"65", + "desc":"You can add a tag for an existing EVS disk. You can also add tags when creating a disk. For details, see Creating an EVS Disk.A tag consists of a tag key and a tag value.", + "product_code":"", + "title":"Adding a Tag", + "uri":"evs_01_0014.html", + "doc_type":"", + "p_code":"67", "code":"69" }, { - "desc":"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 ", - "product_code":"evs", - "title":"Searching for Disks by Tag", - "uri":"evs_01_0019.html", - "doc_type":"usermanual", - "p_code":"65", + "desc":"You can change the value of a tag for an existing disk, but cannot change the key of a tag.A tag consists of a tag key and a tag value. Tag rules are described as follows", + "product_code":"", + "title":"Modifying a Tag", + "uri":"evs_01_0015.html", + "doc_type":"", + "p_code":"67", "code":"70" }, { - "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 EVS Replication (Deprecated)", - "uri":"evs_01_0023.html", - "doc_type":"usermanual", - "p_code":"", + "desc":"If an existing tag is no longer needed, you can delete it.The Elastic Volume Service page is displayed.The disk details page is displayed.The Delete Tag page is displayed", + "product_code":"", + "title":"Deleting a Tag", + "uri":"evs_01_0016.html", + "doc_type":"", + "p_code":"67", "code":"71" }, { - "desc":"For the EVS replication concepts, see EVS Replication (Deprecated). This chapter describes the basic functions and operations of EVS replication. Figure 1 shows the opera", - "product_code":"evs", - "title":"EVS Replication Operation Procedure (Deprecated)", - "uri":"evs_01_0060.html", - "doc_type":"usermanual", - "p_code":"71", + "desc":"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 ", + "product_code":"", + "title":"Searching for Disks by Tag", + "uri":"evs_01_0019.html", + "doc_type":"", + "p_code":"67", "code":"72" }, { - "desc":"Before you create an EVS replication pair, create a DR ECS in the secondary AZ for the production ECS. The DR ECS parameters must be consistent with those of the producti", - "product_code":"evs", - "title":"Creating a DR ECS (Deprecated)", - "uri":"evs_01_0024.html", - "doc_type":"usermanual", - "p_code":"71", + "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":"", + "title":"Managing EVS Replication (Deprecated)", + "uri":"evs_01_0023.html", + "doc_type":"", + "p_code":"", "code":"73" }, { - "desc":"Before you use EVS replication, bind a virtual IP address to the production server and DR server, respectively. Then configure the virtual IP address as the static IP add", - "product_code":"evs", - "title":"Configuring a Virtual IP Address for the Server (Deprecated)", - "uri":"evs_01_0026.html", - "doc_type":"usermanual", - "p_code":"71", + "desc":"For the EVS replication concepts, see EVS Replication (Deprecated). This chapter describes the basic functions and operations of EVS replication. Figure 1 shows the opera", + "product_code":"", + "title":"EVS Replication Operation Procedure (Deprecated)", + "uri":"evs_01_0060.html", + "doc_type":"", + "p_code":"73", "code":"74" }, { - "desc":"This section is used to guide users to collect the production ECS and DR ECS information, including the ECS IDs and the IDs of the EVS disks attached the ECSs.Two EVS dis", - "product_code":"evs", - "title":"Collecting ECS Information (Deprecated)", - "uri":"evs_01_0025.html", - "doc_type":"usermanual", - "p_code":"71", + "desc":"Before you create an EVS replication pair, create a DR ECS in the secondary AZ for the production ECS. The DR ECS parameters must be consistent with those of the producti", + "product_code":"", + "title":"Creating a DR ECS (Deprecated)", + "uri":"evs_01_0024.html", + "doc_type":"", + "p_code":"73", "code":"75" }, { - "desc":"Currently, users need to make API calls to create EVS replication pairs. Each server can have multiple EVS replication pairs. For details, see EVS Replication Pair in the", - "product_code":"evs", - "title":"Creating an EVS Replication Pair (Deprecated)", - "uri":"evs_01_0027.html", - "doc_type":"usermanual", - "p_code":"71", + "desc":"Before you use EVS replication, bind a virtual IP address to the production server and DR server, respectively. Then configure the virtual IP address as the static IP add", + "product_code":"", + "title":"Configuring a Virtual IP Address for the Server (Deprecated)", + "uri":"evs_01_0026.html", + "doc_type":"", + "p_code":"73", "code":"76" }, { - "desc":"Currently, users need to make API calls to create replication consistency groups and add EVS replication pairs to the groups. For details, see Replication Consistency Gro", - "product_code":"evs", - "title":"Creating a Replication Consistency Group (Deprecated)", - "uri":"evs_01_0028.html", - "doc_type":"usermanual", - "p_code":"71", + "desc":"This section is used to guide users to collect the production ECS and DR ECS information, including the ECS IDs and the IDs of the EVS disks attached the ECSs.Two EVS dis", + "product_code":"", + "title":"Collecting ECS Information (Deprecated)", + "uri":"evs_01_0025.html", + "doc_type":"", + "p_code":"73", "code":"77" }, { - "desc":"Currently, EVS replication pairs can be added to or removed from replication consistency groups through APIs only. For details, see Updating a Replication Consistency Gro", - "product_code":"evs", - "title":"Updating a Replication Consistency Group (Deprecated)", - "uri":"evs_01_0029.html", - "doc_type":"usermanual", - "p_code":"71", + "desc":"Currently, users need to make API calls to create EVS replication pairs. Each server can have multiple EVS replication pairs. For details, see EVS Replication Pair in the", + "product_code":"", + "title":"Creating an EVS Replication Pair (Deprecated)", + "uri":"evs_01_0027.html", + "doc_type":"", + "p_code":"73", "code":"78" }, { - "desc":"Production servers and production disks belong to the primary AZ, and DR servers and DR disks belong to the secondary AZ. Users can make API calls to perform a planned mi", - "product_code":"evs", - "title":"Planned Migration (Deprecated)", - "uri":"evs_01_0030.html", - "doc_type":"usermanual", - "p_code":"71", + "desc":"Currently, users need to make API calls to create replication consistency groups and add EVS replication pairs to the groups. For details, see Replication Consistency Gro", + "product_code":"", + "title":"Creating a Replication Consistency Group (Deprecated)", + "uri":"evs_01_0028.html", + "doc_type":"", + "p_code":"73", "code":"79" }, { - "desc":"When the production servers and disks in the primary AZ become faulty due to force majeure, users can make API calls to perform a failover for the replication consistency", - "product_code":"evs", - "title":"Failover (Deprecated)", - "uri":"evs_01_0031.html", - "doc_type":"usermanual", - "p_code":"71", + "desc":"Currently, EVS replication pairs can be added to or removed from replication consistency groups through APIs only. For details, see Updating a Replication Consistency Gro", + "product_code":"", + "title":"Updating a Replication Consistency Group (Deprecated)", + "uri":"evs_01_0029.html", + "doc_type":"", + "p_code":"73", "code":"80" }, { - "desc":"When the production servers and disks in the primary AZ become faulty due to force majeure and a failover has been performed, enable the DR servers and disks to provide s", - "product_code":"evs", - "title":"Reprotection (Deprecated)", - "uri":"evs_01_0032.html", - "doc_type":"usermanual", - "p_code":"71", + "desc":"Production servers and production disks belong to the primary AZ, and DR servers and DR disks belong to the secondary AZ. Users can make API calls to perform a planned mi", + "product_code":"", + "title":"Planned Migration (Deprecated)", + "uri":"evs_01_0030.html", + "doc_type":"", + "p_code":"73", "code":"81" }, { - "desc":"Users can make an API call to expand the EVS disks in one or multiple EVS replication pairs of a replication consistency group. In such an expansion operation, two EVS di", - "product_code":"evs", - "title":"Expanding EVS Disks in a Replication Consistency Group (Deprecated)", - "uri":"evs_01_0043.html", - "doc_type":"usermanual", - "p_code":"71", + "desc":"When the production servers and disks in the primary AZ become faulty due to force majeure, users can make API calls to perform a failover for the replication consistency", + "product_code":"", + "title":"Failover (Deprecated)", + "uri":"evs_01_0031.html", + "doc_type":"", + "p_code":"73", "code":"82" }, { - "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":"Manage EVS Quotas", - "uri":"evs_01_0069.html", - "doc_type":"usermanual", - "p_code":"", + "desc":"When the production servers and disks in the primary AZ become faulty due to force majeure and a failover has been performed, enable the DR servers and disks to provide s", + "product_code":"", + "title":"Reprotection (Deprecated)", + "uri":"evs_01_0032.html", + "doc_type":"", + "p_code":"73", "code":"83" }, { - "desc":"Quotas are enforced for service resources on the platform to prevent unforeseen spikes in resource usage. Quotas can limit the number or amount of resources available to ", - "product_code":"evs", - "title":"Querying EVS Resource Quotas", - "uri":"evs_01_0070.html", - "doc_type":"usermanual", - "p_code":"83", + "desc":"Users can make an API call to expand the EVS disks in one or multiple EVS replication pairs of a replication consistency group. In such an expansion operation, two EVS di", + "product_code":"", + "title":"Expanding EVS Disks in a Replication Consistency Group (Deprecated)", + "uri":"evs_01_0043.html", + "doc_type":"", + "p_code":"73", "code":"84" }, { - "desc":"If any resource quota no longer meets your service requirements, you can apply for a higher quota.The system does not support online quota adjustment. If you need to adju", - "product_code":"evs", - "title":"Increasing EVS Resource Quotas", - "uri":"evs_01_0071.html", - "doc_type":"usermanual", - "p_code":"83", + "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":"", + "title":"Managing EVS Quotas", + "uri":"evs_01_0069.html", + "doc_type":"", + "p_code":"", "code":"85" }, { - "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 EVS Monitoring Data", - "uri":"evs_01_2704.html", - "doc_type":"usermanual", - "p_code":"", + "desc":"Quotas are enforced for service resources on the platform to prevent unforeseen spikes in resource usage. Quotas can limit the number or amount of resources available to ", + "product_code":"", + "title":"Querying EVS Resource Quotas", + "uri":"evs_01_0070.html", + "doc_type":"", + "p_code":"85", "code":"86" }, { - "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", - "doc_type":"usermanual", - "p_code":"86", + "desc":"If any resource quota no longer meets your service requirements, you can apply for a higher quota.The system does not support online quota adjustment. If you need to adju", + "product_code":"", + "title":"Increasing EVS Resource Quotas", + "uri":"evs_01_0071.html", + "doc_type":"", + "p_code":"85", "code":"87" }, { - "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":"Auditing EVS Operation Records", - "uri":"evs_01_0046.html", - "doc_type":"usermanual", + "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":"", + "title":"Cloud Eye Monitoring", + "uri":"evs_01_2704.html", + "doc_type":"", "p_code":"", "code":"88" }, { - "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":"", + "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":"", + "title":"Viewing Basic EVS Monitoring Data", + "uri":"evs_01_0044.html", + "doc_type":"", + "p_code":"88", "code":"89" }, { - "desc":"How Do I Start Using a Newly Created Disk?Can EVS Disks Be Used Directly for Storage?Can EVS Disks Be Used Alone?Can I Change the AZ of My Disk?Can I Change the Disk Type", - "product_code":"evs", - "title":"Summary", - "uri":"evs_01_0096.html", - "doc_type":"usermanual", - "p_code":"89", + "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":"", + "title":"Recording EVS Operations Using CTS", + "uri":"evs_01_0046.html", + "doc_type":"", + "p_code":"", "code":"90" }, { "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":"89", + "product_code":"", + "title":"FAQ", + "uri":"evs_faq_0001.html", + "doc_type":"", + "p_code":"", "code":"91" }, { - "desc":"A newly created disk must be attached to a server and then initialized in the server OS before you can use it.For more information, see Process Overview.", - "product_code":"evs", - "title":"How Do I Start Using a Newly Created Disk?", - "uri":"evs_faq_0033.html", - "doc_type":"usermanual", + "desc":"How Do I Start Using a Newly Created Disk?Can EVS Disks Be Used Directly for Storage?Can EVS Disks Be Used Alone?Can I Change the AZ of My Disk?Can I Change the Disk Type", + "product_code":"", + "title":"Summary", + "uri":"evs_01_0096.html", + "doc_type":"", "p_code":"91", "code":"92" }, { - "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", + "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":"", + "title":"General", + "uri":"evs_01_0081.html", + "doc_type":"", "p_code":"91", "code":"93" }, { - "desc":"No.EVS disks must be attached to servers before you can use them.", - "product_code":"evs", - "title":"Can EVS Disks Be Used Alone?", - "uri":"evs_faq_0054.html", - "doc_type":"usermanual", - "p_code":"91", + "desc":"A newly created disk must be attached to a server and then initialized in the server OS before you can use it.For more information, see Getting Started.", + "product_code":"", + "title":"How Do I Start Using a Newly Created Disk?", + "uri":"evs_faq_0033.html", + "doc_type":"", + "p_code":"93", "code":"94" }, { - "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":"91", + "desc":"No.EVS disks must be attached to cloud servers before use. You cannot use EVS disks alone to store data.", + "product_code":"", + "title":"Can EVS Disks Be Used Directly for Storage?", + "uri":"evs_faq_0065.html", + "doc_type":"", + "p_code":"93", "code":"95" }, { - "desc":"Disk names are used to identify disks. After a disk is created, you can perform operations in this section to change the disk name if needed.The disk list page is display", - "product_code":"evs", - "title":"How Do I Change the Name of My Disk?", - "uri":"evs_01_0061.html", - "doc_type":"usermanual", - "p_code":"91", + "desc":"No.EVS disks must be attached to servers before you can use them.", + "product_code":"", + "title":"Can EVS Disks Be Used Alone?", + "uri":"evs_faq_0054.html", + "doc_type":"", + "p_code":"93", "code":"96" }, { - "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.", - "product_code":"evs", - "title":"Can I Change the AZ of My Disk?", - "uri":"evs_faq_0048.html", - "doc_type":"usermanual", - "p_code":"91", + "desc":"To do so, perform the following operations:The disk list page is displayed.View more information on the Summary tab.", + "product_code":"", + "title":"How Can I View My Disk Details?", + "uri":"evs_faq_0066.html", + "doc_type":"", + "p_code":"93", "code":"97" }, { - "desc":"The following table describes whether the disk type, device type, sharing, and encryption attributes of a disk can be changed.However, you can:Create a backup for the dis", - "product_code":"evs", - "title":"Can I Change the Disk Type, Device Type, or Sharing Attribute of My Disk?", - "uri":"evs_faq_0045.html", - "doc_type":"usermanual", - "p_code":"91", + "desc":"Disk names are used to identify disks. After a disk is created, you can perform operations in this section to change the disk name if needed.The disk list page is display", + "product_code":"", + "title":"How Do I Change the Name of My Disk?", + "uri":"evs_01_0061.html", + "doc_type":"", + "p_code":"93", "code":"98" }, { - "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.", - "product_code":"evs", - "title":"What Should I Do If an Error Occurs on My EVS Disk?", - "uri":"evs_faq_0014.html", - "doc_type":"usermanual", - "p_code":"91", + "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.", + "product_code":"", + "title":"Can I Change the AZ of My Disk?", + "uri":"evs_faq_0048.html", + "doc_type":"", + "p_code":"93", "code":"99" }, { - "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", - "product_code":"evs", - "title":"Why Do Some of My EVS Disks Not Have WWN Information?", - "uri":"evs_faq_0021.html", - "doc_type":"usermanual", - "p_code":"91", + "desc":"The following table describes whether the disk type, device type, sharing, and encryption attributes of a disk can be changed.However, you can:Create a backup for the dis", + "product_code":"", + "title":"Can I Change the Disk Type, Device Type, or Sharing Attribute of My Disk?", + "uri":"evs_faq_0045.html", + "doc_type":"", + "p_code":"93", "code":"100" }, { - "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 ", - "product_code":"evs", - "title":"What Should I Do If My EVS Replication Quotas Are Insufficient? (Deprecated)", - "uri":"evs_faq_0020.html", - "doc_type":"usermanual", - "p_code":"91", + "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.", + "product_code":"", + "title":"What Should I Do If an Error Occurs on My EVS Disk?", + "uri":"evs_faq_0014.html", + "doc_type":"", + "p_code":"93", "code":"101" }, { - "desc":"Data migration involves the following scenarios:Cross-AZ data migration: Disk data can be migrated from one AZ to another through disk backups. You can create backups for", - "product_code":"evs", - "title":"How Can I Migrate Data from an EVS Disk?", - "uri":"evs_faq_0059.html", - "doc_type":"usermanual", - "p_code":"91", + "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", + "product_code":"", + "title":"Why Do Some of My EVS Disks Not Have WWN Information?", + "uri":"evs_faq_0021.html", + "doc_type":"", + "p_code":"93", "code":"102" }, { - "desc":"A system disk runs the server OS. It is like drive C in a PC.When a server is created, a system disk is automatically created and attached. You cannot create a system dis", - "product_code":"evs", - "title":"What Are the Differences Between System Disks and Data Disks?", - "uri":"evs_faq_0084.html", - "doc_type":"usermanual", - "p_code":"91", + "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 ", + "product_code":"", + "title":"What Should I Do If My EVS Replication Quotas Are Insufficient? (Deprecated)", + "uri":"evs_faq_0020.html", + "doc_type":"", + "p_code":"93", "code":"103" }, { - "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":"91", + "desc":"Data migration involves the following scenarios:Cross-AZ data migration: Disk data can be migrated from one AZ to another through disk backups. You can create backups for", + "product_code":"", + "title":"How Can I Migrate Data from an EVS Disk?", + "uri":"evs_faq_0059.html", + "doc_type":"", + "p_code":"93", "code":"104" }, { - "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":"91", + "desc":"A system disk runs the server OS. It is like drive C in a PC.When a server is created, a system disk is automatically created and attached. You cannot create a system dis", + "product_code":"", + "title":"What Are the Differences Between System Disks and Data Disks?", + "uri":"evs_faq_0084.html", + "doc_type":"", + "p_code":"93", "code":"105" }, { - "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":"91", + "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":"", + "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":"", + "p_code":"93", "code":"106" }, { - "desc":"Before an EVS disk is attached, the system will call the reserveVolume EVS API to check whether the disk can be attached. If it can be attached, the system then changes t", - "product_code":"evs", - "title":"What Does the \"reserveVolume\" Trace Mean in CTS?", - "uri":"evs_faq_0095.html", - "doc_type":"usermanual", - "p_code":"91", + "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":"", + "title":"What Are the Differences Between MBR and GPT Partition Styles?", + "uri":"evs_faq_0092.html", + "doc_type":"", + "p_code":"93", "code":"107" }, { - "desc":"EVS disks must be attached to servers before you can use them. For how to upload files, see section \"How Do I Upload Files to My ECS?\" in the Elastic Cloud Server FAQs.", - "product_code":"evs", - "title":"How Can I Upload Files to My EVS Disk?", - "uri":"evs_faq_0096.html", - "doc_type":"usermanual", - "p_code":"91", + "desc":"Before an EVS disk is attached, the system will call the reserveVolume EVS API to check whether the disk can be attached. If it can be attached, the system then changes t", + "product_code":"", + "title":"What Does the \"reserveVolume\" Trace Mean in CTS?", + "uri":"evs_faq_0095.html", + "doc_type":"", + "p_code":"93", "code":"108" }, { - "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":"Attachment", - "uri":"evs_01_0078.html", - "doc_type":"usermanual", - "p_code":"89", + "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":"", + "title":"How Can I Download My EVS Disk Data to a Local PC?", + "uri":"evs_faq_0087.html", + "doc_type":"", + "p_code":"93", "code":"109" }, { - "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":"109", + "desc":"EVS disks must be attached to servers before you can use them. For how to upload files, see section \"How Do I Upload Files to My ECS?\" in the Elastic Cloud Server FAQs.", + "product_code":"", + "title":"How Can I Upload Files to My EVS Disk?", + "uri":"evs_faq_0096.html", + "doc_type":"", + "p_code":"93", "code":"110" }, { - "desc":"My disk cannot be attached to a server.Possible causes are listed here in order of their probability.If the fault persists after you have ruled out one cause, move on to ", - "product_code":"evs", - "title":"Why Can't I Attach My Disk to a Server?", - "uri":"evs_faq_0025.html", - "doc_type":"usermanual", - "p_code":"109", + "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":"", + "title":"Attachment", + "uri":"evs_01_0078.html", + "doc_type":"", + "p_code":"91", "code":"111" }, { - "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", - "product_code":"evs", - "title":"Can I Attach a Disk to Multiple Servers?", - "uri":"evs_faq_0006.html", - "doc_type":"usermanual", - "p_code":"109", + "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":"", + "title":"Why Can't I View the Attached Data Disk on the Server?", + "uri":"evs_faq_0022.html", + "doc_type":"", + "p_code":"111", "code":"112" }, { - "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", - "product_code":"evs", - "title":"Can I Attach a Disk to a Server in Another AZ?", - "uri":"evs_faq_0036.html", - "doc_type":"usermanual", - "p_code":"109", + "desc":"My disk cannot be attached to a server.Possible causes are listed here in order of their probability.If the fault persists after you have ruled out one cause, move on to ", + "product_code":"", + "title":"Why Can't I Attach My Disk to a Server?", + "uri":"evs_faq_0025.html", + "doc_type":"", + "p_code":"111", "code":"113" }, { - "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", - "product_code":"evs", - "title":"How Can I Add a Data Disk to an Existing Server?", - "uri":"evs_faq_0043.html", - "doc_type":"usermanual", - "p_code":"109", + "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", + "product_code":"", + "title":"Can I Attach a Disk to Multiple Servers?", + "uri":"evs_faq_0006.html", + "doc_type":"", + "p_code":"111", "code":"114" }, { - "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":"109", + "desc":"No.Disks and the server you attach the disks to must be in the same AZ. The same is true for shared disks. A shared disk can only be attached to the servers in the same A", + "product_code":"", + "title":"Can I Attach a Disk to a Server in a Different AZ?", + "uri":"evs_faq_0036.html", + "doc_type":"", + "p_code":"111", "code":"115" }, { - "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":"109", + "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", + "product_code":"", + "title":"How Can I Add a Data Disk to an Existing Server?", + "uri":"evs_faq_0043.html", + "doc_type":"", + "p_code":"111", "code":"116" }, { - "desc":"This section describes how to change the function of a disk on the original server.System disk created along with a server: You can detach the system disk and then re-att", - "product_code":"evs", - "title":"Can I Change the Function of a System Disk or Data Disk Created Along with a Server?", - "uri":"evs_faq_0078.html", - "doc_type":"usermanual", - "p_code":"109", + "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":"", + "title":"Can I Attach Different Types of Disks to the Same Server?", + "uri":"evs_faq_0055.html", + "doc_type":"", + "p_code":"111", "code":"117" }, { - "desc":"You find that the device name displayed in the ECS OS is different from that displayed on the management console and you cannot determine which disk name is correct. This", - "product_code":"evs", - "title":"How Do I Obtain My Disk Device Name in the ECS OS Using the Device Identifier Provided on the Console?", - "uri":"evs_faq_0094.html", - "doc_type":"usermanual", - "p_code":"109", + "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":"", + "title":"What Should I Do If a Linux EVS Disk Is Attached to a Windows Server?", + "uri":"evs_faq_0076.html", + "doc_type":"", + "p_code":"111", "code":"118" }, { - "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":"Capacity Expansion", - "uri":"evs_01_0077.html", - "doc_type":"usermanual", - "p_code":"89", + "desc":"This section describes how to change the function of a disk on the original server.System disk created along with a server: You can detach the system disk and then re-att", + "product_code":"", + "title":"Can I Change the Function of a System Disk or Data Disk Created Along with a Server?", + "uri":"evs_faq_0078.html", + "doc_type":"", + "p_code":"111", "code":"119" }, { - "desc":"No. The disk capacity can only be expanded, and temporary capacity expansion is not supported.", - "product_code":"evs", - "title":"Can I Reduce or Temporarily Expand the Disk Capacity?", - "uri":"evs_faq_0026.html", - "doc_type":"usermanual", - "p_code":"119", + "desc":"You find that the device name displayed in the ECS OS is different from that displayed on the management console and you cannot determine which disk name is correct. This", + "product_code":"", + "title":"How Do I Obtain My Disk Device Name in the ECS OS Using the Device Identifier Provided on the Console?", + "uri":"evs_faq_0094.html", + "doc_type":"", + "p_code":"111", "code":"120" }, { - "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":"119", + "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":"", + "title":"Capacity Expansion", + "uri":"evs_01_0077.html", + "doc_type":"", + "p_code":"91", "code":"121" }, { - "desc":"Data will not be deleted during a system disk or data disk capacity expansion. However, incorrect operations during an expansion may result in data loss or exceptions. Ex", - "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":"119", + "desc":"No. The disk capacity can only be expanded, and temporary capacity expansion is not supported.", + "product_code":"", + "title":"Can I Reduce or Temporarily Expand the Disk Capacity?", + "uri":"evs_faq_0026.html", + "doc_type":"", + "p_code":"121", "code":"122" }, { - "desc":"Yes. If backups or snapshots have been created for disks before capacity was expanded, you can restore your disk data from these backups or snapshots after the capacity i", - "product_code":"evs", - "title":"Can I Use Backups or Snapshots Created Before Capacity Expansion to Restore Data on Expanded Disks?", - "uri":"evs_faq_0023.html", - "doc_type":"usermanual", - "p_code":"119", + "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":"", + "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":"", + "p_code":"121", "code":"123" }, { - "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 ", - "product_code":"evs", - "title":"Do I Need to Restart the Server After Expanding the Disk Capacity?", - "uri":"evs_faq_0042.html", - "doc_type":"usermanual", - "p_code":"119", + "desc":"Data will not be deleted during a system disk or data disk capacity expansion. However, incorrect operations during an expansion may result in data loss or exceptions. Yo", + "product_code":"", + "title":"Will My Disk Data Be Lost After I Expand the Disk Capacity?", + "uri":"evs_faq_0044.html", + "doc_type":"", + "p_code":"121", "code":"124" }, { - "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 ", - "product_code":"evs", - "title":"Do I Need to Detach an EVS Disk Before Expanding Its Capacity?", - "uri":"evs_faq_0028.html", - "doc_type":"usermanual", - "p_code":"119", + "desc":"Yes. If backups or snapshots have been created for disks before capacity was expanded, you can restore your disk data from these backups or snapshots after the capacity i", + "product_code":"", + "title":"Can I Use Backups or Snapshots Created Before Capacity Expansion to Restore Data on Expanded Disks?", + "uri":"evs_faq_0023.html", + "doc_type":"", + "p_code":"121", "code":"125" }, { - "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 TiB After Expansion?", - "uri":"evs_faq_0024.html", - "doc_type":"usermanual", - "p_code":"119", + "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 ", + "product_code":"", + "title":"Do I Need to Restart the Server After Expanding the Disk Capacity?", + "uri":"evs_faq_0042.html", + "doc_type":"", + "p_code":"121", "code":"126" }, { - "desc":"In Windows, if you already have a D drive and want to add an E drive, refer to the following:The System Disk: Add Additional Capacity to New Volume (F:) and Data Disk: Ad", - "product_code":"evs", - "title":"How Can I Allocate Newly Added Space to a New Partition?", - "uri":"evs_faq_0029.html", - "doc_type":"usermanual", - "p_code":"119", + "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 ", + "product_code":"", + "title":"Do I Need to Detach an EVS Disk Before Expanding Its Capacity?", + "uri":"evs_faq_0028.html", + "doc_type":"", + "p_code":"121", "code":"127" }, { - "desc":"In Windows, if your disk already has, for example, a D: drive and you want to add space to this volume, refer to the following:The System Disk: Add Additional Capacity to", - "product_code":"evs", - "title":"How Can I Allocate Newly Added Space to an Existing Partition?", - "uri":"evs_faq_0030.html", - "doc_type":"usermanual", - "p_code":"119", + "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":"", + "title":"What Should I Do If My Disk Capacity Exceeds 2 TiB After Expansion?", + "uri":"evs_faq_0024.html", + "doc_type":"", + "p_code":"121", "code":"128" }, { - "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", - "product_code":"evs", - "title":"Why Did My Disk Capacity Remain Unchanged on the Server After Capacity Expansion?", - "uri":"evs_faq_0027.html", - "doc_type":"usermanual", - "p_code":"119", + "desc":"In Windows, if you already have a D drive and want to add an E drive, refer to the following:The System Disk: Create a New Volume with the Additional Space and Data Disk:", + "product_code":"", + "title":"How Can I Allocate Newly Added Space to a New Partition?", + "uri":"evs_faq_0029.html", + "doc_type":"", + "p_code":"121", "code":"129" }, { - "desc":"Capacity expansion is not allowed for the disk.Possible causes are listed here in order of their probability.If the fault persists after you have ruled out one cause, mov", - "product_code":"evs", - "title":"Why Can't I Expand Capacity for My Disk?", - "uri":"evs_faq_0074.html", - "doc_type":"usermanual", - "p_code":"119", + "desc":"In Windows, if your disk already has, for example, a D drive and you want to add space to this drive, refer to the following:The System Disk: Add the Additional Space to ", + "product_code":"", + "title":"How Can I Allocate Newly Added Space to an Existing Partition?", + "uri":"evs_faq_0030.html", + "doc_type":"", + "p_code":"121", "code":"130" }, { - "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":"119", + "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", + "product_code":"", + "title":"Why Did My Disk Capacity Remain Unchanged on the Server After Capacity Expansion?", + "uri":"evs_faq_0027.html", + "doc_type":"", + "p_code":"121", "code":"131" }, { - "desc":"If the root partition of your quickly provisioned BMS is too small, extend the root partition by referring to the following procedure.This example uses CentOS 7.3 and sys", - "product_code":"evs", - "title":"How Do I Extend the Root Partition of a Quickly Provisioned BMS?", - "uri":"evs_faq_0082.html", - "doc_type":"usermanual", - "p_code":"119", + "desc":"Capacity expansion is not allowed for the disk.Possible causes are listed here in order of their probability.If the fault persists after you have ruled out one cause, mov", + "product_code":"", + "title":"Why Can't I Expand Capacity for My Disk?", + "uri":"evs_faq_0074.html", + "doc_type":"", + "p_code":"121", "code":"132" }, { - "desc":"You can use either fdisk or parted to view the disk partition style.Method 1: Check Partition Style and File System Format Using fdiskMethod 2: Check Partition Style and ", - "product_code":"evs", - "title":"How Do I View the Disk Partition Style in Linux?", - "uri":"evs_faq_0131.html", - "doc_type":"usermanual", - "p_code":"119", + "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":"", + "title":"How Do I Extend the File System of an Unpartitioned Data Disk in Linux?", + "uri":"evs_faq_0073.html", + "doc_type":"", + "p_code":"121", "code":"133" }, { - "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":"Detachment", - "uri":"evs_01_0079.html", - "doc_type":"usermanual", - "p_code":"89", + "desc":"If the root partition of your quickly provisioned BMS is too small, extend the root partition by referring to the following procedure.This example uses CentOS 7.3 and sys", + "product_code":"", + "title":"How Do I Extend the Root Partition of a Quickly Provisioned BMS?", + "uri":"evs_faq_0082.html", + "doc_type":"", + "p_code":"121", "code":"134" }, { - "desc":"It depends on if the disk is encrypted or not.EncryptedThe CMK is disabled or scheduled for deletion.The disk can still be used, but there is no guarantee for how long it", - "product_code":"evs", - "title":"If I Detach a Disk, Will I Lose the Data on My Disk?", - "uri":"evs_faq_0012.html", - "doc_type":"usermanual", - "p_code":"134", + "desc":"You can use either fdisk or parted to view the disk partition style.Method 1: Check Partition Style and File System Format Using fdiskMethod 2: Check Partition Style and ", + "product_code":"", + "title":"How Do I View the Disk Partition Style in Linux?", + "uri":"evs_faq_0131.html", + "doc_type":"", + "p_code":"121", "code":"135" }, { - "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", - "product_code":"evs", - "title":"Why Can't I Detach My Disk?", - "uri":"evs_faq_0056.html", - "doc_type":"usermanual", - "p_code":"134", + "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":"", + "title":"Detachment", + "uri":"evs_01_0079.html", + "doc_type":"", + "p_code":"91", "code":"136" }, { - "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":"Deletion", - "uri":"evs_01_0083.html", - "doc_type":"usermanual", - "p_code":"89", + "desc":"It depends on if the disk is encrypted or not.EncryptedThe CMK is disabled or scheduled for deletion.The disk can still be used, but there is no guarantee for how long it", + "product_code":"", + "title":"If I Detach a Disk, Will I Lose the Data on My Disk?", + "uri":"evs_faq_0012.html", + "doc_type":"", + "p_code":"136", "code":"137" }, { - "desc":"Check whether the disk has any snapshots or backups created.If there are, use a snapshot or backup to restore the disk data to the state when the snapshot or backup was c", - "product_code":"evs", - "title":"How Can I Recover Data from a Disk That Was Accidentally Deleted?", - "uri":"evs_faq_0079.html", - "doc_type":"usermanual", - "p_code":"137", + "desc":"EVS disks can be used as system disks or data disks, but the way you detach each one is different.In Linux, a system disk is typically mounted on /dev/vda. In Windows, a ", + "product_code":"", + "title":"Why Can't I Detach My Disk?", + "uri":"evs_faq_0056.html", + "doc_type":"", + "p_code":"136", "code":"138" }, { "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":"Capacity", - "uri":"evs_01_0082.html", - "doc_type":"usermanual", - "p_code":"89", + "product_code":"", + "title":"Deletion", + "uri":"evs_01_0083.html", + "doc_type":"", + "p_code":"91", "code":"139" }, { - "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", + "desc":"Check whether the disk has any snapshots or backups created.If there are, use a snapshot or backup to restore the disk data to the state when the snapshot or backup was c", + "product_code":"", + "title":"How Can I Recover Data from a Disk That Was Accidentally Deleted?", + "uri":"evs_faq_0079.html", + "doc_type":"", "p_code":"139", "code":"140" }, { - "desc":"If your disk space starts to fill up, you can:Create a new disk and attach it to the server. For details, see Create an EVS Disk.Expand the capacity of the existing disk.", - "product_code":"evs", - "title":"What Should I Do If My Disk Starts to Run Out of Space?", - "uri":"evs_faq_0032.html", - "doc_type":"usermanual", - "p_code":"139", + "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":"", + "title":"Capacity", + "uri":"evs_01_0082.html", + "doc_type":"", + "p_code":"91", "code":"141" }, { - "desc":"The capacity of a single disk can be expanded to up to 32 TiB. If this still fails to meet your needs, it is recommended that you create RAID arrays with EVS disks or man", - "product_code":"evs", - "title":"What Can I Do If the Capacity of My Disk Reaches the Maximum But I Still Need More Space?", - "uri":"evs_faq_0069.html", - "doc_type":"usermanual", - "p_code":"139", + "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":"", + "title":"What Is the Maximum Capacity Supported for the System and Data Disks?", + "uri":"evs_faq_0031.html", + "doc_type":"", + "p_code":"141", "code":"142" }, { - "desc":"If your disk capacity is greater than 2 TiB, do not use fdisk to partition the disk. Or any space in excess of 2 TiB will be unable to show up after the disk is partition", - "product_code":"evs", - "title":"What Should I Do If I Use fdisk to Initialize a Disk Larger Than 2 TiB and Then the Space in Excess of 2 TiB Cannot Be Displayed?", - "uri":"evs_faq_0035.html", - "doc_type":"usermanual", - "p_code":"139", + "desc":"If your disk space starts to fill up, you can:Create a new disk and attach it to the server. For details, see Creating an EVS Disk.Expand the capacity of the existing dis", + "product_code":"", + "title":"What Should I Do If My Disk Starts to Run Out of Space?", + "uri":"evs_faq_0032.html", + "doc_type":"", + "p_code":"141", "code":"143" }, { - "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":"139", + "desc":"When the EVS disk space on a server is insufficient, the server running speed will be affected, which will further affect user experience. You can clean up the disk space", + "product_code":"", + "title":"How Do I Clean Up My Disk Space on a Windows Server?", + "uri":"evs_02_0010.html", + "doc_type":"", + "p_code":"141", "code":"144" }, { - "desc":"Sorry, you cannot.Currently, the capacity of an EVS disk cannot be transferred to another disk. Multiple EVS disks cannot be combined into a single, larger disk, either.C", - "product_code":"evs", - "title":"Can I Transfer the Data Disk Capacity to a System Disk?", - "uri":"evs_faq_0061.html", - "doc_type":"usermanual", - "p_code":"139", + "desc":"The capacity of a single disk can be expanded to up to 32 TiB. If this still fails to meet your needs, it is recommended that you create RAID arrays with EVS disks or man", + "product_code":"", + "title":"What Can I Do If the Capacity of My Disk Reaches the Maximum But I Still Need More Space?", + "uri":"evs_faq_0069.html", + "doc_type":"", + "p_code":"141", "code":"145" }, { - "desc":"Troubleshoot this issue by performing the following steps:Check whether the disk partition usage is 100% or almost 100%.df -hChecking the partition usageIn this example, ", - "product_code":"evs", - "title":"Why the Space of My New Disk Is Full After I Uploaded Only 500 MB of Files to the Disk?", - "uri":"evs_faq_280807.html", - "doc_type":"usermanual", - "p_code":"139", + "desc":"If your disk capacity is greater than 2 TiB, do not use fdisk to partition the disk. Or any space in excess of 2 TiB will be unable to show up after the disk is partition", + "product_code":"", + "title":"What Should I Do If I Use fdisk to Initialize a Disk Larger Than 2 TiB and Then the Space in Excess of 2 TiB Cannot Be Displayed?", + "uri":"evs_faq_0035.html", + "doc_type":"", + "p_code":"141", "code":"146" }, { - "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":"Snapshot", - "uri":"evs_01_0092.html", - "doc_type":"usermanual", - "p_code":"89", + "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":"", + "title":"How Can I View My Disk Usage?", + "uri":"evs_faq_0053.html", + "doc_type":"", + "p_code":"141", "code":"147" }, { - "desc":"A snapshot creation will fail if its source disk is in an intermediate state, such as Attaching and Expanding, or an abnormal state, such as Error and Restoration failed.", - "product_code":"evs", - "title":"What Are the Typical Causes of a Snapshot Creation Failure?", - "uri":"evs_faq_0046.html", - "doc_type":"usermanual", - "p_code":"147", + "desc":"Sorry, you cannot.Currently, the capacity of an EVS disk cannot be transferred to another disk. Multiple EVS disks cannot be combined into a single, larger disk, either.C", + "product_code":"", + "title":"Can I Transfer the Data Disk Capacity to a System Disk?", + "uri":"evs_faq_0061.html", + "doc_type":"", + "p_code":"141", "code":"148" }, { - "desc":"No, but you can develop a program to periodically create snapshots through APIs. Alternatively, you may use the CBR service and enable auto backup to create backups perio", - "product_code":"evs", - "title":"Does EVS Support Automatic Snapshot Creation?", - "uri":"evs_faq_0051.html", - "doc_type":"usermanual", - "p_code":"147", + "desc":"Troubleshoot this issue by performing the following steps:Check whether the disk partition usage is 100% or almost 100%.df -hChecking the partition usageIn this example, ", + "product_code":"", + "title":"Why the Space of My New Disk Is Full After I Uploaded Only 500 MB of Files to the Disk?", + "uri":"evs_faq_280807.html", + "doc_type":"", + "p_code":"141", "code":"149" }, { - "desc":"No.Snapshots cannot be created for multiple disks at the same time. You must create snapshots for disks one by one.", - "product_code":"evs", - "title":"Can I Create Snapshots for Multiple Disks at a Time?", - "uri":"evs_faq_0070.html", - "doc_type":"usermanual", - "p_code":"147", + "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":"", + "title":"Snapshot", + "uri":"evs_01_0092.html", + "doc_type":"", + "p_code":"91", "code":"150" }, { - "desc":"There are two types of snapshots: manual snapshots you create on-demand and automatic snapshots created by the system.Manual snapshots: You may manually create snapshots ", - "product_code":"evs", - "title":"How Is a Snapshot Created for My Disk?", - "uri":"evs_faq_0057.html", - "doc_type":"usermanual", - "p_code":"147", + "desc":"A snapshot creation will fail if its source disk is in an intermediate state, such as Attaching and Expanding, or an abnormal state, such as Error and Restoration failed.", + "product_code":"", + "title":"What Are the Typical Causes of a Snapshot Creation Failure?", + "uri":"evs_faq_0046.html", + "doc_type":"", + "p_code":"150", "code":"151" }, { - "desc":"Possible causes are as follows:Snapshot data can be rolled back only when the status of the snapshot's source disk is Available or Rollback failed. If the snapshot's sour", - "product_code":"evs", - "title":"Why Can't I Roll Back My Disk Data from a Snapshot?", - "uri":"evs_faq_0058.html", - "doc_type":"usermanual", - "p_code":"147", + "desc":"No, but you can develop a program to periodically create snapshots through APIs. Alternatively, you may use the CBR service and enable auto backup to create backups perio", + "product_code":"", + "title":"Does EVS Support Automatic Snapshot Creation?", + "uri":"evs_faq_0051.html", + "doc_type":"", + "p_code":"150", "code":"152" }, { - "desc":"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.If you have for", - "product_code":"evs", - "title":"Can I Roll Back the Data from a Snapshot After Reinstalling the OS or Formatting the Disk?", - "uri":"evs_faq_0062.html", - "doc_type":"usermanual", - "p_code":"147", + "desc":"No. Snapshots cannot be created for multiple disks at the same time. You must create snapshots for disks one by one.", + "product_code":"", + "title":"Can I Create Snapshots for Multiple Disks at a Time?", + "uri":"evs_faq_0070.html", + "doc_type":"", + "p_code":"150", "code":"153" }, { - "desc":"When you create a snapshot for a disk for the first time, the snapshot is a full snapshot, and its size is the same as the disk size. Subsequent snapshots created for the", - "product_code":"evs", - "title":"How Is the Snapshot Size Calculated?", - "uri":"evs_faq_0063.html", - "doc_type":"usermanual", - "p_code":"147", + "desc":"There are two types of snapshots: manual snapshots you create on-demand and automatic snapshots created by the system.Manual snapshots: You may manually create snapshots ", + "product_code":"", + "title":"How Is a Snapshot Created for My Disk?", + "uri":"evs_faq_0057.html", + "doc_type":"", + "p_code":"150", "code":"154" }, { - "desc":"No.Snapshots are stored on the physical disks that provide storage resources for EVS disks. Therefore, snapshots do not use the EVS disk space.", - "product_code":"evs", - "title":"Do Snapshots Take Space on the Disk?", - "uri":"evs_faq_0064.html", - "doc_type":"usermanual", - "p_code":"147", + "desc":"Possible causes are as follows:Snapshot data can only be rolled back when the status of the snapshot's source disk is Available or Rollback failed. If the snapshot's sour", + "product_code":"", + "title":"Why Can't I Roll Back My Disk Data from a Snapshot?", + "uri":"evs_faq_0058.html", + "doc_type":"", + "p_code":"150", "code":"155" }, { - "desc":"Yes. You can roll back a snapshot to the source disk multiple times as needed.", - "product_code":"evs", - "title":"Can I Perform Multiple Rollback Operations for a Snapshot?", - "uri":"evs_faq_0088.html", - "doc_type":"usermanual", - "p_code":"147", + "desc":"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.If you have for", + "product_code":"", + "title":"Can I Roll Back Data from a Snapshot After Reinstalling the OS or Formatting the Disk?", + "uri":"evs_faq_0062.html", + "doc_type":"", + "p_code":"150", "code":"156" }, { - "desc":"No. Snapshots cannot be replicated to other regions or accounts.", - "product_code":"evs", - "title":"Can I Replicate Snapshots to Other Regions or Accounts?", - "uri":"evs_faq_0089.html", - "doc_type":"usermanual", - "p_code":"147", + "desc":"The first snapshot is a full snapshot, which backs up all data (data blocks) on the EVS disk at the time of the snapshot. Subsequent snapshots are incremental snapshots, ", + "product_code":"", + "title":"How Is the Snapshot Size Calculated?", + "uri":"evs_faq_0063.html", + "doc_type":"", + "p_code":"150", "code":"157" }, { - "desc":"Possible causes are:You have manually deleted the snapshot.You have deleted the disk based on which the snapshot was created. If a disk is deleted, all the snapshots crea", - "product_code":"evs", - "title":"Why Can't I Find My Snapshot?", - "uri":"evs_faq_0102.html", - "doc_type":"usermanual", - "p_code":"147", + "desc":"No.Snapshots are stored on the physical disks that provide storage resources for EVS disks. Therefore, snapshots do not use the EVS disk space.", + "product_code":"", + "title":"Do Snapshots Take Space on the Disk?", + "uri":"evs_faq_0064.html", + "doc_type":"", + "p_code":"150", "code":"158" }, { - "desc":"The following two scenarios are supported:You can first use a snapshot to create a disk and then use the snapshot to roll back data of its source disk.You can first use a", - "product_code":"evs", - "title":"Can I Use a Snapshot to Create a Disk and Roll Back Disk Data at Almost the Same Time?", - "uri":"evs_faq_281112.html", - "doc_type":"usermanual", - "p_code":"147", + "desc":"Yes. You can use a snapshot to roll back data to the source disk multiple times as needed.", + "product_code":"", + "title":"Can I Perform Multiple Rollback Operations for a Snapshot?", + "uri":"evs_faq_0088.html", + "doc_type":"", + "p_code":"150", "code":"159" }, { - "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":"Performance", - "uri":"evs_01_0080.html", - "doc_type":"usermanual", - "p_code":"89", + "desc":"No. Snapshots cannot be replicated to other regions or accounts.", + "product_code":"", + "title":"Can I Replicate Snapshots to Other Regions or Accounts?", + "uri":"evs_faq_0089.html", + "doc_type":"", + "p_code":"150", "code":"160" }, { - "desc":"In the disk performance test, if the start sector number is not 4-KiB aligned, the disk performance will be greatly affected. Ensure that the start sector number is 4-KiB", - "product_code":"evs", - "title":"How Can I Test My Disk Performance?", - "uri":"evs_faq_0019.html", - "doc_type":"usermanual", - "p_code":"160", + "desc":"Possible causes are:You have manually deleted the snapshot.You have deleted the snapshot's source disk. Then, all the snapshots created for this disk will be automaticall", + "product_code":"", + "title":"Why Can't I Find My Snapshot?", + "uri":"evs_faq_0102.html", + "doc_type":"", + "p_code":"150", "code":"161" }, { - "desc":"You have followed the test performance method, but the test results do not meet expectations.During a disk performance test, the disk and stress test conditions play an i", - "product_code":"evs", - "title":"Why Does My Disk Performance Test Using Fio Have Incorrect Results?", - "uri":"evs_faq_0080.html", - "doc_type":"usermanual", - "p_code":"160", + "desc":"The following two scenarios are supported:You can first use a snapshot to create a disk and then use the snapshot to roll back data of its source disk.You can first use a", + "product_code":"", + "title":"Can I Use a Snapshot to Create a Disk and Roll Back Disk Data at Almost the Same Time?", + "uri":"evs_faq_281112.html", + "doc_type":"", + "p_code":"150", "code":"162" }, { - "desc":"SymptomIf you are aware of a service slowdown, depending on if you are examining a Windows or Linux server, you can take the following actions:Windows: Open Task Manager ", - "product_code":"evs", - "title":"How Can I Handle a Slowdown in Disk Read/Write Speed or Increased I/Os?", - "uri":"evs_faq_0081.html", - "doc_type":"usermanual", - "p_code":"160", + "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":"", + "title":"Performance", + "uri":"evs_01_0080.html", + "doc_type":"", + "p_code":"91", "code":"163" }, { - "desc":"SymptomA 500 GiB ultra-high I/O disk had an I/O usage of 99.94%, but it only had 12,000 IOPS.Description100% disk I/O usage does not mean that the disk IOPS reaches the m", - "product_code":"evs", - "title":"Why My Disk's Read IOPS Can't Reach the Theoretical Maximum IOPS When the Disk I/O Usage Is Almost 100%?", - "uri":"evs_faq_280905.html", - "doc_type":"usermanual", - "p_code":"160", + "desc":"In the disk performance test, if the start sector number is not 4-KiB aligned, the disk performance will be greatly affected. Ensure that the start sector number is 4-KiB", + "product_code":"", + "title":"How Do I Test My Disk Performance?", + "uri":"evs_faq_0019.html", + "doc_type":"", + "p_code":"163", "code":"164" }, { - "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":"Sharing", - "uri":"evs_01_0084.html", - "doc_type":"usermanual", - "p_code":"89", + "desc":"You have followed the test performance method, but the test results do not meet expectations.During a disk performance test, the disk and stress test conditions play an i", + "product_code":"", + "title":"Why Does My Disk Performance Test Using Fio Have Incorrect Results?", + "uri":"evs_faq_0080.html", + "doc_type":"", + "p_code":"163", "code":"165" }, { - "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":"165", + "desc":"SymptomIf you are aware of a service slowdown, depending on if you are examining a Windows or Linux server, you can take the following actions:Windows: Open Task Manager ", + "product_code":"", + "title":"How Can I Handle a Slowdown in Disk Read/Write Speed or Increased I/Os?", + "uri":"evs_faq_0081.html", + "doc_type":"", + "p_code":"163", "code":"166" }, { - "desc":"A shared disk can be attached to up to 16 servers.", - "product_code":"evs", - "title":"How Many Servers Can I Attach a Shared Disk to?", - "uri":"evs_faq_0037.html", - "doc_type":"usermanual", - "p_code":"165", + "desc":"SymptomA 500 GiB ultra-high I/O disk had an I/O usage of 99.94%, but it only had 12,000 IOPS.Description100% disk I/O usage does not mean that the disk IOPS reaches the m", + "product_code":"", + "title":"Why My Disk's Read IOPS Can't Reach the Theoretical Maximum IOPS When the Disk I/O Usage Is Almost 100%?", + "uri":"evs_faq_280905.html", + "doc_type":"", + "p_code":"163", "code":"167" }, { - "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.For details, see Attaching a ", - "product_code":"evs", - "title":"How Can I Attach a Shared Disk to Multiple Servers?", - "uri":"evs_faq_0038.html", - "doc_type":"usermanual", - "p_code":"165", + "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":"", + "title":"Sharing", + "uri":"evs_01_0084.html", + "doc_type":"", + "p_code":"91", "code":"168" }, { - "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":"165", + "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":"", + "title":"Do I Have to Deploy a Cluster to Use Shared Disks?", + "uri":"evs_faq_0039.html", + "doc_type":"", + "p_code":"168", "code":"169" }, { - "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":"165", + "desc":"A shared disk can be attached to up to 16 servers.", + "product_code":"", + "title":"How Many Servers Can I Attach a Shared Disk to?", + "uri":"evs_faq_0037.html", + "doc_type":"", + "p_code":"168", "code":"170" }, { - "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":"Backup", - "uri":"evs_faq_0098.html", - "doc_type":"usermanual", - "p_code":"89", + "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.For details, see Attaching a ", + "product_code":"", + "title":"How Can I Attach a Shared Disk to Multiple Servers?", + "uri":"evs_faq_0038.html", + "doc_type":"", + "p_code":"168", "code":"171" }, { - "desc":"No. You can back up disks when the server is in use. When a server is running, data is written into disks on the server, and some newly generated data is cached in the se", - "product_code":"evs", - "title":"Do I Need to Stop the Server Before Performing a Disk Backup?", - "uri":"evs_faq_0097.html", - "doc_type":"usermanual", - "p_code":"171", + "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":"", + "title":"Can a Shared Disk Be Attached to Servers That Belong to Different Accounts?", + "uri":"evs_faq_0068.html", + "doc_type":"", + "p_code":"168", "code":"172" }, { - "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":"Appendix", - "uri":"evs_01_0039.html", - "doc_type":"usermanual", - "p_code":"", + "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":"", + "title":"Can I Attach a Shared Disk to Servers Running Different OSs?", + "uri":"evs_faq_0083.html", + "doc_type":"", + "p_code":"168", "code":"173" }, { - "desc":"An EVS disk has several statuses. Table 1 lists EVS disk statuses, the meaning of each status, and the operations a disk in each status allows.Disk status detailsEVS Disk", - "product_code":"evs", - "title":"EVS Disk Status", - "uri":"evs_01_0040.html", - "doc_type":"usermanual", - "p_code":"173", + "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":"", + "title":"Backup", + "uri":"evs_faq_0098.html", + "doc_type":"", + "p_code":"91", "code":"174" }, { - "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", - "product_code":"evs", - "title":"EVS Snapshot Status", - "uri":"evs_01_0041.html", - "doc_type":"usermanual", - "p_code":"173", + "desc":"No. You can back up disks when the server is in use. When a server is running, data is written into disks on the server, and some newly generated data is cached in the se", + "product_code":"", + "title":"Do I Need to Stop the Server Before Performing a Disk Backup?", + "uri":"evs_faq_0097.html", + "doc_type":"", + "p_code":"174", "code":"175" }, { "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":"Change History", - "uri":"evs_01_0114.html", - "doc_type":"usermanual", + "product_code":"", + "title":"Appendix", + "uri":"evs_01_0039.html", + "doc_type":"", "p_code":"", "code":"176" }, + { + "desc":"An EVS disk has several statuses. Table 1 lists EVS disk statuses, the meaning of each status, and the operations a disk in each status allows.Disk status detailsEVS Disk", + "product_code":"", + "title":"EVS Disk Status", + "uri":"evs_01_0040.html", + "doc_type":"", + "p_code":"176", + "code":"177" + }, + { + "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":"", + "title":"Change History", + "uri":"evs_01_0114.html", + "doc_type":"", + "p_code":"", + "code":"178" + }, { "desc":"For details about the terms involved in this document, see Glossary.", - "product_code":"evs", + "product_code":"", "title":"Glossary", "uri":"evs_01_0115.html", - "doc_type":"usermanual", + "doc_type":"", "p_code":"", - "code":"177" + "code":"179" } ] \ No newline at end of file diff --git a/docs/evs/umn/en-us_image_0000001439650122.png b/docs/evs/umn/en-us_image_0000001439650122.png new file mode 100644 index 000000000..855f77568 Binary files /dev/null and b/docs/evs/umn/en-us_image_0000001439650122.png differ diff --git a/docs/evs/umn/en-us_image_0000001896813650.png b/docs/evs/umn/en-us_image_0000001896813650.png new file mode 100644 index 000000000..e23dd1aea Binary files /dev/null and b/docs/evs/umn/en-us_image_0000001896813650.png differ diff --git a/docs/evs/umn/en-us_image_0000001911643677.png b/docs/evs/umn/en-us_image_0000001911643677.png deleted file mode 100644 index 90a035319..000000000 Binary files a/docs/evs/umn/en-us_image_0000001911643677.png and /dev/null differ diff --git a/docs/evs/umn/en-us_image_0000001571754664.png b/docs/evs/umn/en-us_image_0000001925046644.png similarity index 100% rename from docs/evs/umn/en-us_image_0000001571754664.png rename to docs/evs/umn/en-us_image_0000001925046644.png diff --git a/docs/evs/umn/en-us_image_0000001933286285.jpg b/docs/evs/umn/en-us_image_0000001933286285.jpg new file mode 100644 index 000000000..ad5684271 Binary files /dev/null and b/docs/evs/umn/en-us_image_0000001933286285.jpg differ diff --git a/docs/evs/umn/en-us_image_0133519241.png b/docs/evs/umn/en-us_image_0000001949357721.png similarity index 100% rename from docs/evs/umn/en-us_image_0133519241.png rename to docs/evs/umn/en-us_image_0000001949357721.png diff --git a/docs/evs/umn/en-us_image_0000001571900348.png b/docs/evs/umn/en-us_image_0000001952166289.png similarity index 100% rename from docs/evs/umn/en-us_image_0000001571900348.png rename to docs/evs/umn/en-us_image_0000001952166289.png diff --git a/docs/evs/umn/en-us_image_0000001959822180.jpg b/docs/evs/umn/en-us_image_0000001959822180.jpg new file mode 100644 index 000000000..ad5684271 Binary files /dev/null and b/docs/evs/umn/en-us_image_0000001959822180.jpg differ diff --git a/docs/evs/umn/en-us_image_0000001959822188.jpg b/docs/evs/umn/en-us_image_0000001959822188.jpg new file mode 100644 index 000000000..ad5684271 Binary files /dev/null and b/docs/evs/umn/en-us_image_0000001959822188.jpg differ diff --git a/docs/evs/umn/en-us_image_0000001959981972.jpg b/docs/evs/umn/en-us_image_0000001959981972.jpg new file mode 100644 index 000000000..ad5684271 Binary files /dev/null and b/docs/evs/umn/en-us_image_0000001959981972.jpg differ diff --git a/docs/evs/umn/en-us_image_0000001487413362.png b/docs/evs/umn/en-us_image_0000001959981980.png similarity index 100% rename from docs/evs/umn/en-us_image_0000001487413362.png rename to docs/evs/umn/en-us_image_0000001959981980.png diff --git a/docs/evs/umn/en-us_image_0210779229.png b/docs/evs/umn/en-us_image_0000001959981992.png similarity index 100% rename from docs/evs/umn/en-us_image_0210779229.png rename to docs/evs/umn/en-us_image_0000001959981992.png diff --git a/docs/evs/umn/en-us_image_0163801956.png b/docs/evs/umn/en-us_image_0000001962012184.png similarity index 100% rename from docs/evs/umn/en-us_image_0163801956.png rename to docs/evs/umn/en-us_image_0000001962012184.png diff --git a/docs/evs/umn/en-us_image_0152754019.png b/docs/evs/umn/en-us_image_0000001962012192.png similarity index 100% rename from docs/evs/umn/en-us_image_0152754019.png rename to docs/evs/umn/en-us_image_0000001962012192.png diff --git a/docs/evs/umn/en-us_image_0197136031.png b/docs/evs/umn/en-us_image_0000001962240620.png similarity index 100% rename from docs/evs/umn/en-us_image_0197136031.png rename to docs/evs/umn/en-us_image_0000001962240620.png diff --git a/docs/evs/umn/en-us_image_0000001991047461.png b/docs/evs/umn/en-us_image_0000001991047461.png new file mode 100644 index 000000000..25d1299bc Binary files /dev/null and b/docs/evs/umn/en-us_image_0000001991047461.png differ diff --git a/docs/evs/umn/en-us_image_0000001996462329.png b/docs/evs/umn/en-us_image_0000001996462329.png new file mode 100644 index 000000000..1909444d2 Binary files /dev/null and b/docs/evs/umn/en-us_image_0000001996462329.png differ diff --git a/docs/evs/umn/en-us_image_0000001998573081.png b/docs/evs/umn/en-us_image_0000001998573081.png new file mode 100644 index 000000000..f4e325b3c Binary files /dev/null and b/docs/evs/umn/en-us_image_0000001998573081.png differ diff --git a/docs/evs/umn/en-us_image_0163801385.png b/docs/evs/umn/en-us_image_0000001998573089.png similarity index 100% rename from docs/evs/umn/en-us_image_0163801385.png rename to docs/evs/umn/en-us_image_0000001998573089.png diff --git a/docs/evs/umn/en-us_image_0152754508.png b/docs/evs/umn/en-us_image_0000001998573101.png similarity index 100% rename from docs/evs/umn/en-us_image_0152754508.png rename to docs/evs/umn/en-us_image_0000001998573101.png diff --git a/docs/evs/umn/en-us_image_0000001487224722.png b/docs/evs/umn/en-us_image_0000002015229526.png similarity index 100% rename from docs/evs/umn/en-us_image_0000001487224722.png rename to docs/evs/umn/en-us_image_0000002015229526.png diff --git a/docs/evs/umn/en-us_image_0000002032822906.png b/docs/evs/umn/en-us_image_0000002032822906.png new file mode 100644 index 000000000..1909444d2 Binary files /dev/null and b/docs/evs/umn/en-us_image_0000002032822906.png differ diff --git a/docs/evs/umn/en-us_image_0152639916.png b/docs/evs/umn/en-us_image_0000002032823162.png similarity index 100% rename from docs/evs/umn/en-us_image_0152639916.png rename to docs/evs/umn/en-us_image_0000002032823162.png diff --git a/docs/evs/umn/en-us_image_0218677657.png b/docs/evs/umn/en-us_image_0000002032981318.png similarity index 100% rename from docs/evs/umn/en-us_image_0218677657.png rename to docs/evs/umn/en-us_image_0000002032981318.png diff --git a/docs/evs/umn/en-us_image_0000002032981542.png b/docs/evs/umn/en-us_image_0000002032981542.png new file mode 100644 index 000000000..1909444d2 Binary files /dev/null and b/docs/evs/umn/en-us_image_0000002032981542.png differ diff --git a/docs/evs/umn/en-us_image_0000002049065922.png b/docs/evs/umn/en-us_image_0000002049065922.png new file mode 100644 index 000000000..25d1299bc Binary files /dev/null and b/docs/evs/umn/en-us_image_0000002049065922.png differ diff --git a/docs/evs/umn/en-us_image_0000002049223182.png b/docs/evs/umn/en-us_image_0000002049223182.png new file mode 100644 index 000000000..99e9a17be Binary files /dev/null and b/docs/evs/umn/en-us_image_0000002049223182.png differ diff --git a/docs/evs/umn/en-us_image_0129867556.png b/docs/evs/umn/en-us_image_0000002051547313.png similarity index 100% rename from docs/evs/umn/en-us_image_0129867556.png rename to docs/evs/umn/en-us_image_0000002051547313.png diff --git a/docs/evs/umn/en-us_image_0000002052020269.png b/docs/evs/umn/en-us_image_0000002052020269.png new file mode 100644 index 000000000..7fb145297 Binary files /dev/null and b/docs/evs/umn/en-us_image_0000002052020269.png differ diff --git a/docs/evs/umn/en-us_image_0000002052179349.png b/docs/evs/umn/en-us_image_0000002052179349.png new file mode 100644 index 000000000..6a597d26b Binary files /dev/null and b/docs/evs/umn/en-us_image_0000002052179349.png differ diff --git a/docs/evs/umn/en-us_image_0000002068902269.png b/docs/evs/umn/en-us_image_0000002068902269.png new file mode 100644 index 000000000..1909444d2 Binary files /dev/null and b/docs/evs/umn/en-us_image_0000002068902269.png differ diff --git a/docs/evs/umn/en-us_image_0000002069061197.png b/docs/evs/umn/en-us_image_0000002069061197.png new file mode 100644 index 000000000..1909444d2 Binary files /dev/null and b/docs/evs/umn/en-us_image_0000002069061197.png differ diff --git a/docs/evs/umn/en-us_image_0162733605.png b/docs/evs/umn/en-us_image_0000002077234357.png similarity index 100% rename from docs/evs/umn/en-us_image_0162733605.png rename to docs/evs/umn/en-us_image_0000002077234357.png diff --git a/docs/evs/umn/en-us_image_0137059230.png b/docs/evs/umn/en-us_image_0137059230.png new file mode 100644 index 000000000..75fb9feff Binary files /dev/null and b/docs/evs/umn/en-us_image_0137059230.png differ diff --git a/docs/evs/umn/en-us_image_0137060651.png b/docs/evs/umn/en-us_image_0137060651.png new file mode 100644 index 000000000..008af1ee8 Binary files /dev/null and b/docs/evs/umn/en-us_image_0137060651.png differ diff --git a/docs/evs/umn/en-us_image_0137061042.png b/docs/evs/umn/en-us_image_0137061042.png new file mode 100644 index 000000000..111964960 Binary files /dev/null and b/docs/evs/umn/en-us_image_0137061042.png differ diff --git a/docs/evs/umn/en-us_image_0137062325.png b/docs/evs/umn/en-us_image_0137062325.png new file mode 100644 index 000000000..7aba8a995 Binary files /dev/null and b/docs/evs/umn/en-us_image_0137062325.png differ diff --git a/docs/evs/umn/en-us_image_0137062384.png b/docs/evs/umn/en-us_image_0137062384.png new file mode 100644 index 000000000..59089b4f7 Binary files /dev/null and b/docs/evs/umn/en-us_image_0137062384.png differ diff --git a/docs/evs/umn/en-us_image_0137062392.png b/docs/evs/umn/en-us_image_0137062392.png new file mode 100644 index 000000000..c119c918c Binary files /dev/null and b/docs/evs/umn/en-us_image_0137062392.png differ diff --git a/docs/evs/umn/en-us_image_0232543567.gif b/docs/evs/umn/en-us_image_0232543567.gif deleted file mode 100644 index bdbbaec02..000000000 Binary files a/docs/evs/umn/en-us_image_0232543567.gif and /dev/null differ diff --git a/docs/evs/umn/en-us_image_0238263232.png b/docs/evs/umn/en-us_image_0238263232.png deleted file mode 100644 index ad1a41d4b..000000000 Binary files a/docs/evs/umn/en-us_image_0238263232.png and /dev/null differ diff --git a/docs/evs/umn/en-us_image_0269609232.png b/docs/evs/umn/en-us_image_0269609232.png index e3201cb3a..beb416824 100644 Binary files a/docs/evs/umn/en-us_image_0269609232.png and b/docs/evs/umn/en-us_image_0269609232.png differ diff --git a/docs/evs/umn/en-us_topic_0014580741.html b/docs/evs/umn/en-us_topic_0014580741.html index 8bf7a7ba4..eb4794b37 100644 --- a/docs/evs/umn/en-us_topic_0014580741.html +++ b/docs/evs/umn/en-us_topic_0014580741.html @@ -1,116 +1,124 @@

What Is EVS?

-

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

-

EVS disks are similar to hard disks in PCs. They must be attached to servers for use and cannot be used alone. You can initialize EVS disks, create file systems on them, and store data persistently on them.

-

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

-
Figure 1 EVS architecture
+

Overview

Elastic Volume Service (EVS) offers scalable block storage for cloud servers. EVS disks provide high reliability, high performance, and come with a variety of disk types. They 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).

+

Just like the physical disks in local PC need to be installed before they can be used, EVS disks need to be attached to servers before they can be used. They cannot be used alone. You also need to partition and create file systems on them before they can be used for persistent data storage.

+

In this document, EVS disks are sometimes just referred to as "disks".

+
Figure 1 EVS architecture
-

EVS Advantages

EVS has the following advantages:

+

EVS Advantages

EVS has the following advantages.

-
Table 1 EVS advantages

Advantage

+
- - - - - - - - - - - - - - - + - - - + + + +
Table 1 EVS advantages

Advantage

Description

+

Description

Related Knowledge

+

Reference

Various disk types

+

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

+

EVS provides a variety of disk types for you to choose from. They can be used as data disks or system disks for cloud servers. You can select whichever disk type that has the specifications best suited to your budget and service requirements.

Disk Types and Performance

+

Disk Types and Performance

Elastic scalability

+

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.

+

The EVS disk capacity ranges from 10 GiB to 32 TiB. You can start with 10 GiB, and if, later on, that no longer meets your needs, you can expand the disk capacity to up to 32 TiB in increments of 1 GiB, without interrupting your applications.

Expansion Overview

+

Expansion Overview

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.

+

In addition to the disk capacity limit, there is an EVS capacity quota. The additional space you add cannot exceed the remaining quota. However, if this happens, you can apply for a higher quota.

Manage EVS Quotas

+

Managing EVS Quotas

High security and reliability

+

High security and reliability

Both system disks and data disks support data encryption to ensure data security.

+

Both system disks and data disks support data encryption to ensure data security.

EVS Encryption

+

Managing Encrypted EVS Disks

Data protection functions, such as backups and snapshots, safeguard the disk data, preventing incorrect data caused by application exceptions or attacks.

+

High security and reliability

EVS Backup

-

EVS Snapshot

+

Data protection functions, such as backups, safeguard the disk data. If your data is ever damaged by a software exception or online attack, you can restore your data from backups.

+

Managing EVS Disk Backups

Real-time monitoring

+

High security and reliability

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

+

Data protection functions, such as snapshots, safeguard the disk data. If your data is ever damaged by a software exception or online attack, you can restore your data from snapshots.

Viewing EVS Monitoring Data

+

Managing EVS Snapshots

+

Real-time monitoring

+

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

+

Viewing Basic EVS Monitoring Data

-

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.

+

Differences Among EVS, SFS, and OBS

There are three types of storage available for you to choose from: EVS, Scalable File Service (SFS), and Object Storage Service (OBS). Their differences are described in the following table.

-
Table 2 Differences among EVS, SFS, and OBS

Service

+
- - - - - - - - - - - - - - -
Table 2 Differences among EVS, SFS, and OBS

Service

Overall Introduction

+

Overall Introduction

Typical Application Scenarios

+

Typical Application Scenarios

Storage Capacity

+

Storage Capacity

EVS

+

EVS

EVS provides scalable block storage that features high reliability, high performance, and a variety of 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
+
  • 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 GiB and can be expanded as required in 1 GiB increments to up to 32 TiB.

+

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

SFS

+

SFS

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.

+

SFS provides completely hosted shared file storage for cloud servers. Compatible with the Network File System (NFS) protocol, SFS is expandable to pebibyte 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
+
  • 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 a maximum of 2 PiB.

+

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

OBS

+

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.

+

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
  • Cloud-native applications
+
  • Enterprise backup and archive
  • Big data analysis
  • Enterprise cloud box
  • Static website hosting
  • Cloud-native applications

OBS has 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.

-

Methods of Access

The public cloud system provides a web-based management console and HTTPS-based APIs for you to access the EVS service.

-
  • APIs

    Use APIs if you need to integrate EVS into a third-party system for secondary development. For details, see Elastic Volume Service API Reference.

    -
  • Management console

    Use the management console if you do not need to integrate EVS with a third-party system. Log in to the management console and choose Elastic Volume Service from the service list.

    +

    Access Methods

    The public cloud system provides a web-based management console and HTTPS-based APIs that you can use to access the EVS service.

    +
    • APIs

      Use APIs if you need to integrate EVS into a third-party system for secondary development. For details, see Elastic Volume Service API Reference.

      +
    • Management console

      Use the management console if you do not need to integrate EVS with a third-party system. Log in to the management console and choose Elastic Volume Service from the service list.

    -

    User Permissions

    Users with resource management permissions can control the operations performed on cloud service resources. For EVS, a user with the Server Administrator permission can perform operations on EVS resources, including creating disks, deleting disks, and creating snapshots.

    -

    For details about user permissions, see Permissions.

    +

    User Permissions

    Users with resource management permissions can control the operations performed on cloud service resources. For EVS, a user with the Server Administrator permission can perform operations on EVS resources, including creating disks, deleting disks, and creating snapshots.

    +

    For details about user permissions, see Permissions.

    -

    Project

    A project is used to group and isolate OpenStack resources, including compute, storage, and network resources. A project can be a department or a project team. You can access IAM with a security administrator to create projects in a region and perform isolated management of resources. For details about projects, see Managing Projects.

    +

    Project

    A project is used to group and isolate OpenStack resources, including compute, storage, and network resources. A project can be a department or a project team. You can access IAM with a security administrator to create projects in a region and perform isolated management of resources. For details about projects, see Managing Projects.

    diff --git a/docs/evs/umn/en-us_topic_0014580744.html b/docs/evs/umn/en-us_topic_0014580744.html index 5f252e871..b64bf4347 100644 --- a/docs/evs/umn/en-us_topic_0014580744.html +++ b/docs/evs/umn/en-us_topic_0014580744.html @@ -1,209 +1,209 @@

    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: This type of EVS disks delivers a maximum IOPS of 1,000. 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 IOPS of 3,000 and a minimum read/write latency of 6 ms. 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 IOPS of 20,000 and a minimum read/write latency of 1 ms. 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.
    • Extreme SSD: This type of EVS disks delivers a maximum IOPS of 128,000. They are designed for workloads demanding super-high bandwidth and super-low latency, such as Oracle databases and AI applications.
    • General Purpose SSD: This type of EVS disks delivers a maximum IOPS of 20,000. They are suitable for workloads requiring high throughput and low latency, such as enterprise OA, development and testing, web server logging, containers, and high-performance system disks.
    -
    • 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 disks are classified based on the disk I/O performance. EVS disks differ in performance and price. You can choose whichever disk type that is the best fit for your applications.

    +

    Application Scenarios

    • Common I/O: This type of EVS disks delivers a maximum IOPS of 1,000. 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 IOPS of 3,000 and a minimum read/write latency of 6 ms. 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 IOPS of 20,000 and a minimum read/write latency of 1 ms. 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.
    • Extreme SSD: This type of EVS disks delivers a maximum IOPS of 128,000. They are designed for workloads demanding super-high bandwidth and super-low latency, such as Oracle databases and AI applications.
    • General Purpose SSD: This type of EVS disks delivers a maximum IOPS of 20,000. They are suitable for workloads requiring high throughput and low latency, such as enterprise OA, development and testing, web server logging, containers, and high-performance system disks.
    +
    • 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 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
    +

    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 EVS performance data

    Parameter

    +
    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    Table 1 EVS performance data

    Parameter

    Common I/O

    +

    Common I/O

    High I/O

    +

    High I/O

    General Purpose SSD

    +

    General Purpose SSD

    Ultra-high I/O

    +

    Ultra-high I/O

    Extreme SSD

    +

    Extreme SSD

    IOPS per GiB/EVS disk

    +

    IOPS per GiB/EVS disk

    1

    +

    1

    2

    +

    2

    12

    +

    12

    50

    +

    50

    50

    +

    50

    Min. IOPS/EVS disk

    +

    Min. IOPS/EVS disk

    100

    +

    100

    100

    +

    100

    1,800

    +

    1,800

    100

    +

    100

    1,800

    +

    1,800

    Max. IOPS/EVS disk

    +

    Max. IOPS/EVS disk

    1,000

    +

    1,000

    3,000

    +

    3,000

    20,000

    +

    20,000

    20,000

    +

    20,000

    128,000

    +

    128,000

    Disk IOPS

    +

    Disk IOPS

    Min. (1,000, 100 + 1 x Capacity)

    +

    Min. (1,000, 100 + 1 x Capacity)

    Min. (3,000, 100 + 2 x Capacity)

    +

    Min. (3,000, 100 + 2 x Capacity)

    Min. (20,000, 1,800 + 12 x Capacity)

    +

    Min. (20,000, 1,800 + 12 x Capacity)

    Min. (20,000, 100 + 50 x Capacity)

    +

    Min. (20,000, 100 + 50 x Capacity)

    Min. (128,000, 1,800 + 50 x Capacity)

    +

    Min. (128,000, 1,800 + 50 x Capacity)

    IOPS burst limit/EVS disk

    +

    IOPS burst limit/EVS disk

    1,000

    +

    1,000

    3,000

    +

    3,000

    8,000

    +

    8,000

    10,000

    +

    10,000

    64,000

    +

    64,000

    Max. throughput

    +

    Max. throughput

    90 MiB/s

    +

    90 MiB/s

    150 MiB/s

    +

    150 MiB/s

    250 MiB/s

    +

    250 MiB/s

    350 MiB/s

    +

    350 MiB/s

    1,000 MiB/s

    +

    1,000 MiB/s

    Disk throughput (MiB/s)

    +

    Disk throughput (MiB/s)

    50

    +

    50

    Min. (150, 100 + 0.15 × Capacity)

    +

    Min. (150, 100 + 0.15 × Capacity)

    Min. (250, 100 + 0.5 × Capacity)

    +

    Min. (250, 100 + 0.5 × Capacity)

    Min. (350, 120 + 0.5 × Capacity)

    +

    Min. (350, 120 + 0.5 × Capacity)

    Min. (1,000, 120 + 0.5 × Capacity)

    +

    Min. (1,000, 120 + 0.5 × Capacity)

    I/O read/write latency (single-queue)

    +

    I/O read/write latency (single-queue)

    10 ms to 15 ms

    +

    10 ms to 15 ms

    6 ms to 10 ms

    +

    6 ms to 10 ms

    1 ms

    +

    1 ms

    1 ms to 3 ms

    +

    1 ms to 3 ms

    Sub-millisecond

    +

    Sub-millisecond

    -

    EVS disk performance is closely related with the data block size:

    -
    • If data blocks are of the same size, a disk can achieve either the maximum IOPS or maximum throughput depending on which one is reached first.
    • If data blocks are of different sizes, the maximum performance metric that a disk can achieve varies:
      • For small data blocks, such as 4 KiB or 8 KiB, a disk can reach the maximum IOPS.
      • For data blocks greater than or equal to 16 KiB, a disk can reach the maximum throughput.
      +

      EVS disk performance is closely related with the data block size:

      +
      • If data blocks are all the same size, a disk can achieve either the maximum IOPS or maximum throughput depending on which one is reached first.
      • If data blocks are of different sizes, the maximum performance metric that a disk can achieve varies:
        • For small data blocks, such as 4 KiB or 8 KiB, a disk can reach the maximum IOPS.
        • For data blocks of a large size, 16 KiB or greater, a disk can reach the maximum throughput.
      -

      The following uses an ultra-high I/O disk as an example. According to the formula, when the size of an ultra-high I/O disk is greater than or equal to 460 GiB, the disk theoretically can reach either the maximum IOPS 20,000 or the maximum throughput 350 MiB/s. However, this is not the case in practice. The maximum IOPS and maximum throughput that a disk can reach also vary with the data block size. For details, see Table 2.

      +

      Table 2 uses an ultra-high I/O disk as an example. In theory, when the size of an ultra-high I/O disk is at least 460 GiB, the disk theoretically can reach either the maximum IOPS 20,000 or the maximum throughput 350 MiB/s. However, this is not the case in practice. The maximum IOPS and maximum throughput that a disk can reach also vary with the data block size.

      -
      Table 2 Maximum performance of an ultra-high I/O EVS disk

      Data Block Size

      +
      - - - - - - - - - - - - - -
      Table 2 Maximum performance of an ultra-high I/O EVS disk

      Data Block Size (KiB)

      Max. IOPS

      +

      Max. IOPS

      Max. Throughput (MiB/s)

      +

      Max. Throughput (MiB/s)

      4 KiB

      +

      4

      About 20,000

      +

      About 20,000

      About 78

      +

      About 78

      8 KiB

      +

      8

      About 20,000

      +

      About 20,000

      About 156

      +

      About 156

      16 KiB

      +

      16

      About 20,000

      +

      About 20,000

      About 312

      +

      About 312

      32 KiB

      +

      32

      About 11,200

      +

      About 11,200

      About 350

      +

      About 350

      -

      Disk IOPS Calculation Formula

      Disk IOPS = Min. (Maximum IOPS, Minimum IOPS + IOPS per GiB x Capacity)

      -
      The following example uses an ultra-high I/O EVS disk with a maximum IOPS of 20,000.
      • If the disk capacity is 100 GiB, the disk IOPS is calculated as follows: Disk IOPS = Min. (20,000, 100 + 50 × 100)

        -

        The disk IOPS is 5,100, the smaller value between 20,000 and 5,100.

        -
      • If the disk capacity is 1,000 GiB, the disk IOPS is calculated as follows: Disk IOPS = Min. (20,000, 100 + 50 × 1,000)

        -

        The disk IOPS is 20,000, the smaller value between 20,000 and 50,100.

        +

        Disk IOPS Calculation Formula

        Disk IOPS = Min. (Maximum IOPS, Minimum IOPS + IOPS per GiB x Capacity)

        +
        Take an ultra-high I/O EVS disk with a maximum IOPS of 20,000 for example.
        • If the disk capacity is 100 GiB, the disk IOPS is calculated as follows: Disk IOPS = Min. (20,000, 100 + 50 × 100)

          +

          The disk IOPS is 5,100, the smaller of the two values (20,000 and 5,100).

          +
        • If the disk capacity is 1,000 GiB, the disk IOPS is calculated as follows: Disk IOPS = Min. (20,000, 100 + 50 × 1,000)

          +

          The disk IOPS is 20,000, the smaller of the two values (20,000 and 50,100).

        -

        Disk Burst Capability and Principles

        EVS disks have burst capability, which allows a small-capacity disk to surpass its maximum IOPS within a certain period of time. This IOPS applies to individual disks.

        -

        Disks with burst capability are well-suited for speeding up server startup. In most cases, system disks have small capacities. For example, the IOPS of a 50-GiB ultra-high I/O disk without burst capability can only reach up to 2,600, calculated as follows: IOPS = Min. (20,000, 100 + 50 x Capacity). If the disk has burst capability, its IOPS can burst up to 10,000.

        -
        The following example uses an ultra-high I/O EVS disk with the IOPS burst limit of 10,000.
        • If the disk capacity is 100 GiB, the disk has a maximum IOPS of 5,100, but it can burst to 10,000 IOPS in a certain duration.
        • If the disk capacity is 1,000 GiB, the disk has a maximum IOPS of 20,000. The disk maximum IOPS already exceeds its burst IOPS 10,000, and the disk does not use the burst capability.
        +

        Disk Burst Capability and Principles

        EVS disks have a burst capability. A small-capacity disk can surpass its official maximum IOPS for a short period of time. This IOPS applies to each disk individually.

        +

        Disks with burst capability are well-suited for speeding up server startup. In most cases, system disks are fairly small, so their basic IOPS is fairly low. For example, the IOPS of a 50-GiB ultra-high I/O disk without burst can only reach up to 2,600 IOPS (Min. (20,000, 100 + 50 x Capacity)). But with burst capability, its IOPS can burst up to 10,000.

        +
        The following example uses an ultra-high I/O EVS disk with the IOPS burst limit of 10,000.
        • If the disk capacity is 100 GiB, the disk has a maximum IOPS of 5,100, but it can burst to 10,000 IOPS in a certain duration.
        • If the disk capacity is 1,000 GiB, the disk has a maximum IOPS of 20,000. The disk maximum IOPS already exceeds its burst IOPS 10,000, and the disk does not use the burst capability.
        -

        The following describes the burst IOPS consumption and reservation.

        -

        A token bucket is used to handle burst I/O operations. The number of initial tokens in the bucket is calculated as follows:

        -

        Number of initial tokens = Burst duration x IOPS burst limit

        -
        In the following example, a 100-GiB ultra-high I/O EVS disk is used, and the fixed burst duration is 1800s. Therefore, the number of initial tokens is 18,000,000 (1,800 x 10,000).
        • Token production rate: This rate equals the disk maximum IOPS, which is 5,100 tokens/s.
        • Token consumption rate: This rate is calculated based on the I/O usage. Each I/O request consumes a token. The maximum consumption rate is 10,000 tokens/s, which is the larger value between the disk burst IOPS and maximum IOPS.
        +

        The following describes the burst IOPS consumption and reservation.

        +

        A token bucket is used to handle burst I/O operations. The number of initial tokens in the bucket is calculated as follows:

        +

        Number of initial tokens = Burst duration x IOPS burst limit

        +
        In the following example, a 100-GiB ultra-high I/O EVS disk is used, and the fixed burst duration is 1800s. Therefore, the number of initial tokens is 18,000,000 (1,800 x 10,000).
        • Token production rate: This rate equals the disk maximum IOPS, which is 5,100 tokens/s.
        • Token consumption rate: This rate is based on the I/O usage. Each I/O request consumes a token. The maximum consumption rate is 10,000 tokens/s, which is the larger value of the disk burst IOPS and the maximum IOPS.
        -

        Consumption principles

        -

        When the token consumption rate is greater than the production rate, the number of tokens decreases accordingly, and eventually the disk IOPS will be consistent with the token production rate (the maximum IOPS). In this example, the disk can burst for approximately 3,673 seconds [18,000,000/(10,000 - 5,100)].

        -

        Reservation principles

        -

        When the token consumption rate is smaller than the production rate, the number of tokens increases accordingly, enabling the disk to regain the burst capability. In this example, if the disk is suspended for approximately 3,529 seconds (18,000,000/5,100), the token bucket will be filled up with tokens.

        -

        As long as there are tokens in the token bucket, the disk has the burst capability.

        +

        Consumption principles

        +

        When tokens are consumed faster than they are produced, the number of tokens decreases accordingly, and eventually the disk IOPS will be consistent with the token production rate (the maximum IOPS). In this example, the disk can burst for approximately 3,673 seconds [18,000,000/(10,000 - 5,100)].

        +

        Reservation principles

        +

        When tokens are consumed more slowly than they are produced, the number of tokens increases accordingly, and the disk regains burst capability. In this example, if the disk is suspended for approximately 3,529 seconds (18,000,000/5,100), the token bucket will be filled up with tokens.

        +

        As long as there are tokens in the token bucket, the disk has the burst capability.

        -
        Figure 1 shows the token consumption and reservation principles. The blue bars indicate the disk IOPS usage, the green dashed line represents the maximum IOPS, the red dashed line indicates the IOPS burst limit, and the black curve indicates the changes of the number of tokens.
        • When the number of tokens is greater than zero, the disk IOPS can exceed 5,100 and has the capability to reach 10,000, the IOPS burst limit.
        • When the number of tokens is zero, the disk does not have the burst capability, and the maximum IOPS is 5,100.
        • When the disk IOPS is less than 5,100, the number of tokens starts to increase, and the disk can regain the burst capability.
        -
        Figure 1 Burst capability diagram
        +
        Figure 1 shows the token consumption and reservation principles. The blue bars indicate the disk IOPS usage, the green dashed line represents the maximum IOPS, the red dashed line indicates the IOPS burst limit, and the black curve indicates the changes of the number of tokens.
        • As long as there are tokens, the disk IOPS can exceed 5,100 and can burst to up to 10,000, the IOPS burst limit.
        • When there are no more tokens, the disk loses the burst capability, and the disk IOPS can reach up to 5,100.
        • Any time the disk IOPS is less than 5,100, the number of tokens starts to increase, and the disk regains the burst capability.
        +
        Figure 1 Burst capability diagram
        -

        Performance Test Method

        For details about how to test the EVS disk performance parameters, see How Can I Test My Disk Performance?.

        +

        Performance Testing

        For details about how to test the EVS disk performance, see How Do I Test My Disk Performance?.

        diff --git a/docs/evs/umn/en-us_topic_0017616396.html b/docs/evs/umn/en-us_topic_0017616396.html index 30e651e33..67e5446e1 100644 --- a/docs/evs/umn/en-us_topic_0017616396.html +++ b/docs/evs/umn/en-us_topic_0017616396.html @@ -1,103 +1,106 @@

        Extending Disk Partitions and File Systems (Windows Server 2008)

        -

        Scenarios

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

        -

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

        -

        If the disk capacity is expanded on a stopped server, the additional space of a Windows system disk or Windows data disk will be automatically added to the partition at the end of the disk upon the server startup. In this case, the additional space can be used directly.

        -
        This section uses Windows Server 2008 R2 Enterprise 64bit as the sample OS to describe the expansion methods:
        • For a system disk: -
        • For a data disk: +

          Scenarios

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

          +

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

          +

          If the disk capacity is expanded on a stopped server, the additional space of a Windows system disk or Windows data disk will be automatically added to the partition at the end of the disk upon the server startup. In this case, the additional space can be used directly.

          +
          This section uses Windows Server 2008 R2 Enterprise 64bit as the sample OS to describe the expansion methods:
          -

          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. Incorrect operations may lead to data loss or exceptions. So 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.

          +

          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.

          +

          Incorrect operations may lead to data loss or exceptions. So you are advised to back up the disk data using CBR or snapshots before expansion. For details about using CBR, see Managing EVS Disk Backups. For details about using snapshots, see Creating an EVS Snapshot.

          -

          Prerequisites

          • You have expanded the disk capacity and attached the disk to a server on the management console. For details, see Expanding Capacity for an In-use EVS Disk or Expanding Capacity for an Available EVS Disk.
          • 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.
            +

            Notes and Constraints

            • The additional space of a data disk cannot be added to the root partition. To extend the root partition, expand the system disk instead.
            • During an expansion, the additional space is added to the end of the disk. If the disk has multiple partitions, the additional space can only be allocated to the partition at the disk end.
            • If a disk uses MBR, the storage space in excess of 2 TiB cannot be used because the maximum capacity that MBR supports is 2 TiB. If your disk already uses MBR for partitioning and you require more than 2 TiB after the capacity expansion, do as follows:
              • (Recommended) Create a new EVS disk and use GPT.
              • Back up the disk data, perform the expansion, and then change the partition style from MBR to GPT. During this change, services will be interrupted and data on the disk will be erased.
            -

            System Disk: Add the Additional Space to the Original Volume

            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.

              -
              Figure 1 Disk Management (system disk)
              -

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

              +

              Prerequisites

              +
              +

              System Disk: Add the Additional Space to the Original Volume

              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.

                +
                Figure 1 Disk Management (system disk)
                +

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

                -

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

                Figure 2 Choosing Extend Volume
                -

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

                Figure 3 Extend Volume Wizard
                -

              6. 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 4 Selecting space
                -

              7. Click Finish.

                After the expansion succeeded, the partition size is larger than the original size.
                Figure 5 Capacity expansion succeeded
                +

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

                Figure 2 Choosing Extend Volume
                +

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

                Figure 3 Extend Volume Wizard
                +

              11. 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 4 Selecting space
                +

              12. Click Finish.

                After the expansion succeeded, the partition size is larger than the original size.
                Figure 5 Capacity expansion succeeded

              -

              System Disk: Create a New Volume with the 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)
                +

                System Disk: Create a New Volume with the 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. If you cannot see 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)
                  -

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

                  Figure 8 New Simple Volume (system disk)
                  -

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

                  Figure 9 New Simple Volume Wizard (system disk)
                  -

                6. 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)
                  -

                7. 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 Drive Letter or Path (system disk)
                  -

                8. 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)
                  -

                9. 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:)
                  +

                10. If you cannot see 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)
                  +

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

                  Figure 8 New Simple Volume (system disk)
                  +

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

                  Figure 9 New Simple Volume Wizard (system disk)
                  +

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

                14. 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 Drive Letter or Path (system disk)
                  +

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

                16. 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:)

                -

                System Disk: Create a New Volume Using the Available Space Shrunk from the Original Volume

                In this example, the system disk has 40 GiB originally, and 60 GiB is added on the management console and then formatted and added to volume (C:). This 60 GiB has not been used.

                -

                The following procedure describes how to use the shrink function to create new volume (D:) with this 60 GiB. After the operation is complete, new volume (D:) 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 Refresh (shrink volume)
                  +

                  System Disk: Create a New Volume Using the Available Space Shrunk from the Original Volume

                  In this example, the system disk has 40 GiB originally, and 60 GiB is added on the management console and then formatted and added to volume (C:). This 60 GiB has not been used.

                  +

                  The following procedure describes how to use the shrink function to create new volume (D:) with this 60 GiB. After the operation is complete, new volume (D:) 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 Refresh (shrink volume)
                    -

                  3. In the (C:) area of Disk 0, right-click the blank area and choose Shrink Volume.

                    Figure 16 Shrink Volume
                    -

                  4. The system automatically queries the available shrink space. In the displayed dialog box, enter the available space and click Shrink.

                    In this example, the volume available space is 60 GiB. Therefore, enter 61440 (60 × 1024 MiB).

                    -
                    Figure 17 Shrink (shrink volume)
                    -
                    After the operation is complete, Disk 0 has 60 GiB unallocated space.
                    Figure 18 Unallocated (shrink volume)
                    +

                  5. In the (C:) area of Disk 0, right-click the blank area and choose Shrink Volume.

                    Figure 16 Shrink Volume
                    +

                  6. The system automatically queries the available shrink space. In the displayed dialog box, enter the available space and click Shrink.

                    In this example, the volume available space is 60 GiB. Therefore, enter 61440 (60 × 1024 MiB).

                    +
                    Figure 17 Shrink (shrink volume)
                    +
                    After the operation is complete, Disk 0 has 60 GiB unallocated space.
                    Figure 18 Unallocated (shrink volume)
                    -

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

                    Figure 19 New Simple Volume (shrink volume)
                    -

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

                    Figure 20 New Simple Volume Wizard (shrink volume)
                    -

                  9. 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 21 Specify Volume Size (shrink volume)
                    -

                  10. 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 D is selected.

                    Figure 22 Assign Drive Letter or Path (shrink volume)
                    -

                  11. 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 23 Format Partition (shrink volume)
                    -

                  12. Click Finish.

                    After the expansion succeeded, new volume (D:) is displayed.
                    Figure 24 Completing the New Simple Volume Wizard (new volume D:)
                    -
                    Figure 25 New Volume (D:)
                    +

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

                    Figure 19 New Simple Volume (shrink volume)
                    +

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

                    Figure 20 New Simple Volume Wizard (shrink volume)
                    +

                  15. 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 21 Specify Volume Size (shrink volume)
                    +

                  16. 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 D is selected.

                    Figure 22 Assign Drive Letter or Path (shrink volume)
                    +

                  17. 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 23 Format Partition (shrink volume)
                    +

                  18. Click Finish.

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

                  -

                  Data Disk: Add the Additional Space to the Original Volume

                  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 26 Disk Management (data disk)
                    -

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

                    +

                    Data Disk: Add the Additional Space to the Original Volume

                    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 26 Disk Management (data disk)
                      +

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

                      -

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

                      Figure 27 Choosing Extend Volume (Windows Server 2008)
                      -

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

                      Figure 28 Extend Volume Wizard (Windows Server 2008)
                      -

                    6. 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 29 Selecting space (Windows Server 2008)
                      -

                    7. Click Finish.

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

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

                      Figure 27 Choosing Extend Volume (Windows Server 2008)
                      +

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

                      Figure 28 Extend Volume Wizard (Windows Server 2008)
                      +

                    11. 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 29 Selecting space (Windows Server 2008)
                      +

                    12. Click Finish.

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

                    -

                    Data Disk: Create a New Volume with the 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 31 Refresh (data disk)
                      +

                      Data Disk: Create a New Volume with the 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 31 Refresh (data disk)
                        -

                      3. If you cannot see 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 32 Unallocated disk space (data disk)
                        -

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

                        Figure 33 New Simple Volume (data disk)
                        -

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

                        Figure 34 New Simple Volume Wizard (data disk)
                        -

                      6. 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 35 Specify Volume Size (data disk)
                        -

                      7. 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 E is selected.

                        Figure 36 Assign Drive Letter or Path (data disk)
                        -

                      8. 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 37 Format Partition (data disk)
                        -

                      9. Click Finish.

                        After the expansion succeeded, new volume (E:) is displayed.
                        Figure 38 Completing the New Simple Volume Wizard (new volume E:)
                        -
                        Figure 39 New Volume (E:)
                        +

                      10. If you cannot see 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 32 Unallocated disk space (data disk)
                        +

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

                        Figure 33 New Simple Volume (data disk)
                        +

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

                        Figure 34 New Simple Volume Wizard (data disk)
                        +

                      13. 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 35 Specify Volume Size (data disk)
                        +

                      14. 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 E is selected.

                        Figure 36 Assign Drive Letter or Path (data disk)
                        +

                      15. 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 37 Format Partition (data disk)
                        +

                      16. Click Finish.

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

                      diff --git a/docs/evs/umn/en-us_topic_0021738346.html b/docs/evs/umn/en-us_topic_0021738346.html index 2e2b466f8..089abe85c 100644 --- a/docs/evs/umn/en-us_topic_0021738346.html +++ b/docs/evs/umn/en-us_topic_0021738346.html @@ -1,205 +1,199 @@ -

                      Create an EVS Disk

                      -

                      Scenarios

                      EVS disks can be used as system disks or data disks for servers. You can create data disks on the EVS console, or create them together with system disks on the ECS console.

                      -

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

                      +

                      Creating an EVS Disk

                      +

                      Scenarios

                      You can use EVS disks as system disks or data disks for servers. You can create data disks on the EVS console, or create them together with system disks on the cloud server console.

                      +

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

                      +

                      -

                      Constraints

                      -
                      Table 1 Constraints on creating disks

                      Created On

                      +

                      Notes and Constraints

                      +
                      - - - - - - -
                      Table 1 Constraints on creating disks

                      Create On

                      Description

                      +

                      Description

                      The EVS console

                      +

                      The EVS console

                      • Disks created on the EVS console are data disks. You need to manually attach them to servers.
                      • Disks can only be attached to servers in the same region and AZ. Once created, the region and AZ cannot be changed.
                      • There are quantity and capacity quotas on EVS disks, so properly plan the number of disks and total disk capacity your workloads require. For details, see Manage EVS Quotas.
                      +
                      • Disks created on the EVS console are data disks. You need to manually attach them to servers.
                      • Disks can only be attached to servers in the same region and AZ. Once created, the region and AZ cannot be changed.
                      • There are quantity and capacity quotas on EVS disks, so properly plan the number of disks and total disk capacity your workloads require. For details, see Managing EVS Quotas.

                      The ECS console

                      +

                      The cloud server console

                      • System disks can only be created together with servers and are automatically attached.
                      • Data disks created together with servers or added after the server creation are automatically attached.
                      • Disks will have the same billing mode as their server if the disks are created together with the server.
                      • By default, disks created with ECSs are VBD disks, and those created with BMSs are SCSI disks.
                      +
                      • System disks can only be created together with servers and are automatically attached.
                      • Data disks created together with servers or added after the server creation are automatically attached.
                      • Disks will have the same billing mode as their server if the disks are created together with the server.
                      • Disks created together with BMSs are SCSI disks.

                      -

                      +

                      -

                      Capacities of multiple disks cannot be combined, and the capacity of a single disk cannot be split.

                      +

                      Capacities of multiple disks cannot be combined, and the capacity of a single disk cannot be split.

                      -

                      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. Click Create Disk.

                        • Figure 1 shows the parameter setting of non-encrypted disks.
                          Figure 1 Non-encrypted disks
                          -
                        • Figure 2 shows the parameter setting of encrypted disks.
                          Figure 2 Encrypted disks
                          +

                          Procedure

                          1. Log in to the console.
                          2. Click in the upper left corner and select the desired region and project.
                          3. Click in the upper left corner and choose Storage > Elastic Volume Service.

                            The Elastic Volume Service page is displayed.

                            +

                          4. Click Create Disk.

                            • Figure 1 shows the parameter setting of non-encrypted disks.
                              Figure 1 Non-encrypted disks
                              +
                            • Figure 2 shows the parameter setting of encrypted disks.
                              Figure 2 Encrypted disks
                            -

                          5. Configure basic disk information according to Table 2.

                            -

                            Table 2 Disk parameters

                            Parameter

                            +

                          6. Configure disk parameters according to Table 2.

                            +

                            - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                            Table 2 Disk parameters

                            Parameter

                            Description

                            +

                            Description

                            Example Value

                            +

                            Example Value

                            Region

                            +

                            Region

                            Mandatory

                            -

                            Resources are region-specific and cannot be used across regions through internal network connections. For low network latency and quick resource access, select the nearest region.

                            +

                            Mandatory

                            +

                            Resources are region-specific and cannot be used across regions through internal network connections. For low network latency and quick resource access, select the nearest region.

                            eu-de

                            +

                            eu-de

                            AZ

                            +

                            AZ

                            Mandatory

                            -

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

                            Mandatory

                            +

                            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.

                            eu-de-1

                            +

                            eu-de-1

                            Disk Specifications

                            +

                            Disk Specifications

                            Mandatory

                            -
                            • Common I/O
                            • High I/O
                            • Ultra-high I/O
                            • General Purpose SSD
                            • 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.

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

                            Mandatory

                            +
                            • Common I/O
                            • High I/O
                            • Ultra-high I/O
                            • General Purpose SSD
                            • Extreme SSD
                            +
                            NOTE:
                            • If the 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.
                            • For more information about disk types, see Disk Types and Performance.

                            Common I/O

                            +

                            Common I/O

                            Disk Size (GiB)

                            +

                            Capacity (GiB)

                            Mandatory

                            -

                            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 a disk capacity, if the snapshot size is smaller than 10 GiB, the default 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.
                            +

                            Mandatory

                            +

                            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 a 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 a disk capacity, if the snapshot size is smaller than 10 GiB, the default 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 GiB

                            +

                            20 GiB

                            Create from backup

                            +

                            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.

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

                            +

                            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.

                            autobackup-001

                            +

                            autobackup-001

                            Create from snapshot

                            +

                            Create from snapshot

                            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.

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

                            +

                            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.

                            +
                            NOTE:

                            For details about how to create disks from snapshots, see Creating a Disk from a Snapshot.

                            snapshot-001

                            +

                            snapshot-001

                            Auto Backup

                            +

                            Auto Backup

                            Optional

                            -

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

                            +

                            Optional

                            +

                            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 Disk Backups.

                            -

                            +

                            -

                            Share

                            +

                            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 you select both SCSI and Share, 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 Shared EVS Disks.

                            +

                            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 you select both SCSI and Share, 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 Shared EVS Disks.

                            -

                            +

                            -

                            SCSI

                            +

                            SCSI

                            Optional

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

                            +

                            Optional

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

                            -

                            +

                            -

                            Encryption

                            +

                            Encryption

                            Optional

                            -

                            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.

                              -

                              After the KMS access rights have been granted, follow-up operations do not require the rights to be granted again.

                              +

                            Optional

                            +

                            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.

                              +

                              After the KMS access rights have been granted, follow-up operations do not require the rights to be granted again.

                            -
                            • 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
                                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 a KMS key and use it 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 evs/default.
                                • CMKs: Existing or newly created CMKs. For details, see Management > Creating a CMK in the Key Management Service User Guide.
                                +
                                A key name is the identifier of the key, and you can use KMS Key Name to specify a KMS key and use it for encryption. You can select one of the following keys:
                                • Default Master Key: After the KMS access rights have been granted to EVS, the system automatically creates a Default Master Key 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 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.

                              +
                              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 permissions 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 Managing Encrypted EVS Disks.

                            -

                            +

                            -

                            Tag

                            +

                            Tag

                            Optional

                            -

                            During the EVS disk creation, you can tag the EVS resources. Tags identify cloud resources for purposes of easy categorization and quick search.

                            -
                            A tag is composed of a key-value pair.
                            • Key: Mandatory if the disk is going to be tagged
                              • Must be unique for each resource.
                              • Can contain a maximum of 36 characters.
                              • Can contain only digits, letters, hyphens (-), and underscores (_).
                              -
                            • Value: Optional if the disk is going to be tagged
                              • Can contain a maximum of 43 characters.
                              • Can contain only digits, letters, hyphens (-), and underscores (_).
                              -
                            -
                            NOTE:
                            • A maximum of 10 tags can be added for an EVS disk.
                            • Tag keys of the same EVS disk must be unique.
                            • Except for tagging the disk during disk creation, you can also add, modify, or delete tags for existing disks. For details, see Manage EVS Tags.
                            -

                            For details about tags, see the Tag Management Service User Guide.

                            +

                            Optional

                            +
                            You can add tags when creating disks. Tags can help you identify, classify, and search for your disks. For details about tag rules, see Adding a Tag.
                            NOTE:
                            • Except for tagging the disk during disk creation, you can also add, modify, or delete tags for existing disks. For details, see Managing EVS Tags.
                            • For details about tags, see the Tag Management Service User Guide.

                            -

                            +

                            -

                            Disk Name

                            +

                            Disk Name

                            Mandatory

                            -
                            • If you create disks individually, this parameter value is used as the actual disk name.

                              The name can contain a maximum of 64 characters.

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

                              +

                            Mandatory

                            +
                            • If you create a single disk, the name you entered will be used as the disk name.

                              The name can contain a maximum of 64 characters.

                              +
                            • If you create multiple disks in a batch, the name you entered will be used as the prefix of disk names. An actual disk name will be composed of the name you entered 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

                            +

                            Quantity

                            Optional

                            -

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

                            Optional

                            +

                            The preset disk quantity is 1, which means only one disk is created. You can create a maximum of 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

                            +

                            1

                            -

                          7. Click Create Now.
                          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.
                            -

                          9. In the disk list, view the disk status.

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

                            +

                          10. Click Create Now.
                          11. On the Details page, check the disk configuration.

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

                          12. In the disk list, view the disk status.

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

                          13. diff --git a/docs/evs/umn/en-us_topic_0032860759.html b/docs/evs/umn/en-us_topic_0032860759.html index 9f1345717..638065ceb 100644 --- a/docs/evs/umn/en-us_topic_0032860759.html +++ b/docs/evs/umn/en-us_topic_0032860759.html @@ -1,36 +1,36 @@ -

                            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 and high availability (HA). 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 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.

                            +

                            Disk Sharing

                            +

                            What Is Disk Sharing?

                            Disk sharing allows you to create 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 provide multiple attachments, high concurrency, high performance, and high reliability. They are usually used for enterprise business-critical applications that require cluster deployment and high availability (HA). 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, including ECSs or 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.

                            +

                            A shared file system or cluster management system must be set up before you can properly use a shared disk. If you simply attach a shared disk to multiple servers, data cannot be shared between those servers and may be overwritten.

                            -
                            Figure 1 Application scenario of shared EVS disks
                            -

                            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, 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 a shared disk to the ECSs in the same ECS group to improve service reliability.
                            • Shared VBD disks: The device type of a newly created shared 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 disks: Such 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 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 disks to this ECS. Otherwise, SCSI reservations may not work properly, which may put your data at risk.
                              +
                              Figure 1 Application scenario of shared EVS disks
                              +

                              Important Notes on Using Shared EVS Disks

                              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, you must install the driver. For details, see Device Types.

                              +
                              You can create shared VBD disks or shared SCSI disks. It is recommended that you attach a shared disk to ECSs in the same ECS group to improve service reliability.
                              • Shared VBD disks: The device type of a newly created shared 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 disks: Such 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 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 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:

                                -
                                • The anti-affinity policy of an ECS group allows ECSs to be created on different physical servers to improve service reliability.

                                  For details about ECS groups, see Managing ECS Groups in the Elastic Cloud Server User Guide.

                                  -
                                • The SCSI reservation mechanism uses a SCSI reservation command to perform SCSI reservation operations. If an ECS sends such a command to an EVS disk, the disk is displayed as locked to other ECSs, preventing the data damage that may be caused by simultaneous read/write operations to the disk from multiple ECSs.
                                • ECS groups and SCSI reservations have the following relationship: A SCSI reservation on a single EVS disk cannot differentiate multiple ECSs on the same physical host. For that reason, if multiple ECSs that use the same shared EVS disk are running on the same physical host, SCSI reservations will not work properly. So you are advised to use SCSI reservations only on ECSs that are in the same ECS group, thus having a working anti-affinity policy.
                                +

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

                                +
                                • The anti-affinity policy of an ECS group allows ECSs to be created on different physical servers to improve service reliability.

                                  For details about ECS groups, see Managing ECS Groups in the Elastic Cloud Server User Guide.

                                  +
                                • The SCSI reservation mechanism uses a SCSI reservation command to perform SCSI reservation operations. If an ECS sends such a command to an EVS disk, the disk is displayed as locked to other ECSs, preventing the data damage that may be caused by simultaneous reads/writes to the disk from multiple ECSs.
                                • ECS groups and SCSI reservations have the following relationship: A SCSI reservation on a single EVS disk cannot differentiate multiple ECSs on the same physical host. For that reason, if multiple ECSs that use the same shared EVS disk are running on the same physical host, SCSI reservations will not work properly. So you are advised to use SCSI reservations only on ECSs that are in the same ECS group, thus having a working anti-affinity policy.
                              -

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

                              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 shared VBD disks are needed. They can also be used for Windows MSCS and Veritas VCS clusters that require SCSI reservations.
                              -

                              Specifications and Performance

                              Shared EVS disks have the same specifications and performance as non-shared EVS disks.

                              +

                              Specifications and Performance

                              Shared EVS disks have the same specifications and performance as non-shared EVS disks.

                              -

                              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.

                              -
                              If shared EVS disks are not managed by a cluster system, the following issues may occur:
                              • Data inconsistency caused by read/write conflicts

                                When a shared EVS disk is attached to two servers (server A and server B), server A cannot recognize the disk spaces allocated to server B, vice versa. That said, a disk space allocated to server A may be already used by server B. In this case, repeated disk space allocation occurs, which leads to data errors.

                                -

                                For example, a shared EVS disk has been formatted into the ext3 file system and attached to server A and server B. Server A has written metadata into the file system in space R and space G. Then server B has written metadata into space E and space G. In this case, the data written into space G by server A will be replaced. When the metadata in space G is read, an error will occur.

                                -
                              • Data inconsistency caused by data caching

                                When a shared EVS disk is attached to two servers (server A and server B), the application on server A has read the data in space R and space G, then cached the data. At that time, other processes and threads on server A would then read this data directly from the cache. At the same time, if the application on server B has modified the data in space R and space G, the application on server A cannot detect this data change and still reads this data from the cache. As a result, the user cannot view the modified data on server A.

                                -

                                For example, a shared EVS disk has been formatted into the ext3 file system and attached to server A and server B. Both servers have cached the metadata in the file system. Then server A has created a new file (file F) on the shared disk, but server B cannot detect this modification and still reads data from its cached data. As a result, the user cannot view file F on server B.

                                +

                                Data Sharing Principles and Common Usage Mistakes

                                A shared EVS disk is essentially the disk that can be attached to multiple servers for use. It 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 to any space on the disk. If no data read/write rules, such as the read/write sequence and meaning, between these servers are defined, data reads and writes between these servers may conflict, 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. 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.

                                +
                                If shared EVS disks are not managed by a cluster system, the following issues may occur:
                                • Data inconsistency caused by read/write conflicts

                                  When a shared EVS disk is attached to two servers (server A and server B), server A cannot recognize the disk spaces allocated to server B, vice versa. That said, a disk space allocated to server A may be already used by server B. In this case, repeated disk space allocation occurs, which leads to data errors.

                                  +

                                  For example, a shared EVS disk has been formatted into an ext3 file system and attached to server A and server B. Server A has written metadata into the file system in space R and space G. Then server B has written metadata into space E and space G. In this case, the data written into space G by server A will be replaced. When the metadata in space G is read, an error will occur.

                                  +
                                • Data inconsistency caused by data caching

                                  When a shared EVS disk is attached to two servers (server A and server B), the application on server A has read the data in space R and space G, then cached the data. At that time, other processes and threads on server A would then read this data directly from the cache. At the same time, if the application on server B has modified the data in space R and space G, the application on server A cannot detect this data change and still reads this data from the cache. As a result, the modified data cannot be viewed on server A.

                                  +

                                  For example, a shared EVS disk has been formatted into an ext3 file system and attached to server A and server B. Both servers have cached the metadata in the file system. Then server A has created a new file (file F) on the shared disk, but server B cannot detect this modification and still reads data from its cached data. As a result, file F cannot be viewed on server B.

                                -

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

                                +

                                Before you buy a shared EVS disk, determine its device type (VBD or SCSI) based on the applications that will use the shared disk. 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 how to use shared EVS disks, see Managing Shared EVS Disks.

                                +

                                If you simply attach a shared disk to multiple servers, data or files cannot be shared between the servers, because the shared disk does not have the cluster management capability. To share files between servers, build a shared file system or deploy a cluster management system.

                                diff --git a/docs/evs/umn/en-us_topic_0052554220.html b/docs/evs/umn/en-us_topic_0052554220.html index e1b5feb49..2b95fe286 100644 --- a/docs/evs/umn/en-us_topic_0052554220.html +++ b/docs/evs/umn/en-us_topic_0052554220.html @@ -1,43 +1,43 @@ -

                                Device Types and Usage Instructions

                                -

                                What Device Types Are Available?

                                There are two EVS device types: Virtual Block Device (VBD) and Small Computer System Interface (SCSI).
                                • VBD is the default EVS device type. VBD EVS disks support only basic read/write SCSI commands.
                                • SCSI EVS disks support transparent SCSI command transmission and allow the server OS to directly access the underlying storage media. Besides basic read/write SCSI commands, SCSI disks support advanced SCSI commands.
                                +

                                Device Types

                                +

                                What Device Types Are Available?

                                There are two EVS device types: Virtual Block Device (VBD) and Small Computer System Interface (SCSI).
                                • VBD is the default EVS device type. VBD EVS disks support only basic read/write SCSI commands.
                                • SCSI EVS disks support transparent SCSI command transmission and allow the server OS to directly access the underlying storage media. Besides basic read/write SCSI commands, SCSI disks support advanced SCSI commands.
                                -

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

                                +

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

                                  -

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

                                  To use SCSI EVS disks, a cloud server must have a SCSI driver installed. If the SCSI driver is not pre-installed, you need to install it manually.

                                  -
                                  Check whether you need to manually install the driver based on the server type.
                                  • 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.

                                    +

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

                                    To use SCSI EVS disks, a cloud server must have a SCSI driver installed. If the SCSI driver is not pre-installed, you need to install it manually.

                                    +
                                    Check whether you need to manually install the driver based on the server type.
                                    • 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.

                                      -
                                    • Xen ECS

                                      Due to driver limitations, you are advised not to use SCSI EVS disk with Xen ECSs.

                                      -
                                      However, a few images support SCSI EVS disks on Xen ECSs. For the supported images, see Table 1.

                                      After confirming that the OS images of Xen ECSs support SCSI EVS disks, determine whether you need to install the driver:

                                      -
                                      • Public Windows images are preinstalled with the Paravirtual SCSI (PVSCSI) driver. Therefore, no driver needs to be installed.
                                      • Private Windows images are not preinstalled with the PVSCSI driver. You need to download and install it explicitly.

                                        For details, see (Optional) Optimizing Windows Private Images in the Image Management Service User Guide.

                                        -
                                      • Linux images are not preinstalled with the PVSCSI driver. You need to obtain the source code of the open-source Linux driver at https://github.com/UVP-Tools/SAP-HANA-Tools, compile the code, and then install the driver.

                                        Note that this driver is different from the PVSCSI drivers attached to some Linux distributions.

                                        +
                                      • Xen ECS

                                        Due to driver limitations, you are advised not to use SCSI EVS disk with Xen ECSs.

                                        +
                                        However, a few Windows and Linux images support SCSI EVS disks on Xen ECSs. For the supported images, see Table 1.

                                        After confirming that the OS images of Xen ECSs support SCSI EVS disks, determine whether you need to install the driver:

                                        +
                                        • Public Windows images are preinstalled with the Paravirtual SCSI (PVSCSI) driver. Therefore, no driver needs to be installed.
                                        • Private Windows images are not preinstalled with the PVSCSI driver. You need to download and install it explicitly.

                                          For details, see (Optional) Optimizing Windows Private Images in the Image Management Service User Guide.

                                          +
                                        • Linux images are not preinstalled with the PVSCSI driver. You need to obtain the source code of the open-source Linux driver at https://github.com/UVP-Tools/SAP-HANA-Tools, compile the code, and then install the driver.

                                          Note that this driver is different from the PVSCSI drivers attached to some Linux distributions.

                                        -
                                        -
                                        Table 1 OSs supporting SCSI EVS disks

                                        Virtualization Type

                                        +
                                        +
                                        - - - - - - diff --git a/docs/evs/umn/en-us_topic_0066615262.html b/docs/evs/umn/en-us_topic_0066615262.html deleted file mode 100644 index d6ed31ab9..000000000 --- a/docs/evs/umn/en-us_topic_0066615262.html +++ /dev/null @@ -1,87 +0,0 @@ - - -

                                        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.

                                        -

                                        Creating snapshots does not affect the performance of the disk.

                                        -
                                        -
                                        -

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

                                        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 OSs supporting SCSI EVS disks

                                        Virtualization Type

                                        OS

                                        +

                                        OS

                                        Xen

                                        +

                                        Xen

                                        Windows

                                        +

                                        Windows

                                        See the Windows images listed on the Public Images page.

                                        -

                                        Log in to the management console, choose Image Management Service, click the Public Images tab, and select ECS image and Windows from the drop-down lists, respectively.

                                        +

                                        See the Windows images listed on the Public Images page.

                                        +

                                        Log in to the management console, choose Image Management Service, click the Public Images tab, and select ECS image and Windows from the drop-down lists, respectively.

                                        Linux

                                        +

                                        Linux

                                        • SUSE Linux Enterprise Server 11 SP4 64bit (The kernel version is 3.0.101-68-default or 3.0.101-80-default.)
                                        • SUSE Linux Enterprise Server 12 64bit (The kernel version is 3.12.51-52.31-default.)
                                        • SUSE Linux Enterprise Server 12 SP1 64bit (The kernel version is 3.12.67-60.64.24-default.)
                                        • SUSE Linux Enterprise Server 12 SP2 64bit (The kernel version is 4.4.74-92.35.1-default.)
                                        +
                                        • SUSE Linux Enterprise Server 11 SP4 64bit (The kernel version is 3.0.101-68-default or 3.0.101-80-default.)
                                        • SUSE Linux Enterprise Server 12 64bit (The kernel version is 3.12.51-52.31-default.)
                                        • SUSE Linux Enterprise Server 12 SP1 64bit (The kernel version is 3.12.67-60.64.24-default.)
                                        • SUSE Linux Enterprise Server 12 SP2 64bit (The kernel version is 4.4.74-92.35.1-default.)
                                        - - - - - - - - - -
                                        Table 1 Snapshot parameter

                                        Parameter

                                        -

                                        Description

                                        -

                                        Example Value

                                        -

                                        Snapshot Name

                                        -

                                        Mandatory

                                        -

                                        The name can contain a maximum of 64 characters.

                                        -

                                        snapshot-01

                                        -
                                        -
                                        -
                                        Figure 1 Create Snapshot
                                        -

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

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

                                        -

                                      • -
                                        -

                                        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 Snapshot parameters

                                          Parameter

                                          -

                                          Description

                                          -

                                          Example Value

                                          -

                                          Region

                                          -

                                          Mandatory

                                          -

                                          After you select a region, disks in the selected region will be displayed for you to choose from.

                                          -

                                          -

                                          -

                                          Snapshot Name

                                          -

                                          Mandatory

                                          -

                                          The name can contain a maximum of 64 characters.

                                          -

                                          snapshot-01

                                          -

                                          Select Disk

                                          -

                                          Mandatory

                                          -

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

                                          -

                                          volume-01

                                          -
                                          -
                                          -
                                          Figure 2 Create Snapshot
                                          -

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

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

                                          -

                                        -
                                        -

                                        Snapshot FAQ

                                        For more snapshot FAQs, see Snapshot.

                                        -
                                        - -
                                        - -
                                        - diff --git a/docs/evs/umn/en-us_topic_0066809008.html b/docs/evs/umn/en-us_topic_0066809008.html deleted file mode 100644 index 6db10204f..000000000 --- a/docs/evs/umn/en-us_topic_0066809008.html +++ /dev/null @@ -1,32 +0,0 @@ - - -

                                        EVS Snapshot

                                        -

                                        What Is EVS Snapshot?

                                        An EVS snapshot is a complete copy or image of the disk data at a specific point in time. Snapshots can be used as a disaster recovery (DR) approach, and you can use snapshots to fully restore data to the time when the snapshot was taken. You can create snapshots for disks on the console or via the API.

                                        -

                                        EVS snapshots are sometimes referred to as snapshots in this document.

                                        -

                                        You can create snapshots to rapidly save the disk data at specified time points. In addition, you can use snapshots to create new disks so that the created disks will contain the snapshot data in the beginning.

                                        -
                                        -

                                        Snapshot Principles

                                        Snapshots and backups are different in that a backup saves the data as another copy in the storage system other than on the disk, whereas a snapshot establishes a relationship between the snapshot and disk data.

                                        -
                                        The following example describes the snapshot principle by creating snapshots s1 and s2 for disk v1 at different time points:
                                        1. Create disk v1, which contains no data.
                                        2. Write data d1 and d2 to disk v1. Data d1 and d2 are written to new spaces.
                                        3. Create snapshot s1 for disk v1 that is modified in 2. Data d1 and d2 are not saved as another copy elsewhere. Instead, the relationship between snapshot s1 and data d1 and d2 is established.
                                        4. Write data d3 to disk v1 and change data d2 to d4. Data d3 and d4 are written to new spaces, and data d2 is not overwritten. The relationship between snapshot s1 and data d1 and d2 is still valid. Therefore, snapshot s1 can be used to restore data if needed.
                                        5. Create snapshot s2 for disk v1 that is modified in 4. The relationship between s2 and data d1, d3, and d4 is established.
                                          Figure 1 Snapshot principle
                                          -
                                        -
                                        -
                                        -

                                        Application Scenarios

                                        The snapshot function helps address your following needs:

                                        -
                                        • Routine data backup

                                          You can create snapshots for disks on a timely basis and use snapshots to recover your data in case that data loss or data inconsistency occurred due to unintended operations, viruses, or attacks.

                                          -
                                        • Rapid data restoration

                                          You can create a snapshot or multiple snapshots before an application software upgrade or a service data migration. If an exception occurs during the upgrade or migration, service data can be rapidly restored to the time point when the snapshot was created.

                                          -

                                          For example, a fault occurred on system disk A of server A, and therefore server A cannot be started. As system disk A is already faulty, data on system disk A cannot be restored by rolling back snapshots. But, you can create disk B using an existing snapshot of system disk A and attach disk B to a properly running server, for example server B. In this case, server B obtains the data of system disk A from disk B.

                                          -

                                          When rolling back data from snapshots, data can only be rolled back to the original disk, and a rollback to a different disk is not possible.

                                          -
                                          -
                                        • 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 diverse service requirements.

                                          -
                                        -
                                        -

                                        Usage Restrictions

                                        See Constraints for the snapshot usage restrictions.

                                        -
                                        -

                                        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 49e062499..ec2b4d613 100644 --- a/docs/evs/umn/evs_01_0001.html +++ b/docs/evs/umn/evs_01_0001.html @@ -1,43 +1,44 @@ -

                                        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. So 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 created.

                                        -

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

                                        +

                                        Disk Encryption

                                        +

                                        What Is Disk Encryption?

                                        EVS enables you to encrypt data on newly created disks as required.

                                        +

                                        It uses the industry-standard XTS-AES-256 cryptographic algorithm and keys to encrypt EVS disks. Keys used to encrypt EVS disks are provided by the Key Management Service (KMS), which is secure and convenient. 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 created.

                                        -

                                        Keys Used for EVS Encryption

                                        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.

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

                                        Keys Used for EVS Encryption

                                        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.

                                          It 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 section "Creating a CMK" in the Key Management Service User Guide.
                                        -

                                        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 a 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 can no longer 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. -
                                        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 a 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 can no longer 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. +
                                        - - - - - - - - - @@ -45,112 +46,112 @@ -

                                        Encryption Scenarios

                                        • System disk encryption

                                          System disks are created along with servers and cannot be created separately. So whether a system disk is encrypted or not depends on the image selected during the server creation. See the following table for details.

                                          +

                                          Encryption Scenarios

                                          • System disk encryption

                                            System disks are created along with servers and cannot be created separately. So whether a system disk is encrypted or not depends on the image you select when creating the server.

                                            -
                                        Table 1 Impact of CMK unavailability

                                        CMK Status

                                        Impact

                                        +

                                        Impact

                                        How to Restore

                                        +

                                        How to Restore

                                        Disabled

                                        +

                                        Disabled

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

                                          +
                                        • For an encrypted disk already attached:

                                          +

                                          Reads and writes to the disk are normal. If the disk is detached, it 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.

                                        Table 2 Encryption relationship between images and system disks

                                        Creating Server Using Encrypted Image

                                        +
                                        - - - - - - - -
                                        Table 2 Encryption relationship between images and system disks

                                        Creating Server Using Encrypted Image

                                        Whether System Disk Will Be Encrypted

                                        +

                                        Whether System Disk Will Be Encrypted

                                        Description

                                        +

                                        Description

                                        Yes

                                        +

                                        Yes

                                        Yes

                                        +

                                        Yes

                                        For details, see Managing Private Images > Encrypting Images in the Image Management Service User Guide.

                                        +

                                        For details, see Managing Private Images > Creating Encrypted Images in the Image Management Service User Guide.

                                        No

                                        +

                                        No

                                        No

                                        +

                                        No

                                        -

                                        +

                                        -

                                        -
                                      • Data disk encryption

                                        Data disks can be created along with servers or separately. Whether data disks are encrypted depends on their data sources. See the following table for details.

                                        +
                                      • Data disk encryption

                                        Data disks can be created along with servers or separately. Whether data disks are encrypted depends on their data sources. See the following table for details.

                                        -
                                        Table 3 Encryption relationship between backups, snapshots, images, and data disks

                                        Created On

                                        +
                                        - - - - - - - - - - - - - - - - - - - - - - - - - -
                                        Table 3 Encryption relationship between backups, snapshots, images, and data disks

                                        Created On

                                        Method of Creation

                                        +

                                        Method of Creation

                                        Whether Data Disk Will Be Encrypted

                                        +

                                        Whether Data Disk Will Be Encrypted

                                        Description

                                        +

                                        Description

                                        The ECS console

                                        +

                                        The ECS console

                                        Created together with the server

                                        +

                                        Created together with the server

                                        Yes/No

                                        +

                                        Yes/No

                                        When a data disk is created together with a server, you can choose to encrypt the disk or not. For details, see Getting Started > Creating an ECS > Step 1: Configure Basic Settings in the Elastic Cloud Server User Guide.

                                        +

                                        When a data disk is created together with a server, you can choose to encrypt the disk or not. For details, see Getting Started > Creating an ECS > Step 1: Configure Basic Settings in the Elastic Cloud Server User Guide.

                                        The EVS console

                                        +

                                        The EVS console

                                        No data source selected

                                        +

                                        No data source selected

                                        Yes/No

                                        +

                                        Yes/No

                                        When an empty disk is created, you can choose whether to encrypt the disk or not. The encryption attribute of the disk cannot be changed after the disk has been created.

                                        +

                                        When an empty disk is created, you can choose whether to encrypt the disk or not. The encryption attribute of the disk cannot be changed after the disk has been created.

                                        Creating from a backup

                                        +

                                        Creating from a backup

                                        Yes/No

                                        +

                                        Yes/No

                                        • When a disk is created from a backup, you can choose whether to encrypt the disk or not. The encryption attributes of the disk and backup do not need to be the same.
                                        • When you create a backup for a system or data disk, the encryption attribute of the backup will be the same as that of the disk.
                                        +
                                        • When a disk is created from a backup, you can choose whether to encrypt the disk or not. The encryption attributes of the disk and backup do not need to be the same.
                                        • When you create a backup for a system or data disk, the encryption attribute of the backup will be the same as that of the disk.

                                        Creating from a snapshot

                                        -

                                        (The snapshot's source disk is encrypted.)

                                        +

                                        Creating from a snapshot

                                        +

                                        (The snapshot's source disk is encrypted.)

                                        Yes

                                        +

                                        Yes

                                        A snapshot created from an encrypted disk is also encrypted.

                                        +

                                        A snapshot created from an encrypted disk is also encrypted.

                                        Creating from a snapshot

                                        -

                                        (The snapshot's source disk is not encrypted.)

                                        +

                                        Creating from a snapshot

                                        +

                                        (The snapshot's source disk is not encrypted.)

                                        No

                                        +

                                        No

                                        A snapshot created from a non-encrypted disk is not encrypted.

                                        +

                                        A snapshot created from a non-encrypted disk is not encrypted.

                                        Creating from an image

                                        -

                                        (The image's source disk is encrypted.)

                                        +

                                        Creating from an image

                                        +

                                        (The image's source disk is encrypted.)

                                        Yes

                                        +

                                        Yes

                                        -

                                        +

                                        -

                                        Creating from an image

                                        -

                                        (The image's source disk is not encrypted.)

                                        +

                                        Creating from an image

                                        +

                                        (The image's source disk is not encrypted.)

                                        No

                                        +

                                        No

                                        -

                                        +

                                        -

                                        -

                                        +

                                        -

                                        Who Can Use the Encryption Function?

                                        When a user uses 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 user, the user needs to follow the prompt to create an agency, which grants KMS Administrator permissions to EVS. Then the user can create and obtain keys to encrypt and decrypt disks.

                                          The first user must have the KMS Administrator permissions to create the agency. If the user does not have the KMS Administrator permissions, contact the account administrator to grant the permissions first.

                                          +

                                          Who Can Use the Encryption Function?

                                          When a user uses 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 user, the user needs to follow the prompt to create an agency, which grants KMS Administrator permissions to EVS. Then the user can create and obtain keys to encrypt and decrypt disks.

                                            The first user must have the KMS Administrator permissions to create the agency. If the user does not have the permissions, contact the account administrator to grant the permissions first.

                                            -
                                          • If the user is not the first user, the user can use encryption directly.
                                          +
                                        • If the user is not the first user, the user can use encryption directly.
                                        diff --git a/docs/evs/umn/evs_01_0002.html b/docs/evs/umn/evs_01_0002.html index f2cd1f70f..20e064861 100644 --- a/docs/evs/umn/evs_01_0002.html +++ b/docs/evs/umn/evs_01_0002.html @@ -1,14 +1,12 @@ -

                                        Detaching and Releasing an EVS Disk

                                        -
                                        +

                                        Detaching and Deleting an EVS Disk

                                        +
                                        diff --git a/docs/evs/umn/evs_01_0003.html b/docs/evs/umn/evs_01_0003.html index c2c946984..f141aedd3 100644 --- a/docs/evs/umn/evs_01_0003.html +++ b/docs/evs/umn/evs_01_0003.html @@ -1,30 +1,93 @@ -

                                        Detaching a System Disk

                                        -

                                        Scenarios

                                        If the file system on your system disk is damaged and your server cannot be started, you can detach the system disk and attach it to another server as a data disk. After the file system is fixed, you can re-attach the disk to the original server as the system disk.

                                        -

                                        If you no longer need a system disk or want to replace it with a new one, you can detach the system disk.

                                        -
                                        A system disk can only be detached offline, which means that its server must be in the Stopped state before the system disk is detached. To detach a system disk from a running server, you must first stop the server and then detach the disk.
                                        • For an attached system disk, 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 disk function selected.
                                        +

                                        Detaching an EVS Disk

                                        +

                                        Scenarios

                                        +
                                        + + + + + + + + + + + + + + + + +

                                        Disk Function

                                        +

                                        Server Status

                                        +

                                        Scenarios

                                        +

                                        Operation Instruction

                                        +

                                        System disk

                                        +

                                        Only offline detachment is supported.

                                        +

                                        You can only detach a system disk when the server status is Stopped.

                                        +
                                        • If the file system on your system disk is damaged and the server cannot be started, you can detach the system disk and attach it to another server as a data disk. After the file system is fixed, you can re-attach the disk to the original server as the system disk.
                                        • If you no longer need a system disk or want to replace it with a new one, you can detach it.
                                        +

                                        Detaching a System Disk

                                        +

                                        Data disk

                                        +

                                        Both online detachment and offline detachment are supported.

                                        +

                                        You can detach a data disk when the server status is Stopped or Running.

                                        +
                                        • If you want to use a data disk on another server in the same region and AZ, you can detach it and then attach it to that server.
                                        • If a data disk is no longer required, you can detach it and then delete it.
                                        +

                                        Detaching a Non-Shared Data Disk

                                        +

                                        Detaching a Shared Data Disk

                                        +
                                        +
                                        +
                                        • For an attached system disk, the disk function is displayed as System disk, and the disk status is displayed as In-use in the disk list. After the system disk is detached, 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 to be used as a system disk or data disk depending on the disk function selected.
                                        • For an attached data disk, the disk function is displayed as Data disk, and the disk status is displayed as In-use in the disk list. After the data disk is detached, the disk function remains unchanged, and the status changes to Available. For a shared disk, the status changes to Available only after it is detached from all its servers.
                                        -

                                        Constraints

                                        • A system disk can only be detached offline, which means that its server must be in the Stopped state before you can detach it. To detach a system disk from a running server, you must first stop the server and then detach the disk.
                                        • After a system disk is detached, some operations cannot be performed on the original server and the system disk. The restricted operations are as follows:
                                          • Server: starting the server, remote login, resetting the password, changing server billing mode, changing server specifications, changing the OS, reinstalling the OS, creating images, creating backups, adding disks, changing the security group, and changing the VPC
                                          +

                                          Notes and Constraints

                                          • You can attach SCSI disks to BMSs and use them as data disks.
                                          • After a system disk is detached, some operations cannot be performed on the original server and the system disk. The restrictions are as follows:
                                            • Server: starting the server, remote login, resetting the password, changing server billing mode, changing server specifications, changing the OS, reinstalling the OS, creating images, creating backups, adding disks, changing the security group, and changing the VPC
                                          -

                                          Procedure

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

                                            The Elastic Cloud Server page is displayed.

                                            -

                                          4. In the server list, locate the row that contains the server whose system disk is to be detached, click More in the Operation column, and choose Stop.

                                            When the server status changes to Stopped, the server has been stopped.

                                            -

                                          5. Click the name of this server.

                                            The server details page is displayed.

                                            -

                                          6. Click the Disks tab to view the system disk attached to the server.
                                          7. 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)
                                            +

                                            Prerequisites

                                            • Before detaching an EVS disk from a running Windows server, ensure that no programs are reading data from or writing data to the disk. Otherwise, data will be lost.
                                            +
                                            • Before detaching an EVS disk from a running Linux server, you must log in to the server and run the umount command to cancel the association between the disk and the file system, and ensure that no programs are reading data from or writing data to the disk. Otherwise, you will not be able to detach the disk.
                                            -

                                          8. Click Yes to detach the disk.

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

                                            -

                                          9. (Optional) Re-attach the bootable disk to a server. You can use it as a system disk or data disk depending on the disk function you select.

                                            +

                                            Detaching a System Disk

                                            1. Log in to the console.
                                            2. Click in the upper left corner and select the desired region and project.
                                            3. Choose Compute > Elastic Cloud Server.

                                              The Elastic Cloud Server page is displayed.

                                              +

                                            4. In the server list, locate the row that contains the server whose system disk is to be detached, click More in the Operation column, and choose Stop.

                                              When the server status changes to Stopped, the server has been stopped.

                                              +

                                            5. Click the name of this server.

                                              The server details page is displayed.

                                              +

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

                                              The Detach Disk dialog box is displayed.
                                              Figure 1 Detach Disk (system disk)
                                              +
                                              +

                                            8. Click Yes to detach the disk.

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

                                              +

                                            9. (Optional) Re-attach the bootable disk to a server. You can use it as a system disk or data disk depending on the disk function you select.
                                            +
                                            +

                                            Detaching a Non-Shared Data Disk

                                            1. Log in to the console.
                                            2. Click in the upper left corner and select the desired region and project.
                                            3. Click in the upper left corner and choose Storage > Elastic Volume Service.

                                              The Elastic Volume Service page is displayed.

                                              +

                                            4. Choose a way to detach the disk by determining whether you want to check the server information first.

                                              • If yes, 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 server where the disk has been attached.
                                                3. Click to select the server and click Detach Disk.
                                                  The Detach Disk dialog box is displayed.
                                                  Figure 2 Detach Disk
                                                  +
                                                  +
                                                4. Click Yes to detach the disk.
                                                +
                                              • If no, 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.
                                                  Figure 3 Detach Disk dialog box
                                                  +
                                                  +
                                                2. Click Yes to detach the disk.
                                                +
                                              +

                                              In the disk list, the disk status is Detaching, indicating that the disk is being detached from the server.

                                              +

                                              When the status changes to Available, the disk has been detached.

                                            -

                                            Related Operations

                                            For more detachment FAQs, see Detachment.

                                            +

                                            Detaching a Shared Data Disk

                                            1. Log in to the console.
                                            2. Click in the upper left corner and select the desired region and project.
                                            3. Choose Storage > Elastic Volume Service.

                                              The Elastic Volume Service page is displayed.

                                              +

                                            4. Choose a way to detach the disk by determining whether you want to check server information first.

                                              • If yes, 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 disk has been attached.
                                                3. Click to select servers 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.
                                                  Figure 4 Detaching a shared disk
                                                  +
                                                  +
                                                4. Click Yes to detach the disk.
                                                +
                                              • If no, 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.
                                                  Figure 5 Detaching a shared disk dialog box
                                                  +
                                                  +
                                                2. Click to select servers.

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

                                                  +
                                                3. Click Yes to detach the disk.
                                                +
                                              +

                                              In the disk list, the disk status is Detaching, indicating that the disk is being detached from the server.

                                              +

                                              If a shared disk has been attached to multiple servers and you only detach it from some of the servers, the disk status will go back to In-use after the disk has been detached from the servers. The disk status changes to Available only after the disk has been detached from all the servers.

                                              +

                                            +
                                            +

                                            Helpful Links

                                            To check out more detachment FAQs, see Detachment.

                                            diff --git a/docs/evs/umn/evs_01_0004.html b/docs/evs/umn/evs_01_0004.html deleted file mode 100644 index 7ba1d890f..000000000 --- a/docs/evs/umn/evs_01_0004.html +++ /dev/null @@ -1,52 +0,0 @@ - - -

                                            Detaching a Data Disk

                                            -

                                            Scenarios

                                            If you want to use a data disk on another server in the same region and AZ, you can detach the data disk and then attach it to that server.

                                            -

                                            If a data disk is no longer required, you can detach it and then delete it.

                                            -
                                            Data disks can be detached online or offline, meaning that the server using the to-be-detached data disk can either be in the Running or Stopped state.
                                            • ECS

                                              Detach a disk from a running server. For details, see Storage > Detaching an EVS Disk from a Running ECS in the Elastic Cloud Server User Guide.

                                              -
                                            • BMS

                                              SCSI disks can be attached to BMSs and used as data disks. You can detach a data disk either from a running or stopped BMS.

                                              -
                                            -
                                            -

                                            For an attached data disk, the disk function is displayed as Data disk, and the disk status is displayed as In-use in the disk list. After the data disk has been detached from the server, the disk function remains unchanged, the disk status changes to Available for a non-shared data disk, and the disk status changes to Available for a shared data disk after it is detached from all its servers.

                                            -
                                            -
                                            -

                                            Precautions

                                            Data may be lost after you detach an encrypted disk. For more information, see If I Detach a Disk, Will I Lose the Data on My Disk?.

                                            -
                                            -

                                            Prerequisites

                                            • Before detaching an EVS disk from a running Windows ECS, ensure that no programs are reading data from or writing data to the disk. Otherwise, data will be lost.
                                            -
                                            • Before detaching an EVS disk from a running Linux ECS, you must log in to the ECS and run the umount command to cancel the association between the disk and the file system. In addition, ensure that no programs are reading data from or writing data to the disk. Otherwise, detaching the disk will fail.
                                            -
                                            -

                                            Detaching a Non-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. Choose a way to detach the disk by determining whether you want to check server information first.

                                              • If yes, 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 server where the target disk has been attached.
                                                3. 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
                                                  -
                                                  -
                                                4. Click Yes to detach the disk.
                                                -
                                              • If no, 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.
                                                -
                                              -

                                              The disk list is displayed. The disk status is Detaching, indicating that the disk is being detached from the server.

                                              -

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

                                              -

                                            -
                                            -

                                            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. Choose a way to detach the disk by determining whether you want to check server information first.

                                              • If yes, 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
                                                  -
                                                  -
                                                4. Click Yes to detach the disk.
                                                -
                                              • If no, 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.
                                                -
                                              -

                                              The disk list page is displayed. The disk status is Detaching, indicating that the disk is being detached from the server.

                                              -

                                              If the shared EVS disk has been attached to multiple servers and needs to be detached from only some of its servers, the disk status will go back to In-use after the disk has been detached from the target servers. The disk status changes to Available only when it has been detached from all the servers.

                                              -

                                            -
                                            -
                                            - - diff --git a/docs/evs/umn/evs_01_0005.html b/docs/evs/umn/evs_01_0005.html index 395885728..05e47c293 100644 --- a/docs/evs/umn/evs_01_0005.html +++ b/docs/evs/umn/evs_01_0005.html @@ -1,21 +1,22 @@ -

                                            Deleting EVS Disks

                                            -

                                            Scenarios

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

                                            -
                                            • The disk status is Available, Error, Expansion failed, Restoration failed, or Rollback failed.
                                            • The disk is not locked by any service.
                                            • The shared disk has been detached from all its servers.
                                            -

                                            When a disk is deleted, EVS immediately destroys the metadata so that data can no longer be accessed. In addition, the physical storage space of the disk is reclaimed and cleared before being re-assigned. For any new disk created based on the re-assigned physical space, before data is written to the disk, EVS returns zero for all the read and write requests to the disk.

                                            +

                                            Deleting an EVS Disk

                                            +

                                            Scenarios

                                            If an EVS disk is no longer used, you can delete the disk to release the virtual resources. When a disk is deleted, EVS immediately destroys the metadata to ensure that data can no longer be accessed. In addition, the physical storage space of the disk is reclaimed and cleared before being re-assigned. For any new disk created based on the re-assigned physical space, before data is written to the disk, EVS returns zero for all the read requests to the disk.

                                            -
                                            • When you delete a disk, all the disk data including the snapshots created for this disk will be deleted.
                                            • A deleted disk cannot be recovered.
                                            +

                                            Notes and Constraints

                                            • The disk status is Available, Error, Expansion failed, Restoration failed, or Rollback failed.
                                            • The disk is not locked by any service.
                                            • The shared disk has been detached from all its servers.
                                            +
                                            +

                                            When you delete a disk, all the disk data including the legacy snapshots created for this disk will be deleted.

                                            +

                                            A deleted disk cannot be recovered.

                                            -

                                            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, click More in the Operation column, and choose Delete.
                                            5. (Optional) If multiple disks are to be deleted, select in front of each disk and click Delete in the upper area of the list.
                                            6. In the displayed dialog box, confirm the information and click Yes.
                                            +

                                            Deleting EVS Disks

                                            1. Log in to the console.
                                            2. Click in the upper left corner and select the desired region and project.
                                            3. Click in the upper left corner and choose Storage > Elastic Volume Service.

                                              The Elastic Volume Service page is displayed.

                                              +

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

                                            Related Operations

                                            For more deletion FAQs, see Deletion.

                                            +

                                            Helpful Links

                                            For more deletion FAQs, see Deletion.

                                            diff --git a/docs/evs/umn/evs_01_0006.html b/docs/evs/umn/evs_01_0006.html index c0c23281a..dff7d06bd 100644 --- a/docs/evs/umn/evs_01_0006.html +++ b/docs/evs/umn/evs_01_0006.html @@ -1,54 +1,54 @@

                                            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. A system disk can be expanded to up to 1 TiB, and a data disk to 32 TiB. Disk capacity can only be expanded, not reduced.

                                            -

                                            If you detach a system disk and then attach it to an ECS as a data disk, the maximum capacity of this disk is still 1 TiB.

                                            +

                                            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. A system disk can be expanded to up to 1 TiB, and a data disk to 32 TiB. Disk capacity can only be expanded, not reduced.

                                            +

                                            If you detach a system disk and then attach it to another server as a data disk, the maximum capacity of this disk is still 1 TiB.

                                            -

                                            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
                                            +

                                            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.
                                            • For an In-use disk:
                                              The disk has been attached to a server. Check whether the disk can be expanded in the In-use state by referring to Constraints. +

                                              Expand the Disk Capacity on the Management Console

                                              Choose a proper expansion method based on the disk status.
                                              -

                                              Log In to the Server and Extend the Disk Partition and File System

                                              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. For details, see Table 1. -
                                              Table 1 Extending the disk partition and file system

                                              Capacity After Expansion

                                              +

                                              Log In to the Server and Extend the Disk Partition and File System

                                              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. For details, see Table 1. +
                                              - - - - -
                                              Table 1 Extending the disk partition and file system

                                              Capacity After Expansion

                                              Extend Disk Partition and File System

                                              +

                                              Extend Disk Partition and File System

                                              Disk capacity ≤ 2 TiB

                                              +

                                              Disk capacity ≤ 2 TiB

                                              +

                                              Disk capacity > 2 TiB

                                              +

                                              Disk capacity > 2 TiB

                                              -

                                              If the server is stopped during the expansion, the additional space of a Windows system disk, Windows data disk, or Linux system disk may be automatically added to the last partition after the server is started. In this case, the additional space can be directly used. If the additional space is not automatically added, extend the partition and file system according to the preceding steps.

                                              +

                                              If the server is stopped during the expansion, the additional space of a Windows system disk, Windows data disk, or Linux system disk may be automatically added to the last partition after the server is started. In this case, the additional space can be directly used. If the additional space is not automatically added, extend the partition and file system according to the preceding steps.

                                              -

                                              Related Operations

                                              For more expansion FAQs, see Capacity Expansion.

                                              +

                                              Helpful Links

                                              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 871f2f5d3..1b5d51ae8 100644 --- a/docs/evs/umn/evs_01_0007.html +++ b/docs/evs/umn/evs_01_0007.html @@ -1,35 +1,35 @@

                                              Expanding Capacity for an In-use EVS Disk

                                              -

                                              Scenarios

                                              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. You do not need to detach the disk when expanding an In-use disk.

                                              +

                                              Scenarios

                                              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. You do not need to detach the disk when expanding an In-use disk.

                                              -

                                              Constraints

                                              • Disk capacity can be expanded, but cannot be reduced.
                                              • When expanding an In-use disk, the server attached with this disk must be in the Running or Stopped state.
                                              • A shared disk in the In-use state cannot be expanded. To expand such a 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.

                                                For servers without such support, 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.

                                                +

                                                Notes and Constraints

                                                • Disk capacity can be expanded, but cannot be reduced.
                                                • When expanding an In-use disk, the server attached with this disk must be in the Running or Stopped state.
                                                • A shared disk in the In-use state cannot be expanded. To expand such a 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 allow you to expand capacity while disks are In-use. For details, see the official document of the corresponding OS.

                                                  For servers without such support, 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.

                                                -

                                                Prerequisites

                                                Disk data has been backed up using CBR or snapshots. For details about backups, see Managing EVS Backups. For details about snapshots, see Creating a Snapshot.

                                                +

                                                Prerequisites

                                                Disk data has been backed up using CBR or snapshots. For details about backups, see Managing EVS Disk Backups. For details about snapshots, see Creating an EVS Snapshot.

                                                -

                                                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. Choose a way to expand the disk by determining whether you want to check server information first.

                                                  • If yes, 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.

                                                      +

                                                      Procedure

                                                      1. Log in to the console.
                                                      2. Click in the upper left corner and select the desired region and project.
                                                      3. Choose Storage > Elastic Volume Service.

                                                        The Elastic Volume Service page is displayed.

                                                        +

                                                      4. Choose a way to expand the disk by determining whether you want to check server information first.

                                                        • If yes, 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 no, 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 no, 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 New Capacity parameter and click Next.
                                                      6. On the Details page, check the disk details.

                                                        • Click Submit to start the expansion.
                                                        • Click Previous to change the settings.
                                                        -

                                                        After the configuration is submitted, go back to the disk list page.

                                                        -

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

                                                        -

                                                        When the status of a disk is Expanding, you are not allowed to modify the specifications of the ECS where the disk is attached.

                                                        +

                                                      8. Set the New Capacity parameter and click Next.
                                                      9. On the Details page, check the disk configuration.

                                                        • Click Submit to start the expansion.
                                                        • Click Previous to change the settings.
                                                        +

                                                        After the configuration is 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 In-use and the disk capacity increases, the expansion has succeeded.

                                                        +

                                                        When the status of the disk is Expanding, you are not allowed to modify the specifications of the ECS where the disk is attached.

                                                        -

                                                        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. Disks whose capacities failed to be expanded are not billed.

                                                        +

                                                        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. Disks whose capacities failed to be expanded are not billed.

                                                        -

                                                      11. Log in to the server and extend the partition and file system after the disk has been expanded on the console, because previous steps only enlarge the disk space.

                                                        The operations vary depending on the server OS.

                                                        - +

                                                      12. Log in to the server and extend the partition and file system after the disk has been expanded on the console, because previous steps only enlarge the disk space.

                                                        The operations vary depending on the server OS.

                                                        +

                                                diff --git a/docs/evs/umn/evs_01_0008.html b/docs/evs/umn/evs_01_0008.html index 56f672ba4..20a43a83f 100644 --- a/docs/evs/umn/evs_01_0008.html +++ b/docs/evs/umn/evs_01_0008.html @@ -1,29 +1,29 @@

                                                Expanding Capacity for an Available EVS Disk

                                                -

                                                Scenarios

                                                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 to any server.

                                                +

                                                Scenarios

                                                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 to any server.

                                                -

                                                Constraints

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

                                                Notes and Constraints

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

                                                Prerequisites

                                                Disk data has been backed up using CBR or snapshots. For details about backups, see Managing EVS Backups. For details about snapshots, see Creating a Snapshot.

                                                +

                                                Prerequisites

                                                Disk data has been backed up using CBR or snapshots. For details about backups, see Managing EVS Disk Backups. For details about snapshots, see Creating an EVS Snapshot.

                                                -

                                                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 New Capacity parameter and click Next.
                                                6. On the Details page, check the disk details.

                                                  • Click Submit to start the expansion.
                                                  • Click Previous to change the settings.
                                                  -

                                                  After the configuration is submitted, go back to the disk list page.

                                                  -

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

                                                  -

                                                  When the status of a disk is Expanding, you are not allowed to modify the specifications of the ECS where the disk is attached.

                                                  +

                                                  Procedure

                                                  1. Log in to the console.
                                                  2. Click in the upper left corner and select the desired region and project.
                                                  3. Choose Storage > Elastic Volume Service.

                                                    The Elastic Volume Service 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 New Capacity parameter and click Next.
                                                  6. On the Details page, check the disk configuration.

                                                    • Click Submit to start the expansion.
                                                    • Click Previous to change the settings.
                                                    +

                                                    After the configuration is submitted, go back to the disk list page.

                                                    +

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

                                                    +

                                                    When the status of the disk is Expanding, you are not allowed to modify the specifications of the ECS where the disk is attached.

                                                    -

                                                    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. Disks whose capacities failed to be expanded are not billed.

                                                    +

                                                    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. Disks whose capacities failed to be expanded are not billed.

                                                    -

                                                  8. Attach the disk to the server. For details, see Attach an EVS Disk.
                                                  9. Log in to the server and extend the partition and file system after the disk has been expanded on the console, because previous steps only enlarge the disk space.

                                                    The operations vary depending on the server OS.

                                                    - +

                                                  10. Attach the disk to the server. For details, see Attach an EVS Disk.
                                                  11. Log in to the server and extend the partition and file system after the disk has been expanded on the console, because previous steps only enlarge the disk space.

                                                    The operations vary depending on the server OS.

                                                    +

                                                  diff --git a/docs/evs/umn/evs_01_0009.html b/docs/evs/umn/evs_01_0009.html index af0dd263e..f9f9c4206 100644 --- a/docs/evs/umn/evs_01_0009.html +++ b/docs/evs/umn/evs_01_0009.html @@ -1,150 +1,192 @@

                                                  Managing Encrypted EVS Disks

                                                  -

                                                  Encryption Scenarios

                                                  • System disk encryption

                                                    System disks are created along with servers and cannot be created separately. So whether a system disk is encrypted or not depends on the image selected during the server creation. See the following table for details.

                                                    - -
                                                    Table 1 Encryption relationship between images and system disks

                                                    Creating Server Using Encrypted Image

                                                    +

                                                    What Is EVS Disk Encryption?

                                                    EVS enables you to encrypt data on newly created disks as required.

                                                    +

                                                    It uses the industry-standard XTS-AES-256 cryptographic algorithm and keys to encrypt EVS disks. Keys used to encrypt EVS disks are provided by the Key Management Service (KMS), which is secure and convenient. 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 created.

                                                    +

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

                                                    +
                                                    +
                                                    +

                                                    Keys Used for EVS Encryption

                                                    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.

                                                      It 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 section "Creating a CMK" in the Key Management Service User Guide.
                                                    +
                                                    +

                                                    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 a 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 can no longer 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. +
                                                    - - - - - - - - + +
                                                    Table 1 Impact of CMK unavailability

                                                    CMK Status

                                                    Whether System Disk Will Be Encrypted

                                                    +

                                                    Impact

                                                    Description

                                                    +

                                                    How to Restore

                                                    Yes

                                                    +

                                                    Disabled

                                                    Yes

                                                    +
                                                    • For an encrypted disk already attached: Reads and writes to the disk are normal. If the disk is detached, it cannot be attached again.
                                                    • For an encrypted disk not attached: The disk cannot be attached anymore.

                                                    For details, see Managing Private Images > Encrypting Images in the Image Management Service User Guide.

                                                    +

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

                                                    No

                                                    +

                                                    Scheduled deletion

                                                    No

                                                    +

                                                    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

                                                    +

                                                    Data on the disks can never be restored.

                                                    -
                                                  • Data disk encryption

                                                    Data disks can be created along with servers or separately. Whether data disks are encrypted depends on their data sources. See the following table for details.

                                                    +
                                                  • +
                                                    +

                                                    Encryption Scenarios

                                                    • System disk encryption

                                                      System disks are created along with servers and cannot be created separately. So whether a system disk is encrypted or not depends on the image you select when creating the server.

                                                      -
                                                      Table 2 Encryption relationship between backups, snapshots, images, and data disks

                                                      Created On

                                                      +
                                                      - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                                                      Table 2 Encryption relationship between images and system disks

                                                      Creating Server Using Encrypted Image

                                                      Method of Creation

                                                      +

                                                      Whether System Disk Will Be Encrypted

                                                      Whether Data Disk Will Be Encrypted

                                                      -

                                                      Description

                                                      +

                                                      Description

                                                      The ECS console

                                                      +

                                                      Yes

                                                      Created together with the server

                                                      +

                                                      Yes

                                                      Yes/No

                                                      -

                                                      When a data disk is created together with a server, you can choose to encrypt the disk or not. For details, see Getting Started > Creating an ECS > Step 1: Configure Basic Settings in the Elastic Cloud Server User Guide.

                                                      +

                                                      For details, see Managing Private Images > Creating Encrypted Images in the Image Management Service User Guide.

                                                      The EVS console

                                                      +

                                                      No

                                                      No data source selected

                                                      +

                                                      No

                                                      Yes/No

                                                      -

                                                      When an empty disk is created, you can choose whether to encrypt the disk or not. The encryption attribute of the disk cannot be changed after the disk has been created.

                                                      -

                                                      Creating from a backup

                                                      -

                                                      Yes/No

                                                      -
                                                      • When a disk is created from a backup, you can choose whether to encrypt the disk or not. The encryption attributes of the disk and backup do not need to be the same.
                                                      • When you create a backup for a system or data disk, the encryption attribute of the backup will be the same as that of the disk.
                                                      -

                                                      Creating from a snapshot

                                                      -

                                                      (The snapshot's source disk is encrypted.)

                                                      -

                                                      Yes

                                                      -

                                                      A snapshot created from an encrypted disk is also encrypted.

                                                      -

                                                      Creating from a snapshot

                                                      -

                                                      (The snapshot's source disk is not encrypted.)

                                                      -

                                                      No

                                                      -

                                                      A snapshot created from a non-encrypted disk is not encrypted.

                                                      -

                                                      Creating from an image

                                                      -

                                                      (The image's source disk is encrypted.)

                                                      -

                                                      Yes

                                                      -

                                                      -

                                                      -

                                                      Creating from an image

                                                      -

                                                      (The image's source disk is not encrypted.)

                                                      -

                                                      No

                                                      -

                                                      -

                                                      +

                                                      -

                                                      -

                                                      +
                                                    • Data disk encryption

                                                      Data disks can be created along with servers or separately. Whether data disks are encrypted depends on their data sources. See the following table for details.

                                                      + +
                                                      + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
                                                      Table 3 Encryption relationship between backups, snapshots, images, and data disks

                                                      Created On

                                                      +

                                                      Method of Creation

                                                      +

                                                      Whether Data Disk Will Be Encrypted

                                                      +

                                                      Description

                                                      +

                                                      The ECS console

                                                      +

                                                      Created together with the server

                                                      +

                                                      Yes/No

                                                      +

                                                      When a data disk is created together with a server, you can choose to encrypt the disk or not. For details, see Getting Started > Creating an ECS > Step 1: Configure Basic Settings in the Elastic Cloud Server User Guide.

                                                      +

                                                      The EVS console

                                                      +

                                                      No data source selected

                                                      +

                                                      Yes/No

                                                      +

                                                      When an empty disk is created, you can choose whether to encrypt the disk or not. The encryption attribute of the disk cannot be changed after the disk has been created.

                                                      +

                                                      Creating from a backup

                                                      +

                                                      Yes/No

                                                      +
                                                      • When a disk is created from a backup, you can choose whether to encrypt the disk or not. The encryption attributes of the disk and backup do not need to be the same.
                                                      • When you create a backup for a system or data disk, the encryption attribute of the backup will be the same as that of the disk.
                                                      +

                                                      Creating from a snapshot

                                                      +

                                                      (The snapshot's source disk is encrypted.)

                                                      +

                                                      Yes

                                                      +

                                                      A snapshot created from an encrypted disk is also encrypted.

                                                      +

                                                      Creating from a snapshot

                                                      +

                                                      (The snapshot's source disk is not encrypted.)

                                                      +

                                                      No

                                                      +

                                                      A snapshot created from a non-encrypted disk is not encrypted.

                                                      +

                                                      Creating from an image

                                                      +

                                                      (The image's source disk is encrypted.)

                                                      +

                                                      Yes

                                                      +

                                                      -

                                                      +

                                                      Creating from an image

                                                      +

                                                      (The image's source disk is not encrypted.)

                                                      +

                                                      No

                                                      +

                                                      -

                                                      +
                                                      +
                                                      +

                                                    • -

                                                      Constraints

                                                      -
                                                      Table 3 Constraints on disk encryption

                                                      Item

                                                      +

                                                      Notes and Constraints

                                                      +
                                                      - - - - - - - - -
                                                      Table 4 Constraints on disk encryption

                                                      Item

                                                      Description

                                                      +

                                                      Description

                                                      Types of disks supporting encryption

                                                      +

                                                      Types of disks supporting encryption

                                                      All disk types

                                                      +

                                                      All disk types

                                                      Constraints on encrypted disks

                                                      +

                                                      Constraints on encrypted disks

                                                      The encryption attribute of a disk cannot be changed after the disk is created, meaning that:

                                                      -
                                                      • An encrypted disk cannot be changed to a non-encrypted disk.
                                                      • A non-encrypted disk cannot be changed to an encrypted disk.
                                                      +

                                                      The encryption attribute of a disk cannot be changed after the disk is created, meaning that:

                                                      +
                                                      • An encrypted disk cannot be changed to a non-encrypted disk.
                                                      • A non-encrypted disk cannot be changed to an encrypted disk.

                                                      Constraints on user permissions

                                                      +

                                                      Constraints on user permissions

                                                      When a user uses 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 user, the user needs to follow the prompt to create an agency, which grants KMS Administrator permissions to EVS. Then the user can create and obtain keys to encrypt and decrypt disks.
                                                        NOTE:

                                                        The first user must have the KMS Administrator permissions to create the agency. If the user does not have the KMS Administrator permissions, contact the account administrator to grant the permissions first.

                                                        +

                                                      When a user uses 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 user, the user needs to follow the prompt to create an agency, which grants EVS Administrator permissions to EVS. Then, the user can create and obtain keys to encrypt and decrypt disks.
                                                        NOTE:

                                                        The first user must have the EVS Administrator permissions to create the agency. If the user does not have the permissions, contact the account administrator to grant the permissions first.

                                                        -
                                                      • If the user is not the first user, the user can use encryption directly.
                                                      +
                                                    • If the user is not the first user, the user can use encryption directly.
                                                    • Constraints on encrypted images

                                                      +

                                                      Constraints on encrypted images

                                                      • Encrypted images cannot be replicated across regions.
                                                      • Encrypted images cannot be changed to non-encrypted images.
                                                      • Encrypted images cannot be exported.
                                                      +
                                                      • Encrypted images cannot be replicated across regions.
                                                      • Encrypted images cannot be changed to non-encrypted images.
                                                      • Encrypted images cannot be exported.
                                                      -

                                                      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 permissions, grant the KMS access rights to EVS directly. If you do not have this permission, contact a user with the security administrator permissions to grant KMS access rights to EVS and then select the encryption option to create an encrypted disk.

                                                      -

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

                                                      +

                                                      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 permissions, grant the KMS access rights to EVS directly. If you do not have this permission, contact a user with the security administrator permissions to grant KMS access rights to EVS and then select the encryption option to create an encrypted disk.

                                                      +

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

                                                      -

                                                      Detaching an Encrypted EVS Disk

                                                      Before you detach a disk encrypted by a CMK, check whether the CMK is disabled or scheduled for deletion.

                                                      -
                                                      • If the CMK is available, the disk can be detached and re-attached, and data on the disk will not be lost.
                                                      • If the CMK is unavailable, the disk can still be used, but there is no guarantee for how long it will be usable. If the disk is detached, it will be impossible to re-attach it later. In this case, do not detach the disk without a working CMK.
                                                      -

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

                                                      -

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

                                                      +

                                                      Detaching an Encrypted EVS Disk

                                                      Before you detach a disk encrypted by a CMK, check whether the CMK is disabled or scheduled for deletion.

                                                      +
                                                      • If the CMK is available, the disk can be detached and re-attached, and data on the disk will not be lost.
                                                      • If the CMK is unavailable, the disk can still be used, but there is no guarantee for how long it will be usable. If the disk is detached, it will be impossible to re-attach it later. In this case, do not detach the disk without a working CMK.
                                                      +

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

                                                      +

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

                                                      diff --git a/docs/evs/umn/evs_01_0010.html b/docs/evs/umn/evs_01_0010.html index d80c84f4c..fe13beccf 100644 --- a/docs/evs/umn/evs_01_0010.html +++ b/docs/evs/umn/evs_01_0010.html @@ -1,25 +1,48 @@

                                                      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 a shared disk to the ECSs in the same ECS group to improve service reliability.
                                                      • Shared VBD disks: The device type of a newly created shared 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 disks: Such 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 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 disks to this ECS. Otherwise, SCSI reservations may not work properly, which may put your data at risk.
                                                        +

                                                        What Is Disk Sharing?

                                                        Disk sharing allows you to create 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 provide multiple attachments, high concurrency, high performance, and high reliability. They are usually used for enterprise business-critical applications that require cluster deployment and high availability (HA). 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, including ECSs or 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.

                                                        +

                                                        A shared file system or cluster management system must be set up before you can properly use a shared disk. If you simply attach a shared disk to multiple servers, data cannot be shared between those servers and may be overwritten.

                                                        -

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

                                                        -
                                                        • The anti-affinity policy of an ECS group allows ECSs to be created on different physical servers to improve service reliability.

                                                          For details about ECS groups, see Managing ECS Groups in the Elastic Cloud Server User Guide.

                                                          -
                                                        • The SCSI reservation mechanism uses a SCSI reservation command to perform SCSI reservation operations. If an ECS sends such a command to an EVS disk, the disk is displayed as locked to other ECSs, preventing the data damage that may be caused by simultaneous read/write operations to the disk from multiple ECSs.
                                                        • ECS groups and SCSI reservations have the following relationship: A SCSI reservation on a single EVS disk cannot differentiate multiple ECSs on the same physical host. For that reason, if multiple ECSs that use the same shared EVS disk are running on the same physical host, SCSI reservations will not work properly. So you are advised to use SCSI reservations only on ECSs that are in the same ECS group, thus having a working anti-affinity policy.
                                                        +
                                                        +
                                                        Figure 1 Application scenario of shared EVS disks
                                                        +

                                                        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 shared VBD disks are needed. They can also be used for Windows MSCS and Veritas VCS clusters that require SCSI reservations.
                                                        +
                                                        +

                                                        Specifications and Performance

                                                        Shared EVS disks have the same specifications and performance as non-shared EVS disks.

                                                        +
                                                        +

                                                        How Do I Use Shared VBD and SCSI Disks?

                                                        You can create shared VBD disks or shared SCSI disks. It is recommended that you attach a shared disk to ECSs in the same ECS group to improve service reliability.
                                                        • Shared VBD disks: The device type of a newly created shared 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 disks: Such 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 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 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:

                                                          +
                                                          • The anti-affinity policy of an ECS group allows ECSs to be created on different physical servers to improve service reliability.

                                                            For details about ECS groups, see Managing ECS Groups in the Elastic Cloud Server User Guide.

                                                            +
                                                          • The SCSI reservation mechanism uses a SCSI reservation command to perform SCSI reservation operations. If an ECS sends such a command to an EVS disk, the disk is displayed as locked to other ECSs, preventing the data damage that may be caused by simultaneous reads/writes to the disk from multiple ECSs.
                                                          • ECS groups and SCSI reservations have the following relationship: A SCSI reservation on a single EVS disk cannot differentiate multiple ECSs on the same physical host. For that reason, if multiple ECSs that use the same shared EVS disk are running on the same physical host, SCSI reservations will not work properly. So you are advised to use SCSI reservations only on ECSs that are in the same ECS group, thus having a working anti-affinity policy.
                                                        -

                                                        Constraints on Shared Disks

                                                        • A shared disk can be attached to a maximum of 16 servers.
                                                        • The sharing attribute of a disk cannot be changed after the disk is created.
                                                        • Shared disks can only be used as data disks. The sharing function is not supported for system disks.
                                                        • A shared file system or cluster management system must be set up before you can properly use a shared disk. If you simply attach a shared disk to multiple servers, the sharing function will not work and data may be overwritten.
                                                        • When a shared disk is attached to multiple servers, the total performance of the disk on all servers cannot exceed the maximum allowed on a single disk.
                                                        +

                                                        Constraints on Shared Disks

                                                        • A shared disk can be attached to a maximum of 16 servers.
                                                        • The sharing attribute of a disk cannot be changed after the disk is created.
                                                        • Shared disks can only be used as data disks, not system disks.
                                                        • A shared file system or cluster management system must be set up before you can properly use a shared disk. If you simply attach a shared disk to multiple servers, data cannot be shared between those servers and may be overwritten.
                                                        • When a shared disk is attached to multiple servers, the total performance of the disk on all servers cannot exceed the maximum allowed on a single disk.
                                                        -

                                                        Attaching a Shared EVS Disk

                                                        A non-shared EVS disk can only be attached to one server, whereas a shared EVS disk can be attached to up to 16 servers.

                                                        -

                                                        For details, see Attaching a Shared Disk.

                                                        +

                                                        Attaching a Shared EVS Disk

                                                        A non-shared EVS disk can only be attached to one server, whereas a shared EVS disk can be attached to up to 16 servers.

                                                        +

                                                        For details, 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, see Deleting EVS Disks.

                                                        +

                                                        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, see Deleting an 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.

                                                        +

                                                        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.

                                                        +

                                                        Data Sharing Principles and Common Usage Mistakes

                                                        A shared EVS disk is essentially the disk that can be attached to multiple servers for use. It 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 to any space on the disk. If no data read/write rules, such as the read/write sequence and meaning, between these servers are defined, data reads and writes between these servers may conflict, or other unpredictable errors may occur.

                                                        +

                                                        Though shared disks are block storage devices that provide shared access for servers, shared disks do not have the cluster management capability. You need to deploy a cluster system to manage shared disks. Common cluster management systems include Windows MSCS, Linux RHCS, Veritas VCS, and Veritas CFS.

                                                        +
                                                        If shared EVS disks are not managed by a cluster system, the following issues may occur:
                                                        • Data inconsistency caused by read/write conflicts

                                                          When a shared EVS disk is attached to two servers (server A and server B), server A cannot recognize the disk spaces allocated to server B, vice versa. That said, a disk space allocated to server A may be already used by server B. In this case, repeated disk space allocation occurs, which leads to data errors.

                                                          +

                                                          For example, a shared EVS disk has been formatted into an ext3 file system and attached to server A and server B. Server A has written metadata into the file system in space R and space G. Then server B has written metadata into space E and space G. In this case, the data written into space G by server A will be replaced. When the metadata in space G is read, an error will occur.

                                                          +
                                                        • Data inconsistency caused by data caching

                                                          When a shared EVS disk is attached to two servers (server A and server B), the application on server A has read the data in space R and space G, then cached the data. At that time, other processes and threads on server A would then read this data directly from the cache. At the same time, if the application on server B has modified the data in space R and space G, the application on server A cannot detect this data change and still reads this data from the cache. As a result, the modified data cannot be viewed on server A.

                                                          +

                                                          For example, a shared EVS disk has been formatted into an ext3 file system and attached to server A and server B. Both servers have cached the metadata in the file system. Then server A has created a new file (file F) on the shared disk, but server B cannot detect this modification and still reads data from its cached data. As a result, file F cannot be viewed on server B.

                                                          +
                                                        +
                                                        +

                                                        Before you buy a shared EVS disk, determine its device type (VBD or SCSI) based on the applications that will use the shared disk. 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 how to use shared EVS disks, see Managing Shared EVS Disks.

                                                        +

                                                        If you simply attach a shared disk to multiple servers, data or files cannot be shared between the servers, because the shared disk does not have the cluster management capability. To share files between servers, build a shared file system or deploy a cluster management system.

                                                        +
                                                        +
                                                        +

                                                        Helpful Links

                                                        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 c47c68ef1..c197c3d7b 100644 --- a/docs/evs/umn/evs_01_0011.html +++ b/docs/evs/umn/evs_01_0011.html @@ -1,18 +1,22 @@ -

                                                        Deleting a Snapshot

                                                        -

                                                        Scenarios

                                                        If a snapshot is no longer needed, you can delete it to release the virtual resources.

                                                        +

                                                        Deleting an EVS Snapshot

                                                        +

                                                        Scenarios

                                                        If you no longer require certain snapshots or the snapshot quantity reaches the maximum allowed, you can delete the snapshots.

                                                        -

                                                        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.
                                                        • A snapshot whose name starts with autobk_snapshot_vbs_, manualbk_snapshot_vbs_, autobk_snapshot_csbs_, or manualbk_snapshot_csbs_ is automatically generated during backup. You can only view details of such snapshots and cannot delete them.
                                                        +

                                                        Prerequisites

                                                        • The snapshot status must be Available or Error.
                                                        -

                                                        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 disappears from the snapshot list, the snapshot is deleted successfully.

                                                          +

                                                          Notes and Constraints

                                                          • If a snapshot is deleted, disks rolled back or created from this snapshot are not affected.
                                                          +
                                                          • If a snapshot's source disk is deleted, all legacy snapshots of this disk are also deleted.
                                                          • If you reinstall or change the server OS, snapshots of the system disk are automatically deleted. Those of the data disks can be used as usual.
                                                          +
                                                          +

                                                          Procedure

                                                          1. Log in to the console.
                                                          2. Click in the upper left corner and select the desired region and project.
                                                          3. Click in the upper left corner and choose Storage > Elastic Volume Service.

                                                            The Elastic Volume Service page is displayed.

                                                            +

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

                                                            The Snapshots page is displayed.

                                                            +

                                                          5. In the snapshot list, locate the target snapshot and click Delete in the Operation column.
                                                          6. In the displayed dialog box, confirm the information and click Yes.

                                                            If the snapshot disappears from 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 107dfbc6d..b446c3e90 100644 --- a/docs/evs/umn/evs_01_0012.html +++ b/docs/evs/umn/evs_01_0012.html @@ -1,18 +1,19 @@ -

                                                        Rolling Back Data from a Snapshot

                                                        -

                                                        Scenarios

                                                        If data on an EVS disk is incorrect or damaged, you can roll back data from a snapshot to the source disk.

                                                        +

                                                        Rolling Back Disk Data from a Snapshot

                                                        +

                                                        Scenarios

                                                        If data on an EVS disk is incorrect or damaged, you can roll back data from a snapshot to the source disk.

                                                        -

                                                        Constraints

                                                        • Data of a snapshot can be rolled back only to its source disk. Rollback to another disk is not possible.
                                                        • Data of a snapshot can be rolled back only when the snapshot status is Available and its source disk status is Available (not attached to any server) or Rollback failed. If the source disk is attached, detach the disk first.
                                                        • A snapshot whose name starts with autobk_snapshot_vbs_, manualbk_snapshot_vbs_, autobk_snapshot_csbs_, or manualbk_snapshot_csbs_ is automatically generated during backup. Such a snapshot can only be viewed. It cannot be used to roll back the disk data.
                                                        • Spot instances do not support snapshot-based rollback of the disk data.
                                                        +

                                                        Notes and Constraints

                                                        • Snapshot data can only be rolled back to source EVS disks. Rollback to a different disk is not possible.
                                                        • You can only roll back disk data from a snapshot when the source disk status is Available (not attached to any server) or Rollback failed. If the source disk is attached, detach the disk first.
                                                        • If a snapshot is being created, it cannot be used to roll back disk data.
                                                        -

                                                        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.

                                                          The snapshot list is displayed. After the snapshot status changes from Rolling back to Available, the data rollback is successful.

                                                          +

                                                          Rolling Back Disk Data from a Snapshot

                                                          1. Log in to the console.
                                                          2. Click in the upper left corner and select the desired region and project.
                                                          3. Click in the upper left corner and choose Storage > Elastic Volume Service.

                                                            The Elastic Volume Service page is displayed.

                                                            +

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

                                                            The Snapshots page is displayed.

                                                            +

                                                          5. In the snapshot list, locate the target snapshot and click Roll Back Disk in the Operation column.
                                                          6. In the displayed dialog box, click Yes.

                                                            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 8f66a2da3..853ba6282 100644 --- a/docs/evs/umn/evs_01_0013.html +++ b/docs/evs/umn/evs_01_0013.html @@ -1,21 +1,21 @@ -

                                                        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.

                                                        +

                                                        Creating a Disk from a Snapshot

                                                        +

                                                        Scenarios

                                                        This section describes how to create an EVS disk on the Snapshots page. 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 Creating an EVS Disk.

                                                        -

                                                        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.
                                                        • Batch disk creation is not possible, and the quantity parameter must be set to 1.
                                                        • The AZ of the disk is the same as that of the snapshot's source disk and cannot be changed.
                                                        • A snapshot whose name starts with autobk_snapshot_vbs_, manualbk_snapshot_vbs_, autobk_snapshot_csbs_, or manualbk_snapshot_csbs_ is automatically generated during backup. Such a snapshot can only be viewed. It cannot be used to create new disks.
                                                        +

                                                        Notes and Constraints

                                                        • Batch disk creation from a snapshot is not supported.
                                                        • A disk created from a snapshot has the same device type (SCSI or VBD), encryption attribute, AZ, region, and disk type as the snapshot's source disk.
                                                        • A snapshot whose name starts with autobk_snapshot_vbs_, manualbk_snapshot_vbs_, autobk_snapshot_csbs_, or manualbk_snapshot_csbs_ is automatically generated during backup. Such a snapshot can only be viewed. It cannot be used to create new disks.
                                                        -

                                                        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. Configure the 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 GiB, the default capacity 10 GiB will be used as the disk capacity; if the snapshot size is greater than 10 GiB, the snapshot size will be used as the disk capacity.

                                                          +

                                                          Creating an EVS Disk from a Snapshot

                                                          1. Log in to the console.
                                                          2. Click in the upper left corner and select the desired region and project.
                                                          3. Click in the upper left corner and choose Storage > Elastic Volume Service.

                                                            The Elastic Volume Service page is displayed.

                                                            +

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

                                                            The Snapshots page is displayed.

                                                            +

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

                                                            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 a 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 snapshot size will be used as the disk capacity.

                                                            -

                                                          7. Click Create Now.
                                                          8. In the disk list, view the disk status.

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

                                                            +

                                                          9. Click Create Now.
                                                          10. Confirm the configuration and click Submit.
                                                          11. In the disk list, view the disk status.

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

                                                          diff --git a/docs/evs/umn/evs_01_0014.html b/docs/evs/umn/evs_01_0014.html index ef0774d4c..eaea08aca 100644 --- a/docs/evs/umn/evs_01_0014.html +++ b/docs/evs/umn/evs_01_0014.html @@ -1,23 +1,27 @@

                                                          Adding a Tag

                                                          -

                                                          Scenarios

                                                          You can add a tag for an existing EVS disk. You can also add tags during the disk creation. For details, see Create an EVS Disk.

                                                          +

                                                          Scenarios

                                                          You can add a tag for an existing EVS disk. You can also add tags when creating a disk. For details, see Creating an EVS Disk.

                                                          -
                                                          • 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 (_).
                                                              -
                                                            • Value:
                                                              • Can contain a maximum of 43 characters.
                                                              • Can contain only digits, letters, hyphens (-), and underscores (_).
                                                              +

                                                              Tag Rules

                                                              A tag consists of a tag key and a tag value. Tag rules are described as follows: (Tag rules vary depending on regions. See the rules displayed on the console.)

                                                              +
                                                              • First set of rules:
                                                                • A tag key can contain a maximum of 36 characters. It can contain only letters, digits, special characters (.-_), and Unicode characters.
                                                                • A tag value can contain a maximum of 43 characters. It can contain only letters, digits, special characters (.-_), and Unicode characters.
                                                                +
                                                              • Second set of rules:
                                                                • A tag key can contain a maximum of 36 characters. It cannot contain special characters (=*<>\\,|/) or start or end with spaces.
                                                                • A tag value can contain a maximum of 43 characters. It cannot contain special characters (=*<>\\,|/) or start or end with spaces.
                                                                +
                                                              • Third set of rules:
                                                                • A tag key can contain a maximum of 128 characters. It cannot contain special characters (*<>\\/,|), start with _sys_, or start or end with spaces.
                                                                • A tag value can contain a maximum of 255 characters. It cannot contain special characters (*<>\\,|) or start or end with spaces.
                                                              -
                                                            • 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 desired disk and click the disk name.

                                                              The disk details page is displayed.

                                                              -

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

                                                              The Add Tag page is displayed.

                                                              -

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

                                                              +
                                                            +

                                                            Notes and Constraints

                                                            • A maximum of 10 tags can be added for an EVS disk.
                                                            • Tag keys of the same EVS disk must be unique.
                                                            +
                                                            +

                                                            Procedure

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

                                                              The Elastic Volume Service 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. Click Add Tag.

                                                              The Add Tag page is displayed.

                                                              +

                                                            7. 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 a11ccb35a..fe3eab68f 100644 --- a/docs/evs/umn/evs_01_0015.html +++ b/docs/evs/umn/evs_01_0015.html @@ -1,18 +1,26 @@

                                                          Modifying a Tag

                                                          -

                                                          Scenarios

                                                          You can change the value of a tag for an existing disk, but cannot change the key of 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 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.

                                                            +

                                                            Tag Rules

                                                            A tag consists of a tag key and a tag value. Tag rules are described as follows: (Tag rules vary depending on regions. See the rules displayed on the console.)

                                                            +
                                                            • First set of rules:
                                                              • A tag key can contain a maximum of 36 characters. It can contain only letters, digits, special characters (.-_), and Unicode characters.
                                                              • A tag value can contain a maximum of 43 characters. It can contain only letters, digits, special characters (.-_), and Unicode characters.
                                                              +
                                                            • Second set of rules:
                                                              • A tag key can contain a maximum of 36 characters. It cannot contain special characters (=*<>\\,|/) or start or end with spaces.
                                                              • A tag value can contain a maximum of 43 characters. It cannot contain special characters (=*<>\\,|/) or start or end with spaces.
                                                              +
                                                            • Third set of rules:
                                                              • A tag key can contain a maximum of 128 characters. It cannot contain special characters (*<>\\/,|), start with _sys_, or start or end with spaces.
                                                              • A tag value can contain a maximum of 255 characters. It cannot contain special characters (*<>\\,|) or start or end with spaces.
                                                              +
                                                            +
                                                            +

                                                            Notes and Constraints

                                                            • A maximum of 10 tags can be added for an EVS disk.
                                                            • Tag keys of the same EVS disk must be unique.
                                                            +
                                                            +

                                                            Procedure

                                                            1. Log in to the console.
                                                            2. Click in the upper left corner and select the desired region and project.
                                                            3. Choose Storage > Elastic Volume Service.

                                                              The Elastic Volume Service 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 204b169f1..0b8613c23 100644 --- a/docs/evs/umn/evs_01_0016.html +++ b/docs/evs/umn/evs_01_0016.html @@ -1,18 +1,18 @@

                                                          Deleting a Tag

                                                          -

                                                          Scenarios

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

                                                          +

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

                                                            The tag is deleted if it disappears from the tag list.

                                                            +

                                                            Procedure

                                                            1. Log in to the console.
                                                            2. Click in the upper left corner and select the desired region and project.
                                                            3. Click in the upper left corner and choose Storage > Elastic Volume Service.

                                                              The Elastic Volume Service 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.

                                                              The tag is deleted if it disappears from the tag list.

                                                          diff --git a/docs/evs/umn/evs_01_0018.html b/docs/evs/umn/evs_01_0018.html index 718024426..f275b0286 100644 --- a/docs/evs/umn/evs_01_0018.html +++ b/docs/evs/umn/evs_01_0018.html @@ -1,19 +1,22 @@

                                                          Extending Partitions and File Systems for SCSI Disks (Linux)

                                                          -

                                                          Scenarios

                                                          After a disk is 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 with the server OS. This section is used for reference only. For detailed operations and differences, see the corresponding OS documents. +

                                                          Scenarios

                                                          After a disk is 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 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. Incorrect operations may lead to data loss or exceptions. So 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.

                                                          +

                                                          Incorrect operations may lead to data loss or exceptions. So you are advised to back up the disk data using CBR or snapshots before expansion. For details about using CBR, see Managing EVS Disk Backups. For details about using snapshots, see Creating an EVS Snapshot.

                                                          -

                                                          Prerequisites

                                                          • You have expanded the disk capacity and attached the disk to a server on the management console. For details, see Expanding Capacity for an In-use EVS Disk or Expanding Capacity for an Available EVS Disk.
                                                          • 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.
                                                            +

                                                            Notes and Constraints

                                                            • The additional space of a data disk cannot be added to the root partition. To extend the root partition, expand the system disk instead.
                                                            • During an expansion, the additional space is added to the end of the disk. If the disk has multiple partitions, the additional space can only be allocated to the partition at the disk end.
                                                            • If a disk uses MBR, the storage space in excess of 2 TiB cannot be used because the maximum capacity that MBR supports is 2 TiB. If your disk already uses MBR for partitioning and you require more than 2 TiB after the capacity expansion, do as follows:
                                                              • (Recommended) Create a new EVS disk and use GPT.
                                                              • Back up the disk data, perform the expansion, and then change the partition style from MBR to GPT. During this change, services will be interrupted and data on the disk will be erased.
                                                            -

                                                            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
                                                              +

                                                              Prerequisites

                                                              +
                                                              +

                                                              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
                                                                 
                                                                 Disk /dev/vda: 42.9 GiB, 42949672960 bytes, 83886080 sectors
                                                                 Units = sectors of 1 * 512 = 512 bytes
                                                                @@ -35,23 +38,23 @@ Disk identifier: 0x915ffe6a
                                                                    Device Boot      Start         End      Blocks   Id  System
                                                                 /dev/sda1            2048   104857599    52427776   83  Linux
                                                                -
                                                                View the /dev/sda capacity and check whether the additional space is included.
                                                                • If the additional space is not included, refresh the capacity according to 2.
                                                                • If the additional space is included, go to 3.
                                                                +
                                                                View the /dev/sda capacity and check whether the additional space is included.
                                                                • If the additional space is not included, refresh the capacity according to 2.
                                                                • If the additional space is included, go to 3.
                                                                -

                                                              2. (Optional) Run the following command to update the capacity of the SCSI data disk:

                                                                1. Run the following command to update the disk capacity on the server:

                                                                  echo 1 > /sys/class/scsi_device/%d:%d:%d:%d/device/rescan &

                                                                  -

                                                                  In the command, %d:%d:%d:%d indicates a folder in the /sys/class/scsi_device/ directory and can be obtained using ll /sys/class/scsi_device/.

                                                                  -
                                                                  Information similar to the following is displayed: (2:0:0:0 indicates the folder to be obtained.)
                                                                  cs-xen-02:/sys/class/scsi_device # ll /sys/class/scsi_device/
                                                                  +

                                                                2. (Optional) Run the following command to update the capacity of the SCSI data disk:

                                                                  1. Run the following command to update the disk capacity on the server:

                                                                    echo 1 > /sys/class/scsi_device/%d:%d:%d:%d/device/rescan &

                                                                    +

                                                                    In the command, %d:%d:%d:%d indicates a folder in the /sys/class/scsi_device/ directory and can be obtained using ll /sys/class/scsi_device/.

                                                                    +
                                                                    Information similar to the following is displayed: (2:0:0:0 indicates the folder to be obtained.)
                                                                    cs-xen-02:/sys/class/scsi_device # ll /sys/class/scsi_device/
                                                                     total 0
                                                                     lrwxrwxrwx 1 root root 0 Sep 26 11:37 2:0:0:0 -> ../../devices/xen/vscsi-2064/host2/target2:0:0/2:0:0:0/scsi_device/2:0:0:0
                                                                    -

                                                                    In this example, run the following command:

                                                                    -

                                                                    echo 1 > /sys/class/scsi_device/2:0:0:0/device/rescan &

                                                                    -
                                                                  2. After the disk capacity is updated, run the following command to view the disk partition information again:

                                                                    fdisk -l

                                                                    -

                                                                    If the additional space is included, go to 3.

                                                                    +

                                                                    In this example, run the following command:

                                                                    +

                                                                    echo 1 > /sys/class/scsi_device/2:0:0:0/device/rescan &

                                                                    +
                                                                  3. After the disk capacity is updated, run the following command to view the disk partition information again:

                                                                    fdisk -l

                                                                    +

                                                                    If the additional space is included, go to 3.

                                                                  -

                                                                3. Run the following command to enter fdisk:

                                                                  fdisk Disk

                                                                  -

                                                                  In this example, run the following command:

                                                                  -

                                                                  fdisk /dev/sda

                                                                  -
                                                                  Information similar to the following is displayed:
                                                                  [root@ecs-scsi ~]# fdisk /dev/sda
                                                                  +

                                                                4. Run the following command to enter fdisk:

                                                                  fdisk Disk

                                                                  +

                                                                  In this example, run the following command:

                                                                  +

                                                                  fdisk /dev/sda

                                                                  +
                                                                  Information similar to the following is displayed:
                                                                  [root@ecs-scsi ~]# fdisk /dev/sda
                                                                   Welcome to fdisk (util-linux 2.23.2).
                                                                   
                                                                   Changes will remain in memory only, until you decide to write them.
                                                                  @@ -60,39 +63,39 @@ Be careful before using the write command.
                                                                   
                                                                   Command (m for help):
                                                                  -

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

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

                                                                6. 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 (1 primary, 0 extended, 3 free)
                                                                      e   extended
                                                                   Select (default p):
                                                                  -
                                                                  There are two types of disk partitions:
                                                                  • Choosing p creates a primary partition.
                                                                  • Choosing e creates an extended partition.
                                                                  -

                                                                  If MBR is used, a maximum of four primary partitions, or three primary partitions plus one extended partition can be created. The extended partition must be divided into logical partitions before use.

                                                                  -

                                                                  Disk partitions created using GPT are not categorized.

                                                                  +
                                                                  There are two types of disk partitions:
                                                                  • Choosing p creates a primary partition.
                                                                  • Choosing e creates an extended partition.
                                                                  +

                                                                  If MBR is used, a maximum of four primary partitions, or three primary partitions plus one extended partition can be created. The extended partition must be divided into logical partitions before use.

                                                                  +

                                                                  Disk partitions created using GPT are not categorized.

                                                                  -

                                                                7. In this example, a primary partition is created. Therefore, enter p and press Enter to create a primary partition.

                                                                  Information similar to the following is displayed:
                                                                  Select (default p): p
                                                                  +

                                                                8. In this example, a primary partition is created. Therefore, enter p and press Enter to create a primary partition.

                                                                  Information similar to the following is displayed:
                                                                  Select (default p): p
                                                                   Partition number (2-4, default 2):
                                                                  -

                                                                  Partition number indicates the serial number of the primary partition. Because partition number 1 has been used, the value ranges from 2 to 4.

                                                                  -

                                                                9. Enter the serial number of the primary partition and press Enter. Partition number 2 is used in this example. Therefore, enter 2 and press Enter.

                                                                  Information similar to the following is displayed:
                                                                  Partition number (2-4, default 2): 2
                                                                  +

                                                                  Partition number indicates the serial number of the primary partition. Because partition number 1 has been used, the value ranges from 2 to 4.

                                                                  +

                                                                10. Enter the serial number of the primary partition and press Enter. Partition number 2 is used in this example. Therefore, enter 2 and press Enter.

                                                                  Information similar to the following is displayed:
                                                                  Partition number (2-4, default 2): 2
                                                                   First sector (104857600-209715199, default 104857600):
                                                                  -

                                                                  First sector indicates the start sector. The value ranges from 104857600 to 209715199, and the default value is 104857600.

                                                                  -

                                                                11. Enter the new partition's start sector and press Enter. In this example, the default start sector is used.

                                                                  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:
                                                                  First sector (104857600-209715199, default 104857600):
                                                                  +

                                                                  First sector indicates the start sector. The value ranges from 104857600 to 209715199, and the default value is 104857600.

                                                                  +

                                                                12. Enter the new partition's start sector and press Enter. In this example, the default start sector is used.

                                                                  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:
                                                                  First sector (104857600-209715199, default 104857600):
                                                                   Using default value 104857600
                                                                   Last sector, +sectors or +size{K,M,G} (104857600-209715199, default 209715199):
                                                                  -

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

                                                                  -

                                                                13. Enter the new partition's end sector and press Enter. In this example, the default end sector is used.

                                                                  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} (104857600-209715199, default 209715199):
                                                                  +

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

                                                                  +

                                                                14. Enter the new partition's end sector and press Enter. In this example, the default end sector is used.

                                                                  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} (104857600-209715199, default 209715199):
                                                                   Using default value 209715199
                                                                   Partition 2 of type Linux and of size 50 GiB is set
                                                                   
                                                                   Command (m for help):
                                                                  -

                                                                15. Enter p and press Enter to view the new partition.

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

                                                                16. Enter p and press Enter to view the new partition.

                                                                  Information similar to the following is displayed:
                                                                  Command (m for help): p
                                                                   
                                                                   Disk /dev/sda: 107.4 GiB, 107374182400 bytes, 209715200 sectors
                                                                   Units = sectors of 1 * 512 = 512 bytes
                                                                  @@ -107,7 +110,7 @@ Disk identifier: 0x915ffe6a
                                                                   
                                                                   Command (m for help):
                                                                  -

                                                                17. Enter w and press Enter to write the changes to the partition table.

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

                                                                18. Enter w and press Enter to write the changes to the partition table.

                                                                  Information similar to the following is displayed:
                                                                  Command (m for help): w
                                                                   The partition table has been altered!
                                                                   
                                                                   Calling ioctl() to re-read partition table.
                                                                  @@ -117,12 +120,12 @@ The kernel still uses the old table. The new table will be used at
                                                                   the next reboot or after you run partprobe(8) or kpartx(8)
                                                                   Syncing disks.
                                                                  -

                                                                  In case that you want to discard the changes made before, you can exit fdisk by entering q.

                                                                  +

                                                                  In case that you want to discard the changes made before, you can exit fdisk by entering q.

                                                                  -

                                                                19. Run the following command to synchronize the new partition table to the OS:

                                                                  partprobe

                                                                  -

                                                                20. Run the following command to set the file system format for the new partition:

                                                                  mkfs -t File system Disk partition

                                                                  -
                                                                  • Sample command of the ext* file system:

                                                                    mkfs -t ext4 /dev/sda2

                                                                    -
                                                                    Information similar to the following is displayed:
                                                                    [root@ecs-scsi ~]# mkfs -t ext4 /dev/sda2
                                                                    +

                                                                  • Run the following command to synchronize the new partition table to the OS:

                                                                    partprobe

                                                                    +

                                                                  • Run the following command to set the file system format for the new partition:

                                                                    mkfs -t File system Disk partition

                                                                    +
                                                                    • Sample command of the ext* file system:

                                                                      mkfs -t ext4 /dev/sda2

                                                                      +
                                                                      Information similar to the following is displayed:
                                                                      [root@ecs-scsi ~]# mkfs -t ext4 /dev/sda2
                                                                       mke2fs 1.42.9 (28-Dec-2013)
                                                                       Filesystem label=
                                                                       OS type: Linux
                                                                      @@ -146,9 +149,9 @@ Creating journal (32768 blocks): done
                                                                       Writing superblocks and filesystem accounting information: done
                                                                    -
                                                                    • Sample command of the xfs file system:

                                                                      mkfs -t xfs /dev/sda2

                                                                      -

                                                                      Information similar to the following is displayed:

                                                                      -
                                                                      [root@ecs-scsi ~]# mkfs -t xfs /dev/sda2
                                                                      +
                                                                      • Sample command of the xfs file system:

                                                                        mkfs -t xfs /dev/sda2

                                                                        +

                                                                        Information similar to the following is displayed:

                                                                        +
                                                                        [root@ecs-scsi ~]# mkfs -t xfs /dev/sda2
                                                                         meta-data=/dev/sda2              isize=512     agcount=4, agsize=3276800 blks
                                                                                  =                       sectsz=512    attr=2, projid32bit=1
                                                                                  =                       crc=1         finobt=0, sparse=0
                                                                        @@ -159,18 +162,18 @@ log      =internal log           bsize=4096    blocks=6400, version=2
                                                                                  =                       sectsz=512    sunit=0 blks, lazy-count=1
                                                                         realtime =none                   extsz=4096    blocks=0, rtextents=0
                                                                      -

                                                                      The formatting takes a while, and you need to observe the system running status. Once done is displayed in the command output, the formatting is complete.

                                                                      -

                                                                    • (Optional) Run the following command to create a mount point:

                                                                      Perform this step if you want to mount the partition on a new mount point.

                                                                      -

                                                                      mkdir Mount point

                                                                      -

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

                                                                      -

                                                                      mkdir /mnt/test

                                                                      -

                                                                    • Run the following command to mount the new partition:

                                                                      mount Disk partition Mount point

                                                                      -

                                                                      In this example, run the following command to mount the new 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.

                                                                      +

                                                                      The formatting takes a while, and you need to observe the system running status. Once done is displayed in the command output, the formatting is complete.

                                                                      +

                                                                    • (Optional) Run the following command to create a mount point:

                                                                      Perform this step if you want to mount the partition on a new mount point.

                                                                      +

                                                                      mkdir Mount point

                                                                      +

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

                                                                      +

                                                                      mkdir /mnt/test

                                                                      +

                                                                    • Run the following command to mount the new partition:

                                                                      mount Disk partition Mount point

                                                                      +

                                                                      In this example, run the following command to mount the new 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.

                                                                      -

                                                                    • Run the following command to view the mount result:

                                                                      df -TH

                                                                      -
                                                                      Information similar to the following is displayed:
                                                                      [root@ecs-scsi ~]# df -TH
                                                                      +

                                                                    • Run the following command to view the mount result:

                                                                      df -TH

                                                                      +
                                                                      Information similar to the following is displayed:
                                                                      [root@ecs-scsi ~]# df -TH
                                                                       Filesystem     Type      Size  Used Avail Use% Mounted on
                                                                       /dev/vda1      ext4       43G  2.0G   39G   5% /
                                                                       devtmpfs       devtmpfs  509M     0  509M   0% /dev
                                                                      @@ -180,17 +183,17 @@ tmpfs          tmpfs     520M     0  520M   0% /sys/fs/cgroup
                                                                       tmpfs          tmpfs     104M     0  104M   0% /run/user/0
                                                                       /dev/sda1      ext4       53G   55M   50G   1% /mnt/sdc
                                                                       /dev/sda2      ext4       53G   55M   50G   1% /mnt/test
                                                                      -

                                                                      If the server is restarted, the mounting will become invalid. You can modify the /etc/fstab file to configure automount at startup. For details, see Configuring Automatic Mounting at System Start.

                                                                      +

                                                                      If the server is restarted, the mounting will become invalid. You can modify the /etc/fstab file to configure automount at startup. For details, see Configuring Automatic Mounting at System Start.

                                                              -

                                                              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.

                                                              +

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

                                                                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
                                                                   
                                                                   Disk /dev/vda: 42.9 GiB, 42949672960 bytes, 83886080 sectors
                                                                   Units = sectors of 1 * 512 = 512 bytes
                                                                  @@ -213,27 +216,27 @@ Disk identifier: 0x915ffe6a
                                                                   /dev/sda1            2048   104857599    52427776   83  Linux
                                                                   /dev/sda2       104857600   209715199    52428800   83  Linux
                                                                  -

                                                                  In the command output, take note of the partition's start and end sectors. In this example, /dev/sda2's start sector is 104857600, and its end sector is 209715199.

                                                                  -
                                                                  View the /dev/sda capacity and check whether the additional space is included.
                                                                  • If the additional space is not included, refresh the capacity according to 2.
                                                                  • If the additional space is included, take note of the start and end sectors of the target partition and then go to 3. These values will be used in the subsequent operations.
                                                                  +

                                                                  In the command output, take note of the partition's start and end sectors. In this example, /dev/sda2's start sector is 104857600, and its end sector is 209715199.

                                                                  +
                                                                  View the /dev/sda capacity and check whether the additional space is included.
                                                                  • If the additional space is not included, refresh the capacity according to 2.
                                                                  • If the additional space is included, take note of the start and end sectors of the target partition and then go to 3. These values will be used in the subsequent operations.
                                                                  -

                                                                2. (Optional) Run the following command to update the capacity of the SCSI data disk:

                                                                  1. Run the following command to update the disk capacity on the server:

                                                                    echo 1 > /sys/class/scsi_device/%d:%d:%d:%d/device/rescan &

                                                                    -

                                                                    In the command, %d:%d:%d:%d indicates a folder in the /sys/class/scsi_device/ directory and can be obtained using ll /sys/class/scsi_device/.

                                                                    -
                                                                    Information similar to the following is displayed: (2:0:0:0 indicates the folder to be obtained.)
                                                                    cs-xen-02:/sys/class/scsi_device # ll /sys/class/scsi_device/
                                                                    +

                                                                  2. (Optional) Run the following command to update the capacity of the SCSI data disk:

                                                                    1. Run the following command to update the disk capacity on the server:

                                                                      echo 1 > /sys/class/scsi_device/%d:%d:%d:%d/device/rescan &

                                                                      +

                                                                      In the command, %d:%d:%d:%d indicates a folder in the /sys/class/scsi_device/ directory and can be obtained using ll /sys/class/scsi_device/.

                                                                      +
                                                                      Information similar to the following is displayed: (2:0:0:0 indicates the folder to be obtained.)
                                                                      cs-xen-02:/sys/class/scsi_device # ll /sys/class/scsi_device/
                                                                       total 0
                                                                       lrwxrwxrwx 1 root root 0 Sep 26 11:37 2:0:0:0 -> ../../devices/xen/vscsi-2064/host2/target2:0:0/2:0:0:0/scsi_device/2:0:0:0
                                                                      -

                                                                      In this example, run the following command:

                                                                      -

                                                                      echo 1 > /sys/class/scsi_device/2:0:0:0/device/rescan &

                                                                      -
                                                                    2. After the disk capacity is updated, run the following command to view the disk partition information again:

                                                                      fdisk -l

                                                                      -

                                                                      If the additional space is included, take note of the start and end sectors of the target partition and then go to 3. These values will be used in the subsequent operations.

                                                                      +

                                                                      In this example, run the following command:

                                                                      +

                                                                      echo 1 > /sys/class/scsi_device/2:0:0:0/device/rescan &

                                                                      +
                                                                    3. After the disk capacity is updated, run the following command to view the disk partition information again:

                                                                      fdisk -l

                                                                      +

                                                                      If the additional space is included, take note of the start and end sectors of the target partition and then go to 3. These values will be used in the subsequent operations.

                                                                    -

                                                                  3. Run the following command to unmount the partition:

                                                                    umount Disk partition

                                                                    -

                                                                    In this example, run the following command:

                                                                    -

                                                                    umount /dev/sda2

                                                                    -

                                                                  4. Run the following command to enter fdisk:

                                                                    fdisk Disk

                                                                    -

                                                                    In this example, run the following command:

                                                                    -

                                                                    fdisk /dev/sda

                                                                    -
                                                                    Information similar to the following is displayed:
                                                                    [root@ecs-scsi ~]# fdisk /dev/sda
                                                                    +

                                                                  5. Run the following command to unmount the partition:

                                                                    umount Disk partition

                                                                    +

                                                                    In this example, run the following command:

                                                                    +

                                                                    umount /dev/sda2

                                                                    +

                                                                  6. Run the following command to enter fdisk:

                                                                    fdisk Disk

                                                                    +

                                                                    In this example, run the following command:

                                                                    +

                                                                    fdisk /dev/sda

                                                                    +
                                                                    Information similar to the following is displayed:
                                                                    [root@ecs-scsi ~]# fdisk /dev/sda
                                                                     Welcome to fdisk (util-linux 2.23.2).
                                                                     
                                                                     Changes will remain in memory only, until you decide to write them.
                                                                    @@ -242,53 +245,53 @@ Be careful before using the write command.
                                                                     
                                                                     Command (m for help):
                                                                    -

                                                                  7. Run the following command to delete the partition to be extended:

                                                                    1. Enter d and press Enter to delete the partition.
                                                                      Information similar to the following is displayed:
                                                                      Command (m for help): d
                                                                      +

                                                                    2. Run the following command to delete the partition to be extended:

                                                                      1. Enter d and press Enter to delete the partition.
                                                                        Information similar to the following is displayed:
                                                                        Command (m for help): d
                                                                         Partition number (1,2, default 2):
                                                                        -
                                                                      2. Enter the partition number and press Enter to delete the partition. In this example, enter 2.
                                                                        Information similar to the following is displayed:
                                                                        Partition number (1,2, default 2): 2
                                                                        +
                                                                      3. Enter the partition number and press Enter to delete the partition. In this example, enter 2.
                                                                        Information similar to the following is displayed:
                                                                        Partition number (1,2, default 2): 2
                                                                         Partition 2 is deleted
                                                                         
                                                                         Command (m for help): 
                                                                        -

                                                                        After deleting the partition, re-create the partition according to the following steps, and data on this disk will not be lost.

                                                                        +

                                                                        After deleting the partition, re-create the partition according to the following steps, and data on this disk will not be lost.

                                                                      -

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

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

                                                                    4. 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 (1 primary, 0 extended, 3 free)
                                                                          e   extended
                                                                       Select (default p): 
                                                                      -
                                                                      There are two types of disk partitions:
                                                                      • Choosing p creates a primary partition.
                                                                      • Choosing e creates an extended partition.
                                                                      -

                                                                      If MBR is used, a maximum of four primary partitions, or three primary partitions plus one extended partition can be created. The extended partition must be divided into logical partitions before use.

                                                                      -

                                                                      Disk partitions created using GPT are not categorized.

                                                                      +
                                                                      There are two types of disk partitions:
                                                                      • Choosing p creates a primary partition.
                                                                      • Choosing e creates an extended partition.
                                                                      +

                                                                      If MBR is used, a maximum of four primary partitions, or three primary partitions plus one extended partition can be created. The extended partition must be divided into logical partitions before use.

                                                                      +

                                                                      Disk partitions created using GPT are not categorized.

                                                                      -

                                                                    5. Ensure that the entered partition type is the same as the partition had before. In this example, a primary partition is used. Therefore, enter p and press Enter to create a primary partition.

                                                                      Information similar to the following is displayed:
                                                                      Select (default p): p
                                                                      +

                                                                    6. Ensure that the entered partition type is the same as the partition had before. In this example, a primary partition is used. Therefore, enter p and press Enter to create a primary partition.

                                                                      Information similar to the following is displayed:
                                                                      Select (default p): p
                                                                       Partition number (2-4, default 2):
                                                                      -

                                                                      Partition number indicates the serial number of the primary partition.

                                                                      -

                                                                    7. Ensure that entered partition number is the same as the partition had before. In this example, partition number 2 is used. Therefore, enter 2 and press Enter.

                                                                      Information similar to the following is displayed:
                                                                      Partition number (2-4, default 2): 2
                                                                      +

                                                                      Partition number indicates the serial number of the primary partition.

                                                                      +

                                                                    8. Ensure that entered partition number is the same as the partition had before. In this example, partition number 2 is used. Therefore, enter 2 and press Enter.

                                                                      Information similar to the following is displayed:
                                                                      Partition number (2-4, default 2): 2
                                                                       First sector (104857600-314572799, default 104857600):
                                                                      -

                                                                      In the command output, First sector specifies the start sector.

                                                                      -
                                                                      Data will be lost if the following operations are performed:
                                                                      • Select a start sector other than the partition had before.
                                                                      • Select an end sector smaller than the partition had before.
                                                                      +

                                                                      In the command output, First sector specifies the start sector.

                                                                      +
                                                                      Data will be lost if the following operations are performed:
                                                                      • Select a start sector other than the partition had before.
                                                                      • Select an end sector smaller than the partition had before.
                                                                      -

                                                                    9. Ensure that the entered start sector is the same as the partition had before. In this example, start sector 104857600 is recorded in 1 or 2. Therefore, enter 104857600 and press Enter.

                                                                      Information similar to the following is displayed:
                                                                      First sector (104857600-314572799, default 104857600):
                                                                      +

                                                                    10. Ensure that the entered start sector is the same as the partition had before. In this example, start sector 104857600 is recorded in 1 or 2. Therefore, enter 104857600 and press Enter.

                                                                      Information similar to the following is displayed:
                                                                      First sector (104857600-314572799, default 104857600):
                                                                       Using default value 104857600
                                                                       Last sector, +sectors or +size{K,M,G} (104857600-314572799, default 314572799):
                                                                      -

                                                                      In the command output, Last sector specifies the end sector.

                                                                      -

                                                                    11. Ensure that the entered end sector is greater than or equal to the end sector recorded in 1 or 2. In this example, the recorded end sector is 209715199, and the default end sector is used. Therefore, enter 314572799 and press Enter.

                                                                      Information similar to the following is displayed:
                                                                      Last sector, +sectors or +size{K,M,G} (104857600-314572799, default 314572799):
                                                                      +

                                                                      In the command output, Last sector specifies the end sector.

                                                                      +

                                                                    12. Ensure that the entered end sector is greater than or equal to the end sector recorded in 1 or 2. In this example, the recorded end sector is 209715199, and the default end sector is used. Therefore, enter 314572799 and press Enter.

                                                                      Information similar to the following is displayed:
                                                                      Last sector, +sectors or +size{K,M,G} (104857600-314572799, default 314572799):
                                                                       Using default value 314572799
                                                                       Partition 2 of type Linux and of size 100 GiB is set
                                                                       
                                                                       Command (m for help):
                                                                      -

                                                                      The partition is created.

                                                                      -

                                                                    13. Enter p and press Enter to print the partition details.

                                                                      Information similar to the following is displayed:

                                                                      -
                                                                      Command (m for help): p
                                                                      +

                                                                      The partition is created.

                                                                      +

                                                                    14. Enter p and press Enter to print the partition details.

                                                                      Information similar to the following is displayed:

                                                                      +
                                                                      Command (m for help): p
                                                                       
                                                                       Disk /dev/sda: 161.1 GiB, 161061273600 bytes, 314572800 sectors
                                                                       Units = sectors of 1 * 512 = 512 bytes
                                                                      @@ -302,7 +305,7 @@ Disk identifier: 0x915ffe6a
                                                                       /dev/sda2       104857600   314572799    104857600  83  Linux
                                                                       
                                                                       Command (m for help):
                                                                      -

                                                                    15. Enter w and press Enter to write the changes to the partition table.

                                                                      Information similar to the following is displayed: (The partition is successfully created.)
                                                                      Command (m for help): w
                                                                      +

                                                                    16. Enter w and press Enter to write the changes to the partition table.

                                                                      Information similar to the following is displayed: (The partition is successfully created.)
                                                                      Command (m for help): w
                                                                       The partition table has been altered!
                                                                       
                                                                       Calling ioctl() to re-read partition table.
                                                                      @@ -312,13 +315,13 @@ The kernel still uses the old table. The new table will be used at
                                                                       the next reboot or after you run partprobe(8) or kpartx(8)
                                                                       Syncing disks.
                                                                      -

                                                                      In case that you want to discard the changes made before, you can exit fdisk by entering q.

                                                                      +

                                                                      In case that you want to discard the changes made before, you can exit fdisk by entering q.

                                                                      -

                                                                    17. Run the following command to synchronize the new partition table to the OS:

                                                                      partprobe

                                                                      -

                                                                    18. Perform the following operations based on the file system of the disk:

                                                                      • For the ext* file system
                                                                        1. Run the following command to check the correctness of the file system on the partition:

                                                                          e2fsck -f Disk partition

                                                                          -

                                                                          In this example, run the following command:

                                                                          -

                                                                          e2fsck -f /dev/sda2

                                                                          -
                                                                          Information similar to the following is displayed:
                                                                          [root@ecs-scsi ~]# e2fsck -f /dev/sda2
                                                                          +

                                                                        2. Run the following command to synchronize the new partition table to the OS:

                                                                          partprobe

                                                                          +

                                                                        3. Perform the following operations based on the file system of the disk:

                                                                          • For the ext* file system
                                                                            1. Run the following command to check the correctness of the file system on the partition:

                                                                              e2fsck -f Disk partition

                                                                              +

                                                                              In this example, run the following command:

                                                                              +

                                                                              e2fsck -f /dev/sda2

                                                                              +
                                                                              Information similar to the following is displayed:
                                                                              [root@ecs-scsi ~]# e2fsck -f /dev/sda2
                                                                               e2fsck 1.42.9 (28-Dec-2013)
                                                                               Pass 1: Checking inodes, blocks, and sizes
                                                                               Pass 2: Checking directory structure
                                                                              @@ -327,38 +330,38 @@ Pass 4: Checking reference counts
                                                                               Pass 5: Checking group summary information
                                                                               /dev/sda2: 11/3276800 files (0.0% non-contiguous), 251790/13107200 blocks
                                                                              -
                                                                            2. Run the following command to extend the file system of the partition:

                                                                              resize2fs Disk partition

                                                                              -

                                                                              In this example, run the following command:

                                                                              -

                                                                              resize2fs /dev/sda2

                                                                              -
                                                                              Information similar to the following is displayed:
                                                                              [root@ecs-scsi ~]# resize2fs /dev/sda2
                                                                              +
                                                                            3. Run the following command to extend the file system of the partition:

                                                                              resize2fs Disk partition

                                                                              +

                                                                              In this example, run the following command:

                                                                              +

                                                                              resize2fs /dev/sda2

                                                                              +
                                                                              Information similar to the following is displayed:
                                                                              [root@ecs-scsi ~]# resize2fs /dev/sda2
                                                                               resize2fs 1.42.9 (28-Dec-2013)
                                                                               Resizing the filesystem on /dev/sda2 to 26214400 (4k) blocks.
                                                                               The filesystem on /dev/sda2 is now 26214400 blocks long.
                                                                              -
                                                                            4. (Optional) Run the following command to create a mount point:

                                                                              Perform this step if you want to mount the partition on a new mount point.

                                                                              -

                                                                              mkdir Mount point

                                                                              -

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

                                                                              -

                                                                              mkdir /mnt/test

                                                                              -
                                                                            5. Run the following command to mount the partition:

                                                                              mount Disk partition Mount point

                                                                              -

                                                                              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.

                                                                              +
                                                                            6. (Optional) Run the following command to create a mount point:

                                                                              Perform this step if you want to mount the partition on a new mount point.

                                                                              +

                                                                              mkdir Mount point

                                                                              +

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

                                                                              +

                                                                              mkdir /mnt/test

                                                                              +
                                                                            7. Run the following command to mount the partition:

                                                                              mount Disk partition Mount point

                                                                              +

                                                                              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.

                                                                            -
                                                                          • For the xfs file system
                                                                            1. (Optional) Run the following command to create a mount point:

                                                                              Perform this step if you want to mount the partition on a new mount point.

                                                                              -

                                                                              mkdir Mount point

                                                                              -

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

                                                                              +
                                                                            3. For the xfs file system
                                                                              1. (Optional) Run the following command to create a mount point:

                                                                                Perform this step if you want to mount the partition on a new mount point.

                                                                                +

                                                                                mkdir Mount point

                                                                                +

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

                                                                                -
                                                                              3. Run the following command to extend the file system of the partition:

                                                                                sudo xfs_growfs Disk partition

                                                                                -

                                                                                In this example, run the following command:

                                                                                -

                                                                                sudo xfs_growfs /dev/sda2

                                                                                -

                                                                                Information similar to the following is displayed:

                                                                                -
                                                                                [root@ecs-scsi ~]# sudo xfs_growfs /dev/sda2
                                                                                +
                                                                              4. Run the following command to extend the file system of the partition:

                                                                                sudo xfs_growfs Disk partition

                                                                                +

                                                                                In this example, run the following command:

                                                                                +

                                                                                sudo xfs_growfs /dev/sda2

                                                                                +

                                                                                Information similar to the following is displayed:

                                                                                +
                                                                                [root@ecs-scsi ~]# sudo xfs_growfs /dev/sda2
                                                                                 meta-data=/dev/sda2              isize=512     agcount=4, agsize=3276800 blks
                                                                                          =                       sectsz=512    attr=2, projid32bit=1
                                                                                          =                       crc=1         finobt=0, spinodes=0
                                                                                @@ -371,9 +374,9 @@ realtime =none                   extsz=4096    blocks=0, rtextents=0
                                                                                 data blocks changed from 13107200 to 26214400df .
                                                                          -

                                                                        4. Run the following command to view the mount result:

                                                                          df -TH

                                                                          -

                                                                          Information similar to the following is displayed:

                                                                          -
                                                                          [root@ecs-scsi ~]# df -TH
                                                                          +

                                                                        5. Run the following command to view the mount result:

                                                                          df -TH

                                                                          +

                                                                          Information similar to the following is displayed:

                                                                          +
                                                                          [root@ecs-scsi ~]# df -TH
                                                                           Filesystem     Type      Size  Used Avail Use% Mounted on
                                                                           /dev/vda1      ext4       43G  2.0G   39G   5% /
                                                                           devtmpfs       devtmpfs  509M     0  509M   0% /dev
                                                                          @@ -385,29 +388,29 @@ tmpfs          tmpfs     104M     0  104M   0% /run/user/0
                                                                           /dev/sda2      ext4      106G   63M  101G   1% /mnt/test

                                                                -

                                                                Configuring Automatic Mounting at System Start

                                                                The fstab file controls what disks are automatically mounted at server startup. You can configure the fstab file of a server that has data. This operation will not affect the existing data.

                                                                -

                                                                The following example uses UUIDs to identify disks in the fstab file. You are advised not to use device names (like /dev/vdb1) to identify disks in the file because device names are assigned dynamically and may change (for example, from /dev/vdb1 to /dev/vdb2) after a server stop or start. This can even prevent your server from booting up.

                                                                -

                                                                UUIDs are the unique character strings for identifying partitions in Linux.

                                                                +

                                                                Configuring Automatic Mounting at System Start

                                                                The fstab file controls what disks are automatically mounted at ECS startup. You can configure the fstab file of an ECS that has data. This operation will not affect the existing data.

                                                                +

                                                                The following example uses UUIDs to identify disks in the fstab file. You are advised not to use device names (like /dev/vdb1) to identify disks in the file because device names are assigned dynamically and may change (for example, from /dev/vdb1 to /dev/vdb2) after an ECS stop or start. This can even prevent your ECS from booting up.

                                                                +

                                                                UUIDs are the unique character strings for identifying partitions in Linux.

                                                                -
                                                                1. Query the partition UUID.

                                                                  blkid Disk partition

                                                                  -

                                                                  In this example, the UUID of the /dev/vdb1 partition is queried.

                                                                  -

                                                                  blkid /dev/vdb1

                                                                  -

                                                                  Information similar to the following is displayed:

                                                                  -
                                                                  [root@ecs-test-0001 ~]# blkid /dev/vdb1
                                                                  +
                                                                  1. Query the partition UUID.

                                                                    blkid Disk partition

                                                                    +

                                                                    In this example, the UUID of the /dev/vdb1 partition is queried.

                                                                    +

                                                                    blkid /dev/vdb1

                                                                    +

                                                                    Information similar to the following is displayed:

                                                                    +
                                                                    [root@ecs-test-0001 ~]# blkid /dev/vdb1
                                                                     /dev/vdb1: UUID="0b3040e2-1367-4abb-841d-ddb0b92693df" TYPE="ext4"
                                                                    -

                                                                    Carefully record the UUID, as you will need it for the following step.

                                                                    -

                                                                  2. Open the fstab file using the vi editor.

                                                                    vi /etc/fstab

                                                                    -

                                                                  3. Press i to enter editing mode.
                                                                  4. 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
                                                                    -

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

                                                                    The system saves the configurations and exits the vi editor.

                                                                    -

                                                                  6. Verify that the disk is auto-mounted at startup.

                                                                    1. Unmount the partition.

                                                                      umount Disk partition

                                                                      -

                                                                      In this example, run the following command:

                                                                      -

                                                                      umount /dev/vdb1

                                                                      -
                                                                    2. Reload all the content in the /etc/fstab file.

                                                                      mount -a

                                                                      -
                                                                    3. 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, automatic mounting has been configured:

                                                                      -
                                                                      root@ecs-test-0001 ~]# mount | grep /mnt/sdc
                                                                      +

                                                                      Carefully record the UUID, as you will need it for the following step.

                                                                      +

                                                                    4. Open the fstab file using the vi editor.

                                                                      vi /etc/fstab

                                                                      +

                                                                    5. Press i to enter 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. Press Esc, enter :wq, and press Enter.

                                                                      The system saves the configurations and exits the vi editor.

                                                                      +

                                                                    8. Verify that the disk is auto-mounted at startup.

                                                                      1. Unmount the partition.

                                                                        umount Disk partition

                                                                        +

                                                                        In this example, run the following command:

                                                                        +

                                                                        umount /dev/vdb1

                                                                        +
                                                                      2. Reload all the content in the /etc/fstab file.

                                                                        mount -a

                                                                        +
                                                                      3. 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, 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 6c23fd50c..eca555c65 100644 --- a/docs/evs/umn/evs_01_0019.html +++ b/docs/evs/umn/evs_01_0019.html @@ -1,19 +1,16 @@

                                                                    Searching for Disks by Tag

                                                                    -

                                                                    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.

                                                                    +

                                                                    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.

                                                                      -

                                                                    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.

                                                                      You can add a maximum of 10 tags to search for disks. If you add more than one tag, only the disks containing all specified tags will be returned.

                                                                      -

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

                                                                      -

                                                                    7. After the tags are added, click Search.

                                                                      Disks owning the added tags are displayed in the list, and the search is complete.

                                                                      +

                                                                      Procedure

                                                                      1. Log in to the console.
                                                                      2. Click in the upper left corner and select the desired region and project.
                                                                      3. Click in the upper left corner and choose Storage > Elastic Volume Service.

                                                                        The Elastic Volume Service page is displayed.

                                                                        +

                                                                      4. In the search box, select Tag and then a key-value pair, and click OK.

                                                                        You can search for disks by multiple tags and they are automatically joined with AND.

                                                                    diff --git a/docs/evs/umn/evs_01_0020.html b/docs/evs/umn/evs_01_0020.html index 2a43614a9..68aae3d6d 100644 --- a/docs/evs/umn/evs_01_0020.html +++ b/docs/evs/umn/evs_01_0020.html @@ -1,17 +1,15 @@

                                                                    EVS Replication (Deprecated)

                                                                    -

                                                                    What Is EVS Replication

                                                                    If your services or disk data demands high reliability, you can use the cross-AZ replication feature provided by EVS. You can create a disaster recovery (DR) disk for a production disk in another AZ and use the production disk and DR disk to create an EVS replication pair. The data on these two disks will be consistent in real time. If a large number of physical resources in the primary AZ are faulty due to force majeure, you can use the DR disks in the secondary AZ to ensure the service availability and continuity.
                                                                    • The server with the production disk attached is referred to as the production server, and the AZ containing the production server is the primary AZ.
                                                                    • The server with the DR disk attached is referred to as the DR server, and the AZ containing the DR server is the secondary AZ.
                                                                    +

                                                                    What Is EVS Replication

                                                                    If your services or disk data demands high reliability, you can use the cross-AZ replication feature provided by EVS. You can create a disaster recovery (DR) disk for a production disk in another AZ and use the production disk and DR disk to create an EVS replication pair. The data on these two disks will be consistent in real time. If a large number of physical resources in the primary AZ are faulty due to force majeure, you can use the DR disks in the secondary AZ to ensure the service availability and continuity.
                                                                    • The server with the production disk attached is referred to as the production server, and the AZ containing the production server is the primary AZ.
                                                                    • The server with the DR disk attached is referred to as the DR server, and the AZ containing the DR server is the secondary AZ.
                                                                    -

                                                                    Application Scenarios

                                                                    The replication function helps address your following needs:
                                                                    • Data in DR disks is consistent with that in production disks in real time. You can perform a planned migration based on your service needs, that is, migrate the services from the primary AZ to the secondary AZ without data loss.
                                                                    • If large-scale physical resources in the primary AZ become faulty due to force majeure, you can use DR disks in the secondary AZ to lower the impact exerted on services.
                                                                    +

                                                                    Application Scenarios

                                                                    The replication function helps address your following needs:
                                                                    • Data in DR disks is consistent with that in production disks in real time. You can perform a planned migration based on your service needs, that is, migrate the services from the primary AZ to the secondary AZ without data loss.
                                                                    • If large-scale physical resources in the primary AZ become faulty due to force majeure, you can use DR disks in the secondary AZ to lower the impact exerted on services.
                                                                    -

                                                                    Usage Instructions

                                                                    For more use methods of EVS replication, see Managing EVS Replication (Deprecated).

                                                                    -

                                                                    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.

                                                                    +

                                                                    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.

                                                                    -