HCIA-Storage V4.5 Training Material

HCIA-Storage V4.
5 Theory Course
Theory Course Overview
M1 Storage Technology Trends 1-1 Storage Technology Trends
2-1 Intelligent Storage Components
2-2 RAID Technologies
2-3 Common Storage Protocols

M2 Storage Basic Technologies
2-4 Storage System Architecture
2-5 Storage Network Architecture

Theory
2-6 Introduction to Huawei Intelligent Storage Products
Course
3-1 Storage Resource Tuning Technologies and Applications
M3 Storage Common Advanced Technologies
3-2 Storage Data Protection Technologies and Applications
4-1 Backup Solution Introduction

M4 Storage Business Continuity Solutions
4-2 DR Solution Introduction
5-1 Storage System Operation Management

M5 Storage System O&M Management
5-2 Storage System O&M Management
1 Huawei Confidential
Storage Technology Trends
Foreword
 Data carries information during the transmission on networks. What is the

relationship between information and data? What is the function of data
storage? This course describes the definition of information and data in the
computer field, their relationship, as well as the concept, development
history, and development trend of data storage.
Objectives
On completion of this course, you will be able to understand:

 Definition of information and data
 Concept of data storage
 History of data storage
 Development trend of data storage products
Contents
1. Data and Information
2. Data Storage
3. Development of Storage Technologies
4. Development Trend of Storage Products
What is Data
 SNIA (Storage Networking Industry Association) defines data as the digital
representation of anything in any form.
Format in which data is stored
Email 0101001010100010000011
1100011100010001110001
1100000111101010100101
Digital music 0101001010100101001010
1001010101001010100010
1010010101001010101010
Digital video
0101010101010010100010
0101001010101010100101
Ebook 0101001010101010100101
0101010010100101001000
1010101001001010010010
Data Types
Semi-
Structured structured Unstructured
data data data
Data Processing Cycle
 Data processing is the reorganization or reordering of data by humans or
machines to increase their specific value. A data processing cycle includes three
basic steps: input, processing, and output.
Input Processing Output
What is Information
 Information is processed, structured, or
rendered in a given context to make it
Processing Information
meaningful and useful.
 Information is processed data, including
data with context, relevance, and
Data
purpose. It also involves the manipulation
of raw data.
Data
Redundancy
Data vs. Information
 After being processed, data can be converted into information.
 In order to be stored and transmitted in IT systems, information need to be
processed as data.
Item Data Information

Raw and meaningless, with no
Feature Valuable and logical
specific purpose
Essence Original materials Processed data
Dependence Data never depend on information Information depends on data
Meteorological data or satellite
Example Weather forecasts
image data
Information Lifecycle Management
 Information lifecycle management (ILM) refers to a set of management
theories and methods from the stage in which the information is generated and
initially stored to the stage where the information is obsoletely deleted.
Data value
Data Data Data Data Data Data

creation protection access migration archiving destruction
Contents
2. Data Storage
What is Data Storage
Storage in a narrow sense Storage in a broad sense
Data Storage System
 Disaster recovery (DR) solutions

 Backup solutions
 Storage management software

Solutions
 Snapshot and mirroring software
 Backup software
 Multipathing software
Storage software
 Storage devices  Connection elements
 Disk array  HBA cards
 Tape library  Switches
Storage hardware  Virtual tape  Cables
library  ……
 ……
Physical Structure of Storage
Hosts
Network switching devices NAS gateway
Storage application
software
The front-end board of
controllers
Cache
Storage
System The back-end board of Storage management
controllers software
Connectors
Disks
Data Storage Types
Internal DAS
Storage SAN
Storage FAS
External NAS
Storage
Evolution of Data Management Technologies
Distributed
Dedicated storage device
storage device
Tape and single

disk
Big data
management
Card and paper Traditional
tape database
File system system
management management
Manual
management
Data Storage Application
Database servers
Users
Application
servers
Email servers
Offline
storage
File servers Online storage Nearline storage
Employees
Classification based on data access frequencies
Data Data Data

generation processing management
Contents
2. Data Storage

 Storage Architecture
▫ Storage Media
▫ Interface Protocols
History of Storage Architecture Development
2000s
1990s • Distributed
• Storage storage
1980s network • Cloud storage
• External
storage
1950s
• Traditional
storage
From Disks to Disk Arrays
Disks in a server Early external storage Storage arrays

Server Server Server
CPU CPU CPU
RAM RAM RAM
Disks Disks Disks
JBOD
Controllers
From Separation to Convergence
SAN NAS Clients Unified

Storage
Server Server
File
Ethernet
system Server
SAN LAN
File
NAS SAN
system
Storage Storage
File
system
Storage
Distributed Storage
 Physical resources are organized using
software to form a high-performance
Front-end
logical storage pool, ensuring reliability service
network Management
and providing multiple storage services. network
 Generally, distributed storage scatters

data to multiple independent storage
servers in a scalable system structure. It
uses those storage servers to share
...
storage loads and uses location servers
to locate storage information. Node Node Node Node
Back-end storage network
Storage Virtualization
 Storage virtualization consolidates the Clients or servers
storage devices into logical resources,

thereby providing comprehensive and
unified storage services. Management
 Unified functions are provided Logical resources
regardless of different storage forms
and device types.
Virtualization
Physical resources
Cloud Storage
 The cloud storage system combines multiple storage devices, applications, and services. It uses
highly virtualized multi-tenant infrastructure to provide scalable storage resources for enterprises.
Those storage resources can be dynamically configured based on organization requirements.
Legacy New
applications applications
Protocol and interface
Converged
Elastic Block storage service File storage service Object storage service
Open Storage device and storage node
Universal hardware platforms
Contents
2. Data Storage

▫ Storage Architecture
 Storage Media
▫ Interface Protocols
History of HDDs
 Larger capacity with the smaller size.
1950s–1960s 1960s–1970s 1970s–1980s 1980s-1990s 1990s-

Giant disk 14-inch disk 8-inch disk Portable Microdrive
IBM 350 RAMAC IBM 3340 Disks started to 5.25-inch 1.8-inch
IBM 1301 enter the civil 3.5-inch Hitachi: 1-inch
market 2.5-inch Toshiba: 0.85-
inch
...
History of SSDs
 Solid-state drives (SSDs) were invented almost as early as HDDs, but were not
popular at that time due to high price and the rapid development of HDDs at
the end of the 20th century.
 With the requirement for high access speed, SSDs are booming.
• Bell Labs
1976 • SanDisk
1999 • Samsung
2010…
• Floating gate • Dataram sold launched flash • BiTMICRO released laptops • Lower costs
transistor Bulk Core. SSDs. launched flash using SSDs.
• Greater capacity
• 2 MB capacity • 20 MB capacity SSDs. • 32 GB capacity
• 18 GB capacity
1967 1991 2006
Development of Flash Memory
Single-level Quad-level cell

cell (SLC): fast Triple-level cell (QLC): larger
read/write and (TLC): mature and cheaper,
long service mainstream applicable to
life technology warm data
Multi-level cell 3D TLC:

(MLC): improve the
moderate storage density
read/write through multi-
speed and layer
service life overlaying
Contents
2. Data Storage

▫ Storage Architecture
▫ Storage Media
 Interface Protocols
Interface Protocols
 Disk interfaces connect disks to hosts.
 Interface protocols refer to the communication modes and requirements that
interfaces for exchanging information must comply with.
Parallel interface Serial interface
History of Interface Protocols
100G NVMe-oF 400G

Ethernet NVMe-oF 1.0 (FC-NVMe) Ethernet
Host interface (RDMA) NVMe-oF 1.1
(TCP) 64G FC
2G FC iSCSI 4G FC 8G FC 16G FC 32G FC
The first-gen FC
protocol was 2004 2008 2012 2016 2017 2018 2020…
released in 1994.
SATA 1.0
Disk interface SATA 3.0
4G FC
SAS 1.0 SAS 2.0 SAS 3.0 SAS 4.0
SATA 2.0
NVMe 1.0 NVMe 1.2 NVMe 1.3 NVMe 1.4
NVMe and NVMe-oF
 NVMe, Non-Volatile Memory Express
 Improve the performance CPU CPU
 Reduce the latency PCIe PCIe
 NVMe-oF, NVMe over Fabrics
SAS Controller
 Potential: low latency and high
SAS Expander
bandwidth
 Purpose: accelerate the data
transmission among the storage NVMe back-end SAS back-end
physical path physical path
network
Contents
2. Data Storage
History of Storage Products
Cloud
Media
HDD SSD
Architecture Trend
Centralized Distributed
All-flash Intelligence
Management
Manual O&M Intelligent O&M
The Intelligence Era is Coming
Steam Age Electricity Age Information Age Intelligence Age
Industry Cloud Service extension

computing AI
Network coordination
Agriculture
+ Data + Intelligence
Internet
IoT
Intelligent production
Service Big data Customization
Challenges to Data Storage
24/7 µs-level
Time-consuming of Always-on Real-time, high-speed
RAID reconstruction services for all processing of production
Service things connected transactions in the 5G era
interruption due
to multiple points
of failure Finance High disk
Reliable Fast
failure rate
Gov & Public Large

enterprise
Low data
deduplication and
compression ratio Efficien
Large
Carrier Transportation t
EB-level TCO reduction

Energy & Electricity Unstable latency Data monetized as Edge-center-cloud
under high assets and intelligent synergy, minimizing
Inefficient convergence of concurrency storage tiering, the per-bit data cost
block, file, and object turning cold data to and maximizing the
services warm data to mine value
data value
Characteristics of Storage in the Intelligence Era
Storage in the intelligence
era
Intelligent data lifecycle
management
Storage for AI AI in storage
Data convergence
Zero data migration Data collaboration
Convergence of Simplified protocol stack and data-
SAN and NAS storage convergence
Intelligent storage tiering of hot, Compute-storage collaboration, on-
warm, and cold data demand capacity expansion
Multi-service convergence Dedicated hardware and
(block, file, and object) distributed storage
Hardware + Algorithm + Architecture = Efficient storage
Robust reliability Large capacity High performance
Device-level of 99.99999% PB-level to EB-level ms-level to µs-level
System-level of 99.999% Efficient deduplication & Intelligent distributed cache
compression
Solution-level reliability + Cost-effective media, warm and High-speed protocols
Cloud-level DR cold data storage and algorithms
Minimum cost and maximum value for per-bit data
Data Storage Trend
Distributed
storage
Database Cloud
applications Blockchain
computing Storage in AI
Mainframe the
system
Private software
Hyper- Big data intelligenc
Traditional
and hardware
external
converged e era
solutions with infrastructure 5G
fully coupled storage (HCI) General-
computing, purpose
Brain-like
storage, and computing DNA Graph
Tensor computin
network computing computing computing
VM Container g
resources, x86
applicable only to
CXL HCCS
large RoCE/NVMe
organizations
FC IP
SAS IB Quantum dot
PCM MRAM
HDD SSD
Biomolecule Optical storage
Optical Storage Technology
Blu-ray storage Gold nanostructured glass
Long service High 100 GB+ per Low power Long-term 10 TB per
life reliability disk consumption stable storage disk
50 years >>> 600 years
DNA Data Storage
 A small number of synthetic DNA molecules can store a large amount of data,
and can freeze, dry, transport, and store data for thousands of years.
 Advantages of using DNA as storage media:
 Small size
 High density
 Strong stability
 Bottlenecks and limitations:
 High costs of DNA molecular synthesis
 Slow data read and search
Atomic Storage
 In 1959, physicist Richard Feynman suggested that it was possible to use atoms to store
information if they could be arranged the way we wanted.
 Because an atom is so small, the capacity of atomic storage will be much larger than that of the
existing storage medium in the same size.
 With the development of science and technology, arranging the atoms the way we want has
become a reality.
 Bottlenecks and limitations:
 Strict requirements on the operating environment.
Quantum Storage
 Now, information in electronic devices is stored and moved through the flow of electrons.
 If electrons are replaced by photons, the movement of information within the computer may
occur at the speed of light.
 Although the storage efficiency and service life are improved, the quantum storage is still difficult
to be widely applied at present.
 Quantum storage cannot meet the following requirements:
 High storage efficiency
 Low noise
 Long service life
 Operating at room temperature
Storage Network Trend
AS-IS TO-BE
FC SAN and IP SAN Converged AI Fabric network
High network costs: The FC private network has low latency but high Reduced network costs: Open Ethernet carries high-performance, low-
costs. The IP SAN has low costs but high latency and poor performance. latency, and low-cost storage networks.
High O&M costs: IP SAN and FC SAN require dedicated O&M personnel Reduced O&M costs: No dedicated O&M skills are required, and unified
separately, and do not support cloud-and-network synergy network management is supported for data centers.
LAN Flexibility
Eth
Flexibility
No packet loss
NIC NIC
Low latency
FC SAN FC SAN
IP SAN IP SAN
10G Eth
IP FC
16G FC SAN iNIC iNIC
SAN SAN
10G IP SAN
Low cost Low latency
25/100G Eth
History of Huawei Storage Products
2019
2017 First high-end
2015 Huawei OceanStor storage
2013 2nd-gen high- Dorado, fastest
2011 accelerated by AI
end storage all-flash storage
2008 1st-gen high- chips
2006 Launched self- end storage
2002 Launched 2nd- developed Interop Best
Released SmartMatrix
Dived into gen FC storage. HSSDs, pioneer architecture Best-in-class of of Show
self-
storage Founded in the all-flash the year Award
developed
technical IP SAN Huawei industry
research Symantec Co.,
Ltd.
Start out Grow Lead
Released self-
Launched developed Distributed Huawei
FC storage virtual storage clustered Launched T OceanStor V3
2003 NAS storage series
2007 unified storage First SAN&NAS Leader in Gartner Industry's first
2009 converged Magic Quadrant full-series
2012 storage Huawei
for the first time NVMe all-flash
2014 OceanStor
2016 storage Pacific series
2018
2020
Architecture of Huawei Intelligent Data Storage Products
Storage Database Big data Edge Intelligent data reduction
• AI-based prediction
Intelligent data reduction Intelligent data storage • Intelligent CPU and GPU reduction algorithms
• Deep • Intelligent • CPU/GPU • Intelligent • Intelligent • Intelligent
compression global acceleration tiering prefetch prediction Intelligent data storage
Intelligence prediction • Optimal media combination using technologies
Intelligent scheduling such as intelligent prefetch, data tiering, hotspot
• Container • Heterogeneous computing power • Near-data computing identification, and data caching
+
Intelligent scheduling
CPU
DRA NPU
SCM GPU
SSD • Dynamic management of heterogeneous
computing resources; near-data computing
Memory Fabric scheduling; quick start of containers
Hardware Network Network
chip chip
Memory Fabric: high-performance network centered
All IP on memory
• High-performance network with ns-level latency
Memory SSD
media
• Memory pooling and tiering
media
All IP: extremely low cost of SSD media

• In-depth disk-controller collaboration,
DRAM SCM SLC/QLC QLC/OLC SLC/QLC/OLC evolution
ns µs 50 µs 200 µs • All IP to build an ultra-simplified network
Edge Production Analysis Backup Archive
Quiz
1. (Multiple-answer question) Which of the following are data types?
A. Structured data
B. Semi-structured data
C. Unstructured data
D. Massive amounts of data
2. (Multiple-answer question) Which of the following statements about storage are correct?
A. Storage refers to disks.
B. A storage system consists of storage hardware, software, and solutions.
C. Storage types include block storage, file storage, and object storage.
D. File storage is used to store data of data applications.
Quiz
3. (Multiple-answer question) Which are characteristics of cloud storage?
A. Convergence
B. Open
C. Elasticity
D. Scale-up
4. (Multiple-answer question) Which of the following are the objectives of integrating AI into storage?
A. Simple
B. Efficient
C. High power consumption
D. Easy to use
Summary
Data and Information
Data Storage Storage Architecture

Trend of Storage
Technologies
Storage Technologies Storage Media
Storage Products Interface Protocols
More Information
Enterprise Huawei
Technical Enterprise
Support App Service App
Recommendations
 Huawei official websites

 Enterprise business: https://e.huawei.com/en/
 Technical support: https://support.huawei.com/enterprise/en/index.html
 Online learning: https://www.huawei.com/en/learning
 Popular tools
 HedEx Lite
 Network Document Tool Center
 Information Query Assistant
Thank you. 把数字世界带入每个人、每个家庭、
每个组织，构建万物互联的智能世界。
Bring digital to every person, home, and
organization for a fully connected,
intelligent world.
Copyright©2020 Huawei Technologies Co., Ltd.

All Rights Reserved.
The information in this document may contain predictive

statements including, without limitation, statements regarding
the future financial and operating results, future product
portfolio, new technology, etc. There are a number of factors that
could cause actual results and developments to differ materially
from those expressed or implied in the predictive statements.
Therefore, such information is provided for reference purpose
only and constitutes neither an offer nor an acceptance. Huawei
may change the information at any time without notice.
Intelligent Storage Components
Foreword
 This chapter describes the components of the storage system, including the
controller enclosure, disk enclosure, disks, interface modules, and
connection modes between enclosures and their respective working
principles.
Objectives
Upon completion of this course, you will understand:

 Storage product forms
 Functions and components of controller enclosures and disk enclosures
 Working principles of HDDs and SSDs
 Cables and interface modules for connecting storage enclosures and the
connection methods
Contents
1. Controller Enclosure
2. Disk Enclosure
3. Expansion Module
4. Disk
5. Interface Module
Storage Product Form
2 U, disk and 4 U, disk and Integrated bay

controller integration controller separation
Note: Huawei OceanStor Dorado V6 is used as the example.
Controller Enclosure
 The controller enclosure uses a modular design and consists of a system subrack,
controllers (with built-in fan modules), BBUs, power modules, management modules,
and interface modules. Management
Power Module Module
Interface
Module
System Subrack
Controller
Front View of a Controller Enclosure
Icon Description
Enclosure ID indicator
Enclosure location indicator

1. Blinking blue: The controller
enclosure is being located.
2U controller enclosure (disk and controller integration) 2. Off: The controller enclosure is
not located.
Enclosure alarm indicator
1. Steady amber: An alarm is
reported by the controller
enclosure.
2. Off: The controller enclosure is
working properly.
Power indicator/Power button

4U controller enclosure (disk and controller separation)
Rear View of a Controller Enclosure
1 2 3 4 5
No. Description
1 Management port
2 Maintenance port
6 7 3 Serial port
4 Interface module
5 Power-BBU module
6 SAS expansion port
7 Interface module
8 Management module
9 Power module
8 9
Controller
 A controller is the core component of a storage system. It processes storage
services, receives configuration management commands, saves configuration
data, connects to disks, and saves critical data to coffer disks.
Controller enclosure
FE FE
Controller Controller
Cache Cache
CPU CPU
BE BE
Disk
enclosure
Cache data
BBU and Fan Module
BBU latch Fan latch
Fan module
Running/Alarm Running/Alarm
indicator of the BBU indicator of the fan
BBU Front view
Coffer Disk
2.5-inch coffer disk Palm-sized NVMe coffer SSD
Alarm/Location indicator Alarm/Location indicator

Running indicator Running indicator
Latch Latch
Handle Handle
Disk Disk
Label Label
Power Module
 The AC power module supplies power to the controller enclosure, allowing the
enclosure to operate normally at maximum power. Running/
Alarm
Handle indicator Latch
Power socket
Contents
2. Disk Enclosure
3. Expansion Module
4. Disk
5. Interface Module
Disk Enclosure
 The disk enclosure uses a modular design and consists of a system subrack,
expansion modules, power modules, and disks.
Power
Module
Expansion
Module
System Subrack
Disk Drive
Module
Front View of a Disk Enclosure
Icon Description
ID indicator of the disk enclosure
Location indicator of the disk enclosure

1. Blinking blue: The disk enclosure is being located.
2. Off: The disk enclosure is not located.
2 U 25-slot SAS disk enclosure
Alarm indicator of the disk enclosure
1. Steady yellow: An alarm is reported by the disk
enclosure.
2. Off: The disk enclosure is working properly.
Power indicator of the disk enclosure
1. Steady green: The disk enclosure is powered on.
2 U 36-slot smart NVMe disk enclosure 2. Off: The disk enclosure is powered off.
Power indicator/Power button
1. The disk enclosure is powered on and off with the
controller enclosure. The power button on the disk
Note: This slide shows the front views of a 2 U SAS enclosure is invalid and cannot be used to power
disk enclosure and a 2 U smart NVMe disk enclosure on or off the disk enclosure separately.
of Huawei OceanStor Dorado V6.
Rear View of a Disk Enclosure
4
No. Description
1 Serial port
2 Mini SAS HD expansion port
3 ID display
4 Expansion module
1 2 3 5
5 Power module
2 U SAS disk enclosure 6 Onboard expansion port
7 Onboard management port
8 Power module
Note: This slide shows the rear

views of the 2 U smart SAS and
6 7 8
smart NVMe disk enclosures of
2 U smart NVMe disk enclosure Huawei OceanStor Dorado V6.
Contents
2. Disk Enclosure
3. Expansion Module
4. Disk
5. Interface Module
Expansion Module
Expansion module of a 2 U SAS disk enclosure

Connects to a controller enclosure through expansion ports
Expansion module of a 2 U smart NVMe disk enclosure

Connects to a controller enclosure through expansion ports
CE Switch
Rear view
48 x 10GE electrical ports 4 x 60 Gbit/s optical ports
Console
Front view
USB port FAN1 FAN2 PWR1 PWR2
Two Ethernet management ports (combo)
Note: Huawei CE6800 series switches are used as an example.
Fibre Channel Switch
Management ports
(serial port and
Ethernet port) USB port 24 Fibre Channel ports Power socket
Three link
aggregation groups
Note: Huawei SNS2124 is used as an example.
Device Cables
1. Serial cable 2. Mini SAS HD 3. Mini SAS HD 4. AOC cable

electrical cable optical cable
5. 100G 6. 25G SFP28 7. FDR cable 8. MPO-4*DLC 9. Optical fiber

QSFP28 cable cable optical fiber
Contents
2. Disk Enclosure
3. Expansion Module
4. Disk
 HDD
 SSD
5. Interface Module
Disk Type
IDE
SCSI
SATA
1.8-inch SAS Interface
2.5-inch FC type
3.5-inch Dimensions
NVMe
5.25-inch ... Enterprise-class
Application
... scenario Desktop-class
...
What are the types of disks?
HDD
SSD Structure
...
HDD Structure
 An HDD consists of platters, an actuator arm, read/write heads, a spindle, a
port, and control circuits.
Platter
Actuator arm
Spindle
Control circuit
Port
Read/write head
HDD Working Principles
Basic
operation The platter is
driven by a motor.
Platter
Landing zone
Spindle Magnetic data

R/W Head
The distance between the

The head flies head and the disk is small.
over the platter.
Data Organization on a Disk
Sector Track
Head
Cylinder
Actuator
Platter arm
Motor
Motor
Disk Capacity and Cache
 Disk capacity
 Disk capacity = Number of cylinders x Number of heads x Number of sectors x 512
bytes. The unit is MB or GB. The disk capacity is determined by the capacity of a
single platter and the number of platters.
 Cache
 Because the processing speed of a CPU is much faster than that of a disk, the CPU
must wait until the disk completes a read/write operation before issuing a new
command. To solve this problem, a cache is added to the disk to improve the
read/write speed.
Factors Relevant to Disk Performance
Primary factor that determines the

Rotation speed throughput in the case of sequential I/Os
Primary factor that affects the random I/O

Seek speed performance
Single platter
Indirect factor for disk performance
capacity
The least important factor for disk

Port speed performance
Average Access Time
 The average access time is determined by:
 Average seek time
 Average latency time
Seek time Latency Wait time
Disc
Data Block
Seek
Tracks
Data Transfer Rate
 The date transfer rate is determined by:
 Internal transfer rate
 External transfer rate/Interface transfer rate
Disk Disc
Seek
Tracks
External
Internal
Disk IOPS and Transmission Bandwidth
 IOPS
 Input/Output operations per second (IOPS) is a key indicator to measure disk
performance.
 IOPS is calculated by the seek time, rotation latency, and data transmission time.
 Transmission bandwidth (throughput)

 Indicates the amount of data that is successfully transmitted in a unit time, that is,
the speed at which data streams are transmitted. For example, if it takes 10s to write
10,000 files of 1 KB size, the transmission bandwidth is only 1 MB/s; if it takes 0.1s to
write a 10 MB file, the transmission bandwidth is 100 MB/s.
Parallel and Serial Transmission
 For example, the methods for transmitting numbers 1 to 8 are as follows:
Parallel transmission Serial transmission
1
2
3 8 7 6 5 4 3 2 1
Transmit 4 Receive Transmit Receive
end 5 end end end
6
7
8
Multiple lines are connected between two ends, Only one line is connected between two ends. Eight
and one number is transmitted on each line. numbers are sent on this line in sequence. The receive
end has all numbers after eight transmissions.
Disk Port Technology
 A disk must provide a simple port for users to access its data. Generally, disks
provide the following physical ports:
IDE port
Used for the ATA
instruction system
SATA port
Disk
Ports Parallel SCSI port
Used for the SCSI

Serial SCSI (SAS) port
instruction system
Fibre Channel port
IDE Disk Port
 The integrated drive electronics (IDE) port is also called the parallel ATA port.
 ATA stands for Advanced Technology Attachment.
 The ATA disk is also called the IDE disk.
 The ATA port uses the parallel ATA technology.
SATA Port
 SATA is short for serial ATA.
 SATA ports use serial transmission and provide a higher rate than IDE ports.
 SATA uses a point-to-point architecture and supports hot swap.
SATA Version Line Code Transfer Rate Throughput

1.0 8b/10b 1.5 Gbit/s 150 MB/s
2.0 8b/10b 3 Gbit/s 300 MB/s
Power 3.0 8b/10b 6 Gbit/s 600 MB/s
SATA Port
SCSI Port
 SCSI is short for Small Computer System Interface.
SAS Port
 SAS is short for Serial Attached SCSI.
 SAS is a point-to-point, full-duplex, and dual-port interface.
 SAS is backward compatible with SATA.
 Rate: 600 Mbit/s per channel
 SAS features high performance, high reliability, and powerful scalability.
Fibre Channel Port
 Fibre Channel disks use the Fibre Channel arbitrated loop (FC-AL).
 FC-AL is a dual-port serial storage interface based on the SCSI protocol.
 FC-AL supports full-duplex mode.
 Fibre Channel provides a universal hardware transmission platform for upper-layer protocols
(SCSI and IP). It is a serial data transmission interface that features high speed, high reliability,
low latency, and high throughput.
40-pin Male FC-SCA II Connector
Contents
2. Disk Enclosure
3. Expansion Module
4. Disk
 HDD
 SSD
5. Interface Module
SSD Overview
 Compared to HDDs, SSDs have absolute advantages in terms of performance, reliability,
power consumption, and portability. SSDs have been widely used in various industries.
 SSD characteristics:
 Uses NAND flash to save data, providing a faster speed than HDDs.
 Has no mechanical structure inside, so it consumes less power, dissipates less heat, and
generates less noise.
 Its service life is determined by the number of program/erase (P/E) cycles.
SSD Architecture
 An SSD consists of a control unit and a storage unit (mainly flash memory
chips).
 Control unit: SSD controller, host interface, and DRAM
 Storage unit: NAND flash
RAM
Flash Flash
SSD Controller ...
Pkg Pkg
Processor
Host Host NAND Flash Flash
interface flash Pkg Pkg ...
Interconnect logic Buffer interface
manager
NAND Flash
 Internal storage units in NAND flash Page 0 Page 0
Page 1 Page 1
include:
...
...
Page P Page P
 LUNs, planes, blocks, pages, and cells Block 0 Block 1
Page 0 Page 0
Operations on the NAND flash include
Logical Unit 0

Page 1 Page 1
...
...
erase, program, and read. Page P Page P
Block 2 Block 3
 NAND flash is a non-volatile medium. A
...
...
block must be erased before new data is Page 0 Page 0
Page 1 Page 1
written to it. A program/erase (P/E) cycle
...
...
Page P Page P
is the process of erasing a block and then Block B Block B+1
Page Register
writing it again. Page Register
Plane Plane
Address 0 Address 1
SLC, MLC, TLC, and QLC
1111
111 1110
11 110 1101
1100
1 101 1011
10 100
1010
1001
1000
011 0111
01 010 0110
0101
0 001 0100
00 000
0011
0010
0001
0000
SLC-1bit MLC-2bit TLC-3bit QLC-4bit

SLC MLC TLC QLC
1. Supports 50,000 to 100,000 1. Supports about 3,000 P/E cycles. 1. Provides higher data density and 1. The capacity is further
P/E cycles, providing the 2. The speed is slower than that of supports only several hundred to improved by 33%.
best reliability. SLC. 1,000 P/E cycles. 2. The performance and life
2. The storage capacity is 3. The storage capacity is relatively 2. The reliability and performance cycle are further reduced.
small. large. are low.
3. The cost is the highest. 4. The price is relatively low. 3. Generally used in personal
devices due to the cost
advantage, but cannot meet the
requirements of enterprise
products.
Flash Chip Data Relationship
Plane Die
1478 blocks 2 planes
Cell Page Block
146688 cells 768 pages

...
... ... ...
...
... ...
Page is the minimum read/write unit, and block is the minimum program/erase unit.
Address Mapping Management
Logical block address (LBA) No. 26, XX Road, Binjiang District, Hangzhou City,
Zhejiang Province, People's Republic of China
Physical block address (PBA) 120º 12' east longitude, 30º 16' north latitude
HDD: The relationship between LBA and PBA is fixed.

 Overwrite
The Flash Translation
Layer (FTL) is responsible
SSD: The relationship between LBA and PBA is not fixed. for the conversion
 Non-overwrite: A block must be erased before new data is between the LBA and PBA.
written to it. New data and old data are at different
locations.
FTL
Sector
0
Sector
2
Sector 3 Main controller
FTL mapping table: saved in the Sector
1
internal SRAM/DRAM, external
Sector 2 DRAM, or NAND flash. Sector
4
Sector Sector
Sector 0 Sector 1 3 5
OS sector (512 FTL mapping Data is stored in the

bytes). File systems operation. The main NAND physical
read/write data in the controller maps the addresses based on
unit of 512 bytes. addresses based on the mapping table.
the mapping table.
Data Write Process on an SSD (1)
 The following uses eight channels as an example to demonstrate how the host writes data to the
SSD.
Channel 0 block Channel 1 block Channel 2 block Channel 3 block
Writes 4 KB
of data
Writes 16 KB
of data
4 KB
SSD controller
Data Write Process on an SSD (2)
 When the SSD is full, old data must be deleted to release space for new data. When a user
deletes and writes data, data in some blocks becomes invalid or aged.
SSD controller
Data Read Process on an SSD
Reads 4 KB Channel 0 block Channel 1 block Channel 2 block Channel 3 block
of data
Reads 32 KB
of data 4 KB
SSD controller
SSD Performance Advantages
SSD Performance Advantages Power consumption under 100,000 read IOPS
I/O I/O
IP/FC SAN
Seek time
Mechanical latency
2 SSDs 250 HDDs
Power (W)
4000
About 400-fold
2000
VS
HDD storage system SSD storage system SSD FC HDD
Use of SSDs in Storage Systems
 Class A applications: high-concurrency applications featuring random reads and writes, such as databases
 Class B applications: large files, images, and streaming media featuring sequential reads and writes
 Class C applications: data backup or rarely used applications
Access frequency
A SSD media
FC/SAS disk
SATA/NL-SAS/Tape
C
Data distribution
Contents
2. Disk Enclosure
3. Expansion Module
4. Disk
5. Interface Module
GE Interface Modules
GE electrical interface module 40GE interface module 100GE interface module
SAS Expansion Module and RDMA Interface Module
25 Gbit/s RDMA 100 Gbit/s RDMA 12 Gbit/s SAS

interface module interface module expansion module
SmartIO Interface Module
PCIe and 56 Gbit/s IB Interface Modules
PCIe interface module 56 Gbit/s InfiniBand interface module
Fibre Channel and FCoE Interface Modules
Power Power
indicator/Hot indicator/Hot Handle
Handle swap button
swap button
16 Gbit/s Fibre
Channel port 10 Gbit/s
FCoE port
Link/Speed
indicator of
the port Link/Speed
indicator of a 10
Gbit/s FCoE port
16 Gbit/s Fibre Channel interface module 10 Gbit/s FCoE interface module
Quiz
1. What are the types of SSDs?
A. SLC
B. MLC
C. TLC
D. QLC
2. Which of the following can be used to measure the performance of an HDD?

A. Disk capacity
B. Rotation speed
C. Data transfer rate
D. Average access time
Summary
Controller
Controller enclosure Coffer disk
Disk enclosure BBU
Expansion module
Expansion module
Intelligent storage components Device cables
HDD
Disk
SSD
Interface module
More Information
Enterprise Huawei
Recommendations

 Popular tools
 HedEx Lite
intelligent world.


RAID Technologies
Foreword
 This course introduces technologies of traditional RAID and RAID 2.0+. The
evolution of RAID technologies aims at data protection and performance
improvement.
Objectives
After completing this course, you will be able to understand:

 Common RAID levels
 Different levels of data protection provided by different RAID levels
 Working principles of RAID 2.0+
 Dynamic RAID and RAID-TP
Contents
1. Traditional RAID
2. RAID 2.0+
3. Other RAID Technologies
Background
 Problems in traditional computer systems must be addressed.
Instructions
processed per
second
CPU > 1 million Disks become the system performance bottleneck.
Operations on disks are limited, making it impossible to

RAM > 100,000 provide large capacities.
Data is stored on individual disks, making it impossible

< 300 to provide consistent high data reliability.
Disk
What Is RAID?
 Redundant Array of Independent Disks (RAID) combines multiple physical disks into one
logical disk in different ways, for the purposes of read/write performance and data
security improvement.
 Implementations: hardware RAID and software RAID.
How large is
a logical disk?
Logical disk
Physical Physical Physical Physical

disk disk disk disk
Data Organization Forms
 Disk striping: Space in each disk is divided into multiple strips of a specified size. Data is
also divided into blocks based on strip size when data is being written.
 Strip: A strip consists of one or more consecutive sectors in a disk, and multiple strips
form a stripe.
 Stripe: A stripe consists of strips of the same location or ID on multiple disks in the
same array.
Disk 1 Disk 2 Disk 3

D6 D7 D8 Stripe 2 Depth of a stripe
D3 D4 D5 Stripe 1
D0 D1 D2 Stripe 0
Data strips in Data strips in Data strips in
a disk a disk a disk
Data Protection Techniques
 Mirroring: Data copies are stored on another redundant disk.
 Exclusive or (XOR)
 XOR is widely used in digital electronics and computer science.
 XOR is a logical operation that outputs true only when inputs differ (one is true, the other is
false).
 0 ⊕ 0 = 0, 0 ⊕ 1 = 1, 1 ⊕ 0 = 1, 1 ⊕ 1 = 0
Physical disk 1 Physical disk 2 Parity disk
1 1 0
0 1 1
0 0 0
XOR for redundant backup
Common RAID Levels and Classification Criteria
 RAID levels use different combinations of data organization forms and data
protection techniques.
Consists of block-level striping with

RAID 6 double distributed parity.
Consists of striping, but
no mirroring or parity. RAID 0
RAID 0 is implemented after RAID

RAID 10
Consists of data mirroring, Common RAID levels 1 is implemented.
without parity or striping. RAID 1
RAID 0 is implemented after RAID

RAID 50
5 is implemented.
Consists of byte-level striping
RAID 3
with dedicated parity.
Consists of block-level striping RAID 5

with distributed parity.
How Does RAID 0 Work
Write data to D 2, Read data from D 2,
D 3... D 3...
Write data to D 1. Read data from D 1.
D0 Write data to D 0. Read data from D 0.
D5 D 0, D 1, D 2, D 3, D 4, D 5
D4
D3
Physical disk 1 Physical disk 2
D2 D6
D4 D5 Stripe 2
D1
D2 D3 Stripe 1
D0
D0 D1 Stripe 0
Logical disk Data strips in a disk Data strips in a disk

Stripping without error check
Just a Bundle Of Disks (JBOD)
Write data to and read data from D 2.

D2 D 0, D 1, and D 2 pass through a mirror.
D1
Physical disk 1 Physical disk 2

D0
D2 D2
D1 D1
Logical disk D0 D0
Disk array with mirroring
Write data to C.
Write data to B.
Read data.
Write data to A.
C
A 0, A 1, A 2, B 0, B 1, B 2, C 0, C 1, C 2
Physical disk 1 Physical disk 2 Physical disk 3 Parity disk
A C0 C1 C2 P3
B0 B1 B2 P2
A0 A1 A2 P1
Logical disk
Note: A write penalty occurs when just a small amount of new data needs to be written to one or two disks.
Write data.
Read data.
D5
D 0, D 1, D 2, D 3, D 4, D 5
D4
D3
D2
Physical disk 1 Physical disk 2 Physical disk 3
D1
P2 D4 D5
D0
D2 P1 D3
D0 D1 P0
Logical disk
Independent disk structure with distributed parity check codes
RAID 6
 RAID 6
 Requires at least N + 2 (N > 2) disks and provides extremely high data reliability and
availability.
 Common RAID 6 technologies:
 RAID 6 P+Q
 RAID 6 DP
How Does RAID 6 P+Q Work?
 P and Q parity data is calculated. A maximum of two data blocks that are lost can be recovered
using P and Q parity data. Formulas for calculating P and Q parity data are as follows:
 P = D 0 ⊕ D 1 ⊕ D 2...
 Q = (α * D 0) ⊕ (β * D 1) ⊕ (γ * D 2)...
Physical disk 1 Physical disk 2 Physical disk 3 Physical disk 4 Physical disk 5
P1 Q1 D0 D1 D2 Stripe 0
D3 P2 Q2 D4 D5 Stripe 1
D6 D7 P3 Q3 D8 Stripe 2
D9 D 10 D 11 P4 Q4 Stripe 3
Q5 D 12 D 13 D 14 P5 Stripe 4
How Does RAID 6 DP Work?
 Double parity (DP) adds another disk in addition to the horizontal XOR parity disk used in RAID 4 to store
diagonal XOR parity data.
 P0 to P3 in the horizontal parity disk represent the horizontal parity data for respective disks.
 For example, P0 = D0 XOR D1 XOR D2 XOR D3
 DP 0 to DP 3 in the diagonal parity disk represent the diagonal parity data for respective data disks and the
horizontal parity disk.
 For example, DP 0 = D 0 XOR D 5 XOR D 10 XOR D 15
Physical Physical Physical Physical Horizontal Diagonal

disk 1 disk 2 disk 3 disk 4 parity disk parity disk
D0 D1 D2 D3 P0 DP 0 Stripe 0
D4 D5 D6 D7 P1 DP 1 Stripe 1
D8 D9 D 10 D 11 P2 DP 2 Stripe 2
D 12 D 13 D 14 D 15 P3 DP 3 Stripe 3
How Does RAID 10 Work?
 RAID 10 consists of nested RAID 1 + RAID 0 levels and allows disks to be mirrored
(RAID 1) and then striped (RAID 0). RAID 10 is also a widely used RAID level.
User data D 0, D 1, D 2, D 3, D 4, D 5
Disk mirror Disk mirror
D4 D4 D5 D5
D2 D2 D3 D3
D0 D0 D1 D1
Physical disk 1 Physical disk 2 Physical disk 3 Physical disk 4

RAID 1 RAID 1
RAID 0
How Does RAID 50 Work?
 RAID 50 consists of nested RAID 5 + RAID 0 levels. RAID 0 is implemented after RAID 5
is implemented.
D 0, D 1, D 2, D 3, D 4, D 5, D 6, D 7...
D 0, D 1, D 4, D 5, D 8, D 9 D 2, D 3, D 6, D 7, D 10, D 11
P4 D8 D9 P5 D 10 D 11 Stripe 2
D4 P2 D5 D6 P3 D7 Stripe 1
D0 D1 P0 D2 D3 P1 Stripe 0
Physical Physical Physical Physical Physical Physical
disk 1 disk 2 disk 3 disk 4 disk 5 disk 6
RAID 5 RAID 5
RAID 0
Contents
1. Traditional RAID
2. RAID 2.0+
RAID Evolution
Hot
spare
Traditional RAID LUN virtualization Block virtualization
How Does RAID 2.0+ Work?
Extent
LUN Extent
Extent
Extent ... ... Hot spare

space
CKG ... ...
CK ... ... ... ... ... ...
Disk
Disk 0 Disk 1 Disk k Disk n
Reconstruction
Traditional RAID (many-to-one) RAID 2.0+ (many-to-many)
01 02 03 51 52 53 CKG 0 (RAID 5)
HDD 0 HDD 5
HDD 0 04 05 06 HDD 5 54 55 56
Hot spare 07 08 09 57 58 59
HDD 1 HDD 6 RAID 5 (4 + 1) 11 12 13 61 62 63
HDD 1 14 15 16 HDD 6 64 65 66
17 18 19 67 68 69 CKG 1 (RAID 5)
HDD 2 HDD 7 21 22 23 71 72 73
HDD 2 24 25 26 HDD 7 74 75 76
27 28 29 77 78 79
HDD 3 HDD 8 31 32 33 81 82 83
HDD 3 34 35 36 HDD 8 84 85 86 CKG 2 (RAID 5)
37 38 39 87 88 89 52 13 63 74 85
HDD 4 HDD 9
41 42 43 91 92 93
Hot spare disk HDD 4 44 45 46 HDD 9 94 95 96 Unused CK
Hot spare
47 48 49 97 98 99 block space
Logical Objects
Storage pool LUNs that can be
Chunk CKG Extent Volume
consisting of viewed on the host
physical disks
Tiered
Not tiered
A CKG is
divided into Not tiered
Multiple types of Space provided by each Chunks from spaces of a
Several extents
disks are added to disk is divided into fine- different disks smaller LUNs can be created quickly.
form one volume.
a storage pool. grained chunks. form a CKG. granularity.
Disk Domain
 A disk domain is a combination of disks (which can be all disks in the array). After the disks are
combined and reserved for hot spare capacity, it provides storage resources for the storage pool.
Physical disks Disk domain #1
Tiers
High-performance tier
Performance tier
Disk domain #2
Capacity tier
Storage Pool and Tier
 A storage pool is a storage resource container. The storage resources used by application servers are all from
storage pools.
 A storage tier is a collection of storage media providing the same performance level in a storage pool.
Different storage tiers manage storage media of different performance levels and provide storage space for
applications that have different performance requirements.
Storage Supported
Tier Type Application
Tier Disk Type RAID Level RAID Policy
High- Best for storage of data that is RAID 1 1D + 1D, 1D + 1D + 1D + 1D
Tier 0 performance SSD frequently accessed with high
tier performance and price. 2D + 2D or 4D + 4D, which is automatically
RAID 10
selected by a storage system.
Best for storage of data that is less
Performance frequently accessed with relatively RAID 3 2D + 1P, 4D + 1P, 8D + 1P
Tier 1 SAS
tier high performance and moderate RAID 5 2D + 1P, 4D + 1P, 8D + 1P
price.
(2D + 1P) x 2, (4D + 1P) x 2, or (8D + 1P) x
Best for storage of mass data that RAID 50
2
is infrequently accessed with low
Tier 2 Capacity tier NL-SAS RAID 6 2D + 2P, 4D + 2P, 8D + 2P, 16D + 2P
performance and price, and large
capacity per disk.
Disk Group
A disk group (DG) is a set of disks of the same type in a disk domain. The disk
type can be SSD, SAS, or NL-SAS.
SSD
Disk type
SAS NL-SAS
Logical Drive
A logical drive (LD) is a disk that is managed by a storage system and corresponds
to a physical disk.
LD 0 LD 1 LD 2 LD 3
Disk 0 Disk 1 Disk 2 Disk 3
Chunk
A chunk (CK) is a disk space of a specified size allocated from a storage pool. It is
the basic unit of a RAID array.
Chunk Chunk
HDD 0 HDD 1 HDD 2 HDD 3 HDD 4
Chunk Group
A chunk group (CKG) is a logical storage unit that consists of CKs from different
disks in the same DG based on the RAID algorithm. It is the minimum unit for
allocating resources from a disk domain to a storage pool.
CKG CKG
Disk Disk
CK
DG DG
Extent
Each CKG is divided into logical storage spaces of a fixed and adjustable size called
extents. Extent is the minimum unit (granularity) for migration and statistics of
hot data. It is also the minimum unit for space application and release in a storage
pool.
LUN 0 (thick)
Extent
CKG
LUN 1 (thick)
Grain
When a thin LUN is created, extents are divided into blocks of a fixed size, called
grains. A thin LUN allocates storage space by grains. Logical block addresses
(LBAs) in a grain are consecutive.
LUN (thin)
Extent Grain
CKG
Volume and LUN
 A volume is an internal management object in a storage system.
 A LUN is a storage unit that can be directly mapped to a host for data reads and writes.
A LUN is the external embodiment of a volume.
Server
LUN
Volume Storage
Contents
1. Traditional RAID
2. RAID 2.0+
Huawei Dynamic RAID Algorithm
Common RAID algorithm Huawei dynamic RAID algorithm
 When a block in a RAID array fails, recover the data in the faulty  When a block in a RAID array fails, recover and migrate the data in
block, migrate all the data in the RAID array, and then shield the the faulty block, shield the faulty block, and reconstruct a new
RAID array. RAID array using remaining blocks.
 Result: A large amount of available flash memory space is wasted.  Benefit: The flash memory space is fully and effectively used.
4. Shield and obsolete the faulty RAID array, which wastes space. 4. Reconstruct a new RAID array using remaining blocks to store data.
ch 0 ch 1 ch n-1 ch n ch P ch 0 ch 1 ch n-1 ch n ch P
PBA 0 16 17 ...
… 100 60 P0 PBA 0 16 17 ... 100 60
60 PPm+2
0
1. A block in a RAID array fails.
1. A block in a RAID array fails.
PBA 1 101 160 … 10 11 P1 PBA 1 101 160 ... 10 11 P1
PBA m 3000 1280 … n n+1 Pm PBA m 3000 1280 ... n n+1 Pm
2. Create a new RAID array to store the data of the RAID array where a block fails. 2. Create a new RAID array to store the data in the faulty block.
PBA m+1 P m+1 PBA m+1 P m+1

3. Recover the data in the faulty block using the RAID 3. Recover the data in the faulty block using the RAID
algorithm and migrate all the data in the RAID array. algorithm and migrate the data.
RAID-TP
 RAID protection is essential to a storage system for consistent high reliability and performance. However, the
reliability of RAID protection is challenged by uncontrollable RAID array construction time due to drastic
increase in capacity.
 RAID-TP achieves the optimal performance, reliability, and capacity utilization.
Tolerates failures of up to three disks RAID-TP

with zero service interruptions.
Traditional
RAID
Huawei RAID-TP: • Greatly reduces reconstruction time.

• Tolerates failures of up to three disks. • Effectively copes with data protection challenges in
the era of large-capacity disks.
Quiz
1. What is the difference between a strip and stripe?
2. Which RAID level would you recommend if a user focuses on reliability and
random write performance?
3. Is it true or false that data access will remain unaffected when any disk in a RAID
10 array fails?
Summary
RAID 0, RAID 1, RAID 3, RAID 5 and RAID 6

Traditional RAID
RAID 10 and RAID 50
RAID Technologies RAID 2.0+ RAID 2.0+
Dynamic RAID
Other RAID
technologies
RAID-TP
More Information
Enterprise Huawei
Recommendations

 Popular tools
 HedEx Lite
intelligent world.


Common Storage Protocols
Foreword
 A protocol is a set of conventions that both communication computers

must comply with. For example, how to set up a connection and how to
identify each other.
 A protocol not only defines the language used for communication, but also
specifies the hardware, transmission medium, transmission protocol, and
interface technology. This course describes the definitions and principles of
different storage protocols.
Objectives
Through this course, you are expected to:

 Learn about common protocols used in storage systems.
 Understand the working principles and features of the protocols.
Contents
1. SCSI
2. iSCSI, Fibre Channel (FC), and FCoE
3. SAS and SATA
4. PCIe and NVMe
5. RDMA and (InfiniBand) IB
6. CIFS, NFS, and NDMP
SCSI Protocol
 Small Computer System Interface (SCSI) is a huge
protocol system evolved from SCSI-1 > SCSI-2 > SCSI device instruction set
(SBC/SSC)
SCSI-3.
 The SCSI protocol defines a model and a necessary
instruction set for different devices to exchange SCSI system model
information by using the framework. (SAM/SPC)
 The SCSI protocol is irrelevant to transmission

media, that is, it can be implemented on various
SCSI link implementation
media, and even virtual media. (FCP/SAS/iSCSI)
SCSI Evolution
SCSI-1
 Launched within 1983 to
1985.
SCSI-1  Supports synchronous and
asynchronous modes. SCSI-2
 Supports up to seven 8-bit
devices.  Launched within 1988 to
 Provides up to 5 Mbit/s speed. 1994.
 Uses 50-pin cables that span  Compatible with SCSI-1.
6 m at most. Supports 16-bit
SCSI-3

 Out of use. bandwidth.

Provides up to 20 Mbit/s
SCSI-2

 Standardized in 1993.
speed.  Compatible with SCSI-1 and
SCSI-2.
 Becomes a standard system.
 Supports various media such
SCSI-3 as FCP and IEEE1394.
SCSI Logical Topology
Initiator
Initiator 1 Initiator 2
SDS
Target
Target 1 Target 2 Target 3
LUN 0
LUN 2
LUN 5
LUN namespace Target device
SCSI Initiator Model
 Generally, the SCSI system of a host works in the initiator mode. The SCSI
architecture on Windows, Linux, AIX, Solaris, and BSD contains the architecture
layer (middle layer), device layer, and transport layer.
SCSI device driver layer
SCSI middle layer
SCSI link layer
SCSI Target Model
 Based on the SCSI architecture, a target is divided into
three layers: port layer, middle layer, and device layer.
Port layer
 The most important part is the middle layer, at which
LUN namespaces, link ports, target devices, tasks, task
sets, and sessions are managed and maintained based Middle layer
on SAM/SPC specifications.
 Drivers at the port layer are dynamically loaded in the
Device layer
form of registration. Drivers at the device layer are also
dynamically loaded.
SCSI Protocol and Storage System
 The SCSI protocol is the basic protocol used for communication between hosts
and storage devices.
 DAS uses the SCSI protocol to achieve interconnection between hosts and
storage devices.
SCSI bus
Host adapter Data/Address bus

SCSI ID 7
Control signal
SCSI array SCSI array
ID 0 ID 5
LUN 0 LUN 1 LUN 0

LUN 2 LUN 1
SCSI Protocol Addressing
Bus
number Differentiates SCSI buses.
Device Differentiates devices

ID on SCSI buses.
Logical
Differentiates sub-devices
unit
number in SCSI devices.
Contents
1. SCSI
2. iSCSI, FC, and FCoE
3. SAS and SATA
4. PCIe and NVMe
5. RDMA and IB
Emergence of iSCSI
SCSI allows a small number of

devices to be connected.
The distance between devices is
limited.
IP-network-based SCSI: iSCSI
iSCSI
SCSI applications (file systems and databases)
SCSI block SCSI flow Other SCSI SCSI commands, responses, and data
instructions instructions instructions
SCSI instructions, data, and status

Receives SCSI data, generates iSCSI
protocol data, and encapsulates
iSCSI
the data into iSCSI PDUs.
TCP Encapsulates iSCSI PDUs into

TCP/IP packets for transmission
and reception.
IP
Converts bit streams and transmits
Ethernet them over physical links.
iSCSI protocol stack
iSCSI Initiator and Target
 Initiator iSCSI
 The SCSI layer generates command descriptor blocks (CDBs) Initiator Target
and transfers them to the iSCSI layer. SCSI SCSI

 The iSCSI layer generates iSCSI protocol data units (PDUs)
and sends them to the target over an IP network. iSCSI iSCSI
 Target
 The iSCSI layer receives PDUs and sends CDBs to the SCSI TCP TCP
layer.
 The SCSI layer interprets CDBs and gives responses when IP IP
necessary.
Link Link
iSCSI Architecture
 iSCSI nodes encapsulate SCSI instructions and data into iSCSI packets and send the packets to the
TCP/IP layer, where the packets are encapsulated into IP packets to be transmitted over an IP
network.
iSCSI node iSCSI node
IP address IP address
of the of the iSCSI
network network Target
port port
iSCSI IP network
Initiator
IP address
IP address
of the
of the iSCSI
network
network Target
port
port
Relationships Between iSCSI and SCSI, TCP and IP
Initiator Function Target
SCSI application SCSI commands, responses, and SCSI application

protocol data protocol
Receives SCSI data, generates iSCSI

protocol data, and encapsulates
iSCSI protocol the data into iSCSI PDUs. iSCSI protocol
Encapsulates iSCSI PDUs into

TCP/IP protocol TCP/IP packets for transmission TCP/IP protocol
stack and reception. stack
Performs 8-bit/10-bit encoding, as
well as transmits and receives
NIC driver data. NIC driver
Performs 0/1 code stream

transmission.
Physical Physical
FC in Storage
 FC can be referred to as the FC protocol, FC network, or FC interconnection. As FC delivers high
performance, it is gradually used for front-end host access on point-to-point and switch-based
networks.
 FC brings the following advantages to the storage network:
 The scalability is improved.
 The transmission distance is increased. Initiator
Host Initiator
 Security problems are solved.
FC switch FC switch
Target Target Disk Disk

Storage
enclosure enclosure
FC Protocol Structure
Upper-layer protocol
SCSI-3 IP ATM
FC-4 IPI-3 SCSI-3 FC-LE

Command Command Link
FC-ATM
set mapping set mapping encapsulation
FC-3 General equipment
FC-2 Structure protocol FC-AL FC-AL2

FC-PH
FC-1 Coding/Decoding FC-PH2
FC-0 FC-PH3 Copper cables and optical cables,
Physical conversion
8-bit/10-bit encoding
FC Topology
Point-to-point FC-AL FC switching network
Most widely used technology

Only two devices can Up to 127 devices
be connected. Up to 16 million devices
can be connected. can be connected.
(Direct connection)
Seven Types of Ports for the FC Protocol
 On an FC network, there are seven types of ports.
FC terminal N F FC switch F N FC terminal
FL
Fabric device Fabric device
FC FC
terminal terminal
NL NL
Open ring device Open ring device
FC-AL device
L L L
FC FC FC
terminal terminal terminal
Private ring device Private ring device Private ring device
FC Adapter
 The FC host bus adapter (HBA) supports FC network applications and provides
high-bandwidth and high-performance storage network solutions.
FCoE Protocol
 The FCoE protocol is used to transmit FC signals over lossless enhanced
Ethernet infrastructure.
 FCoE encapsulates FC data frames in Ethernet frames and allows service traffic
on a LAN and SAN to be transmitted over the same Ethernet.
Ethernet data link
layer frame
 Service flow IP address
 Block storage FCoE
 VoIP call
 Video stream VoIP
Comparison Between FC and FCoE
 FCoE: defines the mapping from FC to
IEEE 802.3 Ethernet, and uses the physical
FC-4 FC-4
layer and data link layer of the Ethernet
FC-3 FC levels
FC-3 (No changes)
and the network layer, service layer, and FC-2V FC-2V
protocol layer of FC. FC-2 FC-2M
FC_BB_E
FCoE entity Mapping
FC-2P
 FCoE retains the protocol stack above FC-
FC-1 MAC IEEE
2 and replaces FC-0 and FC-1 with the FC-0 PHY
802.3
Layers
link layer of the Ethernet. FCoE protocol stack
Contents
1. SCSI
3. SAS and SATA
4. PCIe and NVMe
5. RDMA and IB
Background of SAS
• The parallel bus has been developed to the peak and the bandwidth limit is
reached.
• Serial buses such as FC, IB, and the Ethernet have the following disadvantages for
storage applications:
- FC: It is expensive, and applicable to complex networking and long-distance
scenarios.
- IB: It is expensive, and the networking is complex.
- iSCSI: The latency is high, and the transmission rate is low.
SCSI in serial mode: SAS
What is SAS
 SAS is the serial standard of the SCSI bus protocol.
 SAS uses the serial technology to achieve higher transmission rate and better scalability, and is
compatible with SATA disks.
 SAS adopts the point-to-point architecture to achieve a transmission rate of up to 3 Gbit/s, 6
Gbit/s, 12 Gbit/s, or higher. The full-duplex mode is supported.
SAS Protocol Layers
SCSI application layer ATA application layer Management application layer Application layer
SSP transport layer STP transport layer SMP transport layer Transmission layer
SAS port layer Port layer
SSP link layer STP link layer SMP link layer

Link layer
SAS link layer
SAS phy layer PHY layer
SAS physical layer Physical layer
Highlights of SAS
 Provides the serial communication mode to allow multiple data channels to communicate with devices at full
speed.
 Binds multiple narrow ports to form a wide port.
 Uses expanders to expand interfaces, providing excellent scalability.
Expander
 Works in full-duplex mode. Server
SAS Expander
RAID Expander
Controller Wide Expander
Link
Expander
SAS
Read data
RAID Expander
Controller Commands
Scalability of SAS
 SAS uses expanders to expand interfaces. One SAS domain supports a maximum
of 16,384 disk devices. 1
Expander
Expander
Expander
SASRAID
Expander
Controller
1
Expander
Expander
128
128
Cable Connection Principles of SAS
 Generally, a SAS cable has four channels, each of which supports 12 Gbit/s bandwidth.
 SAS devices are connected in the form of a loop (also called a chain).
 A cable supports 4 x 12 Gbit/s bandwidth, which limits the number of disks in the loop.
 A maximum of 168 disks are supported in a loop. That is, a loop consists of a maximum
of seven disk enclosures with 24 disk slots each.
SAS cable connectors:
Mini SAS
High-density mini SAS
SATA
 SATA is short for Serial ATA, which is a kind of computer bus used for data transmission between
the main board and storage devices (disks and CD-ROM drives).
 Instead of simple PATA improvement, the bus structure is brand new.
 A SATA bus uses embedded clock signals and has better error correction capability.
 SATA has better anti-interference capability than PATA.
 SATA, designed for entry-level applications, is not as powerful as SCSI in terms of big data throughput or
multi-thread transmission.
Serial
SAS SATA transmission
Serial
SCSI transmission PATA
Contents
1. SCSI
3. SAS and SATA
4. PCIe and NVMe
5. RDMA and IB
PCIe
 PCIe is short for PCI Express, which is a high-performance and high-bandwidth serial
communication interconnection standard. It was first proposed by Intel and then
developed by the Peripheral Component Interconnect Special Interest Group (PCI-SIG)
to replace the bus-based communication architecture, such as PCI, PCI Extended (PCI-X),
and Accelerated Graphics Port (AGP).
Why PCIe
PCIe is used to obtain significantly improved system throughput,

scalability, and flexibility at lower production costs, which are almost
impossible to achieve using the traditional bus-based interconnection.
High-performance and high-bandwidth serial interconnection standard:

PCIe
PCIe Protocol Structure
 PCIe device layers include the physical layer, data link layer, transaction layer,
and application layer. PCIe Device
 Physical layer AP
 Data link layer

 Transaction layer Transaction
 Application layer Physical Data link
Logical sub-block
Physical
Electrical sub-block
Tx Rx
NVMe
 NVMe is short for Non-Volatile Memory Express.
 The NVMe standard is oriented to PCIe SSDs. Direct connection of the native PCIe channel to the
CPU can avoid the latency caused by the communication between the external controller (PCH) of
the SATA and SAS interface and the CPU.
 PCIe is an interface form and a bus standard, and NVMe is a standard interface protocol
customized for PCIe SSDs.
NVMe Protocol Stack
App Reduced interaction: The number of
communication interactions is reduced from 4 to 2,
reducing the latency.
Block Layer
Controller SSD
1. Transfer command
Controller
SCSI
Initiator NVMe 2. Ready to transfer
SAS
3. Transfer data
SAS 4. Response feedback
1. NVMe write command

Target
SAS NVMe
NVMe 2. NVMe write finished
SCSI
The average I/O latency when NVMe is used

SAS Protocol Stack NVMe Protocol Stack
is less than that when SAS 3.0 is used.
Advantages and Application of NVMe
IOPS
Over Fabric
Fusion Server End-to-end 100GE
FC NVMe-oF
CloudEngine
100GE NVMe-oF
CE8800 End-to-end hardware Reduced by 50%
uninstallation Latency
NVMe-oF protocol
Huawei
OceanStor
FC NVMe-oF
Dorado
Reduced by 66%
TCO
End-to-end DIF
Data integrity protection
NVMe SSD
FC NVMe-oF
Contents
1. SCSI
3. SAS and SATA
4. PCIe and NVMe
5. RDMA and IB
RDMA
 RDMA is short for Remote Direct
Memory Access, which is a method of
Traditional mode RDMA mode
transferring data in a buffer between
application software on two servers over APP Buffer App Buffer
a network.
OS
TCP/IP Buffer
 Low latency OS TCP/IP
Driver Buffer
 High throughput
 Low CPU and OS resource occupancy Buffer
RDMA
Buffer
Adapter Adapter
RDMA Bearer Network
Software RDMA application/ULP
RDMA API (Verbs)
RDMA software stack

Typical hardware
IB transport protocol IB transport protocol IB transport protocol iWARP protocol
UDP TCP
IB network layer IB network layer
IP IP
IB link layer Ethernet link layer Ethernet link layer Ethernet link layer
IB RoCEv1 RoCEv2 iWARP
Ethernet/IP Ethernet/IP Ethernet/IP

IB management
management management management
Content defined by IBTA

Content defined by IEEE/IETF
IB
 Overview:
 The IB technology is specifically designed for server connections, and is widely used for
communication between servers (for example, replication and distributed working), between a
server and a storage device (for example, SAN and DAS), and between a server and a network
(for example, LAN, WAN, and the Internet).
 Highlights:
 Standard-protocol-based
 High bandwidth and low latency
 RDMA
 Transmission uninstallation
IB Architecture
 IB defines a series of devices for system communication, including channel
adapters, switches, and routers.
FCP
TCA
Host interconnect
Host
CPU HCA Switch Router
controller
CPU System main TCA TCA

storage
SCSI Gbit
CPU Ethernet
IB in Storage
Converged storage
Distributed storage
Server
Initiator
Back-end IB Back-end IB
switch switch Switch cascading
FCoE FC TOE 10GE IB
Back-end network
Target Front-end network

Frontend
Storage controller ...
Node Node Node Node
Initiator Backend 1 2 3 n
SAS SAS Distributed cluster
Target
Front-end IB Client
Disk Front-end IB
switch switch
IB Layers
Application layer
Transmission layer Sends, receives, and reassembles data

packet segments.
Network layer Provides addressing and routing.
Provides data packet design and point-to-

Link layer
point connection for local subsystems.
Physical layer Determines the connection rate.
IB Interface
 There are two types of channel adapters (CAs):
 Host channel adapter (HCA), for example, Mellanox
 Target channel adapter (TCA), an I/O interface used for IB switches and storage
systems
IB connectors:
CA 10 Gb/s to 40 Gb/s
Contents
1. SCSI
3. SAS and SATA
4. PCIe and NVMe
5. RDMA
CIFS Protocol
 In 1996, Microsoft renamed SMB to CIFS and added many new functions. Now,
CIFS includes SMB1, SMB2, and SMB3.0.
 CIFS uses the C/S mode and basic network protocols including TCP/IP and
IPX/SPX.
Redefined
Named as SMB CIFS Defined SMB2 SMB2.2 => SMB3.0
1988 1992 1996 2000 2007 2009 2012 2020
IBM Realized Samba Added new features

Defined SMB2.1
NFS Protocol
 NFS is short for Network File System. The network file sharing protocol is
defined by the IETF and widely used in the Linux/Unix environment.
 NFS works based on the client/server architecture. The servers provide the
clients with access to shared file systems. NFS enables clients using different
operating systems to share files over a network.
NFSv1 NFSv2 NFSv3 NFSv4.0 NFSv4.1 NFSv4.2
1990 2000 2010 2020
NDMP Protocol
 NDMP protocol is designed for the data
backup system of NAS devices. It enables NAS
2-way
devices to directly send data to the connected
networking Production Production Backup
system A system N server disk devices or the backup servers on the
network for backup, without any backup
NAS storage
system Tape library client agent required.
 There are two networking modes for NDMP
 2-way
3-way  3-way
networking Production Production Backup
system A system N server
NAS storage FC
system A Ethernet
NAS storage system A Backup data flow

Tape library
Control flow
Quiz
1. Which networks are included in FC topologies?
A. Arbitrated loop network
B. Point-to-point network
C. Switching network
D. Dual-switching network
2. Which PCIe versions are available currently?

A. PCIe 1.0
B. PCIe 2.0
C. PCIe 3.0
D. PCIe 4.0
Quiz
3. Which of the following are file sharing protocols?
A. HTTP protocol
B. iSCSI protocol
C. NFS protocol
D. CIFS protocol
4. Which NFS versions are available currently?

A. NFSv1
B. NFSv2
C. NFSv3
D. NFSv4
Quiz
5. Which processes are involved when the CIFS protocol is used?

A. Protocol handshake
B. Security authentication
C. Connection to the share
D. File operation
E. Disconnection
Summary
SCSI
iSCSI, Fibre Channel (FC), and FCoE
SAS and SATA

Common Storage Protocols
PCIe and NVMe
RDMA: RoCE, IB, and iWARP
CIFS, NFS, and NDMP
More Information
Enterprise Huawei
technical enterprise
support App business App
Recommendations

 Popular tools
 HedEx Lite
intelligent world.


Storage System Architecture Evolution
Foreword
 With the development of cloud computing and big data, the storage
architecture changes from scattered to centralized, and gradually evolves
to network-based, virtualized, and massive cloud storage. Storage not only
needs to provide routine services such as data management, data
replication, snapshot, mirroring, and migration, but also needs to enable
functions such as data disaster recovery, data consistency, virtualized
convergence, elastic computing, and resource expansion. These services and
functions depend on a good storage system architecture.
Objectives
On completion of this course, you will be able to know:

 Storage architecture evolution and expansion methods
 Huawei storage product architecture
Contents
1. Storage System Architecture Evolution
2. Storage System Expansion Methods
3. Huawei Storage Product Architecture
Storage System Architecture Evolution
Single controller Dual controllers Multiple controllers Distributed

architecture
Single-controller Storage
SCSI interface
Logical disks are presented to hosts as LUNs.
SCSI
Terminator
controller
Controller
OS
Host Single-controller storage
Dual-controller Storage
Services are running on Services are running on
only one controller. both controllers.
Controller A Controller B Controller A Controller B
Active-Standby Active-Active
Mid-range Storage Architecture Evolution
Fixed storage Dual-controller Flexible hardware Flexible software
system active-active component function
configuration redundancy configuration configuration
configuration
Limited Fibre Channel The single-controller Fast Ethernet (FE) Unified storage that
interfaces are and dual-controller interface module are supports both SAN
provided, and the active-passive supported, greatly and NAS protocols has
flexibility is poor. architecture gradually improving flexibility become a hotspot.
Capacity expansion evolve to the active- and scalability. Users can flexibly
can be implemented active architecture. The number of ports configure multi-
only by cascading disk can be selected as protocol services as
enclosures. required. required.
Multi-controller Storage
Controller A Controller B Controller C Controller D
SAS controller SAS controller SAS controller SAS controller
SAS expander SAS expander
Disk Disk
enclosures enclosures
Mission-Critical Storage Architecture Evolution
Bus Hi-Star Direct-connection Virtual matrix
architecture architecture architecture architecture
Scale-up multi- Switch-based Front-end interfaces Scale-out expansion

controller architecture connection of front- and back-end disk mode, full switching
based on bus end interfaces, back- interfaces directly mode, x86 platform,
interconnection and end disk interfaces, connected to cache and loose coupling
upgrade by using and cache modules, resources to avoid
more powerful CPUs, and back-end Fibre latency caused by bus
interface modules, Channel connection and switch connection
memory, and
protocols
Storage Software Technology Evolution
Improved data Simplified data Improved space Optimized service
reliability management utilization performance
Emergence of Storage devices are Tiered storage Performance is

snapshot, clone, and flexibly managed by promotes storage optimized according
data replication centralized space utilization and to service types.
(synchronous and management service efficiency. The Resources are properly
asynchronous) software. Thin data deduplication allocated according to
technologies provisioning technology reduces service importance.
technology resolves maintenance and Storage resources are
the conflict between capacity expansion balanced and shared
resource investment costs. flexibly and globally.
and optimal use.
Distributed Storage Technology Evolution
Automatic metadata extension
Giga+ indexing
Hadoop FS
Universal hardware Universal hardware Metadata separation Public cloud storage
Customized hardware Software-defined Software-defined Metadata extension
Scale-up Scale-up Scale-out EC Coding
Integrated Parallel cluster file Huawei
GoogleFS Azure Storage
box system OceanStor 100D
General purpose Scientific computing Analysis scenario Facebook
Facebook F4
Haystack
Social scenario Warm storage
MooseFS NoSQL
Small files
199x 2000 2008 to 2011 2014

2003
EMC PVFS Facebook/Microsoft/Huawei Facebook
Google
NetApp Lustre
Distributed Storage Architecture
iSCSI S3/Swift client
VBS
initiator
HDFS client
Compute node Compute node
VBS EDS-F EDS-F EDS-F OBJ OBJ OBJ

service service service
EDS-B EDS-B EDS-B HDFS HDFS HDFS
Block Block Block service
OBJ OBJ OBJ
service service
service service service index index index
Index Index Index Index Index Index
Storage pool (block) Storage pool (HDFS) Storage pool (object)

MDC MDC MDC
OSD OSD OSD OSD OSD OSD OSD OSD OSD
CM CM CM
Server node Server node Server node Server node Server node Server node Server node Server node Server node
Note: Huawei OceanStor 100D is used as an example to describe the distributed storage architecture.
Contents
1. Storage Architecture Evolution
Scale-up and Scale-out
 With the continued development of enterprise information systems and the ever-increasing expansion in the
scale of services, service data keeps increasing. The initial configuration of storage systems is often not
enough to meet these demands. Storage system capacity expansion has become the major concern of system
administrators. There are two capacity expansion methods: scale-up and scale-out. The following uses Huawei
storage products as an example to describe the two methods.
Storage
Devices (enclosures and disks) Storage controllers
controllers
Storage Storage
controllers controllers
Scale-out Switch Fabric

Storage
Scale-up controllers Storage
controllers
Scale-up architecture
Scale-out architecture
SAS Disk Enclosure Scale-up Networking Principles
Adding a 2 U SAS disk enclosure to
an existing loop
Controller
enclosure
2 U SAS disk
enclosure 0
2 U SAS disk
enclosure 1
Smart Disk Enclosure Scale-up Networking Principles
Adding a 2 U smart disk enclosure
to an existing loop
Controller
enclosure
Smart disk
enclosure 0
Smart disk
enclosure 1
PCIe Scale-out and IP Scale-out
 PCIe scale-out runs on the PCIe protocol while IP scale-out works based on the IP protocol.
Large Mission-critical storage

enterprises Functions first
PCIe scale-out
Mid-range storage
Medium Functions and prices
enterprises balanced
IP scale-out
Entry-level storage
Small enterprises Price first
IP scale-out
Scale-out Technologies Used by Huawei Storage Systems
OceanStor OS
XNET
XNET-PCIe XNET RDMA XNET UDP
iWARP
UDP
IB
PCIE DRV transport TCP
IP
PCIe IB ETH
Scale-out Networking
Connects to the user's management network
0 (original)
Connects to the user's

management network
1 (new)
The figure shows the scale-out

networking of Huawei solid-state
storage Huawei OceanStor Dorado
5000 V6 and 6000 V6.
Four-controller direct connection
Local Write Process
1 2
SAN
1
LUN 2 PCIe switched network
4
Engine 0 Engine 1 Engine 2 Engine 3

3 5
Non-local Write Process
1 4
SAN
1 4
LUN
2 PCIe switched network
3
6

5 7
Local Read Process
1 2
SAN
2
LUN PCIe switched network
5
8
3 4 6 7
Non-local Read Process
1 4
SAN
1 4
2 PCIe switched network

LUN
3
7
10
5 6 8 9
Contents
1. Storage Architecture Evolution
Hardware Architecture with Two Controllers
Interface .. Interface Interface Interface
.. Service subsystem
module A0 . module A7 module B7 module B0
.
PCIe 3.0 x8 PCIe 3.0 x8
Fan module 0 PCIe 3.0 Fan module 0

Fan module 1
Control x8 Control
Fan module 1
module A module B
Fan module 2 Fan module 2
Management
Management Management subsystem
interface module A interface module B
12 V
12 V
Power Power Electromechanical
BBU 0 BBU 1 BBU 2 BBU 3
supply 0 supply 1 subsystem
Service channel
Manage channel
Power supply
Hardware Architecture with Multiple Controllers
Interface ... Interface Interface ... Interface
module A0 module A5 module B5 PCIe 3.0 x8 module B0
PCIe 3.0 x8
Fan module 0 PCIe 3.0 x8 Fan module 0

Control Control Service subsystem
module C module D
... ...
Interface Interface Interface Interface
module A0 module A5 module B5 module B0
PCIe 3.0 x8 PCIe 3.0 x8
Fan module 0 PCIe 3.0 x8 Fan module 0

Control Control
module A module B
Management
Management Management
subsystem
interface module A interface module B
12 V
12 V
Electromechanical
Power Power Power Power
BBU 0 BBU 1 BBU 2 BBU 3 subsystem
supply 0 supply 1 supply 2 supply 3
Full-mesh Architecture
Host I/O
Network adapter Network adapter
Fully-shared FIMs
 Each front-end interconnect I/O module (FIM)
connects to all four controllers through PCIe ports
in a controller enclosure. This module can
FIM FIM FIM FIM simultaneously access the four controllers with
multi-channel technology in active-active mode.
Full interconnection among controllers

192 192  The controllers in a controller enclosure are fully
cores core interconnected using the passive backplane.
s  100 Gbit/s RDMA shared interface modules are
used for expansion across controller enclosures,
BIM BIM BIM BIM 192 192
implementing full interconnection between 8/12/16
cores cores
controllers.
Interconnection of disks and

enclosures across controller enclosures
 A controller enclosure uses the back-end
interconnect I/O module (BIM) to connect a disk
enclosure which can be accessed by all controllers in
the enclosure.
Note: Huawei OceanStor Dorado 8000 and 18000 V6  A smart disk enclosure has two groups of uplink
are used as the example. ports and can connect to two controller enclosures,
implementing full interconnection between the disk
enclosure and eight controllers.
Fully Interconnected Disk Enclosures
Controller Controller
enclosure 0 enclosure 1
2 U smart disk
enclosure 0
2 U smart disk
enclosure 1
E2E Global Resource Sharing
Host
SAN
Distributed based
on hash results DHT
Global cache
... ...
Switchover in Seconds: Mission-Critical Storage with FIMs
Host
 Hosts are unaware of the

Fibre Channel switch switchover, and links are
not interrupted.
Hi1822
I/O process I/O process I/O process I/O process
System mgmt. Device mgmt. Configuration Network

process process mgmt. process mgmt. process
User mode
OS kernel mode
Controller 0 Controller 1 Controller 2 Controller 3
Global Cache
Write latency
LUN 0 LUN 1 LUN 2 95 μs
4 KB 4 KB ... 8 KB 4 KB 4 KB ... 8 KB 4 KB 4 KB ... 8 KB
50 μs
Write Ahead Log (WAL)

Cache linear ...
A B C D E
space
Traditional cache OceanStor
Data Dorado V6
write
A B C D E ... Global memory

Virtual address space
RDMA
AddrN1 AddrN2 AddrN3
Memory of controller A Memory of controller B Memory of controller C Memory of controller D
Global Pool
A A1 A2 A3
LUN B B1
C C1 C2
D D1 D2
LUN mapping
and FP mapping
Strip A B C D P Q
Strip A1 B1 C1 D1 P Q
Strip A2 A3 C2 D2 P Q
RAID ... ...
...
Back-End Sharing
Engine 0 Engine 1 • A single port is connected via a single
13 0 13 connection in the external system.
• A single port is connected to four
A A controllers in the internal system.
0 13 0 13
B B
100 Gbit/s 100 Gbit/s • Dual physical links, balanced and
100 Gbit/s redundant
100 Gbit/s
A 0 1 2 3
B 0 1 2 3
A B C D
x4 x4 x4 • A single port on the controller
x4 cascades two disk enclosures in a
loop.
• A single expansion module supports
A 0 1 2 3
dual links, achieving load balancing
1822
B 0 1 2 3 and redundancy.
Active-Active Architecture with Full Load Balancing
Cache Mirroring Technology
 The function is as follows:
Controller enclosure 1 Controller enclosure 2
Controller A Controller B Controller C Controller D Controller A Controller B Controller C Controller D
Hybrid flash storage
Key Reliability Technology
 The function is as follows:
Controller A Controller B Controller C Controller D Controller A Controller B Controller C Controller D Controller A Controller B Controller C Controller D
Normal Failure of a controller (controller A)
Host Service Switchover upon Failure of a Single
Controller
Host Host
Fibre Channel switch Fibre Channel switch
Interconnect I/O Interconnect I/O

module module
Automatic
switchover
Backplane Backplane
Controller Controller Controller Controller Controller Controller Controller Controller

1 2 3 4 1 2 3 4
Quiz
1. (True or False) Scale-up is a method in which disk enclosures are continuously

added to existing storage systems to cope with increasing data volumes.
2. (Short Answer Question) What are the differences between scale-up and scale-
out?
Summary
Storage Architecture
Evolution
Storage System
Scale-up and Scale-out
Storage System Expansion Methods
Architecture
Hardware System Architecture

Huawei Storage
Product Architecture
Full-mesh Architecture
More Information
Enterprise Huawei
Recommendations

 Enterprise business: https://enterprise.huawei.com/en/
 Online learning: https://learning.huawei.com/en/
 Popular tools
 HedEx Lite
intelligent world.


Storage Network Architecture
Foreword
 With the development of host, disk, and network technologies, the storage
system architecture evolves, and the storage network architecture also
develops to meet service requirements. This lesson introduces the storage
network architecture.
Objectives
Upon completion of this lesson, you will be able to understand:

 Storage network architecture evolution
 Storage networking technology evolution
Contents
1. DAS
2. NAS
3. SAN
4. Distributed Architecture
DAS
External disk array (DAS) Smart disk array (DAS)
Server Server
CPU CPU
RAM
RAM
Disk
Disk
SCSI card
RAID SCSI card
Controller
JBOD
Challenges for DAS
Challenges Description
Limited number of ports that can be connected to a host.

Low
Scalability Limited number of addressable disks.
Limited distance.
Inconvenient
The system needs to be powered off during maintenance.
Maintenance
Insufficient Front-end ports and storage space are difficult to share.

Resource
Sharing Resource silos: For example, the DAS with insufficient storage
space cannot share the remaining space of the DAS with excessive
storage resources.
Contents
1. DAS
2. NAS
3. SAN
4. Distributed architecture
NAS
 Network-attached storage (NAS) connects storage devices to the
live network and provides data and file services.
 The most commonly used network sharing protocols for NAS are
Common Internet File System (CIFS) and Network File System  Benefits:
(NFS).  Improved efficiency
OS: Windows  Improved flexibility
 Centralized storage
 Simplified management
OS: Linux  High scalability
 High availability
 Security (user
Switch NAS device authentication and
OS: MAC OS
authorization)
General-Purpose Server and NAS Devices
File system
Application
OS
Printer driver
Network
File system
OS
Network Uni-functional
NAS device
General-purpose server
(Windows or UNIX)
NAS Protocols
Enterprise Enterprise
office office • NFS
• CIFS
IP IP IP IP
• FTP
Linux Windows
• HTTP
IP IP IP IP
• NDMP
NFS CIFS
FS
CACHE
POOL
Working Principles of NFS
POR TMAP
Client Server Port mapping
1. RPC request
table
2. RPC response RPC

Client program
Request
RPC
Registration
3. Communication NFS processes:

rpc.nfsd and
Rpc.mountd
NFS share
information
Typical Application of NFS: Shared Storage for Cloud
Computing
 Cloud computing uses the NFS server as the internal shared storage.
Converged storage
NFS client
Cloud computing server

Internal IP
Firewall
External IP network
network Cloud computing server
NFS server
Cloud computing server
Working Principles of CIFS
Client Server
SMB NEGOTIATE Request
Protocol Protocol
SMB NEGOTIATE Response negotiation handshake
SMB SESSION_SETUP Request

Security
SMB SESSION_SETUP Response Session setup authentication
SMB TREECONNECT Request

Tree Share
SMB TREECONNECT Response connection connection
...... Network file

File operation
operation
SMB TREE_DISCONNECT Request
Disconnection Disconnection
SMB TREE_DISCONNECT Response
Typical Application of CIFS: File Sharing Service
 The file sharing service applies to scenarios such as enterprise file servers and
Enterprise office
media assets.
IP Windows IP IP Management
Performance Service Share User
IP IP IP monitoring management management management
NAS service
LAN
DNS
Authentication flow
AD server Management flow
Data flow
Contents
1. DAS
2. NAS
3. SAN
 IP SAN Technologies
▫ FC SAN Technologies
▫ Comparison Between IP SAN and FC SAN
NIC + Initiator Software
The initiator software

converts iSCSI packets into
TCP/IP packets, which
consumes host resources.
NIC
TCP/IP-based Ethernet IP SAN

connection
Internal bus
Storage device Ethernet
TOE NIC + Initiator Software
The initiator software
implements the
functions of the iSCSI
layer, which consumes
host resources.
The TOE NIC implements
TCP/IP conversion, which
TOE NIC does not consume host
resources.
TCP/IP-based IP SAN
Ethernet connection
Internal bus
iSCSI HBA
The iSCSI HBA converts

iSCSI packets into TCP/IP
iSCSI HBA packets, which does not
consume host resources.
TCP/IP-based IP SAN
Ethernet connection
Internal bus
Logical Port
 Logical ports are created based on bond ports, VLAN ports, or Ethernet ports. The logical ports
are virtual ports that carry host services.
 A unique IP address is allocated to each logical port for carrying its services.
No. Description
Logical port
Indicates that multiple Ethernet ports are 4
1
bonded to form a bond port.
One to One to
5
Indicates that an Ethernet port is added many many
2
to multiple VLANs.
Indicates that a bond port is added to One to
3
One to
3 Bond port VLAN
multiple VLANs. many many
Indicates that a bond port is used to
4
create multiple logical ports.
Many to One to
2
Indicates that a VLAN port is used to one many 6
5
create multiple logical ports. 1
Indicates that an Ethernet port is used to Ethernet port

6
create multiple logical ports.
VLAN Configuration
 VLAN is a technology that logically divides a physical LAN into multiple broadcast
domains.
 Ethernet ports or bond ports in a storage system can be added to multiple independent
VLANs. You can configure different services in different VLANs to ensure the security
and reliability of service data.
VLAN 1 VLAN 2 VLAN 3 VLAN k

ID = 1 ID = 2 ID = 3 …… ID = k
Ethernet port
Bond port
P0 P1 P2 P3 Storage device
Adding ports to VLANs
IP Address Failover
 IP address failover indicates that a logical IP address fails over from a faulty port to an available
port. In this way, services are switched from the faulty port to the available port without
interruption. The faulty port can take over services back after being recovered.
 During the IP address failover, services are switched from the faulty port to the available port,
ensuring service continuity and improving reliability of paths for accessing file systems. This
process is transparent to users.
 The essence is a service switchover between ports. The ports can be Ethernet ports, bond ports, or
VLAN ports.
Ethernet Port–based IP Address Failover
 To improve reliability of paths for accessing file systems, you can create logical ports based on
Ethernet ports.
 When the Ethernet port that corresponds to a logical port fails, the system will:
 Locate an available Ethernet

port of the same type.
 Delete the logical port from
the faulty Ethernet port.
Search
 Create the same logical port Logical port A Logical port A
Logical port A
(IP address a) (IP address a)
on the available Ethernet Port fault Port switchover
port to carry services.
 Ensure service continuity.
Ethernet port A Ethernet port A Ethernet port B
Bond Port–based IP Address Failover
 To improve reliability of paths for accessing file systems, you can bond multiple Ethernet ports to
form a bond port.
 When the Ethernet ports that are used to create the bond port fails, the system will:
 Locate an available port.

 Delete the logical port created
High-speed
on the faulty port. data
 Create a logical port with the transmission
Search
same IP address on the Logical port A
Logical port A
Logical port A
available port. Port fault Port switchover
 Switch services to the
available port.
After the faulty port recovers, it Ethernet port A Ethernet port A Ethernet port C
can take over services again. Ethernet port B Ethernet port B Ethernet port D
Bond Port A Bond Port A Bond Port A
VLAN-based IP Address Failover
 You can create VLANs to isolate different services.
 When an Ethernet port on a VLAN fails, the system will:
 Locate an available port of

the same type.
 Delete the logical port from
Search
the faulty port. Logical port A Logical port A
Logical port A
 Create the same logical port Port fault Port switchover
on the available port.

 Switch services to the Ethernet port A Ethernet port A Ethernet port B
available port. VLAN A VLAN A VLAN B
ID = 1 ID = 1 ID = 1
Contents
1. DAS
2. NAS
3. SAN
▫ IP SAN Technologies
 FC SAN Technologies
▫ Comparison Between IP SAN and FC SAN
FC HBA
The FC HBA converts SCSI

packets into Fibre Channel
FC HBA packets, which does not
consume host resources.
Fibre Channel
FC SAN
protocol-based
Internal bus
Storage device FC network
FC Network
Zoning
Zone 1: Server 1 can Zone 2: Server 2 can

access Storage 1. access Storage 2.
Server 1 Server 2
Storage 1 Storage 2
Zone 3: Server 3 can

access Storage 1 and
Storage 3 Storage 2.
Server 3
Contents
1. DAS
2. NAS
3. SAN
▫ IP SAN Technologies
▫ FC SAN Technologies
 Comparison Between IP SAN and FC SAN
IP SAN and FC SAN
DAS IP SAN FC SAN
iSCSI
FC FC
IP
SCSI
IP
FC FC
iSCSI
Comparison Between IP SAN and FC SAN
Item IP SAN FC SAN
Dedicated Fibre Channel networks and
Network architecture Existing IP networks
HBAs
Transmission Limited by the maximum transmission
Not limited theoretically
distance distance of optical fibers
Management and Complicated technologies and
As simple as operating IP devices
maintenance management
Compatibility Compatible with all IP network devices Poor compatibility
High purchase (Fibre Channel switches,
Lower purchase and maintenance costs HBAs, Fibre Channel disk arrays, and so
Cost than FC SAN, higher return on on) and maintenance (staff training,
investment (ROI) system configuration and supervision,
and so on) costs
Disaster recovery Local and remote DR available based High hardware and software costs for
(DR) on existing networks at a low cost DR
Security Relatively low Relatively high
Contents
1. DAS
2. NAS
3. SAN
Distributed Storage Networking
Node 1
Frontend service
network
Node 2
Node 3
Management
network
Node 4
Node 5
Backend storage network
Networking Overview
 Frontend service/Tenant network
 The front-end service/tenant network is used to interconnect the distributed storage with the customer network. It
provides the tenant UI for tenant users to complete operations such as resource application and usage query, and
processes service requests sent by tenant clients or APIs.
 Backend storage network

 The backend storage/internal management network is used for internal interconnection between nodes. It provides
heartbeat communication between high availability (HA) components such as the data service subsystem (DSS), and
internal communication and data interaction between components.
 Management network
 The management network is used to interconnect with the customer's maintenance network. It provides a management
UI for the system administrator to perform service operations such as system configuration, tenant management,
resource management, and service provisioning, as well as maintenance operations such as alarm, performance, and
topology management. In addition, the Mgmt ports of all physical nodes can be aggregated to provide remote device
maintenance capabilities, such as remotely logging in to the virtual KVM of a device and viewing hardware running data
such as temperature and voltage.
Network Planes
Private client node Standard protocol node
access mode FSM access mode FSM
Storage node Compute node Storage node Compute node

REP REP
VBS Application Application
VBS/HDF
EDS EDS
S-SVR
OSD OSD
Third-place Third-place
DR site quorum DR site quorum Management plane:
server server Storage plane:
Replication plane:
Arbitration plane:
Service plane:
Networking Rules
 Nodes must be placed in a cabinet from bottom to top.
 A deployment solution is usually chosen based on project requirements. The
total power consumption and weight of the storage nodes, switches, and KVM
in a cabinet must be calculated and the number of nodes that can be housed by
a cabinet must be determined based on the equipment room conditions.
 In typical configuration, nodes and switches in the base cabinet are connected
through network cables and SFP+ cables, and nodes in an expansion cabinet
connect to switches in the base cabinet through network cables and optical
fibers.
Quiz
1. Which of the following are included in distributed storage networking?
A. Management network
B. Frontend service network
C. Frontend storage network
D. Backend storage network
2. Which of the following protocols are commonly used in SAN networking?

A. FC
B. iSCSI
C. CIFS
D. NFS
Summary
DAS
NAS IP SAN
Storage network
architecture evolution
SAN FC SAN
Comparison between
Distributed architecture
IP SAN and FC SAN
More Information
Enterprise Technical Huawei Enterprise

Recommendations

 Popular tools
 HedEx Lite
intelligent world.


Introduction to Huawei Intelligent Storage
Products
Foreword
 This course describes features, positioning, and typical application scenarios

of Huawei intelligent storage products, including Huawei OceanStor all-
flash storage, Huawei OceanStor hybrid flash storage, Huawei OceanStor
distributed storage, and Huawei edge data storage (FusionCube).
Objectives
Upon completion of this course, you will be able to know the following about
Huawei intelligent storage products:
 Features
 Positioning
 Typical application scenarios
Contents
1. All-Flash Storage
2. Hybrid Flash Storage
3. Distributed Storage
4. Edge Data Storage (FusionCube)
All-Flash Product Display
Huawei OceanStor
Huawei OceanStor
Dorado 18000 V6
Huawei OceanStor Dorado 8000 V6
Dorado 3000 V6
Huawei OceanStor
Huawei OceanStor
Dorado 18000 V3
Dorado 5000 V3
Huawei OceanStor
Dorado 3000 V3
Features
Intelligent AI chips+FlashLink
SSDs+NVMe disks for high SmartMatrix 3.0 full-

performance and low latency mesh architecture
Huawei OceanStor Dorado all-flash storage
Device Model Examples
2 U, disk and controller integration, 2 U, disk and controller integration, built-in 36 x

built-in 25 x 2.5-inch disks palm-sized NVMe disks
Power-BBU module Icon Description

Management Maintenance Serial Interface
port port port  1+1 redundancy
module
Enclosure ID indicator
Enclosure location indicator
1. Blinking blue: The controller enclosure is
being located.
2. Off: The controller enclosure is not
located.
Enclosure alarm indicator
SAS expansion port 1. Steady amber: An alarm is reported by
 Each controller provides two SAS (SAS version) or 100
the controller enclosure.
Gbit/s RDMA (NVMe version) expansion ports. 2. Off: The controller enclosure is working
properly.
Note: Huawei OceanStor Dorado series is used as an example. Power indicator/Power button
Storage System Components
Power Module
Controller
System Subrack
Disk Module
Note: Huawei OceanStor Dorado (2 U) is used as an example.
Software Architecture
Software on a Software running on an

maintenance terminal application server
Management
network Software on the
storage system iSCSI/Fibre Channel
port/Serial port
OceanStor BCManager SNMP CLI Syslog Management function

control software
Cache HyperSnap HyperReplication HyperClone HyperMetro HyperCDP
Pool
SmartQoS SmartThin SmartMigration SmartVirtualization Three-copy mode
SCSI
RAID SmartDedupe and SmartCompression HyperSnap
Storage operating system
Intelligent Chips
FLASHLINK ® intelligent algorithm
Controller with0
five chips
0
00
0 0
1 1 Reconstruction
1 010 Multi-core
1
00
1101
0 scheduling X00 minutes/TB
001 0 1X minutes/TB
1 1 1 00 1 Restart 1 2 3 4 5
0
0
0 1 10
0 1 count
1 010 1 Kunpeng chip + service
1
1
1
0 101enclosure
Smart0disk0 0
0
Kunpeng chip + multi-core
splitting
AI chip + cache algorithm
1 1010 1 algorithm Improved read hit ratio
Faster reconstruction
1
0 01
0 0101 0
0
1 1010 1
10 1 10
0101 0
0 1 1 10 1
0 Metadata Data read
0 01
1 0 0 01 0
1 New data Data write
0 1 1 11 1
00 0
Advanced feature
1 10
1 1 SSD1
11 1
GC migration Disk reconstruction
1 data
11 1 Garbage collection
0 11
Multi-stream data Global I/O priority
1 Full-stripe write
Reduced write amplification
partitioning adjustment
Reduced garbage collection Constant low latency
Typical Application Scenario – Mission-Critical Service
Acceleration
Data center
Operational Product Risk control Supervision and

analytics management reporting
SAN
Data Data
Data analysis
extraction consolidation
...
Huawei OceanStor
Dorado
Contents
Hybrid Flash Storage Series
Huawei OceanStor 18810F V5
Huawei OceanStor 18800F V5 Huawei OceanStor 18810 V5

Performance, IOPS

Huawei OceanStor 18510 V5
Huawei OceanStor 5610F/5810F V5
Huawei OceanStor 5310F/5510F V5 Huawei OceanStor 6810 V5
Huawei OceanStor
Huawei OceanStor 5610/5810 V5
5100/5210F V5 Huawei OceanStor 18800 V5


All Flash Arrays

Hybrid Flash Arrays
Scalability, PB Usable
Hybrid Flash Storage
Enterprise-class hybrid flash storage products
provide stable, reliable, converged, and
efficient data services.
Meets requirements of various services and

applications such as OLTP/OLAP databases,
high-performance computing, digital media,
Internet operation, centralized storage,
backup, disaster recovery, and data migration.
Provides a wide range of efficient and flexible

backup and disaster recovery solutions to
ensure business continuity and data security.
Huawei OceanStor hybrid flash storage
Device Model Examples
Storage device (2 U) For example, Huawei Storage device (2 U) For example, Huawei OceanStor
OceanStor hybrid flash storage 5110 V5 hybrid flash storage 5600/5800 V5 Kunpeng
Storage device (2 U) For example, Huawei Storage device (4 U), for example, Huawei OceanStor
OceanStor hybrid flash storage 5300 V5 Kunpeng hybrid flash storage 6800/18800 V5 Kunpeng
Convergence of SAN and NAS Storage
LUN
Extent
iSCSI/FC/FCOE NFS/CIFS/FTP/HTTP
Block Service File Service Tier0: SSD Tier1: SAS Tier2: NL-SAS
ROOT
Storage POOL RAID 2.0+

File system
Dir Dir
File
Convergence of SAN and NAS resources of Tier0: SSD Tier1: SAS and NL-SAS
Huawei OceanStor hybrid flash series
Intelligent tiering of SAN and NAS cold/hot data
Support for Multiple Service Scenarios
Cloud Finance
computing
Carrier
Social
intercourse
Energy
Big data
Government
Enterprise
Backup
and DR
Application Scenario – Active-Active Data Centers
Data center A Data center B
Database service
Virtualization
service
File service
...
Switch Switch
Active-active
SAN NAS SAN NAS
Contents
Distributed Storage
• The distributed technology creates a large-scale storage

resource pool that provides services for upper-layer
applications and clients through standard service interfaces.
• Supports large-scale expansion and elastic EC data
redundancy protection, improving disk space utilization.
• One storage system supports block, file, HDFS, and object
storage services.
• The solution with separated storage and computing
resources ensures stable latency and fast response to
mission-critical services.
Note: Huawei OceanStor 100D is used as an example in the figure.
Product Highlights
Object service
File service
Block service HDFS service
Note: Huawei OceanStor 100D is used

as an example.
Block File Object
HDFS
OceanStor distributed storage
Four-in-one storage service, enabling one storage

system to support four types of storage services
Hardware Node Examples
• Virtualization
Performance scenario
node • Cloud computing
For example: OceanStor 100D P100 and P110
scenario
• Big data analytics

Capacity scenario
node • Object resource
pool scenario For example: OceanStor 100D C100 and C110
All-flash
node • Database scenario
For example: OceanStor 100D F100 and F110
Note: Huawei OceanStor 100D is used as an example in the figure.
Hardware Node Examples
P36A C36A
TaiShan 5280 V2
TaiShan 5280 V2
P12A S12A
TaiShan 2280 V2 TaiShan 2280 V2
x86 Platform Application Scenario Remarks

Checkpoint/Portrait checkpoint, hybrid
storage of video and images, media
P36X
asset production, HPC production, and
mobile centralized procurement TaiShan 5280 V2 server
Video surveillance, media asset library,
C36X
and HPC archiving
Small-sized media asset production and
P25X None
resource pool
Note: Huawei OceanStor 9000, the scale-out storage for files, is

used as an example in the figure.
Software System Architecture
Service Layer
VBS (SCSI/iSCSI) NFS/SMB HDFS S3/SWIFT/POE

Disaster Recovery OAM Plane
HyperReplication
Cluster
Block File HDFS Object
HyperMetro Management
LUN Volume Direct IO Cache NameNode LS OSC Billing
Device
Manager
Index Layer
QoS
Write Ahead Log Snapshot Compression Deduplication Garbage Collection
Alarm/Log
Persistence Layer Authentication

Mirror Erasure Coding Fast Reconstruction Write-back Cache SmartCache
License
Hardware x86/Kunpeng
Note: Huawei OceanStor 100D is used as an example.
Application Scenario – Cloud Resource Pool
Traditional compute-storage convergence
Data nodes + Compute nodes
Data nodes + Compute nodes
Storage-compute separation
Compute node
Cloud storage resource pool
Data node Data node Data node
Contents
Edge Data Storage (FusionCube)
 FusionCube:
 It is an edge data storage
infrastructure based on the
converged architecture. It is  FusionCube 1000:
mainly used in hybrid load  It is an edge IT infrastructure
scenarios, such as databases, solution with integrated
desktop clouds, containers, design and is delivered as
and virtualization. integrated cabinet. The
 The Kunpeng ecosystem is solution is mainly used in
supported to flexibly meet edge data centers and edge
the elastic configuration application scenarios of
requirements of computing, vertical industries.
storage, and I/O resources Huawei FusionCube  The Kunpeng ecosystem is
and meet the requirements supported. Pre-cabling and
of multiple types of pre-configuration can be
application load modes with completed in advance based
an IT infrastructure at the on the customer's plan, and
edge. the solution is delivered as
integrated cabinet to
implement quick deployment.
Huawei FusionCube 1000
Hardware Model Examples
Blade server High-density server Rack server
4 U with 4 nodes or 2 U with 4

12 U with 8 or 16 nodes 2 U with one node
nodes
Introduction to Intelligent Management
System device Virtual resource
VM provisioning and management

Automatic detection
Server Resource usage monitoring
Status monitoring
One-click capacity expansion
Switch One-click O&M
FusionCube
Center
Unified
management
Storage resource Bare metalresource

Storage pool status monitoring Resource usage monitoring

Storage usage monitoring Network configuration
Distributed
Disk volume device management
block storage
Storage System
Node 1 Node 2 Node N
VM VM VM VM VM VM
...
Distributed storage resource pool
SSD HDD SSD HDD SSD HDD
Software Architecture
Office Application VDI BI CRM&ERP Email Web Application
Service
Database
software
Linux OS Operating
Hyper-convergence
Unified system
management Backup software
Distributed storage system
One-click
Asynchronous
capacity EC Active-active QoS
replication
expansion
Multiple
Thin Linked Distributed
Snapshot resource
provisioning clone cache
pools
Hyper-convergence
Unified installation DR
Huawei server hardware
Note: The figure uses FusionCube as an example.
Application Scenario – Edge Data Center Service Scenario
FusionCube
Installer
Hardware
installation in an
edge data center
Edge data
center
Compute
+ module
Network
Site
module
management +
Service provisioning
Real-time Storage
Edge data center module
monitoring
Data backup HQ data center
+
Intelligent UPS
O&M
Modular
design and
Edge data center all-in-one
cabinet
Quiz
1. (Single-answer question) Which of the following statement about Huawei OceanStor all-
flash storage is false?
A. Supports SSDs and NVMe disks.
B. Supports SAS disks.
C. Supports HDDs.
D. Supports palm-sized SSDs.
Quiz
2. (Multi-answer question) Which of the following storage services are supported by Huawei
distributed storage (such as Huawei OceanStor 100D)?
A. Block storage
B. File storage
C. Object storage
D. HDFS storage
E. Linked storage
Summary
All-flash storage
Hybrid flash storage

Introduction to Huawei intelligent Characteristics, positioning,
storage products and application scenarios
Distributed storage
Edge data storage

(FusionCube)
More Information
Enterprise Technical Huawei Enterprise

Recommendations

 Popular tools
 HedEx Lite
intelligent world.


Storage Resource Tuning Technologies and
Applications
Foreword
This course describes storage resource tuning technologies, including

SmartThin, SmartTier, SmartQoS, SmartDedupe, SmartCompression, and
SmartMigration.
Objectives
On completion of this course, you will be able to understand the service features,
implementation principles, and application scenarios of the following features:
 SmartThin
 SmartTier
 SmartQoS
 SmartDedupe
 SmartCompression
 SmartMigration
Contents
1. SmartThin
2. SmartTier
3. SmartQoS
4. SmartDedupe
5. SmartCompression
6. SmartMigration
Overview
 The traditional deployment of a storage system has the following problems:
 Adverse impact or even interruption on services when expanding the storage space
 Uneven storage space utilization
 Low storage efficiency
 SmartThin can allocate the storage space on demand to improve storage
resource utilization and fully meet service requirements.
Working Principle of SmartThin
Logical virtual Actual physical
Servers
space space
DB
Data
RAID
server
Disk
DB
Data
RAID
server
Space Disk
DB
Data
server RAID
Disk
DB
Data
server RAID
Visible storage Storage Disk Storage

space resource pool resources array
SmartThin Read Process
1. A thin LUN receives a read 2. Queries the mapping table between
request from a host. the thin LUN and the storage pool.
3. Confirms that the space is allocated by the storage pool and returns the data
read from the corresponding area in the storage pool to the host.
Data
2 1 D 3
1 2 D D D
3 D
1 1 3 5 2
0000 4
2 4 6 5 D
3
Thin LUN 6 Storage pool
Mapping
1. The thin LUN receives a read request from the host. table
2. Queries the mapping table between the thin LUN and the storage pool.
3. Confirms that the space is not allocated by the pool and returns all zeros to the host.
SmartThin Write Process
2. Queries the mapping table between
1. A thin LUN receives a write
the thin LUN and the storage pool.
request from a host.
3. Confirms that the space is allocated by the pool and performs the write process on the
corresponding area in the storage pool. If the write request asks for releasing space, the
space is released.
Data
Data
2 1 D 3
1 2 D D
1 1 5 2
3 3
3
4
2 4 6 5
1. A thin LUN receives a write
request from the host. Storage pool
Thin LUN 6
2. Queries the mapping table between
the thin LUN and the storage pool. Mapping table
3. If the space is not allocated by the pool, the storage system allocates the space first. And then performs write process
on the corresponding area in the storage pool. If the write request asks for releasing space, a message is returned to the
host.
Application Scenarios
 SmartThin can help core system services that require high service continuity, such as
bank transaction systems, expand system capacity online without interrupting ongoing
services.
 SmartThin can assist with on-demand physical space allocation for services where the
growth of application system data is hard to be accurately evaluated, such as email
services and web disk services, preventing a space waste.
 SmartThin can assist with physical space contention for mixed services that have diverse
storage requirements, such as carriers' services, to achieve optimized space
configuration.
Configuration Process
Start Modify properties of a

thin LUN.
Check the SmartThin
license.
Expand a thin LUN online.
Import a SmartThin
Delete a thin LUN.
license.
Create a disk domain. Delete a storage pool.
Create a storage pool. Create a disk domain.
Create a thin LUN. End
Contents
1. SmartThin
2. SmartTier
3. SmartQoS
4. SmartDedupe
5. SmartCompression
6. SmartMigration
Overview
 The random distribution of hot and cold data fails to fully utilize disk characteristics of different
media. SmartTier automatically matches different active data with storage media of different
characteristics. For example, cold data is stored on NL-SAS disks, and hot data is stored on SSDs.
In this way, data flows vertically, improving storage system performance and reducing costs.
High-performance tier
SSDs
Performance tier
SAS disks
Most active data
Capacity tier Hot data

NL-SAS
disks Cold data
Dividing Storage Tiers
 In the same storage pool, a storage tier is a collection of storage media with the same
performance. Each storage tier respectively uses the same type of disks and RAID policy.
Performance tier: SAS disks

High-performance tier: SSDs
 High bandwidth under a large number of
 High IOPS; Short task response
service loads; Moderate task response time;
time; High cost of storage Storage Write speed slower than read speed without
capacity per unit tiers
 Applicable to applications with cached data
 Applicable to applications with moderate
intensive random access requests
access requests
Capacity tier: NL-SAS disks

 Low IOPS; Long task response time.
High cost for storage request
processing per unit
 Applicable to applications with light
access requests
Three Phases for Implementing SmartTier
 The storage system undergoes three phases of I/O monitoring, data placement
analysis, and data relocation to implement SmartTier.
The I/O monitoring module collects statistics on the

I/O monitoring
activity levels of all data blocks.
Data placement The data placement analysis module ranks the

analysis activity levels of all data blocks.
Data migration The data migration module migrates data based on

the ranking result and data migration policies.
SmartTier Key Technologies
Migration Monitoring
Initial capacity Data
policy statistics
allocation migration
formulation analysis
• Automatic • Automatic • I/O monitoring • Data migration

allocation migration and statistics plan
• Preferential • Migration to the collection • Data migration
allocation to the higher- • Determining the rate
high-performance performance tier data to be • Data migration
tier • Migration to the migrated granularity
• Preferential lower-
allocation to the performance tier
performance tier • No migration
• Preferential
allocation to the
capacity tier
Application Scenarios
 SmartTier is used for various service

environments.
Disk procurement cost (USD)

25000
 The following uses the Oracle database

20000
service as an example:
15000
 After using SmartTier, enterprise A
reduces 25% cost for disk procurement. 10000
 The more cold data is stored, the more

5000
disk procurement costs are saved.
0
0 20 40 60 80 100
Idle data percentage (%)
Storage system-level configuration includes the
Start
configuration of data migration speed, which is applied
to all storage pools in a storage system.
Check the license. Storage pool-level configurations include configurations
of data migration granularity, RAID policy, data
migration plan, enabling I/O monitoring, and forecast
Configure SmartTier parameters based
on the storage system level. analysis. The mentioned configurations are applied to a
single storage pool.
Configure SmartTier parameters base LUN-level configurations include the

on the storage pool level. configuration of the initial capacity allocation
policy, and SmartTier policy, which are applied to
a single LUN.
Configure SmartTier parameters based
on the LUN level.
End
Contents
1. SmartThin
2. SmartTier
3. SmartQoS
4. SmartDedupe
5. SmartCompression
6. SmartMigration
Overview
 SmartQoS traffic control management

SmartQoS dynamically allocates storage system resources to meet
certain performance goals of some applications.
 The storage system uses LUN-, file system-, or snapshot-based I/O
priority scheduling and I/O traffic management to ensure the proper
running of critical services.
I/O Priority Scheduling
High Middle Low High Middle Low
App 1 App 2 App 3 App 1 App 2 App 3
FIFO 7
8 4
7 1
9 8
6
5 6
4 2
3 9
2 5
1 3
Traditional storage I/O priority scheduling
I/O Traffic Control
Application server 1 Application server 2
I/O I/O
1 request 1 request
Number of allocated tokens

(I/O queue processing mechanism Storage
of applications in the system) system
2 Processes
dequeued I/O
Application I/O queue 1 requests.
...... 3
Application I/O queue n

Disk
Application Scenario
User Type Service Quality
Requirements
Subscriber A (gold High
subscriber) The limited bandwidth is less
Subscriber B (silver Low Subscriber A
than or equal to 100 MB/s,
subscriber) gold
which ensures robust
subscriber
resources.
• SmartQoS traffic control policy A: limits the service
bandwidth of subscriber A (for example, ≤ 100 MB/s) to
ensure the service performance of subscriber A without
Subscriber B
The limited bandwidth is less
silver
affecting the service performance of the whole storage than or equal to 30 MB/s.
subscriber
system.
• SmartQoS traffic control policy B: limits the service
bandwidth of subscriber B (for example, ≤ 30 MB/s). The
bandwidth of subscriber B is less than that of subscribe A to
reserve robust system resources for other users.
Start
Check the SmartQoS license.

Monitor service performance.
Configure SmartQoS. Configure the I/O priority.
Create a SmartQoS policy.

End
Main steps
Sub-steps
Contents
1. SmartThin
2. SmartTier
3. SmartQoS
4. SmartDedupe
5. SmartCompression
6. SmartMigration
Overview
 SmartDedupe eliminates redundant data from a storage system and reduces the
physical storage capacity for storing data to meet the increasing needs for
storage capacity.
 Dorado V6 storage systems support online deduplication and post-process
similarity deduplication.
 Online deduplication: Data is deduplicated before being written to disks.
 Post-processing similarity deduplication: Data is written to disks in advance and then
read and deduplicated when the system is idle.
Working Principle of Online Deduplication
Data to be deduplicated
Block 1 Block 2 Block 3

Fingerprint (FP) table
FP Data Address References

FP0 FP1 FP2
FP0=FPx Data address 0 1
FP1=FPy Data addition 1->2
FP2 Data address 2 1
FPx Data address 1

New block Old block New
(same FP)
(same FP) block
(byte-by-byte comparison)
Writes data. +1 Writes data.
Working Principle of Post-processing Similarity
Deduplication
Data to be deduplicated
Block 1 Block 2 Block 3 Similarity deduplication opportunity table
<LBA> <FP> <Similarity

SFP0 SFP1 SFP2 fingerprint
FP0 FP1 FP2 (SFP)>
LBA0 FP0 SFP0
Storage LBA1 FP1 SFP1
LBA2 FP2 table
Fingerprint SFP2
Same block <FP> Data Address References

New block Similar block
(same FP)
(same SFP)
(byte-by-byte comparison) FP0 Data address 0 2,1
Differentially
Writes data. +1
compresses.
Saved after differential compression
Application Scenarios of SmartDedupe
 Virtual Desktop Infrastructure (VDI) is a common application scenario of
deduplication.
 In VDI applications, users create multiple virtual images on a storage device.
These images have a large amount of duplicate data. As the amount of
duplicate data increases, the storage system space fails to meet service running
requirements. SmartDedupe can delete duplicate data between images to
release storage resources and store more service data.
Start
1. Checking the
availability of Check the license.
SmartDedupe
2. Enabling
SmartDedupe for Enable SmartDedupe.
LUNs
End
Contents
1. SmartThin
2. SmartTier
3. SmartQoS
4. SmartDedupe
5. SmartCompression
6. SmartMigration
Overview
 SmartCompression reorganizes data to save storage space and improves the
data transfer, processing, and storage efficiency under the precondition that no
data is lost. The storage system supports online compression, that is, only newly
written data is compressed.
 The storage systems of the Dorado V6 storage systems support online
compression and post-compression, both of which are lossless compression.
 Online compression: Data is compressed before being written to disks.
 Post-compression: Data is written to disks in advance and then read and compressed
when the system is idle.
Working Principle of SmartCompression
Compression window
The window moves forward The window moves forward
Data to be
... ... abcdefg abc hj abchj
compressed
Searches for the

longest identical
After character string, (0,3) hj (2,5)
starting from the
compression first character.
Offset in the Longest

window matched string
(LZ77 example)
Application Scenarios of SmartCompression
Engineering
and
File
Databases Seismic
Services
Geological
Data
Scenarios Where SmartDedupe and SmartCompression
Are Used Together
 The deduplication and compression technologies can be used at the same time
to achieve the optimal space saving effect.
 Application scenarios:
 VDI and VSI scenarios
Less
Longer
storage Less cost
 Data tests or development systems space
SSD life
 Storage systems with the file service enabled

 Engineering data systems
Start
1. Checking the
availability of Check the license.
SmartCompression
2. Enabling
SmartCompression Enable SmartCompression.
for LUNs
End
Contents
1. SmartThin
2. SmartTier
3. SmartQoS
4. SmartDedupe
5. SmartCompression
6. SmartMigration
Overview
 SmartMigration is a key service migration technology. Services on a source LUN
can be completely migrated to a target LUN without interrupting host services.
The target LUN can totally replace the source LUN to carry services after the
replication is complete.
What does
"completely" mean?
Working Principle of SmartMigration
 SmartMigration is leveraged to adjust service performance or upgrade storage
systems by migrating services between LUNs.
 SmartMigration is implemented in two phases:
Service data LUN information

synchronization exchange
Start Finish
SmartMigration Service Data Synchronization
 After creating a SmartMigration task, create the pair relationship between a source LUN
and a target LUN.
 Service data synchronization between the source and target LUNs involves initial
synchronization and change synchronization.
A B C Host
D E F 1 5
G H I DCL Log
A B C A B C 2
4
Storage
D E F Copy all data. D E F
4 LM
G H I G H I
2 2
3 3
Source LUN Target LUN
Source Target
LUN LUN
Initial synchronization
Change synchronization
SmartMigration LUN Information Exchange
 LUN information exchange is used for mappings between LUNs and data volumes,
namely, the exchange between both data volume IDs when the IDs of source LUNs and
target LUNs remain unchanged.
Source Target
The host reads the ID LUN LUN
of the source LUN.
LUN ID Source data volume ID LUN ID Target data volume ID

Before LUN 0 0
1
1 1
information exchange Mapping
LUN ID Target data volume ID LUN ID Source data volume ID

During LUN 2
0 1 1 0
information exchange Exchanging data volume IDs
LUN ID Target data volume ID LUN ID Source data volume ID

After LUN 3
0 1 1 0
information exchange Mapping
SmartMigration Pair Splitting
 Splitting is performed on a single pair. The splitting process includes stopping service
data synchronization between the source LUN and target LUN in a pair to exchange
LUN information, and removing the data migration relationship after the exchange.
After service data synchronization is stopped.
1. Information
exchange
Splitting What if multiple

Source Pair Target
LUN LUN pairs are split?
2. Pair splitting
Start
Check the license file.
Create a SmartMigration task.
Split SmartMigration pairs or

perform consistency splitting on
SmartMigration pairs.
End
Summary
SmartThin
SmartTier
SmartQoS
Storage resource tuning Definitions, working
principles, and
technology and application configuration processes
SmartDedupe
SmartCompression
SmartMigration
Quiz
1. (True or false) SmartTier cannot be enabled for a storage pool whose member disks are of the same
type. ( )
2. (Multiple-choice) Which of the following migration policies can be set for LUNs? ( )
A. Automatic migration
B. Migration to the higher-performance tier
C. Migration to the lower-performance tier
D. No migration
Quiz
3. (Single-answer question) Which status must a pair be before consistency splitting during
LUN
migration? ( )
A. Migrating
B. Stop
C. Normal
D. Migrated
More Information
Enterprise Huawei
support app business app
Recommendations

 Enterprise business: https://enterprise.huawei.com/en/
 Technical support: https://support.huawei.com/enterprise/
 Online learning: https://learning.huawei.com/en/
 Popular tools
 HedEx Lite
 Network Documentation Tool Center
intelligent world.


Storage Data Protection Technologies and
Applications
Foreword
 Traditional data protection solutions focus on periodic data backup.

Therefore, problems such as no backup window, inconsistent data, and
impact on the production system always occur.
 This course describes storage data protection technologies such as
HyperSnap, HyperClone, HyperReplication, and HyperMetro which are new
data protection methods.
Objectives
On completion of this course, you will be able to understand the principles,

configuration methods, and application scenarios of the following features:
 HyperSnap
 HyperClone
 HyperReplication
 HyperMetro
Contents
1. HyperSnap
2. HyperClone
3. HyperReplication
4. HyperMetro
Overview
 Storage Networking Industry Association (SNIA) defines a

snapshot as follows:
A snapshot is an available copy of the specified data collection. The
copy contains the image for the relevant data at a time point when
the copy begins.
A snapshot can be a duplicate or replicate of data.
Working Principles of HyperSnap
 Definition: A snapshot is a consistent copy of the source data at a certain point in time. After the snapshot is
generated, it can be read by hosts and used as a data backup at a certain point in time.
 Main features
 Instant generation: A storage system can generate a snapshot within a few seconds to obtain the consistent copy of
source data.
 Small storage space occupation: A snapshot is not a full physical data copy, which does not occupy large storage space.
Therefore, a snapshot for a large amount of source data occupies only a small space.
a b c a b c
d e f d e f
8:00 AM
g h i g h i
j k l j k l
a b c a b c
d m f d e f 9:00 PM
g h n g h i
j k l j k l
HyperSnap Principles – Zero Performance Loss
Data requested to be written to L2 of
the source LUN is written to P5. Data requested to be Data requested to be written
Data requested to be written to L2 of written to L0 of snapshot to L2 of snapshot 2 is written
the source LUN is again written to P7. 1 is written to P6. to P8.  Data requested to be written to
L2 of the source LUN is written
LUN Mapping Table Snap Mapping Table to a new space P5. The original
Snap Mapping Table
space P2 is referenced by the
snapshot.
 Data requested to be written to
L0 of snapshot 1 is written to the
new space P6, bringing no
additional read and write
overhead.
 When data is written to L2 of the
source LUN again, the requested
L3->P3 L4->P4 L2->P5 L2->P7 L2->P8
L0->P6 L0->P0 L1->P1 L2->P2 data is written to a new space
P7. The original space P5 is
released because it is not
A B C D E F G H I referenced by a snapshot.
 A new snapshot 2 is created and
P0 P1 P2 P3 P4 P5 P6 P7 P8 activated.
SSD storage space
HyperSnap Principles – Rollback
Data 10:00 AM Data 11:00 AM Virus Infection Data 11:00 AM
Restore
10 11 12 TIME
Snap 10:00 AM Snap 11:00 AM
HyperSnap Principles – Snapshot Cascading and Cross-
Level Rollback
Source
 Snapshot cascading: It is a child
volume
snapshot of a parent snapshot. The
difference between snapshot duplicates
and snapshot cascading is that the
latter includes the data of its parent
8:00 9:00
snapshot. Other functions are the same
snapshot0 snapshot1
as common snapshots.
10:00 11:00
Snapshot1.snapshot0 Snapshot1.snapshot1
 Cross-level rollback: Snapshots sharing
the same source volume can roll back
each other regardless of their cascading
levels.
Key Technologies of HyperSnap-Duplicate
How can I obtain multiple

Source duplicates of the same
volume Snapshot snapshot?
8:00
Snapshots are virtual, so

8:00 8:00 8:00
they can be duplicated fast.
Key Technologies of HyperSnap - Rollback Before Write
How can I instantly recover data?
Source
volume Snapshot
Snapshot
rollback During the rollback, when a
8:00 host writes data to a source
LUN, the snapshot copies the
data blocks to the source LUN,
and then the host continues to
write data.
When no host reads or writes
data, the snapshot data is
rolled back to the source
volume in sequence.
Application Scenario
Source Snapshot
LUN LUN
Source
LUN
Snapshot
Duplicate Duplicate Duplicate Duplicate
LUN
1:00
2:00
4:00 3:00
Report Data Data Decision-

generation test analysis making
support
 Continuous data protection  Data backup and restoration
Required
Start
Optional
1. Checking the
Check the license
availability of the
snapshot function file.
Create a source Performing this operation when a

storage system does not have the
LUN.
source LUN of a snapshot.
2. Creating a snapshot Create a snapshot.
End
Contents
1. HyperSnap
2. HyperClone
3. HyperReplication
4. HyperMetro
Overview
 Definition
 HyperClone creates a full data copy (a target LUN) of a source LUN at a specified
point in time (synchronization start time).
 Features
 A target LUN can be read and written during synchronization.
 Full synchronization and incremental synchronization are supported.
 Forward synchronization and reverse synchronization are supported.
 Consistency groups are supported.
Working Principles of HyperClone
 Definition: Clone is a consistent data copy of a source data at a specific point in time. It functions as a
complete data copy after data synchronization. It serves as a data backup and is accessible to hosts.
 Main features:
 Quick clone generation: A storage system can generate a clone within several seconds to obtain a consistency copy of a
source data. The generated clone can be read and written immediately. Users can configure different deduplication and
compression attributes for the generated clone.
 Online splitting: A split can be performed to cancel the association between a source LUN and a clone LUN without
interrupting services. The split read and write operation on the clone LUN will not affect the I/O process of the source
LUN.
Create Synchronize
HyperClone. HyperClone.
a b c a b c a b c
d e f d e f d e f
g h i g h i g h i
j k l j k l j k l
HyperClone Principles - Synchronization
Scenario 1: Initial Scenario 2: Synchronization is
synchronization and full performed again after the first
copy are performed. synchronization, and differential
copy is performed.
a
b a a b Stored data
b
2 3
Snapshot c
1 2 a b c Newly copied data
Snapshot
1 c New data written to the host
a a
b b a a Internal signal flow of the
b b storage system
Source Target
LUN LUN c c
HyperClone pair
1 Create a HyperClone pair. Source Target
LUN LUN
2 Create a snapshot for the source
LUN after synchronization is 1 Create a snapshot for the source LUN
started. after a second synchronization.
3 Copy all data a and b to the target 2 Copy incremental data c to the target
LUN.
LUN.
HyperClone Principles - Reverse Synchronization
Scenario 1: Full copy Scenario 2: Differential copy a b c Stored data
a a a b c d Newly copied data

b b
c c
d New data written to the host
d d
2 1 2 1 Internal signal flow of the
Snapshot Snapshot storage system
HyperClone pair
a a a a
b b b b
c c c c
d d d d
Source Target Source Target
LUN LUN LUN LUN
1 Create a snapshot for the target LUN after 1 Create a snapshot for the target LUN after
the reverse synchronization is started. the reverse synchronization is started.
2 Copy all data a, b, c, and d to 2 Copy incremental data d to the source LUN.
the source LUN.
HyperSnap Principles - Restrictions on Feature Configuration
Feature Restriction
A source LUN of HyperSnap can be used as a source LUN of HyperClone, but a LUN of HyperSnap
HyperSnap
cannot be used as a target LUN of HyperClone.
HyperMetro A member LUN of HyperMetro can be used as a source or a target LUN of HyperClone.
Primary and secondary LUNs of HyperReplication can be used as a source or a target LUN of
HyperReplication
HyperClone.
SmartMigration A source or a target LUN of HyperClone cannot be used as the source or target LUN of SmartMigration.
SmartVirtualization A heterogeneous LUN cannot be used as a source or a target LUN of HyperClone.
HyperCDP A source LUN of HyperCDP can be used as a source or a target LUN of HyperClone.
Application Scenarios - Data Backup and Restoration
Source
Target LUN
LUN
Time
point A a  Create HyperCopy.
 Synchronize data on a source LUN to a target

Time LUN. In this case, the target LUN stores the data
a a
point B on the source LUN at time point B.
Time
point C a  Data on the source LUN is lost.
Time
 Reversely synchronize data on the target LUN
point D a a to the source LUN. In this case, the source
LUN is restored to the status at time point B.
Application Scenarios - Data Analysis and Reproduction
Data analysis
Source Data analysis The data analysis service uses data on a
LUN host
target LUN to prevent the data analysis
service and production service from
Reproducing n contending for resources of a source LUN
pieces of data Only for data
analysis and affecting performance.
Data reproduction
Target Target LUN Target LUN HyperClone can create multiple copies of the
LUN (1) (n-1) (n) same source LUN for multiple target LUNs.
Start
Check the license.
Create a protection
group.
Create a clone pair.
Create a clone
consistency group.
End
Contents
1. HyperSnap
2. HyperClone
3. HyperReplication
4. HyperMetro
Overview
 As a core technology for DR and backup, HyperReplication can realize the
remote data backup and disaster recovery.
Function Purpose Benefit
To recover service data using backup data in the This function prevents damage caused
Remote backup and
remote storage system after the service data is by data loss in the case that data at
recovery
invalid. the primary site becomes unavailable.
To quickly switch service data from the primary This function prevents damage caused
Continuous service
site to the secondary site to protect service by a service interruption upon a failure
support
continuity when a disaster occurs. at the primary site.
This function prevents damage caused

To recover data at the primary site using backup
DR by service data loss or a long recovery
data at the secondary site after a disaster.
duration after a disaster.
Introduction to DR and Backup
 When the HyperReplication feature is used, two data centers work in active/standby mode. The primary site is in
the service running status, and the DR center is in the non-service running status.
 For active/standby DR, when a device in data center A is faulty or even the entire data center A is faulty, services
are automatically switched to data center B.
 For backup, data center B backs up only data in data center A and does not carry services when data center A is
faulty.
Data center B (secondary site)

Data center A (primary site)
HyperReplication Concepts
 Question: What are HyperReplication pairs, consistency groups, synchronization,
splitting, primary/secondary switchover, data status, and writable secondary LUNs?
 To implement remote backup and recovery of service data, HyperReplication involves
the following phases: creating a HyperReplication relationship, data synchronization,
service switchover, and data recovery. What do these phases mean?
Phases for Realizing Remote Backup and Recovery of
Service Data
1. Create a HyperReplication pair. 2. Synchronize data.
Primary LUN Secondary LUN Primary LUN Secondary LUN
HyperReplication HyperReplication
Link Link
WAN WAN
Pair Pair
3. Switch over services. 4. Recover data.
Primary LUN Secondary LUN Primary LUN Secondary LUN

HyperReplication HyperReplication
Link Link
WAN WAN
Pair Pair
Running Status of a Pair
 By viewing the running status of a pair, you can perform synchronization, splitting, and primary/secondary
switchover operations on HyperReplication in time. After performing an operation, you can view the running
status of the pair to check whether the operation is successful.
Running
Description
Status
Normal Indicates that data synchronization between the primary and secondary LUNs is complete.
Indicates that data replication between the primary and secondary LUNs is suspended. For the need of services, a pair of primary
Splitting
and secondary LUNs is manually split. As a result, the running status of the pair changes to the splitting status.
Indicates that if the pair relationship between the primary and secondary LUNs is interrupted because the link used by
Interrupted
HyperReplication is down or the primary or secondary LUN of HyperReplication is faulty. The pair running status is interrupted.
Indicates that if HyperReplication requires to be restored using a manual policy after the fault caused by a pair interruption is
To be recovered rectified, the pair running status changes to the to-be-recovered status. This status indicates that users need to manually
synchronize data between the original primary LUN and the secondary LUN to restore the pair.
Indicates that if the original attributes of a primary or secondary LUN change when a pair is interrupted (for example, when the
Invalid HyperReplication link is down, the pair is deleted on the primary or secondary end), the pair running status changes to the
invalid status because the primary and secondary system configurations become inconsistent.
When the primary LUN is synchronizing data to the secondary LUN, the secondary LUN cannot be read or written. If a disaster
Synchronizing occurs, data on the secondary LUN cannot be used for service recovery. When the secondary LUN is in the complete status, data
on the secondary LUN can be used for service recovery.
Principles of Asynchronous Remote Replication
 Based on the known
Host
asynchronous remote
1 2 DCL
replication, try to draw a 3 6
RM
schematic diagram of
1 2
synchronous remote 5
Primary Secondary
replication. LUN Cache
Primary 5 Secondary
LUN LUN
4 4
Snapshot of the HyperReplication Link Snapshot of the
primary LUN secondary LUN
7 WAN 7
Snapshot of the Snapshot of the

primary LUN secondary LUN
DCL
Secondary Storage System
Primary Storage System
HyperReplication Service Switchover
Production Host Production host Standby host
Standby Host
√
Services run by the Read-only

Read-only
production host
Primary Secondary Primary Disconnected Secondary
Replication LUN LUN
LUN LUN Link
Link
WAN WAN
Secondary storage Primary storage Secondary storage
Primary storage
1. Normal production at the primary site 2. A disaster at the primary site
Production host Standby host

√
Services
Read/Write taken
over by
Primary Disconnected Secondary the 3. Service taken over by the secondary site
LUN Link LUN standby
host
WAN
Primary storage Secondary storage
HyperReplication Data Recovery
Production host Standby host Production host Standby host
√
Data
recovered
Services
run by the
Secondary Primary standby
Link Secondary New Primary
LUN LUN host.
Recovery LUN Link LUN
WAN WAN
Primary storage Secondary storage Primary storage Secondary storage
1. Disaster recovery at the primary site. 2. Data recovery at the primary site
Production host Standby host

√
Services
run by 3. Service recovery at the primary site
the Unreadable
producti Primary Unwritable
on host Replication Secondary
LUN
Link LUN
WAN
Primary storag Secondary storage
Functions of a Consistency Group
Primary LUN 01 CG 01 Secondary LUN 01 Primary LUN 01 CG 01
Secondary LUN 01
HyperReplication
HyperReplication Task 01
Task 01
Primary LUN 02 Secondary LUN 02 Primary LUN 02 Secondary LUN 02
HyperReplication
Task 02
Primary LUN 03 Secondary LUN 03 Primary LUN 03 Secondary LUN 03
HyperReplication
Task 03
1. Create a consistency group. 2. Stop replication tasks for the consistency group.
Primary LUN 01 CG 01 Secondary LUN 01
HyperReplication
Task 01
Primary LUN 02 Secondary LUN 02
HyperReplication 3. Ensure data validity for the consistency group.

Task 02
Primary LUN 03 Secondary LUN 03
HyperReplication
Task 03
Typical Application Scenarios
Analysis Item Central DR and Backup Geo-redundancy
Backup data is managed centrally so that data

analysis and data mining can be performed Three data centers are deployed in two cities to perform
without affecting services. real-time backup and remote backup concurrently.
When a disaster occurs at any service site, the Service data is backed up to an intra-city DR center in
central DR and backup site can quickly take over real time through a high-speed link.
Scenario feature its services and recover data, achieving unified After data in the primary site is invalid, services are
service data management. quickly switched to the intra-city DR center.
HyperReplication mode can be selected for a If a disaster damages the primary site and the DR center
service site flexibly based on the distance in the same city, an inter-city DR center takes over
between the service site and the central DR and services and implements DR.
backup site.
HyperReplication Intra-city: asynchronous remote replication

Asynchronous remote replication
mode Inter-city: asynchronous remote replication
Maximum distance
Asynchronous remote replication: no restriction Asynchronous remote replication: no restriction
for DR and backup
Central DR and Backup Scenario
 Central DR and backup refer to backing up service data from different places to the same site for centralized
management. Service data at multiple service sites is centrally backed up to and managed at the central DR
and backup site. When a disaster occurs, the central DR and backup site can take over services from the
service site and recover data.
Secondary
Primary LUN 02 HyperReplication 02 LUN 02
WAN
Host
Service site 02 Asynchronous
......
......
......
Secondary
Primary LUN n HyperReplication n LUN n
WAN
Service site n Asynchronous Central DR and

backup site
Realizing DR Used with BCManager eReplication
 BCManager eReplication is a DR management software specially designed for Huawei typical DR solutions. It
provides a visualized and process-based platform for simple and fast operations and monitoring based on
data consistency, HyperSnap, and HyperReplication technologies.
Primary site DR center
BCManager BCManager
Production host eReplication
eReplication
Server Agent
BCManager
eReplication
Agent
Standby host
BCManager
eReplication
Host
HyperReplication
Storage system Storage system
Start
Required
Check the license.
Optional
Create a logical port.
Manage a route.
Create an authentication user.
Add a remote device.
Create a protection group.
Create a HyperReplication
pair. Create a remote replication
consistency group.
End
Contents
1. HyperSnap
2. HyperClone
3. HyperReplication
4. HyperMetro
Overview
 HyperMetro is also called active-active feature. Two data centers are backups
for each other in the running status.
 If a device is faulty in a data center or even the entire center is faulty, the other
data center will automatically take over services, solving the problems of
traditional DR centers in switchover. This ensures high data reliability and
service continuity, and improves the resource utilization of the storage system.
Working Principles of HyperMetro
How to perform
arbitration when
Oracle RAC cluster/VMware a fault occurs?
vSphere cluster/
FusionSphere cluster
......
WAN
FC/IP SAN SAN SAN
FC/IP
Production Real-time data synchronization

Production
storage storage
IP network IP network
Quorum device
Quorum Mode
 If the link between two data centers is down or one data center is faulty, data
cannot be synchronized between the two data centers in real time. In this case,
only a HyperMetro pair or a site of HyperMetro consistency group can continue
providing services. For data consistency, HyperMetro adopts an arbitration
mechanism to determine service priority in data centers.
 HyperMetro provides two quorum modes:
 Static priority mode: applied to scenarios where no quorum server is configured.
 Quorum server mode (recommended): applied to scenarios where a quorum server
is configured.
Static Priority Mode
Fault Type Result
A HyperMetro pair is in the to-be-synchronized status.
A link between storage
LUNs in data center A continue providing services while LUNs in
systems is down.
data center B stop providing services.
Host Data center B is faulty. LUNs in data center A continue providing services while LUNs in
Data center A is faulty. LUNs in data center A cannot be accessed and LUNs in data center
B stop providing services.
A HyperMetro replication
HyperMetro link is down and a link
between a host and data
center B is down.
Data center B is faulty
and the link between the
Data center A Data center B host and data center B is
down.
Links between the host
A HyperMetro pair is in the normal status.
and data centers A and B
A host fails to access LUNs in both data center A and B.
are concurrently down.
Quorum Server Mode
Host Fault Type Result

The quorum server is faulty. LUNs in data center A and data center B continue
providing services.
A link between a storage system
and the quorum (example of the
LUNs in data center A and data center B continue
storage system in data center A)
HyperMetro providing services.
is down.
A storage system is faulty A HyperMetro pair is in the to-be-synchronized status.
(example of the storage system in LUNs in data center A are invalid, but LUNs in data center
data center A). B continue providing services.
A link between storage systems is
LUNs in data center A continue providing services while
down.
LUNs in data center B stop providing services.
A storage system and the quorum

server (example of the storage
Data center A is faulty and LUNs in data center B stop
Quorum server system in data center A) are
services.
concurrently faulty.
Dual-Write Principle
Host
Write I/O
1 5
Cross-site active-active cluster
Array A Array B
2 HyperMetro LUN
4
4 3 3
HyperMetro LUN HyperMetro LUN
Strong Data Consistency
Host Application cluster Host
Cross-site active-active cluster
Mutual exclusion of HyperMetro LUNs' distributed locks
Array A Array B
HyperMetro LUN HyperMetro LUN
Solution Extensibility Design
Disaster recovery solution HyperMetro data center solution
Site A Site B Site A
Upgraded Site B
architecture and
uninterrupted
services
Synchronous/
asynchronous HyperMetro
replication
Geo-redundant solution
Data Data Data center C
center A center B
Typical Application Scenarios
Industry Feature
With the development of hospital services, the growing numbers of beds and new outpatient buildings pose
higher requirements on service continuity.
Once critical departments such as out-patient, in-patient, and electronic medical record (EMR) are interrupted,
Healthcare medical treatment will be delayed and hospitals will suffer from great economic loss and inestimable damage to
their reputation. In addition, an out-patient building is close to an in-patient network information center in the
same hospital, and two hospitals in the same city are physically close to each other. HyperMetro can meet their
requirements.
In the finance industry, banking services, 24-hour ATM services, POS services, and e-bank services are developing
quickly as bank services develop. These services require that banking systems process around-the-clock services.
Finance For reliability and stability, banks require a solution to store for reused and meet their service construction
requirements (RPO = 0, RTO = 0) to ensure business continuity. Service interruptions damage banks' reputation
and pose huge pressure on technical departments.
In the social security industry, service continuity requirements are high. Monthly settlement and year-end carry-
over require 24/7 online operation. Otherwise, people's livelihood problems may occur. For example, pension
Social cannot be paid in time, and medical insurance cannot be settled in time.
security HyperMetro is applicable to social insurance application scenarios including the basic information management,
social insurance card service, labor relationship, public services, public resource management, employment, and
social insurance management.
Start
Required
Prepare the configuration. Optional
Configure the switches.
Configure quorum server

software. Check the license.
Add a remote device.
Create a quorum server.

Configure HyperMetro.
Create a HyperMetro
domain.
Create a HyperMetro pair.

Configure a multipathing
policy for hosts. Create a HyperMetro
consistency group.
End
Summary
HyperSnap
HyperClone
Storage Data Protection Definitions, principles,
Technologies and and configuration
Applications processes
HyperReplication
HyperMetro
Quiz
1. (True or false) A source LUN can form multiple HyperClone pairs with different target
LUNs. A target LUN can be added to only one HyperClone pair.
2. Which of the following statements are correct? ( )

A. Synchronous replication synchronizes data in real time to maximize data consistency and minimize
data loss in the event of a disaster.
B. Asynchronous replication performs periodic data synchronization, minimizing service performance

deterioration caused by data transmission latency.
C. HyperReplication does not require a license.
D. Synchronous replication uses snapshots for replication.
Quiz
1. Which of the following statements about consistency groups are correct? ( )

A. If multiple LUNs at the primary end have write dependency relationships, replication
consistency groups must be configured to ensure that the secondary LUNs also have
write dependency relationships.
B. A consistency group is only used to manage the replication relationship between

multiple LUNs.
C. If one member in a consistency group is faulty, all members in the consistency group
are unavailable.
More Information
Enterprise Huawei
support app business app
Recommendations

 Popular tools
 HedEx Lite
intelligent world.


Backup Solution Introduction
Foreword
This course introduces storage backup solutions for data centers, including:
 Overview
 Architecture
 Network
 Common technologies
 Typical applications
Objectives
After completing this course, you will be able to understand and master:
 Technologies of storage backup solutions for data centers
 Technical differences between backup and disaster recovery solutions
 Deployment of a backup solution
Contents
1. Overview
2. Architecture
3. Network
4. Common Technologies
5. Applications
Why Is Backup Important?
Legal requirements on data protection Risks of data loss
Software Viruses
Human and and Natural
errors hardware hacker disasters
failures attacks
Higher efficiency Lower costs Better data

utilization
Gartner: More than 30% of users use backup copies for development and testing,
and more than 20% of users adopt cloud-based disaster recovery.
What Is Backup?
 In information technology and data management, a backup refers to a copy of data in
a file system or database for swiftly and promptly recovering the valid data and normal
operation of the system when a disaster or misoperation occurs.
Application server
Nature: Stores a copy of data elsewhere.
Purpose: Recovers data when an accident occurs. LAN
Management Media server

server
Backup storage device
Why Is Backup Irreplaceable?
Two servers ≠ Backup System script X ≠ Backup

≠ Backup
Availability Security × Heterogeneous networks
 A cluster ≠ Backup
× Fault tolerance  A RAID array ≠ Backup

 High system  Accidental
× Openness  A dual-controller disk array ≠
availability deletion
× Complex backup policies Backup
 Physical fault  Logical
tolerance damage × Large databases  System script ≠ Backup
× × Special devices, such as

tape libraries
: Supported
×: Not supported
Backup and DR
Backup vs. DR
Backup: DR:
 Recovers missing data.  Recovers data from a recent
 Recovers damaged data. point in time.
: Supported
 Recovers historical data.  Directly takes over services.
X Recovers missing data.
×: Not supported
X Directly takes over services.
X Recovers damaged data.
Backup focuses on data recoverability, while DR is focused on application continuity.

Backup is the basis of DR.
Backup and Archive
Backup vs. Archive
Backup: Archive:
 Recovers data and system.  Retains data for a long term.
 Meets the SLA (RPO and RTO).  Meets legal requirements and
 Retains source data at the efficiency requirements. : Supported
original location.  Only retains data copies and ×: Not supported
 Provides data retention control. deletes source data.
 Provides object retention control.
Backup is for data recovery and archiving is for legal compliance.
Considerations
 Effective data recovery must be guaranteed. Requirements
Objective: data recovery Backup success rate
1. Reliable recovery Multiple data copies
Off-site protection
2. Availability of recovered data
Compatibility for applications
3. Fast recovery
Backup mode
4. Minimal system impact Backup data identification
Backup granularity
5. Recovery from a specified point in time
Data retention period
Challenges to Data Backup
A complex application
Challenges
Numerous data copies
Security threats
Contents
1. Overview
2. Architecture
3. Network
5. Applications
Components
Production center Backup center

LAN
...
Application server Backup management system
 Consists of backup management software

Application
server Database server File server Media Backup and backup management servers.
server management  Automatically initiates and performs a
SAN server
backup task, and reads and writes data
from the backup client to the backup media.
Backup media
Production
storage
Backup client Backup network Backup media
A client agent of backup software  Backup data flows from the backup client to  Devices that store backup data.
must be installed on service hosts the backup server over the backup network.  Tape library, VTL, disk array, CD-ROM
that need to be backed up.  TCP or IP network or Fibre Channel network tower, and cloud storage
Three Key Elements
Backup Window (BW)
Backup period for the backup system within a working period
Recovery Point Objective (RPO) Recovery Time Objective (RTO)

Tolerable amount of lost data Tolerable downtime
A backup task A backup Data can be A fault or A recovery task starts. A recovery task ends. Recover
starts. task ends. recovered from disaster occurs. applications.
any point in time
during this period.
BW 00:00 RPO 06:00 RTO 12:00
Backup Solutions
All-in-one backup
Hybrid cloud backup
Enterprise branch and SMB local backup
HUAWEI CLOUD
All-in-one backup node

Centralized backup
Centralized backup for data centers Remote backup center
Backup node
Replication with
deduplication
Backup node
Backup storage Huawei OceanStor

resource pool backup storage Physical and
resource pool virtual tape library
All-In-One Backup Solution
Item Description
Application Local backup for small data centers
Production  Integrated backup server and backup storage,

server ...
A greatly reducing device acquisition and maintenance
A
costs
Data Protection
Fibre  Broad compatibility for various operating systems,
Appliance
Channel or IP
databases, and virtualization environments
Benefits  Comprehensive protection for virtual, physical, and
Production
storage cloud environments. P2P, P2V, V2V, and V2P
A Backup agent migration scenarios

 Deduplication and compression
 Web UI for easy management, operation, and
maintenance
Centralized Backup Solution
Center
Backup
management
node (Backup software)
...
A A A A
IP network
Production server Backup service
Fibre Channel node
or IP
Production (Backup software) (Backup software)

Backup
storage
storage
Branch Branch
A
Backup Production ...

A Backup agent Production A ... A A A
service server
server
node
Fibre Channel Fibre Channel All-in-one
or IP backup
or IP
node
Production Backup storage Production storage

storage
Cloud Backup Solution
Backup service management Management flow

platform
ManageOne SC
Data flow
Data protection service
platform
DJ-DPS HUAWEI CLOUD
Cloud platform BC&DR management

FusionSphere OpenStack software Cloud DC 2
Highlights
 Huawei's unique two-level cloud backup solution can store backup
data in the local data center, in the backup resource pool of the
cloud data center, or in the S3 space of the public cloud.
 Huawei VBS can back up data to the backup resource pool of the
Production storage Backup storage remote cloud data center and or in the S3 space of the public cloud,
which can be used to build the two-level e-Government cloud.
DC 1
Contents
1. Overview
2. Architecture
3. Network
5. Applications
LAN-Base
LAN
Data flow Data flow
Agent Agent
File service Application service

Data flow
Command flow
LAN-Free
LAN
Application server Application server Backup server

Media server
SAN
Storage device Storage device Data flow

Command flow
Server-Free
LAN
Application server Backup server

Application server
Media server
SAN
Data flow
Storage device Storage device
Command flow
Server-Less (NDMP)
LAN
Application server Backup server

Application server
Media server
Tapes
Storage device
Data flow
Command flow
Architecture Comparison
Architecture Strength Weakness
Additional backup servers increase hardware costs.
Backup agents adversely affect the performance of application servers.
The backup system and the application
Backup data is transmitted over the LAN, which adversely affects network
system are separated, conserving
LAN-Base hardware resources of application
performance.
Backup services must be separately maintained, complicating management and
servers during backup.
maintenance operations.
Users must be quite competent in processing services.
Backup data is transmitted using no

Backup agents adversely affect the performance of application servers.
LAN resources, significantly improving
LAN-Free backup performance while maintaining
The costs are high.
Devices must meet certain requirements.
high network performance.
Backup data is transmitted using no
LAN resources, and network
The costs are high.
Server-Free performance remains unaffected.
Devices must meet strict requirements.
Host services remain nearly unaffected.
Backup performance is excellent.
Backup and recovery duration is

shortened. The throughput depends on
Workloads on the server are greatly relieved, but the backup software and its host
the speed of storage devices rather than
NDMP the processing capability of the server.
server are still required for backup process control. Metadata must be recorded in the
database of the backup software, which still consumes CPU resources.
Therefore, the system performance is
greatly improved.
Contents
1. Overview
2. Architecture
3. Network
5. Applications
Common Backup Types
Full backup Cumulative incremental backup Differential incremental backup
Sun. Sun. Sun.
Mon. Mon. Mon.
Tue. Tue. Tue.
Wed. Wed. Wed.
Thu. Thu. Thu.
Fri. Fri. Fri.
Sat. Sat. Sat.
Sun. Sun. Sun.
 All data is fully backed up.  Full backup is performed once  Full backup is performed once
 Easy management a week. a week.
 In the rest of the week, the  In the rest of the week, the
difference with the last full difference with the last backup
backup is backed up every day. is backed up every day.
* The definitions of incremental backup may vary with the backup software.
Backup Policies
Files, operating systems, databases,
Data to be backed up software, logs...
Backup media Disk, tape, cloud storage...
Full backup, incremental backup, and

Backup type differential backup
Source-side deduplication and target-side

Deduplication policy deduplication
Data retention period One month or one year
Backup frequency Daily or weekly
Backup window One week or one month
Deduplication
3. Maps data blocks to the fingerprint library.
1. Reads fingerprint data.
Storage unit Processing unit
Fingerprint pool
Memory-level File-level Global Task-level
Production server
Centralized backup solution

2. Transfers data with deduplication (data blocks with deduplication).
Memory-level deduplication: Fingerprint query and calculation are
Global deduplication: A fingerprint library is shared globally.
performed in the memory.
Highlights: high deduplication ratio for optimal resource utilization
Highlights: conserved disk I/O resources for higher query efficiency
Task-level deduplication: Backup tasks for different types of File-level deduplication: One fingerprint is created for each file,
applications use independent fingerprint databases. eliminating the need for data slicing.
Highlights: high fingerprint query efficiency and low memory usage Highlights: higher deduplication ratio
Fingerprint: It is a unique value calculated based on a data block by hashing.
Source-Side Deduplication
 Huawei Data Protection Appliance supports deduplication. That is, data is deduplicated
before being transferred to the storage media, greatly improving backup performance.
1. Calculates the
fingerprints of data blocks.
2. Queries fingerprints in
the fingerprint library.
3. Returns the query result.
Deduplication
fingerprint library
3. Transfers data blocks
without deduplication.
Data
Protection
Appliance
Backup storage pool
Parallel Deduplication
Parallel deduplication:
Deduplication fingerprint libraries are

created on multiple nodes and
fingerprints are distributed on these
nodes, effectively addressing poor
performance of a single node and
saving storage space.
Snapshot Backup
Production LUN/volume
Recovers copies.
Snapshot is performed every

two hours.
Storage array
Mount/Index
Retains copies.
Agent (media agent)

Disk Tape
Standard Backup
File systems
Windows, Linux, and UNIX Permanent
NeoKylin, Kylin, and Huawei Euler incremental Huawei Data Disk
backup
Protection Appliance
Volumes Parallel
deduplication Tape
Windows and Linux
Source-side
Databases deduplication
Operating systems Oracle: RMAN (Recovery

Compression Cloud
Windows, Red Hat, and SUSE Manager)
Encryption
 SQL Server: Virtual Device
Interface (VDI) Multi-channel
backup
Virtualization platforms
 DB2: Vendor
Blu-ray optical disc
 MySQL: MySQL Plugin Agent-free
VMware, H3C CAS, XenServer, backup
 GBase: GBase API
Hyper-V,  Informix, Dameng, Concurrent
FusionCompute, and Huawei Object storage
Kingbase, and Shentong: backup
HCS
export and import
Production data capture Copy management D2D2R or D2C
Continuous Backup
Continuous backup:
Data on production hosts is

continuously backed up to the
backup media.
With block-level continuous data

protection, data can be stored in
native format and host-level backup
and volume-level backup are
supported.
Advanced Backup
Oracle Snapshot
Fast recovery
copy 1 Copy 1
Development and
Oracle RAC Snapshot
copy 1 Copy 2 testing
Data mount
Snapshot and recovery Application data
SQL Server copy 1 Copy 3 extraction
in minutes
Snapshot
Snapshot ...
VMware Permanent Base volume copy 1
incremental Copy n Recovery to the
Snapshot
backup
Windows NTFS file system copy 1 same host
Clone volume
Recovery
Recovery to
another host
The system periodically creates a snapshot
Users can access and use
copy of any point in time for the base
Users can obtain application- virtual copies on demand or
volume and deletes a snapshot when a copy
consistent production data copies instantly and benefit from
expires.
in native format. diverse data services.
Production data capture Copy management Copy access and use
Contents
1. Overview
2. Architecture
3. Network
5. Applications
Database
Databases, such as GaussDB, Oracle, SQL Server, MySQL, DB2, and GBase, are supported.
* The preceding figure uses the Oracle database as an example.
Virtualization Platform
Virtualization platforms, such as VMware, FusionCompute, HCS, CAS, OpenStack, XenServer and Hyper-V, are
supported.
File System
Operating System
Windows
Linux
One of the defining features of Linux operating systems is that

everything is a file. Therefore, for backup of a Linux operating
system, we just need to back up the files in the operating system
and then modify configuration file and boot upon recovery.
Quiz
1. (Multiple) Which are not common backup types?
A. Full backup
B. Incremental backup
C. Extension backup
D. Elastic backup
2. (Single) Which is not a common backup topology?

A. LAN-Base
B. LAN-Free
C. Server-Free
D. Server-Base
Section Summary
Overview
Architecture
Backup solution Network
Common
technologies
Applications
More Information
Enterprise Huawei
Recommendations

 Popular tools
 HedEx Lite
intelligent world.


DR Solution Introduction
Foreword
 This part includes:

 Definition of the DR system and importance of the DR system to enterprise
service continuity
 Common solutions of the DR system
 Technology used by the DR system
 Success stories of the DR solution
Objectives
On completion of this course, you will be able to:

 Describe the concept and importance of the DR system.
 Know advantages and disadvantages of common DR solutions.
 Master the technical principles of the DR solution.
 Learn how to deploy a DR system based on typical application cases of the DR
solution.
Contents
1. DR Solution Overview
2. DR Solution Architecture
3. Common DR Technologies
4. DR Application Cases
DR Requirements
 Three risks: data loss, data damage, and service interruption. The loss caused by service
interruption per hour is millions of dollars.
 Regulatory compliance: financial compliance, security isolation, geo-redundant solution, and high
service continuity
 IT O&M: System disaster recovery simplifies IT O&M work and avoids the impact of major events.
Enterprise: Avoid major Enterprise: Comply with IT: Simplify O&M and
losses and reduce policies and regulations, avoid the impact of
enterprise risks. and meet industry emergencies.
regulatory requirements.
DR Challenges
Cumbersome
Costly investment Limited DR capability
management
High capital expenditure Multiple devices are not Poor security and DR
(CAPEX) centrally managed. capabilities
 High purchase costs of  Independent storage media,  Data cannot be backed up out
infrastructure such as servers, servers, and network of the data center, and
storage devices, and software management pages, complex infrastructure faults may cause
 High basic construction costs workflows, and low efficiency extreme situations.
on facilities such as equipment Complicated capacity Poor agility
rooms. expansion  Capabilities such as disaster
High OPEX  The capacity is insufficient and recovery and data sharing are
 Professional O&M support needs to be expanded. The restricted by physical locations
(implementation, training, and rollout period is long. of data. Applications and data
onsite support) cannot be separated. Agile
 Long-term costs on resources applications and better DR
such as water and electricity. features cannot be built.
HA
 High availability (HA) ensures that applications can still be accessed when a single component of the local system is faulty,
no matter whether the fault is a service software fault, physical facility fault, or IT software/hardware fault.
 The best HA is that users using the data center service are completely unaware of a machine that breaks down in the data
center. However, if a server in a data center breaks down, it takes some time for services running on the server to fail over. As
a result, customers will be aware of the failure.
 The key indicator of HA is availability. Its calculation formula is [1 – (Downtime)/(Downtime + Runtime)]. The following nines
are used to represent availability:
 4 nines: 99.99% = 0.01% x 365 x 24 x 60 = 52.56 minutes/year
 5 nines: 99.999% = 0.001% x 365 = 5.265 minutes/year
 6 nines: 99.9999% = 0.0001% x 365 = 31 seconds/year
 For HA, shared storage is usually used. In this case, RPO = 0. In addition, the active/active cluster HA mode is used to ensure
that RTO is almost 0. If the active/passive HA mode is used, RTO needs to be reduced to the minimum.
Disaster Recovery
 A disaster is an unexpected event (caused by human errors or natural factors) that results in
severe faults or breakdown of the system in one data center. In this case, services may be
interrupted or become unacceptable. If the system unavailability reaches a certain level at a
specific time, the system must be switched to the standby site.
 Disaster recovery (DR) refers to the capability of recovering data, applications, and services in
data centers at different locations when the production center is damaged by a disaster.
 In the DR mode, a redundant site is established in addition to the production site. If the
production site is damaged due to a disaster, the redundant site can take over services from the
production site to ensure service continuity. To achieve higher availability, customers even
establish multiple redundant sites.
Relationship Between HA and DR
 They are interrelated and complementary to each other. They overlap with each other
and have significant differences.
Dimension HA DR
HA refers to a local HA system. When one or more
applications are running on multiple servers, ensure that DR refers to a remote (intra-city or remote) HA system. It is
Scenario the running applications are not interrupted when any used to recover data, applications, and services when a disaster
server is faulty. The applications and system can be occurs.
quickly switched to other servers.
Data replication is used for remote disaster recovery data.
Generally, HA uses shared storage. Therefore, data will Based on different data replication technologies (synchronous
Storage not be lost (RPO = 0) and the switchover duration, that and asynchronous), data loss often causes RPO to be greater
is, RTO, is considered. than 0. However, remote application switchover usually takes a
longer time. In this case, RTO is greater than 0.
Load switchover between servers in the cluster caused by Service switchover between data centers caused by large-scale
Fault a single faulty component. faults.
Network HA is used in LAN. DR is used in WAN.

HA is a mechanism that ensures service continuity in a DR is a mechanism that ensures service continuity among
Cloud cloud environment. multiple cloud environments.
Objective HA is used to ensure high availability of services. DR ensures data reliability and service availability.
Differences Between DR and Backup
 Backup: Backup is a process of copying all or part of data
DC1
sets from an application host's disks or a storage array to
other storage media in a data center. Backup is a method
of DR. MA MA CS
iDA iDA MA
Backup & VTL/NAS
SAN
Archive
Server
 DR: A DR system consists of two or more sets of IT systems PTL
that are geographically far from each other. These IT Production Center Backup Center
systems provide the same functions, and monitor the

DC1 DC2
health status of each other. In the event of an accident APP
APP
APP APP
APP
APP
OS
OSOS OS
OSOS
(such as a fire or an earthquake), applications on a broken- HA
down system can be switched to other systems to ensure Cluster

business continuity.
Mirror
 Generally, DR indicates the backup of data or application systems across equipment rooms, whereas backup refers to local data or system backup.
 A DR and backup solution combines local backup and remote data replication to provide comprehensive data protection.
Main Indicators for Measuring a DR System
 Recovery Point Objective (RPO) indicates the maximum amount of data that can be lost when a disaster occurs.
 Recovery Time Object (RTO) indicates the time for system recovery.
 The smaller the RPO and RTO, the higher the system availability, and the larger the investment required by users.
Backup Backup A fault or Recovery Data Application

started completed Point in disaster started Time recovery recovery
time to occurs. required completed
which data for data
is recovered recovery
Backup 00:00
window RPO 06:00
RTO 12:00
Levels of DR Systems
Level Definition RTO TCO
Builds a remote DR center to back up data remotely, which prevents data loss
or corruption in the event of a disaster.
The remote DR center is considered as a remote data backup center. Data- The RTO is the longest
level DR cannot prevent service interruption if a disaster occurs. (several days) because
Data level The recovery time of data-level disaster recovery is long, but the cost is low
device re-deployment Lowest
is needed to restore
and facilities are easy to construct. services.
The data source is essential to all key service systems. Therefore, data-level
DR is indispensable.
Builds a backup site that carries the same application system as the Medium. The same
production site, and uses synchronous or asynchronous replication to system or a smaller
Medium RTO (several
Application level synchronize data between the sites. This allows critical applications to recover
hours)
system can be
within the specified time and minimizes the loss. Data recovery is transparent established at the
to users, ensuring integral, reliable, and secure businesses. backup site.
Requires all of the necessary IT technologies and infrastructures to achieve

full-service DR. Most of the contents are from non-IT systems (such as Shortest RTO (several
Service level telephones and offices). If a disaster damages the original office, a backup minutes or seconds)
Highest
office is also needed in addition to data and application recovery.
Global Standards for a Disaster Recovery System
According to SHARE 78, a disaster recovery system can be categorized into 7 tiers:
Expenses Remote DR center

Tier 7: Near-zero or zero data loss, remote data mirroring, and automatic service switchover
Tier 6: Near-zero or zero data loss. Remote data mirroring ensures data integrity
and consistency.
Tier 5: transaction integrity
Tier 4: Batch/online database image or log transmission

Available backup center
Tier 3: electronic vaulting
Tier 2: PTAM + Hot standby site

Time-based backup
Tier 1 – PTAM
15Min 1~4Hr 4~8Hr 8~12Hr 12~16hr 24Hr Days Weeks RTO
Huawei Business Continuity and Disaster Recovery
(BC&DR) Solution
FusionCloud
Cloud server high
Remote DR availability
Local production center Cloud server Cloud server
Intra-city DR disaster recovery backup service
center center
 Geo-redundant DR Volume high Volume backup
 HyperMetro DC solution solution availability service
 Local HA solution  Active-passive DR solution  Active-passive DR
solution
Private cloud
≥ 100 km
≤100 km
Cloud server backup service

 Centralized backup solution and
integrated backup solution
Volume backup service
 Converged data management Volume high availability
Traditional data center Public cloud

Contents
Disaster Recovery and Backup Solution
Government Finance Transportation Energy Education Healthcare ......
International China Consulting

standard standard Cloud computing mode Physical server mode
Application-level DR Application-level DR Cooperation
Levels 6 Level 6 delivery
to 7 Same-city application-level DR
Active-active
cloud DR DR
WAN application-level DR selection
Data-level DR Data-level DR Link

Level 4 Level 4 design
Array replication–
to 5 to 5 Database DR
Active-passive based DR
CDP DR Drill
cloud DR
Virtual storage DR switchover
Level 3 Level 3 Service

Backup Backup
delivery
VM backup Backup software

Integrated backup Evaluation
backup
Levels 1 Levels 1 optimization
to 2 to 2
DR Design Mode: Combination of Synchronous and
Asynchronous Modes
High Active- Synchronous disaster recovery: Asynchronous disaster recovery:
Hot active distance limit exists. no distance limit
backup
Availability
2 3
Warm
backup 1 1
Low High
3 4
4 2
Cold
backup RPO: from 30 minutes to several hours,
RPO: 0s. The two images are the same. with data synchronized regularly
Low
resource utilization
DR Mode Reliability Solution Disaster Recovery Data Backup Requirement
Active-active Cluster + Load balancing Automatic Real-time synchronous replication (< 100 km)
Hot backup Cluster Automatic Real-time synchronous replication (< 100 km)
Warm backup Manual intervention Manual Asynchronous replication (> 100 km)
Cold backup Strong manual intervention Manual Same as above
Active-Passive DR Solution
WAN
Production center DR center

Disaster
recovery
VM VM VM VM VM VM management VM VM VM VM VM VM
Virtualization/
Middleware/
Applications
Database
SAN SAN
Synchronous/
Asynchronous
replication
Active-Active DR Solution
WAN
Production center 1 GSLB/SLB Data center 2

cluster
(F5/L2800)
VM VMVM VMVMVM VM VMVM VMVMVM
FusionSphere
/VMware
/WebLogic
/WAS cluster
Oracle, DB2,
or SQL Server
cluster
SAN SAN
HyperMetro
V3 mid-range
and high-end
storage
Geo-Redundant DR Solution
Cascading architecture
Production center Same-city DR center Remote DR center
HyperMetro or
synchronous/
A Asynchronous
asynchronous
replication replication
SAN SAN SAN
A A A
Parallel architecture
Production center Same-city DR center
Synchronous/
A asynchronous
replication Remote DR center
(HyperMetro)
SAN SAN
A A
Asynchronous SAN
replication A
New DR Mode Evolution in Cloud Computing
High reliability in traditional data centers Traditional cross-DC DR
Component redundancy and Dual-host hot backup Mainly service data replication
high device reliability The recovery process is complex and the recovery period is long.
High reliability in cloud computing data centers Cloud computing cross-DC DR
App App App App VM: WEB VM: WEB

OS+Apache OS+Apache
OS OS OS OS
VM: APP VM VM: APP
OS+J2EE migration OS+J2EE
Cloud management platform
VM: DB VM: DB
OS+DB OS+DB
Storage
All service data and running environment data are replicated and
Automatic migration of VMs (including services) managed in an integrated manner.
The recovery process is simple and the recovery period is short.
Implementation of Cloud Active/Passive Data-Level DR
Production center DR center (passive)
(active)
APP APP ESC/CRM/ APP APP

APP APP APP APP
OS APP OS APP OMM OS APP OS APP
OS OS ESC/CRM/OMM OS OS
OS OS OS OS
Management
data
replication
IP SAN IP SAN
VM data
replication
Production storage pool DR storage pool
IP network Protected LUN

FC network Protected LUN copy Unprotected LUN
Contents
Major Disaster Recovery Technologies
Applications Applications
Database management system Database management system

Host layer
OS OS
File system • Application replication File system
• Database replication
Raw devices/volumes • Logical volume replication Raw devices/volumes
Device I/O driver Device I/O driver
SAN IP SAN-based network layer SAN IP
Array layer
Disk array NAS Disk array NAS
Host Layer DR Technology - Application Level
 The application-level DR technology uses application software to implement remote data
replication and synchronization. When the production center fails, the application software system
in the DR center recovers and takes over services from the production center.
Host Layer DR Technology - Database Level
 The database-level DR technology is designed for specific databases. Generally, typical databases
have the database-level DR function, for example, Oracle Data Guard and DB2 HADR. Database-
level DR is implemented by transmitting database logs and replaying them at the DR site. The
database-level DR technology supports smooth switchover.
Host Layer DR Technology - Logical Volume Level
 Remote data replication based on logical disk volumes refers to remote synchronous (or
asynchronous) replication of one or more volumes as required. This solution is usually
implemented by using software.
WAN
Volume Replication System/Software
Servers
Servers
Fiber Connection/DWDM
FC Switch
FC Switch
Storage Storage
Device Device
Network-layer DR Technology
 A smart switch is added to the storage area network (SAN) between the front-
end application servers and back-end storage systems.
Production Center DR Center
③Write completed
New Data Write ① ④Write Request to DR Center
⑤Confirmation Signal from DR
⑦Write Completion Signal from DR

⑥Write into Replication
Write into Log Volume② ④Write into Production Volume
Volume
Production Replication
LOG Log Volume
Volume
Array-layer DR Technology
 Array-level DR is implemented using the inter-array replication technology. The
replication of the array does not pass through the host. Therefore, the impact on the
host performance is small.
Application
LAN
Application
Hosts
FC/IP FC/IP FC/IP

Switch Switch
SAN
Local Storage Remote Storage

System System
SAN Synchronous Replication
Production DR center
center DR management
DR DR server
network network
WAN
Service plane
Application (Optional)
server Data DR servers
replication
network
FC switch
FC switch
DWDM DWDM
Synchronous
IP management network
replication
IP service network
FC network
Data flow
Server
Agent
Huawei OceanStor Huawei OceanStor
Hybrid Flash Storage Hybrid Flash Storage
SAN Synchronous Replication Principles
① Synchronous
Replication
②
③ ②
Cache Cache
③
④
Primary Secondar
Host y LUN
LUN
DR Storage
Production Storage
DB Server
Cache Synchronou Cache

s
Data Change Log (DCL) LUN A LUN B
Primary Site Secondary Site
SAN Asynchronous Replication DR
Production DR center DR management
center server
DR management DR management
WAN
network network
Service plane
(Optional) DR
Application
servers
server
FC switch
FC switch
IP management network
WAN IP service network
FC network
Data flow
Server
Agent
Hybrid Flash Storage Hybrid Flash Storage
SAN Asynchronous Replication Principles
4
N+1 x+1
2 1 1
N x
Cache Cache
DB Server 3 5 Asynchronous Replication
5
LUN A
Primary Site Secondary Site LUN B
Production Backup
Server Production
Server
Primary Secondary
LUN LUN
Switch Switch
Secondary Primary
Primary Site LUN LUN
Secondary Site
NAS Asynchronous Replication DR
Production DR center DR
center management
server
DRM network WAN DRM network
Service
network
(Optional)
DR servers
Application
servers
FC
switches
FC IP management
switches network
IP service
WAN network
FC network
Huawei OceanStor Asynchronous Data flow
Hybrid Flash Storage replication Server
Agent
Huawei OceanStor Hybrid
Flash Storage
DRM: Disaster recovery
management
NAS Asynchronous Replication Principles
Replicate
Incremental
① ④ Data
Primary FS Secondary FS
③
⑤
②
Host
Primary FS Secondary
Snapshot FS Snapshot
Production Storage DR Storage
Multi-Point-in-Time Asynchronous Remote Replication
Technology – Second-Level RPO
DB Server
3 2
Time Time
segment T2 segment T2
4
Time Time
segment T1 segment T1
Cache 1 Cache 1
Asynchronous remote
5 5
replication
Active LUN Standby LUN
Production DR center
center
Remote Replication - Application Consistency
Host Consistency Agent Application engine
Triggered Requests
periodically archiving
Writes the data in the

Host status
memory to the disk.
recovered.
1 2 3 4 5 6
Memory
7 8 9 A B C
Storage array Completed Host channel
Snapshot
Mirroring
Replication
Remote Replication - Consistency Group
 A consistency group ensures time consistency of mirrored data among multiple LUNs.
 All pairs in a consistency group are simultaneously synchronized, split, interrupted, or
switched over.
Active LUN 1 Standby LUN 1
Comparison of DR Technologies
This function is implemented on hosts, and the compatibility between underlying devices does not
Advantages
Host layer (typical need to be considered.
replication software such During database replication, the DR center can take over part of the work of the production center.
as Symantec VVR, Oracle
DataGuard, DSG and Database replication can be implemented only for the corresponding database.
Quest) Disadvantages Host-layer replication occupies certain host resources and affects the application system.
Implemented on hosts, which is complex and usually requires system reconstruction.
Broad compatibility with different back-end heterogeneous SAN storage resources.

Advantages Simultaneous disaster recovery for multiple SAN arrays without a one-to-one relationship.
Network layer (typically Extendable disaster recovery platform.
IBM SVC, EMC VPLEX, No extra investment required as the number of hosts and arrays increases.
and Huawei VIS)
Disadvantages High initial investment because few vendors can provide such a solution.
Data replication does not affect the host application system.

When the production array is faulty, applications can be switched to the DR array in a short time.
Array layer (arrays that Advantages Data replication is implemented based on lower-layer arrays, and users are not charged based on
support mirroring or host licenses.
replication, such as
Huawei OceanStor Does not support heterogeneous storage arrays. Storage arrays at the production center and the
series) Disadvantages disaster recovery center must be from the same vendor.
The data at the remote site cannot be accessed in real time. The data can be viewed only after the
data volume can be read and written or the snapshot mode is used.
Typical DR Drill Solution
Drill switchback
Publishing the drill
start message
Analysis and
Making a drill plan
assessment
Drill switchover Verification after the

drill switchback
Approving the Verification Publishing the drill Drill summary

drill plan after the drill finish message
switchover
Contents
Case 1: XX Virtualization DR Project
2、The standby end requests the

1、The active end creates a replication task information from
remote replication task (task 1). Windows the active end, and then creates a
Windows
The active LUN is LUN 1, and the Server recovery task at the backup end
Server
standby LUN is LUN 1'. based on a replication task.
HA HA
Linux Linux Linux Linux Linux Linux

Server Server Server Server Server Server
A disaster
occurs at the 4、The replication task is complete.
active end. 3、The active end starts
task1 to copy data from
LUN1 to LUN1‘. 5、The standby end chooses
snapshots to recover VMs based on
the specified recovery task.
Case 2: Application-Level DR Solution
MSTP Internet
Production center DR center

Data
replication
2 Mbit/s
GSLB Core switch private line Core switch GSLB
CDP CDP
aggregation aggregation
switch switch
Application Application
IP SAN server server IP SAN
switch switch
CDP device CDP device
Data Data
replication replication
Production storage CDP storage CDP storage Production storage
Quiz
1. (Multiple) Data replication is the core of a DR technology. On which three layers are replication
devices distributed? ( )
A. Application layer
B. Host layer
C. Network layer
D. Storage layer
2. (True or False) When designing a DR solution, set RTO to 0 to ensure that services are not
interrupted. ( )
Summary
DR Solution Overview
DR Solution Architecture
DR Solution Introduction
Common DR
Technologies
DR Application Cases
More Information
Enterprise Huawei
Recommendations

 Popular tools
 HedEx Lite
intelligent world.


Storage System Operation Management
Foreword
 This chapter describes two methods of managing storage systems:

OceanStor DeviceManager and CLI, as well as management content and
related operations.
Objectives

 DeviceManager and CLI storage system management tools.
 Basic management operations of the storage system.
Contents
1. Storage Management Overview
2. Storage Management Tools
3. Basic Management Operations
Storage Management Definition
 Storage management allows users to use management tools to query, set,
manage, and maintain storage systems.
Storage resource allocation
User management
Management
content
Data protection feature management
Device performance monitoring
Alarm management
......
Common Storage System Access Mode
In what ways can I log in to a

storage system?
Log in to DeviceManager.
Log in to the CLI.
Main Functions of DeviceManager
 DeviceManager is storage management software designed by Huawei for a single storage system.
It can help you easily configure, manage, and maintain storage devices.
 Main software functions include storage resource allocation, user management, data protection
feature management, device performance monitoring, and alarm management.
Logging In Using DeviceManager
You must add port number 8088 after

the IP address of the management
Enter an IP address. Enter port number 8088. network port. Otherwise, the login fails.
Format: https://xxx.xxx.xxx.xxx:8088
Enter the user name.

Enter the
password.
Introduction to the CLI
 CLI allows you to manage and maintain the storage system. Configuration commands are entered on the keyboard and
compiled and executed by programs. The command output is displayed in text or graphics on the CLI.
 Terminal software is required for logging in to the CLI. PuTTY is used as an example.
Enter the IP address of the

management network port.
Set Connection type to SSH.
Click Open. The CLI window is displayed asking

you to log in.
Logging In Using the CLI
 Enter the user name and password as prompted. The system asks you to change the password upon the first login. Change
the password immediately to ensure system security. The following information is displayed when the login is successful:
1. Enter the
user name.
2. Enter the
password.
3. Change the
password.
Contents

 DeviceManager
▫ CLI
DeviceManager GUI (1)
Navigation bar
Alarm and task statistics area
Function pane
Note: The GUI may vary slightly depending on the product version and model. The actual GUI prevails.
DeviceManager GUI (2)
No. Name Description
1 Function pane Displays available functions related to the current operation.
2 Navigation bar Lists all functional modules of the storage system.
The alarm statistics area displays the number of alarms by severity

and helps users learn about the running status of the storage
Alarm and task statistics
3 system.
area
The task statistics area displays all the tasks executed by users. You
can check whether the tasks are executed successfully.
In the device management area, you can view and modify device
4 Device management area
information, and power off or restart devices.
The logout and language area provide buttons of logout and
Logout and language
5 language. DeviceManager supports two languages: English and
area
simplified Chinese.
Managing the Access Permission of a Storage System
• Account policy
• Login policy
Security • Access control
policy • Account audit
adjustment
Ensuring system
security • IP address or address
• Administrator-----role User Access IP
segment list
• management address
Role--operation rights
control • Operation rights of the
super administrator
Storage System User Management
 To prevent misoperations from compromising the storage system stability and service data security, the
storage system defines user levels and roles to determine user permission and scope of permission.
Operation permission
Level: super administrator
Role: super administrator
All functional modules of
the system
User A
Creating a user and specifying the

user level and role
Operation permission Access permission

Level: administrator Level: read-only user
Role: built-in role B Role: customized role C
Disk Storage
...... LUN Host ......
domain pool
User B User C
Roles and Permissions of a User
• Full control permissions
Data protection • Local data protection
• Creates users of different levels. 5 administrator • Remote data protection
management
Super
administrator 1 • HyperMetro
management
4 SAN resource •
administrator
Storage pool
management
Security 2 •
•
LUN management
Mapping view
administrator 3 Network •
management
Host management
administrator • Port management
• Security rule management
• Certificate management
• Physical port management
• KMC management
• Logical port management
• Antivirus management
• VLAN management
• Data destruction management
• Failover group management
• Regulatory clock management
Downloading a DeviceManager Demo
Visit Huawei technical support

website: Go to Tools.
support.huawei.com
Click Storage Simulator Demo

and select the simulator of the Search for Storage Simulator.
desired version for installation.
Contents

▫ DeviceManager
 CLI
3. 3. Basic Management Operations
CLI Format Conventions (1)
 You are required to follow the format conventions when you use the CLI commands. Typical
command formats are:
change storage_pool relocation_speed relocation_speed=?

1 2 3
show host
 First field: operation that you want to perform, for example, change (modify) and show (query)
 Second field: object of an operation, for example, storage_pool (storage pool) and host (host)
 Third field (available only in some commands): object attribute, for example, relocation_speed (migration
rate)
 Other fields: other parameters required.
CLI Format Conventions (2)
 For example, change user user_name=? { level=? | action=? }
 change user keeps unchanged.
 user_name=?, mandatory; For level=? and action=?, one of them can be selected.
 For parameter level=?, level= remains unchanged. The value of ? must be an optional value, for example, level=admin.
Correct command example: admin:/>change user user_name=newuser level=admin
Format Description
Boldface The keywords of a command are in boldface.
Italic The arguments of a command line, which will be replaced by actual values, are in italics.
[] Items in square brackets [ ] are optional.
{ x | y | ... } Indicates that one option is selected from two or more options.
[ x | y | ... ] Indicates that one or no option is selected from two or more options.
Indicates that multiple options are selected from two or more options. At least one option must be selected, and at most all
{ x | y | ... } *
options can be selected.
[ x | y | ... ] * Indicates that multiple options are selected or none is selected from two or more options.
CLI Command Completion
 On the CLI, you can press Tab or the space bar to use the command completion function.
 The difference between the two keys is as follows: The space key is used to supplement only the current field,
whereas the Tab key is used to supplement all possible values.
After the starting segment is determined and completed, press

Press Tab once to display the available
Tab once to display the available adjacent segments of the
starting segments of a command line.
starting segment.
admin:/>//Press“Tab” admin:/>add//Press“Tab”
^ cache_partition clone consistency_group
add change create disk_domain host host_group
delete exit export lun_copy lun_group mapping_view
help import poweroff notification port port_group
poweron reboot remove remote_device security_rule smartqos_policy
scan show swap snmp storage_pool
When all the fields required by the command are entered and the conditions for running the command are met, the
system prompts that the command can be run after you press Tab. In this case, you can press Enter to run the command.
admin:/>add port ipv4_route eth_port_id=0 type=net target_ip=192.168.3.0 mask=255.255.255.0 gateway=10.0.0.1//Press“Tab”
Command is executable now.
Context-Sensitive Help
• Enter a question mark (?) to

• Press Ctrl+A to view the query the basic instruction of CLI
optional values of certain operations and detailed
parameters in certain description of command
commands. Generally, these parameters.
Ctrl+A ?
values need to be obtained • After entering the first field of the
from the system. Context- command and a space, enter a
sensitive question mark (?). You can query all
Help available next fields and the detailed
PageDown description of each field.
• You can turn pages on the
context-sensitive help page. PageUp q
• Exit the context-
sensitive help page.
CLI Command Filtering
Redundant information is deleted, and valid
Purpose
content is displayed as required.
After entering the complete query command, enter |

How to Use
and press Tab or the space bar.
Filtering
Related • filterColumn column filtering command

Commands
• filterRow row filtering command
CLI Column Filtering Command - filterColumn
show xxx|filterColumn { exclude | include } columnList=?
}
Choose either. Columns available
for filtering
exclude: Filter out information that does

not need to be displayed. If multiple columns are involved, they are
separated by commas (,).
Include: Only the columns to be displayed
are reserved.
admin:/>show bbu general|filterColumn exclude//Press“Tab” admin:/>show bbu general |filterColumn include

<columnList=?> column list separated by comma, select one or more columnList=Inter\sID,ID
seperated by comma, the spaces are replaced with \s in the
parameter list. Inter ID ID
columnList=Inter\sID columnList=ID -------- ------
columnList=Health\sStatus columnList=Running\sStatus 0.0A.0 CTE0.0
columnList=Current\sVoltage(V) columnList=Number\sOf\sDischarges 0.0A.1 CTE0.1
columnList=Firmware\sVersion columnList=Delivered\sOn
columnList=Owning\sController columnList=Electronic\sLabel
CLI Row Filtering Command - filterRow
show xxx|filterRow column=? predict=? [ predict2=? ] value=? [ logicOp=? ]
Columns required Filtering Filtering Logical relationship

for filtering condition condition 2 Value
between columns
predict=? logicOp=?
• not: The logicOp is not. • and: Multiple columns
• equal_to: a value equal to value=? that meet the condition
• greater_than: a value greater than are displayed.
value=? • or: Any column that
• greater_equal: a value equal to or meets the condition is
greater than value=? displayed.
• less_than: a value less than value=?
• less_equal: a value less than or
equal to value=?
• match: regular expression matching
value=?
Error Prompt Function
Specify the position of the input error in the command

Purpose
and provide the correct field for reference.
Error
When the format of the entered command is incorrect,
prompt How to Use
the system displays the error location with symbol ^.
function
When multiple errors occur in the command,

Note
the system displays only the first error.
admin:/>add part
^
port port_group
admin:/>add part
Contents
Basic Management Operations
Version information
and ESN
Managing a storage 3 Managing alarms

system license and events
2 4
1 5
Collecting storage
Managing basic
system information
information about a
storage system
Configuring basic
storage services
Managing Basic Information About a Storage System -
Setting the Device Time (1)
A protocol used to synchronize the system time of a computer to the

Coordinated Universal Time (UTC). A server that supports the NTP
Introduction
protocol is called an NTP server.
When an alarm is generated, users can accurately locate the time

NTP Function
when the alarm is generated based on alarm logs.
• Set the time manually.

Setting mode • Synchronize the client time.
• Set automatic NTP synchronization.
Managing Basic Information About a Storage System -
Setting the Device Time (2)
 Managing the device time on DeviceManager  Managing the device time on the CLI
 The change ntp_server config command is used to
automatically synchronize the storage system time
with the NTP server time.
 The show system ntp command is used to query
NTP settings.
 The show ntp status command is used to query the
NTP status.
 The show ntp_server general command is used to
query the settings of the time synchronization
function.
Managing Device Licenses (1)
Permission credentials for using various value-added features (such as

Introduction
snapshot, remote replication, clone, and SmartQoS)
License
file
Precautions During routine device management, you need to check whether the
license file is available.
Using DeviceManager to manage licenses
Based on the status of the imported or activated license, different license operations are
displayed on the License Management page: Import License, Activate License, and Update
License.
For an activated license file, DeviceManager provides two control modes:
 Running time-based control: displays the expiration time of the license.
 Capacity-based control: displays the used/total capacity of the license.
Viewing Device Licenses (2)
Using CLI to manage licenses
 The export license command is used to export a license file.

Example: export license ip=? user=? password=? license_path=? [ port=? ] [ protocol=? ]
 The import license command is used to import a license file.

Example: import license ip=? user=? password=? license_path=? [ port=? ] [ protocol=? ]
 The show license command is used to query the function configuration of the imported license file in
the system.
Example: show license
 The show license_active command is used to query information about active licenses.
Example: show license_active
Obtaining the Current Version Information of the Device
Version The matching software version can be accurately determined

Information Function
based on the system version.
 Obtaining the current system version information  Log in to the CLI as a super administrator.
on DeviceManager  Run the show system general command.
 The following shows the device information:  Product Version indicates the version of the current storage
system.
admin:/>show system general
System Name : XXX.Storage
Health Status : Normal
Running Status : Normal
Total Capacity : 3.186TB
SN : 210235G6EHZ0CX0000XX
Location :
Product Model : XXXX
Product Version : VX00R00XCXX
High Water Level(%) : 80
Low Water Level(%) : 20
WWN : XXXX
Time : 2020-07-07/15:34:05 UTC+08:00
Patch Version : SPCXXX SPHXXX
Description :
Obtaining the Device ESN
Introduction Character string that uniquely identifies a device.
ESN
Application Scenarios such as license application, device repair, and eService service
scenarios configuration
 Obtaining the ESN using DeviceManager • Obtaining the ESN using the CLI
>> Run the show system general command.
admin:/>show system general
System Name : XXX.Storage
Health Status : Normal
Running Status : Normal
Total Capacity : 3.186TB
SN : 210235G6EHZ0CX0000XX
Location :
Product Model : XXXX
Product Version : VX00R00XCXX
High Water Level(%) : 80
Low Water Level(%) : 20
WWN : XXXX
Time : 2020-07-07/15:34:05 UTC+08:00
Patch Version : SPCXXX SPHXXX
Description :
Managing Alarms and Events
• Email notification
• Email notification
• SMS notification
• SMS notification
• Syslog notification
• Trap notification
• Trap notification
Configuring the Configuring the
event notification alarm notification
method mode
Managing
alarms and
events
Configuring alarm
masking Configuring alarm
dump
• Alarm masking needs to be enabled or
disabled so that the system does not • When the number of alarms exceeds
report or reports alarms to the network the threshold, the alarms will be
management system. dumped automatically to a specific
FTP or SFTP server.
Collecting Storage System Information
• Prevent storage system faults and other unpredictable

Purpose disasters from damaging the storage system.
• Know the storage system operating status.
Collecting • Regularly export and securely save the system data for fault
information
How locating and analysis.
• Configuration information, system logs, disk logs, and

System data diagnosis files
Collecting Storage System Information (2)
Collecting storage system configuration data using DeviceManager

On DeviceManager:
• You can export the configuration information to collect the information about the current running status of
the system.
• You can download Recent logs or All logs to collect configuration information, event information, and
debugging logs on the storage device.
• You can download DHA Runtime Log List or HSSD Log List to collect disk run logs, I/O statistics and
service life, and S.M.A.R.T. logs.
• You can export the diagnosis file to collect fault information.
Collecting storage system configuration data using the CLI
Log in to the CLI of the storage system as the super administrator and run the following command to export
the configuration file to an FTP or SFTP server:
export configuration_data ip=? user=? password=? db_file=? [ port=? ] [ protocol=? ] [ clean_device_file=? ]
Configuring Basic Storage Services
• The storage space provided by the storage system is divided

Configuring into multiple LUNs.
basic Function • Map LUNs to an application server.
services
• The application server can use the storage space provided by
the storage system.
Using DeviceManager to configure basic storage services

 Creating a storage pool: DeviceManager allows you to create a storage pool in either recommended or
custom mode.
 Allocate storage resources by creating LUN groups or file systems.
Configuring Basic Storage Services Using the CLI
3. Using the storage space on an

application server
 Use the storage space on

2. Setting up connection an application server.
• Create a host.
• Create a host group.
• Configure initiators.
1. Creating storage space
• Create a mapping view.
• Configure connectivity
 Create a disk between a host and a
domain. storage system.
 Create a storage
pool.
 Create a LUN.
 Create a LUN group.
Quiz
1. The management IP address of a storage device is 192.168.5.12. Engineer A needs to enter

( ) in the address box of the browser to log in to the storage device.
A. 192.168.5.12
B. http://192.168.5.12
C. https://192.168.5.12
D. https://192.168.5.12:8088
2. DeviceManager can monitor the performance of controllers, front-end ports, and back-end ports. ( )
Summary
Storage
Management
Overview
Storage
Management DeviceManager
Overview
Storage
Management Login
Mode
Introduction to
Storage System Operation Management Storage CLI
Management Tools
Basic Management
Operations of the
Storage System
More Information
Enterprise Huawei
Recommendations

 Popular tools
 HedEx Lite
intelligent world.


Storage System O&M Management
Foreword
 As the cost of storage devices decreases, large-capacity storage devices

have been used by more and more enterprises to store data generated by
enterprise service application systems and IT systems, such as emails,
documents, service data, and data backup. Therefore, effective
management of storage devices is critical to the continuity and stability of
enterprise services.
Objectives

 General O&M management process
 Common storage system O&M management tools
 Process and methods of typical storage system O&M scenarios
Contents
1. O&M Overview
2. O&M Tools
3. O&M Scenarios
O&M
 O&M is essentially the operation and maintenance of networks, servers, and services in each
phase of their lifecycles to achieve a consistent and acceptable status in terms of cost, stability,
and efficiency. • • Organizational structure
Asset management
• Event management • Skill
• Energy efficiency management • Personnel allocation
• ... • ...
Maintenance Personnel
management organization
Management Resource • Maintenance tool

• Device maintenance • Knowledge base
Technical Platform
• Device repair • Maintenance platform
assurance configuration
• Risk identification • ...
• ...
Standard
Standard Process
system
• Standard operation procedure
• ITIL
• Emergency response process
• Uptime O&M
• Troubleshooting process
• ISO 2000
• ...
• ...
How to Perform O&M
 Technical layer: Streamline the O&M lifecycle of each product and identify the key measures of each task.
 Process layer (ITIL process management framework): change, event, and problem management.
Before the device goes online O&M/Operation period

Model O&M/
Requirement Design Implementation Online Offline
selection Operation Process management
Requirement Configuration selection Offline
analysis and architecture design specifications Event management
Service rollout and maintenance
transfer specifications Problem management
Operation
Rollout and deployment Monitoring and security compliance Change management
specifications
Capacity management and expansion
Configuration management
Performance and experience optimization
Emergency and DR drill
Release management
Cost and efficiency optimization
......
PRR management (performance, reliability, and recoverability)
Event Management
Objective
A  To restore services as soon as possible
 To minimize the impact of emergencies on service running
 To ensure that the service quality and availability meet the SLA requirements
Definition
B  Emergency
 Any event that causes or may cause service interruption or service quality deterioration
 Hardware faults, software faults, and service request interruption
Task
C  Detection and recording
 Classification and online support
 Priority (based on the impact and urgency)
 Investigation and diagnosis
 Solution and recovery
 End
 Responsibilities, monitoring, tracking, and communication
Event Management Process
Transfer and supervision
Service request
Accident data
Incident Problem
Service desk management Temporary measures management
process:
• Identification Change requirement
Computer Change
operations Input: and record management
• Classification Solution
accident
and initial Report
Network support Service level
Output: • Investigation SLA parameters management
solution& and analysis
Procedure temporary • Solution and Report Capability
measures recovery management
Other sources • Incident
of accidents termination
Report Availability
management
Configuration
information
Configuration management
database (CMDB)
Problem Management
Objective
A  Locate the root cause of the problem and take measures to eliminate known errors.
 Minimize the number of incidents caused by IT infrastructure errors and minimize the negative impact of problems.
Prevent the recurrence of emergencies related to errors.
Definition
B  Problem: obtained from multiple emergencies with the same symptom or a major incident and indicates
that an error with unknown causes exists.
 Known errors: The root cause of a problem has been successfully located and a solution has been found.
Task
C  Problem control
 Known error control
 Proactive problem management
 Trend analysis
 Review of major issues
Problem Management Process
Incident Configuration Service level Capability Availability

management management management management management
Information
Matching information,
emergency measures, and
quick recovery solution Record
Problem Problem
management Information database
Change request Post implementation
(RFC) review (PIR)
Change
management
Change Management
Objective
A  Ensure that all changes are effectively controlled and handled through standardized means and
processes, and that approved changes are implemented with minimum risks, high efficiency, and high
cost-effectiveness.
Definition
B  Change: An action that causes the status of one or more IT infrastructure CIs to change.
 Standard change (approved in advance)
 Request for Change (RFC)
 Change Schedule (FSC)
 Change Advisory Board (CAB)
Task
C  Receive, record, approve, plan, test, implement, and review change requests.
 Provide the IT infrastructure change report.
 Modify CMDB.
Change Management Process
 The input information includes:
 Change request
 Data information provided by the configuration management database, especially information about the impact of changes
 Change implementation schedule
 Capability database provided by capability management and budget information provided by the financial management process
Change
management
 The output information includes:

 Updated change implementation schedule
Problem Configuration Release
 Signals that trigger the start of configuration management management management management
and release management
 Agenda, minutes, and action items of CAB
 Change management report

Incident
management
Configuration Management
Objective
A  Measure the value of all IT assets and configuration items used in organizations and services.
 Provide accurate information about IT infrastructure configuration for other service management processes.
 Support the operation of incident management, problem management, change management, and release management
 Verify the correctness of the configuration records related to the IT infrastructure and correct the detected errors.
Definition
B  Identify and define configuration items.
 Plan, define, and manage the configuration management database.
 Periodically verify the accuracy and integrity of CMDB.
 Detailed report of IT assets
Task
C  Receive, record, approve, plan, test, implement, and review change requests.
 Provide the IT infrastructure change report.
 Modify CMDB.
Configuration Management Process
Change management Release management Configuration
management
Report and audit
Change request
configuration information
Configuration management database

Categorization &
Report
Plan
Definitive software library

Release Update information.
(CMDB)
(DSL)
Release and distribute
the hardware and
Implementation Update CMDB & DSL.
software of the new
version.
Comment
Check whether CMDB is

End
updated.
Release Management
Objective
A  Comprehensively assess changes to IT services and ensure that all aspects
(including technical and non-technical factors) of a release are considered
Definition
B  Release
 Delta release
 Full release
 Package release
 Emergency release
 Release policy
Task
C  Release planning
 Design, development, and configuration release
 Release review
 Rollout plan
 Communication, preparation, and training
 Distribution and installation
Release Management Process
Design and development Controlled test
Production environment
environment environment
Release management
Communication
and training
Release policy
configuration
building, and
Distribution
Installation
First-time
planning
planning
Building and Release test
running
Release
Release
design,
configuration and
release acceptance
Configuration management database (CMDB)

Definitive Software Library (DSL)
Contents
1. O&M Overview
2. O&M Tools
3. O&M Scenarios
Components of Huawei Enterprise Storage O&M System
Customer Data Center Huawei Technical
DME Support Center
Storage resource control
O&M administrator
Trouble submission
Server Resource pooling & Service Orchestration
Remoting solution
eSight eService
Multi-device management Cloud Platform
Fabric O&M administrator
Fault monitoring & Performance report
Remote Control
eService
Storage Device Device Device
Remote maintenance
Manager Manager Manager
O&M administrator
Fault monitoring & Fault feedback Authentication system
18000 V3 9000
Device archive system
SmartKit
DeviceManager Storage service tool
Single Device Management Service personnel
Trouble order handling system
O&M administrator Delivery & Upgrade & Toubleshooting
Configure & Alarming Fault diagnosis expert system
Main Functions of DeviceManager
 DeviceManager is storage management software designed by Huawei for a single storage system.
It can help you easily configure, manage, and maintain storage devices.
 Main software functions include storage resource allocation, user management, data protection
feature management, device performance monitoring, and alarm management.
Home Page of DeviceManager
Introduction to SmartKit
1. Unified platform
The desktop tool management
platform integrates O&M tools
for storage systems, servers, and
cloud computing.
2. Scenario-based guidance
Tools specific to each O&M
scenario can be downloaded
on demand.
3. Standardized operations
The wizard guides you
through operations based
on scenarios in an easy and
intelligent manner.
Home Page of SmartKit
 Standardized and process-based operations in various service scenarios, improving operation
efficiency
Function
navigation bar Domain Function
management
Device
Scenario-
based entry
Introduction to DME
ITSM
Automation platform Monitoring platform Report platform
Northbound API
Planning Construction O&M Optimization
Service level-based pooling Flexible automation Automatic identification Multi-dimensional analysis

and consolidation modes and proactive prevention and optimization suggestions
Intelligent planning and Orchestratable Automatic analysis and One-click change and
automatic pooling scheduled tasks quick locating automatic driving
Gold Silver
Gold Silver Bronze
Southbound API

FC switch Third-party storage
all-flash storage distributed storage
DME Functions and Features
Planning Construction O&M Optimization
SLA-based pooling Automatic provisioning Proactive problem Automatic problem

identification resolution
and consolidation - SLA change
- Full-process automation - Configuration compliance/
- Workload evaluation Data protection - Data flow
- Auxiliary automation (reclamation/migration)
- Capacity threshold/
- QoS policy Performance threshold
- Best practice
- Orchestratable scheduled
implementation
- Threshold policy tasks - Capacity prediction/
Performance prediction Multi-dimensional analysis
- Scheduling policy - Application template - SLA/Cost/Capacity/
- Disk service life prediction
Performance
- Quota policy - Disk health/Abnormal load - Application/Device/
Automatic protection
Automatic problem analysis Project/Label
- Protection policy - Copy creation - Customized report/
- Automatic masking/
aggregation/association Large screen
- Copy visualization
Autonomous driving
- Copy enabling Fast fault locating - Policy-based autonomy
- E2E performance analysis - AI-based inference
- E2E topology autonomy
Infrastructure User role Multi-DC

Open API
management management management
Introduction to eSight
 eSight provides multi-vendor device adaptation for unified network-wide device management,
component-based architecture for on-demand construction of enterprise O&M platforms, and
lightweight design and web client for lower system maintenance and upgrade costs.
Switches/Routers/
WLAN PON Management ……
Management
Architecture UC/Telepresence,
Transport Device
Platform + Components Video Surveillance eLTE Management
Management
Management
eSight
Servers/Virtual Equipment
Storage
Resources Room Facility
Management
eSight Basic Management Platform
Logical Architecture of eSight
Administrator
WLAN Management Storage Capacity Management Server Stateless Computing
Value-added Network SLA&QoS management Storage Network Analysis Server Configuration and Deployment
O&M Network Traffic Analysis Management Business Service Management Report Management
…… …… ……
Communication Devices Network Devices eLTE Devices
Telepresence & Videoconferencing Virtual Resource PON Devices

Device
Management Terminal Servers Transport Devices
Intelligent Video Surveillance Storage Devices Equipment Room Facilities
…… …… ……
Management
Platform eSight Management Platform
Managed object: server/storage/VM/switch/router firewall/……
Introduction to eService
 Based on Cloud-Native, Huawei eService cloud intelligent management platform uses big data analysis and AI technologies to provide services
such as automatic fault reporting, capacity and performance prediction, and disk risk prediction, preventing potential risks and providing a basis for
capacity planning.
Efficient Complex management

Reactive response Service rollout delay
O&M for multiple devices
Technical Real-time Intelligent Asset

Rapid
support analysis prediction platform
response
capabilities
Cloud platform capability building

Proactive problem handling Intelligent prediction and analysis Asset management
 24/7 remote monitoring for all
 Intelligently identifies risky disks,  Collects device asset
IT devices, and automatic fault ensuring data security. information for future
eService reporting and SR creation
 Predicts the capacity trend in the reference.
 Proactive problem handling next 12 months to facilitate  Provides product EOX
reduces the troubleshooting procurement planning. information and device
duration and improves the
 Predicts performance bottlenecks maintenance information.
operation efficiency. according to performance
fluctuation rules.
System Architecture of eService
Customer network Huawei network
FusionCloud DMZ
Intranet
Email (optional channel)
zone
ManageOne OC/SC Supports only fault
monitoring.
DC1
DC2 Customer Huawei
Email Email
Cloud OS
Internet
server server
Fusion Manager/Fusion
Compute/Fusion eService
eSight
Access/FusionSphere OpenStack OM Storage cloud
/Server system
Network HTTPS
Hardware /Network
layer
Storage Fault monitoring
eService
Remote inspection Proxy HTTPS
Server Client
Remote log collection server service
& FusoinCare
Capacity prediction (Optional)
Maintenance Performance
host exception analysis
Disk prediction
Contents
1. O&M Overview
2. O&M Tools
3. O&M Scenarios
Routine Maintenance Items
03
02 Weekly
maintenance items
01
Daily maintenance
item  Inspecting a storage device
Initial maintenance  Checking the equipment room
items environment
 Checking and handling alarms  Checking the rack internal
environment
 Checking the SmartKit
installation
 Checking the installation and
configuration of eService
 Checking the alarm policy
configuration
Quick Maintenance Process
Start
Check the indicator status The indicators on the front and rear panels of the storage devices indicate the device
and handle related exceptions. running status and help you discover and rectify common hardware faults.
By checking the system information and service status, you can learn about the basic
Check the service status.
information, alarms, capacity trend, and performance of the storage system, as well as
and handle related exceptions.
the status of storage resource allocation and value-added features.
Check the system performance

You can query the real-time and historical performance statistics on DeviceManager.
and handle related exceptions.
If a fault occurs in the storage system, DeviceManager automatically determines the

Check and clear alarms.
severity of the fault and reports an alarm. Maintenance personnel should rectify the
fault in a timely manner to prevent service interruption or data loss.
Can the preceding Yes

exceptions be handled?
No
Collect information and report faults.
End
O&M Scenario 1: Inspection
Background
 After the storage devices purchased by company E are
deployed, services are deployed and running properly. To
ensure the storage security of core devices in the service
system, engineer A in the IT department is responsible for
the inspection of storage devices. Help engineer A make
an inspection plan.
Inspection Method
Check the
storage system
operating
environment.
Inspection
Manual
inspection
Check the using tools
Check service SmartKit inspection
indicators. running DeviceManager
status. inspection
Check the device

running status.
O&M Scenario 2: Performance Monitoring
Background
 Company E's business has gone online. To learn about the
performance and usage of the storage device, engineer B in
the IT department is responsible for monitoring the
performance of the storage device. Help engineer B
monitor the performance of the storage device.
Performance Monitoring Process
Start
Different service scenarios have special requirements on

performance monitoring parameters. You can set performance Set performance monitoring
monitoring parameters based on service requirements. Ensure parameters.
that the performance monitoring function is enabled.
Configure the threshold. When the threshold is exceeded,

Configure the threshold.
check the alarm information.
Create a service-related indicator template so that you can

view the indicators in a timely manner. Create a metric chart.
After the dump function is enabled, newly generated Configure performance

performance monitoring files are automatically dumped to the monitoring file dump.
specified application server through the SFTP or FTP protocol.
View performance monitoring data.
View storage device performance information, including real- View storage system Check storage system alarm information.
time performance monitoring data, alarms, events, and power performance information.
consumption. Check storage system event information.
End Check storage system power consumption.
Performance Monitoring Metrics
IOPS
• For applications with an I/O size smaller than 64
KB, mainly focus on the IOPS.
• For applications with an I/O size greater than or
equal to 64 KB, mainly focus on the bandwidth.
Monitoring
metrics
Bandwidth Latency
Performance Metrics
1 Snapshot 1 Logical port 1 Heterogeneous iSCSI link
2 Front-end Ethernet port 2 Host 2 Heterogeneous FC link
Remote replication consistency

3 LUN priority 3 Controller 3
group
4 Back-end SAS port 4 LUN 4 FC replication link
5 Front-end FC port 5 Storage pool 5 Remote replication
6 Front-end bound port 6 SmartQoS policy 6 System
7 Disk 7 LUN group 7 Host group
O&M Scenario 3: Parts Replacement
Background
 After the storage system of enterprise E has been running
for a period, it reports a disk failure and disk replacement
is needed. After receiving the disk replacement request,
Huawei technical support engineer C is going to the
customer site to perform the replacement.
Parts Replacement Procedure
Start
Remove cables from Check the system after

Log in to SmartKit.
the component. the replacement.
Select the component to be replaced Remove the Successful

No Rectify the fault as
and start the replacement. component. check prompted.
Yes
Use the tool to perform the pre- Insert a new Use the tool to perform
replacement check. component. the inspection.
Rectify the No No
Successful
fault as Connect cables.
check Successful Rectify the fault as
prompted.
Yes check prompted.
Confirm that the Yes
Use the tool to power off the replacement is
component. complete on the
tool.
End
Replaceable Parts
FRU CRU
Controller Power module
Interface module BBU module
System subrack Fan module
Management module Disk module
Cable Expansion module
Assistant cooling unit Optical module
Quorum server -
Data switch -
Spare Parts Query Assistant
Key Points for Disk Replacement
 When handling a disk module, hold only its edge to prevent damage.
 Remove and insert a disk module with even force. Excessive force may damage the appearance of
the disk module or cause faults.
 To avoid damaging disk modules, wait at least 1 minute between removal and insertion.
 To prevent data loss, replace only a disk module of which the Alarm/Location indicator is steady
yellow.
 Complete the replacement within five minutes after removing a disk module. Otherwise, the
system heat dissipation is compromised.
 Use SmartKit to replace a risky disk (not faulty).
 Ensure that the replacement disk is inserted in to the same slot as the replaced disk. Otherwise,
the system may work abnormally.
Disk Replacement Using SmartKit
 Start SmartKit and select the parts replacement tool.
Disk Replacement Wizard
Quiz
1. (Multiple choices) Which of the following are common management software? ( )

A. A. DeviceManager
B. B. eSight
C. C. SmartKit
D. D. eService
2. (True or False) SmartKit integrates various tools required for deploying, maintaining, and
upgrading IT devices, helping service and maintenance engineers perform precise
operations on these devices, improving work efficiency. ( )
Summary
O&M concepts
O&M overview
O&M handling process
DeviceManager
Storage system O&M management

SmartKit
Common O&M tools eSight
Common O&M scenarios DME
eService
More Information
Enterprise Huawei
Recommendations

 Popular tools
 HedEx Lite
intelligent world.



HCIA-Storage V4.5 Training Material

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

HCIA-Storage V4.5 Training Material

Uploaded by

Copyright:

Available Formats

HCIA-Storage V4.

2-1 Intelligent Storage Components

2-2 RAID Technologies

2-3 Common Storage Protocols

2-5 Storage Network Architecture

4-1 Backup Solution Introduction

5-1 Storage System Operation Management

 Data carries information during the transmission on networks. What is the

On completion of this course, you will be able to understand:

1. Data and Information

3. Development of Storage Technologies

4. Development Trend of Storage Products

Input Processing Output

Item Data Information

Data Data Data Data Data Data

1. Data and Information

3. Development of Storage Technologies

4. Development Trend of Storage Products

 Disaster recovery (DR) solutions

 Storage management software

Network switching devices NAS gateway

Tape and single

Data Data Data

1. Data and Information

3. Development of Storage Technologies

4. Development Trend of Storage Products

Disks in a server Early external storage Storage arrays

CPU CPU CPU

RAM RAM RAM

Disks Disks Disks

SAN NAS Clients Unified

 Generally, distributed storage scatters

Back-end storage network

storage devices into logical resources,

Protocol and interface

Open Storage device and storage node

Universal hardware platforms

1. Data and Information

3. Development of Storage Technologies

4. Development Trend of Storage Products

1950s–1960s 1960s–1970s 1970s–1980s 1980s-1990s 1990s-

Single-level Quad-level cell

Multi-level cell 3D TLC:

1. Data and Information

3. Development of Storage Technologies

4. Development Trend of Storage Products

Parallel interface Serial interface

100G NVMe-oF 400G

NVMe 1.0 NVMe 1.2 NVMe 1.3 NVMe 1.4

1. Data and Information

3. Development of Storage Technologies

4. Development Trend of Storage Products

Steam Age Electricity Age Information Age Intelligence Age

Industry Cloud Service extension

Service Big data Customization

Gov & Public Large

EB-level TCO reduction

Biomolecule Optical storage

Blu-ray storage Gold nanostructured glass

50 years >>> 600 years

Start out Grow Lead

All IP: extremely low cost of SSD media

Edge Production Analysis Backup Archive

D. Massive amounts of data