Module 4 - Storage Cloud Services - Huawei

Storage Services - Elastic Volume Service
Copyright © 2019 Huawei Technologies Co., Ltd. All rights reserved.

Foreword
 This course introduces HUAWEI CLOUD Elastic Volume Service (EVS).
Page 1 Copyright © 2019 Huawei Technologies Co., Ltd. All rights reserved.
Objectives
 Upon completion of this course, you will be able to:
 Describes HUAWEI CLOUD EVS.
 Understand the concepts, functions, and application scenarios of EVS.
 Understand how to create and manage EVS disks.
 Understand how to troubleshoot EVS frequently asked questions (FAQs).
Contents
1. Overview
2. Purchasing
3. Usage and Management
4. FAQs
5. Related Services
Concepts
 EVS offers scalable block storage for cloud servers. With high reliability,
high performance, and rich specifications, EVS disks can be used for
distributed file systems, development and test environments, data
warehouse applications, and high-performance computing (HPC) scenarios
to meet diverse service requirements.
 You can create EVS disks and attach them to servers. The method for using
EVS disks is the same as that for using traditional disks on physical servers.
Product Advantages
High
reliability
Rich High
specifications performance
EVS
Multi-
Easy to use terabyte
capacity
Product Architecture
Functions
EVS provides storage resources for servers.
 Create disks.
 Attach disks to servers.
 Detach disks.
 Expand disk capacities.
 Create backups for disks.
 Create snapshots.
 Delete disks.
 Query disks.
Application Scenarios
IOPS per Max. IOPS/EVS
Disk Type Typical Application Scenario
GB/EVS disk disk
Common I/O 2 2,200 Suitable for scenarios that feature few transactions and
require large capacity and normal read/write speed.
For example, office applications or small-scale test
environments.
High I/O 6 5,000 Suitable for mainstream scenarios that require high
performance and high reliability.
For example, large-scale development and test
environments, web server logs, and enterprise
applications. Typical enterprise applications include SAP,
Microsoft Exchange, and Microsoft SharePoint.
Ultra-high I/O 20 33,000 Suitable for read/write-intensive applications that
require ultra-high I/O and throughput, such as
distributed file systems used in the HPC scenarios or
NoSQL and relational databases used in I/O-intensive
scenarios.
Typical databases include MongoDB, Oracle, SQL Server,
MySQL, and PostgreSQL.
Billing
 EVS disks are billed based on factors, including capacity, type, and usage
duration. You can pay for EVS disks in yearly/monthly or pay-per-use
billing mode.
 EVS disk types are classified as common I/O, high I/O, and ultra-high I/O
based on I/O performance and differ in performance and price.
Contents
1. Overview
2. Purchasing
4. FAQs
5. Related Services
Operation Procedure
Key Purchasing Parameters
Parameter Mandatory Description
Billing Mode Mandatory Pay-per-use or yearly/monthly
AZ Mandatory Availability zone (AZ) where the disk belongs
Disk types are classified as common I/O, high I/O, and ultra-high I/O
Disk Type Mandatory
by I/O performance.
Capacity (GB) Mandatory Data disk: 10 GB to 32768 GB
Create from backup Optional The disk will be created from a backup.
Create from snapshot Optional The disk will be created from a snapshot.
Share Optional A shared disk can be attached to multiple servers for use.
SCSI EVS disks allow the server OS to directly access the underlying
SCSI Optional
storage media and send SCSI commands to the disks.
Encryption Optional Disk encryption is used for data disk encryption only.
Auto Backup Optional Data on the disks can be backed up according to the backup policy.
Tags can be created during disk creation to identify cloud resources
Tag Optional for purposes of easy categorization and quick search.
Disk Name Optional volume-0001

Quantity Mandatory -
Disk Type
IOPS per GB/EVS

Disk Type Max. IOPS/EVS disk Max. Throughput
disk
Common I/O 2 2,200 90 MB/s
High I/O 6 5,000 150 MB/s

Ultra-high I/O 50 33,000 350 MB/s
Device Type
 VBD is the default disk device type. VBD EVS disks support only basic SCSI
read/write 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 EVS disks also support advanced SCSI commands.
 SCSI EVS disks: BMSs support only SCSI EVS disks, which can be used as either system
disks or data disks.
 Shared SCSI EVS disks: Shared SCSI EVS disks must be used together with a distributed
file system or cluster software. Because most cluster applications, such as Windows
MSCS, Veritas VCS, and Veritas CFS, require the usage of SCSI reservations, you are
advised to use shared EVS disks with SCSI.
Disk Status
Status Description Status Description
Data is being downloaded from an
The EVS disk is attached to a server and
In-use Downloading image to the EVS disk. This status
is in use.
occurs when you create a server.
The EVS disk is successfully created and An error occurs when you try to create
Available Error
has not been attached to any server. an EVS disk.
An error occurs when you try to delete
Creating The EVS disk is being created. Deletion Failed
an EVS disk.
An error occurs when you try to expand
Attaching The EVS disk is being attached. Expansion failed
the capacity of an EVS disk.
An error occurs when you try to restore
Detaching The EVS disk is being detached. Restoration failed
an EVS disk from a backup.
Data on the EVS disk is being restored
Deleting The EVS disk is being deleted. Rolling back
from a snapshot.
A VBS backup is being used to restore An error occurs when an EVS disk is
Restoring Rollback failed
the EVS disk. being rolled back from a snapshot.
The capacity of the EVS disk is being
Expanding Awaiting transfer An EVS disk is awaiting for a transfer.
expanded.
Data on the EVS disk is being uploaded
Uploading to an image. This status occurs when - -
you create an image from a server.
Disk Status Changes
 Create a disk: Creating → Available (if the creation succeeded) or Error (if the creation failed)
 Attach a disk: Available → Attaching → In-use (if the attachment succeeded)
 Detach a disk: In-use → Detaching → Available (if the detachment succeeded)
 Expand the capacity of an Available disk: Available → Expanding → Available (if the expansion
succeeded) or Expansion failed (if the expansion failed)
 Expand the capacity of an In-use disk: In-use → Expanding → In-use (if the expansion succeeded) or
Expansion failed (if the expansion failed)
 Delete a disk: Available, Expansion failed, Error, Restoration failed, or Rollback failed → Deleting → No
longer displayed (if the deletion succeeded) or Deletion failed (if the deletion failed)
 Restore data from a backup: Available → Restoring → Available (if the restoration succeeded) or
Restoration failed (if the restoration failed)
 Roll back data from a snapshot: Available or Rollback failed → Rolling back → Available (if the rollback
succeeded) or Rollback failed (if the rollback failed)
 Transfer a disk: Available → Awaiting transfer → Available (if the transfer succeeded)
Contents
1. Overview
2. Purchasing
4. FAQs
5. Related Services
Common Functions
 Attachment
 Detachment
 Deletion
 Capacity Expansion
 Backup
 Snapshot
Attachment
 EVS disks cannot be used independently. You must attach EVS disks to servers,
and the disks can be used as data disks.
 A system disk is automatically added during server creation, and you do not need to
manually attach the system disk.
 Data disks can be created during or after server creation. If you create data disks during
server creation, the disks will be automatically attached to the server. If you create data
disks after server creation, you need to manually attach the disks to the server.
 Number of servers that a data disk can be attached to:
 A non-shared data disk: 1
 A shared data disk: 16
 Disk attachment process:
Available → Attaching → In-use (if the attachment succeeded)
Detachment
 If an EVS disk is attached to a server, the disk status is In-use. In this case, if
the operations you need to perform require the disk to be in the Available
state, detach the disk from the server. Such operations include data rollback
from a snapshot.
 Before detaching a system disk, ensure that the server using this system disk is in the
Stopped state. That said, the server must be stopped when detaching its system disk.
 A data disk can be detached when the server is in either Stopped or Running state.
 Disk detachment process:

 In-use → Detaching → Available (if the detachment succeeded)
Deletion
 If an EVS disk is no longer used, you can delete it to release virtual resources. After
a disk was deleted, it will no longer be charged.
 Before deleting an EVS disk, ensure that the disk status is Available, Error, Expansion
failed, Restoration failed, or Rollback failed.
 Before you delete a shared disk, ensure that the disk has been detached from all its
servers.
 When you delete an EVS disk, all the disk data including the snapshots created for this
disk will be deleted. Exercise caution when performing this operation.
 Disk detachment process:

Available, Expansion failed, Error, Restoration failed, or Rollback failed → Deleting → No
longer displayed (if the deletion succeeded) or Deletion failed (if the deletion failed)
Capacity Expansion
 When the storage space of an EVS disk is insufficient, you can handle the insufficiency in
either of the following ways:
 Create a new disk and attach it to a server.
 Expand the capacity of an existing disk. The capacities of both system disks and data disks can be
expanded.
 You can expand the disk capacities when the disks are in the In-use or Available state.
 Expanding an In-use disk means that the to-be-expanded disk has been attached to a server.
 Expanding an Available disk means that the to-be-expanded disk has not been attached to any
server.
 Capacity expansion process (Available disks):
Available → Expanding → Available (if the expansion succeeded) or Expansion failed (if the expansion
failed)
 Capacity expansion process (In-use disks):
In-use→ Expanding → In-use (if the expansion succeeded) or Expansion failed (if the expansion failed)
Backup
 EVS disk backups are created using the Volume Back Service (VBS) service.
 Backups can be created for EVS disks only when the disks are in the Available
or In-use state.
 With backup policies configured, data on EVS disks can be periodically backed
up to improve data security.
 When data on an EVS disk is lost, you can restore the disk data from the
backup.
 Process of data restoration from a backup:

Available → Restoring → Available (if the restoration succeeded) or Restoration
failed (if the restoration failed)
Snapshot
 You can create EVS snapshots to save the disk data at specific time points.
 If a snapshot is no longer used, you can delete it to release virtual resources.
 You can create EVS disks from snapshots.
 If the data on an EVS disk is incorrect or damaged, you can roll back the data from
a snapshot to the source disk to restore data.
 You can only roll back the snapshot to its source EVS disk. A rollback to another EVS disk
is not possible.
 A snapshot can be rolled back only when the snapshot status is Available and the sourc
e EVS disk status is Available (not attached to any server) or Rollback failed.
 Process of data rollback from a snapshot:
Available or Rollback failed → Rolling back → Available (if the rollback succeeded) or Rollb
ack failed (if the rollback failed)
Contents
1. Overview
2. Purchasing
4. FAQs
5. Related Services
FAQs
 Can I attach an EVS disk to multiple servers?
 No. An EVS disk can be attached to only one server.
 A shared EVS disk can be attached to a maximum of 16 servers.
 Will data in the EVS disk be lost after the disk is detached?
If the CMK used to encrypt the disk is available, you can detach the encrypted
disk, and data will not be lost.
 Why I cannot view the attached EVS disk on the server?

After attaching the disk to the server on the management console, the disk
cannot be used. You need to initialize the disk first and then view and use the disk
on the server.
Contents
1. Overview
2. Purchasing
4. FAQs
5. Related Services
Related Services
 Elastic Cloud Server (ECS)
 Bare Metal Server (BMS)
 Volume Backup Service (VBS)
 Data Encryption Workshop (DEW)
 Cloud Eye
 Cloud Trace Service (CTS)
 Tag Management Service (TMS)
Related Services (Diagram)
Quiz
1. Which of the followings are EVS disk types? (multiple-answer question)
A. Ultra-high I/O
B. High I/O
C. Common I/O
D. Optimized I/O
2. How many servers can a shared EVS disk be attached to at most? (single-choice
questions)
A. 5
B. 7
C. 8
D. 16
Quiz
1. Briefly describes the methods that can be used to restore data on EVS disks.
 Restore disk data from backups.
 Restore disk data from snapshots.
Summary
 Describes HUAWEI CLOUD EVS.
 Introduces the concepts, functions, and application scenarios of EVS.
 Introduces how to create and manage EVS disks.
More Information
 For more information, visit at:
 https://support-intl.huaweicloud.com/evs/index.html
Recommendations
 Huawei learning website
 http://support.huawei.com/learning/en/newindex.html
 Huawei support cases

 http://support.huawei.com/enterprise/servicecenter?lang=en
Acronyms
Acronym Full Name Description

Number of operations performed
IOPS Input/Output Operations Per Second
per second
VBD Virtual Block Device Virtual block storage device
SCSI Small Computer System Interface Small computer system interface
Cloud Storage Services - Volume Backup
Service
Foreword
 This chapter describes Volume Backup Service (VBS) on HUAWEI CLOUD.
Objectives
 On completion of this course, you will be able to:
 Describe VBS.
 Know the concepts, functions, application scenarios, and common operations of

VBS.
 Know the VBS advantages and the charging standards.
 Know the frequently asked questions (FAQs) and some troubleshooting cases of
VBS.
Contents
1. Service Overview
2. Key Features
3. Common Operations
4. Limitations and Restrictions
5. FAQs and Troubleshooting Cases
6. Related Services
Introduction to VBS
 HUAWEI CLOUD provides Cloud Server Backup Service (CSBS) and Volume
Backup Service (VBS) to protect your data against viruses, unintentional
deletions, and software and hardware faults. This course introduces VBS.
 VBS secures your data. If an Elastic Volume Service (EVS) disk is faulty or
encounters a logical error (for example, mis-deletion, hacker attack, and
virus infection), you can use data backups to restore data quickly.
Product Architecture
Region A
1. Back up EVS disks to OBS.
EVS disk
ECS
2. Restore EVS disks from backups.

OBS
3. Create EVS disks from backups.

EVS disk
ECS
Comparison with CSBS
Aspect CSBS VBS

Backup and All or part of EVS disks (including
One or more specified EVS disks
restoration system and data disks) on a single
(system or data disks)
objects Elastic Cloud Server (ECS)
Only data disks need to be backed

Recommended An entire ECS needs to be
up, because the system disk does
scenarios protected.
not contain personal data.
All EVS disks on an ECS have

consistent data. They are backed up
at the same time, eliminating the Backup cost is reduced while
Advantages
problem of data inconsistency maintaining data security.
caused by backups generated at
different points in time.
Main Functions
 EVS disk backup
 Policy-driven data backup
 Data backup management
 Restoration of EVS disk data from backups
 EVS disk creation from backups
Application Scenarios
Hacker Attack or Virus Infection
VBS immediately restores data to the latest snapshot point in time.
Data Mis-deletion
Application Update Error

ECS Breakdown
VBS immediately restores data to the latest snapshot point in time to
ensure normal ECS running.
Advantages
Traditional disk backup VBS


Stores data to backup Provides 99.999999999% durability for
storage media, with low OBS data, ensuring your backup data
reliability. Secure security.


Uses dedicated backup Provides a simple GUI for you to
software, needing extra back up or restore your data with a
expertise. Easy to use few clicks.

 Performs incremental backups after
Requires dedicated backup
the initial full backup to reduce
storage devices, with high
Cost-effective storage space occupied.
cost on procurement and 
Pays for backup storage space on a
configuration.
per-use basis, reducing costs.
Charging Standards
 VBS itself is currently free of charge.
 Because VBS backups are stored on Object Storage Service (OBS), you
are charged for the OBS service you use by storage capacity and
storage duration.
Contents
1. Service Overview
2. Key Features
6. Related Services
Key Features
 Online backup
 Permanent incremental backup
 OBS for backup storage
 Policy-driven automatic backup
Online Backup
 Backs up EVS disks based on snapshots.
 Supports on-demand online backup at any time.
 Does not interrupt services.
 Does not require uninstallation of EVS disks.
 Requires no agents to be deployed in the service system.
 Minimizes impacts on customers' service systems.
 Requires no agents to be deployed on VMs.
Permanent Incremental Backup
 Offers permanent incremental backup.
 Improves backup efficiency.
 Cuts down the backup window by 95%.
 Reduces backup data storage space.
 Performs full backup upon the initial backup operation.
 Performs incremental backup for subsequent backup operations.
 Restores data to any backup point in time, independent from single

backups.
OBS for Backup Storage
 VBS stores backup data on OBS, improving data availability.
 Backup data can be remotely replicated to other storage devices,

improving reliability.
 OBS is inexpensive, reducing customers' costs.
 An EVS disk only occupies one snapshot no matter how many times it is
backed up, relieving the burden on local storage performance and
reducing local storage space.
Policy-Driven Automatic Backup
 A backup policy can be associated with multiple EVS disks to implement
automatic backup for them, greatly reducing manual works.
 You can set execution times for periodic backup to ensure data is backed
up in every critical point in time.
 You can also set the number of backups, so that expired backups are
deleted automatically, avoiding unnecessary backups being retained.
Contents
1. Service Overview
2. Key Features
6. Related Services
Common Operations (1)
 Creating backups
1. On the VBS page, click Create VBS
Backup.
2. Select EVS disks you want to back up. 3. Set the backup name and select the backup methods.
 Creating EVS disks from backups
1. Click Create Disk.
2. Configure the disk specifications. 3. Confirm the disk information and click Submit.
 Deleting a single backup
2. Confirm the deletion information and click OK.
1. In the row of the disk, choose More > Delete.
 Deleting backups in a batch

1. Select the backups you want to delete and 2. Confirm the deletion information and click OK.
click Delete in the upper left corner.
 Viewing backup details
1. Click the expansion arrow at the left of the backup name.
2. View the backup details.
 Searching for backups

Specify the filter criteria to search for backups.
 Sharing backups with other projects
1. Click the expansion arrow at the left of the name of the backup. 2. On the Shares panel, click Share Backup.
3. Enter the project ID which can be obtained from the

My Credential page.
4. Specify the search criteria to Backups shared with me,

and you can view the backup.
2. Configure the backup policy.
 Creating a backup policy
1. On the Policies tab page, click Create Policy.
 Editing backup policies
1. In the row of the policy, click Edit.
2. Modify the configuration

parameters of the backup
policy.
 Executing a backup policy 2. Confirm the policy information and click OK.
1. In the row of the policy, click Execute.
 Deleting a backup policy
1. In the row of the policy, choose More > Delete. 2. Confirm the deletion information and click OK.
 Associating EVS disks
1. In the row of the policy, click Associate Disk.
2. Select the disks you want to associate with the policy and click OK.
 Disassociating EVS disks
1. Expand the list of associated disks.
2. Confirm the disk information and click OK.
Contents
1. Service Overview
2. Key Features
6. Related Services
Limitations and Restrictions
 VBS does not support concurrent multiple backups for one EVS disk,
because backup creation in such scenarios may fail and the time sequence
of backups may be incorrect.
 Multiple EVS disks cannot be restored using one backup at the same time.
 EVS disks created from backups cannot be used as system disks.
 The default backup policy cannot be deleted.
Contents
1. Service Overview
2. Key Features
6. Related Services
FAQs (1)
 Does VBS Support Cross-Region Backup and Restoration?
 No. Currently VBS supports only backup and restoration within a region but not across
regions.
 Does VBS Support Simultaneous Backup of All EVS Disks on an ECS?

 Yes. You can create a backup policy and associate the backup policy with multiple EVS
disks. Then the backup policy can be executed to back up the multiple EVS disks at the
same time.
 Can a Disk Only Be Associated With One Policy?

 Yes. If an EVS disk you select to be associated with the target policy has been associated
with another one, the system will disassociate it from the original policy and then
associate it with the target one.
FAQs (2)
 Do I Need to Stop the ECS Before Backing Up EVS Disks on an ECS Using VBS?
 VBS can back up EVS disks that are being used. When an ECS is running, data is written onto EVS
disks on the ECS, and some newly generated data is stored in the ECS memory as cached data.
During EVS disk backup, the data in the memory will not be automatically written onto EVS disks,
resulting in data inconsistency between EVS disks and their backups.
 To ensure data consistency and integrity, back up EVS disks during off-peak hours without data
writing to the EVS disks, or stop writing data to the EVS disks before backup. For a strict
requirement for data integrity, stop the server (cached data is written to EVS disks) and start an
offline backup job.
 Do I Need to Stop the ECS Before Restoring EVS Disk Data with a VBS Backup?
 Yes. Before restoring the EVS disk data using a VBS backup, you must stop the ECS to which the EVS
disk is attached, and detach the EVS disk from the ECS. After the EVS disk data is restored, attach
the EVS disk to the ECS and start the ECS.
FAQs (3)
 Can a VBS Backup of a System Disk Be Used to Restore an ECS?
 Yes. You can restore the system disk using a VBS backup. Before restoring the system disk, you
must detach it from the ECS.
 You can also use the system disk to create new EVS disks. However, newly created EVS disks cannot
be used as system disks.
 Is There a Quota Limit on the Number of Backups?

 Yes. A quota is used to prevent resource abuse. You can submit an application to increase your
quota if necessary.
 Are My VBS Backups Retained After ECS Subscription Expires or EVS Disks Are Deleted?
 Yes, VBS backups created for EVS disks are retained when your ECS subscription expires or is
canceled. VBS backups are also retained when you delete EVS disks. You can continue to use these
VBS backups to create EVS disks.
FAQs (4)
 Does Backup Can Be Performed Several Times a Day?
 Yes. Up to 24 automatic backup jobs can be executed per day. Manual backup jobs have
no such restriction. The minimum frequency for policy-driven backup is once per
integral hour. Manual backup can be performed at any frequency.
 Why Are CSBS Backups Displayed on the VBS Backup Page?

 CSBS backups of ECSs are also displayed on the VBS Backups tab page and can be
distinguished from VBS backups by Source in the backup details. To use CSBS to back
up a server is to back up every disk of the server. These disk backups are displayed on
the VBS backup list and can be directly used to restore disks. Backups whose Source is
CSBS can be deleted only on the CSBS page.
Troubleshooting Cases
 When a backup is being created, its status changes to Error.
 Delete the VBS backups in the Error state and re-create them.
 When an EVS disk is being restored, the status of the EVS changed to
Failed.
 Delete the failed EVS disk and create a new EVS disk using the backup.
 VBS backups cannot be deleted, and the status of the backups is Deletion
failed.
 Contact technical support.
Contents
1. Service Overview
2. Key Features
6. Related Services
Related Services
 EVS
 VBS provides the data backup function for EVS disks. The created data backups
can be used to create EVS disks.
 CSBS
 CSBS and VBS both provide data backup protection.
 Simple Message Notification (SMN)

 VBS adopts SMN to notify users of VBS backup information.
 Tag Management Service (TMS)

 Working with TMS, VBS supports tag presetting and backup filtering and
management.
Summary
 Describes VBS provided on HUAWEI CLOUD.
 Introduces the concepts, functions, application scenarios, common

operations, and restrictions and limitations of VBS.
 Introduces the advantages and the charging standards of VBS.
 Introduces FAQs, troubleshooting cases, and related services of VBS.
More Information
 Huawei E-Learning website:
 http://support.huawei.com/learning/Index!toTrainIndex
 Huawei support case library:

 http://support.huawei.com/enterprise/servicecenter?lang=en
Cloud Storage Service – Object Storage
Service
Foreword
 This course provides an overview about Object Storage Service (OBS) in
HUAWEI CLOUD.
Objectives
 Upon completion of this course, you will:
 Know what OBS is.
 Understand basic concepts, functions, and application scenarios of

OBS.
 Know advantages and the charging standards of OBS.
 Know how to use the basic functions.
Contents
1. Introduction
2. Basics
3. Functions and Features
4. Using and Managing
5. FAQs and Troubleshooting
6. Reference Documents and Websites
Introduction to OBS
 What is OBS?
Object Storage Service (OBS) is a stable, secure, efficient, and easy-to-use cloud
storage service. It provides highly reliable storage capabilities at relatively low
costs.
Product Advantages
 Stable  Efficient
With reliability built into multiple levels of the OBS schedules data in the most optimal way,
architecture (such as equipment and data and leverages transfer acceleration and big
redundancy within an AZ, as well as cross-AZ data optimization to deliver the best possible
data DR), OBS achieves up to 99.999999999% data access experience.
(11 nines) in data durability, and maintains an
impressive 99.99% service continuity rate.
Object storage service
 Secure  Easy to use

OBS has passed the Trusted Cloud Service OBS supports REST APIs, provides multi-
(TRUCS) certification. It secures your data with language software development kits (SDKs),
multiple protection mechanisms, including and is compatible with all mainstream client
server-side encryption, URL validation, VPC- tools. Furthermore, OBS gives you the freedom
based network isolation, log auditing, and fine- to upload, download, and manage your data
grained permission control. anytime, anywhere.
OBS Charging Standards (1/2)
 OBS provides two billing modes. You can prepay for yearly/monthly packages or pay per use. You are
charged per use by default.
Billing Mode Billing Item Details
Storage capacity per hour (GB) x hourly price of

Storage capacity
the corresponding storage class
Price per 10-thousand requests x Actual requests

Request
per hour/10,000 (rounded down)
• Inbound traffic over the Internet and intranet.
Pay per use Free of charge
• Outbound traffic over the intranet. Free of
Traffic fee
charge
• Outbound traffic over the Internet. Hourly
traffic (GB) x Unit price per GB
Data Restoration Restored data volume (GB) x Unit Price per GB
OBS Charging Standards (2/2)
 OBS provides two billing modes. You can prepay for yearly/monthly packages or pay per use. You are
charged per use by default.
Billing Mode Billing Item Details
• One-off payment and effective upon

payment
• Clear-up monthly
Resource package • Renewal and unsubscription not
supported
Yearly/Monthly OBS offers packages for multi-AZ • Multiple packages supported for one
prepayment storage, common storage, account
downstream traffic, and pull • Within the validity period of a package,
traffic. used resources are deducted from the
package quota first. If the used resources
exceed the package quota, the excessive
part is charged at the pay-per-use rates.
OBS Application Scenario - Video Surveillance
• A single bucket can support a maximum of 1 billion
cameras.
Video Surveillance Cloud Services • A single bucket can store 100 billion objects, with the
capacity amounting to EB-level.
Campuses, buildings,
residences, stores 1 • One-channel video analysis can be done in 10
Video billion+ seconds; single-stream reaches the bandwidth
surveillance Camera performance of 300 MB/s; GPU computing efficiency
platform
links
Public increased by 50%.
network/ VMS • Fillp patent transmission acceleration is available.
Dedicated
Private connection • Storage price starts from ¥0.08/month per GB.
network
Object Storage
Service (OBS) You can pay as you go, without worries about
NVR Infrequent depreciation and O&M, greatly reducing the
Access
50% costs.
Costs • Multiple agencies can share their video
Archive
networking resources, video storage resources,
Screen Screen
and video analysis application resources.
• Resources can be provisioned in minutes, and
services can be flexibly deployed.
OBS Application Scenario - Video on Demand
Cloud Services CDN Terminals

Latency as low as 10 ms
• QAT acceleration (HTTPS); delay
WAV
less than 10 ms; fluent online
Media transcoding video playing

Video on Demand
300 MB/s single-stream bandwidth
• Single-stream bandwidth reaches
300 MB/s.
High concurrency TPS
HD Upload videos • 10-million TPS concurrency and 100-billion
object storage per bucket (meeting the
OBS
requirements of processing 3 million
concurrent access requests out from 250
million mobile users)
OBS Application Scenario - Backup and Archiving
Secure and reliable

Enterprise Cloud Services
Transmission • Widely compatible, supporting backup of all
Data Centers
channel
DR hosts/Test hosts mainstream OSs, applications, and databases;
Direct Connect/
Internet encrypted data transmission and storage
Enterprise Backup
applications Elastic Cloud Server
software
(ECS) Economic and efficient
Direct Connect/
Internet • Cloud resources are provisioned and charged
Restoration in cloud
Storage on demand. The initial investment is reduced
Databases gateway
Lifecycle OBS by 60%, and the construction period is
Direct Connect/
Internet shortened from months to days.
Standard
Unstructured
Data express Easy to manage
service (DES)
data • Public cloud computing, storage, and
Offline delivery Infrequent Access Archive
network services are at your request. No
dedicated O&M is required.
OBS Application Scenario - High Performance
Computing
Fast upload and download
• Up to 300 MB/s single-stream
Public cloud
bandwidth, implementing quick
online import of data
VPC
• Temporary authorization: Secure and
Head convenient secondary distribution of
Jobs nodes Auto-Scaling Image
(ECS) Service (AS) Manageme data
nt Service
EVS (IMS)
Enterprise Large volume data import
Data Common
users
upload I/O • 120 TB data can be migrated to the
and Worker Scalable
Cloud Eye
download Computing nodes File Service cloud with the Teleport offline data
results HPC flavors (SFS)
transfer capabilities.
DES
Teleport OBS Archive storage price starts from
Identity and
Access ¥0.033/GB per month
Management
• Source data and calculation results can
(IAM)
be stored in the Archive storage,
costing as low as ¥0.033/GB per month.
OBS Application Scenario - Mobile Internet
Scalable as needed
• Elastic resource scalability and flexible
End Users (Browsers, Apps) resource allocation
• Unlimited space for object storage
Static data
Static data responses Highly secure
Dynamic Dynamic requests • End to end (E2E) security service
data data
• 100 Gbit/s Anti-DDoS traffic cleaning
requests responses
CNAME • Web Application Firewall (WAF)
• Multi-level security protection for object
CDN
storage, ensuring data security
Retrieve
contents
10-million TPS concurrency
Dynamic website contents • 10-million TPS concurrency and 100-billion
Original site (Static script, object storage per bucket (meeting the
Intranet update attachments, images,
videos, and audio files)
requirements of processing 3 million
concurrent access requests out from 250
OBS million mobile users)
ELB ECS RDS
OBS Application Scenario - Enterprise Cloud Box
100 km disaster recovery
Email • 99.999999999% (11 nines) data
system
durability
• 99.99% (4 nines) service availability
Mobile Online
PCs PAD Virtual
phones play
desktops Archive storage price starts from ¥0.033/GB
Dynamic Dynamic VPN dedicated network per month
data data
requests responses Static • Lower cost of storage for data archiving
Enterprise cloud box (service system): authentication, data • Replacement of tape library for long-term
management, and search archiving
Dual encryption
ELB ECS RDS VBS
• Encrypted transmission
Intranet
• Encrypted storage
update
Enterprise cloud box (data storage): files, video storage,
emails Full compatibility
• Partners and open source cloud disks provide
Lifecycle full compatibility with applications (Windows
OBS OBS
Standard Infrequent Access and macOS).
storage storage
Contents
1. Introduction
2. Basics
Basic OBS Concepts
 Object
Internet
 Bucket
 AK and SK
 Region OBS
Object Object
Object Object
Object Object
Object Object
Bucket Bucket
Contents
1. Introduction
2. Basics
Key Functions
 Permission control
 monitoring
 Versioning
 Tags
 Event Notification
 Lifecycle management
 Static website hosting
 Server-side encryption
Permission Control (1/6) Permission Control (1/6)
 This section describes how to set the operation permissions to OBS

resources through Identity and Access Management (IAM).
IAM user group Permission Description
IAM user
Tenant Users with this permission can perform any
group Administrator operation on OBS resources.
IAM user 1
IAM user 1
Users with this permission can query the usage of
Tenant Guest
OBS resources.
IAM user
IAM user 22
OBS Buckets Users with this permission can obtain the list,
IAM
IAM user
user 33 Viewer metadata, and location information of buckets.
Permission Control (2/6)
 You can configure object and bucket ACLs to control requests for accessing OBS.
 OBS provides account-based access control lists (ACLs).
 By configuring bucket and object ACLs, you can authorize the access permission to specific users,
bucket owners, anonymous users, registered users. In addition, bucket ACLs support the
authorization of access permission to log delivery users.
 Through bucket and object ACLs, you can authorize users the permissions to access buckets/objects
and ACLs.
 OBS supports fine-grained permission control for buckets and objects
through bucket policies. If an ACL and a bucket policy conflict with each
other, the bucket policy takes precedence over the ACL.
 ACL authorized users
Authorized
Description
User
Object owner is the account that creates the object. The owner of an
Owner
object has the ACL read and write permissions permanently by default.
A user that is not registered with OBS. If the access permission for a
Anonymous
bucket and objects in the bucket is authorized to anonymous users, all
User
users can access the bucket and its objects.
A user that is registered with OBS. For example, a registered user can
Registered User
access OBS Browser using AKs and SKs.
An account that has permission to access a bucket. The bucket owner

Specific User
authorizes this permission by account ID or account name.
Only bucket ACLs support this user group. A log delivery user delivers
Log Delivery
the access logs of buckets and objects to the target bucket.
User
 ACL Permission Control
Permission Description
A grantee with this permission for a bucket can obtain the

Read list of objects in the bucket and the metadata of the
Bucket access bucket.
permission
A grantee with this permission for a bucket can upload,
Write
overwrite, and delete any object in the bucket.
Object access
Read Allowed to obtain the object content and metadata.
permission
Allowed to obtain the ACL of the object/bucket.
Read The owner of this object/bucket has this permission
permanently by default.
ACL access
permission
Allowed to update the ACL of the object/bucket.
Write The owner of this object/bucket has this permission
permanently by default.
 Bucket policy application scenarios
 Get object contents.
 To obtain the content of an object in a bucket, you must configure the bucket policy (set General
Settings to Public Read or configure the Customized mode in the Advanced Settings) to grant such fine-
grained permissions to users.
 Manage OBS access permissions across accounts.

 To grant an IAM user in an account with the access permission to resources under another account, you
must configure a bucket policy with advanced settings.
 Manage all OBS operation permissions.

 To manage all operation permissions of OBS buckets and objects, you need to configure a bucket policy
with advanced settings.
Monitoring
 OBS Control supports the monitoring of storage space, object counts, traffic, and number of requests.
You can view the bucket monitoring information on the Summary page of a bucket.
 The Cloud Eye management console monitors the following statistics for buckets: upload traffic,
download traffic, GET and PUT requests, average TTFB of GET requests, 4xx and 5xx errors.
Versioning (1/4)
 Enabling Versioning
 Upload objects and check their versions.
Existing objects before versioning is enabled Objects uploaded after versioning is enabled
Object.txt Object.txt
Versioning enabled Version ID=00002
Version ID=00001
Versioning disabled
Version ID=null Version ID=00001
Versioning enabled
 The latest objects in a bucket are returned by default after a GET Object request.
 Objects can be downloaded by version IDs. By default, the latest object is downloaded if the version
ID is not specified.
Versioning (2/4)
 You can select an object and click Delete on the right to delete the object. After the object is
deleted, OBS generates a Delete Marker with a unique version ID for the deleted object, and the
deleted object is displayed in the Deleted Objects list. If you try to access the deleted object, a 404
error will be returned.
Object.txt (delete marker)

Version ID=00003
Object.txt
Version ID=00002
Object.txt
Version ID=00001
 You can recover a deleted object by deleting the object version that has the Delete Marker.
 After an object is deleted, you can specify the version number in Deleted Objects to permanently
delete the object of the specified version.
Versioning (3/4)
 An object is displayed either in the object list or the list of deleted objects. It will never be displayed
in both the lists at the same time. For example, after object A is uploaded and deleted, it will be
displayed in the Deleted Objects list. If you upload an object named A again, the object A will be
displayed in the Objects list, and the previously deleted object A will no longer be displayed in the
Deleted Objects list.
Object.txt
Version ID=00004
Object.txt (delete marker)

Version ID=00003
Object.txt
Version ID=00002
Object.txt
Version ID=00001
Versioning (4/4)
 Suspending Versioning
 Once the versioning function is enabled, it can be suspended but cannot be disabled. Once versioning is
suspended, version IDs will no longer be allocated to newly uploaded objects. If an object with the same name
already exists and does not have a version ID, the object will be overwritten.
Versioning enabled Upload a
Version ID=00002 Version ID=null
namesake object
Versioning enabled Object.txt after versioning Object.txt
Version ID=00001 is suspended Version ID=00002
Versioning disabled
Version ID=null Version ID=00001
Versioning suspended
 Historical versions will be retained in OBS. If you do not need these historical versions, manually delete them.
 Objects can be downloaded by version IDs. By default, the latest object is downloaded if the version ID is not
specified.
Tags
 Tags are used to identify and classify OBS buckets.
 A tag is described using a key-value pair. Each tag has only one key and one value.
 The key and value can exist in either sequence in a tag. Each key is unique among
all tags of a bucket, whereas values can be repetitive or blank.
Event Notification (1/2)
 You can use Simple Message Notification (SMN) to send alarms and notifications,
and trigger workflows.
Event Notification (2/2)
 OBS supports event notifications for the following events:
 Upload objects using PUT.
 Upload objects using POST.
 Replicate objects using COPY.
 Upload an object in multiparts.
 Delete objects with a specific object version.
 Delete objects with random object versions.
Lifecycle Management
 You can manage the lifecycle of objects by configuring rules for deletion or
transition.
Static Website Hosting
 OBS allows you to access static websites hosted by OBS.
Register a domain name.
Access Company A's website.

Create a bucket.
Upload static website files.

Users website
Configure static website
hosting.
Convert the domain Configure DNS.

Name to its CNAME.
Verify
Configure static website hosting.
Company A OBS bucket
Server-side encryption
 Server-side encryption enabled:
 When uploading an object, the object data is encrypted on the server and then stored in OBS.
 When downloading the encrypted objects, the encrypted data will be decrypted on the server and displayed in
plaintext to users.
 OBS supports both server-side encryption with KMS-managed keys (DEW-KMS) and server-side encryption with
customer-provided keys (SSE-C) by invoking APIs. In SSE-C mode, OBS uses the keys and MD5 values provided by
customers for server-side encryption.
URL Validation
 To prevent data in OBS from being stolen by other users, OBS supports URL validation based on the Referer field in
HTTP headers.
 OBS also supports both whitelist and blacklist settings.
 If the Referer field in a request matches the whitelist, the request is allowed.
 If the Referer field in a request matches the blacklist, the request is denied or a specified page is returned.
Fragments Management
 Why are fragments generated:
 The network is in poor conditions, and the connection to the OBS server is interrupted frequently.
 The upload task is manually suspended.
 The device is faulty.
 The device is powered off suddenly.
 The storage space occupied by fragments in OBS is charged.
 Fragments need to be manually cleared.
Contents
1. Introduction
2. Basics
Methods for Accessing OBS
OBS
OBS Browser OBS Console
OBS Browser Management Functions
Bucket management OBS Browser Object management
Adding a bucket Creating a folder
Searching for a bucket Searching for a file or folder
Viewing bucket information Uploading a file or folder
Bucket ACL Task management Downloading a file or folder
Managing upload tasks

Bucket policies Renaming a file
Managing download tasks

CORS Copying a file or folder
Managing deletion tasks Moving a file or folder

Logging
Managing rename tasks

Lifecycle management Restoring an Archive file
Managing copy tasks

Fragment management Configuring an ACL for an object
Managing move tasks

Deleting a bucket Configuring a policy for an object
Managing restoration tasks

Adding an external bucket Deleting a file or folder
Preparing the OBS Browser Environment
1. Log in to OBS Console to obtain the OBS Browser software package.
On the home page of OBS Console, download the OBS Browser software package through the link based
on your operating system.
2. Create an access key (AK and SK).

a. In the upper right corner of the OBS Console page, click the username and choose My Credential.
b. On the My Credential page, click Add Access Key below the Access Keys area.
c. Enter the related information as prompted and save the newly created access key.
3. Log in to OBS Browser.

a. Decompress the OBS Browser software package.
b. Double-click obs.exe to run OBS Browser.
c. In the Manage Account dialog box that is displayed, click Add Account.
d. Enter the account information and click OK. Then you can log in to the storage service using the account and che
ck bucket and object resources owned by the account.
Using OBS Browser (1/4)
 Adding a bucket
 Click Add Bucket in the upper left corner of the OBS browser home page.
 In the Add Bucket dialog box that is displayed, set Method to Create new bucket,
enter a region name and bucket name, and select a storage class for the bucket. Then
click OK.
 In the displayed dialog box, click OK.
The newly created bucket is displayed in the list.
 Uploading a file or folder
You can use OBS Browser to upload files in multiparts. It supports the upload of a single
file with the maximum size of 48.8 TB.
OBS Browser supports resumable transfer.
 Click the bucket name to go to the object management page.
 Choose Upload > Upload File. You can upload a maximum of 500 files at a time.
 Alternatively, you can click Upload, and choose Upload Folder to upload a folder.
 Select a storage class.
 Click OK.
Click in the upper right corner of the page to enter the task management page. On the
page that is displayed, you can manage the upload tasks.
 Downloading a file or folder
 Select the file or folder to be downloaded and click Download.
 Select a storage path and click Download.
Click in the upper right corner of the page to enter the task management page. On the
page that is displayed, you can manage the download tasks.
 Deleting a file or folder

 Click next to the file or folder to be deleted and select Delete.
 In the dialog box that is displayed, click OK.
 Deleting a bucket
Before deleting a bucket, ensure that all objects in the bucket have been deleted.
Only the bucket owner can delete a bucket.
 Click next to the bucket to be deleted and select Delete.
 Click OK in the confirmation dialog box.
 In the dialog box that is displayed, click OK.
Contents
1. Introduction
2. Basics
FAQs and Troubleshooting
Question 1
 After an object with a long name is downloaded to the local path using OBS
Console, why does the object name change?
Answer
 For Windows, a file name can contain a maximum of 255 characters, including the
file name and file name extension. When an object with a name containing more
than 255 characters is downloaded to a local computer, the system keeps only the
first 255 characters automatically.
Question 2
 A user logs in to OBS Console using Internet Explorer 11 and uploads an object. When the
user attempts to download the object to the original path to replace the original object
without closing the browser, a message is displayed indicating a download failure. Why is
this?
For example, a user uploads object abc from the root directory of local drive C to a bucket on
OBS Console. When the user attempts to download the object to the root directory of local
drive C to replace the original object without closing the browser, a message is displayed
indicating a download failure.
Answer
 This problem is caused by browser incompatibility. It can be solved by using Google

Chrome as the browser. Alternatively, you can close the browser and try again.
Question 3
 Why cannot objects be globally searched for in a bucket? For example, if the root directory
of bucket abc contains folder A and object B and folder A contains object C, object C
cannot be searched for in the root directory of bucket abc. It can be searched for only in
folder A.
Answer
 OBS Console does not support iterative query of objects in a bucket but supports query of
objects in a directory only. If you want to search for an object, go to the directory where the
object resides and search for the object.
Question 4
 Why is no upload task created and nothing displayed on the page after a large number of
files are selected for upload using OBS Browser? For example, after a user logs in to OBS
Browser and chooses Upload > Upload File to select a large number of files from drive C
for upload, no upload task is created and nothing is displayed on the page.
Answer
 The total name length of all files to be uploaded cannot exceed 25,500 characters
(approximate value). If the name length exceeds the threshold, the system stops
responding to the upload request. The file uploading function of OBS Browser allows 500
files to be uploaded at the same time. If more files need to be uploaded, it is recommended
that you put the files in a folder and use the folder uploading function for upload.
Question 5
 Why are the relevant tasks not displayed in the task list when objects are being uploaded,
downloaded, or deleted using OBS Browser?
Answer
 When you use OBS Browser to upload, download, or delete objects, the internal database
of OBS Browser is invoked. By default, binary data generated while the database is running
is saved in the personal folder of the Windows operating system user.
 If the username of the Windows operating system contains non-English characters, the
internal database of OBS Browser cannot identify the save path of data. As a result, upload,
download, and deletion tasks cannot be added to the task list. In this case, click System
Configuration > Other in the upper right corner of the page to change the save path to
ensure that the database is running properly.
Question 6
 OBS is unavailable when an error is reported stating "Time difference is longer
than 15 minutes between the client and server." Why is this?
Answer
 For security purpose, OBS checks the time difference between OBS Browser and
the server. When the time difference is longer than 15 minutes, such an error is
reported and you need to adjust the local time.
Contents
1. Introduction
2. Basics
Reference Documents and Websites
 OBS Overview:
https://support.huaweicloud.com/en-us/productdesc-obs/en-us_topic_0045853681.html
 OBS Console Operation Guide:
https://support.huaweicloud.com/en-us/usermanual-obs/obs_03_0054.html
 OBS Client Operation Guide (OBS Browser):
https://support.huaweicloud.com/en-us/clientogw-obs/en-us_topic_0086375542.html
 OBS Developer Guide:
https://support.huaweicloud.com/en-us/devg-obs/en-us_topic_0100849894.html
Quiz
1. (Multiple choices) Access requests to OBS can be controlled by ( )
A. ACLs
B. Bucket policies
C. User signature authentication
D. Server-side encryption
Summary
 Introduces OBS.
 Introduces the concepts, functions, and application scenarios of OBS.
 Introduces the advantages and charging standards of OBS.
Acronym or Abbreviation
Abbreviation Full Name

API Application programming interface
AK Access key ID
SK Secret access key
ACL Access control list
SDK Software development kit
CORS Cross-origin resource sharing

Module 4 - Storage Cloud Services - Huawei

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Module 4 - Storage Cloud Services - Huawei

Uploaded by

Copyright:

Available Formats

Storage Services - Elastic Volume Service

Copyright © 2019 Huawei Technologies Co., Ltd. All rights reserved.

 Understand the concepts, functions, and application scenarios of EVS.

 Understand how to create and manage EVS disks.

 Understand how to troubleshoot EVS frequently asked questions (FAQs).

3. Usage and Management

 Attach disks to servers.

 Expand disk capacities.

 Create backups for disks.

3. Usage and Management

Disk Name Optional volume-0001

IOPS per GB/EVS

Common I/O 2 2,200 90 MB/s

High I/O 6 5,000 150 MB/s

3. Usage and Management

 Disk detachment process:

 Disk detachment process:

 Process of data restoration from a backup:

3. Usage and Management

 A shared EVS disk can be attached to a maximum of 16 servers.

 Why I cannot view the attached EVS disk on the server?

3. Usage and Management

 Bare Metal Server (BMS)

 Volume Backup Service (VBS)

 Data Encryption Workshop (DEW)

 Cloud Trace Service (CTS)

 Tag Management Service (TMS)

 Restore disk data from backups.

 Restore disk data from snapshots.

 Introduces the concepts, functions, and application scenarios of EVS.

 Introduces how to create and manage EVS disks.

 Huawei support cases

Acronym Full Name Description

 Know the concepts, functions, application scenarios, and common operations of

 Know the VBS advantages and the charging standards.

4. Limitations and Restrictions

5. FAQs and Troubleshooting Cases

1. Back up EVS disks to OBS.

2. Restore EVS disks from backups.

3. Create EVS disks from backups.

Aspect CSBS VBS

Only data disks need to be backed

All EVS disks on an ECS have

 Policy-driven data backup

 Data backup management

 Restoration of EVS disk data from backups

 EVS disk creation from backups

Application Update Error

Traditional disk backup VBS

4. Limitations and Restrictions

5. FAQs and Troubleshooting Cases

 Permanent incremental backup

 OBS for backup storage

 Policy-driven automatic backup

 Supports on-demand online backup at any time.

 Does not interrupt services.

 Does not require uninstallation of EVS disks.

 Requires no agents to be deployed in the service system.

 Minimizes impacts on customers' service systems.

 Requires no agents to be deployed on VMs.

 Improves backup efficiency.

 Cuts down the backup window by 95%.

 Reduces backup data storage space.

 Performs full backup upon the initial backup operation.