HCNA-Storage V3 BSSN Building The Structure of Storage Network Training Material

The privilege of HCNA/HCNP/HCIE:
With any Huawei Career Certification, you have the privilege on http://learning.huawei.com/en to enjoy:
n
1e-Learning Courses Logon http://learning.huawei.com/en and enter Huawei Training/e-Learning
/e

o m
If you have the HCNA/HCNP certificateYou can access Huawei Career Certification and Basic Technology e-Learning
courses.
e i .c
If you have the HCIE certificate: You can access all the e-Learning courses which marked for HCIE Certification Users.
aw

Methods to get the HCIE e-Learning privilege : Please associate HCIE certificate information with your Huawei account, and
hu

email the account to Learning@huawei.com to apply for HCIE e-Learning privilege.

g .
2 Training Material Download
i n

arn
Content: Huawei product training material and Huawei career certification training material.

//le
MethodLogon http://learning.huawei.com/en and enter Huawei Training/Classroom Training ,then you can download
training material in the specific training introduction page.
p :
3 Priority to participate in Huawei Online Open Class (LVC)
t t

s :h
The Huawei career certification training and product training covering all ICT technical domains like R&S, UC&C, Security,
4Learning Tools: rc e
Storage and so on, which are conducted by Huawei professional instructors.
s o
eNSP Simulate single Router&Switch device and large network.

R e
WLAN Planner Network planning tools for WLAN AP products.
n g
In addition, Huawei has built up Huawei Technical Forum which allows candidates to discuss technical issues with Huawei experts ,
ni
share exam experiences with others or be acquainted with Huawei Products.
a r
Statement:
L e
r e
This material is for personal use only, and can not be used by any individual or organization for any commercial purposes.
o
M
HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 1
HCNA-Storage
Huawei Certified
HCNA-Storage BSSN
Building the Structure of Storage Network
e n
/
o m
e i.c
aw
u
g.h
i n
arn
//le
p :
t t
: h
e s
r c
sou
Re
i n g
n
e ar
e L
or
Huawei Technologies Co.,Ltd
HUAWEI TECHNOLOGIES
HCNA-Storage
Copyright Huawei Technologies Co., Ltd. 2015. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means
without prior written consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd. All other
e n
trademarks and trade names mentioned in this document are the property of their respective
/
holders.
o m
Notice
e i.c
w
The information in this document is subject to change without notice. Every effort has
a
u
been made in the preparation of this document to ensure accuracy of the contents, but all
.h
statements, information, and recommendations in this document do not constitute the
g
n
warranty of any kind, express or implied.
i
arn
//le
p :
t
Huawei Certified
h t
HCNA-BSSN Building the Structure of Storage Network Training Courseware
s :
r ce Version 3.0.1
s ou
Re
i n g
n
e ar
e L
or
M
HUAWEI TECHNOLOGIES
HCNA-Storage
Huawei Certification System
Relaying on its strong technical and professional training system, according to different
customers at different levels of ICT technology, Huawei certification is committed to provide
customs with authentic, professional certification. Based on characteristics of ICT
e n
technologies and customers needs at different levels, Huawei certification provides customers
/
with certification system of four levels.
o m
HCNA-Storage BSSN (Huawei Certified Network Associate Storage Building the Structure of
e i.c
w
Storage Network) training aims to provide guidance to participants in learning contents related
a
u
to the HCNA-Storage exam.The training covers the knowledge, technologies and application
g .h
of SAN,NAS, and structure ,network, connection, deploying ,troubleshooting in Huawei SAN
Storage system.
i n
arn
HCNP-Storage certification is positioned in ability construction for IT information storage
//le
:
professional engineer or storage scheme expert. The curriculum includes, but is not limited to
t p
the following: SAN, NAS, Backup and DS technology, Unified storage system principle and
t
h
application, Huawei storage solution planning, deployment, troubleshooting and maintenance.
:
e s
c
HCIE-Storage (Huawei Certified Internetwork Expert-Storage) is designed to endue engineers
r
ou
with a variety of Storage network and system technology and proficiency in maintenance,
s
diagnostics and troubleshooting of Huawei solution, which equips the engineers with
e
R
competence in planning, design and optimization of large-scale ICT Solution.
i n g
n
e ar
e L
or
M
HUAWEI TECHNOLOGIES
HCNA-Storage
e n
/
o m
e i.c
aw
u
g.h
i n
arn
//le
p :
t t
: h
e s
r c
sou
Re
i n g
n
e ar
e L
or
M
HUAWEI TECHNOLOGIES
HCNA-Storage
Foreword
Outline
HCNA-Storage covers the storage technologies (RAID, SCSI, iSCSI, FC) and its application,
focusing on the IP-SAN, FC-SAN architecture, networking, connectivity, deployment and
maintenance.
e n
Content
/
The course contains a total of 11 chpaters
o m
e i.c
Chapter1 Describes what is information, the life cycle of data , concept of business Continuity,
and an introduction of components in an ICT infrastructure.
aw
u
.h
Chapter2 Describes what is DAS, SCSI technology, Hard Disk Technology, Solid State
Technology.
i n g
rn
Chapter3 Describes What is NAS, Ethernet Basics, Ethernet Hardware Components.
le a
Chapter4 Describes the ideal ICT infrastructure, Storage protocols Fibre Channel, IP SAN
Storage protocols iSCSI.
: //
Chapter5 Describes traditional RAID Technology.
t t p
: h
s
Chapter6 Describes basic concepts of Big Data, Object-based storage technologies, and
r ce
OceanStor 9000 key technologies of Big Data
ou
Chapter7 Describes backup concepts and topologies, backup technologies, disaster Recovery
introduction.
es
R
Chapter8 Describes concepts and background of Cloud Computing, Modules of Cloud
n g
Computing, and Huawei FusionCloud Products..
i
n
ar
Chapter9 Describes Huawei Storage Products, Huawei RAID 2.0+,Huawei platform
L e
improvements, Huawei NAS products, Huawei Backup products, and Huawei Licensing policy.
e
or
Chapter10 Describes how to initialize a Huawei OceanStor system, how to configure a Huawei
OceanStor system, File systems and Storage, and maintenance jobs.
M Chapter 11 Describes Data Cofferr, Pre-emptive replacements, Firmware and updates, principle
of HyperSnap, SmartThin, HyperClone, SmartTier, and HyperReplication.
In conclusion, you should be able to plan and deploy SAN networks and storage systems, to
install, deploy, and maintain Huawei SAN storage products, and to become a qualified SAN
storage engineer or system administrator
Readers Knowledge Background
Know server fundamental and application.

HUAWEI TECHNOLOGIES
HCNA-Storage
Know SAN, NAS, DR concepts and technology.
Understand mainstream OS and DB operation and management .
e n
/
o m
e i.c
aw
u
g.h
i n
arn
//le
p :
t t
: h
e s
r c
s ou
Re
i n g
n
e ar
e L
or
M
HUAWEI TECHNOLOGIES
HCNA-Storage
Icons Used in This Book
e n
/
m
FC Switch GE Switch Storage Array Host
o
i.c
//
w e
u a
g .h
i n
arn
//le
p :
t t
: h
e s
r c
sou
Re
i n g
n
e ar
e L
or
M
HUAWEI TECHNOLOGIES
HCNA-Storage
Account for Experiment environment
Experiment network introduce
The experiment environment aims to provide guidance to participants in learning contents

related to the HCNA-Storage exam( H13-612-ENG).
Experiment contents include storage array hardware installation, network deploying of FC SAN
e n
and IP SAN, storage management, configuration RAID/LUN/ mapping ,connection between /
storage and hosts,storage maintenance etc.
o m
e i.c
One suit of experiment equipment includes : 1 PCS GE switch,1 PCS FC switch,1 PCS Windows
w
hostwith OS and NIC or FC HBA card ,1PCS Linux hostwith OS and NIC or FC HBA
a
u
card,12 PCS S5300 V3 or S5500 V3 storage array, several network cables ,24 PCS PC
for students.
g .h
i n
One suit of experiment equipment fits 2-4 students operating at the same time.
Equipment introduce
arn
/ l e version
:/ S5300 V300R002
Device type Device name Software
tp
Storage array S5300 V3 or S5500 V3
h t S5300 V300R002
Switch SNS2124 OR S3900
s : General version
Server
SuSE 11 SP2
r ce
Windows 2008 SP2 Be compatible with storage
cable
ou
Network cable 8PCS
s
Null
Console PC PC e
FC 6 PCS
R Win7
i n g
n
e ar
e L
or
M
HUAWEI TECHNOLOGIES
e n
/
o m
HCNA e i .c
aw
u
.h
Introduction to storage
i n g
r n
// lea
p : www.huawei.com
t t
s:h
r c e
sou
Re
i n g
r n
e a
e L
or
M
e n
/
o m
e i .c
aw
u
g .h
ni n
r
// lea
p :
t t
s:h
r c e
sou
Re
i n g
r n
e a
e L
or
M
Table of Contents
Module 1: Data Management

Data Management 11
Information Life Cycle Management 17
The Value of Data 24
Components of an ICT Infrastructure 27
e n
Questions 30
/
Exam Preparation
o
31
m
Module 2: What is DAS?
e i .c
Building an ICT infrastructure
aw 37
u
.h
Direct Attached Storage 38
SCSI Protocol and Storage System
ATA and SATA
i n g 40
57
r n
lea
Disk Technology 63
//
SSD Introduction 80
Questions
p : 84
Exam Preparation
t t 85
s:h
Module 3: What is NAS?
Network Attached Storage
r c e 93
NAS Network Topology
s ou 95
What is CIFS?
What is NFS? Re 99
100
i n
Ethernet Standard g 104
r
Questions
n 115
e a
Exam Preparation 116
e L
or Module 4: What is SAN?
M
The Ideal ICT Infrastructure 123
Storage Area Networks 125
Differences between DAS and SAN 128
Network Topology: Fibre Channel 137
IP SAN 157
iSCSI connection modes 160
Convergence of Fibre Channel and TCP/IP 166
Questions 168
HCNA V3 | Table of Contents Page | 3

Module 5: RAID Technology and Application
Traditional RAID 177
Basic concepts and implementation modes of RAID 177
Data Organization modes of RAID 178
RAID technology and application 181
Working principle of RAID 0 182
e n
/
m
Overview of RAID 6 198
Working principle of RAID 6 P+Q
.c
199
o
Working principle of RAID 6 DP
e i 200
Hybrid RAID - RAID 10
aw 202
u
Hybrid RAID - RAID 50 203
Comparison of common RAID levels
g .h 204
n
Application scenarios of RAID 205
ni
r
RAID Data Protection 206
lea
Questions 211
://
t tp
:h
Module 6: Big Data
es
What is Big Data? 219
c
Advantaged of Object Based Storage 227
r
ou
Hadoop: Internet Big Data solution 230
Huawei OceanStor 9000
es 232
Erasure Code
R 234
ing
OceanStor 9000 hardware structure 235
rn
Recommend networking: Front and Back End 10Gb 238
a
Questions 239
L e
r e
o
Module 7: Back up and Recovery
MWhat is a backup?
LAN-free backup topology
247
250
Components of a backup system 251
Deduplication 257
Contents of a backup strategy 261
Huawei Backup Products: VTL6900 family 268
Introduction to HDP3500E 271
Backup Software Architecture 273
Page | 4 HCNA V3 | Table of Contents

Introduction to Disaster Recovery 274
Questions 280
Module 8: Cloud Computing

Concept of Cloud Computing 289
Cloud computing models 297
Categories of cloud computing 299
Value of cloud computing 306
e n
/
m
Huawei FusionCloud solutions 307
Questions
.c o
312
Exam preparation
e i 313
aw
Module 9: Huawei Product Information and Licensing
u
RAID 2.0+ Evolution
g .h 319
RAID 2.0+ Logical objects
ni n 324
r
Huawei Storage Products 329
OceanStor 5300 V3
le a 334
://
OceanStor 5500 V3 Specifications 338
tp
OceanStor 5600 V3 339
t
:h
OceanStor 5800 V3 Specifications 341
es
OceanStor 6800 V3 342
OceanStor 18000
r c 346
ou
OceanStor 18500 Specifications 347
es
OceanStor 18800 Specifications 348
R
OceanStor 18800F Specifications 349
ing
I/O Modules for the OceanStor V3 series 350
rn
OceanStor Dorado 2100 G2 353
e a
OceanStor Dorado 5100 355
e L
OceanStor VIS6600T 356
r
OceanStor 9000 Big Data Storage System 358
o Cabling Diagrams 360
M Huawei Licensed Software Features

Questions
365
368
HCNA V3 | Table of Contents Page | 5

Module 10: Huawei Storage: Initial Setup and Configuration
Initial Setup 377
Launching the DeviceManager User Interface 381
Create Storage Pool 387
Create LUN 391
Create LUN Group 397
Create Host 400
Create Host Group 405
Create Port Group 408
e n
/
m
Create Mapping View 410
OS Specific Steps
.c
413
o
Disk Management
e i 416
Questions
aw 423
u
g .h
Module 11: Huawei Storage: Firmware and Features
ni n
r
HyperSnap 431
lea
Create Snapshot 433
://
SmartThin 448
tp
SmartTier 450
t
:h
HyperClone 463
es
HyperReplication: Synchronous mode 468
c
HyperReplication: Asynchronous mode 469
r
ou
Firmware Updates 471
Questions
es 481
Exam Preparation
R 482
i n g
r n
e a
e L
or
M
Page | 6 HCNA V3 | Table of Contents

e n
/
o m
OHC1109101
e i .c
Data Management Introduction aw
u
g .h
ni n
r
lea
://
www.huawei.com
t tp
s:h
r c e
sou
Re
i n g
r n
e a
e L
or
M
e n
/
o m
e i .c
aw
u
g .h
ni n
r
// lea
p :
t t
s:h
r c e
sou
Re
i n g
r n
e a
e L
or
M
Introduction
In this, the first module of the course, the focus will be on data management. The scope of the
entire course is about the technology that Huawei provides to build an ICT infrastructure, but in
this module we will look at the reason why a company needs an ICT infrastructure. A companys
primary goal is to provide a service to its customers and for almost every company an ICT
infrastructure is required to be able to do that. The module will discuss the data that is generated
in the company to do its business and about the way this data is kept.
e n
/
o m
Objectives
e i .c
aw
u
After completing this module, you will be able to:
Describe the importance of data for an organization.
g .h
n
Understand the difference between structured and unstructured data.

ni
r
Explain what Information Lifecycle Management is.
lea
List a number of file formats to store digital data in.
Understand the reasons for data retention.
: //
Describe how data can be protected.
t t p
s :h
Module Contents
r c e
s ou
e
1. Data Management.
R
2. What is information?
n g
3. What is Information Lifecycle Management?
i
n
4. File formats.
r
a
5. Retention policies.
e
eL
6. Protecting the data.
or
M
HCNA-storage V3 | OHC1109101 Data Management Introduction Page | 9

e n
/
o m
e i .c
aw
u
g .h
ni n
r
// lea
p :
t t
s :h
r c e
sou
Re
i n g
r n
e a
e L
or
M
Page | 10 HCNA-storage V3 | OHC1109101 Data Management Introduction

Data Management
Data Management
SNIA definition: Data is the digital representation of anything in

any form.
A company needs/creates a large amount of data to run its

business.
e n
/
m
Each employee needs the data to be present in a specific form or
shape.
.c o
Data should be available as long as the business needs it.
e i
w
When data is no longer needed it must/can be destroyed.
u a
g .h
ni n
r
Copyright 2015 Huawei Technologies., Ltd. All rights reserved. Slide 6
// lea
:
Today a company uses a wide range of resources to run its business well. Examples of resources
p
are:
t t
-
s :h
e
telecommunication equipment: i.e. smart phones, faxes.
- computer hardware:
r c i.e. PCs, laptops, network switches, storage devices.
ou
- computer software: i.e. email programs, databases, graphical design software,
es web design, software.

- facilities:
R i.e. production plant, warehouse, showroom, offices,
i n g production tools.
-
r n
personnel: i.e. production staff, logistics staff, accounting / finance,
e a marketing, management, IT staff.
e L
or Each of these resources has to be bought and implemented. These processes have to be defined
to make sure every person in the business process has all the information he or she needs to do
M their work well. In a later module the physical solutions, that can be used to achieve the goals of a
business, will be explained in more detail. In this module the actual data has the focus. So the
question to be answered first is: What is data?

What is data?
A definition by the SNIA (Storage Networking Industrial Association) defines data as: The
digital representation of anything in any form.
Although this definition seems very vague it is true because if you look at an average company it
generates an enormous amount of data every day. All this data is there to keep the business
running and keep it making a profit.
e n
/
Imagine a company that does not use any electronic messaging system like emails, that has no
o m
website to promote their products or no web shop where customers can order the products the
company offers. Also imagine a company where everybody still creates handwritten documents
e i .c
when ordering parts and raw materials; where all employees use traditional A0 size drawings for
aw
u
.h
production purposes.
The reasons that we do not use the traditional skills and tools anymore are because of the
i n g
r n
lea
obvious advantages of having the information in a digital format.
: //
Digital information is easier to keep, modify and/or duplicate. Also: it is relatively easy to have
multiple persons work with/on the same information.
t t p
s :h
What is Information?
r c e
o u
s
Data equals Information?
e
R
i n g
Information will be extracted from the data that was gathered.
arn Information can :
L e provide a company with marketing information and customer behavior.
r e help to run the business more effectively.
o help to determine risk factors.

The biggest challenges companies face today is how to interpret the tremendous amount of data
that was collected on a daily or yearly base. This is so important because it is not data that will
benefit the company I work for. Important is the information extracted from all data. If we would
just look at the numbers (=collected data) it does not show if a company is making a profit or not.
Only when we compare numbers (this weeks and last weeks sales) we can understand that the
sales have gone up or down. The information extracted from two weeks of sales data could then
be: we had a good week!
Depending on the information it can extract from collected data, a company can gain insight about
e n
/
m
the way the organization works and the way it collects data. So looking at the data might lead to
the conclusion that more data is required!
.c o
e i
w
Information about the sales that are going down can lead to a lot of changes for a company in the
a
u
way it works, what the products should be like, what the target customers are and how expensive
the products are compared to other manufacturers.
g .h
ni n
r
So in most situations more data means a better chance to find useful information from it. And
lea
there the problem occurs: we now generate so much data that we almost cannot handle it
anymore.
: //
t t p
:h
Problems:
-
e s
First the problem is with the capacity available to store the data on a digital medium.
-
r c
Second problem is to filter out the relevant data that provides the correct information.
ou
- Third problem is how to make sure that the relevant data is available to all the employees that
es
might need the data for their job.
-
R
Fourth problem: how do I make sure we do not lose that vital data? Most data loss, around
i n g
80%, occurs because of human errors. So how do I prevent a single person deleting
r n
information that is vital for a company?
-
e a
Fifth problem is to determine how long the data must be kept.
e L
or Some of the problems we face will be discussed in this module. In other modules of this course
M
we will look at solutions for the other problems. In module 9 and 10 we will discuss Huawei
storage arrays. In module 5 and 9 we will explain RAID which is a way of protecting data against
losing it. Module 6 discusses Big Data.
In the rest of this module we will focus on the data itself, the format in which we want to keep it
and the length of time we want to keep it.

Where is the data?
Where is the data?
e n
/
1 1
4
o m
2
e i .c
aw
3
u
g .h
ni n
r
// lea
:
Most companies are situated in multiple sites, sometimes in multiple cities and even in multiple
p
t
countries. But even for a smaller company the data is generated by all employees working from
t
:h
various offices. Each one of these employees uses tools to generate the data. Some of these
s
tools are very common tools like e-mail programs and word processor software. Others will use
e
r c
highly specialized software designed for the company itself.
s ou
e
For companies that produce goods we find that they have some sort of Graphical Design
R
Software (Computer Aided Design). They often use logistics software to keep track of ordered
n g
goods (parts, materials, tools) and delivered products. Customer information must be kept as well
i
r n
as financial information. All this data must be stored and kept safe.
e a
L
A less ideal situation would be when that data was stored on laptops and PCs of individual
e
or
employees in their respective offices. There would be no easy way of protecting the data against
human errors and/or against hardware failures.
M
That is why in most organizations data is stored centrally in Main Equipment Rooms (MERs).
Another term that is often used next to MER is data center. A MER should always have enough
cooling capacity to keep the systems running at the optimal temperatures and enough power
ratings to support the power consumption of all equipment. In a well-equipped data center there
are also facilities like fire-extinguishing installations and for instance a diesel generator that can
power the entire data center when the external power to the data center fails.

However well-equipped the data center may be, there is always a need to protect the data itself.
Hardware will fail and sometimes disasters occur that ruin entire buildings. Examples of disasters
are earthquakes, floods and fires. If something dramatic as that happens it is nice to know that the
data is still intact and available.
So of the most business critical data we want to have a copy stored outside of the original MER in
another MER or stored in a (fireproof and waterproof) safe.
e n
/
o m
.c
Who creates or uses the data?
e i
Who creates or uses the data?
aw
u
g .h
i n
Logistics Human Resources
r n
lea
Marketing
//
& Sales
p :
t t
s :h
Finance
r c e Customers i.e.
ou
- e-mail
- purchase orders
es
R
ing
arn
e
Structured data refers to any data that resides in a fixed field within a record or file. Examples of
e L
structured data are databases and spreadsheets.
or
M
It is the unstructured data that is confusion for many organizations as it is not directly clear what
the data represents and what the contribution of the data to the information is. Text documents,
images and web pages are examples of unstructured data. Although the contents of a document
can be relevant to an organization it is not visible at first glance. Someone should read the text
and from that decide if the contents is useable for the organization.

Statistics have proven that the data generated and stored within an average company mainly
consists of static data. With that we mean that data is generated and stored, but the data is hardly
ever read again. About 70% of the stored data is static data which might lead to the question:
Why do we store data and not look at it again on a later stage?
The answer to this is not very scientific. Most organization cannot determine the value of data
quickly and then take the decision to keep the data. They think that maybe later the data may
prove to be useful.
e n
/
m
The 30% of the data that is used or re-read must definitely be accessible for all employees. This
is called file sharing or data sharing. It is an important task for a company to arrange this well.
.c o
e i
aw
u
Information and data
g .h
ni n
Information and data
r
// lea
p :
t
a. Every company needs information to be able to do business.
t
:h
b. Information is extracted from both structured as well as unstructured data.
s
c. Almost all data is now generated in a digital form.
c e
d. Data should be accessible for multiple employees.
r
s ou
Re
i n g
r n
e a
e L
r
o
MEach employee should have to get to the right data quickly to fulfill the tasks for the company.
With data in a digital form we can use networking and file-sharing technologies to make that work.
The process of determining who needs what information is a science itself. It is called Information
Analysis. It is not a topic for this course but it is a vital step in the process of a business to
understand how data should flow within the organization.
If the analysis is incorrect employees might be missing information for their part of the business
process. That might lead to other people also missing information and so on.

Information Life Cycle Management
a. What data is needed for every person in the organization ?

b. What is the format in which data should be presented / kept ?
c. How long should the data be kept ?
d. If the data is no longer required what needs to be done with the data?
e n
/
o m
e i .c
aw
u
g .h
ni n
r
// lea
:
What data each employee needs to do its job is of course depending on the job. There are
p
t
hundreds of categories of information: marketing data, sales information, production costs, cost of
t
:h
staff (wages), logistic costs, Research and Development.
e s
r c
In any way a company must make sure that everybody has the right information at the right time.
ou
Almost just as important as having the information /data is the format in which you give that
es
information. If someone sends an email to a colleague with vital information that other person
R
should have a computer, an email program and an account to be able to receive and read it.
i n g
r n
If someone receives a document, in a file format his application cannot import and read, then this
e a
information is inaccessible to him.
e L
or Next important question to ask is how long the information is needed. Again this varies from one
business to the next but mostly regulations of the government has companies store and keep
M information for years. Sometimes information is needed for decades for instance if you are a
bridge building company you would have to keep diagrams; structural design information for as
long as the bridge exists!
Assuming we know what the data is that each employee needs, the next step would be to look at
the format in which the data should be accessible.

1.1 Physical Parameters
What is the format in which data should be available for the

organization?
1. For physical parameters.

Online information or paper based.
e n
Read only / Eyes only / not reproduceable.
/
Version control.
o m
Environmental requirements when keeping hard copies.
e i .c
aw
u
g .h
Copyright 2015 Huawei Technologies., Ltd. All rights reserved.
ni n
Slide 12
r
// lea
The format in which data is stored needs to be thought of in the broadest sense of the word.
p :
t
Although much of the information nowadays is kept as digital information, there is still a lot of
t
:h
analog information. Examples of this analog information are pictures, paper documents that have
s
a legal basis, faxes or entire archives that were never digitized.
e
r c
ou
1.2 Digital Information Parameters
es
R
i n g
r n
e a organization?
eL
2. For digital information parameters
or
Which application is required to read/modify the data.
M

Which file format for text (PDF; ODF; DOC).
Which file format for images (JPG; TIFF; DWG; PNG......).
Use lossless or lossfree formats.
Are there standards to be met (ODF; CALS; BASEL) for physical
parameters.

Digital documents also have their restrictions. We need the correct applications to open, read
and/or modify the files. It is therefore important to choose a format for the file that allows all of the
appropriate users to access the information in the files.
We typically identify three types of files:
1. Text documents.
These documents contain mainly characters (letters and/or numbers) and sometimes small
e n
/
images. Examples are word processor documents, spreadsheet and databases.
o m
.c
2. Bitmap image documents.
e i
In a bitmap all relevant picture elements (or pixels) of the image are individually stored.
w
Photos and scanned images are examples of bitmap files. As for each image thousands of
a
u
individual pixels (dots in many colors that make up the images) have to be kept it means that
bitmap images take up a lot of storage capacity.
g .h
ni n
r
3. Vector Based image documents
lea
The image is described as mathematical objects and the formulas are stored. Most Computer
Aided Design software (i.e. AutoCAD; SolidWorks)
: //
t t p
:h
When selecting a method consider using a file format that is not vendor specific and therefore is
s
readable with any program. Several of these file formats exist and they typically are supported
e
c
over many years. Examples: TIFF format for bitmap images, IGES for vector based images and
r
ou
SGML for text files. For text documents there is also the ODF (Open Document Format) that is
becoming more popular.
es
R
Important when storing bitmap information, is the effect of compression. Although compression
i n g
is mostly used to minimize the space required to store the information digitally, one must realize
n
that many compression methods imply loss of information! Sometimes storing information in so-
ar
called lossless formats prevents this loss of information. TIFF and PNG are examples of file
L e
types that are stored in a lossless way. The popular JPG format uses a method to reduce the file
r esize that deletes image information and is therefore not lossless.
o
M Note:
CALS and BASEL are other examples of standards that are very specific for a branch in the
industry.
CALS (short for Computer Aided Logistics Support) is used by the United States army to make
sure that every part of the army can get to all relevant information. The impact of CALS is huge
for every company that wants to do business with any part of the army. Even a bakery store that
wants to deliver bread to the army cantina needs to comply with the CALS standard.

That means his purchase order; price list etc. must be created in a format dictated by the armys
CALS standard. This would also apply to a manufacturer of rotors for an army helicopter. All
drawings, test reports etc. have to be CALS approved.
BASEL is a standard for organizations in the financial sector. BASEL has strict rules for reports,
accounting information and all other financial matters.
1.3 Hardware
e n
/
o m
e i .c
w
a
organization?
u
.h
3. Hardware
Is access to the information granted/allowed?
i n g
Should the data be kept intact and therefore unable to be changed?
r n
lea
Multiple employees can access the same data simultaneous.
: //
t t p
s :h
r c e
ou
es
R
All documentation has its relevancy and with it comes the need to keep it for a certain period.
i n g
Some documents have sensitive information and should be stored safely. Some information is
n
eyes-only and for example should not be duplicated. In those situations special paper can be
ar
used that prevents the paper being copied as it makes the text on the copy unreadable. With
L e
paper there is also the problem of version control. In other words version control means that you
r e
want to keep different versions of a document when changes have been made to the original.
o
MFor paper the concept of version control means that multiple versions of the document are stored
in the archives. Paper nowadays is pretty reliable but older types of paper have the tendency to
become brittle. Also the ink used can fade away or damage the paper it is on. It is a tremendous
expensive job to restore and preserve old documents. Nowadays we digitize many of those
documents and store the originals in conditioned rooms. We now can inspect the scanned
documents and have the added options of zooming in on details, modifying the image file and
share them with other users by simply copying the document files.

If access to information should be controlled methods can be implemented where documents are
stored in vaults. Archives must then be in enclosed spaces (is mostly the case if conditioned
rooms are required) and guarded.
For digital information we can use physical blockades and software blockades. By creating
multiple separate physical networks we can regulate access to data. Only devices inside of the
physical network are able to interconnect.
The same kind of separation can also be done via software. Then we would use technical
possibilities of the ICT infrastructure to block access to specific sections of the network. This can
e n
/
m
be done with techniques like firewalls, security gateways, access control lists and in switches we
can create so-called VLANs (virtual LAN).
.c o
e i
w
In some situations there is the requirement for data to be integer. This implies that information will
a
u
be stored as it is now and there is no way to change the information later. In legal documents and
.h
medical reports this is sometimes required to prevent illegal changes being made. For paper
g
i n
documents this is done by storing the document in a container that is tamper proof. Digital
n
r
information can be stored on so-called WORM media where WORM is short for (Write Once Read
lea
Many). This technology allows data to be written once and not changed afterwards. Reading the
data can be done as often as needed.
: //
t t p
:h
To have access to information by multiple persons we can create multiple copies. Having multiple
s
persons modifying the same paper documents requires them to sequentially access and modify
e
the document.
r c
s ou
Digitally allowing multiple applications to open and modify the same document files requires
Re
technologies such as cluster technologies. In cluster technologies multiple hosts and their
i n g
applications access a single file simultaneous. Each of the users is now allowed to change the file
n
contents and store all changes correctly in the document file afterwards.
ar
L e
r e
o
M

1.4 The retention periods
What are the retention periods?

Based on the business requirements of the organization itself.
Based on the general rules for your type of business.
Based on the rules that governments in specific countries dictate.
e n
How to arrange for digital information to be stored for many years.
/
o m
e i .c
aw
u
g .h
ni n
Slide 15
r
// lea
It is not only important that you need to have the information but in most cases you must keep it
p :
t
for a certain period. All businesses keep orders, invoices, pay check information, bills etc. for
t
:h
many years in case they need to reproduce the information for their own business process.
s
Warranty information or service agreements for production tools are kept as long as the tool will
be used.
r c e
s ou
Sometimes the type of business you are in also has external rules. So is stated in many Western
Re
European countries that medical information on patients has to be stored for more than fifteen
i n g
years. This allows doctors in hospitals to look back at a patients history and can help him plan a
n
better treatment for that patient. If your company is providing any medical services than this is a
ar
requirement for your organization. On top of that government rules might force you to keep the
L e
information for even longer than needed for your organization. Business information like invoices,
r e
employee contracts etc. should typically be kept for seven or more year.
o
Fact is that much information is stored digitally and the question is now: How long will the digitally
Mstored data survive?.
If we store data on magnetic media (we may remember the video recorders and cassette players)
the tape gets demagnetized after a few years. Even data stored on CD or DVD is not stored
indefinitely. We have heard of situations where CDs became unreadable after some time. We
have to find a way to store the data more reliable or we have to make sure we update the medium
on which the data is stored regularly (make a copy of a tape every two years).

1.5 How to remove obsolete information?
How to remove obsolete information?
Who is responsible for data ?

SOX ; JSOX ; EuroSOX.
e n
/
Physically destroying information.
Shredding.
Burning.
o m
Digitally destroying information.
e i .c
Whipe the disk in Operating System.
Secure whipe.
aw
u
.h
Disk shredding.
i n g
n
r
// lea
After the retention period information is sometimes no longer useful and sometimes an
p :
t
organization is not supposed to keep the information within the organization. The question is how
t
:h
to get rid of information we dont need anymore.
e s
c
First of all there are rules about keeping data safe against disabuse. The SOX (Sarbanes-Oxley
r
ou
Act) regulations state that a company is responsible for storing and removing information it
s
generates or uses. This also includes the responsibility for an organization to make sure that
e
R
nobody can make copies of important documents (or files) and take them outside of the
organization.
i n g
r n
a
If the information is stored as paper archives shredding might be a definitive solution and also
e
e L
burning the information might be applicable.
or Digital information is not so easily discarded. Traditional methods like formatting a disk is not
M secure enough as it might leave traces of data recoverable. For those situations there is
specialized software that erases data from a medium and afterwards writes random data over the
old information (and multiple times if needed).
For many government based organizations wiping data from a disk requires them to physically
shred the disks so nobody can reuse the media ever again.

The Value of Data
Business Continuity
Definition according to the SNIA organization:

Processes and / or procedures for ensuring continued business
operations.
Applies to physical and operational procedures.
e n
/
m
Physical: Buildings: Machinery, tools, products.
o
Personell: Production staff.
.c
Management staff.
Financial staff, etc.
e i
Operational procedures: Workflows.
aw
Planning and delivery of production.
u
Human Resource Management, etc.
g .h
ni n
r
// lea
:
The term Business Continuity is almost ten years old now. It was around that time that companies
p
t t
starting thinking about situations that could impact the business processes. Like so many times
:h
before it took some serious accidents and disasters for companies to be aware of the risks the
companies have.
e s
r c
ou
Recent examples of the impact of a disaster are:
es
1. The tsunami that hit Thailand. Apart from the human lives that were lost and the houses that
R
g
were destroyed there were other consequences. One of the buildings that was hit was a
i n
manufacturing plant for specific parts for hard disks. In that plant millions of these parts were
n
r
made per year. Now all of a sudden this plant produced no more parts. So the companies that
a
e
assemble the hard disk could not produce any hard disks anymore. And for the manufacturers
L
e
of computer, laptops and storage devices it meant they could not get the hard disks anymore.
or Hard disks became scarce and the production slowed down at the plants of the
M computer/laptop manufacturers.
2. In 2011 a volcano on Iceland erupted. Unfortunately the wind was blowing towards the
European continent at that time. The dust particles that were pushed in the air were a
problem for airplanes. If the dust would come into the jet engines they might be damaged or
even be destroyed. So thousands of planes had to be kept on the ground. This situation kept
going on for days and in that time almost all air traffic in Northern Europa was cancelled. For
companies who depend on airplanes for travelling or transport this was a very bad situation.

3. In 2007 an Apache helicopter of the Dutch army crashed into a high voltage power grid
system in the Netherlands. The cables that are used to transport 150.000V signals were
disrupted leaving 50.000 households without electrical power for three days. But also
businesses were impacted. Supermarkets had to close because the lights would not work nor
the refrigerators or the cash registers. All security alarms were not working as well.
These are just a few examples of a problem that leads to other companies having problems with
their business. So business continuity has companies think about these types of problems. But
the question is: Can you prevent these accidents happening and what could you do if it actually
e n
/
m
happens?
.c o
e i
The Value of Data
aw
u
The general manager decides what the data is worth.
g .h
ni n
r
Recovery Point Objective (RPO):
lea
amount of data that may be lost without consequences for the
organization.
: //
p
Restore Time Objective (RTO):
t t
Time allowed to restore the data to the last saved situation.
Cost Of Downtime (COD):

s :h
e
Total costs involved for every hour the data is not available.
r c
s ou
Re
g
n i n
ar
Of course it is impossible to prevent disasters like earthquakes or volcanic eruptions happening,
L e
but smaller scale problems like the power outage can be addressed.
r e
o The question then is how much does the solution cost. For instance is it cost effective for
M everyone to have their own diesel generator so they still can watch TV if the main power grid fails?
The answer is probably no, but for a supermarket or a small company that might be a solution.

To determine if the solution can be implemented cost effective we have to ask ourselves the
following questions:
1. What is the value of your data?

Not all data is equally important. Assign a quality grade to all data and try to protect the most
relevant or costly data. For many companies e-mails are costly data as their business is
driven by e-mails. Purchase Orders, online transaction, websites are all vital information that
should be available 100% of the time. So we must find a way to keep that data safe.
e n
/
m
2. How old can the data be?
.c o
In case of a problem we have safe copies of the vital data. But this data is not the latest data.
It is the data at the time the safety copy was made. It is in fact old data.
e i
aw
u
For that we have to explain the concept of RPO or Recovery Point Objective. It means how old
.h
the recovered data can be before it becomes useless. In a huge online web shop like ALIBABA
g
ni n
hundreds of thousands of products are sold every day. That translates into a couple of hundred
r
items per minute. If the ICT administrator would make safe copies every four hours that would
lea
mean his RPO is four hours. In case of a problem with the current data the only thing he has is
the saved data from up to four hours ago.
: //
t t p
:h
If losing four hours of incoming purchase orders represent $100.000 it means that each problem
s
will at least cost $100.000 for the owner of ALIBABA. It is the owner that decides if that $100.000
e
c
is a big problem (maybe bankruptcy) or that it is a minor setback in the turnover of the company.
r
ou
So the RPO basically means: how much data can my company lose and still not go bankrupt.
es
R
A second thing when making safe copies is the time needed before we can use the saved data
i n g
again. If an ICT administrator makes safe copies every four hours his general manager might be
n
happy. However: if a problem occurs and it takes the ICT administrator twelve hours to restore the
ar
four hour old data that might still lead to a big problem.
L e
r e
The RTO or Restore Time Objective is also a very important factor in the business continuity
o
plan. However: setting up a plan with excellent RPO and RTO will only succeed if the cost of that
Mplan outweighs the costs of not having the data!
That is why the last and maybe most important business continuity factor is COD or Cost Of
Downtime. How much money per hour is lost if I cannot have access to my business critical data?

It is typically the general manager of an organization that can determine that. He knows the
turnover per day. He knows the cost of all employees. He can calculate, using last weeks
information, how much money could have been made in the time the ICT administrator is
restoring old data!
With the Cost of Downtime as a calculated factor a company may decide to spend money to
prevent downtime happening or in other words have the business continuity guaranteed
sufficiently.
e n
/
m
In the remaining modules of this course we will look at the various technical solutions (software
and hardware) that can be used to build an ICT infrastructure that is providing business continuity.
.c o
e i
The next images are an introduction of some general components one might see in the technical
aw
solution for the various ICT infrastructures.
u
g .h
ni n
r
Components of an ICT Infrastructure
// lea
:
t tp
Components of an ICT Infrastructure
: h
e s
r c
Used terminology in ICT infrastructures
o u
Host: Any computer system to which disks, disk subsystems, or
es file servers are attached for data storage and data access.
R
Switch: A network infrastructure component to which multiple
i n g ports attach.
rn
Storage Array: A collection of disks or tapes from one or more commonly
a
accessible storage subsystems, combined with a body of
e
control software.
eL
Network: An interconnection system that enables communication among
or
a collection of attached nodes.
M Copyright 2015 Huawei Technologies., Ltd. All rights reserved. Slide 19
The term Host (or server) is used to indicate a higher specification computer that runs software
programs that are vital to the company. A computer (desktop or laptop) is a simpler version of the
host. Hosts are built to run twenty-four hours a day and for many years.

A switch is an electronic component that is used to interconnect devices. Switches have many
ports where cables can be plugged into to connect multiple devices to the same switch.
Storage array is a term generally used for a device that provides capacity to store digital data.
Storage arrays can be the size of a server or much bigger as some storage arrays can hold
thousands of hard disks.
The cables and switches are used to interconnect hosts and storage arrays together form the
e n
/
network.
o m
Components Front View
e i .c
aw
u
g .h
n
Host Host
ni
r
lea
Switch
//
Switch
Switch
p : Network
t t
:h
Storage Array Storage Array
e s
r c
s ou
Re
i n g
r n
e a
e L
or
M

Components Rear View
Host Host
n
Switch Switch
Switch Network
/ e
o m
i .c
Storage Array Storage Array
we
u a
g
Slide 21 .h
ni n
r
// lea
p :
t t
s :h
r c e
s ou
Re
i n g
r n
e a
e L
or
M

Questions
Questions
1. Name four important steps in Information Lifecycle Management.
2. What is the main reason for data loss in most companies?
3. What methods can be used to protect data?
e n
4. What is the difference between structured and unstructured data?
/
5. Name three file formats in which we can store images.
o m
.c
Describe the difference between them.
e i
aw
u
g .h
ni n
r
// lea
Answers
p :
t t
:h
1. Determine what data is needed. Decide who can access the data. Determine how long to
e s
keep the data. Determine what must be done with the data that is not needed anymore.
2. Human errors (80%).
r c
ou
3. Make copies of the data; restrict access to the data to qualified employees; for very delicate
es
information use a storage medium with WORM specifications.
R
4. Unstructured data has no known structure to it. Structured data has a well-defined database
structure
i n g
r n
5. TIFF (bitmap image, lossless, been used for years); JPG (bitmap image; popular because of
e a
compression option, not lossless); DWG (vector based; Autocad format; lossless)
e L
or
M

Exam Preparation
Exam Preparation
1. E-mails are examples of unstructured data.

This statement is: True or False.
2. Statement 1: Files should be stored in formats that are

supported by many independent software builders.
e n
Statement 2: The retention period for data is determined by
/
government based rules.
o m
a.
b.
Statement 1 is true ; Statement 2 is true.
Statement 1 is true ; Statement 2 is false.
e i .c
w
c. Statement 1 is false ; Statement 2 is true.
d. Statement 1 is false ; Statement 2 is false.
u a
g .h
ni n
r
// lea
Answers:
p :
t t
:h
1. True. E-mails are unstructured data.
s
2. B. (Statement 2 is false). The combination of government rules and requirements for your
e
r c
own organization determines how long data should be kept.
s ou
Re
i n g
r n
e a
e L
or
M

Thank you e n
/
www.huawei.com
o m
e i .c
aw
u
g .h
ni n
r
lea
: //
t t p
s :h
r c e
s ou
Re
i n g
r n
e a
e L
or
M

e n
/
o m
OHC1109102
e i .c
DAS Technology aw
u
g .h
ni n
r
lea
://
www.huawei.com
t tp
s:h
r c e
sou
Re
i n g
r n
e a
e L
or
M
e n
/
o m
e i .c
aw
u
g .h
ni n
r
// lea
p :
t t
s:h
r c e
sou
Re
i n g
r n
e a
e L
or
M
Introduction
In the first module you have learned that a great amount of digitally generated data is used to keep
the average company running its business. All equipment (hardware and software) that is needed to
have people do their job well is referred to as the ICT infrastructure. In this module you will learn
about the first of three possible technical solutions a company can use to build its ICT infrastructure.
In a Direct Attached Storage (or DAS) solution we see a compact solution with server technology; the
interconnect devices and the storage device all connected together where the distance between the
components is short, typically less than 25 meters.
e n
/
As DAS was the way used to build ICT infrastructures some 15 to 20 years ago. This module is also a
o m
.c
perfect place to explain the SCSI technology that was used then (and often still today) to transport
e i
user data from the host (and the application it runs) to the actual disk systems that store the
information.
aw
u
g .h
Objectives
ni n
r
lea
After this module you will be able to:

: //
Describe the characteristics of a DAS solution and mention the advantages of DAS.

t t
Explain what the major disadvantages are of DAS.p
:h
Describe the SCSI technology and identify the characteristics of a bus structure; explain the
e s
way electrical signals are transported over a SCSI bus.

r c
Describe the difference between parallel and serial SCSI technology.

ou
Explain how traditional hard disk technology works.
s

e
Understand the workings of Solid State Disks.
R
i n g
Module Contents
r n

e a
L
Building an ICT Infrastructure using DAS.
r e DAS characteristics.
o SCSI technology.
M o
o
Parallel SCSI.
Serial SCSI.
Hard disk technology.
o Mechanics.
o Disk drive characteristics.
o Disk drive performance.
Solid State Technology.
HCNA-storage V3 | OHC1109102 DAS Technology Page | 35

e n
/
o m
e i .c
aw
u
g .h
ni n
r
// lea
p :
t t
s:h
r c e
sou
Re
i n g
r n
e a
e L
o r
M
Page | 36 HCNA-storage V3 | OHC1109102 DAS Technology

An ICT infrastructure is the physical solution that allows users to

access the digital information they need.
n
Components of an ICT infrastructure include:
Personal computers; laptops.

/ e

Smartphones / VOIP telephones.
o m
.c
Software like Operating Systems and business applications.
i
Devices to make secure backups of data that has to be kept.
e
Network devices to interconnect various components with each other.

w
Storage devices that actually store the information and also allow a
a
user to quickly access the data when necessary.
u
.h
Three designs are mostly used : DAS NAS SAN.
i n g
r n
lea
: //
t t p
:h
In this module we will look at the possible solutions a company can use to build its ICT infrastructure.
s
With an ICT infrastructure we mean all equipment (hardware, networks and software) that can be
c e
used to create, store and distribute all relevant information for a company.
r
s ou
In the last decades the role of digital information has grown and nowadays a company cannot do
Re
business without emails, websites and other applications. This results in the need for a company to
i n g
generate the digital information; store it safely and have the information available for every employee
n
that needs the information to do its work well.
ar
L e
Examples of components of an ICT infrastructure include personal computers, laptops, mobile phones
r ebut also network switches, backup devices, digital scanners and of course the storage systems on
o which the digital information is stored.
M Three methods are mostly used to physically build the storage network part of the ICT infrastructure.
In this module we will have a closer look at the first (and oldest method): Direct Attached Storage. We
will look at the way data moves between the host and the storage device.
In the next modules the two alternative methods will be discussed: Network Attached Storage (NAS)
and Storage Area Network (SAN).

Direct Attached Storage
An ICT infrastructure is the physical solution that allows users to

access the required information they need.
The first ICT infrastructures were based on a very simple concept we
n
now refer to as : Direct Attached Storage.
DAS definition : One or more dedicated storage devices connected

/ e
to one or more servers.
o m
Disk technologies used:
SCSI / SATA / SAS.
e i .c
aw
u
HOST
g .h
DISK STORAGE
ni n
r
// lea
p :
t
In a DAS environment, every host is responsible for the data it generates. So the information
t
:h
generated by the user with his application is stored locally on the same host. For that purpose the
s
host needs physical storage capacity in the server to store the data, but also storage capacity is
c e
needed to store the operating system and application software. The actual storage devices used in
r
ou
each server can be internal and\or external. Internal storage mostly means that the server has built in
s
hard disks that hold both the operating software as well as the user data. External storage means that
e
R
in most cases the capacity of the internal disk was not enough. When more capacity is needed an
i n g
extra chassis holding hard disks can be connected to the server via a SCSI cable.
Because all data is stored locally it meant that the host administrator was also responsible for keeping
r n
a
the data secure.
L e
In case of a technical problem or when a user deletes data the host administrator should be able to
r e
recover the lost data. So in practice every host was fitted with a local backup device and on the host a
o
backup software program was installed.
M
Because of the fact that no centralization was possible we also describe DAS infrastructures as
Islands of Storage. Sharing information between DAS infrastructures was/is virtually impossible.
The method used to connect a host with its physical disk (both internal disks in the host itself as well
as a connection to an external disk storage unit) in the first generation of DAS was based on the SCSI
technology.
In SCSI (Small Computer Systems Interface) there are strict regulations on the cables, connectors
and electronic signals used to transmit the user data between host and physical disk.

Initially based on parallel SCSI technology.

Small Computer System Interface is an intelligent system for
exchanging data between SCSI devices.
Limited in :
e n
- Number of devices (max=16).
/
m
- Cable length (up to 25 meter).
- Performance (320 MB/s).
.c o
SCSI Bus architecture congestion problems.
e i
A SCSI block represents 512 Bytes of data.
aw
u
g .h
ni n
r
lea
Slide 5
: //
t t p
The technology used to connect the host to the storage device (could be a hard disk or a CD-ROM
:h
player or a backup unit) was parallel SCSI. The technology was developed in the 1970s and has
e s
been in use until the beginning of this millennium.
r c
ou
In SCSI we use the term block to indicate the smallest amount of data that can be transported. The
es
block size for SCSI is 512 bytes. If a file of 2 MB is stored on a SCSI based device it means that many
R
individual blocks are used to represent the file.
i n g
r n
Let us look to the traditional parallel SCSI technology first.
e a
e L
Based on a so-called bus system we can connect up to 16 devices to a SCSI bus and have them
or communicate amongst themselves. As the technology was improved over the years from the original
M
SCSI standard into Ultra 320 SCSI the throughput was increased from 5 MB/s to 320 MB/s. But at the
same time the maximum cable length allowed has decreased because of technical limitations. At best
the cable length in Ultra 320 SCSI is 25 meters, but in practice a cable is hardly ever over 12 meters.

SCSI Protocol and Storage System
SCSI protocol and storage system
Small Computer System Interface (SCSI) is an interface technology

specifically developed for midrange computers and used for connecting
hosts and peripheral devices.
The SCSI protocol is the basic protocol for communication between hosts
and storage arrays.
DAS uses the SCSI protocol to interconnect hosts and storage arrays.
e n
SCSI bus
/
HBA Data/Address bus
o m
SCSI ID 7
e i .c
w
Control signal
SCSI array SCSI array
a
ID 0 ID 5
u
.h
LUN 0 LUN 1 LUN 0
g
LUN 2 LUN 1
ni n
r
// lea
The controller sends a signal requesting to use the bus to the bus processor. After this request is
:
accepted, the source device sends data. In this way, the bus is occupied by the source device and the
p
t t
other devices connected to this bus cannot use the bus. SCSI is an interface used to connect
:h
between hosts and peripheral devices including disk drives, tape drives, CD-ROM drives, and
e s
scanners. Communication is handled according a protocol and consists of user data, commands and
r c
status information. Communication is started by the initiator and is directed to go to the target.
s ou
SCSI protocol
Re
i n g
Host-to-Disk communication is from the Initiator to a Target.
r n
e a Host/ I/O request Disk/
L
Initiator Target
r e C/S
o
SCSI Application Layer SCSI Application Layer
M SCSI Transport
Command/Data
SCSI Transport
Protocol Layer Protocol Layer
Bus connection
SCSI Interconnect Layer SCSI Interconnect Layer

Parallel SCSI Technology
ANSI standard (describes electrical bus interface and command set).
Bus for computer devices attachment.

termination
e n
/
host
adapter
multidrop bus
SCSI
o m
Device A Device B Device C Device D
e i .c
w
devices
u a
g .h
ni n
r
// lea
p :
t t
In the SCSI bus architecture any of the connected devices can communicate with any other device.
:h
To achieve that a signal will be transmitted from the device and it will eventually end up at the
e s
multidrop bus. From there it should be forwarded to the required second device. There are a few
r c
physical and logistical problems in this way of communicating.
s ou
Two of these problems are:
Re
g
- How to make sure that multiple simultaneous users of the bus do not interfere with one another?
i n
- How to arrange things so that data actually arrives at the right device on the bus?
n
ar
e
These problems of course have been solved and the solutions will be explained in the upcoming
L
e
sections.
or
M

SCSI Principles
SCSI principles
SCSI is an intelligent protocol that allows devices to communicate

without the help of the CPU or SCSI adapter card.
Transfer protocols: - asynchronous.
n
- synchronous.
Multiplexed bus for transfer of commands, data and status / e

information.
o m
SCSI
e i .c
w
DATA commands DATA Status info DATA
Sync Async Sync Async Sync
u a
time
g .h
ni n
r
// lea
:
A great advantage of SCSI is the intelligence of the system. If multiple devices are connected to the
p
t
same bus (parallel communication path) they can communicate with each other independently. That
t
:h
means that two devices that want to communicate do not need the approval of for instance a CPU in
the host or a special card.
e s
r c
ou
The communication itself is in two different types: synchronous and asynchronous.
es
R
In asynchronous transmission there is no predefined timeframe between two sent transmission
n g
signals. The protocol uses extra information, that will be send before the official data, so the receiving
i
r n
side becomes aware of the fact that packets that will be arriving soon. Examples of information that is
e a
sent asynchronous: status information (i.e. bus free checks) or commands that initiate a new
L
connection. Commands and status information will not be generated in a fixed pattern so the time
e
r
between the transmissions is variable. This is very specific for asynchronous communication.
o
M
Synchronous communication requires a clock circuit to transmit the data packets with specific
intervals. In practice two devices will communicate asynchronously first to find out if the other device
is ready to receive new information. After this initial connection is set up the actual data is sent using
the fastest method possible and that is synchronous communication. In synchronous mode data is
sent quickly after another with a fixed time between two data packets. The receiving devices know
this fixed time interval and can accept and process the packets quickly.

Multiplexing is the term used to describe a system where a physical cable is shared by sequentially
allocating the use of the cable to different devices. In this case the data send across the cable on a
certain moment is a user data packet and a moment later it can be an address or status information. It
means that inside of a SCSI cable there are no separate wires used for addressing the devices and
separate wires for sending user data across. At one point in time the signal must be interpreted as an
address where the next moment the signal represents user data.
e n
/
o m
e i .c
aw
host
u
.h
bus
adapter
g
SCSI
ni n
r
lea

: //
Device A
t t p
Device B Device C Device D
:h
(1) Device B transmits a signal headed for device D.
e s
r c
s ou
e
R
i n g
r n
Electrical signals move across a copper wire in all directions and at each intersection the signal splits
a
up and continues (as a bit weaker signal) across all wires.
e
e L
or So: as the signal arrives at the intersection of the cable from device B and the bus; the signal will be
split up into two identical signals and move on in two different directions. The signal will split at the
M intersection to device A as well as at the intersection to device C. But also will it continue towards the
intersection with device D.

host
adapter
SCSI
e n
/
Device A Device B Device C Device D
o m
e i .c
w
(2) The signal will be split up at the intersection and moves in two directions !
u a
g .h
ni n
r
// lea
The signal travels onwards towards the intersection of the bus and the cable from Device D. There
again it will split up into two identical copies.
p :
t t
s :h
r c e
s ou
e
host
R
adapter
SCSI
i n g
r n
e a
e L Device A Device B Device C Device D
o r
M (1) Device B transmits a signal headed for device D.
(3) The signal will split again : a signal goes towards Device D but another signal will go on !
One copy moves towards device D just as we wanted. The second copy continues until it reaches the
physical end of the cable.

Device D (just as devices A and C) receives the signal. Inside of the message the devices receive
there is information that makes it clear that a packet is meant for one specific device only. So devices
A and C will see that the packet is not for them and ignore the information. Of course device D
recognizes that the information is for him and accepts the new packet.
e n
host

/
m
adapter
o
SCSI
e i .c
aw
u
Device A Device B Device C
g .h
Device D
ni n
r
lea
//
(3) The signal will split again : a signal goes towards Device D but another signal will go on !
:
(4) The terminator at the cable end will absorb the signal so it cannot be reflected and cause problems.
t t p
s :h
c e
So device D gets the information it needs, but we still have a signal that continues to travel across the
r
ou
bus towards the end of the physical cable. At the end of the cable there are a few possibilities : the
s
signal could be reflected, absorbed or distorted. In any case we dont want any signals to be reflected
e
R
as the signal will interfere with other signals sent that move over the bus.
i n g
n
To avoid the signal being reflected back onto the bus in the opposite direction a so-called terminator
ar
is used to absorb the signal. A terminator looks like a very simple plug that is connected to the end of
L e
the cable but it is a very important part of the success of any SCSI bus communication. A SCSI bus
r ewithout terminator will not be able to transmit any packets of information successfully.
o
M Note:
On the first slide of the SCSI bus we saw that a signal also travels towards Device A (and will have a
copy continue to the SCSI adapter). That signal that travels to the SCSI adapter will have to be
terminated too in order to prevent reflections there.

Parallel SCSI Specifications
Parallel SCSI specifications
Maximum of 16 devices on the SCSI bus.
Bandwidth limitation of 320 MB/s.
Cable length limitation of 25 m in HVD and 12 m in LVD.
e n
/
Terminators are used at end of bus.
o m
e i .c
aw
u
Single Ended LVD LVD/SE
g
HVD
.h
ni n
r
Slide 14
// lea
p :
The number of devices connected to the SCSI bus (including the adapter) was 8 in the very first SCSI
t t
:h
standards. Later the number was increased to be 16.
e s
c
Physical problems (skewing and interference) have made it almost impossible to keep on improving
r
ou
the bandwidth of SCSI beyond 320 MB/s. Different technologies like Single Ended, Low Voltage
s
Differential and High Voltage Differential have been used but the cable length could not be more than
e
R
25 meters at best.
i n g
n
As the technologies are different it is important not to mix them : Single Ended devices cannot be
ar
connected to a SCSI bus that is also connected to High Voltage Differential devices !
L e
r e
Each technology is indicated with an icon. There is one combination allowed : Single Ended and Low
o
Voltage Differential can work together because they use the same voltage level of the signal so the
M
components will not be damaged. However the Single Ended technology has much lesser
specifications and whenever two devices SE and LVD are mixed the lowest specifications will be used.
This of course means that the LVD device will work less optimal.

Electrical Specifications
Electrical specifications
Single Ended.
Uses a reference (ground) to determine whether or not a signal
that is received is a logical 1 or a 0.
Operates at a level of 3.3 Volt.
e n
Low Voltage Differential and High Voltage Differential.
/
Uses a clever trick to eliminate the effect from external distortions.
Operates at 3.3 Volts (LVD) or 5 Volts (HVD).
o m
e i .c
aw
u
g .h
ni n
r
Slide 15
// lea
p :
Inside of the definition of the SCSI standard there are rules and regulations about how the SCSI
t t
:h
protocol works with the sending of data and the way to make sure the right device receives the data it
s
needs. But there are more things defined in the SCSI standard and one of the things is all electrical
c e
properties of the devices. Because all devices are connected to the bus the requirements are such
r
ou
that signals should not influence other signals or other devices. First thing was to agree on a specific
s
voltage level for a signal. In SCSI the data is transmitted as digital information. In digital information
e
R
the only information is 0 or 1.
n g
The way to make clear that a logical 1 was sent is by defining a voltage level to represent it. The
i
n
sending device now creates a pulse with a given voltage level. The receiving device can detect the
r
a
signal as the electronics detect a signal with a certain voltage level. When the voltage level is equal to
e
e L
what was defined as a logical 1 the message will be interpreted as a valid signal 1. Anything less than
or that voltage level is not accepted as a valid signal.
M
In the electronics in the 1970s and 1980s commonly used the 5 Volt voltage level. Later the levels
have been lower to 3.3 Volts and nowadays it is 1.5 Volts. Although the difference between 5 V and
3.3 V seems very small for the production of the electronic components it is a big advantage when the
voltage level is lower.
There are two ways to transmit signals over a copper wire : asymmetrical (or Single Ended) and
Symmetrical (Differential Signaling). In the next section the difference will be explained.

Single Ended SCSI
Single Ended SCSI
Cable lengths are from 6 m (Fast SCSI) down to 1.5 m for the last
standard that supported SE (Wide Ultra SCSI).
e n
original signal external signal
/
3.3 Volt
o m
.c
0 Volt
1 0 1 0 1 0
0 Volt
1 0 1 1 1 0
e i
Ground/ reference signal Ground/ reference signal
aw
u
g .h
ni n
r
Slide 16
// lea
p :
With Single Ended, the signal is transported to the other device using a single cable and for reference
t t
:h
purposes a ground signal (equals 0 Volts) is used. At the receiving end the signal is measured again
s
with reference to the ground signal. If somewhere in the cable an external signal is picked up (cross
c e
talk signals, external noises) the receiving end might interpret this distortion as a legitimate signal and
r
ou
read a logical 1 where the original signal sent a logical 0 signal.
es
R
As the performances got higher and higher it became more difficult to distinguish between real data
defined.
i n g
and distortions. Single Ended technology was basically used until the Wide Ultra SCSI standard was
r n
e a
L
At the end Single Ended cables could not be longer than 1.5 meters. The reasons is that physics
r e
creates problems for Single Ended systems with high speed communication.
o
The biggest problem is that with higher speeds the signals that need to be transported cannot easily
M
be distinguished from externally created distorting signals.
The next problem was that it became more and more difficult to protect the physical cable against the
influence of external signals. It is obvious that when the cable is very long the chance that a cable
picks up distortion signals is higher than with short cables. That is basically the reason that Single
Ended cables had to be so short that the distance was less than a couple of meters. And that of
course is not useful when building an ICT infrastructure.

Differential Signaling
Differential signaling
Two signals are transmitted: 3.3 Volt
a) the original signal. 0 Volt
b) the inverted original signal. 0 Volt

-3.3 Volt
e n
/
At the receiving end the inverted signal is subtracted from the
o m
.c
original signal.
e i
w
6.6 Volt
a
a
u
a-b
0 Volt
.h
b
i n g
n
r
Slide 17
// lea
:
With the differential signaling the effect of external distortion can be eliminated because the original
p
t
signal will be detected in an amplified state (3.3 V - -3.3 V equals a 6.6 V output signal). However the
t
:h
distortion, here the red pulse in the cable that transports the original signal, will not be amplified and
s
so it is possible to state that all signals less than 5 Volts are logical 0-s or distortions which we now
e
can ignore.
r c
s ou
e
With differential signalling it becomes easier to determine whether a received signal is a valid 1 or a
R
distortion. That is why with differential signalling the cable lengths were 25 meters.
i n g
r n
However: there are two versions of differential signalling called HVD and LVD.
e a
In HVD or High Voltage Differential the voltage levels used are the traditional 5 Volts. With LVD or
e L
Low Voltage Differential the voltage level is 3.3 Volts. Just as with other electronic components the
or cost for producing 5 Volts components is higher than with 3.3 Volts components. So over the years
the HVD devices became less popular and LVD devices became more or less the standard.
M
It is obvious that on a bus only signals of the same voltage levels can be transmitted. It is therefore
impossible to connect HVD devices on a bus that is also connected to LVD (or Single Ended) devices.
The difference in voltage levels will probably damage the electronics in the LVD and SE devices !

SCSI Bus Communication
SCSI bus communication
While one device uses the bus other devices may be active
performing internal activities.
Devices only connects to the bus for Data transfer or status reports.
Devices may disconnect from the bus and reconnect if needed.

e n
Connections takes place between Initiator and Target. /
m

.c o
i
4
e
7
target
initiator
device
aw
u
5 9 3 13
g .h
ni n
r
Slide 18
// lea
p :
One of the problems with bus communication is to make sure that multiple devices should not send
t t
:h
data at the same time. When multiple devices send out signals at the same time congestion will occur.
s
Congestion means that the signals will clash together and the result is that the transmission is
c e
unsuccessful. To test if the bus is available for a connection, we use the bus free phase. A device will
r
ou
test if the BSY and the SEL signal wire are false for a specific time (bus settle delay). If the bus is free
s
the protocol moves into the next phase: arbitration. Arbitration arranges two things: first it allows a
e
R
device to claim the bus for its upcoming transmission. Secondly there is a system that decides who
i n g
will get the bus if multiple devices try to claim the bus at the same time.
r n
a
The SCSI ID is the ID used in the addressing phase to indicate who the specific receiver\addressee of
L e
the message is. So using the SCSI ID it can be determined who will receive a packet but also how
e
high the priority is of that receiver. Typically the fastest devices (i.e. hard disk) on the bus get higher
r
o
priorities than slower devices (tape backup units).

SCSI Phases
SCSI Phases
SCSI-communication is divided into phases :
Bus Free: before starting a communication the bus must be idle. A

test signal will detect if this is the case.
Arbitration: making sure only one communication runs at any
e n
/
given time
Addressing: here, using the sender address and the receiver
address, will be decided who are about to communicate.
o m
Negotiation: both sides decide on which data path width and
speed to use in the transmission afterwards.
e i .c
Connection: the actual data transmission part.
aw
u
.h
Disconnect: transmission successfully completed => bus released.
i n g
r n
// lea
p :
Every time a connection is established (or in other words a connection between two SCSI devices is
t t
:h
created) all steps of the communication have to be made. Once the device notices that the bus is free
s
the device has now exclusive rights to transmit data over the bus.
r c e
ou
First thing to do next is to tell with which device he wants to communicate. This is called the
s
addressing phase and SCSI uses the SCSI IDs to indicate the target device.
e
R
i n g
Because of the fact that various SCSI versions exist (in speed and number of devices used) both
n
devices have to negotiate on which settings to use:
ar
L -
eWhat will be the transmission rate.
r e - How many addresses are available (8 or 16).
o
M This negotiation phase takes a relative long time to complete. Only then the actual user data will be
transmitted between the devices.
As for every data transmission the steps have to be completed it means that sending data across
SCSI busses can take a long time. Techniques are used to make this time shorter. One important
technique is disconnect-reconnect. Here a device makes the initial connection following all the steps.

Only when the device wants to transmit data to the same device again they can now skip the
negotiation phase as they already know who the receiving device is and what its specifications are.
Another time-saving feature is Tagged Command Queuing or Native Command Queuing.

It is used in most modern hard disks and it uses the concept of sending multiple data packets in one
batch. The device (here the hard disk) will then internally handle the multiple packets and write the
individual SCSI blocks to the physical disk.
e n
/
While the device internally stores the SCSI block the bus will be released so other devices can use
m
the bus in the meantime. This requires the connection to be created less often and the usage of the
bus gets improved.
.c o
e i
aw
u
SCSI Development
g .h
ni n
r
lea
SCSI development
: //
Datapath : 8 BITS
t t p Datapath : 16 BITS
:h
1 MB/s 5 MB/s
SCSI Async Sync
freq x 2
e s
c
FAST SCSI 10 MB/s FAST WIDE 20 MB/s
r
ou
freq x 2
ULTRA 20 MB/s ULTRA WIDE 40 MB/s
es freq x 2
R
ULTRA2 40 MB/s WIDE ULTRA2 80 MB/s
ing
DTC
ULTRA3 160 MB/s
rn
freq x 2 DTC
ULTRA320 320 MB/s
e a
e L
r
o
M
It was decided in the first SCSI standard to transmit all status information and all SCSI commands (i.e.
addresses) in asynchronous mode at 1.5 MB/s. Once the selection phase was completed the actual
user data was sent in the synchronous mode which leads to higher transmission speeds.
To stay backward compatible in Fast SCSI the asynchronous status/command transmission was kept
constant at 1.5 MB/s whereas the data speed was doubled to 10 MB/s. This is still the situation at this
moment !

Mostly the performance gain was achieved because of increasing the clock frequency so signals
could be transmitted faster. As from Ultra3 they used a second technology to improve the
transmission rate: Double Transition Clocking.
In SCSI a clock is used to determine when a sample has to be taken of the incoming signal and at
that point they will measure the signal. The clock signal is a block shaped signal and it varies between
0 Volts and 3.3 Volts. The stage in which the signal changes from 0 Volts to 3.3 Volts is called the
raising flank of the clock signal.
When the signal has a value of more than 3.3 Volts it is considered to be a logical 1 signal. Anything
e n
/
m
less than 3.3 Volts is considered a logical 0.
.c o
e i
Single / Double Clocking
aw
u
Single/Double Transition Clocking
g .h
ni n
r
lea
1 0 1 1 0 1 1 0
single
: //
t t p
s :h
r c e1 0 1 0 1 1 1 0
ou
1 0 1 1 0 1 1 0
es
R
double
i n g
r n
e a Copyright 2015 Huawei Technologies., Ltd. All rights reserved. Slide 21
e L
or In the above diagram with single transition clocking the rising flank of the clock signal is used. In
M the example the data received will be interpreted to be 8 bits of data :
1 0 1 1 0 1 1 0
With double transition clocking the falling flank of the clock signal (indicated in red) is also used as
sampling moments. Now not 8 data bits but 16 bits can be represented and that means the number of
transmitted information is doubled without actually changing the clock frequency !
1 1 0 0 1 1 1 0 0 1 1 1 1 1 0 0

SCSI Definitions
SCSI definitions
Max. Bus Length, Meters

Bus Speed Bus Bus Max.
Mbytes/sec. Speed, Width, Single
n
SCSI-Protocol Devices
Max MHz Bits -
Ended
LVD HVD
Support
/ e
SCSI-1 5 5 8 6 25 8
o m
Fast SCSI 10 10 8 3 25
e i .c
8
w
Wild Fast SCSI 20 10 16 3 25 16
Ultra SCSI 20 20 8 1.5
u a
25 8
Wide Ultra SCSI 40 20 16 1.5
g .h 25 16
n
Ultra 2 SCSI 40 40 8 12 25 8
ni
r
Wide Ultra 2 SCSI 80 40 16 12 25 16
lea
Ultra 3 SCSI 160 40 16 12 25 16
://
Ultra 320 SCSI 320 80 16 12 25 16
t tp
:h
es
r c
s ou
The table clearly shows that the maximum cable lengths have decreased over the years. For Single
Re
Ended devices the cable could not be more than 1,5 meters at the time of Wide Ultra SCSI.
i n g
Also visible is the fact that there is no Wide Ultra 3 SCSI defined. At that time it was decided that the 8
r n
bit wide addressing was no longer required and therefore only the 16 bit version was standardized.
e a
L
Although both HVD and LVD are still supported as a SCSI standard in practical life the LVD standard
e
is mostly used. Reason is mainly because of the cost difference between the hardware components
r
o
for LVD and HVD. It was already stated before that HVD devices cannot be mixed with LVD devices
M
on the same SCSI bus. To prevent this happening it is important to check that before powering on the
devices. At that point it is useful to look at the specifications of all connected devices and the icons
used for SE, LVD and HVD.

SCSI Protocol Addressing
SCSI protocol addressing
Bus
Differentiates SCSI buses.
number
e n
Device Differentiates devices
/
ID connected to SCSI buses.
o m
e i .c
LUN
Differentiates sub-
aw
u
devices in SCSI devices.
g .h
ni n
r
Slide 23
// lea
p :
The SCSI protocol introduces SCSI device IDs and logical unit numbers (LUNs) to address devices
t t
:h
connected to the SCSI bus. Each device connected to the SCSI bus has a unique ID. The host bus
s
adapters (HBAs) on servers also have device IDs. Each bus has 8 or 16 device IDs. It is the Device
c e
ID that can be used for prioritization. SCSI IDs were set inside of the devices and with that the priority
r
ou
of a device could be determined. It was then important not to give the same SCSI ID to two different
s
devices as that would interfere with the addressing and priorities !
e
R
i n g
Storage devices may have a number of sub-devices, such as virtual disks, tape drives, and medium
changers. LUNs are used to address those sub-devices.
r n
e a
L
A traditional SCSI adapter is connected to a single bus and therefore has only one bus number. One
r eserver may be configured with multiple SCSI controllers. Accordingly, the server has multiple SCSI
o buses. In a storage network, each Fibre Channel HBA or iSCSI network adapter is connected to a bus.
M Therefore, each bus must have a unique bus number. We can identify a SCSI target with three
variables: bus number, device ID, and LUN.

Method for querying the SCSI device ID in Windows
Method for querying the SCSI device ID in Windows
e n
/
o m
e i .c
aw
u
g .h
ni n
r
Slide 24
// lea
p
Right-click on My computer and choose Manage from the short-cut menu. In the Computer :
t t
:h
Management window, click Disk Management in the navigation tree. Right-click the mapped disk and
s
choose Properties from the shortcut menu. On the General tab page, you can view the SCSI device
ID information in Location.
r c e
s ou
The picture shows the identifier as Bus Number, Target ID and LUN ID. (or B-T-L). The target ID is
Re
now the actual SCSI ID. The term target is generally used for the location where data is physically
i n g
stored. That could be a physical hard disk but also a more complex storage system.
r n
e a
e L
o r
M

ATA and SATA
ATA and SATA
Advanced Technology Attachment was the standard in desktops in

the 1990s.
Use the Programmed IO method and are therefore not very fast or
intelligent.
e n
Serial ATA is the improved version. It has first replaced ATA in
/
m
desktops but...
Because they were relatively cheap and had big capacities they are
.c o
also used in enterprise servers and storage devices.
e i
NL-SAS offers the advantage of big capacity with SAS intelligence.
aw
u
g .h
ni n
r
Slide 25
// lea
:
Parallel SCSI has reached its limits of use. It is too difficult to improve the performance as physical
p
t
problems at that point become hard to solve. Serial communication is indifferent to many of the
t
:h
physical problems that parallel communication has. It is therefore the way technology evolves in.
s
SATA is the improved serial version of the ATA (Advanced Technology Attachment) technology that
e
r c
was used in laptops and desktops. With ATA (or better Parallel ATA or PATA) there is a bus
ou
architecture just like with parallel SCSI. However : the PATA interface works different from SCSI.
es
Unlike with SCSI, where the devices can independently decide to communicate with other devices, a
R
PATA interface uses a so-called PIO mode concept.
n g
In PIO mode, or Programmed Input Output, communication is always controlled by the Central
i
n
Processing Unit (CPU) in the host. In the CPU a special software program is used to transfer the data
r
a
that needs to be stored from the RAM memory towards a special register in the CPU. The design of
e
e L
the CPU and software now enables the data to be moved from within the CPU chip via a copper
or based bus system to the interface of the hard disk.

PATA interface were not used in high end solutions because the speed was not optimal. That was
M partly because of the PIO mode but also because with parallel communication in general the
performance is limited.
When SATA was introduced they initially replaced the PATA interfaces that were used in desktops
and laptops. Later they also got used more and more in high end systems. That was primarily
because the capacity of SATA drives was larger than of SCSI drives and at the same time the price
was relatively low. Many vendors used SATA drives in their storage solutions because of the price
and capacities of the disks for some 5 years.

SATA itself is not completely outdated but most vendors have switched over to the superior SAS
technology. With SAS the benefits of SCSI are kept and the limitations it had have been removed.
Capacities of SAS disks are however smaller than the capacities of SATA disks. So a number of
vendors offer storage solutions that use so-called NL-SAS disks or Near Line SAS. The NL SAS disk
is basically a SATA disk drive that is fitted with a SAS type interface and that therefore can be
connected with a SAS device.
So let us have a look at Serial Attached SCSI.
e n
/
o m
e i .c
aw
u
Serial Attached SCSI
g .h
ni n
r
Serial Attached SCSI (1)
// lea
In storage SAS has taken over from parallel attached SCSI and
p :
from SATA.
t t
:h
SAS uses a point-to-point architecture : performance 300 MB/s.
s
r c e
s ou
Re
i n g
r n
e a
e L
o r Copyright 2015 Huawei Technologies., Ltd. All rights reserved. Slide 26
M
A point-to-point connection is designed to be a dedicated link for communication whereas a multidrop
bus has to share the bus. Accessing a point-to-point link is much quicker because no negotiations
have to be held to find out who is allowed to use the link.

e n
/
o m
e i .c
w
SAS SATA compatibility
a
u
g
Slide 27
.h
ni n
r
lea
In the design of the SAS interfaces, they have decided to use the same form factor as with SATA for
//
all connectors. This even allows some mixes of device types within a group of disks.
p :
t t
:h
e s
c
Architecture allows multiple datapaths with each link running at full
r
speed. Supports bundling of channels for wide-links.
s ou
Re
i n g
r n
e a
e L
or
M
SAS is using full duplex communication.
The most important improvements that SAS offer compared to parallel SCSI are :
Much more throughput because of the serial communication and the promise for the future
that even more performance will be possible. Four channels can be bundled: Wide Link.

A greater number of devices can be connected together. Where SCSI per domain had a
maximum of 16 the maximum for SAS per domain is now 16,384.
Full duplex or bidirectional communication with SAS instead of half duplex (unidirectional).
With traditional parallel SCSI only one connection could be used in one direction. When a
device received a packet in parallel SCSI the response to the packet would be arranged as a
new SCSI communication (with all the necessary steps) after the first connection was
released. Now in SAS two-way communication is possible.
e n
/
o m
e i .c
Up to 16,384 SAS devices can be joined together in a SAS domain.
aw
u
.h
1
Expander
Expander
i n g
r n
lea
Expander
//
SAS
:
RAID Expander
Controller
p
1
t t
:h
Expander
e s Expander
c
128
r
128
s ou
Re
i n g
Per expander a maximum of 128 devices (expanders and/or drives) can be connected. The total
n
maximum of drives attached is 128x128 equals 16,384 drives.
ar
e
A SAS domain therefore exists of expanders and SAS drives. Two types of expanders were defined:
e L 1. Edge expander with only disks attached.
o r 2. Fan-out expander that hold up to 128 expanders.
M
Fan-out expanders are originally equipped with an address routing table that keep track where all
SAS drives are located (each SAS drive gets an unique home address within the domain).
Nowadays also edge expanders are equipped with the routing functionality so the need for separate
fan-out expanders is no longer there.
Note : In practical life the amount of connectors on expander cards (like shown in the picture above) is
less than 128.

Principles of SAS cabling
Principles of SAS cabling
SAS cable has four channels typically. Each channel is now 12 Gb/s.
SAS devices are linked together in a loop (also called chain).
Bandwidth of 4 x 12 Gb/s limits the number of disks in the loop.
e n
Currently the maximum number is 168 as best practise.
/
With 24 disk drive enclosures this makes 7 enclosures.
o m
However: with the faster SSD drives the maximum number is 96 disks or 4
disk enclosures.
e i .c
SAS connectors are:
aw
u
Mini SAS
g .h
n
Mini SAS High Density
ni
r
lea
: //
t t p
Most vendors of storage devices now offer SAS as the technology to connect disk enclosures to the
:h
controller(s). SAS cables usually contain 4 separate channels that can be bundled to provide more
e s
bandwidth. At this point a channel can perform at a speed of 12 Gb/s and as a wide link the four
r c
channels can provide 48 Gb/s of bandwidth. To make sure that the bandwidth is not exceeded best
ou
practices are defined that limit the number of disks that are connected in one single loop.
es
R
For Huawei this maximum at this moment is 168 disks. There can be 24 disks in an enclosure which
i n g
means that a maximum of 7 enclosures are supported per loop. However, this is assuming that the
r n
disks are traditional SAS disks. Now that the SSD is getting more popular we must realize that they
e a
can deliver more output than a SAS disk. This has resulted in a best practice maximum for SSD in a
e L
loop to be set to 96 (or 4 enclosures).
or
M
The physical connector has changed when the 6 Gb/s standard was improved. The 6 Gb/s connector
is referred to as mini SAS and the newer 12 Gb/s standard uses the mini SAS HD (High Density)
connector.

SAS and bandwidth limitations
In principle a loop or chain can contain an unlimited number of devices. It is however very important to
realize that practical problems can occur when the number is too big. In the picture below we will
explain these problems.
SAS and bandwidth limitations

e n
/
m
SAS Interface
5 blocks on the loop

.c o
e i

w
Target
u a
.h
Disk Enclosure #1

g
Target
ni n
r
lea
Disk Enclosure #2

//
Target
p :
t
Disk Enclosure #3
t
s :h
r c e
ou
In the above image a typical situation is given where three disk enclosures are connected to a
es
controller. It is a simplified drawing as in real life all cabling is a bit more complex. This will be
R
explained in the chapter about SAN and there are a few real cabling schemes in chapter 9 too.
i n g
r n
The three enclosures are daisy-chained (or put in a one-after-one loop) and all data from an
e a
enclosure will pass through the enclosure in front of the enclosure. In other words the data sent from
L
a disk in enclosure three will pass through enclosure 2 and enclosure 1 on its way to the SAS
e
r
interface in the device. Similar will all data from enclosure 2 pass through enclosure 1.
o
M
The diagram now shows that adding enclosure after enclosure means that the last cable, from
enclosure 1 back to the SAS interface, transports all sent date from enclosure 1,2 and 3. If too many
disks are sending data at the same time the total sum of data in the last cable may be higher than
what the cable can handle. So in the example 2 or 3 blocks (from 3-2 and 2-1) is not a problem, but
the last cable has to handle 5 blocks (all of them). When 4 block is the maximum for the cable then
sending 5 blocks would be done slower than expected. That is why a maximum number is suggested.

Disk Technology
Disk technology
e n
/
o m
e i .c
aw
u
g .h
ni n
r
Slide 32
// lea
p :
Regardless of the technology of the disk (SCSI, SATA, SAS), the mechanics of disk drives have not
t t
:h
changed much over the years. Having said this we must already mention a new technology that is
s
making a big entry in the disk storage world. This new technology is called SSD or Solid State Disks.
r c e
ou
In a SSD hard disk there are no more mechanical moving parts and data is stored on a medium
s
which is best compared with a huge USB flash disk. Solid State Disks are therefore also referred to as
e
R
Flash Disks. At this moment SSD drives are relatively expensive and their capacity is smaller than
i n g
that of traditional mechanical spinning disks. Later in this module Solid State technology will be
explained in more detail.
r n
e a
L
So let us look at the interior of a disk now.
r e
o
M

HDD Components
HDD components
Platter
Spindle
e n
Actuator
Head
/
o m
Control Circuit
e i .c
aw
u
.h
Interface
i n g
n
r
// lea
The following are mechanical and electrical components of an HDD:
p :
t t
Head: It reads and writes data.
s :h

c e
Actuator: It moves the head or head arm to a desired position.
r
ou
Platter: It holds the recorded data.

s
Spindle: It spins the flat circular disks, which is the platter.
e

R
Control circuit: Implements system control, speed and spinning adjustments.
i n g
n
All hard disks are based on the same principle:
ar
Magnetic materials are used to cover the platter and then magnetic particles are polarized to encode
L e
a binary information unit (or bit).
r e
o
Using the magnetic properties to store data is very old, relatively cheap and therefore very popular to
M
store large amounts of data. Other storage technologies that also use the magnetic properties
are/were floppy disks and tape.

Recording Methods
Recording methods
Longitudinal recording (used in the past).
e n
/
Perpendicular recording. Now used and offers disk capacities of
o m
.c
many terrabytes.
e i
aw
u
g .h
ni n
r
Slide 34
// lea
p :
Although hard disks have now gotten smaller (the format was 3.5 inch initially but now the format is
t t
:h
2.5 inch), the capacity of disk drives has increased over the years.
e s
c
An important reason is the quality of the magnetic materials, the actuator motors and the construction
r
ou
of the read/write head. But even more important was the introduction of perpendicular recording.
s
Now the magnetic field of the read/write head can change the magnetic particles in a vertical plane
e
R
where in the past it changed the particles in a horizontal plane.
i n g
n
With perpendicular recording a higher density can be achieved and therefore a higher capacity. In the
ar
nearby future capacities of more than 8 TB per disk will be available.
L e
r e
o
M

Hard Disk Properties
Hard disk properties
Sector Track
Read / Write head
e n
/
o m
Cylinder
Actuator
e i .c
Platters
aw
Motor
u
Motor
g .h
ni n
r
Slide 35
// lea
p :
Data on a hard drive is stored in tracks and sectors. This is because the platter on which the magnetic
t t
:h
material is fixed rotates and a magnetic read/write moves to a specific location over the disk platter.
The pattern the read/write head sees, is a circular pattern called a track. A cylinder is made up of all
e s
c
similar sectors on a track on all of the platters. So in the picture above sectors A, B, C and D form one
r
ou
cylinder
s
The amount of tracks a hard disk uses is dependent on the size of every individual step the actuator,
e
R
on which the read/write head is mounted, makes. In modern hard disks the number of steps the
i n g
actuator arm can make could be in the hundreds which create hundreds of tracks on the platter. Each
of these tracks is divided into sectors. In a sector a fixed amount of binary information can be stored:
r n
a
For most drives this is 512 bytes (or 512 x 8 bits) although a new sector size of 4k (4096 bytes) is now
L e
also available.
r e
o
The motor spinning the platters/disks are high speed motors that have rpms (rotations per minute)
M
ranging from 7200 rpm up to 15.000 rpm for modern disk drives.
The motor moving the actuator is a so-called stepper-motor which can make specific steps from 1 or 2
degrees if necessary with a great accuracy. This of course is also required for the read/write head to
be positioned in the correct way for each movement it makes.
A small difference in the movement will lead to the head not being positioned over the correct track!

Hard Disk Performance
Hard disk performance (1)
Track Sector 250 sectors per track
Data: 512 bytes per sector (0.5kB)
Per track: 512

250
e n
/
x
125 kB
o m
e i .c
aw
u
g .h
ni n
r
Slide 36
// lea
p :
In this and following slides a few simplifications have been made. Most important one is the
t t
:h
assumption that every track contains 250 sectors. That was the case with early magnetic storage
s
devices but nowadays drives are more intelligent and one can definitely state that the outer tracks
c e
have more sectors in them than the inner tracks. However the average of 250 still is valid in most
r
ou
cases.
es
R
The number of 512 physical bytes of data per sector is also valid but it is depending on the operating
i n g
system accessing the drive how much actual data can be stored on a disk. Within operating systems
like MS Windows the term cluster size is used. This is the smallest amount of hard disk space a file
r n
a
can occupy. Floppies have a cluster size of 512 bytes and hard disks can have a cluster size ranging
L e
from 1 kilobyte to 16 kilobytes (sometimes even more).
r e
o
M

10k RPM One revolution takes
60
= = 6 ms
10.000
One revolution equals 125 kB of data
e n
/
o m
Transfer =
125 kB
6 ms
= 20.83 MB/s
e i .c
aw
u
g .h
ni n
r
lea
The rotational speed of a disk drive is the number of rotations the platter makes every minute. In
storage devices nowadays three rotational speeds (or RPMs) are used:
: //
t t p
:h
- 7.200 Rotations Per Minute.

e s
r c
ou
es
R
It takes the platter 6 ms to make one full turn. If the read/write head reads all the data in that track it
i n g
has read 125 kB of data. Transfer speeds or throughput are measured in MB/s so in this case: 125 kB
n
in 6 ms makes a throughput of 20.83 MB/s for a 10.000 RPM disk drive.
ar
Note :
L e
r e
This is the ideal situation. As normally the read/write head is not over the right track and has to be
o
moved there. Also: once the read/write head is over the track it does not mean that the right sector is
M
beneath the read/write head. Statistically you will have to wait half a turn to get to the correct sector to
begin the read. This half turn is called the rotational latency. Sometimes the sector is directly under
the read head and sometimes it has just moved past the read/write head and you will have to wait a
full turn. The average wait is therefore a half turn.

15k RPM One revolution takes
60
= = 4 ms
15.000
One revolution equals 125 kB of data
e n
/
o m
Transfer =
125 kB
e i
= 31.25 MB/s .c
w
4 ms
u a
g Slide 38
.h
ni n
r
// lea
With a disk with a higher number of RPMs, the full turn is shorter in time. Now it would take just 4 ms
to read the same 125 kB and the throughput would then be 31.25 MB/s.
p :
t t
As mentioned before this is the ideal situation. The next picture shows the effect of rotational latency
:h
and the effect of having to move the read /write head to the proper track on the throughput.
e s
r c
o u
Hard disk performance (4a)
e s
R 10k drive:
i n g Seek Time 6 ms
r n
a
Rotational latency = track = 3 ms
e
eL
Read time track = 6 ms
or
+
Total time needed = 15 ms
M
Full
access 125 kB
transfer = = 8.33 MB/s
15 ms

Hard disk performance (4b)
15k drive:
Seek Time 6 ms
Read time track = 4 ms
n
+
e
Total time needed = 12 ms
/
o m
Full
access 125 kB
e i .c
w
transfer = = 10.4 MB/s
a
12 ms
u
g .h
ni n
r
lea
Modern day hard disks take approximately 6 ms to move the read/write head actuator from one track
//
to another track. This is referred to as the seek time. So it takes 6 ms to get to the right track; another
:
t p
half a turn to find the right starting point on the track and then another full turn to read all data in the
t
:h
track. The above picture shows that this has a big impact on the throughput of a disk. Things get even
s
worse when we do not want to read the entire track but we are now interested in a single sector!
r c e
ou
The term sequential read is used when data is read from a disk drive from many consecutive sectors
s
on the same track. Sequential reads (or writes) are relatively quick as the read\write head does not
e
R
have to move between tracks to get to many sectors of data.
i n g
In real life the data is stored randomly across the magnetic surface of the platters. It is partly because
n
of the working of the operating system but also because of the technology inside of storage device.
ar
L e
For random reads the data needs to be picked up as individual sectors that are located on different
r e
tracks. The next picture shows what that means for the performance of the disk drive.
o
M

Hard disk performance (5a)
10k drive:
Seek Time 6 ms
Read time one sector = 0.02 ms
n
+
Total time needed = 9.02 ms
/ e
o m
Single
sector 512 bytes
e i .c
transfer =
9.02 ms
aw
= 55.4 kB/s
u
g Slide 41
.h
ni n
r
// lea
:
Hard disk performance (5b)
t tp
: h
e s 15k drive:
r c Seek Time 6 ms
o u
s
R e Read time one sector = 0.016 ms
g
+
n
Total time needed = 8.016 ms
n i
ar
e
eL
Single
sector 512 bytes
or
transfer = = 63.9 kB/s
8.016 ms
Per disk the throughput is not very high if only individual sectors are picked up off of a disk platter.
Fortunately in a hard disk multiple platters are used and multiple read/write heads that can pick up
more data for us. Add to that the fact that many disk drives can be used simultaneously which then
implies that the amount of data that can be read per second is enormous.

Apart from the amount of data a disk drive can read from the magnetic platters there is also a
parameter to be mentioned: IOPS.
IOPS is short for Input and Outputs Per Second. This IOPS value states how many times per
second a disk drive can push out data blocks (different sizes are possible when you do test) out of
the interface of the disk drive onto the network/path to the host.
For performance information the number of IOPS a disk drive can deliver is very important. If an
e n
/
application wants data to be moved from the disk to the host quickly it needs many IOPS. The number
m
of IOPS per disk is mechanically fixed. The following (average) values for IOPS can be used:
.c o
Drives based on SATA technology : 80 100 IOPS.
e i
Drives based on SAS technology : 150 200 IOPS.
aw
u
g .h
By having multiple hard disks send data simultaneously the total amount of IOPS can be calculated
by simply adding the IOPS values of all individual hard disks used.
ni n
r
// lea
p :
t t
s :h
r c e
s ou
Re
i n g
r n
e a
e L
o r
M

Average Access Time
Average access time
Average access time contains two parts:
1. Average seek time.
2. Average latency time.
Platter Latency
e n
/
Data block
o m
Seek
e i .c
Tracks
aw
u
.h
Seek time Latency time
i n g
n
r
// lea
:
Average Seek Time
t t p
The average seek time of an HDD is the time it takes for the head to move from its initial position to
:h
the specified position. It is an important parameter that affects internal data transfer rate. The lower
e s
the average seek time, the better. The average seek time of IDE HDDs ranges from 8 ms to 11 ms.
r c
Average Latency Time
s ou
Re
The latency time, also known as hibernation time, refers to the time it takes for the desired data to be
n g
beneath the read head, assuming the head is over the desired tracks. Statistically it is half of the time
i
r n
it takes for a complete turn of the platter. Therefore, the faster an HDD rotates the lower the average
a
latency time. The average latency time is usually less than four milliseconds.
e
e L
or Average Access Time
M The average access time is the sum of the average seek and latency time.

Transfer Rates
Transfer rates
Data transfer rate.
Internal transfer rate.
External transfer rate.
Platter
e n
/
HDD
o m
Seek
e i .c
Tracks
aw
u
.h
External Internal
i n g
n
r
Slide 44
// lea
Data Transfer Rate
p :
t t
Data transfer rate refers to the speed at which an HDD writes or reads data and is expressed in MB/s.
:h
Data transfer rate is divided into internal transfer rate and external transfer rate.
e s
r c
ou
Internal Transfer Rate
es
Internal transfer rate, also called sustained transfer rate, refers to the speed at which data are
R
transferred from an HDD to its high-speed cache. It reflects the performance when the disk cache is
n g
not in use. It is a bottleneck for the overall HDD speed. Internal transfer rate mainly depends on the
i
r n
HDD rotational speed and is expressed in Mbit/s rather than MB/s.
e a
e L
External transfer rate
o r
External transfer rate, also known as burst data transfer rate or interface transfer rate, refers to the
M
speed at which data are transferred from the system bus to the disk cache. It is affected by the HDD
interface type and the size of HDD cache.

IOPS and Throughput
IOPS and throughput
IOPS
Input/Output Operations Per Second (IOPS) is a common disk

performance indicator that refers to the number of reads and writes
per second in an HDD.
e n
Throughput
/
Throughput indicates the amount of data that can be successfully
o m
i .c
transferred within a given time. For applications involving large-
e
quantity sequential reads and writes such as video editing and video
on demand (VoD), throughput is more important than IOPS.
aw
u
g .h
ni n
Slide 45
r
// lea
:
I/O calculation algorithm
t t p
The time it takes for a disk to complete an I/O request consists of the seek time, latency time, and
:h
data transfer time.
e s
r c
The seek time (Tseek) refers to the time taken by the head to move to a specified position. A shorter
ou
seek time indicates faster I/O operations.
s
e
Mainstream disk seek time ranges from 3 ms to 15 ms.
R
i n g
The rotation latency (Trotation) refers to the time it takes for the desired data to be beneath the
r n
read head. The rotation latency depends on the rotational speed and is usually half of the time it takes
e a
for a complete turn of the platter.
e L
For example: The average latency of a 7200 rpm disk is: 60 x 1000/7200/2 = 4.17 ms, and that of a
or 15,000 rpm disk is 2 ms.
M The data transfer time is the time that an HDD takes to transfer the requested data. It depends on
the data transfer rate. It is equal to the data size divided by the data transfer rate. Mainstream IDE
and ATA disks can reach an interface data transfer rate of 133 MB/s, and SATA II disks can reach up
to 300 MB/s.

Given such a high transfer rate, the data transfer time is usually much shorter than the seek and
latency time. Therefore, the maximum IOPS in theory is 1000 ms/ (Tseek + Trotation), neglecting data
transfer time.
Suppose that the average seek time is 3 ms and rotational speeds are 7200, 10,000, and 15,000 rpm,
then the maximum IOPS values in theory are:
IOPS = 1000 / (3 + 60,000/7200/2) = 140.
IOPS = 1000 / (3 + 60000/10,000/2) = 167.
e n
IOPS = 1000 / (3 + 60000/15,000/2) = 200.
/
o m
e i
Earlier it was mentioned that SATA based disk drives on average could deliver 80-100 IOPS and SAS .c
w
based disk drives could deliver 150-200 IOPS. That number of IOPS varies a little with different
a
rotational speeds but the maximum numbers are still valid.
u
g .h
Depending on the size of each block that is pushed out we can calculate theoretical throughputs for
i n
the hard disks. The table below shows the values for the three most used types : SATA; SAS; SSD
n
r
// lea
Device Type Realized Transfer speed
p : Number of devices/bus
t t
:h
SATA 200-300 MB/s 2
e s
c
SAS 300-500 MB/s 16,384
r
SSD
s ou
500-1800 MB/s 16,384
Re
i n g
r n
e a
e L
o r
M

Solid State Disk
Solid State Disk
A Solid State Disk (or SSD) is becoming more popular because of

the price that is dropping and the capacity that is getting bigger and
bigger.
Three basic types of SSD exist:
Single Level Cell or SLC.
e n
/
Multi Level Cell or MLC.

m
Triple Level Cell or TLC.
SSDs:
.c o
use flash technology to store digital information.
e i
w
have no mechanical moving parts internally and therefore use less
power; generate less heat and noise.
u a
.h
However: SSDs have a life span based on the usage of the SSD.
i n g
n
r
// lea
:
Although the traditional mechanical hard disk will not disappear very soon the successor is already
t p
widely available and becoming more popular every day. Solid State Disks or SSDs do not store the
t
:h
information using magnetic properties but store the information within so-called cells. This technology
s
is referred to as flash and it makes it possible to store digital information very quickly and very
e
c
compact. Another big advantage of SSDs is that they do not generate noise and also do not generate
r
ou
a lot of heat compared to traditional hard disks.
es
R
SSDs have no moving parts internally but that does not mean they will last forever. Because of the
n g
internal technology used in flash drives there is what they call a wear process. Every cell has a limited
i
n
number of times the content of the cell can be changed. Once this number has been reached the disk
r
a
cannot guarantee to be used (reads or writes) without errors in the data. This drive wear is however
e
e L
easy to monitor and predict so a replacement disk can be ordered in time. Traditional hard disks often
or fail without any warning which means that replacement disks have to be available at that moment.

SLC MLC - TLC
Every cell in a SSD can store digital information using NAND.
In a SLC.
every cell in a SSD can represent one single bit of information: 0 or 1.
e n
/
In a MLC.
o m
.c
a cell represents two bits of information: 00, 01, 10 or 11.
In a TLC.
e i
a cell represents three bits of information: 000, 001, 010, 011, 100,
aw
u
101, 110 and 111.
g .h
ni n
r
lea
A cell consists of a small transistor-like component called a NAND circuit. Each NAND circuit
//
traditionally could store a single bit of information so a 1 or a 0. The newer generation of SSD
:
drives uses a special technique to store more information in a cell.
t t p
s :h
A MLC or multi-level cell can store 2 bits in a cell and the TLC or triple level cell can store 3 bits per
c e
cell. Two bits of information means that 4 different data patterns can be stored: 00 , 01 , 10 and 11.
r
ou
With three bits the number of data patterns is 8 so more information can be stored in a TLC as the
s
physical size of a cell in a SLC is the same as for a MLC or TLC.
e
R
i n g
That is the reason that the capacity of SSDs has gone up a lot the last couple of generations. The
first SSDs had capacities starting from 64 GB. Now the biggest models TLC can store up to 2.4 TB of
r n
data.
e a
e L
r
However : The different types of SSD drives have different wear patterns. This means that it is
o
important to understand the wear characteristics when a SSD is selected.

Solid State Disk wear
The most important limitation is the number of changes a cell can

have.
Enterprise versions of SLC , MLC and TLC have different values:
Type Capacity Number of P/Es * Price per unit
n
SLC Small About 100,000 High
eMLC Moderate About 30,000 Medium

/ e
cMLC Moderate 5,000 to10,000 Low
o m
TLC Large 500 to 1,000 Very Low
e i .c
* P/Es are the number of changes of the cell.
aw
u
g
Slide 48
.h
ni n
r
lea
The table shows that number of P/Es vary between the SLC, MLC and TLC types. That means that a
//
basic understanding of the application that writes (or reads) data from the SSD is required so the
p :
impact on the wear of the SSD can be determined. So for an application that primarily writes new data
t t
:h
it is best to select a SLC type SSD. Those are much more expensive but the wear of the SLC is much
s
better as it allows 100.000 P/Es compared to the 1000 a TLC allows.
c e
TLS on the other had are very good choices when a SSD should store a lot of data that gets read
r
ou
often for example video files, audio files or even website information. This data does not get changed
s
a lot and will then not wear out the SSD so quickly.
e
R
i n g
Note: eMLC and cMLC are terms to describe different versions of quality of Solid State Disks. The
n
letter e stands for Enterprise (high quality, expensive) where the letter c stands for Consumer (lower
ar
quality, less expensive).
L e
r e
o
M

SSD Introduction
SSD introduction
SSD Hardware Components
SSD Structure Backup power supply
Multi-channel 6 Gbit/s
n
SSD controller SAS interface
Flash concurrency
/ e
m
DDR memory
.c o
Elimination of high-speed rotational component, high
performance, and lower energy consumption.
e i
Multi-channel concurrency.
aw
u
TCQ/NCQ, simultaneous response to multiple I/O
.h
requests.
Average response time less than 0.1 ms.
i n g
n
r
Slide 49
// lea
Native Command Queuing (NCQ) and Tagged Command Queuing (TCQ) technologies again sort
p :
t
the commands sent from a computer to disks, improving disk performance. NCQ technology was
t
:h
introduced in 300 MB/s SATA II disks, tailored for mainstream disks. TCQ technology was introduced
s
in SCSI2 (also in ATA-4) by Compaq, tailored for servers and enterprise-class disks.
e
r c
The same technology was later adapted by most hard disk manufacturers but the name was changed
ou
to be NCQ.
es
R
For a system to support NCQ and TCQ, its disk interfaces as well as disks of the chip group must
n g
support these two technologies. If a motherboard supports NCQ while a disk doesn't, then the
i
r n
technologies are unavailable.
e a
e L
o r
M

Advantages of SSD Performance
Advantages of SSD performance
Short response time. SSD technology advantages
HDDs waste plenty of time in data

seeking and latency, greatly
affecting data transfer efficiency.
I/O
n
I/O
High read/write efficiency. Seek time

IP/FC SAN
/ e
When data is randomly read and
Latency time
o m
i .c
written on an HDD, its head has to
e
keep rotating, leading to inefficient
reading and writing. An SSD uses
its internal controller to locate and
aw
u
directly read data, improving vs
.h
reading and writing efficiency.
Traditional HDD SSD storage
g
storage system system
ni n
r
Slide 50
// lea
Short response time
p :
t t
HDDs waste plenty of time in data seeking and latency, greatly affecting data transfer efficiency.
:h
SSDs eliminate the seek time and latency time as they have no mechanical motion components,
responding fast to read and write requests.
e s
r c
High read/write efficiency
s ou
Re
When data is randomly read and written on an HDD, its head has to keep rotating, leading to
i n g
inefficient reading and writing.
r n
a
An SSD uses its internal controller to locate and directly read data, improving reading and writing
e
e L
efficiency. In a 4k random read/write scenario, a Fibre Channel disk delivers 400/400 IOPS, while a
r
SSD delivers 26,000/5600 IOPS.
o
M

SSD Energy Efficiency and SDD Environment Adaptability Advantage
SSD energy efficiency advantage
Heat distribution 100,000 read IOPS energy consumption
SSD HDD
e n
/
o m
.c
2 SSDs 250 HDDs
Energy consumption (W)
e i
4000
aw
u
Nearly 400x
.h
2000
SSD
i n g FC HDD
r n
//
SSD's energy efficiency advantage over HDD cannot be seen when only a few disks are used.
lea
p :
However, if a large number of disks are used, SSDs consume far less energy than HDDs. This is also
t
a key factor for enterprises to consider when selecting storage solutions.t
s :h
r c e
SDD environment adaptability advantage
ou
SSDs have no rotational component and can
es
withstand severe environment conditions.
For example, HUAWEI SSDs can:
R

i n g
withstand a vibration acceleration of 16.4 G
while HDDs can withstand only 0.5 G
n
acceleration.
ar
e
withstand 1500 G impact while HDDs usually
L
withstand only 70 G.
r e HSSDs have gone through the following
o tests using professional testing equipment:
M Static pressure test, drop test, random

vibration test, impact test and collision test.
SSDs are resistant to harsh environments such as high temperature or humidity and strong vibration.
Some industry-class applications require that SSDs should withstand a temperature ranging from
20C to +70C or 40C to +85C.

SSD Application in Storage
SSD application in storage
Level-A application: features highly concurrent random reads and

writes, such as database applications.
Level-B application: sequential reading and writing of large-size

files, pictures, and stream media.
Level-C application: features backup data or rarely used data.

e n
/
m
Access frequency
SSD media
o
A
.c
Fibre Channel or
i
SAS disk
e
SATA or tape
w
B
u a
C
g .h Data
distribution
ni n
r
Slide 53
// lea
80/20 Principle:
p :
t
Data that is frequently read, written, and changed by users usually accounts for 20% of the total data
t
:h
amount. This type of data is called hot data and corresponds to level-A applications.
e s
Tiered storage:
r c
ou
Hot data is stored on SSDs. Data of level-B and level-C applications is usually stored on high-speed
es
HDDs or general HDDs to improve performance and reduce costs.
R
i n g
r n
e a
e L
or
M

Questions
Questions
1. Name three characteristics of a DAS ICT infrastructure.
2. What is the difference between parallel and serial

communication?
e n
/
3. How many devices can be connected together in a SAS domain?
4. Name the three types of Solid State Disks.
o m
5. Describe what is meant with the term : SSD wear.
e i .c
aw
u
g .h
ni n
r
// lea
p :
Answers
t t
s :h
r c e
1. Block based (SCSI); Islands of Storage ; short distances between components.
2. With parallel communication multiple paths are used simultaneous to transmit data. With
s ou
parallel communication come physical and electrical problems.
e
Serial communication uses a single path to transmit the data sequentially.
R
g
3. Maximum is 16,384 devices in a single SAS domain.
4. SLC; MLC; TLC.
n i n
r
5. The maximum amount of physical changes to the SSD medium before the SSD reports that it
a
e
has to be replaced. It is therefore not really a mechanical wear indicated in days, years or
L
e
months but a number.
o r
M

Exam Preparation
Exam preparation (1)
1. Statements
n
Statement 1: A DAS solution is also referred to as an Island of Storage.
Statement 2: SLC type SSDs are ideal when large amounts of data
/ e
m
need to be stored and read many times.
a. Statement 1 is true ; Statement 2 is true.

.c o
b. Statement 1 is true ; Statement 2 is false.
e i
aw
u
.h
i n g
r n
lea
: //
t t p
Exam preparationh(2)
s :
r c e
u
2. Which of the following disk drive technologies are used in high
o
s
end storage solutions? Select all that apply
a.
ReParallel SCSI.
ing
b. ATA.
rn
c. SAS.
e a d. SSD.
eL
e. PIO.
or
M
Answers
1. The correct answer is: B.
2. The corrects answers are : A, C, D.

Summary
Summary
Direct Attached Storage is not used anymore as the idea of

having islands of storage is no longer popular.
SCSI technology is still used to connect hosts with their physical

disks.
e n
Serial Attached SCSI has replaced the old parallel SCSI /
technology almost completely.
o m
SAS is highly scalable; has a high performance and is relatively
cheap to implement.
e i .c
aw
u
g .h
ni n
r
// lea
p :
t
In the previous chapter we have seen the development of disk technology (parallel SCSI, SATA, SAS)
t
:h
as the interface between hosts, and their applications, with the physical hard disks that hold the user
s
data.
r c e
ou
DAS systems have a limitation in the fact that all data is private to the host. Sharing was/is not easy
s
between islands of storage. So the evolution of ICT infrastructures led to the next step: Network
e
Attached Storage.
R
i n g
n
Goals for Network Attached Storage solutions are:
-
ar
to eliminate the islands of storage.
-
L e
to allow people to share disk space.
-
r eto allow people to share data with other hosts and their applications.
o
M

e n
Thank you /
o m
www.huawei.com
e i .c
aw
u
g .h
ni n
r
// lea
p :
t t
s :h
r c e
s ou
Re
i n g
r n
e a
e L
or
M

e n
/
o m
e i .c
aw
u
g .h
ni n
r
// lea
p :
t t
s:h
r c e
sou
Re
i n g
r n
e a
e L
o r
M

e n
/
OHC1109103 o m
NAS Technology e i .c
aw
u
g .h
ni n
r
lea
www.huawei.com
: //
t t p
s:h
r c e
sou
Re
i n g
r n
e a
e L
or
M
e n
/
o m
e i .c
aw
u
g .h
ni n
r
// lea
p :
t t
s:h
r c e
sou
Re
i n g
r n
e a
e L
or
M
Introduction
In this module we will look at the second of the possible ICT infrastructures: NAS or in full Network
Attached Storage.
Objectives
After completing this module you will be able to:
e n
/
m
Know the NAS structure and implementation.
Master NAS file sharing protocols, NFS and CIFS.

.c o
e i
w
Understand the I/Os and performance of a NAS system.
Understand the differences and relationship between SAN and NAS.

u a
Understand Huawei NAS products.
g .h
ni n
r
Module Contents
// lea
p :
1. Characteristics of a NAS ICT infrastructure.
t t
:h
2. NAS network topology.
3. Network protocols CIFS and NFS.
e s
r c
ou
4. Ethernet Standard.
s
5. Ethernet Cables.
10-BASE5.
Re

10-BASE2.
10-BASE-T.
i n g

r n
a
Crossover and straight cables.
L e
6. Ethernet Frame.
r e
o
M
HCNA-storage V3 | OHC1109103 NAS Technology Page | 91

e n
/
o m
e i .c
aw
u
g .h
ni n
r
// lea
p :
t t
s:h
r c e
sou
Re
i n g
r n
e a
e L
or
M
Page | 92 HCNA-storage V3 | OHC1109103 NAS Technology

OS=Windows OS=Linux OS=MAC OS
1. Network is based on Ethernet.

2. With Gigabit Ethernet and CAT 6 cables: max = 100 m.
e n
/
3. Shared folders are created on the NAS server for
individual users.
4. Files are moved across the network.
o m
.c
5. Hosts can run different operating systems.
i
6. Different protocols are used such as CIFS and NFS.
we
u a
With Direct Attached Storage (or DAS) there are a few problems and limitations.
g .h
ni n
r
The lack of scalability and the fact that you cannot share data between the DAS islands of storage are
lea
the biggest problems. With the introduction of Network Attached Storage these problems have been
//
solved. Now it is possible to build an infrastructure that uses Ethernet networking technology to
p :
connect multiple workstations (that is where the applications run that need or create the data) to the
t t
:h
actual place where the data is now centrally stored.
e s
Important difference with DAS technology is the shape in which data is moved between the application
r c
running on a workstation and the physical disk.
s ou
e
With DAS the data was transmitted as SCSI blocks with a size of 512 bytes. For the transmission all
R
actions in the SCSI protocol, discussed in the previous module, were required.
i n g
n
Network Attached Storage (or NAS) solutions work differently. If you would be able to look inside of
ar
the network cables you would see entire files being moved across the network. In the beginning when
L e
the speed of the Ethernet technology was rather limited it took a lot of time to move for instance a file
r e
of two GB across the network. NAS solutions were not very popular then, but now the speed of the
o
Ethernet network is 1 or even 10 Gb/s and NAS infrastructures have been proven to be very fast as
Mwell.

What still remains is the scalability of NAS infrastructures. As the medium across which we
transport the files is mostly a copper-based Ethernet cable (we use an indication like CAT 5E or CAT6
to indicate the quality of an Ethernet cable) there are limits to the length of an individual Ethernet cable.
That in itself does not mean that NAS infrastructures are bound to the length of a single cable. There
is of course the option to connect multiple cables using switches/repeaters to span greater distances.
However, it takes time for switches/repeaters to receive the signal and retransmit it again. So the more
switches/repeaters are used (in other words, the longer the distance between the various components
of a NAS infrastructure) the longer it will take for the signal to be physically transmitted. That can then
be translated in a rather slow connection/transmission.
e n
/
o
Ethernet itself is a standard which is officially called IEEE 802.3 and it describes hardware as well as
m
software specifications.
e i .c
Note:
aw
u
.h
Throughout this course the speeds of a transmission will be indicated in Gb/s or Gbit/s. In both cases it
g
ni n
refers to a transmission speed of 1 gigabit per second or 1,000,000,000 bits per second.
r
lea
In upcoming slides a few of the most important specifications of Ethernet will be discussed.
: //
t t p
:h
Note:
e s
IEEE is the name of the committee that has set up the specifications for many technologies among
r c
ou
which the Ethernet standard. The full title of the committee is the Institute of Electrical and
s
Electronics Engineers.
Re
i n g
r n
e a
e L
or
M

NAS Network Topology
NAS network topology

Windows clients Unix/Linux clients
CIFS NFS
e n
/
m
Windows
share
o
Unix/Linux
Windows server share Unix/Linux Server
.c
NAS server
e i
w
u a
The picture shows a modern NAS solution where the device identified with NAS is the most important
g .h
component. The NAS device is connected via a network switch with multiple servers and/or client
ni n
systems (sometimes also referred to as workstations).
r
// lea
:
The workstations and servers can run different operating systems and they all run their specific
p
t t
applications. The data that these applications generate is stored on the hard disk(s) that are inside of
:h
the NAS device.
e s
c
In the past the network technology to connect the workstations with the NAS device could be
r
ou
something like Token Ring, FDDI or ArcNet. As Ethernet has become the most popular network
s
connection mode, we will only discuss the NAS environments that are based on Ethernet.
e
R
g
As discussed before the NAS device transports entire files across the network to and from the
i n
workstations/servers. As workstations optional run different operating systems there is a need for the
n
r
NAS device to understand how each operating systems handles the transport of a file. Reason of
a
e
course is that a Windows based host uses a different method to find and access a file that is stored
L
e
externally than a Linux\Unix based host. The way an operating system accesses a file that is stored on
or
a network connected device is called a protocol.

Protocols are used within operating systems to access a file which is not physically located inside a
host but are only accessible via the network interfaces over an Ethernet based network.
Operating system Protocol.
Windows SMB (Server Message Block), CIFS (Common Internet File System).
n
Linux/Unix NFS (Network File System).
/ e
o m
.c
Apple AppleTalk (older Apple MAC OS-es), NFS.
e i
Novell NCP (Novell Control Protocol).
aw
u
g .h
ni n
r
lea
The goal in Network Attached Storage solutions is to allow file sharing. With File sharing computer
//
data (or space) is shared (public or private) in a network with various levels of access privileges. Of
:
course there are other ways to share a file with someone (for example, simply by handing someone
p
t t
your file on a usb stick or mailing the file), the term file sharing almost always means sharing files in a
:h
networking environment, even in a small local area network. File sharing allows a number of people to
e s
use the same file (or multiple files in a folder) by some combination of being able to read or view it,
r c
write to or modify it, copy it or print it.
s ou
e
There are two possible implementations of NAS: Integrated NAS and NAS gateway.
R
i n g
The next slides will discuss the differences between them.
r n
e a
e L
o r
M

NAS implementation: Integrated NAS
NAS implementation: Integrated NAS
IP
e n
/
Example: Huawei OceanStor V3.
o m
.c
NetApp FAS series.
e i
aw
u
The Integrated NAS is the last stage of the evolution of NAS. In the older version called NAS
g .h
gateway an extra device is used for NAS functionalities.
ni n
r
In the integrated NAS everything needed is collected in one single device. It has the options to store
// lea
:
data on hard disk and handle the request of all the clients computers that want to write (or read) the
p
files on the NAS.
t t
s :h
Some examples of solutions of Integrated NAS are Huaweis OceanStor V3 series storage and
NetApps FAS series.
r c e
s ou
Re
i n g
r n
e a
e L
or
M

NAS implementation: NAS gateway
NAS implementation: NAS gateway
NAS gateway
IP FC
e n
/
Storage Array
o m
.c
Example: Huawei N8500.
NetApp FAS 8000.
e i
aw
u
The picture clearly shows that a NAS gateway is a device that links the client computers (left) with the
g .h
actual storage array where the data is stored. The storage arrays are then block based and the NAS
ni n
r
lea
gateway converts the data from bits and bytes into files (and vice versa). The NAS gateway is a
//
dedicated solution that has connections with both the IP network as well as the FC network.
p :
t t
:h
NAS Architecture
e s NETWORK FILE SYSTEM
c
NFS and CIFS
r
s ou FILE SYSTEM
Re
ing
OPERATING SYSTEM
arn
e
NAS HARDWARE
e L
r
o
MThis image show the NAS architecture or in other words: the software structure for a NAS device.

What is CIFS?
What is CIFS?
Common Internet File System (CIFS).
A protocol that enables application programs to access files and
services on a remote Internet computer.
Transmission protocol used is TCP/IP.
TCP (Transmission Control Protocol).

Part of the TCP/IP protocol that takes care that packets are send
n
in the right order. It is also responsible for the error-checking part.
IP (Internet Protocol).
/ e
Responsible for the actual delivering of the packets to the
receiving system. To find that receiving system it uses the IP
o m
.c
address of the receiver.
e i
w
u a
The name CIFS itself is not really accurate. The real name is SMB v2 (and later v3). SMB or Server
g .h
Message Blocks was used for a couple of reasons and one was to access files which were on another
ni n
Windows based host connected to the same network.
r
// lea
CIFS uses the client/server model and is dedicated to file sharing in the Windows environment. A
p :
t t
client sends a request to a remote server, asking for services and the server responds to the request.
:h
A NAS system uses the CIFS file system to share storage resources with Windows servers. In a NAS
s
system it is very important that we not only store our data centrally but also there should be the
e
r c
possibility to have more hosts access the same data simultaneously. In the common language the
ou
name File Server is also used to describe the functions of NAS devices. In many organizations the
es
concepts of sharing data is then described as: our data is stored on a public folder on the fileserver.
R
i n g
Public folders, or better shared folders, are then used to store data that has to be accessible for
n
several users. In practice a company creates multiple shared folders and it uses methods within the
ar
operating system to allow only certain users to access certain folders.
L e
e
It is even possible to organize things in such a way that some users can only see the files and use
or
them (Read-Only permission) where others have the possibility to change the contents of a file (Read-
MWrite permission). These options to set permission levels (Read-Only \ Read-Write) can be set on
individual files or on folders or subdirectories that hold many, many files.
Also: both Linux as well as Windows have the options to assign these permissions to individual users
(or even groups of users).
What is NFS?

What is NFS?
Network File System (NFS).

A technology for sharing files among UNIX systems. It allows data to
be stored on central servers and easily accessed from clients over a
network.
Originally developed by Sun Microsystems in 1984.
Based on the Open Network Computing Remote Procedure Call

system. This is an open standard allowing anyone to implement it.
e n
/
o m
e i .c
aw
u
Although most of the servers in professional data centers run the Microsoft operating system there are
also quite a few companies that use the open source Linux operating systems. Nobody can really
g .h
state to be the actual owner of the Linux operating system because the open source concepts means
ni n
r
that everybody can get the software for free and use (or adapt) it freely. That has led to a number of
lea
different versions of the Linux operating system.
Examples of Linux versions or Linux distributions are Red Hat, SuSe, Ubuntu and CentOS. A good
: //
t t p
thing with all these Linux versions, and also with similar operating systems like Unix and Mac OS X, is
:h
that they all use the same foundation. In that foundation, also referred to as the kernel, the protocol to
e s
access remote files is present: NFS. With NFS or Network File System a Linux\Unix based host can
access a remote file via the network.
r c
s ou
The NFS protocol was originally developed by SUN Microsystems in 1984, allowing directories and
Re
files to be shared among systems, even if they are running different distributions. Through the NFS,
i n g
users and programs can access files on a remote system just like they would when accessing local
n
files. The NFS enables each computer to utilize network resources as conveniently as local resources,
ar
that is to say, NFS allows file access and sharing among heterogeneous computers, operating
L e
systems, network architectures, and transmission protocols.
r e
o
M

NFS also uses the client/server model and involves a client program and a server program. The server
program allows other computers to access the shared file system, and the result of the process is
called "output". The client program accesses the shared file system, and result of the process is called
"input". Files are transmitted in blocks (a block = 8 KB). Operations may be divided into fragments of
a smaller size. The NFS enables file access and sharing among servers and clients, and allows clients
to access data saved on remote storage devices.
In the past it was very common to have only Windows based hosts interconnected on a network or
e n
Linux\Unix based hosts. A combination of the two was virtually impossible as the protocols CIFS and
/
NFS are not compatible as they run on different operating systems.
o m
e i
Long before the first real NAS solutions were made there was a project called SAMBA that was .c
w
intended to allow a Windows based host to transport files to and from a Unix\Linux based host.
a
u
SAMBA is basically a project where tools were developed for a Windows host (NFS client software) to
.h
transfer files to a Unix\Linux host. Of course the reverse option was/is also available: tools exist for
g
i n
Unix\Linux hosts (Samba is one of them) to perform CIFS actions. Today a NAS device has both
n
r
protocols on board. The SAMBA project itself still exists. For more information on SAMBA please
lea
visit http://www.samba.org.
: //
t t p
s :h
r c e
s ou
Re
i n g
r n
e a
e L
or
M

Comparison between CIFS and NFS
Comparison between CIFS and NFS

If a file system is already set to:
a CIFS share, the file system can only be set to a read-only NFS share
additionally.
an NFS share, the file system can only be set to a read-only CIFS share
additionally.
Supported
n
Transmission
Protocol Client Fault Impact Efficiency Operating
Protocol
Systems
CIFS TCP/IP
Integrated operating
system without the need Large High Windows
/ e
m
for additional software.
o
Small: The interaction
Requires additional
.c
NFS TCP or UDP process can be auto- Low Unix
software.
matically resumed.
e i
w
u a
CIFS is a network-based sharing protocol. It has high demands on network transmission reliability,
g .h
so it usually uses TCP/IP. NFS is used for independent transmission, so it uses TCP or UDP.
ni n
r
lea
One disadvantage of NFS is that clients must be equipped with dedicated software. CIFS is
integrated into the operating system and requires no extra software.
: //

t t p
NFS is a stateless protocol while CIFS is a stateful protocol. NFS can be automatically recovered
:h
from a fault while CIFS cannot. CIFS transmits only a little redundant information, so it has a
s
higher transmission efficiency than NFS.
r c e
ou
Both protocols require file format conversion.
es
R
i n g
From the picture above it becomes clear that a folder or volume can be accessed by users from
r n
a
different systems as there can be a CIFS and a NFS share created to access the files.
L e
However: looking at the restrictions that can be applied there is a limitation. Once a CIFS folder is
r e
o
assigned a read-write permission; the NFS permissions can only be read-only!
MSimilarly: when an NFS read-write permission is assigned the additional CIFS permission will be read-
only.

Accessing files on a NAS
We already discussed the fact that the files on a NAS device can be written to, or read from, client
computers that run different operating systems. In the next image we show an image of how a
Windows based client can create a so-called network mapping in Windows 2008/7/8/2012. Once this
mapping is created the user in Windows can see all the files on the share that is created on the NAS
device.
Accessing files on a NAS
Steps to host a file system:
e n
Create a LUN.
/
Map LUN to
o m
.c
the NAS device.
Create a file system

on the LUN.
e i
Mount the file system.
aw
Access the file system.
u
Use NFS in UNIX environment.
Execute mount/nfsmount command.
g .h
Use CIFS in windows environment.
Map the network drive as: \\ACCOUNT1\ACT_REP.
ni n
r
lea
: //
Also in the image is the reference to the procedure for Linux-based clients that use NFS. There the
procedure consists of a few actions.
t t p
:h
The most important one is shown: the MOUNT/NFSMOUNT command
e s
r c
s ou
Re
i n g
r n
e a
e L
or
M

Ethernet Standard
Ethernet Standard
The IEEE 802.3 standard from the Institute of Electrical and
Electronics. Engineers describes concepts and hardware (cabling,
connectors) of Ethernet.
Ethernet was defined in 1983 and over the years it has replaced
alternatives like Token Ring ; FDDI and ArcNet.
Ethernet (and all its variations) have been standardized in many

IEEE802.3 sub-definitions.
e n
Examples: 802.3a (100 Mb/s).
/
m
802.3ab (Gigabit Ethernet).
o
802.3at Power-over-Ethernet.
Concept of Ethernet is a technology called CSMA/CD or Carrier

Sense Multiple Access with Collision Detection.
e i .c
aw
u
The IEEE 802.3 standard is a working group standard which means that there will be changes,
g .h
updates and improvements constantly. IEEE 802.3 is therefore never finished. It was primarily created
ni n
r
lea
to document and standardize methods that can be used in local area networks. Because of all the
//
improvements and additions over the last 30 years we now have a large number (more than 30) of
IEEE 802.3 standards.
p :
t t
s :h
Here are a just few of them:
r c e
IEEE number Year
s ou
Description
802.3 1983
Re 10BASE-5 with thick coax.
802.3i
i n g
1990 10BASE-T with twisted pair.
r n
a
802.3u 1995 100BASE-T also known as Fast Ethernet.
e
eL
802.3ab 1999 1000BASE-T Gigabit Ethernet with twisted pair.
or
802.3bq ~2016 40GBASE-T Planned 40 Gigabit Ethernet with twisted pair.
MOn top of all these versions of the 802.3 standards different physical versions of each standard can
exist. Again as an example some versions of the 802.3ab standard are shown in the next table.

Name Medium Specified distance
1000BASE-CX Shielded balances copper cable. 25 meters.
1000BASE-KX Copper backplane. 1 meter.
1000BASE-LX Multi-mode fiber. 550 meters.
1000BASE-EX Single-mode fiber at 1,310 nm wavelength. ~ 40 km.
1000BASE-TX Twisted-pair cabling (Cat-6, Cat-7). 100 meters.
e n
/
m
All Ethernet based networks have a bus structure where multiple devices (hosts; switches; storage
.c o
arrays) can access the bus to transport information. Just like with the SCSI protocol something has to
e i
be arranged to prevent a device interfering with other devices on the network. The solution for
Ethernet is CSMA/CD.
aw
u
g .h
ni n
r
// lea
p :
t t
s :h
r c e
s ou
Re
i n g
r n
e a
e L
or
M

CSMA / CD
CSMA / CD
START
Channel
Free?
No
Yes
Transmit Data WAIT
e n
/
Collission
detected?
m
Yes
No
Transmission
.c o
i
complete
we
u a
The above picture shows that a wait period is started as soon as a collision is detected. This waiting
g .h
period is generated random so with CSMA\CD a device does not know the waiting period he will get
ni n
when a collision happens. No priority system therefore can be used to make one device wait longer (or
r
lea
shorter). It is just a matter of waiting and trying again before a device can communicate in a very busy
: //
Ethernet network. Especially in situations where the Ethernet speed was still low (10 or 100 MB/s) it
t p
might take a few minutes before lets says 30 booting devices managed to connect to the network
t
:h
successfully.
e s
r c
ou
The actual CSMA/CD process is a two steps approach:
s
1. Main procedure
Re
-
n g
Is my frame ready for transmission? If yes, it goes on to the next point?
i
-
r n
Is medium idle? If not, wait until it becomes ready.
-
e a
Start transmitting.
eL
- Did a collision occur? If so, go to collision detected procedure.
or
- Reset retransmission counters and end frame transmission.
M2. Collision detected procedure

- Continue transmission (with a jam signal instead of frame header/data/CRC) until minimum
packet time is reached to ensure that all receivers detect the collision.
- Increment retransmission counter.

- Was the maximum number of transmission attempts reached? If so:
Abort transmission.
Calculate and wait random back off period based on number of collisions.
Re-enter main procedure at stage 1.
What this means is that there will be collisions when two devices send packets at the same time. In
this respect it looks like the problems the SCSI protocol had when multiple devices started transmitting
over the SCSI bus. With SCSI we used the SCSI ID for priority. Here with CSMA/CD each device,
when it detects a collision, uses a random calculated number to indicate the waiting period (or back off
e n
/
m
time) before trying again. So eventually an Ethernet based systems will allow, with optionally a few
collisions included, more than one device to send/receive Ethernet packets over a shared medium.
.c o
e i
aw
u
g .h
CSMA / CD: Principle
ni n
r
lea
CSMA/CD : Principle
: //
D
t t p
:h
E
e s
r c
s ou A
e
Sending
R
B device
g
C
n i n Copyright 2015 Huawei Technologies., Ltd. All rights reserved. Slide 15
ar
L e
When a device sends a packet it will be dropped onto the network. On every intersection the signal will
r e
propagate in all possible directions. So a packet send from device A will be delivered in the network
o
interface of all other devices. Inside of the packet is the information of who did send the packet and to
Mwhich device the packet should go. This addressing information is present in each packet and is part
of the overhead needed to transmit packets.

At the start of a transmission two situations can exist:
1. The network is already moving packets from another device. A that point the device that wants
to send must wait. It uses a system called CARRIER SENSE to find out that the network is
already busy.
2. The network is free. Now the first packets can be sent.
However : it is impossible to have two devices sending packets at the same time as the signals would
collide on the network which would mean that the signal will be distorted. So if two devices have
e n
/
m
checked the status of the network and both found that nobody is using the network they both think
they can go on to the transmission stage.
.c o
Therefore we must investigate how to detect these collisions first. Then the next question would be e i
how to allow multiple devices to communicate across the network.
aw
u
g .h
CSMA/CD: Collision Detection
ni n
r
CSMA/CD : Collision Detection
// lea
p :
t t
s :h
r c e
s ou
Re
i n g
r n
a
L e
r e
As soon as a device notices a collision it stops transmitting any further. A collision is detected because
o
the original signal that was sent is damaged because of the collision. This can be detected by each
Mdevice. Each device involved in the collision will then use a random number generator to calculate a
waiting period. Typically each device will have a different waiting time now. After that waiting period a
device will start sending packets again to find out if the network is free. So the one with the lowest
number of seconds to wait will win the access to the network!

Ethernet Cable 10-BASE5
Original Ethernet was called 10-BASE5.

Cable length was a type of COAX cable with a length of up to 500m.
e n
/
m
A transceiver module was clamped onto the cable to be able to
o
connect a host to the transceiver module.
10-Base5 was also known as Thick Ethernet.
e i .c
w
u a
The first implementation of Ethernet was called 10-Base5 which was also known as thick Ethernet.
g .h
The cable was of the type COAX which means there is a central copper wire within a plastic core.
ni n
r
lea
Around that a meshed shield is placed which should protect the inner copper wire from being
//
influenced by external distorting signals. Next another plastic cover was placed over the mesh. A coax
p
cable is built to be a Faradays cage. The 10-Base5 cable was around 1 cm thick and a 500 meter:
t t
:h
long cable is therefore very heavy. This created the nickname thick Ethernet.
e s
To connect a device to the thick Ethernet cable a transceiver module was clamped onto the cable.
r c
Inside the module a screw was screwed right through the outer mantle; the mesh; the plastic core so it
would touch the core wire.
s ou
Re
Thick Ethernet was rather bulky and the cables were difficult to maneuver.
i n g
r n
e a
e L
or
M

10-BASE2 is the successor of 10-BASE5.

Cable length was up to 100m and the cable itself was much thinner!
e n
T-shaped BNC connectors were used to make connections to hosts.
/
The number in front of BASE indicates the transmission speeds in
o m
.c
Mb/s.
e i
w
u a
With the design of 10-Base2 the cables became much thinner and easier to handle. The cable length
g .h
was decreased to 100 meters as the changed physical dimensions meant that shielding was less
ni n
optimal.
r
The system of clamping connection modules to the cable was also abandoned as it was a precise task
// lea
p
to do that with 10-Base5. Every device now was connected to the cable using t-shaped joins so the:
t t
:h
cable end itself was also fitted with a connector. The connectors used were BNC connectors or
s
Bayonet Neil-Concelman.
r c e
Same as with SCSI busses a Ethernet network has to be terminated. For that purpose a plug with
ou
BNC connection with a build in resistor was connected at the cables end.
s
Re
i n g
r n
e a
e L
or
M

Ethernet Cables UTP & STP
Ethernet Cables UTP & STP
Nowadays the cables used to connect Ethernet based devices are

based on 10-Based T. The T means Twisted Pair.
Two versions exist: Unshielded and Shielded.
e n
/
o m
.c
Unshielded Twisted Pair Shielded Twisted Pair
Twisted Pair cables are intertwined and that results in

e i
the fact that distortions are compensated
aw
10-Based T cables use a 8P8C connector but we
u
.h
usually call them a RJ-45 connector.
i n g
n
r
// lea
:
A big improvement was the invention of 10-BaseT internet cables. This is the type we still use today. It
t p
is no longer like a coax cable but they use another technology to eliminate the effect of external
t
:h
signals. The method used is called Twisted Pair cabling and the T in 10-BaseT is what indicates the
twisted pair technology.
e s
r c
ou
Because of the twisting of the two wires that carry the signal the effect of external signals is
s
compensated to a high degree. There is an even better version of this Twisted Pair cable : In a
e
R
Shielded Twisted Pair (STP) cable there is a very thin metal foil around every pair of twisted cables.
i n g
So the original twisted pair cables that do not have this extra shielding are now referred to as
Unshielded Twisted Pair (UTP).
r n
e a
The connectors used are the familiar cables we see in switches, servers and laptops and we use the
L
name RJ-45 for them. However the name RJ-45 (Registered Jack) is not the official name. That is
e
or
8P8C which is short for : 8 Position 8 Contact.

Ethernet Cable Wiring
Ethernet Cable Wiring
Ethernet cables are available in straigth cables and crossover cables.
straight
e n
crossover
/
o m
e i .c
w
u a
To properly work, Ethernet networks need four separate wires to send data across. For a twisted pair
g .h
cable that would mean eight copper wires per cable. Each of the four wires has a color to identify them.
ni n
Green, Orange, Blue, Brown.
r
// lea
The second wire that they are twisted with, also have specific colors: green-white, orange-white, blue-
white, brown-white.
p :
t t
:h
Depending on the usage of the cable we can identify a straight or a crossover cable. The above
s
r c e
diagram shows the pin number within a RJ-45 connector of each color wire.
ou
A crossover cable is typically used when two PCs or servers are directly interconnected with a direct
es
cable plugged into the RJ45 network ports.
R
i n g
Straight cables are used to connect hosts or servers to switches. Today using the wrong cable is not
n
really providing problems as most switch ports are designed in such a way that both straight as well as
ar
crossover cables can be used. The switch port will auto-detect the cable type and adjust internally to
L e
make the correct connection.
r e
o
M

Ethernet Basics Frame size
Ethernet Basics Frame size
Ethernet sends socalled frames over the network.

Preamble
Ethertype
DMA
SMA
SFD
FCS
PAYLOAD
e n
7 bytes 1 bytes 6 bytes 6 bytes 2 bytes 46 - 1500 bytes 4 bytes
/
o m
.c
SFD = Start of Frame Delimiter.
i
DMA = Destination MAC Address.
e
SMA = Source MAC Address.
w
FCS = Frame Check Sequence.
Ethernet packets vary in size from 1500 bytes up to 9000 bytes

u a
.h
(Jumbo frames).
i n g
n
r
// lea
:
Ethernet was developed in the 1970s at Xerox in the United States and made into the IEEE 802.3
t p
standard in 1983. Ethernet became popular and was commercially used in the 1980s. With Ethernet
t
:h
networks the actual information sent is a predefined set of bits and bytes. This is officially referred to
s
as a datagram but when we talk about Ethernet we often use the term PACKET or FRAME to identify
e
r c
the individual packets of information that get sent across the network.
s ou
Ethernet frames were designed to be around 1500 bytes in size. Inside of a frame we have a portion
Re
of user defined data (the data the user wants to send to another device) also called the payload.
i n g
However we need more information to be able to bring the frame to the correct destination. This extra
information is the overhead involved with Ethernet (and any other networking protocol). Information
r n
a
needed is: who is sending the frame, where is it going to, error correcting information, etc. This
L e
overhead is also called heading and trailing information as, seen in the above image, some of the
e
extra information is send before the payload data (heading information) and some is send after the
r
o
payload is sent (trailing information).
MTo be more efficient (ration between payload and overhead) a new frame size was developed. In a so-
called JUMBO frame they have increased the frame size to be around 9000 bytes. The overhead is
still the same but now the payload is roughly 6 times bigger!

Ethernet Networking Components
Ethernet Networking Components

Ethernet cards in hosts.
Switches to interconnect hosts
n
with the NAS device using certified
e
cables.
/
o m
.c
NAS server.
e i
w
u a
To make a NAS based ICT infrastructure we need three main components:
g .h
ni n
r
1. Hosts\servers\workstations with network interfaces.
lea
2. Ethernet switches.
3. NAS capable devices or NAS servers.
: //
t t p
Important in the setup of a NAS solution is the physical distance between the various components and
the cable types used to connect them.
s :h
r c e
The cables can be both copper-based as well as fiber optic-based although in practice the copper-
ou
based version is used predominantly. Then the quality aspect of the cable is the next thing to watch.
es
Copper-based cables used for Ethernet networks are classified with the letters CAT followed by a
R
number. Generally a cable with CAT 5 is meant to be used with 100 Mb/s transmissions only. The
n g
improved CAT5e is also supported for 1000 Mb/s (also referred to as Gigabit) transmissions. However
i
r n
it would be better in the last situation to use CAT 6 qualified cables as they were specifically designed
e a
for 1000 Mb/s transmissions.
e L
or
M

Questions
Questions
1. What is NAS?
2. What is a share?
3. What is a collision?
4. What are scenarios where NFS and CIFS can be applied?
5. What does STP mean?
e n
/
o m
e i .c
w
u a
Answers
g .h
1. Network Attached Storage where all devices (servers; storage devices; backup devices) are
ni n
interconnected with Ethernet based switches and cables.
r
lea
2. A share is a storage capacity allocated on a NAS server. Shares are accessible for one or
//
more hosts via the network.
p :
3. A collision occurs when multiple servers try to access the network. At that point the signals
t t
broadcast by the servers will collide and the signals will be distorted leading to failed
:h
communication.
s
4. NFS shares are set up in such a way that Linux based servers can use shares on the NAS
servers.
r c e
server. CIFS is the method used with Windows based servers to access shares on NAS
ou
5. STP is short for Shielded Twisted Pair. This is the most common cable type used in Ethernet
s
networks. It provides good specifications and can be used in high speed configurations.
e
R
i n g
r n
e a
e L
or
M

Exam Preparation
Exam Preparation (1)
1. Which of the following are NAS components? ( Select all that apply)
a. Storage.
b. Network.
c. Engine.
d. Server.
2. What best describes the characteristics of a NAS solution?
e n
a. Centralized storage; Operating System dependent; Campus.
/
b. Share folders; Multiple operating systems; Campus.
c. Centralized storage; Multiple protocols; Global.
o m
.c
d. Share folders ; Single protocol ; Global.
e i
w
u a
g .h
Exam Preparation (2)
ni n
r
lea
3. Statement 1 : IEEE802.3 is a collection of standards that describe
//
many generations of Ethernet versions.
Statement 2 : CSMA/CD gives the IEEE standard no options to
p
give a higher priority to a specific device on the
:
network.
t t
:h
a. Statement 1 is true ; Statement 2 is true.
e s b. Statement 1 is true ; Statement 2 is false.
c
r
ou
es
R
Answers:
i n g
r n
a
1. A, B and D.
2. B.
L
3. A. e
r e
o
M

Summary
Summary
NAS structure and implementation.
NAS file sharing protocols, NFS and CIFS.
Cabling and connectors.
NAS limitations.
Ethernet standards.
e n
/
o m
e i .c
w
u a
g .h
ni n
r
Network Attached Storage infrastructures are very useful where the distance is not too big between
lea
workstations; switches and NAS servers.
: //
p
When the distance is increased to many kilometers the limited length of each individual cable
t t
becomes a performance bottleneck. The signal has to be retransmitted and that takes time! Although it
:h
is possible to use optical cable links between two components in a NAS infrastructure we see that
s
r c e
copper is mostly used. That is why the scale of a NAS solution is often limited to campus style
environments where the distances are a couple of hundred meters.
s ou
Re
i n g
r n
e a
e L
or
M

Thank you
www.huawei.com
e n
/
o m
e i .c
aw
u
g .h
ni n
r
// lea
p :
t t
s :h
r c e
s ou
Re
i n g
r n
e a
e L
or
M

e n
/
OHC1109104 o m
e i .c
SAN Technology
aw
u
g .h
ni n
r
lea
www.huawei.com
: //
t t p
s:h
r c e
sou
Re
i n g
r n
e a
e L
or
M
e n
/
o m
e i .c
aw
u
g .h
ni n
r
// lea
p :
t t
s:h
r c e
sou
Re
i n g
r n
e a
e L
or
M
e n
/
o m
e i .c
aw
u
g .h
ni n
r
// lea
p :
t t
s:h
r c e
sou
Re
i n g
r n
e a
e L
or
M
Introduction
This is the chapter that will discuss the third of the ICT infrastructure types that can be used. It is
this Storage Area Network solution, or short SAN, that today is used in almost all companies. It
has many advantaged over the previous two DAS and NAS. We will also use this chapter to
introduce the Fibre Channel protocol as well as the fiber optic technology that is used in SAN
solutions a lot.
e n
/
Objectives
o m
e i .c
w
Identify the main components of a SAN.
u a
Describe the concepts of a SAN.
g .h
Explain how a SAN is designed.
ni n
Explain what the multipathing problem is.
r
lea
Describe how a Fibre Channel frame looks like.
Understand how optical fibers work.
: //
t p
Describe the role of zones in a Fibre Channel network.
t
:h
Identify the topologies used in a Fibre Channel network.
e s
Describe the differences between FC and IP SAN.
r c
Identify the networking components in a host.
s ou
Re
i
Module Contents n g
r n
e a
L
1. The ideal ICT infrastructure.
r e 2. Concepts of SAN design.
o 3. The multipathing problem.
M 4. The Fibre Channel protocol and FC frames.

5. Components of a SAN.
Server.
Switch.
Storage device.
Host Bus Adapter.
Transceiver.
HCNA-storage V3 | OHC1109104 SAN Technology Page | 121

6. Principles of fiber optics.
7. FC switches.
Concept of World Wide Name.
FC port types.
Zoning concepts.
Configuration.
8. Concepts of FC fabrics.
9. Concepts of IP SANs.
10. Network interfaces in hosts in IP SANs.
e n
/
m
Network Interface Connector.
TOE card.
.c o
iSCSI HBA.
e i
11. Converging networks.
aw
u
g .h
ni n
r
// lea
p :
t t
s :h
r c e
s ou
Re
i n g
r n
e a
e L
or
M
Page | 122 HCNA-storage V3 | OHC1109104 SAN Technology

The Ideal ICT Infrastructure
The ideal ICT infrastructure
Is scalable in capacity.
Can be stretched across the entire world.
e n
/
m
Is very reliable.
.c o
e i
Offers the highest possible transmission speeds.
aw
Is easy to manage and flexible.
u
Is heterogeneous.
g .h
ni n
r
lea
: //
t t p
In organizations like Huawei, with more than 100,000 employees worldwide, the design of the ICT
:h
infrastructure becomes very complex. People working from The Netherlands Office of Huawei
e s
should be able to access relevant data that is stored on a storage device in Huaweis head office
in Shenzhen.
r c
s ou
Re
For this infrastructure to work well a design has to be made that will last for many years to come.
When a huge design is needed there is also a list of requirements for the design.
i n g
r n
1. The design must be in such a way that it can be expanded indefinitely. There must
e aalways be the possibility to grow the number of devices.
e L
or 2. The design must allow the distance between the individual components to be unlimited.
M
In practice that means 20,000 kilometers which allows a device to be on the other side of
the globe.
3. The design must be reliable and resilient. This means that the design architect must
realize that sometimes hardware fails or people make mistakes. Still when that happens it
should not lead to serious problems for the organization.
4. The components connected to each other must be able to communicate at the highest
possible speeds available.

5. Even when the design becomes very complex it should be able to do maintenance and
monitoring with a limited amount of ICT staff. You can imagine that an ICT department
should not need fifty people to manage fifty or even a hundred devices. Cost
effectiveness for management is also a big design requirement.
6. The design should be flexible. That means that it must be possible to change; replace;
add components to the infrastructure without any limits. That means that if technology
improves over years the new technology can be integrated in the current infrastructure.
e n
/
m
7. By design an ICT infrastructure should be heterogeneous. Heterogeneous means that
devices from different vendors should be working together just as well as devices that all
.c o
e i
come from one vendor. This is at this point not often the case but that has a reason that is
w
mostly non-technical. Huawei devices like servers, switches and storage devices will work
a
u
well with most other vendors equipment. However most customers of Huawei will buy
.h
only Huaweis products. The reason is often that customers want to have a service
g
n
contract with one supplier of the hardware. That prevents them to contact multiple support
ni
r
teams of multiple vendors in case of a technical problem. Practice has shown that
lea
sometimes vendors will blame the other vendor when a problem occurs.
: //
t t p
A Storage Area Networks or SAN can deliver on all the points from the wish list we saw earlier.
s :h
e
In a SAN up to 16.77 million devices can be connected to each other. The distance between
r c
components can indeed be 20,000 kilometers. The speed at which data can be transported has
ou
improved a lot from the first SAN infrastructures. Speeds of 16 Gb/s or even 40 Gb/s are now
es
possible. With all these functionalities and the great number of components it is still relatively
R
easy to manage a SAN because of the many tools available for monitoring, managing and
reporting.
i n g
r n
e a
e L
or
M

Storage Area Networks
Storage Area Networks Concepts
e n
/
o m
e i .c
aw
u
g .h
n
SAN Components : Hosts ; Storage Devices; Switches.
ni
r
lea
: //
t p
Components like storage arrays, backup units etc are referred to as storage devices.
t
s :h
Currently there are no SANs used by companies that reach the physical limits of 16.77 million
c e
components. However we do see that SANs now span the entire globe as a companys business
r
ou
sometimes extends from China to America and from Europe to Africa. Then a vast number of
s
people depend on the possibility to access data within a company wherever the employee might
e
R
be. Picking up a file from an office in Shenzhen that is stored on a server in Brazil should then be
possible.
i n g
r n
Perhaps the most important factor in a SAN infrastructure is the reliability. A well designed
e a
infrastructure can prevent an infrastructure to collapse when a single component fails. A good
e L
design is described as a design without a Single Point Of Failure (SPOF). That just means that
or any component can fail but all the functionalities of the IT infrastructure are still there.
M The first step in creating a SAN design is the choice for the components themselves. The second
step is to make the design be reliable. When building a SAN for a big company (also referred to
as an Enterprise infrastructure) the quality of the individual components is very important. The
quality of equipment is often defined as:
1. For personal use at home.

2. For use in SOHO environments (Small Office Home Office).
3. Enterprise class equipment.

It is obvious that in an enterprise SAN the components should be enterprise class components.
An enterprise component is defined as a device with 5x9 reliability or 99.999% uptime
classification. This level of availability is sometimes also referred to as 24/7.
Enterprise components have been tested for usage over many years in a 24 hours a day
production environment. Compare that with laptops; printers we use at home that are only
designed to be used a couple of hours a day.
e n
/
A rating of 99.999% means that statistically a component should be up 365 days, 23 hours and 45
m
minutes per year. But of course most components will run for years without problems!
.c o
e i
Storage Area Networks Cabling
aw
u
g .h
ni n
r
// lea
p :
t t
s :h
r c e
s ou
Cables can be copper or optic, protocols can be FC, iSCSI or FCoE.
Re
g
n i n
ar
So all the components used are of the best possible quality. Huawei offers enterprise class
L e
equipment for all components in a SAN infrastructure. The cables, that are used to connect the
r e
many components with each other, in a SAN solution can be both copper-based as well as fiber
o
optic-based.

Storage Area Networks Components
Huaweis products offer everything to build this ideal infrastructure.

Components we find in a SAN are :
Servers/Host where applications (Database; Email; Graphical Design) run

hosted by operating systems (Windows; Linux; Solaris; AIX).
Interconnect devices:
switches; routers.
e n
/
m
Storage devices:
o
Disk arrays; backup devices
.c
(tape or disk based).
e i
w
Of course we need cables to connect them all together.
u a
g
Slide 8 .h
ni n
r
lea
However in the design we must include the scenario where a component will fail mechanically
//
after all. Also the design should include methods to make sure that human errors do not lead to
:
problems.
t t p
s :h
r c e
ou
In a later section of this module the design of a SAN will be explained. Now it is important to look
s
at the details of how a SAN works.
e
R
i n g
r n
e a
e L
or
M

Differences between DAS and SAN
Differences between DAS and SAN
Item DAS SAN
Multiple protocols: FC, iSCSI,

Protocol. SCSI protocol.
n
FCoE.
Small and medium-sized LANs that

Mid-range and high-end storage
environments such as key
/ e
m
Application
have only a few number of servers and databases, centralized storage,
o
scenarios.
general storage capacity requirements. mass storage, backup, and disaster
.c
recovery.
e
High availability, high performance,
high scalability, powerful i
w
Advantages. Easy deployment, small investment.
compatibility, centralized
management.
u a
.h
Poor scalability, waste of resources,
Disadvantages. management difficulties, performance Comparatively large investment.
bottlenecks.
i n g
r n
lea
: //
t p
A SAN works much like a DAS when we look at the form in which the data is transported from one
t
:h
component to the other. With both DAS as well as SAN the data is sent as SCSI blocks. Of
s
course there is a difference because the cable limitations of DAS were in the range of 12 25
c e
meters whereas a SAN can stretch over distances of hundreds or thousands of kilometers.
r
s ou
The solution used in SAN infrastructures is not to send the individual SCSI blocks over the
Re
network but to put the SCSI blocks (referred to as the user data or payload data) inside a packet
i n g
or frame. It is the network that now is optimized to transport the packets across great distances.
r n
a
Packets can be compared with envelopes that we use to send letters to someone. A letter (a
e
L
sheet of A4 paper) is the user data and the envelope is the packet. It will be virtually impossible to
e
r
send a letter to someone by simply throwing the sheet of paper out on the street hoping that the
o
wind will bring it to the addressee.
MA better way is to put the letter inside of an envelope and put on a postage stamp. Of course you
will have to write the correct address information and drop the letter in a postbox. Once that is
done the national postal service will take care that the letter is picked up from the postbox and
delivered at the address of the recipient.
Of course there are other ways to bring the letter to the home of the addressee. One of the
alternatives would be a specialized delivery service like UPS or FedEx. They have their own

system where you would put the letter inside of a special envelope again. It is now the transport
system of the delivery service that brings the envelope to the recipient.
To send SCSI blocks across a long SAN connection multiple methods can be used. These
methods are referred to as protocols. Each protocol has a distinct way of describing the way the
SCSI blocks are handled for transport.
Three protocols are used with SAN infrastructures:
e n
/
1. FC protocol (Fibre Channel).
o m
.c
2. iSCSI protocol (Internet SCSI).
3. FCoE protocol (Fibre Channel over Ethernet).
e i
aw
The first two of these protocols are mostly used in modern SANs (FC and iSCSI) where FCoE is
u
an upcoming technology. New alternative methods include Infiniband (IB) and SAS.
g .h
ni n
r
// lea
SAN Storage Applications
p :
t t
: h
s
SAN Storage Applications
e
r c
o u
Centralized deployment of Storage resources are
es
storage devices enables divided into blocks that are
R
application servers to access mapped to application
g
and share data in a cost- servers to achieve storage
n
effective manner. resource sharing.
n i
ar Application
e
eL
Data backup uses a SAN SANs employ multiple
or
independent from the service mechanisms for automatic
network, making backup data backup, allowing data
possible for data across to be immediately
M heterogeneous servers and

of diversified forms.
recovered after occurrence
of a disaster.
Before we look at the various protocols used with SANs we will look at application scenarios for
SANs. As the total cost of a SAN solution is rather high (for the hardware as well as for the staff

that needs to be experienced in SAN technology) we see SANs in companies with 100+
employees. In this kind of company the data is typically:
Generated by mission-critical database applications that have demanding requirements for

response time, availability, and scalability.
Backed up centralized and with high performance, data integrity, and data reliability.
e n
/
Massive in number. Examples of organizations that create and store huge amounts of data
are libraries, banks, social media sites like YouTube, Facebook.
o m
A very special example:
e i .c
aw
The CERN Research Institute in Geneva Switzerland uses a 7 x 9 (99.99999%) classified Huawei
storage system to store all relevant data CERN collects from its experiments.
u
g .h
i n
The design of the storage system had a number of demands that should be met:
n
r
lea
1. It should be able to store the data very reliable as the data cannot be generated a second
time.
: //
t t p
2. The capacity that at the beginning could be stored had to be at least 50+ PB (=
:h
50,000,000 GB).
s
3. The system should be extendable with at least 20 PB per year.
e
r c
ou
For environments such as at CERN the best possible hardware is required. Still we have to
es
consider the risk of a hardware failure. Nothing will work forever so how do we eliminate the
R
problem of a piece of hardware failing.
i n g
r n
The answer is to create a clever design. The most important concept there is redundancy.
e a
L
Redundancy is defined as:
e
r
The inclusion of extra components of a given type in a system (beyond those required by the
o
M
system to carry out its function) for the purpose of enabling continued operation in the event of a
component failure.
In easier terms: Add extra hardware that can be used in case of a hardware failure. What that
means to a SAN design is shown in the next section.

Redundancy in hardware
Host Most simple design with a lot

of SPOFs !!!
Network Interface Card

1. Network Interface Card.
e n
/
m
2. Cable hostSwitch.
3. Switch.
.c o
i
Switch
4. Cable SwitchStorage.
we
5. Controller module
Storage.
u a
.h
Controller + Interface Storage Device
g
disk disk disk disk
n
disk disk disk disk
i
disk disk disk disk
r n
lea
: //
t t p
In the above example the goal is to connect a host via a switch to a storage device. In the
:h
simplest solution we need two cables and one switch to make it work. The host itself is an
e s
enterprise class device and it has dual power supplies build into the chassis. If one of them fails
r c
the other surviving power supply will keep the host powered on.
s ou
Re
Although this will work the design does not include enough reliability as a single cable breaking
would disrupt the data traffic between host and storage device.
i n g
r n
Any component that fails, however small or cheap it is, and that disrupts the working of the total
e a
system is called a Single Point Of failure or SPOF.
e L
or A good design has no single points of failure. So a much improved design would be the next one.

Host
NIC
SPOF ? Yes / No
NICs No
Switch Cable Switch

Cables between
n
No
HostSwitch
Switches No
/ e
m
Cable Cable
Cables between
No
.c o
i
Controller Controller SwitchStorage
Disk
Disk
Disk
Disk
Disk
Disk
Disk
Disk
Disk
Disk
Disk
Disk
Controllers No
we
u a
g .h
ni n
r
lea
In this design there is almost complete redundancy in hardware because almost all hardware can
//
fail (single component at a time however!) and still there would be an alternative route from host
:
to the storage device.
t t p
There are two more SPOFs left that we must identify:
s :h
r c e
ou
1. What if the Operating System or the Application running on the host crashes ?
s
2. If we store all our vital information on a physical hard disk and that hard disks fails ?
e
R
i n g
For both problems there, of course, are solutions available.
r n

a
There are a few methods to be able to survive a crash of a complete host or an Operating
e
eL
System failure. We often refer to an operating system crash as a Blue Screen Of Death.
or
This is because some operating systems in those situations show a screen with a blue
background that sometimes gives troubleshooting information about the system crash.
M The most well-known solution is a so-called cluster. With intelligent cluster software we
can arrange for an application to be shared between multiple systems or nodes. Nodes
communicate with each other and check their neighbors health continuously. As soon as
a host goes down the other nodes notice this and automatically take over the role of the
crashed system.

The simplest solution to prevent this is not to store the data on a single disk but spread
the data across multiple disks. Then they have designed methods to protect the data.
Using a clever method they make it possible for the remaining disks to recalculate all data
from a failed disk. Optionally systems will automatically recalculate the data and store it
on a spare disk which is already inserted in the system.
The technology where we intelligently distribute the data across multiple disk drives and
have the opportunity to recalculate failed disks is called RAID which is short for
Redundant Array of Independent Disks.
e n
/
o m
RAID will be explained in more detail in later modules.
e i .c
aw
u
g .h
Multipathing problem
ni n
r
// lea
p :
t t
s
Host
:h From the host perspective
e
NIC there are multiple paths that
r c lead from the host to the
ou
storage device where the 100
GB volume lives.
Switch
1
es 2
Cable
3 4
Switch
R
i n g Cable Cable
The redundant paths provide
r n reliability but for the host
e a Controller Controller operating system it leads to
L
Disk Disk Disk Disk confusion called the
Disk Disk Disk
100 GB Disk multipathing problem.
e
Disk Disk Disk Disk
or
Now we know what has to be done to allow the host to use the volume when we encounter a
problem. The host discovers multiple routes through the network towards the storage device that
holds the volume. Of course the redundant cables are there by design but it is confusing for many
operating systems because each of these paths (indicated by the numbers 1-2-3-4) appears to
the operating system as independent routes to a total of up to four volumes!

This confusing situation has been given a name: the multipathing problem.
Operating systems that have/had multipath problems: Windows, AIX,

Solaris, HP-UX, Unix, Linux.
Operating systems that handle multipathing well: Tru64, OpenVMS,

VMware vSphere.
e n
/
m
Vendors sometimes build their own specific software module to handle
o
multipathing :
Huawei UltraPath.
Dell EqualLogic DSM.
e i .c
EMC PowerPath.
aw
u
g .h
ni n
r
lea
: //
t p
In a host running the latest versions of Windows (2008 and 2012) multipathing intelligence is
t
:h
integrated so we do not see these problems as much as before. Older versions, like Windows
s
2000 and 2003, would show the newly discovered disks multiple times. The next image shows
e
c
four 100 GB volumes on a Windows 2003 server, where in fact there was just one volume created
r
ou
on the storage device.
es
R
i n g
r n
Example of a Windows host without multipathing software.
e a
e L
or
M
Each of the paths is represented with a separate volume.

Without the intelligence of the multipathing software every volume created within the storage
device will be represented as multiple independent volumes for the operating system. Out of the
detected volumes (in this case 4) the operating system will not detect which one of them is
actively moving data. If the path (or better: the cable) is broken the operating system cannot use
any of the alternative paths to continue accessing the volume. So although there is redundant
hardware it is not understood and used by the operating system.
It needed extra software installed on the host to make clear to the operating system that it was a
single volume but with multiple physical paths to it.
e n
/
o m
.c
With the correct multipathing software installed a single volume will be displayed in disk
management.
e i
aw
u
g .h
ni n
r
// lea
p :
t t
s :h
r c e
s ou
Re
i n g
r n Copyright 2015 Huawei Technologies., Ltd. All rights reserved. Slide 16
e a
e L
r
The picture above now shows the same 100 GB volume but now only once. At the same time the
o multipathing software is now intelligent enough to redirect the data over another cable in case the
M current active path fails. The multipathing software is so fast in this redirection that the operating
system is not even aware that the data was redirected. The operating system had a continuous
access to the data on the volume.

New volumes in disk management
e n
/
o m
e i .c
aw
u
g .h
ni n
r
lea
For any operating system the newly discovered storage capacity is what is called raw capacity.
//
The host will have to initialize the volume and then format it creating a file system partition. Once
:
this is done files can be stored on the volume.
t t p
s :h
This finishes the design of the SAN. We can now afford to lose a hardware component and still be
c e
able to access our data. In the next section we will look at the protocols used to transport the data.
r
ou
First we will discuss the protocol that is already used for a long time: the Fibre Channel protocol
es
R
i n g
r n
e a
e L
or
M

Network Topology: Fibre Channel
In this section we will look at the Fibre Channel protocol which is one of the possible protocols
that can be used with SAN infrastructures.
Network topology: Fibre Channel
e n
Point-to-point Arbitrated loop Fibre Channel switched fabric
/
o m
e i .c
aw
u
g .h
i n
Most widely used topology
n
r
lea
Two devices only Up to 127 devices Up to 16 million devices
(Direct connection). (Fibre Channel hub). (Fibre Channel switches).
: //
t t p
:h
e s
r c
It was already mentioned that the Fibre Channel protocol is used for a long time (starting in the
ou
1990s). In these days the SAN infrastructures were much smaller and there were a couple of
s
e
ways to physically connect the components to form the SAN.
R
i n g
1. Point-to-point
r n
Two devices are directly connected to each other. This is the simplest topology, with
e alimited connectivity.
e L
or 2. Arbitrated loop
M
All devices are connected in a loop or a ring. Adding or removing a device to or from the
loop interrupts all activities on the loop. The failure of a device on the loop causes the
loop to break. By adding a device called a hub it was possible to connect multiple devices
to a logical loop and bypass faulty nodes so that the communication on the loop is not
interrupted.
Arbitrated loops were used in the first small scale SANs but nowadays it is no longer
used. Reason is the fact that an Arbitrated Loop can only hold a maximum of 127 devices.
Today SANs should be able to include many more devices than 127.

3. Switched network
This is the modern way how FC SANs are built. It uses switches to connect hosts to
storage devices. Maybe it is better to state that modern SANs use at least two switches
for redundancy reasons!
A switch in itself is an intelligent device that is not only used to interconnect a device with
another but it can do much more. Switches, especially if there are many of them, can be
e n
/
configured in such a way that data going from one device can find the optimal path
m
through the big network of interconnected switches.
.c o
e i
aw
Fibre Channel Protocol
u
g .h
ni n
r
lea
Fibre Channel protocol
: //
High-level protocols
t t p
:h
SCSI-3 IP ATM
e s
FC-4
r c IPI-3
Command set
SCSI-3 FC-LE FC-ATM
ou
Command set Link
mapping mapping encapsulation
FC-3
es General equipment
FC-2
R
Structure agreements.
g
FC-PH FC-AL FC-AL2
n
FC-PH2
i
FC-1 Coding and decoding.
FC-PH3
r nFC-0 Physical transformation. 8/10 bit/s copper and optical fiber.
e a
e L
r
o
MFibre Channel was developed in 1988. At that time, Fibre channel was primarily concerned with
simplifying the connections and increasing distances, as opposed to increasing speeds. Later, it
was used to increase the transfer bandwidth of the disk data transfer protocol to provide fast,
efficient, and reliable data transfer. By the end of 1990s, Fibre Channel SAN had been used
extensively. The most important layer of the Fibre Channel protocol is FC-2. FC-0 to FC-2 are
referred to as FC-PH, or the physical layer. Fibre Channel mainly uses FC-2 for data transfer. As
a result, Fibre Channel is also known as "Layer 2 Protocol" or "Ethernet-like Protocol".

A frame is the data unit of Fibre Channel. Though Fibre Channel has several other layers, it uses
FC-2 in most cases. A Fibre Channel frame contains a maximum of 2148 bytes. The header of a
Fibre Channel frame is different from that of an Ethernet packet. Fibre Channel uses only one
frame format to accomplish various tasks on multiple layers. The functions of a frame determine
its format.
A Fibre Channel frame starts from the Start Of Frame (SOF) delimiter, which is followed by the
frame header. We will talk about the frame header later. Then comes data, or Fibre Channel
content. Finally, it is the End Of Frame (EOF) delimiter.
e n
/
o m
.c
Relationship between Fibre Channel and SCSI:
e i
Fibre Channel is not a substitute of SCSI. Fibre Channel can transfer the instructions, data, status
aw
messages of SCSI by using frames. SCSI is an upper-layer protocol of FC-4 and is a subset of
u
Fibre Channel.
g .h
i n
To transmit large amounts of data we still need a lot of frames to be sent. When a group of frames
n
r
are sent as a batch is we call this an exchange.
// lea
p :
t
Fibre Channel Frames
t
s :h
e
Frame Frame Frame Frame Frame Frame
c
1 2 3 4 5
r
0
ou
SEQUENCE X SEQUENCE y
es
R EXCHANGE X
i n g
r n F0 = Start of exchance, start of sequence.
e a F1 F3 = Middle of exchange, middle of sequence.
eL
F4 = Middle of exchange, end of sequence and added to that is a Transfer
Sequence Initiative.
or
F5 = Middle of exchange, start of new sequence.
Inside an exchange there are sequences of frames that are sent. In each frame there should be
information about the exchange and sequence the frame belongs to. Also the number of the
frame itself and its source and destination is listed. This is what an FC frame looks like.

A Fibre Channel frame consists of multiples of Transmission Words

of 4 bytes each. The maximum number of TWs is 537 which makes
the maximum frame size 2148 bytes.
Header
SOF xx
EOF xx
n
Idles
CRC
Idles
Optional headers + PAYLOAD
/ e
6 TW 1 TW 6 TW 0 - 528 TW or 0 -2112 bytes 1 TW 1 TW 6 TW
o m
.c
537 TW or 2148 bytes
e i
w
A full payload of data is 2048 bytes with 64 bytes reserved for optional
headers.
u a
g .h
ni n
r
lea
The next picture shows the layout of the header in a Fibre Channel frame.
: //
t t p
:h
e s
r c
The frame header is used by both the fabric (for routing) and the
ou
receiving port (for re-assembling the messages).
Bit 32
es 24 16 8 0
R
Byte 0 Byte 1 Byte 2 Byte 3
ing
Word 0 R_CTL DESTINATION_ID
rn
1 RSVD SOURCE_ID
a 2 TYPE F_CTL
L e 3 SEQ_ID DF_CTL SEQ_CNT
r e 4 OX_ID RX_ID
o 5 PARAMETER
M
Note: this information is very detailed and is here for reference only.

Storage device with FC interface
Storage device with FC interface
The Fibre Channel interface modules on a storage device provide

service interfaces for connecting to application servers and receiving
data exchange requests from the application servers.
e n
/
Module Power
Indicator
o m
.c
Module
i
handle
e
Fibre Channel
host ports 8 Gbit/s Fibre
Channel port
aw
u
Link/Speed indicator
.h
of an 8 Gbit/s Fibre
Channel port
i n g
r n
lea
: //
t t p
In many cases the Fibre Channel frames are transported via fiber optic cables. That means that a
:h
light pulse is used to indicate a logical one signal. By switching the light on and off we can
e s
indicate one and zero signals. All devices involved therefore must have the appropriate
r c
equipment to send the optical signals and receive them.
s ou
Re
The Huawei storage devices for that reason have interface module or I/O cards. Hosts will
typically have a dedicated card installed that allows fiber optic connections. Of course the
i n g
switches in the middle must be equipped with optic modules too.
r n
e a
The special cards inserted in hosts are so-called Host Bus Adapters (HBAs). Essentially a Fibre
e L
Channel HBA converts the electrical signals into light pulses that will be emitted by a laser source
or in the HBA. The light pulses that are received by the host will then be detected by photoelectric
M
sensors and converted into electrical signals that the computer can use again internally.

HBA
HBA: Various HBAs
HBA is short for host bus adapter, which is

the I/O adapter that connects the host I/O
bus to the computer memory system.
Categories:
Fibre Channel HBA, SCSI HBA, SAS HBA,
e n
/
iSCSI HBA, and so on.
Function:
o m
.c
Enables bidirectional or serial data
communication between servers and
storage devices through hubs, switches, or
e i
point-to-point connections.
aw
u
g .h
ni n
r
lea
The actual component with the light source and the photoelectric sensor is a module referred to
//
as a transceiver. A transceiver is a module in itself that will be inserted in a slot called an SFP port.
:
This is a so-called Small Form factor Pluggable or SFP for short.
t t p
s :h
Transceiver
r c e
s ou
Transmitter + Receiver = Transceiver.
Re
Contains a laser or a LED to create the light pulses.
i n g
Contains an optical sensor that can detect light.
r n
Transceivers are present in storage devices; switches
e a and server HBAs.
eL
Can individually be removed/replaced.
or
M

Transceivers are available for different transmission speeds, for different distances the signal has
to travel and there are different versions of physical interfaces. The most common interface type
for HBAs now is the PCI-E slot which is present in almost all enterprise class servers.
Connecting a host to a FC switch
Host Bus Adapter is put in a PCI slot.
e n
/
o m
e i .c
aw
u
g .h
ni n
r
//
A fibre channel transceiver is put in a SFP slot in the switch.
lea
p :
t t
s :h
There are different vendors for HBAs like Emulex, Brocade and Qlogic. They have HBA models
c e
with different numbers of ports. In the above image a 2-port FC HBA is used as an example.
r
s ou
With the correct HBA installed and the appropriate cable type used a signal can be transported
Re
via an optical cable over a distance of 50 km.
i n g
r n
e a
e L
or
M

Common optical connection medium
Media Type Transmitter Rate Distance
1 Gbit/s 2 m to 50 km
1550 nm long-wave laser.
9 m single-mode
optical fiber.
1300 nm long-wave laser.
n
50 m multi-mode
1 Gbit/s 0.5 m to 500 m
/ e
m
2 Gbit/s 0.5 m to 300 m
optical fiber.
o
4 Gbit/s 0.5 m to 170 m
.c
850 nm short-wave laser.
i
1 Gbit/s 0.5 m to 300 m
e
62.5 m multi-mode
2 Gbit/s 0.5 m to 150 m
optical fiber.
w
4 Gbit/s 0.5 m to 70 m
u a
g .h
ni n
r
lea
With single mode cables it is much more difficult to get the light inside of the cable because the
//
diameter of the cable. That is why the light source should be very bundled. This means that the
:
best light source for these situations is a laser source.
t t p
s :h
Multimode cables are 5 - 7 times the diameter and the demands for the light source are less strict.
c e
That is why in some lower cost solutions the light source is a LED (Light Emitting Diode). Those
r
ou
are much cheaper to produce but generate light in multiple colors (or better a range of colors) and
s
LED light is not bundled the way laser light is.
e
R
i n g
Note: multi-mode cables are used mostly in datacenters as the distances there are limited to a
n
maximum of a couple of hundred meters. The multi-mode cables used are the ones with a core
ar
diameter of 62.5 m. In comparison: a human hair typically has a diameter of 75 m.
L e
r e
o
M

Fiber optics
Fiber optics
n1 coating
Snells law: =n

foam
2
n2 cladding

n1
core
e n
=
nair
n1
/

n2
o m
light bundle
e i .c
n = refractive index of the optical medium.
aw
Note: n for vacuum is set to 1; n for air 1.
u
g .h
i n
r n
lea
There is a lot of physics needed to explain how it is that a light signal can be transported over
//
:
these distances. The most important physical law with fiber optics is Snells law. That law states
p
t t
that light moving from one matter to another will be refracted. In the above picture we see a light
:h
bundle come in at an angle and then hit the optical material of the cable. At the surface of the
e s
cable there is refraction and that results in the fact that the signal continues with an angle .
r c
Snells law now teaches us what determines the change in the angle. He found out that it is
s ou
depending on a property of a material called the refractive index.
Re
g
Fiber optics
i n
arn
L e 1
n2
r e
o n1
M 1
n2
light bundle
If the light hits the surface at a angle <= 1 then the light beam will
bounce off at the same angle.

When the angle is incorrect (here shown with 1) the signal will not be refracted and enter the
cable but it will reflect or bounce back from the surface. The angle of reflection is than again 1
which makes the effect look like the light bundle hits a mirror and reflects from it with the same
angle.
The pictures shown before show the physical construction of the fiber optic cable. The core of the
cable is made of a plastic like (so not glass) material that carries light very well. The better a
material carries light the lower its refractive index is. The refractive index for vacuum is set to be
e n
/
one. Air has a refractive index of almost one. Optical cables use materials with refractive indexes
in the range of 2.2 to 3.0.
o m
Directly outside the core there is another layer of optical material with a slightly different refractive
e i .c
index: the cladding. Then a layer of foam is used to protect the fragile optical parts. The actual
aw
outer layer is a plastic sheath that is often orange or yellow.
u
g .h
ni n
FC optical cables
r
// lea
Macro bends
p :
t t
:h
cladding
e s
r c
s ou
Re
i n g
r n minimum radius 0.05 m ( 5 cm)
e a
eL
or
MAs it is important to keep the light inside of the core and have it bounce back against the surface
where the core and the cladding meet. Light that leaves the cladding (indicated with the red arrow)
has hit the surface in an unfavorable angle. That part of the signal will then be lost. That would
mean that the signal is less bright which at the end may result in a weak signal that cannot be
detected by the photoelectric sensors. All the theory above is used to make clear that handling
the cable is very important. An engineer should not bend the cable too much and also should he
keep the ends of the cable and the transceivers dust free.

FC optical cables
Possible problems resulting in power loss (attenuation):
Macro bends: minimal radius 1 inch. Even though bends are

according to specs light paths differ leading to a
distorted signal.
Micro bends: pinching of cables leads to loss of signal.
e n
Scattering : impurities have a different refractive index.
/
m
Light is scattered when it passes impurities.
Absorption : light hits the cladding in an unfavorable angle and is

.c o
absorbed in the cladding.
e i
aw
u
g
Slide 30 .h
ni n
r
lea
It is important to handle the cables in such a way that the optimal amount of light stays in the
//
cable making the success rate of detecting the light pulses as high as possible. Fiber optic cables
:
t p
should be laid out without sharp bends. Also any dirt that is collected on the optic material of the
t
:h
cable or inside the transceivers impact the amount of light transported.
e s
FC multimode rc
o u
es
R
Multimode fiber exists in:
i n g
rn
Step-Index multi-mode.
e a supports thousands of nodes.
eL
high dispersion.
or
lowest bandwidth.
M Graded-Index multi-mode.
reduced dispersion.
increases bandwidth.

The more light is trapped inside the cable the higher the intensity of the light pulse will be at the
end of the cable. To improve the quality of the optical cable they changed the way the core itself
is built. Using multiple layers with slightly different refractive indexes they have arranged that the
light pulses will be pushed in to the center of the cable. This type of cable is called a step-index
cable.
Nowadays almost all cables used are graded index cables. In such cables the density of the
optical material is changed in such a way that the refractive index changes continuously from the
inside of the core towards the cladding. This is the optimal construction to keep the light directed
e n
/
m
towards the inside of the core.
.c o
e i
aw
Fibre Channel switch
u
g .h
ni n
r
lea
Fibre Channel switch
: //
p
Directly connected to a Fibre Channel network.

t t
:h
Directly connected to an initiator and a target.
s
Exclusive use of all optical bandwidths.
Zoning.
r c e
s ou
Re
i n g
r n
e a
e L
r
o
MFibre Channel (FC) switches are considered to be the core of a SAN. FC switches connect hosts
to storage devices.
In order to eliminate unwanted traffic between certain fabric nodes in an FC SAN we define zones
in the Fibre Channel switches. A zone is similar to a VLAN with Ethernet switches. Devices in
different zones cannot communicate with each other.

Fibre Channel switch ports
Fibre Channel switch ports
Fibre Channel switch 1
Node N_Port F_Port F_Port N_Port Node
e n
/
E_Port
o m
E_Port
FL_Port
e
NL_Port Node i .c
G_Port FL_Port FL_Port
aw
u
.h
FL_Port NL_Port Node
Fibre Channel switch 2
i n g
n
Fibre Channel hub
r
lea
: //
t t p
Fibre Channel switches house various ports. The ports provide different functions depending on
:h
the types of devices connected to them.
e s
r c
The following types of ports are defined by Fibre Channel:
s ou
F_Ports (also known as Fibre Channel network ports) are ports on the switch that connect to
Re
a node point-to-point (for example, connects to an N_Port). In the case of the arbitrated loop
i n g
topology, the node is regarded as an NL_Port. Fibre Channel switches identify these nodes
by the names of N_Ports or NL_Ports.
r n
e a
E_Ports (also called expansion ports) are connection between two Fibre Channel switches.
e L
or FL_Port is a port on the switch that connects to an FC-AL loop (for example, to NL_ports). A
M
switch port on a Fibre Channel switch can be part of a loop and data can be transferred from
the switch to the loop. The switch port working correctly in a loop is referred to as an FL_Port.
G_Ports are generic ports, which can operate as F_Ports or E_Ports depending on the
implementation mode. Thanks to its adaptability, G_Ports can deliver flexibility to Fibre
Channel switches and cut down the administrative costs of each port on a multi-switch Fibre
Channel SAN.
Currently, Fibre Channel switches can support a port rate of 1, 2, 4, 8 or 16 Gbit/s.

World Wide Name
WWNs of Fibre Channel HBAs
WWNN = World Wide Node Name.
WWPN = World Wide Port Name.
e n
/
o m
.c
P2P
i
Input Fibre Channel FC-AL
e
WWPN network FC-SW
output
WWNN Link
aw
u
g .h
ni n
r
lea
: //
t t p
Because a SAN can have thousands of components there must be a way to identify each one of
:h
them with a unique code. Compare this with a home address that should be unique so only one
e s
person will receive a letter with that address written on it.
r c
ou
For the Fibre Channel protocol they use an identifier called the World Wide Name or WWN. All
es
Fibre Channel compatible equipment has a unique WWN up to the single interfaces of the I/O
R
modules in storage devices. For that reason different WWNs are defined:
i n g
1.
r n
World Wide Node Name (WWNN)
e a
The globally unique node name. Each upper-layer node is assigned a unique 64-bit identifier.
e L
All ports on an HBA share the same WWNN. A WWNN is allocated to a node (or terminal, for
or example, a device) on a Fibre Channel network. The WWNN can be used by one or multiple
M
ports that have different WWPNs and belong to the same node.
2. World Wide Port Name (WWPN)

The globally unique port name. Each Fibre Channel port is assigned a unique 64-bit identifier
and has an exclusive WWPN. The application of WWPNs in a SAN is similar to that of an
Ethernet MAC address.
An example of a World Wide Name could be: 2000-C29C-34FA-BC0D

In the WWN each character is a so-called hexadecimal number that represent 4 bits.

Fibre Channel zoning
Fibre Channel Zoning
BLUE ZONE
RED ZONE
e n
/
BACKUP1
HOST 2
o m
.c
HOST1
e i
STOR1
STOR2
aw
STOR3
u
HOST 3
g .h
i n
GREEN ZONE
n
r
lea
: //
t t p
Zones are mostly created because of security reasons where the manager of the SAN wants
:h
to restrict access to specific devices. In a zone of a switch the equipment can only
e s
communicate with the other equipment in the same zone. In the above example the green
r c
zone contains two storage devices (STOR1 and STOR2) and a host (HOST3). That means
ou
that HOST3 can detect the devices STOR1 and STOR2 and can communicate with them.
es
Although the other devices are connected to the same switch HOST3 will not be able to
R
communicate with the other hosts or the backup device (BACKUP1). STOR3 is not in any
i n g
zone and therefore cannot be detected by any other device.
r n
e a
It is possible to add a device to multiple zones. In the picture STOR1 is in two zones (RED
eL
and BLUE). Also in two zones is STOR2. It is in the BLUE and the GREEN zone.
or
M
The picture above is a symbolic representation of the zones. In practice the devices are all
connected to a Fibre Channel switch. The zones can then be represented like shown in the
next image.

Fibre Channel Zoning
RED ZONE STOR1

BLUE ZONE
HOST2
HOST1
e n
/
o m
STOR3
BACKUP1
e i .c
HOST3 STOR2
aw
u
GREEN ZONE
g .h
ni n
r
lea
Zones are defined within the switch using a graphical interface or in a command line mode. With
//
the command line mode (also called CLI) special commands have to be typed to make all the
:
t p
settings for the zones. Multiple zones can exist inside of a switch. Zones can be active or inactive.
t
:h
Which zones are active is defined in so-called configurations. Multiple configurations can exist in
s
a switch, but only one configuration can be active!
r c e
ou
Two major methods can be used to define the zones in a switch:
es
1.
R
Port zoning. For each of the zones the number of the ports, the devices are connected to,
i n g
are listed. This requires the switch administrator to know exactly for each cable, connected to
n
the switch, what device is connected. The term used to indicate a device being connected to
ar
a switch is: patch. For port zoning to work the patching of all devices must be documented.
L e
r
2.
e Soft zoning. This is also called World Wide Name zoning. In the switch the zones are
o defined by listing all WWNs of the devices that should be in the same zone. As WWNs are
M identifiers that are not easy to memorize; usually aliases are defined for each WWN.
The following pictures show sections of the graphical user interface Huawei uses inside its Fibre
Channel switch model SNS2124

Zone Basic configuration
1. Configure.
2. Zone Admin.
3. enter Zone Administration.
e n
/
o m
e i .c
aw
u
NoteScreenshots are for the FC switch model SNS2124
g
Slide 38 .h
ni n
r
lea
The Configure menu has an item that will open the special Zone Administration window. There
//
the user can create aliases for the WWNs in the various devices connected to the switch. Note
:
that this is typically done when soft zoning is used.
t t p
s :h
New Alias
r c e
s ou
Re Step 3
i n g Step 1
r n
e a
e L
or
M Step 2

New Zone
Step 3
Step 1
e n
/
o m
Step 2
e i .c
aw
u
g
Slide 40 .h
ni n
r
lea
Once the aliases are defined the next step is to create the individual zones. Step 1 is to give the
zone a symbolic name and then add aliases (or port numbers) to them.
: //
t t p
:h
After the creation of all required zones the configuration(s) must be defined. Again this starts with
s
a symbolic name for the configuration. Then the zones that should be active, when the
e
c
configuration is enabled, are added to the configuration.
r
s ou
Re
Creating and enable Zone Config
i n g
r n
a
Step 4 Step 3
e
eL
Step 1
or
M
Step 2

Inside of a switch there can be a number of zones and a number of configurations. Only one
configuration can be active at any time. This is the running configuration. Every time a change is
made to the zones or the configurations the new changes will be applied in the running
configuration.
However: it is important to save the configuration! When a switch reboots or gets powered off and
powered on it will not use the running configuration. A switch always starts with the startup
configuration and that is the last saved version of the active configuration.
e n
/
m
A Fibre Channel SAN typically has at least two Fibre Channel switches. The reason is not only
redundancy but also because the design of Fibre Channel SANs demands it. An FC SAN must
.c o
consist of two separate networks called fabrics.
e i
aw
u
g .h
Fibre Channel fabrics
ni n
r
// lea
p :
t t
:h
Fabric:

e
Separate network within a
s
FC SAN.
r c
ou
FC FC

s
Can consist of multiple
e
switches.
R
Fabric A Fabric B
g
FC FC
n i n
ar
L e
r e
o
Depending on the size of the required SAN infrastructure the choice for FC switch models ranges
between entry level FC switches and high end switches called core switches.
The difference between them is mostly based on the number of physical ports that are present in
the switch. For an entry level switch this could be 24 ports where core switches can have
hundreds of ports.

When a switch has not enough ports the option could be to replace it with a bigger one. But there
is an alternative. Two switches that are connected together using a Fibre channel link between
them will from that moment function as one switch! So one could keep the old switch and buy a
second switch. In both switches one port is used to put the interconnecting cable in. With this
method two 24 port switches combined with the interconnect cable act like a 46 port switch. (2 x
24 2).
The next picture shows a few possibilities for connecting switches together.
e n
/
o m
.c
e i
aw
u
g .h
ni n
r
// lea
p : Core Edge Design
t
Ring network Meshed network
t
s :h
r c e
s ou
Re
i n g
r n
e a
e L
or
M

IP SAN
What is an IP SAN?
An IP SAN is an approach to using the Internet Protocol in a

storage area network usually over Gigabit Ethernet.
n
The typical protocol that implements an IP SAN is Internet SCSI
(iSCSI), which defines the encapsulation mode of SCSI instruction
sets in IP transmission.
/ e
o m
.c
User A User B User C
Server
e
LAN
i
w
Server
HBA
a
HBA
u
.h
TCP/IP network
Storage device Ethernet switch
i n g Storage device
r n
lea
: //
t t p
The title of this section is IP SAN and that may be confusing as the next topic will be the iSCSI
:h
protocol. However this is correct because the iSCSI protocol is one of the options we have to
e s
move the SCSI blocks across an IP based (maybe we should say Ethernet based) network. The
r c
other options are FCIP and iFCP but they are not used nearly as much as iSCSI. So iSCSI will be
ou
the protocol we focus on next.
es
R
An iSCSI SAN puts the SCSI blocks in Ethernet packets and sends them over the network.
i n g
r n
The iSCSI was initiated by Cisco and IBM and then advocated by Adaptec, Cisco, HP, IBM,
e a
Quantum, and other companies. iSCSI offers a method of transferring data through TCP and
e L
saving them on SCSI devices. The iSCSI standard was drafted in 2001 and submitted to IETF in
or 2002 after numerous discussions and modifications. In Feb. 2003, the iSCSI standard was
M
officially released. The iSCSI technology is developed based on traditional technologies and
inherits their advantages. On one hand, we have SCSI technology which is a storage standard
widely applied by storage devices including disks and tapes. It has been developing at a rapid
pace since 1986. On the other hand, we have TCP/IP which is the most universal network
protocol with an advanced IP network infrastructure. These two provide a solid foundation for
iSCSI development.

Advantages of IP SANs
Advantages of IP SANs
IP SANs do not need dedicated HBAs or FC switches but

Standard access common NICs and switches for connecting storage devices
n
to servers can be used.
Long transmission
IP SANs are available wherever IP networks exist. In fact,
/ e
m
distance IP networks are now the most widely used networks in the
o
world.
Enhanced
maintainability
Networking experience is generally already present in
many ICT departments. FC switch knowledge is not.
e i .c
aw
With the development of the 40 Gbit/s Ethernet, IP SANs
u
.h
Scalable bandwidth will soon be faster than the 16 Gb/s of Fibre Channel.
i n g
r n
lea
: //
1.
t t p
The minimal hardware configuration needed is widely available which makes IP SANs
:h
cheaper to implement than FC SANs. Most hosts already have suitable network interfaces
e s
and switches are often also suitable (but not ideal) for iSCSI traffic. High performance IP
r c
SANs however are usually equipped with special iSCSI HBAs and high end switches.
s ou
2.
e
Setting up an IP SAN is easy because the IP infrastructure is already spanning the entire
R
globe. The Ethernet cables that are used to run the internet are considered to form the
i n g
biggest network in the world.
r n
3.
e a
To manage an IP SAN the knowledge required is not much more than what most IT
e L
employees already have. Basic Ethernet networking skills are required plus some iSCSI
or specific knowledge.
M
Fibre Channel technology is new to most organizations and that requires a lot of training to
bring every SAN administrator at the right knowledge level.
4. The development of Ethernet is a continuous process and at this point 10 Gbit/s is widely
available. Also the development of 40 Gbit/s and even 1 Tbit/s are well on the way. Fibre
Channel has been upgrade from 8 to 16 Gbit/s just a few years ago.

Fibre Channel SAN vs. IP SAN
Indicator Fibre Channel SAN IP SAN

Transmission speed. 4 Gbit/s, 8 Gbit/s, 16 Gbit/s. 1 Gbit/s, 10 Gbit/s, 40 Gbit/s.
Network architecture. Dedicated Fibre Channel networks and HBAs. Existing IP networks.
Transmission Limited by the maximum transmission distance Unlimited theoretically.

distance. of optical fibers.
Management and Complicated technologies and management. As simple as operating IP devices.
maintenance.
Compatibility. Poor. Compatible with all IP network
e n
/
devices.
Performance. Very high transmission and read/write 1 Gbit/s (mainstream) and 10 Gbit/s.
m
performance.
o
Cost. High purchase cost (of Fibre Channel switches, Lower purchase and maintenance
.c
HBAs, Fibre Channel disk arrays, and so on) costs and higher return on
i
and maintenance cost (of staff training, system investment (ROI) than Fibre Channel
e
configuration and supervision, and so on). SANs.
Disaster recovery. High hardware and software costs for disaster Local and remote DR available on
w
recovery (DR). existing networks at a low cost.
Security. High. Medium/Low.
u a
g
Slide 48 .h
ni n
r
// lea
p :
Networking in IP SANs
t t
s :h
Networking in IP SANs
r c e
s ou
Re Single switch Dual switch
ing
Application Application
server server
arn
e
eL
Ethernet
or
switch Stack/ISL/Trunk
M
Storage device Storage device
The network of IP SANs usually exists out of multiple switches. That is because of the
redundancy in hardware or because of the number of switch ports required. But even with two or

more switches used there will be just one fabric. For IP SANs there is no official need for two
separate fabrics like with FC.
The picture above shows the single switch next to the dual switch solution. Both solutions
however consist of one fabric:
The dual switch networking mode features high scalability and allows multiple hosts to share
the storage resources offered by the same storage device. And even, when a switch fails, the
n
storage resources are still available.
/ e
m
The way the individual switches are connected together to form that one fabric varies. Three
options are available in modern switches.
.c o
e i
w
1. Use a cable to connect two ports on different switches together.
2. Many switches have dedicated ports called uplink ports just for connecting them to other
u a
.h
switches.
3. With midrange and high end switches there is the option to install a so-called stacking
i n g
n
module. Together with a special stacking cable two switches can be stacked together using
r
lea
the stacking modules in them. Stacking allows for high performance interconnection of two or
//
more switches.
p :
t t
s :h
iSCSI connection modes
r c e
s ou
Re
iSCSI connection modes
i n g
r n
Three adapter types can be used with iSCSI communication.
e a
e L
or
M NIC + initiator TOE NIC + initiator iSCSI HBA
software software
SCSI USER DATA - 1 iSCSI INFO - 2 TCP INFO - 3 IP INFO - 4

iSCSI devices use IP ports as their host ports, through which iSCSI devices are connected to
Ethernet switches to form a TCP/IP-based SAN. Depending on the connection mode adopted by
hosts, there are three iSCSI connection modes:
NIC + initiator software: The host uses standard NICs to connect to the network. The
functions of the iSCSI and TCP/IP protocols are processed by the host CPU. This mode
requires the lowest cost because it uses the universally integrated NICs on hosts, but it
requires CPU resources for iSCSI and TCP/IP processing. Note: NIC = Network Interface
e n
/
Connector.
o m
.c
TOE + initiator software: The host incorporates a TOE NIC. The functions of the iSCSI
protocol are processed by the host CPU, but those of the TCP protocol are processed by the
e i
TOE NIC, reducing the workload of the host CPU. Note: TOE = TCP/IP Offload Engine.
aw
u
iSCSI HBA: The functions of the iSCSI and TCP/IP protocols are processed by the iSCSI
g .h
HBA installed on the host. The host CPU has the least overhead.
ni n
r
// lea
NIC + initiator software
p :
t t
s :h The initiator software converts
e
iSCSI packets into TCP/IP
c
packets, which consumes host
r resources.
s ou
e
NIC
R
i n g
TCP/IP-based Ethernet
IP SAN
n
connection.
ar
e
Internal bus
eL
Ethernet
or
Storage device
M
Host devices such as servers and workstations use standard NICs to connect to Ethernet
switches. iSCSI storage devices also connect to the Ethernet switches or to the NICs of the hosts.
The initiator software installed on hosts virtualizes NICs into iSCSI cards. The iSCSI cards are
used to receive and transmit iSCSI data packets, implementing iSCSI and TCP/IP transmission
between the hosts and iSCSI devices. This mode uses standard NICs and switches, eliminating
the need for adding other adapters. Therefore, this mode is the most economical. However, this

mode consumes host resources during iSCSI to TCP/IP packet conversion, increasing operating
overhead and decreasing system performance. The NIC + initiator software mode is applicable to
the scenarios that require moderate I/O and bandwidth performance for data access.
TOE NIC + initiator software
The initiator software

implements the functions of the
n
iSCSI layer, which consumes
e
host resources.
/
m
The TOE NIC implements
o
TCP/IP encapsulation, which
.c
TOE NIC does not consume host
i
resources.
we
a
IP SAN
connection.
u
g .h
Internal bus
n
Ethernet
Storage device
ni
r
lea
: //
t t p
TOE NICs process the functions of TCP/IP protocol while hosts process the functions of the iSCSI
:h
protocol. As a result, the data transfer rate is remarkably improved. Compared with the software
e s
mode, this mode greatly reduces host operating overhead and requires only a little additional
r c
network construction cost. This is a trade-off solution.
s ou
iSCSI HBA Re
i n g
r n
e a
e L
or The iSCSI HBA converts iSCSI
packets into TCP/IP packets,
M
iSCSI HBA which does not consume host
resources.
connection.
IP SAN
Internal bus
Ethernet
Storage device

An iSCSI HBA is installed in the host to implement efficient data exchange between the host and
switch or between the host and storage device. The iSCSI and TCP/IP protocol functions are
handled by the host HBA, consuming the least CPU resources. This mode delivers the best data
transfer performance but requires the highest cost.
The iSCSI communication system inherits part of SCSI's features. The iSCSI communication
involves an initiator that sends I/O requests and a target that responds to the I/O requests and
executes I/O operations. Acting as the primary device, the target controls the entire process after
a connection is set up between an initiator and a target. Targets include iSCSI disk arrays and
e n
/
m
iSCSI tape libraries.
.c o
The iSCSI protocol defines a set of naming and addressing methods for the iSCSI initiator and
e i
target. All iSCSI nodes are identified by their iSCSI names. The naming method distinguishes
aw
iSCSI names from host names.
u
g .h
ni n
iSCSI uses iSCSI qualified names (IQNs) to identify initiators and targets. Addresses change with
r
the relocation of initiator or target devices, but their names remain unchanged. An initiator delivers
lea
a request. After the target receives the request, it checks whether the iSCSI name contained in
: //
the request is consistent with that bound with the target. If the iSCSI names are consistent, the
t p
connection is set up. Each iSCSI node has a unique IQN name. One IQN name is used while
t
:h
connecting one initiator to multiple targets. Multiple IQN names are used while connecting one
target to multiple initiators.
e s
r c
o u
s
iSCSI encapsulation model
Re
i n gAll SCSI commands are encapsulated into iSCSI PDUs. iSCSI uses
rn
the TCP protocol at the transport layer of the TCP/IP protocol stack
to provide reliable transmission mechanisms for connections.
e a
eL
Ethernet header IP header TCP header Data (iSCSI) FCS
or Source port Destination port Basic header segment (BHS)
M Serial number
Acknowledgment number
Additional header segment (AHS)
Header checksum
Reserved Flags
HELN
(4 bits) (8 bits) Windows size Data segmentation
Checksum Urgent pointer Data checksum
Options and padding

All SCSI instructions are encapsulated into iSCSI Protocol Data Units or PDUs. A PDU is the
basic information unit that is sent. The iSCSI protocol uses the TCP protocol at the transport layer,
providing a reliable transmission mechanism for connections. After TCP segment headers and IP
packet headers are encapsulated, the encapsulated SCSI instructions and data are transparent to
network devices. As a result, network devices send them as common IP packets.
One of the things that gave a lot of SAN administrators an excuse not to use iSCSI is the fact that
Ethernet is not a lossless system (and Fibre Channel is lossless). With a lossless system we
mean that each packet that is transmitted will be guaranteed to arrive at the destination or target.
e n
/
m
For Ethernet that was not the case and as iSCSI relies on Ethernet technology it meant that data
sent from an iSCSI initiator not always reached the destination.
.c o
e i
Why is that ?
aw
u
In the concept of Ethernet there are no limitations on the amount of packets that may be
.h
transmitted. Also there is no way of regulating the number of packets transmitted. When the
g
i n
number is so high that it reaches the maximum throughput of the physical network components
n
r
problems will occur.
// lea
:
An unsuccessful transmission may lead to a new attempt to send the same packets again (and
t p
again). If the capacity of the network remains a bottleneck than the delivery of packets cannot be
t
:h
guaranteed.
e s
c
The last couple of years improvement on the 10 Gbit/s Ethernet standard have lead to the fact
r
ou
that Ethernet now can be a lossless protocol. The improvements all are described in a number of
s
IEEE802.3 additions but the general name of the group of additions that make Ethernet lossless
e
R
is the term Data Center Bridging (DCB). DCB is only available from 10 Gbit/s speeds (and
i n g
higher) so many traditional 1 Gbit/s iSCSI solutions are still not lossless.
r n
a
The hardware for 10 Gb/s has become cheaper over the last year so iSCSI is now a true
e
L
competitor for the traditional Fibre Channel protocol.
e
or
M

Huawei IP SAN storage applications
Module Power Module Handle Module Power Module
n
indicator Indicator Handle
Speed indicator of a
e
10 Gb/s
/
1 Gb/s 1 Gb/s iSCSI port
iSCSI TOE port
m
port
o
Link/Active indicator Link/Speed
.c
of a 1 Gb/s iSCSI indicator of a 10
i
port Gb/s TOE port
we
1 Gb ETH
u a
10 Gb ETH
g
Slide 55 .h
ni n
r
lea
To demonstrate that Huawei fully supports iSCSI in most of their storage devices the above
picture shows an OceanStor S5500 storage array with iSCSI modules.
: //
t t p
:h
A 1 Gb/s iSCSI interface module provides service ports to the storage system for receiving data
s
read/write requests from application servers. Each 1 Gb/s iSCSI interface module houses four 1
e
c
Gb/s iSCSI ports to receive data exchange commands sent by application servers.
r
s ou
A 10 Gb/s TOE interface module provides service ports to the storage system for receiving data
Re
read/write requests from application servers. Each 10 Gb/s TOE interface module houses four 10
i n g
Gb/s TOE ports to receive data exchange commands sent by application servers.
r n
a
In the above picture we see a Huawei storage array with two controllers where each controller
e
e L
has two 10 Gb/s Ethernet I/O modules. Optionally the configuration can be changed in such a
r
way that the same S5500 storage array has both FC and 10 Gb/s IO modules. This offers the
o possibility to mix the technologies.
M Two examples:
1. An infrastructure where the local data center needs to have high performance specifications
but there should also be a copy of all data in a data center on a second site 10 kilometers
away.
For the optimal performance the local data center might be equipped with FC components.
The data could then be copied to a remote site using cost effective Ethernet based networks.

2. The infrastructure demands that the data generated on one site (Main datacenter) gets copied
for security reasons to a second site thousands of kilometers away.
Locally the iSCSI solution might be applied and for the connection to the remote site a high
speed (but very expensive) Fibre Channel based link might be used.
Convergence of Fibre Channel and TCP/IP

e n
/
o m
Convergence of Fibre Channel and TCP/IP
e i .c
aw
u
.h
Fibre Channel and TCP/IP can be converged in two ways:
1. Fibre Channel channels carried over a TCP/IP network.

FCIP.
i n g
iFCP.
r n
lea
FCoE.
2. TCP/IP data carried over Fibre Channel channels.

: //
IPFC.
t t p
:h
Ethernet technologies and Fibre Channel technologies are both
e s
developing fast. IP SANs and Fibre Channel SANs currently coexist
and will continue to serve as complements to each other for the
foreseeable future.
r c
s ou
Re
i n g
n
The term convergence is here used to indicate a system that both uses the FC as well as the
r
a
iSCSI protocol. A couple of combinations are possible: put SCSI packets inside of a FC frame or
e
L
put FC packets inside an Ethernet frame.
e
or
Out of the four methods (FCIP, IFCP, FCoE and IPFC) the one that is used most is FCoE. This
Mstands for Fibre Channel over Ethernet. The FCoE standard is getting more popular as with FCoE,
Fibre Channel becomes another network protocol running on Ethernet, alongside traditional IP
traffic. The fact that now one switch (Ethernet) can be used to transport both FC as well as IP
information is a cost effective solution.

FCoE protocol
The FCoE protocol is used to transmit Fibre Channel signals over a

lossless enhanced Ethernet.
FCoE encapsulates Fibre Channel data frames into Ethernet packets

and allows service traffic on a LAN and a SAN to be concurrently
transmitted over the same physical interface.
e n
/
Ethernet data link layer frame
m
Service flow IP address
Block storage FCoE
.c o
Internet telephony VoIP
e i
Video stream VoIP
aw
u
g
Slide 57 .h
ni n
r
lea
Fibre Channel over Ethernet (FCoE) provides services specified by Fibre Channel standards,
//
including discovery, global naming, and zoning. These services run in the same way as the
:
t
original Fibre Channel services with low latency and high performance.
t p
s :h
Note:
r c e
ou
VoIP = Voice over IP. A method to transmit audio and or video for digital telephony over an
Ethernet network.
es
R
i n g
r n
e a
e L
or
M

Questions
Questions
1. What five specifications identify a Storage Area Network?
2. What methods can be used to define zoning in a FC switch?
3. What is a transceiver?
e n
/
4. What are the differences between an IP SAN and a Fibre Channel SAN?
o m
.c
5. What are the main components of an IP SAN?
6. What are the functions of the iSCSI initiator and target?

e i
aw
u
g .h
ni n
r
lea
: //
t t p
1. Scalable in number of components; scalable geographical, reliable, flexible, heterogeneous,
:h
easy to manage
e s
2. Port zoning; World Wide Name zoning and Alias zoning
r c
3. A module in a switch; Host Bus Adapter or storage device that holds a light source and a
ou
photoelectric sensor. It is used to create an optical signal from an electrical signal and vice
versa.
es
R
4. IP SANs use a single fabric; are Ethernet based; requires little training to master ; speeds of
i n g
up to 40 Gbit/s; relatively cheap to implement. FC SANs use dual fabrics with dedicated
r n
networks; requires training to master; speeds up to 16 Gbit/s; FC components are more
e a
expensive
L
5. Host with Ethernet network interface; multiple Ethernet switches that are connected with each
e
or other; Ethernet type CAT cable; Storage devices with Ethernet interfaces.
M
a. Network Interface Connector. Already present in most hosts. Software, running on the
hosts CPU, is used to encapsulate the payload with iSCSI+TCP+IP information
b. TCP/IP Offload Engine. A dedicated I/O card that performs the encapsulation of TCP +
IP.The software in the host still is involved in iSCSI encapsulation
c. iSCSI Host Bus Adapter. A dedicated I/O card that performs all encapsulation tasks and
forwards the relevant SCSI data to the host CPU
6. The initiator is responsible for the selection of the destination device in a IP connection. The
target is the device that controls the connection after it has been established.

Exam Preparation
Exam Preparation
1. Statement 1: In IP SANs two switches are used for redundancy

and for creating two fabrics.
Statement 2: A host can be part of multiple zones in a FC switch.

e n
a. Statement 1 is true; Statement 2 is true. /
b. Statement 1 is true; Statement 2 is false.
o m
c. Statement 1 is false; Statement 2 is true.
d. Statement 1 is false; Statement 2 is false.
e i .c
2. Which of the following characteristics are applicable to FC SANs.
aw
Select all that apply.
u
.h
a. Lossless protocol. d. Up to 16.77 million devices.
g
b. Single fabric. e. Speeds up to 10 Gb/s.
c. IQN zoning.
ni n
f. Design should include SPOFs.
r
lea
: //
t t p
Exam Preparation h
s :
r c e
u
3. iSCSI Host Bus Adapters are used because they offload the
o
CPU of the host of all the work needed to encapsulate iSCSI
s
packets in Ethernet frames. True or false?
Re
4. Statement 1 : E_Ports are FC ports in a host that connects to a
i n g switch.
Statement 2 : Every interface in a FC switch has a unique
r n World Wide Port Name assigned to it. The
e a switch chassis itself has a unique World Wide
L
Node Name.
r e a) Statement 1 is true; Statement 2 is true.
o b) Statement 1 is true; Statement 2 is false.
M c)
d)
Statement 1 is false; Statement 2 is true.
Statement 1 is false; Statement 2 is false.
Answers:
1. C, 2. A + D, 3. True, 4. C.

Summary
Summary
Essential parameters of a SAN.

scalable in size and distance, reliable, flexible.
Components and networking of a FC SAN.

e n
dual fabric, zoning, fiber optical cable, HBA/transceiver.
/
Fibre Channel protocol, FC Frame, Port types (F, N, L, FL, E, G).
o m
Components and networking of an IP SAN.
single fabric, NIC / TOE / iSCSI HBA.
e i .c
iSCSI frame.
aw
u
Convergence of Fibre Channel and TCP/IP.
FCoE.
g .h
ni n
r
lea
: //
t t p
s :h
r c e
s ou
Re
i n g
r n
e a
e L
or
M

Thank you
www.huawei.com
e n
/
o m
e i .c
aw
u
g
Slide 62 .h
ni n
r
// lea
p :
t t
s :h
r c e
s ou
Re
i n g
r n
e a
e L
or
M

e n
/
o m
e i .c
aw
u
g .h
ni n
r
// lea
p :
t t
s:h
r c e
sou
Re
i n g
r n
e a
e L
or
M

e n
/
o m
e i .c
aw
u
OHC1109105
g .h
RAID Technology
ni n
r
// lea
p :
t t
:h
es
www.huawei.com
r c
sou
Re
i n g
r n
e a
e L
or
M
e n
/
o m
e i .c
aw
u
g .h
ni n
r
// lea
p :
t t
s:h
r c e
sou
Re
i n g
r n
e a
e L
or
M
Introduction
In this chapter the focus is on the data protection methods used in storage devices based on hard
disks. As the data generated in an organization is important data protection must be implemented in
case the physical disk, on which the data is stored, fails.
e n
Objectives
/
o m
.c
Explain the most common RAID types.
e i

aw
Understand what level of data protection is offered with the various RAID types.
u

.h
Understand the relation between the RAID levels and properties like performance, security
g
and cost.
ni n
r
// lea
Module Contents
p :
t t
:h
1. Traditional RAID.
e s
c
2. Basic concepts and implementation modes of RAID.
r
ou
3. RAID technology and application.
es
4. RAID data protection.
R
i n g
5. Relationship between RAID and LUNs.
r n
e a
e L
or
M
HCNA-storage V3 | OHC1109105 RAID Technology Page | 175

e n
/
o m
e i .c
aw
u
g .h
ni n
r
// lea
p :
t t
s:h
r c e
sou
Re
i n g
r n
e a
e L
o r
M
Page | 176 HCNA-storage V3 | OHC1109105 RAID Technology

Traditional RAID
In this module we will look at the data protection system called Redundant Array of
Independent Disks (RAID). RAID has two different version or generations. This module
covers the traditional version of RAID. Here the RAID is based on protecting data that is disk
based. In other words: if a disk fails, how can I make sure that the data on that disk is
recovered.
The advanced RAID 2.0+ technology used in Huaweis enterprise class storage arrays is
e n
covered in module 9. /
o m
Basic concepts and implementation modes of RAID e i .c
aw
hu
.
Basic concepts and implementation modesgof RAID
nin
ar
/ l e
RAID: short for redundant array of independent disks
: /
also referred to as disk array.
t tp
: hRAID
e s
r c
o u
es
Implementation methods:
R Hardware RAID.
i n g Software RAID.
r n
e L
or The first idea behind RAID was to combine multiple smaller disks together to get a bigger capacity.
M Today the term RAID is used more in relation to data protection, in other words RAID can be used to
prevent data loss in case a physical device fails.
Over the years there have been a number of RAID types, but just a small number is still in use. In this
module we will discuss the most commonly used RAID types. We will also look at other factors than
data protection because choosing a RAID type has consequences for the performance and/or for the
cost of the RAID solution.

In practice RAID can be implemented in two modes: hardware RAID and software RAID.
Hardware RAID uses a dedicated RAID adapter, RAID controller or Storage Processor. The
RAID controller has its own processor, I/O processing chip, and memory, improving resource
utilization and data transfer speed. The RAID controller manages routes, the buffer, and data
flow between hosts and the disk array.
Software RAID does not have its own processor or I/O processing chip and is fully dependent
on the host CPU. Therefore, low-speed CPUs can hardly meet the requirements for RAID
e n
implementation. Software RAID is not used much in Enterprise solutions as the performance
/
of hardware RAID is typically better than the performance of software RAID.
o m
e i .c
Data Organization modes of RAID
aw
u
g .h
Data organization modes of RAID
ni n
r
lea
Stripe unit or Chunk size: smallest amount of data written on a disk before
//
selecting another disk.
p :
t
Strip: logical grouping of a number of stripe units or chunks.
t
:h
Stripe: strips with the same stripe numbers (i.e. D3, D4, D5) on multiple disks
s
in a disk array.
r c e
Stripe depth or Stripe width: the amount of disks that form the stripe or the
ou
total amount of space stored in a stripe. #disks x chunk size (kB).
es Disk 1 Disk 2 Disk 3

Strip
R D6 D7 D8 Chunk
ing
D3 D4 D5
Stripe
rn
D0 D1 D2
e a
eL
or
M
Stripe unit or chunksize: amount of data that will be written in one instance before the next
instance gets written to another disk.
Strip: a number of stripe units that are logically grouped together.
Stripe: all chunks in a RAID set that are on the same stripe i.e. that have the same stripe number.
Stripe width: Capacity of a stripe (#disks x chunk size) or the amount of disks that form the stripe.

Parity mode of RAID
Parity mode of RAID
XOR or eXclusive OR is a logical function used with digital electronics

and in computer science. The output is true if only one of the inputs is
true. If both inputs are the same (true or false) than the output is false.
XOR: true whenever the inputs differ and false whenever the inputs
e n
are the same. The symbol for the XOR operation is .
/
0 0 = 0, 0 1 = 1, 1 0 = 1, 1 1 = 0
o m
Disk 1 Disk 2 Parity disk
e i .c
1 1 0
aw
u
0 1 1
.h
0 0 0
XOR redundancy backup
i n g
r n
lea
: //
t t p
There are two different ways RAID can be used to protect data. One way is to keep identical copies of
:h
the data on another disk. The second way is using a concept called Parity. The parity is extra
e s
information calculated using the actual user data. For the RAID types that use parity it means that
r c
extra disks are needed. Parity is calculated using the exclusive or (XOR the symbol is) function.
s ou
The output of an XOR system is shown in the following table.
Input A R
e AB
g
Input B
i n
arn 0 0 0
L e
r e 1 0 1
o
M 0 1 1
1 1 0

RAID status
RAID status
RAID
group Creation succeeded
created
e n
RAID
/
m
group
o
Reconstruction succeeded working
.c
correctly
i
RAID
e
group
failed
RAID group
A member disk is offline
aw
u
or has failed
degraded
# failed disks > # hot spare disks
g .h
ni n
r
Slide 7
// lea
p :
Providing there are multiple disks used together to form a RAID protected group (sometimes called a
RAID set) this group has a status.
t t
s :h
1. Everything is working as planned. The status is referred to as NORMAL.
r c e
2. A hardware failure has occurred, but the system is able to present all the data. No recovery
ou
procedures have started (yet). The status is called DEGRADED.
es
R
3. After a hardware failure the recovery process has started, but it has not finished yet. The status is
g
referred to as REBUILDING (or reconstructing).
n i n
4. After a hardware failure there are no recovery options available and the data cannot be presented
ar
in a correct way anymore. The status is called FAILED.
L e
Whether or not a degraded RAID group can be reconstructed depends on the RAID type used, the
r e
number of hardware failures and the availability of recovery hardware.
o
M

RAID technology and application
Common RAID levels and classification criteria
Common RAID levels and classification criteria

e n
/
o m
RAID technology combines multiple independent physical disks into
a logical disk in different modes. Corresponding to these modes,
e i .c
w
RAID levels are formed. This mechanism improves the read/write
performance of disks while increasing data security.
u a
RAID 0
RAID 6
g .h
ni n
r
Common RAID RAID 10
lea
levels
RAID 1
//
RAID 50
RAID 3
p :
t t RAID 5
:h
es
r c
s ou
Re
Advantages of RAID technology:

i n g
Combines multiple disks into a logical disk to provide storage capacity as one entity.
r n

e a
Divides data into data blocks and writes/reads data to/from multiple disks in parallel,
e L improving disk access speed.
or Provides fault tolerance by offering mirroring or parity check.

Working principle of RAID 0
D0
e n
D5 D0, D1, D2, D3, D4, D5
/
D4
o m
i .c
D3
e
Disk 1 Disk 2
D2 D6
w
D4 D5 Stripe 2
D1
a
D2 D3 Stripe 1
u
D0
.h
D0 D1 Stripe 0
Data blocks on disks
g
Data blocks on disks
i n
Logical disk Striped disk array without error control
r n
lea
: //
t t p
RAID 0 (also referred to as striping) has the highest storage performance of all RAID levels. RAID 0
:h
uses striping technology to distribute data among all disks in the RAID group.
e s
A RAID 0 group contains at least two member disks. RAID 0 group divides data into data blocks of
r c
ou
sizes ranging from 512 bytes to megabytes (usually integral multiples of 512 bytes), and writes them
s
onto different disks in parallel. For example: The first data block is written onto disk 1, and the second
Re
onto disk 2 of Stripe 0. After the data block is written onto the last disk of Stripe 0, the next data block
g
is written onto the next stripe (Stripe 1) on disk 1. In this way, I/Os are load balanced to all disks in
the RAID group.
n i n
ar
The disk appears to offer a single big capacity and still has the benefits of being very fast. Before
L e
RAID 0 was used there was a technique which was similar to RAID 0 called JBOD. A JBOD (short for
r e
Just a Bunch Of Disks) is a group of disks concatenated to form a virtual bigger disk. The big
o
difference with RAID 0 is that with a JBOD the blocks are not written to disks at the same time. In a
M
JBOD the first disks will be used until it is full. Then the second disk will be used. So the total
available capacity is the sum of the capacity of the individual disks, but the performance is the
performance of a single disk! JBODs are not considered to be a RAID implementation.

Data write of RAID 0
Writing D2, D3,...
Writing D1
Writing D0
e n
/
m
D5 D0, D1, D2, D3, D4, D5
D4
.c o
D3
D2 Disk 1 Disk 2
e i
D1 D4 D5
aw
u
D0 D2 D3 Stripe 1
.h
D0 D1 Stripe 0
g
Logical disk
ni n
r Slide 10
// lea
p :
RAID 0 uses striping technology to write data onto all disks. It divides the data into data blocks and
t t
evenly distributes them among all disks in the RAID group. Data is written onto the next stripe only
:h
when the data is written onto all blocks in the previous stripe. In the figure, data blocks D0, D1, D2,
s
r c e
D3, D4, and D5 are waiting to be written onto disks in RAID 0. D0 will be written onto the block in the
ou
first stripe (Stripe 0) on disk 1 and D1 onto the block in the first stripe on disk 2. Then, data will be
s
written onto all blocks in the second stripe. D2 will be written onto the next stripe, that is, the block in
e
the second stripe (Stripe 1), on disk 1, D3 will be written onto a block in stripe1 on Disk 2. The same
R
g
method will be applied for D4 and D5 but now of course on stripe 2 across the two disks.
n i n
The write performance of a RAID 0 set is proportional to the number of disks.
ar
L e
r e
o
M

Data read of RAID 0
Data read of RAID 0
Reading D2, D3,...
Reading D1
Reading D0
e n
/
m
D5 D0, D1, D2, D3, D4, D5
D4
.c o
D3
D2 Disk 1 Disk 2
e i
D1 D4 D5
aw
u
D0 D2 D3
.h
D0 D1
g
Logical disk
ni n
r
Slide 11
// lea
p :
t t
:h
When a RAID 0 receives a data read request, it searches for the target data blocks on all disks and
s
reads data across stripes. In the figure, we can see the entire read process.
e
r c
A request of reading data blocks D0, D1, D2, D3, D4, D5 is received. D0 is read from the disk 1, D1
ou
from the disk 2, and the other data blocks are also read. After all data blocks are read from the disk
es
array, they are integrated by using the RAID controller and then sent to the host.
R
i n g
n
The read performance of a RAID 0 set is proportional to the number of disks.
ar
L e
r e
o
M

Data loss of RAID 0
Data loss of RAID 0
Data on the disk array is lost if any of the disks in the disk array fails.
e n
/
o m
e i .c
Disk 1 Disk 2 Disk 3
aw
u
D6 D7 D8
.h
D3 D4 D5
D0 D1 D2
i n g
r n
Slide 12
// lea
p :
t t
:h
RAID 0 only organizes data in a certain way but does not provide data protection. If any of the disks in
s
the RAID group becomes faulty, the entire RAID group fails. This is of course not a physical failure of
e
c
the RAID group but a logical. If files are stored on a RAID 0 based volume it means the data blocks
r
ou
that form that file are stored on all disks of the RAID 0 set. If a single disk fails the other disks still
s
have their data blocks. The file itself now is no longer complete because some of the blocks it uses
e
R
are no longer available. So maybe it is better to say that the data is incomplete. For most files and file
i n g
systems however we would not be able to access the files anymore. These files would be most likely
n
be reported as being corrupt files.
ar
L e
e
In enterprise solutions the use of RAID 0 is very limited. The data is often so important that a form of
or data protection is needed. Yes, of course there is always the necessity for physical backups but these
M take time to make and it takes time for the data to be restored.
A use for RAID 0 would be were file access performance should be very high and at the same time
the restore time, in case of a problem, is allowed to be long (Text documents, public images, audio
files that can easily be recreated or recovered).

e n
D0, D1, and D2 passing through a mirror
/
m
D2
.c o
i
D1
Disk 1 Disk 2
D0
D2 D2
we
a
D1 D1
u
.h
D0 D0
g
Logical disk Disk array with mirroring
ni n
r
Slide 13
// lea
p :
RAID 1 (also referred to as mirroring) aims to build a RAID level with super high security. RAID 1 uses
t t
two identical disk systems and builds a mirror setup. Data is written onto one disk and a copy of the
:h
data is stored on the mirror disk. When the source disk (physical) fails, the mirror disk takes over
s
r c e
services from the source disk, ensuring service continuity. The mirror disk acts as a backup and as a
ou
result, the highest data reliability is offered.
es
R
Another limitation is the fact that a RAID 1 set can only store data based on the capacity of the single
i n g
disk. The other disk simply holds the copy of the data. For every gigabyte stored there is 2 gigabyte of
r n
hard disk space used. This so-called overhead is 100%.
e a
The two disks in a RAID 1 set must be identical in size. If they are different in size the available
e L
capacity is the capacity of the smaller of the two disks.
o r
M

Writing D2
Writing D1
Writing D0
e n
/
m
D0, D1, D2
D2
.c o
D1
e i
w
Disk 1 Disk 2
a
D0 D2 D2
u
.h
D1 D1
g
Logical disk D0 D0
ni n
r Slide 14
// lea
p :
Unlike RAID 0, which uses striping technology to write data onto all disks, RAID 1 simultaneously
t t
writes the same data onto each disk so that data is identical on all member disks. In the figure, data
:h
blocks D0, D1, and D2 are waiting to be written onto the disks. D0 and D1 are both simultaneously
s
r c e
written onto the two disks (disks 1 and 2). Then, other data blocks are written onto the two disks in the
ou
same manner.
es
R
The write performance of a RAID 1 system is the performance of the single disk.
i n g
r n
e a
e L
or
M

Data read of RAID 1
Data read of RAID 1
Reading D2
Reading D1
n
Reading D0
/ e
m
D0, D1, D2
o
D2
D1
Disk 1 Disk 2
e i .c
D0 D2 D2
aw
D1
u
.h
D1
D0 D0
g
Logical disk
ni n
r
Slide 15
// lea
p :
t t
RAID 1 simultaneously reads data from the data and mirror disks, improving read performance. If one
:h
of the disks fails, data can be read from the other disk.
e s
r c
ou
The read performance of a RAID 1 system is equal to the performance of both disks combined. In
s
case the RAID set is degraded the performance is halved.
e
R
i n g
r n
e a
e L
o r
M

Data recovery of RAID 1
e n
/
m
D0, D1, D2
Replacing/Recovering
the disk
Reading/Writing
the backup disk
.c o
Disk 1 Disk 2
e i
D2 D2
aw
D1 D1
u
D0 D0
g .h
n
Disk damaged Backing up disk data
ni
r Slide 16
// lea
p :
Member disks of RAID 1 are mirrored and have the same content. When one of the disks becomes
t t
faulty, data can be recovered using the mirror disk. In the figure, disk 1 fails and data on it is lost. We
:h
can replace disk 1 with a new one and replicate data from disk 2 to the new disk 1 to recover the lost
s
r c e
data. In most storage solutions this rebuild process after the faulty disk has been replaced is an
ou
automatic process.
s
An important consideration is that the RAID 1 set is in degraded state as long as the new disk has not
e
been rebuilt completely. Especially in these days where the capacity of individual disks is very high
R
g
this rebuild time can be long. The table below shows some examples of rebuild times.
n i n
r
DISK SIZE REBUILD TIME (HOURS)
e a
L
72 GB < 1 hr
r e 146 GB < 4 hrs

o
M 600 GB <8
1 TB < 20 hrs
4 TB < 48 hrs
Note: These rebuild times are depending on RAID controller type and workload on the system!

n
D0, D1, D2, D3, D4, D5, D6, D7, D8
/ e
Parity codes generated
o m
.c
Disk 1 Disk 2 Disk 3 Parity disk
D6 D7 D8 P3
e i
D3 D4 D5 P2
aw
u
D0 D1 D2 P1
Striped disk array with parity codes.
g .h
ni n
r
Slide 17
// lea
p :
t t
:h
RAID 3, which is loosely based on RAID 0, is referred to as striping with dedicated parity. Data is now
s
written to the data disks of the RAID 3 set (here disk 1-2-3). The blocks from disks 1, 2 and 3 are (at
e
c
byte-level) used to calculate a parity value. That value is stored on a dedicated parity disk. If any
r
ou
incorrect data is detected or a disk becomes faulty, we can recover the data on the faulty disk using
s
the parity check information. RAID 3 is applicable to data-intensive or single-user environments that
e
R
need to access long and continuous data blocks. RAID 3 distributes data write operations to multiple
i n g
disks. However, RAID 3 needs to recalculate and possibly rewrite the information on the parity disk no
n
matter onto which disk new data is written. As a result, for the applications that produce a large
ar
number of write operations, the parity disk will have heavy workloads. That may have a consequence
L e
for the performance when one has to wait for the parity disk. Also, because it has much higher
r e
workloads, it is often the disk that fails first in a RAID 3 set. That is why the parity disk in RAID 3 is
o
often called a hot spot.

Writing C
Logical disk
Writing B
Writing A
e n
/
C
m
A0, A1, A2, B0, B1, B2, C0, C1, C2
.c o
e i
Parity disk
w
A C0 C1 C2 P3
B0 B1 B2
u a
P2
.h
A0 A1 A2 P1
i n g
r n Slide 18
// lea
p :
RAID 3 adopts single-disk fault tolerance and parallel data transfer. In other words, RAID 3 employs
t t
striping technology to divide data into blocks, implements the XOR algorithm for these blocks, and
:h
writes the parity data onto the last disk. One of the disks in the RAID group functions as the parity disk.
s
r c e
When a disk becomes faulty, data is written onto other disks that are not faulty and the parity check
ou
continues.
es
R
The performance of a RAID 3 set is not a fixed number. In principle RAID 3 is an N+1 data protection
i n g
method. That means that when there are N disks, with user data you want to protect, one extra disk is
r n
needed to store the parity information. In that situation new data blocks will be written to N disks
e a
simultaneous. After the parity information is calculated that will be written to the parity disk.
e L
However: there is a situation that happens quite often. This situation is when there is so little new data
or it can fit on one or two disks. Normally all N disks would cooperate in the striping process, now there
M is just a few disks involved. The problem now is that we still have to read all disks (or better the data
in the stripe of the disks) to be able to recalculate the new parity value. This of course makes that
writing small amounts of data does not benefit from having many disks in the RAID 3 set. This is
known as the write-penalty with RAID 3.
The write performance of a RAID 3 set is depending on the amount of changed data; the number of
disks minus the time needed to calculate and store the parity information.

Data read of RAID 3
Data read of RAID 3
Logical disk
Reading data
e n
C
/
m
A0, A1, A2, B0, B1, B2, C0, C1, C2
.c o
Disk 1 Disk 2 Disk 3 Parity disk
e i
w
A C0 C1 C2 P3
B0 B1 B2 P2
u a
.h
A0 A1 A2 P1
i n g
r n
Slide 19
// lea
p :
t t
:h
In RAID 3, data is read in stripes across the disks. The disk motor of each disk in a RAID group is
s
controlled such that data blocks in the same stripe on all disks can be read at the same time. By doing
e
c
so, each disk is fully utilized and read performance is boosted. RAID 3 uses the parallel data read
r
ou
(and write) mode.
es
R
g
The read performance of a RAID 3 set is depending on the amount of data read and the number of
disks in the set.
n i n
ar
L e
r e
o
M

Data recovery in RAID 3
Logical disk
e n
/
C
A0, A1, A2, B0, B1, B2, C0, C1, C2
o m
.c
B

e i
Parity disk
w
A
a
C0 C1 C2 P3
u
B0 B1 B2 P2
.h
A0 A1 A2 P1
Disk failure
i g
Data recovery
n
r n Slide 20
// lea
p :
For data recovery, RAID 3 implements XOR operations for all the disks including the parity disk to
recover the lost data on the faulty disk.
t t
s :h
As shown in the figure, when disk 2 fails, data blocks A1, B1, and C1 on disk 2 are lost. To recover
c e
these data blocks, we should first recover A1, which can be obtained by applying XOR operations to
r
ou
A0, A2, and P1 on disk 1, disk 2 and the parity disk. B1 and C1 are also recovered using the same
s
method. In the end, all the lost data on disk 2 is recovered.
e
R
However, all parity check operations run on a single disk causing heavy write pressure onto the parity
i n g
disk during data recovery and decreasing RAID group performance.
r n
e a
RAID 3 is supported with Huawei but in practice it is not used a lot nowadays. Two disadvantages
e L
exist: data is written simultaneous to all disks, but also read simultaneous. This requires the disks to
or rotate at the same speed all the time. This requires spindle-synchronization and that has proven to be
M
a technical challenge for disk manufacturers. Second disadvantage is the byte-level approach. It is a
very small part of the disk capacity that today has become very high. That is why in fact RAID 4 has
replaced RAID 3 somewhat. RAID 4 does not require spindles to run synchronized and the parity is
now calculated using a bigger sized data block. Still RAID 4 has the bottleneck of the hot spot with
the dedicated parity disk! So an improved RAID type was introduced: RAID 5.

e n
D0, D1, D2, D3, D4, D5
/
o m
e i .c
w
P2 D4 D5
D2 P1 D3
u a
.h
D0 D1 P0
Independent disk structure with distributed parity check codes.
i n g
r n
Slide 21
// lea
p :
RAID 5 is the improved version of RAID 3 and RAID 4. It also uses striping and it also calculates
t t
parity information. In RAID 3/4 the parity had to be written to (or read from) a dedicated disk. That led
:h
to the hot spot situation we mentioned before and an impact on the performance. In RAID 5 they use
s
r c e
so-called distributed parity. It means that each disk will be used to store user data nd parity
ou
information. Then writing new data involves all disks for user data and also involves all disks for
s
storing parity information. So there are no bottlenecks or hotspots.
Re
In RAID 5 out of N disks in a RAID 5 group the capacity of N-1 disks is available. As with other RAID
i n g
systems the disks in a RAID 5 set should be identical.
r n
In both RAID 3/4 and RAID 5, if a disk fails, the RAID group transforms from its online state to the
e a
degraded state until the failed disk is rebuilt. However, if another disk in a degraded RAID group fails,
L
all data in the RAID group will be lost.
e
o r
M

n
Logical disk
D5
/ e
m
D0, D1, D2, D3, D4, D5
o
D4
.c
D3
D2
e i
w
D1
a
P2 D4 D5
u
D0
D2 P1 D3
D0 D1
g
P0
.h
ni n
r Slide 22
// lea
p :
t t
:h
In RAID 5, data is also written in stripes across the disks. Each disk in the RAID group stores both
s
data blocks and parity information. After data blocks are written onto a stripe, the parity information is
e
c
written onto the corresponding parity disk. For each consecutive write to other stripes the disk used to
r
ou
store the parity is a different one.
es
Just as with RAID 3/4 there is a write penalty with RAID 5 when a small amount of data is written.
R
i n g
n
The write performance of a RAID 5 set is depending on the amount of data written and the number of
ar
disks in the RAID 5 set.
L e
r e
o
M

Data read of RAID 5
Data read of RAID 5
n
Logical disk
D5 / e
m
D0, D1, D2, D3, D4, D5
o
D4
D3
D2
e i .c
D1
P2 D4 D5
aw
u
D0
D2 P1 D3
D0 D1 P0
g .h
ni n
r
Slide 23
// lea
p :
Data is stored as well as read in stripes across the disks. For each read N-1 disks can be used to
retrieve the data.
t t
s :h
r c e
The read performance of a RAID 5 set is depending on the amount of data written and the number of
ou
disks in the RAID 5 set.
es
R
i n g
r n
e a
e L
o r
M

Logical disk
e n
D5
/
m
D0, D1, D2, D3, D4, D5
o
D4
i .c
D3
D2
D1
Disk 1
P2
Disk 2 Disk 3
we
a
D4 D5
u
D0 D2 P1 D3
.h
D0 D1 P0
Disk failure
g
Data recovery
i n
r n Slide 24
// lea
p :
When a disk in RAID 5 fails, XOR operations are implemented for the other member disks to recover
data on the failed disk.
t t
s :h
r c e
However, with RAID 5 it is not so that all parity check operations run on a single disk like with RAID 4.
ou
So rebuilding a new disk to replace the faulty disk with RAID 5 does not cause the heavy write
pressure that RAID 3/4 has.
es
R
i n g
r n
e a
e L
or
M

Overview of RAID 6
Overview of RAID 6
RAID 6:
Is an independent disk structure with two parity modes.

n
It requires at least N+2 (N > 2) disks to form an array.
Is applicable to scenarios that have high requirements for data reliability
/ e
m
and availability.
.c o
i
Frequently used RAID 6 technologies are:
RAID 6 P+Q.
we
RAID 6 DP.
u a
g .h
ni n
r
Slide 25
// lea
p :
The RAID types discussed until now provided data protection when a single disk is lost. That is of
t t
course with the exception of RAID 0. Over the years the capacities of disks have increased a lot and
:h
with that the rebuild times. If there are many big disks combined to form a RAID 5 set then the rebuild
s
r c e
of the failed disks may take days instead of hours. In this period the system is in a degraded state and
ou
any additional disk failure will result in a failed RAID set and loss of data.
s
That is why some organizations require a system that is dual redundant. In other words: two disks
e
should be allowed to fail and still all data should be accessible. There are a few implementations of
R
g
such dual redundant data protection types:
n i n
N-way mirroring is the method where each written block to the main disks leads to multiple copies of
ar
the blocks on multiple disks. This of course means a lot of overhead.
L e
r e
o
RAID 6 offers protection against two disks failing in a RAID 6 set. These disks can even fail exactly at
M
the same time.
The official name for RAID 6 is striping with distributed dual parity. In essence it is an improved
version of RAID 5 that also did striping and distributed parity. Now in RAID 6 there is dual parity. That
means two things:
1. In additional to writing the user data two parity calculations have to be made. RAID 6 is in that
respect the slowest of all RAID types.
2. This additional parity information costs space. That is why we refer to RAID 6 as an N+2 type.

Currently, RAID 6 does not have a uniform standard. Companies implement RAID 6 in different ways.
The following two are the major implementation modes:
RAID P+Q: Huawei, HDS.
RAID DP: NetApp.
These two modes differ in the methods of obtaining parity data. Nevertheless, they can both ensure
data integrity and support data access in case of double-disk failure in the RAID group.
e n
/
o m
e i .c
aw
u
g .h
For RAID 6 P+Q, two parity data, P and Q, are calculated. When two
data blocks are lost, they can be recovered by using the parity data.
ni n
r
lea
P and Q are calculated using the following formulas:
P = D0 D1 D2
//

Q = ( D0) ( D1) ( D2)
p :
t t
:h
Disk 1 Disk 2 Disk 3 Disk 4 Disk 5
es
P1 Q1 D0 D1 D2 Stripe 0
c
D3 P2 Q2 D4 D5 Stripe 1
r
ou
D6 D7 P3 Q3 D8 Stripe 2
D9 D10 D11 P4 Q4 Stripe 3
e
Q5
s D12 D13 D14 P5 Stripe 4
R
ing
arn
L e
In RAID 6 P+Q, P and Q are two parity values independent from each other. They are obtained using
different algorithms to data in the same stripe on all the disks.
r e
o P is obtained from the simple XOR operation implemented for the user data blocks in a single stripe.
M Q is calculated using a process called GF conversion (GF = Galois Field). In the picture above the
Galois field values are represented with , and . The resulting value is a so-called Reed-Solomon
code. The algorithm converts all data in the same stripe on all data disks and implements XOR for
those converted data.
As shown in the figure, P1 is obtained from the XOR operation implemented for D0, D1, and D2 in
stripe 0, P2 from the XOR operation implemented for D3, D4, and D5 in stripe 1, and P3 from the
XOR operation implemented for D6, D7, and D8 in stripe 2.

Q1 is obtained from the XOR operation implemented for GF-converted D0, D1, and D2 in stripe 0, Q2
from the XOR operation implemented for GF-converted D3, D4, and D5 in stripe 1, and Q3 from the
XOR operation implemented for GF-converted D6, D7, and D8 in stripe 2.
If a disk in a stripe fails, only the value P is required to recover data on the failed disk. XOR
operations are performed between P and data on the other disks. If two disks in a stripe fail, handling
methods will vary according to two scenarios. If Q is on either of the failed disks, data can be can
recovered on the data disk first and then the parity information on the parity disk. If Q is on neither of
n
the failed disks, the two formulas are used to recover data on both failed disks.
/ e
o m
e i .c
aw
u
.h
i n g
DP means double parity. RAID 6 DP adds a diagonal XOR parity disk based
r n
lea
on the row XOR parity disk used by RAID 4.
//
P0 to P3 on the row parity disk are the parity information of row data blocks
on all data disks. For example, P0 = D0 XOR D1 XOR D2 XOR D3.
p :
t t
DP0 to DP3 on the diagonal parity disk are the parity information of diagonal
:h
data on all data disks and the row parity disk. For example, DP0 = D0 XOR
D5 XOR D10 XOR D15.
e s
r c Row parity Diagonal
ou
Disk 1 Disk 2 Disk 3 Disk 4 disk parity disk
D0 D1 D2 P0 DP0 Stripe 0
s
D3
e
D4 D5 D6 D7 P1 DP1 Stripe 1
D8
R D9 D10 D11 P2 DP2 Stripe 2
ing
D12 D13 D14 D15 P3 DP3 Stripe 3
rn
e a
e L
RAID 6 DP also has two types of independent parity data blocks. The first parity information is
o r
identical with RAID 6 P+Q. The second one is different from RAID 6 P+Q: the parity is calculated
M
diagonally. Both the row and diagonal parity data blocks are obtained using XOR operations. For row
parity, P0 is obtained from the XOR implemented for D0, D1, D2, and D3 in stripe 0, P1 from the XOR
implemented for D4, D5, D6, and D7 in stripe 1, and so on. That is, P0 = D0 D1 D2 D3, P1 =
D4 D5 D6 D7 etc.
Diagonal parity implements XOR operations to diagonal data blocks. The data block selection process
is complicated. DP0 is obtained from the XOR operation implemented for D0 on disk 1 in stripe 0, D5
on disk 2 in stripe 1, D10 on disk 3 in stripe 2, and D15 on disk 4 in stripe 3. DP1 is obtained from the
XOR operation implemented for D1 on the disk 2 in stripe 0, D6 on disk 3 in stripe 1, D11 on disk 4 in

stripe 2, and P3 on the parity disk in stripe 3. DP2 is obtained from the XOR operation implemented
for D2 on the disk 3 in stripe 0, D7 on the disk 4 in stripe 1, P2 on the parity disk in stripe 2, and D12
on the disk 1 in stripe 3, and so on. That is, DP0 = D0 D5 D10 D15, DP1 = D1 D6 D11
P3 etc.
RAID 6 DP is tolerant to double-disk failure in an array. For example, If disks 1 and 2 fail in the above
figure, D0, D1, D4, D5, D8, D9, D12, and D13 are lost.
Data and parity information on other disks are valid. Let's have a look at how data is recovered. First,
recover D12 by using DP2 and diagonal parity (D12 = D2 D7 P2 DP2).
e n
/
Then recover D13 by using P3 and row parity (D13 = D12 D14 D15 P3), D8 by using DP3
o m
.c
and diagonal parity (D8 = D3 P1 DP3 D13), D9 by using P2 and row parity (D9 = D8 D10
e i
D11 P2), D4 by using DP4 and diagonal parity, D5 by using P1 and row parity, and so on.
These operations are repeated until all data on disks 1 and 2 is recovered.
aw
u
g .h
n
The performance of a RAID 6 system is relative slow for all types DP or P+Q. It is therefore that RAID
6 is used in two situations:
ni
r
lea
1. The data is very valuable and needs to be online and available as long as possible.
: //
2. The disks used are very big (typically over 2 TB). At those capacities the rebuild times
t p
become so long that the chance of losing a second disk is a real threat. With RAID 6 there is
t
:h
the option to lose a second disk while a faulty disk is being reconstructed. Some vendors
s
force the users of their storage arrays to use a dual protection RAID type as soon as big disks
e
are discovered.
r c
s ou
Re
i n g
r n
e a
e L
or
M

RAID 10 combines mirroring and striping. RAID 1 is implemented

before RAID 0. RAID 10 is also a widely used RAID level.
n
User data D0, D1, D2, D3, D4, D5
/ e
m
Disk mirror Disk mirror
.c o
D4 D4 D5 D5
e i
w
D2 D2 D3 D3
D0 D0 D1 D1
u a
.h
Physical disk 1 Physical disk 2 Physical disk 3 Physical disk 4
g
RAID 1 RAID 1
n
RAID 0
ni
r
Slide 28
// lea
p :
RAID 0 was not a real option for most enterprise customers and RAID 1 was limited to the capacity of
t t
the disk. The combination of RAID 1 and RAID 0 however offers the best of both worlds!
s :h
In a RAID 10 set there is always an even number of disks. Half of the disks have the user data written
c e
to it and the other half holds the mirror copy of the user data. Mirroring is performed before striping.
r
ou
In the figure, physical disks 1 and 2 form one RAID 1 group, and physical disks 3 and 4 form another
es
RAID 1 group. These two RAID 1 groups form RAID 0.
R
A write to a RAID 10 system will mean that the data i.e. D0 will be written to physical disk 1 and a
i n g
copy will be written to physical disk 2.
r n
When two disks in different RAID 1 groups fail (for example disks 2 and 4), data access of the RAID
e a
10 group is not affected. This is because the other two disks (1 and 3) will have a complete copy of
e L
data on disks 2 and 4 respectively. However, if two disks in the same RAID 1 group (for example,
o r
disks 1 and 2) fail at the same time, data access becomes unavailable.
M
Theoretically there is the chance that half the physical disks may fail and there still would be no data
loss. However, looking at it from a worst case scenario, the RAID 10 guarantee is against a single
drive failing.

RAID 50 is a combination of RAID 5 and RAID 0. RAID 5 is

implemented before RAID 0.
D0, D1, D2, D3, D4, D5, D6, D7
e n
D0, D1, D4, D5, D8, D9 D2, D3, D6, D7, D10, D11
/
o m
P4
D4
D8
P2
D9
D5
P5
D6
D10
P3
D11
D7
e i
Stripe 2
.c
w
Stripe 1
a
D0 D1 P0 D2 D3 P1 Stripe 0
Physical Physical Physical Physical Physical
u
Physical
.h
disk 1 disk 2 disk 3 disk 4 disk 5 disk 6
RAID 5 RAID 5
RAID 0
i n g
r n Slide 29
// lea
p :
RAID 50 is a combination of RAID 5 and RAID 0. RAID 5 is implemented across two RAID 5 arrays
t t
which are configured with RAID 0. The two RAID 5 sets are totally independent from each other.
:h
RAID 50 requires at least six disks as the minimum for a RAID 5 is three disks.
s
c e
Physical disks 1, 2, and 3 form one RAID 5 group, and physical disks 4, 5, and 6 form another RAID 5
r
ou
group. The two RAID 5 groups form RAID 0.
es
RAID 50 can sustain simultaneous failure of multiple disks in different RAID 5 groups. However, once
R
two disks in the same RAID 5 group fail at the same time, data in the RAID 50 group will be lost.
i n g
r n
e a
e L
or
M

RAID Level RAID 0 RAID 1 RAID 5 RAID6 RAID 10 RAID 50
Fault tolerance No Yes Yes Yes Yes Yes
Parity Parity
Redundancy type No Replication Replication Parity check
n
check check
/ e
Hot spare disk No Yes Yes Yes Yes Yes
m
Read performance High Low High High Medium High
o
Random write
.c
High Low Low Low Medium Low
performance
Sequential write
performance
High Low Low Low Medium Low
e i
Min. number of disks 2 2 3 4 4 6
aw
u
Available capacity
.h
(Capacity of a single Nx 1/N x (N - 1) x (N - 2) x N/2 x (N - 2) x
g
disk)
ni n
r
Slide 30
// lea
p :
Conclusion: the ideal RAID type does not exist. Users must select the RAID depending on the
demands they have for speed, security or cost.
t t
s :h
r c e
RAID sets should not contain too many physical disks as statistically the number of failures will
ou
increase as the group gets bigger. Recommended RAID 5 maximum is typically 12 disks.
s
Recommendation for RAID 6 is mostly a maximum of 42 disks.
Re
i n g
r n
e a
e L
o r
M

Application scenarios of RAID
Typical application scenarios of RAID
RAID level Application scenario

RAID 0 A scenario requiring fast reads and writes but not high security,
such as graphic workstations.
n
RAID 1 A scenario featuring random writes and requiring high security,
e
such as servers and databases.
RAID 5 A scenario featuring random transfer and requiring medium
/
security, such as video editing and large databases.
o m
.c
RAID 6 A scenario featuring random transfer and requiring high security,
RAID 10
Such as mail servers, file servers.
A scenario involving large amounts of data and requiring high
e i
security, such as banking or finance field.
aw
RAID 50 Random data transmission, security requirements, concurrency
u
.h
requirements, such as mail servers, web servers.
i n g
r n
Slide 31
// lea
p :
With most vendors the storage administrator has the option to create multiple LUNs (or sometimes
t t
also referred to as volumes) with each a different protection system. Still the selection of the RAID
:h
type is important as the previous slides prove that there are differences in properties with each
s
selected RAID type.
r c e
ou
Fortunately with most vendors it is even possible to change the RAID type assigned to a LUN. That
s
can then be done on the fly which means that the LUN stays accessible for the users of the LUN while
the conversion takes place.
Re
i n g
r n
e a
e L
or
M

RAID Data Protection
Hot spare disk
Hot spare = When one of the disks in a RAID group fails and an idle or
standby disk immediately replaces the failed disk, this disk is known as the
n
hot spare.
Hot spare disks are classified as global hot spare disks or as dedicated hot
/ e
spare disks.
o m
e i .c
w
RAID 1 / RAID 5 / RAID 6 /
u a
.h
Disk 1 Disk n Hot spare disk
i n g
r n
lea
: //
t t p
In most storage solutions there are many disks present and often they are different types of disks.
:h
Each of the disk types has its specific qualities (capacity, rotational speed, access speed, reliability).
e s
By creating multiple RAID groups we can assign RAID levels to each of these groups and create
r c
storage capacity with the exact right specifications. Imagine 4 RAID groups are used. The question is
ou
now how to address the problem of hot spare disks. How many do you need? The answer is not 100%
es
fixed. Normally each RAID group would have its own hot spare disk. So in case of a failure there
R
would be a spare disk available. On the other hand: how often will it happen that in four different RAID
i n g
groups a drive fails. One spare for all four groups would then be enough.
r n
This one spare should then be configured as a global hot spare disk. It will replace any failed disk in
e a
any RAID group. Of course there is a requirement: the hot spare disk used should be the same size,
e L
or bigger, than the failed disk!
o r
In the situation that hot spares are really meant to be used by one RAID group the hot spare disk
M
should be a dedicated hot spare. Now, if in other RAID groups a disk fails the hot spare disk will not
be used.

Pre-copy
Pre-copy
Pre-copy: When the system detects that a member disk in a RAID

group is about to fail, data on that disk is copied onto a hot spare
disk, reducing risks of data loss.
e n
/
RAID 1 / RAID 5 / RAID 6 /
o m
Disk 1 Disk 2 Hot spare disk
e i .c
aw
u
g .h
ni n
r Slide 33
// lea
p :
The pre-copy option is a real nice addition that makes life much easier (or more relaxed) for storage
t t
administrators. Most enterprise class disks are fitted with a technology called SMART. This stands for
:h
Self-Monitoring Analysis and Reporting Tool. It basically means that the disk itself monitors its health
s
r c e
situation. It does this as it checks the rotational speed of the disk and the quality of the magnetic
ou
surface of the disk platters.
es
R
Providing we use the correct tools we can receive the message from the SMART disk and act quickly.
g
So when a SMART disks reports it is not doing very well it means it is not dead yet, but we can
i n
assume it may die pretty soon.
n
ar
L e
As soon as the tool receives the SMART message it starts copying the data from the disk onto (one of)
r ethe hot spare disk(s). When the drive later actually fails the majority of data is already present on the
o hot spare disk and the rebuild will take much less time!

Reconstruction
Reconstruction
Reconstruction: It is a process of recovering user data and parity

data on a failed disk in a RAID group onto a hot spare disk of the
RAID group.
e n
/
o m
.c
D0, D1, D2, D3, D4, D5
e i
Disk 1 Disk 2 Parity disk Hot spare disk
aw
u
D4 D5 P3 D4
.h
D2 D3 P2 D2
D0 D1 P1 D0
i n g
r n
Slide 34
// lea
p :
RAID of course is a great concept that helps protect the data. Hot spare disks can add to that
t t
protection level by automatically rebuilding or reconstructing a failed disk. Reconstruction of course
:h
must not impact the behavior of the RAID group. So for optimal reconstruction to work:
s
The hot spare disk should be ready.
r c e
ou
All disks should be configured in RAID 1, 3, 5, 6, 10 or 50.
es
Reconstruction must not interrupt system services.
R
i n g
r n
e a
e L
o r
M

Relationship between RAID and LUNs
Relationship between RAID and LUNs

RAID is like a large physical volume composed of multiple disks.
We can create one or multiple logical units of a specified capacity on the physical
volume. Those logical units are referred to as LUNs. They are the basic block devices
that can be mapped to hosts.
e n
/
Logical volume Logical volumes LUN 3
o m
.c
LUN 1 LUN 2
Physical volume Physical volume

e i
aw
u
g .h
i n
One logical volume created on a physical Multiple logical volumes created on a
volume. physical volume.
r n
lea
: //
t t p
Data is stored as files on a volume that are visible from within an operating system. For the Windows
:h
operating system these volumes are represented with drive letters (C:\ , F:\ etc.). In Unix\Linux based
e s
operating systems there would be mount points. The relation between a drive letter (or a mount point)
and the physical disks is like this:
r c
s ou
1. Physical disks combined form a RAID group.
Re
2. A RAID group has a specific RAID type associated to it.
i n g
3. A LUN is made up of (a section of) the storage capacity a RAID group presents.
r n
e a
e L
or
M

Creating RAID groups and logical volumes
LUN 1 LUN 2 LUN 3

Logical
volumes
RAID Segmentation
e n
/
o m
Physical
disks
e i .c
aw
u
g .h
ni n
r
lea
An example:
//
There are 4 physical disks each of which is 300 GB in size. When we put them together in a RAID
:
t p
group this group represents 4 x 300 GB = 1.2 TB of raw disk capacity. Assuming we want to use
t
:h
RAID 5 for data protection the actual available space would be 3 x 300 GB = 900 GB. We loose the
s
capacity of 1 disk because of the parity information that has to be stored across the 4 disks.
r c e
From the perspective of the storage administrator there now can be 1 big LUN occupying the 900 GB
ou
of space or multiple smaller LUNs that partly use the 900 GB capacity.
es
For each of the LUNs the data protection system would be RAID 5.
R
i n g
r n
e a
e L
o r
M

Questions
Questions
1. Explain the difference between stripe unit and stripe width.
2. Describe the various states a RAID group can be in.
3. Explain the basic principles of RAID 5.

e n
/
m
4. Explain the differences between the application scenarios of RAID
5 and those of RAID 1.
.c o
5. If a customer is concerned with reliability and performance, what
e i
RAID schemes will you recommend?
aw
u
.h
6. What is the relationship between RAID and LUNs?
i n g
r n
lea
: //
Answers:
t t p
s :h
e
1. Stripe unit (or chunk) is the smallest amount written to a physical disk. The stripe width is the total
r c
number of disks in a RAID group or the total capacity in a stripe.
ou
2. Good: everything is operational and hot spares are available; reconstructing: there is a disk failure
es
and at this point the hot spare disk is being reconstructed; degraded: there is a disk failure but no
R
hot spare disks are available; failed: too many disk failures have occurred and the data cannot be
i n g
represented anymore=> data loss is inevitable.
r n
3. RAID 5 uses striping with distributed parity. Data is split up in chunks (selectable in size); then a
e a
parity block is calculated. Data blocks and parity blocks and in parallel written to all the disks of
eL
the RAID group.
or
4. RAID 1 is used when the capacity does not exceed the size of one single disk and when the data
M
is very important. RAID 5 has a single disk protection level and has less performance than RAID1.
5. RAID 10.
6. LUNs are logical space allocations taken from the total disk capacity available in a RAID group. A
RAID group is a number of disk working together to provide storage capacity.
The free space available in a RAID group is calculated by the formula:
(number of disks x disk capacity) overhead for the RAID type.

Exam Preparation
Exam Preparation
1. Which of the following RAID levels provide redundancy?

a. RAID 0. ( check all that apply)
b. RAID 1.
c. RAID 5.
e n
d. RAID 10.
/
2. Statement 1: Failure of any two disks in a RAID 10 group does not affect
o m
data access.
Statement 2 : Rebuilding a global hot spare disk is faster than rebuilding
e i .c
dedicated hot spare disk.
aw
a. Statement 1 is true; Statement 2 is true.
u
b. Statement 1 is true; Statement 2 is false.
g .h
n
c. Statement 1 is false; Statement 2 is true.
ni
r
lea
: //
t t p
s :h
e
Answers:
r c
ou
1. B, C, D.
s
2. D.
Re
i n g
r n
e a
e L
o r
M

Summary
Summary
RAID levels and principles.
Characteristics of all mentioned RAID levels.
e n
/
Data protection technologies of RAID.
Application of RAID types.

o m
e i .c
aw
u
g .h
ni n
r
lea
: //
t t p
RAID nowadays is intended to protect data loss if physical disks fail in a so-called RAID group. Each
:h
RAID level has characteristics like the performance of the RAID group; the number of disk that can fail
e s
before data loss occurs and the cost involved to implement the RAID type. The cost is expressed in
r c
the overhead i.e. the amount of disk (space) that is used to have the data protection. Two methods
ou
are used: make a copy of the data (RAID 1 and RAID 10) and add extra parity information that can
es
help reconstruct the data (RAID 3, RAID 5; RAID 6, RAID 50).
R
i n g
RAID 0 is not used in enterprises very often because it offers no data protection. RAID 0 groups
r n
however are very fast and have no overhead. That means that all disk capacity available can be used
e a
to store user data.
e L
or
M

Thank you
www.huawei.com
e n
/
o m
e i .c
aw
u
g .h
ni n
r
// lea
p :
t t
s :h
r c e
s ou
Re
i n g
r n
e a
e L
o r
M

e n
/
o m
OHC1109106
e i .c
Basics of Big Data
aw
u
g .h
ni n
r
lea
://
www.huawei.com
t tp
s:h
r c e
sou
Re
i n g
r n
e a
e L
or
M
e n
/
o m
e i .c
aw
u
g .h
ni n
r
// lea
p :
t t
s:h
r c e
sou
Re
i n g
r n
e a
e L
or
M
Introduction
In this module you will be learning about Big Data. Big Data is now a topic that is very hot. In the
module we will show some of the concepts used to handle big data sets. The module is intended
to give a brief overview and will not go in much detail. The reason for that is simple: there is a
complete course that was created especially around the Big Data phenomenon.
e n
Objectives
/
o m
.c
Describe the concepts of Big Data.
e i
Mention reasons why there is a Big Data problem.
aw
Understand the difference between structured and unstructured data.
u
Explain how Object Based Storage can help us manage Big Data.
g .h
List the main specifications of Huaweis OceanStor 9000.
ni n
r
// lea
p :
Module Contents
t t
1. What is the definition of Big Data?
s :h
2. Why do we have Big Data?
r c e
ou
3. Characteristics of Big Data.
s
4. How to handle Big Data: Hadoop solution.
Re
5. Huawei OceanStor 9000 Big Data solution.
i n g
r n
e a
e L
or
M
HCNA-storage V3 | OHC1109106 Basics of Big Data Page | 217

e n
/
o m
e i .c
aw
u
g .h
ni n
r
// lea
p :
t t
s:h
r c e
sou
Re
i n g
r n
e a
e L
or
M
Page | 218 HCNA-storage V3 | OHC1109106 Basics of Big Data

What is Big Data?
What is Big Data?
Big Data is high-volume, high-velocity and high-variety information

assets that demand cost-effective, innovative forms of information
processing for enhanced insight and decision making.
e n
/
o m
e i .c
aw
u
SNIA definition: Big Data is a characterization of datasets that
.h
are too large to be efficiently processed in their entirety by the
g
most powerful standard computational platforms available.
ni n
r
Slide 3
// lea
In this module we will discuss Big Data. Big Data has everything to do with data and more
p :
importantly: with the amount of data that is generated. In the first module of this course we
t t
discussed the fact that data is very important for the business processes of a company. So what
is Big Data?
s :h
r c e
ou
Gartner states Big Data is high-volume, high-velocity and high-variety information assets that
s
demand cost-effective, innovative forms of information processing for enhanced insight and
decision making.
Re
i n g
SNIAs definition: Big Data is a characterization of datasets that are too large to be efficiently
r n
a
processed in their entirety by the most powerful standard computational platforms available.
L e
r eAlthough Big Data doesn't refer to any specific quantity, the term is often used when speaking
o about Petabytes and Exabytes of data.

Two things are important to take away from these definitions:
1. It is about an enormous amount of data (Petabytes / Exabytes) and the data is of different
types (structured/unstructured).
2. Inside of the Big Data is important information that can help my business work (better).
The practical consequences from this will be twofold again:
e n
1. How can we arrange for such amounts of data to be stored and kept?
/
2. How do we understand what data we have and how do we extract the right information from it?
o m
e i .c
aw
u
Why do we have so much Big Data?
g .h
ni n
Why do we have Big Data?
r
// lea
What causes the amount of data to explode?
p :
Increased amount of multimedia devices
t t
:h
like smart phones and social media.
The Internet of Things.

e s
High resolutions images.
r c
More bandwidth available.
s ou
e
Increased push to work with online (public) services.
R
i n g
r n
e a
eL
or
MThe picture above lists a number of causes of Big Data. Of course for a company some of these
causes may not be applicable. Fact still remains that companies store huge amounts of data and
at that point the Big Data problem can occur.
The amount of smart phones has risen in the last couple of years. Statistics show that at this point
there are six billion mobile phones used in the world. For a country like Holland there are one
hundred-twenty-five telephone connections for every one hundred persons. That means that
many Dutch own and use two phones!

Smart phones and tablet PCs are more and more used for creating social media data. It is now
possible to share images and audio as well as text with other persons. The resolution of the
images is increasing as nowadays a mobile phone has a built in high resolution camera. The size
of a single image taken is now 10 times bigger than 5 years ago!
Quantities of data are traditionally measured in Terabytes (1,000,000,000,000 Bytes or 1000 GB).
With Big Data new sizes are used:
e n
/
Petabyte 1,000 Terabyte
m
Exabyte 1,000,000 Terabyte or 1,000 Petabyte
Zettabyte 1,000,000 Petabyte or 1,000 Exabyte
.c o
Yottabyte 1,000 Zettabyte or 1,000,000,000,000,000,000,000,000 bytes
e i
aw
u
There are many applications used for Social Media. Examples of popular sites in Asia are Alibaba
.h
(like eBay you can buy and sell almost anything there), Youko (Small online videos just like with
g
YouTube) and Sina (as a Twitter like smart messaging system).
ni n
r
lea
It was estimated that 3.5 Zettabyte of information was stored all over the world in 2013. The data
: //
that was generated over the last two years is now forming 95% of all data ever created.
t t p
:h
Estimations state that in 2020 there will be more than 40 Zettabyte of data!
e s
r c
Another thing that adds to the problem is the fact that it is now easy to generate large amounts of
ou
data and send them as the network has been upgraded continuous. Now almost everybody has
es
access to broadband networks; 3G or even 4G wireless networks so sharing even big images is
R
not time consuming and expensive anymore.
i n g
n
What in the nearby future may lead to even more Big Data is described as the Internet of Things
r
e a
e L
With that we mean that more and more devices will have intelligence on board and they will then
or be connected to the global network. It is no longer just computers that are connected. Think of the
huge numbers of webcams and internet printers. In the future more of these devices will be
M introduced. Think of refrigerators with internet connection that automatically order groceries;
domotica applications where one can control the heating systems; lights; garage doors in your
house from a remote location using a smartphone application. The electricity and gas meters in
houses will in the future send their information to the electricity and gas board where today a
person comes and writes down the values. The car of the future will be one more example of
where the internet of things will be. Cars at this point may have on-board computers for navigation;
diagnostics and configuring features like air-conditioning, audio etc.

In the future each car will generate data about the fuel consumption; the location; speed averages;
how many people are in the car and maybe even information about the driver. Imagine that a car
will report automatically when a driver is too tired or has fallen ill. Automatically the car could then
do an emergency stop and even call for medical assistance.
Value of Big Data

e n
/
Characteristics of Big Data
o m
e i .c
Written once, few modifications
aw
u
Videos
g .h
n
Music
i
Uncertain value
25%
r n
lea
Unstructured Pictures
data 75%
://
Large capacity, rapid growth
Data composition
tp
Emails
t
:h
Data files
Long-term storage required
e s
r c
ou
es
R
i n g
r n
e a
e L
or
M

According to researches, 75% of data is unstructured data typically from videos, music, pictures,
emails, and data files. Most of the massive data has the following characteristics:
Written once, few modifications.

For example, many videos and pictures are typically read but seldom edited.
Uncertain value.
The value of a picture or video may increase due to a certain event. For example, the
childhood picture of a person in the spotlight has value. Video surveillance data also has
similar characteristics. No one knows when such data becomes useful, but the data cannot be
e n
abandoned.
/
o m
Large capacity and rapid growth.
e i
The number of images taken with digital cameras and smart phones has grown explosively. At .c
the same time the resolution of the cameras has increased too.
aw
u
Long-term storage required.
g .h
i n
Some data may need to be stored for dozens of years or even longer. This requires a storage
n
r
lea
medium that can hold the data for that many years.
: //
Another example of the need to filter out what is valuable data within the huge amount of data that
t t p
could be collected is the LHC project in Geneva. In the Large Hadron Collider project there is
:h
research done on the behavior of atomic particles. They have experiments where they accelerate
e s
atomic particles to speeds close to the speed of light. At that speed they have the particles collide
r c
with other particles. They then look at the results of the collision. In such collisions new particles
ou
might appear. In the LHC they are trying to create (and then study) a very special particle called
s
the Higgs boson.
Re
i n g
r n
e a
e L
or
M

The Large Hadron Collider experiments represent about 150 million sensors delivering data 40
million times per second. There are nearly 600 million collisions per second. After filtering and
refraining from recording more than 99.999% of these streams, there are 100 collisions of interest
per second.
As a result, only working with less than 0.001% of the sensor stream data, the data flow
from all four LHC experiments represents 25 petabytes annual rate before replication (as
of 2012). This becomes nearly 200 Petabytes after replication.
e n
/
If all sensor data were to be recorded in LHC, the data flow would be extremely hard to
o m
.c
work with. The data flow would exceed 150 million petabytes annual rate, or nearly 500
e i
Exabytes per day, before replication. To put the number in perspective, this is equivalent
w
to 500 quintillion (51020) bytes per day, almost two hundred times more than all the
a
other sources combined in the world.
u
g .h
i n
An even bigger project is about to be started. The Square Kilometers Array is a telescope which
n
r
consists of millions of antennas, and it is expected to be operational by 2024. Collectively, these
lea
antennas are expected to gather 14 Exabytes and store one petabyte per day. It is considered to
: //
be one of the most ambitious scientific projects ever undertaken.
t t p
s :h
r c e
s ou
Re
i n g
r n
e a
e L
or
M

How can we handle Big Data?
Because it is very difficult to limit the growth of data, the solution is to organize the data we have
as good as possible. Before this is possible it is important to identify the way in which data (files)
are stored today.
OBS: Object Based Storage
e n
/
iSCSI/FC protocol layer NFS/CIFS HTTP/REST/S3
o m
Storage layer File system Object system
Object
Object Key
e i Objects
Data
.c
w
Object
a
Object
Object Metadata
u
User-
.h
... ...
defined
meta
...
g
data
Block storage File storage OBS
ni n
Direct access, minimum Easy to manage and easy to
r
lea
Flat structure with almost unlimited scalability.
overhead and maximum interwork with applications.
Intelligent self-management.
efficiency.
Moderate scalability but many
//

Use of standard Internet protocols and cross-
Highest cost and poor restrictions.
region data transfer capability.
:
scalability.
Scenarios: application
p
Scenarios: Internet service-oriented storage
Scenarios: enterprise integration and file sharing in
t
and enterprises' internal archiving and backup.
databases (ie Oracle). an enterprise.
t
:h
e s
r c
ou
Block storage directly accesses the storage layer, featuring fast speed, minimum overhead, and
s
maximum efficiency. However, block storage has the highest cost and poor scalability. Block
e
R
storage uses protocols like iSCSI and Fibre Channel.
i n g
n
File storage creates a file system on the basis of block storage. Data is organized in the
ar
directory-directory-file mode, facilitating data management. The objects operated by most
L e
application programs are files. Therefore, file storage enables easier interworking with application
r esystems. File systems are restricted by directory trees. Therefore, a file system can be typically
o expanded to dozens of PB at most. The scalability is limited. File systems are applicable to
M application integration and file sharing in an enterprise.
OBS(object-based storage) is a new emerging storage technology. OBS creates an object

management layer on the basis of block storage. Compared with a file system, the object system
layer is flat with almost unlimited scalability. An object consists of a unique key, file, data (file),
metadata, and user-defined metadata. Objects contain self-management information and
therefore are more intelligent. OBS employs interfaces that are compatible with standard Internet

protocols. OBS does not use traditional directory structures and there is no need to be involved in
the creation of volumes on the underlying hardware. This is all shielded from the OBS system.
In an OBS system, the MDS (Meta Data server) stores the mapping between files and OSDs
(Object Storage Device) and the organization relationship between files and directories. The MDS
provides operations, such as file search, file creation, and file/directory property processing. From
the perspective of a client, an MDS is similar to the logical window of a file, and an OSD is similar
to the physical window of a file. When a user operates a file, the file system obtains the actual
storage address of the file from the MDS. Then, the file system operates the file on the
e n
/
m
corresponding OSD. In subsequent I/O operations, the MDS will not be accessed, greatly
reducing the burden of the MDS. In this way, system scalability becomes possible.
.c o
e i
aw
Data access model
u
g .h
File names / inode
i n
Objects/OIDs
n
r
// lea
p :
t t
0 1 2 3
s 4
:h Object Object
5 6 7
r c e
8 9 Object Object
ou
10 11 12 13 14 Object
15 16 17 18 19 Object Object
es Object
RTraditional storage OBS
i n g
r n
e a
L
The file system of traditional storage employs tree directories. If there are a lot of files and file
e
r
layers, the root node has a great pressure and file search is time-consuming. As a result, the
o
performance will become poor. OBS employs a flat structure based on decentralization. Even if
Mthere are massive files, data access performance is not affected and with that it is still easy to add
more capacity.

Advantaged of Object Based Storage
Advantages of OBS
Object interfaces, dividing data flexibly.
Flat objects, allowing easy access and expansion.
Automated management.
e n
/
Multiple tenants.
Data integrity and security.
o m
e i .c
aw
u
g .h
i n
Slide 8
n
r
Object interfaces, dividing data flexibly
// lea
p :
OBS systems do not need to know about the physical way data is stored. Traditional storage
t t
devices store SCSI blocks and with that comes the chunk size of the storage device. Chunks are
:h
typically 512 bytes to 4 kB. OBS can use any object size to store the objects with the support for
s
r c e
an object size ranging from several bytes to several terabytes.
ou
Flat objects, allowing easy access and expansion
es
Flat data structures allow the OBS capacity to be expanded from a TB level to an EB level. An
R
OBS system typically builds a global namespace based on a scale-out (or grid hardware)
n g
architecture. This makes OBS applicable to could computing environments. Some OBS systems
i
r n
even support seamless upgrade and capacity expansion.
e a
e L
Automated management
r
OBS allows users to configure attribute (metadata) policies for objects based on service needs
o from the application perspective.
M Multiple tenants
The multi-tenant feature can use the same architecture and the same system to provide storage
services for different users and applications. Besides, specific data protection and storage
policies can be configured for each user and application. Data is isolated from each other.
Data Integrity and Security

OBS can have systems to protect objects and underlying hardware can have data protection in
place.

Procedure of Big Data processing
Procedure of Big Data processing
e n
Data collection Data storage Data management Analysis
/
o m
e i .c
aw
u
g .h
ni n
r
// lea
:
Big data is processed similar to common data, which includes: data capturing, storage,
p
management and analysis.
t t
s :h
Data capturing leverages multiple means: methods and tools to capture data for later analysis.
r c e
What data should we capture? How do we capture them? What tools are required? What tools
ou
can be more efficient? These are questions we must pay close attention to.
es
R
Data storage is to transfer and store the captured data. As the data increases exponentially,
n g
traditional data storage methods fail to meet Big Data requirements. New technologies are
i
needed.
r n
e a
L
Data management is an extension of data storage. With regards to data storage, data
e
or
management refers to deep data processing and categorization so that useful metadata is
provided for subsequent data analysis.
M
Data analysis involves the use of data analysis methods, models, and tools in order to make
correlations. More in-depth data mining based on the preceding analysis and acquired data can
meet higher-level requirements.
This chapter focuses on data storage and the extension of data storage (namely data
management) to introduce key technologies of Big Data.

Content types of big data
Content data: items, photos, videos, texts ~ 23%
Individual ~10 %
user behaviors
User ~5 %
e n
/
Profile
Collective social network data ~35%
o m
Web Page & Log ~27%
e i .c
aw
Mostly structured In every PB data
u
Semi-structured
(e.g. Internet-based company)

.h
Structured Unstructured
i n g
r n Slide 10
// lea
p :
t t
:h
es
~25 % captured by probe, including
Network XDP
historical data
Bill CDR
r c ~15% including historical data
ou
Internet web pages and
logs ~13% including historical data
SND
es
~3% Social Network Data
R ~7%
g
Content data Photos, videos, texts
n i n
Primary data ~12% subscription + contact
ar Analysis and summary data ~18% including historical data
e
CUBE and
eL
unified view ~7%
In every PB data Semi-structured
or
Mostly structured (e.g. telecom operator) Structured Unstructured
By structure, data can be categorized as structured data, semi-structured data, and unstructured
data.
Structured data is expressed as a two-dimensional table structure. Simply put, structured data is
information in a database. For example, an ERP system, a financial system, a Customer Relation
Management database all store structured data.

Unstructured data cannot be expressed in a two dimensional database logic conveniently. Such
data includes office documents, text, graphics, XML pages, HTML pages, various reports, photos,
audio files and video files. For example, medical imaging system, campus video-on-demand
system, video surveillance, GIS of national land bureaus, design institutes, file servers
(PDM/FTP), and media resource management all store unstructured data.
Semi-structured data is data that has not been organized into a specialized repository, such as
a database, but that nevertheless has associated information, such as metadata.
e n
/
m
Whatever solution is selected, it is important to realize that it takes a lot of computing power to
have software investigate; organize and filter great amounts of data. That is why Big Data solution
.c o
management software is run not on a single host, but on multiple hosts that work in parallel.
e i
aw
u
g .h
Hadoop: Internet Big Data solution
ni n
ar
How to handle Big Data : Hadoop solution
l e
: //
t t p
: h
Analysis platform
e s
r c
o u
MapReduce HBase
es
distributed parallel processing architecture non-relational database
R
i n g
r n HDFS distributed file system
e a
e L
or Copyright 2015 Huawei Technologies., Ltd. All rights reserved. Slide 12
MOne of the options is Hadoop. Hadoop is an open-source technical framework for distributed Big
Data processing. The Hadoop project was started in 2005 and was later adopted into the Apache
community. Hadoop was designed to run complex data management tasks with relatively simple
hardware. It can use virtually all storage devices for storing data and it can use multiple hosts
(referred to as nodes) for computing tasks. Therefore Hadoop has distinct performance and cost
advantages in unstructured data processing compared with the traditional mainframe computers
needed before.

Hadoop contains three components:
1. The Hadoop Distributed File System (HDFS).

2. The non-relational Hadoop Database (HBase).
3. The MapReduce distributed parallel processing architecture.
The architectural difference between structured Big Data solutions and unstructured Big Data
solutions lies in database management.
e n
The traditional relational databases have been used for a long time, there are multiple auxiliary
/
tools, and database applications are very stable and reliable. However, (relational) databases
o m
e i .c
have a complex hierarchy. As a result, data processing takes a long time. It is difficult for a
traditional relational database to process over 1 TB of data and support high-level data analysis.
aw
u
.h
The Parallel Database System is a new-generation high-performance database system. It
i n g
breaks down the complex hierarchy into independent units. The units are isolated from each other,
and their relationship hierarchy is simple, which is the core of parallel database systems. By
r n
lea
dividing a large database into small ones and storing them on different nodes, Parallel Database
Systems process data in a parallel manner. The failure of one unit does not affect other units. In
: //
addition, the Parallel Database Systems inherit all advantages from a relational database.
t t p
:h
With parallel databases, we can create more data categories when data is carried and stored.
e s
During data analysis, the Business Intelligence analysis tool does not require data categorization.
r c
Instead, the tool directly analyzes the data and provides the results, greatly improving the data
ou
analysis efficiency.
es
R
Apache Hadoop is currently used by many companies that have to store large amounts of data.
i n g
The data can be stored in local datacenters or the data can be store in the Cloud. Facebook,
r n
Yahoo and Google all store their data using a Hadoop based system. Other companies have also
e a
adopted Hadoop but have created their own applications to work together with Hadoop :
e L
or Amazon: It uses Amazons S3 (Simple Storage Services).
M Microsoft: Especially created for use in Cloud storage solutions there is Microsofts Azure.

Huawei OceanStor 9000
OceanStor 9000 Big Data storage architecture
Video surveillance HPC Web Billquery Net-surfing Precision Business

disk behavior analysis marketing promotion
Application
layer
Files Objects Query/Retrieval Data analysis
NFS CIFS HDFS Object
e n
/
SQL MR/Hbase
Distributed database Enterprise-class &
m
Data WushanSQL FusionInsight Hadoop
o
processing
.c
layer
i
Distributed file system / WushanFS Archiving
we
Hardware
u a
.h
node layer
g
Node Node Node Node Node Node Node Node Node Node
ni n
r
// lea
:
The Huawei OceanStor 9000 model is the solution that Huawei provides for storing Big Data.
p
t t
Within the OceanStor 9000 Big Data Solution there is everything you need to manage Big Data.
s :h
e
It combines data storage, backup and analysis (unified management, hardware platform and
r c
networking) in one product that is easy to manage. The file system directly manages underlying
ou
disks, eliminating complex RAID configuration and LUN division steps. The OceanStor 9000
es
product is highly scalable with up to 288 nodes to be configured to work together.
R
n g
All nodes are integrated into the OceanStor 9000 hardware platform. The internal network mode
i
r n
can be 10GE or InfiniBand High-Speed. Therefore, the OceanStor 9000 delivers excellent
e a
performance while ensuring low latency, high bandwidth, and high concurrency. To meet various
L
application scenarios, the OceanStor 9000 provides such nodes as high-OPS nodes, large-
e
or
bandwidth node, and large-capacity node. Users can configure a flexible number of various nodes
based on performance and capacity requirements.
M
The OceanStor 9000 supports multiple interface and data types, including NAS interfaces (NFS,
CIFS, and POSIX), target interfaces (REST and SOAP), database interfaces (JDBC and ODBC),
and backup and archiving interfaces (VTL and OST). The OceanStor 9000 solution is perfectly
qualified for storage of core production data, and business data storage and analysis.

File system key technologies Unified namespace
File system key technologies Unified namespace
Independent namespace Unified namespace

Domain Namespace
Namespace Namespace
vs.
e n
Dir Dir Dir File Dir Dir Dir File
/
o m
.c
File File File File File File
Description
A unified file system namespace is provided externally. The namespace can use
e i
and manage all the available capacity of a system.
aw
u
File system space is presented externally as directories.
.h
A namespace is automatically created along with system startup and is named
g
after the system name.
ni n
r
// lea
:
Although the data can be stored on various storage devices and access to the data is arranged
p
t
through multiple nodes; the total amount of data appears to be on one location. The intelligent file
t
:h
system within the OceanStor 9000 called Wushan presents all data (or files because that is what
s
you really access) as stored on one single namespace. A namespace is the symbolic reference to
e
r c
the physical location of an object. Normally files are stored in directories. Directories are parts of a
ou
file system. Multiple directories are grouped into a namespace. Multiple hardware (the physical
es
location of the files) leads to multiple namespaces.
R
n g
In an OceanStor 9000 there can be up to 288 nodes, where each node can have its own storage
i
r n
capacity, which allows an OceanStor 9000 to store up to 50 PB of data. However, when
a
accessing the information, it will appear to be in one single namespace and the data appears to
e
e L
be stored on one storage device. Metadata and data are stored on each node that acts as both a
or metadata server and a data server. When accessing file data, the Wushan distributed file system
locates the metadata server to which the target file belongs, obtains data distribution of the target
M file from the metadata server and then accesses the nodes to complete data access.
Managing the metadata is one of the strong points of the OceanStor 9000. It does this very
efficient so even in a Big Data system with many petabytes of data the performance of the system
is outstanding. Metadata is organized based on a dynamic subtree structure. All metadata in a
namespace is grouped into name subtrees. Each name subtree is allocated to one Meta Data
Service or MDS. One MDS can manage multiple subtrees. Multiple nodes running multiple MDSs
provide high performance.

Overview of OceanStor 9000 key technologies
Load balancing
Dynamic storage tiering
Global
n
cache
Quota management
/ e
o m
Erasure Code
e i .c
aw
u
File system
g .h
ni n
r
// lea
:
The above picture shows the key technologies of the OceanStor 9000. In this module we only
p
t
want to introduce the OceanStor 9000. There is another course designed that explains the
t
:h
workings of the OceanStor 9000 in more detail. A short explanation of the key technologies
follows next.
e s
r c
ou
Load Balancing.
es
A service called InfoEqualizer divides the workload across multiple nodes.
R
n g
Dynamic Storage Tiering.
i
r n
With this function the data that is accessed often is automatically placed on high performance
e a
storage devices. Lesser accessed data is moved to slower (and cheaper) storage devices.
e L
or
Quota Management.
The administrator can monitor and control the usage of storage capacity and of the number of
Mfiles for individual users of the OceanStor 9000.

Erasure Code
Erasure code is the technical term for the storage virtualization technique Huawei uses for storing
files on physical disks of their NAS devices and protecting the data. In module 5 the RAID
technology was discussed. That is traditional protection of failing disks. In module 9 the
technology Huawei uses, RAID 2.0+, will be explained. The next pictures show that the erasure
code offers a better protection of files and also a better performance in case data has to be
n
recovered.
/ e
o m
e i .c
Erasure Code
aw
u
.h
Main technology designed to prevent file loss.
Big files are chopped in 4 GB parts.
i n g
n
Parts can be spread over multiple disks, over multiple OceanStor
r
lea
9000 systems across multiple racks.
//
Offers a very high, selectable, protection of files.
p :
t
On first glance erasure code resembles RAID technology.
t
s :h
r c e
s ou
Re
g
Internally the OceanStor of course stores the data in SCSI blocks on physical disk drives.
i n
However from the outside it looks like the OceanStor 9000 chops files into smaller parts and uses
n
r
a RAID like technology to store them internally.
a
L e
All the advantages of RAID can now be applied on files that are stored on the OceanStor 9000.
r eBig difference is now that with RAID we think about protecting data when disks fail and with
o Erasure code it can be even better. Files can be protected against loss even if a complete
M OceanStor 9000 fails or even a full rack with several OceanStor 9000s!
Added to these obvious advantages the RAID approach also helps the rebuilding of the system
when a disk, or a node (a single OceanStor 9000) or a rack of nodes fails.

Inter-Node distributed RAID
Traditional RAID 5
tolerates a concurrent
Failed
failure of one disk or node.
Failed
Traditional RAID 6
n
Failed tolerates a concurrent failure
Failed
of two disks or nodes.
/ e
o m
.c
Failed
i
N+1, N+2, N+3, N+4
e
Failed redundancy tolerates a
w
concurrent failure of up to
a
Failed four disks or nodes.
u
g .h
ni n
r
lea
The above picture is representation of an animated slide that is shown during the course. Here
//
the concept of Erasure code is shown clearly.
p :
Inter-Node distributed RAID storage 1 N+M
t t
:h
es
File data is divided into N (3 Writing data fragments to different
c
for example) fragments and M nodes improves data read/write
r
File data (2 for example) redundant performance, ensures high data
ou
fragments are calculated. reliability and service availability,
N ranges from 2 to 16. maintains optimal disk utilization,
s
M ranges from 1 to 4. and maximizes return on
e
investment (ROI).
R
Source data Source data Source data Redundant Redundant
fragment fragment fragment data data
fragment fragment As long as the number of failed
g
disks in the cluster is less than M
n
(the number of redundant data
i
fragments), the OceanStor 9000
n
implements data reconstruction
r
Disk Disk Disk Disk Disk across nodes to quickly restore lost
a
data, thereby ensuring data
e
Disk Disk Disk Disk Disk reliability of the system.
eL
... ... ... ... ...
Any available space can serve as
or
hot spare space, eliminating the hot
Disk Disk Disk Disk Disk spare disk problem in traditional
RAID and improving storage
M
utilization.
Node 1 Node 2 Node 3 Node 4 Node 5
Storing three data fragments and two redundant fragments on five nodes is used as an example.
The above image is a more technical explanation of the Erasure code technology. It can be used
to determine how much hardware (disks and/or nodes) are needed to get a specific level of
redundancy.

OceanStor 9000 hardware structure
OceanStor 9000 hardware structure
High Performance Large Capacity

Storage Node Archiving Node Analysis Node
P Series C Series I Series
e n
P12 C36 I 25
/
2U, 3.5, 12 drives 2U, 2.5, 25 drives
o m
.c
Big data analysis,
P25 4U, 3.5, 36 Drives
i
video analysis
On-line media assets,
e
2U, 2.5, 25 drives HPC, video surveillance
P36 C72
aw
u
.h
4U, 3.5, 36 Drives 4U, 3.5, 72 Drives
g
HD editing, news Near-line media assets,
video surveillance
n
production, high-end HPC
ni
r
lea
: //
t t p
The OceanStor 9000 hardware solution contains at least 3 identical nodes. Three types of nodes
:h
exist: P Series is short for High Performance Storage Node, C Series is short for Large Capacity
e s
Archiving Node, and I Series is short for Analysis node. The application scenarios for these
r c
different nodes are explained in the slide.
s ou
Optional Model
P12 Re Description
2 U, 12 data disks (Typical configuration: 12 SATA disks, or 1 SSD +
i n g 11 SATA disks)
P25
r n 2 U, 25 data disks (Typical configuration: 1 SSD + 24 SAS disks)
P36
e a 4 U, 36 data disks (Typical configuration: 1 SSD + 35 SATA disks)
eL
C36 4 U, 36 data disks (Typical configuration: 36 SATA disks)
or
C72 4 U, 72 data disks (Typical configuration: 72 SATA disks)

The OceanStor 9000 network architecture contains the front-end service network and rear-end
storage network.
Recommend networking: Front and Back End 10Gb
Recommended networking: Front & Back End 10Gb
e n
Networking Features
/
m
Application layer
o
Application servers Management Front-end 10GE + back-
.c
server end 10GE (default typical
i
networking).
e
...
Separation between
front-end and back-end
w
networks.
a
10GE switch 10GE switch

u
Fully redundant
networking.
.h
Storage layer GE switch The GE switch
g
connected to
OceanStor 9000
n
management network
i
ports on each node and
n
also connected to the
r
management server.
...
lea
Node Node Node Node
://
GE network
10GE switch 10GE switch 10GE network
tp
Stack cable
t
:h
e s
OceanStor 9000 networking structure:
r c

ou
The front-end service network is used for connecting the OceanStor 9000 to a user network.
s

e
The back-end storage network is used to internally interconnect all nodes on the OceanStor
9000. R

i n g
The IPMI network is used for connecting the OceanStor 9000 to customers' maintenance
r
network.
n
e a
e L
The OceanStor 9000 supports multiple types of networks containing the 10GE network, InfiniBand
o r
network, and GE network for meeting different network requirements.
MNote: 10GE = 10 Gbit/s and GE = 1 Gbit/s.

Questions
Questions
1. What are the main differences between traditional data and big
data?
2. Name five reasons why we now have so much data that needs
n
to be collected.
3. Describe the concepts of Hadoop and OBS.
/ e
o m
e i .c
aw
u
g .h
ni n
r
// lea
p :
t t
:h
Answers
e s
r c
1. Big Data is largely unstructured data. Traditional data is stored as blocks or as files. Big Data
ou
is stored as objects. Big data solutions work independent from the underlying hardware.
es
2. Five answers are:
R

i n g
Social media is used more and more.

r n
Bandwidth available.

e aImages are generated in much higher resolutions.
eL
Many tasks have been converted into digital tasks (taxes, webshops, travel arrangements,
or
bookings).
M
The Internet of Things.
3. Hadoop uses a structure built on top of physical storage hardware and organizes the data as
objects. Using a distributed file system data is no longer dependent on its physical location.
Also with the use of a MapReduce function the tasks (searching for metadata that tells the
system where the physical data is) can be split up in subscale tasks. The tasks are then
forwarded to multiple nodes that all together process these subscaletask in parallel.

Exam Preparation
Exam Preparation
1. Big Data solutions are primarily used to store what type of data?
a. Mostly structured data.
b. Mostly unstructured data.
c. Both structured data and unstructured data.
d. None of the above.
e n
/
2. What are characteristics of HUAWEIs OceanStor 9000 big data
o m
.c
solution?
a.
b.
Integration of data storage, backup, and analysis.
Support for multiple namespaces only.
e i
c. Can support up to 128 nodes.
aw
u
d. Support for dynamic storage tiering.
.h
e. Quota management for capacity and/or number of files.
f. Support for CIFS and NFS.
i n g
r n
// lea
p :
t t
:h
Answers
e s
1. C.
r c
ou
2. A, D, E, F.
es
R
i n g
r n
e a
e L
or
M

Summary
Summary
Definition and characteristics of big data

Key big data technologies

n
Object Based Storage
Parallel computing
/ e
Hadoop
o m
Architecture and features of Huawei OceanStor 9000 big data
e i .c
product
aw
u
g .h
ni n
r
// lea
p :
t t
s :h
r c e
s ou
Re
i n g
r n
e a
e L
or
M

Thank you
www.huawei.com
e n
/
o m
e i .c
aw
u
g .h
ni n
r
// lea
p :
t t
s :h
r c e
s ou
Re
i n g
r n
e a
e L
or
M

e n
/
o m
OHC1109107
e i .c
Backup and Recovery aw
u
g .h
ni n
r
lea
://
www.huawei.com
t tp
s:h
r c e
sou
Re
i n g
r n
e a
e L
or
M
e n
/
o m
e i .c
aw
u
g .h
ni n
r
// lea
p :
t t
s:h
r c e
sou
Re
i n g
r n
e a
e L
or
M
Introduction
In this module we will look at the options a customer has to implement a disaster recovery method.
The method will allow the ICT staff to recover data when it has been lost. For most companies
this disaster recovery is not so dramatic as the title suggests. It is not about real disaster as in
most cases the disaster is caused by one of the companys employees accidentally deleting files
(and with that losing some data). A backup strategy is typically implemented to recover for these
scenarios. As roughly 80% of all data loss is caused by human intervention it is important for a
e n
/
company to have a backup strategy in place.
o m
e i .c
Objectives
aw
u
g .h
Describe the backup concepts and topologies.
ni n
Understand backup technologies.
r

lea
Explain the steps required to set up a backup strategy.
//

:
Know about Huawei backup solutions and applications.
p

t
Know the concepts of Disaster Recovery.
t
s :h
r c e
Module Contents
s ou
Re
g
1. Backup concepts and topologies: LAN-based and LAN-free.
i n
2. Backup structures: D2T, D2D and D2D2T.
n
r
3. Backup strategy.
a
e
4. Deduplication.
eL
5. Huawei Backup Solutions and application.
or
6. Disaster Recovery introduction.
HCNA-storage V3 | OHC1109107 Backup and Recovery Page | 245

e n
/
o m
e i .c
aw
u
g .h
ni n
r
// lea
p :
t t
s:h
r c e
sou
Re
i n g
r n
e a
e L
or
M
Page | 246 HCNA-storage V3 | OHC1109107 Backup and Recovery

What is a backup?
In previous modules we have discussed the importance of data for an organization. It is therefore
very important to understand the risks of not having the data anymore. If we understand the risks
it is logical that we have to try to prevent losing the data. For that we have to implement a backup
strategy. Any backup strategy has to be made with the assumption that the amount of data that
can be lost is known. This is the so-called Restore Point Objective or RPO. For each company
n
there can be different RPO requirements ranging from minutes (banks, airline companies,
government) up to hours or even days. This module focusses on the traditional backup strategy
/ e
using backup servers and backup software.
o m
At the end of the module there will be a short introduction of disaster recovery methods.
e i .c
aw
u
.h
What is a backup?
i n g
In information technology, a backup, or the process of backing up,
r n
lea
refers to the copying and archiving of computer data so it may be
used to restore the original after a data loss event.
: //
t t p Workstation
:h
LAN
e s
r c Backup
server
Agent Application
server
ou
Tape library
es
R Storage device
i n g
n
ar
L e
A backup system usually consists of the following components:
r e
o 1. Backup server:
M The backup server is the PC or a UNIX server where the backup software resides.
2. Backup software:
Backup software is the core of a backup system. It is used to make and manage copies of the
production data on the storage media. Typical backup software includes Backup Exec,
NetBackup and CommVault.

3. Storage device
A storage device is used to store backup data. It can be a disk array, a physical tape library,
or a virtual tape library (VTL).
There are two methods used to build a backup environment. The first one is the LAN-based
backup topology. In a LAN-based backup topology the network is used for moving the data from
e n
/
the application server to the backup server, but also for the command flow. With the command
m
flow we mean the communication between the components of the backup system. For instance
the command send from the backup server to tell an agent (running on an application server) to
.c o
send data. Another example of a command could be the request sent from the backup server to
e i
the backup device to select a specific tape from the tape library.
aw
u
g .h
LAN-based backup topology
ni n
r
// lea
p :
t
LAN
t
:h
Data flow
Data flow
e s
c
Backup server
Agent Agent
r
Media server
File
server
s ou Application
server
Re Backup storage
g
device
i n
Data flow
n
Command flow
ar
L e Copyright 2015 Huawei Technologies., Ltd. All rights reserved. Slide 4
r e
o
In the above picture it is clear that the same network is used for data and commands. In many
Mcases the infrastructure uses just a single network. In that case making backups during office
hours is an extra load on the network traffic. The users of applications that access their data via
the network could then find that the network is becoming overloaded (=slow). That is also the
reason that many backup jobs are run outside working hours. That of course can be a problem
when the RPO is set in such a way that multiple backups have to be made during working hours!

The data backup process involves these steps:
1. The backup server sends a control command to the application server that runs the agent
software.
2. The agent on the application server receives these commands and sends the backup data to
the backup server.
3. The backup server then moves the data to the backup device and has it backup up on the
correct media (i.e. tape).
4. Optionally the data is not stored locally on the application server but on a file server. An agent
on the file server will then send the data.
e n
/
m
5. The backup server receives data and stores it on the storage device.
.c o
The whole process will be executed over a LAN connection.
e i
aw
u
Advantages:
-
g .h
The backup system is separate from the application system. The backup process does
not occupy hardware resources on the application server.
ni n
r
Disadvantages:
// lea
-
p :
A backup server is needed, increasing the investment.
-
t t
The backup agent program affects the performance of the application server.
-
:h
Data backup is based on a LAN, affecting the network performance.
s
-
-
r c e
Backup services must be independently managed and maintained.
ou
A demanding requirement is posed on the processing capability of the users' applications.
es
R
g
The next method of building a backup system is the LAN-free backup topology. There, as the
i n
name suggests, backup data flows and command flows use different physical networks.
n
ar
L e
This of course eliminates the impact of one flow on the other.
r e
o
M

LAN
Application Application Backup server

server server Media server
e n
/
SAN
o m
i .c
Backup
e
Storage
device
aw
Storage device Storage device
u
.h
Data flow
g
Command flow
ni n
r
// lea
:
In LAN-free backup, control flows are transmitted over a LAN while data flows are not. As a result,
p
this backup mode does not occupy LAN resources.
t t
The data backup process:
s :h
r c e
1. The backup server sends a control flow to the application server that runs the agent program.
ou
2. The application server receives the command and reads production data.
es
3. The media server reads data directly from the application server and sends the data to the
backup media.
R
n g
4. Optionally the data will be transported from the storage device to the backup server, again
i
r n
directly via the SAN network.
e a
L
Advantages
e
-
o rBackup data flows do not occupy LAN resources, improving the backup performance without
impacting the network performance.
M- Using LAN-free backups allows backups to be run even in working hours as the data
movement will not impact the LAN performance.
Disadvantages
- The backup agent program affects the performance of the application server.
- The method demands a SAN infrastructure to work. This makes the solution more expensive
than a LAN-based solution which can be applied in smaller NAS or DAS infrastructures.

Components of a backup system
Components of a backup system
Backup software Backup media Backup server
Creates the backup Tape library. Houses the backup
n
policy. Disk array. software.
/
Manages the Virtual tape library Backs up data to the
m
backup media. (VTL). storage media
o
according to a
.c
Performs other CD-ROM
preset backup
i
extended functions. tower/library.
e
policy.
aw
u
g .h
ni n
r
// lea
:
A complete backup system usually consists of backup software, backup media, and backup
p
server(s).
t t
s :h
The backup software is used to implement a backup strategy, manage the backup media and
r c e
perform the data backup. Using backup software offers the possibility to protect application data,
ou
application programs, and if desired complete application systems.
es
R
Some advanced backup software can realize more functions. Complete backup and recovery
n g
solutions are designed to protect, back up, archive, and recover data in various computing
i
r n
environments which include large enterprise data centers, remote groups, desktops, and laptops.
e a
Backup software can provide management solutions spanning the entire lifecycle of the data.
e L
Data stored on heterogeneous media, including disks, tapes, and optical storage media, can also
or be managed on-site or remotely. With the help of backup software, data can be easily recovered
from device faults, virus attacks, or unexpected data loss. Examples of advanced backup
M applications are NetBackup, CommVault and Backup Exec.
Tape libraries have been the traditional backup medium for many years, however nowadays, we
can also use disks and Virtual Tape Libraries for data backup.

The design of a backup system has many factors to consider:
1. Amount of data to be backed up.

2. Frequency of the backups (Recovery Point Objective).
3. Time allowed to make the backups.
4. Retention period, in other words how long the backup data should be kept for recovery
purposes.
5. Granularity and integrity. With that we mean how detailed the backups should be. Should data
be restorable on volume level, on folder level or file level? Also: Is the restore requirement
e n
such that recovered data should be application ready?
/
6. How much time is allowed to restore data? (Restore Time Objective).
o m
e i
All these factors combined there is of course the final question: How much money do I have to
.c
aw
invest in a backup strategy in order to prevent losing money (or actually data that represents
u
.h
money)?
i n g
n
This last question can be answered when we have established the Cost Of Downtime or COD.
r
lea
The COD is a value in Dollars, Euros or Yuan that shows how much money is lost if the data is
//
not available.
p :
t t
Depending on all factors and also taking into consideration the total cost of ownership (TCO),
:h
there are a few backup system methods we can choose from:
s

r c
Disk-to-tape library backup (D2T). e
ou
Disk-to-disk backup (D2D).

es
Disk-to-VTL backup (D2V).

R
Disk-to-disk-to-tape data backup (D2D2T).
i n g
n
D2D backup is a solution that uses disk arrays as both the primary and backup storage media.
r
a
The disk-to-disk backup can be implemented by the following two methods:
e

e L
r
Users deploy a disk array on the backup system as backup media. With the help of the
o backup software, the application data is backed up to the disk array connected to the backup
M server.
Users deploy a new disk array for the backup system as backup media. The new disk array
and the existing online disk array should be of the same brand and model. The data
protection functions provided by the disk arrays, such as LUN copy, snapshot, and remote
replication, copy data from the existing disk array to the new backup disk array.

1. Disk-to-tape backup structure
Disk-to-Tape backup structure
SAN (Fiber Channel/iSCSI)
e n
/
o m
.c
Disk array
i
Physical tape library
we
u a
.h
Backup data flow
i n g
r n
// lea
:
D2T backup is the most widely used backup structure. Although D2T is the most commonly used
p
t
method with companies to back up their data, there are also those who think that this method has
t
:h
potential risks and challenges on the running and management of the backup system. The
s
combination of a physical tape library and backup software can facilitate the planning of backup
e
r c
policies. However, faults caused by the physical tape library usually affect the implementation of
ou
the backup policy and the backup plan of the entire system. According to the IDG, the annual
es
maintenance cost of a physical tape library is 15% of its deployment cost. The physical tape
R
library is comprised of many high-precision mechanical parts. Damage to any of these parts may
n g
result in a system breakdown. Faults caused by physical tape drives and mechanical arms are
i
n
primary causes of physical tape library faults. Once the physical tape library is faulty, users have
r
a
to return it to the manufacturer or replace it with a new one. This may take anything from a few to
e
e L
several days or even longer. During this period, no backup can be made and the backup policy is
or affected greatly.
M The I/O bottleneck on the physical tape library is also considered to be a problem. Physical tapes
are built for sequential reads and writes and do not allow random reads and writes. Therefore, the
I/O performance of a physical tape drive is fixed. If the existing I/O performance cannot meet the
requirement, users can only add more physical tape drives in an attempt to enhance the
performance. The cost of deploying extra physical tape drives is high and the stability of the whole
backup system is decreased with the increase of the number of physical tape drives. Many users
suffer from the data loss due to the physical tape damage or inaccessibility.

The capacity of each physical tape is fixed. The backup policy usually selects several tapes for
incremental or differential backup and the other tapes for full backup. Incremental backups are
much smaller than full backups so multiple incremental backups would probably fit on a single
tape. However, one should not store many incrementals on a tape because a tape failure would
lead to losing a lot of backup sessions then!
2. Disk-to-Disk backup structure
e n
Disk-to-Disk backup structure
/
o m
SAN (Fiber Channel/iSCSI)
e i .c
aw
u
g .h
ni n
r
lea
Primary disk array Primary disk array Backup disk array
: //
t t p
:h
Backup data flow
e s
c
r
s ou
e
The big advantage of D2D solutions is the backup performance. Backing up data on a disk
R
(especially if the disk is a volume on a dedicated storage system) is much faster than backing up
n g
to tape. The backup can then also benefit from the storage network to move the backup data
i
across.
r n
a
It is even possible (but not advised) to use a part of the capacity as storage for the D2D backup
e
L
strategy. The risk here of course is loss of original data nd backup data when the physical
e
or
storage system becomes unavailable! Huawei offers special solutions that consist of dedicated
backup software and backup storage capacity.
M

3. Disk-to-VTL backup structure
Disk-to-VTL backup structure
SAN (Fiber Channel/IP/SAS)
e n
/
o m
i .c
Disk array
e
VTL
aw
u
.h
Backup data flow
i n g
r n
// lea
:
In the D2V backup structure, the VTL uses physical disks as storage media, virtual engines
p
t
integrate mechanical arms, disk drives and tape slots. Without mechanical parts, the reliability
t
:h
and maintainability of the VTL are equal to those of disk arrays and much better than those of the
s
physical tape library. A VTL uses physical disks as its storage medium. When compared with the
e
r c
sequential read/write performance of physical tapes, physical disks deliver higher performance in
ou
random reads/writes as well as high-speed addressing. The I/O performance of a VTL is
es
determined by its external bandwidth, instead of the types and quantity of the physical tape drives
inside it.
R
i n g
r n
A VTL uses virtual engines and the connected servers also regard the VTL as a physical tape
a
library. However, a physical tape library must run specific backup software before being accessed.
e
e L
A VTL uses physical disks to store data but does not use them as the storage medium, protecting
or data from accidental deletion and viruses.
M The VTL improves the backup efficiency and ensures the reliability of the backup system, but
does not increase the system investment. However, some issues must be taken into
consideration. First, the VTL stores all the data on physical disks, and these disks are scattered in
RAID groups. The need to archive important backup data imposes challenges on the VTL,
because users cannot locate which physical disk the data is stored on unlike on a physical tape
library, where one can easily locate the correct tape.

Secondly, the VTL cannot compress data in the same way as a physical tape library can. Thirdly,
the VTL does not provide the on-demand storage function, that is, the VTL can only provide fixed
space for incremental or differential backup, but cannot provide only the space that is actually
required.
4. Two Stage backup structure D2D2T

e n
/
Two Stage backup structure - D2D2T
o m
e i .c
D2D2T: Disk-to-disk-to-tape backup
aw
u
SAN (Fibre Channel/IP/SAS)
g .h
ni n
r
Offline archiving
// lea
:
VTL
p
t
Online disk array Online disk array Tape library
t
Backup data flow
s :h
r c e
ou
es
R
The D2D2T is the most suitable backup method, meeting the requirements on reliability,
n g
manageability and performance.
i
r n
e a
A VTL is safe, reliable and of high performance while a physical tape library can support the
L
media movement. The best solution must combine their advantages as follows:
e
o

r
M
Use physical disks as a level-1 backup medium and protect them with RAID.
Use the VTL technology on host clients to ensure the manageability and security of the
backup system.
Employ the on-demand storage function to fully utilize storage resources.
Allow data to be exported from virtual tapes to physical tapes, facilitating the archiving and remote
storage of backup data.

Deduplication
Deduplication
C A B C D
e n
BIndexAand metadata
/
B A A De-dupe
o m
.c
D B B C A
Original data Duplicates removed

e i
aw
u
g .h
ni n
r
// lea
:
The deduplication technology eliminates duplicate data by using hardware or software to reduce
p
the occupied storage space.
t t
The deduplication process is as follows:
s :h

r c e
ou
Stores original data on the storage media.

s
Compares fixed sized data blocks.

Re
Stores the unique data in the deduplicated space. Compares new data with the unique data in
g
the space, deletes the duplicate data, and stores the index and metadata in the specified
space.
n i n
ar
L e
Benefits to backup:
r e Saves great amounts of storage space, leverages storage resources, and lowers users' TCO.
o Reduces the required backup window.

Comparison between deduplication and compression
Comparison between deduplication and compression
Item Function Implementation Data Content Condition
Compares blocks and Retains only Has blocks
e n
/
Deduplication. retains only unique unique data available for
data sources. sources. comparison.
Saves storage
o m
.c
space.
i
Has the
Implements a
e
Does not modify compression
Compression. compression
original data. software
algorithm.
w
available.
u a
g .h
ni n
r
Slide 12
// lea
p :
Deduplication can be regarded as a special type of compression. A deduplication algorithm
t t
divides data into blocks (each of 4 KB, 16 KB, or 32 KB) and compares the blocks to find
:h
duplicates. Unique data blocks are then saved on to the physical disk space.
s
r c e
ou
Deduplication is primarily used to delete duplicate data before backup, so it requires basic data
blocks for comparison.
es
R
i n g
Compression is implemented by a compression algorithm to reduce the file size. Deleting
n
duplicate data is only one of the file compression methods.
ar
L e
r e
o
M

Deduplication categories
Deduplication categories
Deduplication can be divided into multiple categories by location,

time, granularity, and scope.
e n
/
o m
e i .c
aw
u
g .h
ni n
r
// lea
Deduplication at source end.
p :
t
Deletes duplicate data and then copies data to a backup device.
t
Deduplication at the target end.
s :h
c e
Transfers data to a backup device and deletes duplicate data during data storage.
r
ou
Inline deduplication.
es
Deletes duplicate data before writing data to disks.
i n g
Post-processing deduplication.
n
Deletes duplicate data after writing data to disks.
ar

e
Adaptive deduplication.
eL
Uses inline deduplication in environments with low performance requirements and uses post-
or
processing in environments with high performance requirements.
M File-level deduplication.
Checks the properties of files to be stored according to the file system index and compares
them with files that have already been stored. It is also called single instance storage (SIS). If
no identical file exists, the technology stores the new files and updates the index. If an identical
file already exists, it only stores the pointer to the existing file.

Block-level deduplication.
Divides files and objects into data blocks with fixed or with variable lengths, computes the
Hash values of these new data blocks and compares them with values with those of the
existing data blocks, and deletes duplicate data blocks if their values are the same.
Byte-level deduplication.
Searches for and deletes duplicate data by byte, and usually uses a compression algorithm to
compress data for storage.
e n
/
m
Local deduplication.
Compares only new data with data stored on the local storage device.
.c o
e i
Global deduplication.
aw
Compares new data with data stored in all storage devices in the deduplication domain.
u
g .h
ni n
r
Key indexes of Deduplication
// lea
p :
Key indexes of Deduplication
t t
s :h
Customers' concerns
r c e Key indexes
ou
Deduplication
How much space and TCO can be saved?
ratio
es
R
How long does a deduplication process take? Deduplication
Will it affect the backup window? performance
i n g
Is data after deduplication reliable and
n
Data reliability
recoverable?
ar
e
How long can data recovery (DR) be ready in DR Replication
L
scenarios? performance
r e How long does DR take after production data is Recovery
o
lost? performance

Contents of a backup strategy
Contents of a backup strategy
Files, operating systems, databases, raw device backup, backup

Data type:
software logs, etc.
Backup media: Disks, tapes, backup servers, etc.
e n
Backup type: Full, incremental, and differential backup.
/
o m
.c
Data retention period: 1 week, 1 month, 1 year, etc.
e i
w
Backup period: Every day, every week, etc.
u a
.h
Backup window: Time elapsed for a backup operation.
i n g
r n
// lea
Data type: the type of data that we need to protect.
p :

t t
Backup media: the device to which protected data is backed up. It is also the backup
:h
destination.
e s
c
Backup type: the backup method, including full backup, incremental backup, and differential
r
ou
backup.
es
Data retention period: the period of time when data is saved on storage media. It is also the
R
validity period of backup data.
i n g
Backup period: the frequency of backup jobs. It can be daily, weekly, monthly, etc.
r n
a
Backup window: the period of time from the start to the end of a backup job.
e
eL
Selecting a backup policy:
or
- Perform a full backup job for an operating system or application software every time the
M -
operating system is updated or new application software is installed.
Perform a full backup job for critical application data during off-peak hours every day,
because the data is updated every day but the total amount of data is not large.
- Perform a full backup job for critical applications every week or month, and perform
incremental backup jobs for them with a higher frequency, because the data is only
updated slightly every day.

Backup strategy - Data type
Backup strategy - Data type
Files, databases, operating systems, application software, etc.
Files/folders: Word / Excel / PPT / photo...
e n
Database: Oracle / DB2 / Informix / Sybase
/
o m
.c
Logical volumes: Oracle / MySQL
e i
w
Operating systems: Windows / Red Hat / SUSE...
u a
.h
Backup software: Backup Exec / NetBackup / CommVault...
i n g
r n
// lea
:
It is highly recommended to categorize the data that an organization uses. Categories could be:
p
t
valuable data that needs to be up-to-date as much as possible, archival data that must be kept
t
:h
but typically will not be accessed on a regular base. Depending on the categories that exist for
s
each of the categories other backup requirements can be defined which at that point will lead to
e
r c
different backup strategies i.e. hardware medium, retention, backup frequency etc.
s ou
Re
i n g
r n
e a
e L
or
M

Backup media
Backup media
Common backup media include disk arrays, tape libraries, VTLs and
CD-ROM towers/libraries.
e n
/
o m
e i .c
w
Disk array Tape library VTL CD-ROM
tower/library
u a
g .h
ni n
r
// lea
Disk array.
p :

t t
:h
Advantages:
s
high performance, fast read/write speed, easy maintenance, redundant components
c e
(including power supplies, fans, and controllers), easily impacted by environmental
r
ou
factors (including temperature, humidity, and dust), and RAID protection for disk arrays.
Disadvantages:
es
R
g
high initial investment, unsatisfactory storage efficiency, prone to man-made mistakes.
n i n
r
Physical tape library.
a
e
eL
Advantages:
or
tape-based storage system (a combination of drives, slots, mechanical arms, and tapes),
low cost per storage unit, separation of data and read/write devices, theoretically
M unlimited storage space.
Disadvantages:
high hardware failure rate, fragile tape media easily impacted by environmental factors
(including temperature, humidity and magnetic influences), high management and
maintenance costs, poor device redundancy (even large-scale tape libraries only have
redundant power supplies), long backup and restoration periods, and applicable to
sequential reads/writes only.

Virtual Tape Library (VTL).
Advantages:
easy management, high performance, adaptive to existing tape storage systems, high storage
performance and advanced technologies (including compression and deduplication).
Disadvantages:
high cost per storage unit (as disks are used as the storage medium), high deployment cost,
and lower capacity expansion capability than tape libraries.
e n
CD-ROM tower/library. /
o m
.c
Advantages:
low prices of drives and disks, long data retention periods, and low requirements on storage
e i
environments.
aw
u
.h
Disadvantages:
low read/write speed, limited numbers of drives, data sources, and supported users, and
inability to repeatedly write data to and erase data from the storage media.
i n g
r n
// lea
Backup strategy Backup Window
p :
t t
: hWindow
s
Backup strategy Backup
e
r c
o u
s
A backup window is the interval of time during which it is possible to
R
system.e
back up data from a system without degrading performance on the
i n g 80
rn
70
60
e a 50
Network
L
40
utilization
30
r e 20
o 10
M
0
0
9
00
00
00
:0
:0
:0
:5
0:
4:
8:
12
16
20
23
Business continuity and backup windows are in conflict. A good backup system must balance
these two factors.

As shown in the figure, the network utilization between 8:00 to 12:00 is the highest. So this period
of time is not a suitable backup window as it will affect the system services. Perform data backup
during periods when the network utilization is low.
For most companies backup windows have become smaller over the last couple of years. We live
in a 24 hour economy and people need access to their data almost around the clock.
The solution is to improve the speed with which we can do the physical backups. One way is to
e n
/
get the best (fastest) possible hardware. The second way is using differential and incremental
m
backups. This allows the time to backup the relevant data to be much shorter. However: these
two methods have one downside: restoring data takes longer than with the traditional full backup.
.c o
e i
aw
u
g .h
ni n
Backup strategy backup type
r
// lea
Backup strategy backup type
p :
t t
Full backup
s :hDifferential backup Incremental backup
Sun.
r c e Sun. Sun.
ou
Mon. Mon. Mon.
s
Tue. Tue. Tue.
Wed.
Thu.
Re Wed.
Thu.
Wed.
Thu.
ing
Fri. Fri. Fri.
rn
Sat. Sat. Sat.
a
Sun. Sun. Sun.
e
eL
Full backup every day Full backup once a week Full backup once a week
or
Easy to manage Differential backup on Incremental backup on
other days other days
Full backup: Copies all data from a volume to one (ore more tapes)
Advantages:
fast data recovery based on the previous full backup data and short recovery windows.
Disadvantages:
large storage space occupation and long backup windows.

Differential backup: copies all changes since the last full backup to tape. Full backups are taken in
the weekend and daily differential backups are made. As the week progresses more data has to
be backed-up!
Advantages:
Reduced storage space occupation compared with full backup, and short backup and
recovery windows.
Disadvantage:
n
Data recovery must depend on the full backup data and differential backup data.
/ e
Incremental backup: copies all changes since the last incremental backup. Full backups are taken
o m
.c
in the weekend and daily incremental backups are made. Per day only the daily changes are
backed up.
e i
Advantages:
aw
u
.h
Small storage space occupation and short backup windows.
Disadvantages:
i n g
Data recovery must depend on the previous full backup data and incremental backup
r n
lea
data of each time, resulting in slow data reconstruction and large recovery windows.
: //
t t p
s :h
r c e
s ou
Re
i n g
r n
e a
e L
or
M

Backup strategy retention period
Backup strategy retention period
A retention period defines how long backup data can be saved. Only
after this period expires the backup data can be overwritten.
Dispose Create
e n
/
l
o m
l Archive Data life cycle l Protect
e i .c
aw
u
.h
l Migrate l Access
i n g
r n
// lea
:
The system administrator defines a retention period for each backup. When the retention period
p
t
expires, the backup software automatically deletes the backup information from the backup
t
:h
software database (but not from tapes and disks). This way, users can no longer find related
backup data.
e s
r c
ou
When data is created, the important data is protected normally because it is frequently accessed.
es
The importance of the data decreases over time and will eventually be migrated to a storage
R
media with a larger capacity but lower performance. As time goes by, and the importance of the
n g
data continues to drop, it will be archived on the least important storage media. After the data
i
r n
retention period expires, the data will be disposed off, and this backup set will become invalid.
e a
e L
Note:
or A backup set is a group of data that is backed up in a batch. A backup set can be used for either
full backup or incremental backup.
M

Huawei Backup Products: VTL6900 family
Huawei Backup Products: VTL6900 family
Dedicated disk backup system VTL6900
Cluster
All-in-one device Single-node
e n
/
o m
i .c
Architecture: Architecture: Architecture:
e
all-in-one device. single-engine + array. clustered engines + array.
Max. performance: 2.34 TB/hr. Max. performance: 9 TB/hr. Max. performance: 31 TB/hr.
a
Max. capacity: 48 TB. Max. capacity: 864 TB. Max. capacity: 1728 TB.
Flexible and easy deployment. Easy to expand, high efficiency, Stable and reliable.
u
.h
and low energy consumption.
i n g
r n
// lea
p :
t t
s :h
r c e
s ou
Re
i n g
r n
e a
e L
or
M

VTL centralized backup solution
VTL centralized backup solution
VTL centralized backup

Small-scale centralized data backup
solution
All-in-one (20 TB to 50 TB at 2.34 TB/hour).
LAN device
All-in-one device: low cost and easy
deployment.
IP IP IP IP IP IP
Medium-scale centralized data backup
e n
/
Backup (50 TB to 500 TB at 9 TB/hour).
m
Fibre Channel SAN server Single-node + array: high cost-
Single-node
o
effectiveness, easy management and
.c
maintenance.
e i
Large-scale centralized data backup
w
(500+ TB at 31 TB/hour).
a
Inline/Post- Highly reliable cluster: high
VTL6900
u
processing performance/concurrent flow backup,
.h
deduplication Cluster and central management.
i n g
r n
// lea
Small and medium scale sites:
p :
t t
:h
Capacity: 20 TB to 160 TB.
e s
Retention period: 1 to 6 months.
r c
s ou

e
Performance: 400 MB/s to 1250 MB/s.
R

i n g
Budget: limited.
r n
e a
e L
or
M

VTL Backup and archiving solution
VTL backup and archiving solution
Application scenarios:
Data center
Large amounts of historical data requires long-term
retention (6+ months).
The existing physical tape library delivers low LAN
backup performance. IP IP IP IP IP IP
n
Backup management and maintenance are
e
complicated.
The existing devices must be reused to reduce cost.
/
m
Backup
. server
Fibre Channel SAN
o
Customer benefits:
.c
The VTL6900 functions as a high-performance
archiving cache, greatly reducing the backup
window. FC
e i
w
FC
Existing physical tape libraries are used to provide
large-capacity archiving storage resources.
The VTL6900 automatically archives backup data
u a
.h
VTL6900 Physical tape library
to the tape library, simplifying data management.

i n g
n
Slide 23
r
Tiered backup:
// lea
p :

t t
:h
The existing physical tape library must be reused.
e s

c
The original backup performance is lower than 200 MB/s.
r

s ou
The backup retention period is longer than 12 months.
Re
i n g
r n
e a
e L
o r
M

Introduction to HDP3500E
Introduction to HDP3500E
The HDP3500E is a high-performance backup device that

combines backup software, backup server, and backup media.
The HDP3500E runs NetBackup to deliver all-round data

protection for mission-critical services.
e n
/
o m
e i .c
aw
u
g .h
ni n
r
// lea
:
Twelve slots in 2U space, 18 TB available backup capacity and four GE service network ports
p
t t
:h
HDP3500E systems can scale out to form a backup domain so as to achieve a linear growth of
backup capacity and performance.
e s
r c
s ou
Re
i n g
r n
e a
e L
or
M

HDP3500E + tape library solution
HDP3500E + tape library solution
n
HDP3500E
master server
Backup domain
/ e
m
HDP3500E
o
media server
...
.c
Fiber Channel switch
HDP3500E
e i
w
media server
Disk array Physical tape library
u a
.h
Backup data flow
LAN
g
SAN
ni n
r
// lea
In this solution, multiple HDP3500E systems form a backup domain. One HDP3500 system
p :
functions as a master server while the rest function as media servers.
t t
s :h
Backup data is transmitted over a LAN. The backup data is first saved on local disks in
r c e
HDP3500E systems, and is then periodically migrated to the physical tape library. This tiered
ou
storage of backup data improves storage utilization and the overall total cost.
es
R
If the storage space becomes insufficient, more HDP3500E systems can be added to the backup
n g
domain to improve backup performance and increase the overall storage space. External physical
i
r n
tape libraries can also be added to the domain to achieve tiered data storage and improve the
e a
storage utilization. The external tape libraries must support the Vault function for offline disk
L
management.
e
or
M

Backup Software Architecture
Backup software architecture
NetBackup Global data

NetBackup architecture master server manager
e n
/
NetBackup
o m
.c
media server
e i
aw
u
NetBackup
.h
client/agent
i n g
r n
// lea
The NetBackup software consists of the following components:
p :
Master server:
t t
:h
Manages all modules in a backup system as well as monitors the progress of backup
s
r c e
policies, backup tasks, and data recovery tasks.
Media server:
s ou
e
Manages media devices as well as communication and I/O operations among media
R
g
devices. It is the middleware between backup servers and backup media.
n i n

ar
Client:
L e Functions as the target backup device and is used to communicate with the master server.
r e
o Agent:
M Required for database backup.
Management console:
Provides an intuitive GUI used to manage backup software.

Introduction to Disaster Recovery
Some companies must have an ICT

infra-structure that must provide
Business Continuity even when a
disaster takes place. When creating
n
the ICT infrastructure they must
e
assume a worst case scenario.
/
m
Examples of disasters are fires, floods,
earthquakes or large scale failures in
the power grid of a state or country.
.c o
For disaster recovery solutions
e i
the RTO is typically less than
minutes and sometimes it
aw
u
.h
should be (near) to zero.
i n g
r n
// lea
:
There are many examples where companies did have a good backup strategy but when those
p
t
companies were faced with a disaster their backup strategy proved to be too limited.
t
s :h
Fortunately disasters like the 2012 tsunami and the eruption of volcanos do not happen on a
r c e
weekly basis. However, if it happens to your company then the company may not survive. To
ou
think of a good disaster recovery plan means you have to think of the worst case scenario. What
es
is the greatest disaster, the building in which my data is stored, can experience. If your company
R
is based in earthquake zones or is next to a river that floods every so many years you know it is a
n g
matter of time until things go wrong.
i
r n
e a
If you are in the neighbourhood of a nuclear power plant or if you are near to an oil refinery it is
L
not predictable when a disaster takes place. However, when it happens you are impacted. Even
e
or
when the building itself is not damaged in any way, the police or fire brigade will have you leave
the building for security reasons. From that point your local data is inaccessible.
M
A disaster recovery plan will then tell what the next steps are to keep the business up and running.
Most disaster recovery plans are based on using two sets of data that are kept as far away from
each other as possible. This should prevent both the local and the remote site to be struck by the
same disaster.

In a good disaster recovery plan:
Loss of user data is prevented.
Access to recovered data is immediate.
n
Applications to work with the recovered data is in place.
Staff to use the applications and recovered data is in place.

/ e

o m
.c
There are still traditional backup strategies in place.
e i
aw
u
g
Slide 28
.h
ni n
r
lea
It is one thing to have the user data available after the disaster struck, but more must be done.
//
There must be servers that run the applications that can use the recovered data. The data itself
:
t p
must not be too old as for disaster recovery the RTO and RPO are typically very low. The data
t
:h
itself is not the only thing: There must be people that work with the data. Many disaster recovery
s
plans went wrong because, although they managed to recover the correct data, there were not
enough people to use the data.
r c e
s ou
For organizations that have very short RTO requirements having tapes in remote locations is not
Re
working. Restoring large amounts of data from a tape is usually very time-consuming.
i n g
n
Having a good disaster recovery plan does not mean you can choose not to implement a backup
ar
strategy. Disaster recovery is no substitute for backups because in most cases manually deleting
L e
data (mostly by mistake=> user error) means that the data will also be removed on the remote
r esite automatically. In those situations backup tapes are needed.
o
M There are many disaster recovery methods than can be used. Two popular ones are replication
and host-based mirroring. We will briefly discuss these methods and add a little bit of information
on alternatives too.

Disaster recovery Solutions:
Replication.
Host Base mirroring & Clustering technologies.
n
Intelligent backup software.
/ e
o m
e i .c
aw
u
g .h
ni n
r
// lea
p :
1. Replication
t t
: h Replication
s
Introduction to Disaster Recovery:
e
r c
o u
s
With replication the goal is to have a (near)identical data set available
e
on a remote site that is as far away as possible.
i n g
Synchronous replication
2 4
rn
1 3
e a 6 5
eL
Asynchronous replication
or
2 5
1 4
M 3 6
Replication comes in two different versions: Synchronous and Asynchronous.

With synchronous replication we can be certain that the data kept on the local site is identical to
the recovery data on the remote site. The first step in synchronous replication is to establish a link
between the two sites by connecting the two storage systems together.
Now, when the host application writes data to the volume (in the local storage device) the data
gets stored there but the host will not get a confirmation that it has been stored. First the next
steps should be taken: send a copy of the written data to the remote storage device. Once the
remote storage device has stored the copy of the data it sends an acknowledgement back to the
local site. Only when the acknowledgement is received by the local storage device it will send a
e n
/
m
confirmation of the write to the host. The entire process, steps one through six, takes time. This
time is very much dependable on the time needed to move the copy of the data to the remote site
.c o
e i
and the acknowledge signal back to the local site. This time is referred to as the round trip time.
w
Applications will have to be patient for the confirmation of their writes, but when they receive the
a
u
confirmation they have the guarantee that the data is now physically present on two different
locations.
g .h
ni n
r
In the situation where the round trip time is too long for the application to wait for, asynchronous
lea
replication should be used.
: //
t p
With asynchronous replication the host gets the confirmation directly after the write. At that
t
:h
point it is not certain that the data has a copy on the remote site. That takes another waiting
s
period that again is mostly depending on the round trip time.
e
r c
ou
With asynchronous replication one must understand therefore that there can be a difference
s
between the data on the local site and the remote site.
e
R
i n g
Most vendors of storage devices provide replication in both methods. On top of that they have
n
tools that make the process of failover (automatic or manual) very easy. Of course Huawei
ar
supports all replication options a customer could ever wish for!
L e
r eBecause replication is, as they call it, storage-based there is a requirement to have two (near)
o identical storage devices spread over the two sites. It is the intelligence built in the storage
M devices that perform the replication tasks. Often the replication feature is an extra option that has
to be activated through a purchased license.
The investment costs for all of that is not always achievable / affordable. The alternative could
then be host-based mirroring.

2. Host-Based Mirror
Introduction to Disaster Recovery: Host-Based Mirror
Host-based replication is the processes of using servers to copy data

from one site to another.
Copies file data on application level.
n
Uses LAN / WAN.
/ e
o m
e i .c
aw
Hosts can be configured as nodes of a stretched cluster for seamless
u
.h
failover.
i n g
r n
// lea
:
With host-based mirroring the actual copying is done on the servers that house the application
p
t
whos data should be copied. It is typically a much cheaper solution and it still has the same end
t
:h
result. The data is safely stored on a remote site. However: the performance of host-based mirror
s
is lower than traditional replication. And also: the distances that can be reached for copying are
e
often limited to less than 100 km.
r c
s ou
e
If the distance is relative small host-based mirroring can be done between two servers that are
R
part of a cluster. In that case the two servers (in cluster terms we call them nodes) actually run the
n g
application together. That means that in case of a node crash the other node will take over
i
r n
immediate. Of course when one of the data volumes is lost the copy is accessible on the remote
site.
e a
e L
or
Next to replication and host-based mirroring there are other possibilities for disaster recovery. In
the next section we will highlight a few of the alternatives.
M

3. Backup software
Introduction to Disaster Recovery: Backup software
Some advanced backup software offer disaster recovery options:
Automatic replication of data that was already backed up.
n
Virtual instant restore of even TB sized volumes.
Log shipping in combination with backup data.

/ e
o m
e i .c
aw
u
g .h
ni n
r
// lea
p :
t t
s :h
r c e
s ou
Re
i n g
r n
e a
e L
or
M

Questions
Questions
1. How many backup topologies are available? What are their advantages
and disadvantages?
2. What are the categories of deduplication technology?
e n
/
o m
e i .c
aw
u
g .h
ni n
r
// lea
p :
t t
:h
Answers
e s
1. LAN-based backup and LAN-free backups. With LAN-based backup the data that is being
r c
backed up goes across the same network as the regular user data. This may lead to
ou
congestion. With LAN-free backups a dedicated network must be built to be used for backup
s
e
purposes only. More costly but with less congestion problems.
R
i n g
2. Ten Deduplication categories:
r n
a. Deduplication at the source end.
e a
b. Deduplication at the source end.
eL
c. Inline deduplication.
or
d. Post-processing deduplication.
M e. Adaptive deduplication.
f. File-level deduplication.
g. Block-level deduplication.
h. Byte-level deduplication.
i. Local deduplication.
j. Global deduplication.

Exam Preparation
Exam Preparation
Multiple response questions:
1. Common backup media include:

a. Tape library.
b. Disk array.
e n
c. VTL.
/
m
d. CD-ROM tower/library.
2. By granularity, deduplication can be divided into:
.c o
a.
b.
File-level deduplication.
Block-level deduplication.
e i
c. Byte-level deduplication.
aw
u
d. Deduplication at source end.
g .h
ni n
r
// lea
Answer (Multiple response questions):
p :
1. A, B, C, D.
t t
2. A, B, C.
s :h
r c e
s ou
Re
i n g
r n
e a
e L
or
M

Summary
Summary
Backup concepts and topologies.

Backup technologies.
Backup policies.
Huawei backup solutions and application.
Disaster Recovery Introduction.
e n
/
o m
e i .c
aw
u
g .h
ni n
r
// lea
p :
t t
s :h
r c e
s ou
Re
i n g
r n
e a
e L
or
M

Thank you
www.huawei.com
e n
/
o m
e i .c
aw
u
g
Slide 36
.h
ni n
r
// lea
p :
t t
s :h
r c e
s ou
Re
i n g
r n
e a
e L
or
M

e n
/
o m
e i .c
aw
u
g .h
ni n
r
// lea
p :
t t
s:h
r c e
sou
Re
i n g
r n
e a
e L
or
M

e n
/
o m
OHC1109108
e i .c
aw
Basics of Cloud Computing u
g .h
ni n
r
lea
://
www.huawei.com
t tp
s:h
r c e
sou
Re
i n g
r n
e a
e L
or
M
e n
/
o m
e i .c
aw
u
g .h
ni n
r
// lea
p :
t t
s:h
r c e
sou
Re
i n g
r n
e a
e L
or
M
Introduction
In this module we will give a glimpse on the future. It is the conviction of most ICT gurus that the
future of ICT is in The Cloud. Many of us will already have some of our data stored in the cloud
because many vendors like Microsoft, Google and Apple offer storage capacity to their users. The
real cloud solution of the future will go one step further than just to offer storage capacity. The
cloud of the future will offer both storage capacity as well as computing power. Essentially we, as
users, only need a very simple device and connect to all resources we need in our cloud.
e n
/
o m
Objectives
e i .c
aw
u
Know the concepts and backgrounds of cloud computing.
g .h

i
Master the deployment and business models of cloud computing.
n n

r
lea
Know the core technologies and value of cloud computing.

//
Master Huawei cloud computing solutions.
p :
t t
s :h
Module Contents
r c e
s ou
1. Concept and background of cloud computing.
e
2. Models of cloud computing.
R
g
3. Core technologies and value of cloud computing.
i n
4. Huawei cloud computing solutions.
n
ar
L e
r e
o
M
HCNA-storage V3 | OHC1109108 Basics of Cloud Computing Page | 287

e n
/
o m
e i .c
aw
u
g .h
ni n
r
// lea
p :
t t
s :h
r c e
s ou
Re
i n g
r n
e a
e L
or
M

Concept of Cloud Computing
Concept of cloud computing
Cloud computing is a style of computing in which dynamically

scalable and often virtualized resources are provided as a service
over the Internet.
From Wikipedia
e n
/
o m
e i .c
aw
u
g .h
ni n
r
lea
: //
t p
Cloud computing is a style of computing in which dynamically scalable and often virtualized
t
:h
resources are provided as a service over the Internet. The term "cloud" is a metaphor for the
network and Internet.
e s
r c
ou
In earlier modules, we initially used the picture of a cloud to indicate a network infrastructure or
the Internet.
es
R
i n g
In this module we will use the cloud symbol, and the general term cloud, to describe an ICT
n
infrastructure as a whole. In that infrastructure the users can obtain desired resources through
ar
networks in an on-demand and scalable manner. In other words, in the cloud there are computing
L e
resources available and storage capabilities. For the users it is not visible where the resources
r ecome from. The only thing is that the cloud guarantees that the computer and storage resources
o you need are available when you need them. Cloud computing resources are therefore
M dynamically scalable and virtualized, provided using Internet. End users do not need to know the
details about the cloud infrastructure, acquire professional knowledge, or even directly operate
the cloud. They only need to know what resources they want and how they can obtain these
resources over the Internet.

Cloud computing from a business perspective
For many companies the term Cloud Computing appears to offer the ideal solution for their ICT
problems. The problems are partly technical (hardware, software, knowledge IT staff, disaster
recovery) as well as economical (costs of hardware, software licenses, training, costs for cooling
and power). Especially for an external cloud, that is when somebody else is responsible for the
cloud, it is just a matter of ordering resources for the business to use.
e n
Business perspective:
/
cloud computing = information power plant
o m
Changes in consumption models
Cloud computing provides software, hardware,
Changes in business models
Users do not need to buy all the required
e i .c
w
and services over the Internet. Users obtain hardware or software, but only need to buy
a
services using browsers or lightweight information services.
u
terminals. buy information services.
Age of PC
Enterprise data center
Age of Internet
g
Internet data center
.h
App2 App1 App3
1
Computing and storage:
ni n
r
migrated from LANs to Internet. App1 App2 Appn
lea
://
LAN
Decoupled hardware
Internet
tp
and software.
App1 App1 App1 Hardware sharing.
t
App2 App2 App2
Appn Appn Appn
s :h
c e
r
Slide 4
s ou
e
A number of services can be distinguished from the perspective of the business owner:
R
DaaS :
i n g
Data as a Service. With Daas we want to use the data wherever it resides
r n
(access the data where it lives). Data may be stored locally or centralized in
e a cloud based storage. Wherever it is the application will find it and access it.
e L
or
IaaS : Infrastructure as a Service. Here the user only worries about resources and
M
not about hardware. The IaaS has to provide everything and keep it running.

PaaS : Platform as a Service. With PaaS the provider will offer a platform to the user.
The user is often a software developer. In traditional environments a software
developer had to consider hardware and operating systems when creating
applications. With PaaS he only has to worry about writing the best application
as the underlying platform is taken care of by the PaaS provider.
SaaS : Software as a Service. This has been the first implementation of the cloud
computing technology. The user had minimal hardware to think about and the
SaaS provider arranged a working environment with an operating system and
e n
/
m
the necessary applications. All the annoying jobs like licensing and software
updates are now handled by the provider of the SaaS environment.
.c o
e i
aw
u
g .h
ni n
r
// lea
p :
t t
s :h
r c e
s ou
Re
i n g
r n
e a
e L
or
M

Cloud computing from a technical perspective
Technical perspective:
cloud computing = computing / storage network
Service and
Community Search Commerce Computing File Storage
application software.
e n
Application service API Cloud capability service API
/
m
Cloud platform
Cluster management Parallel processing Automation software: the soul of
Operating system + virtual machine Distributed storage

cloud computing.
.c o
Servers and storage
e i
w
supporting mass
a
information processing.
u
0.3inch
Ethernet switches
.h
interconnecting
thousands of devices.
i n g
r n
lea
: //
t p
There are a lot of changes in Cloud Computing compared with traditional ICT infrastructures like
t
:h
NAS and SAN. In traditional ICT infrastructures an application would run on a physical server and
s
the application would be stored on a local disk or an external disk. The user data also would be
e
c
stored locally (DAS) or on an external disk (SAN / NAS volume). The ICT administrator was given
r
ou
the task to keep all the hardware components running. All the data generated must be protected
s
against data loss. It meant that within every organization there must be knowledge about server
e
R
technology, application, operating systems, networking, storage technology and backup / disaster
i n g
recovery technologies. Imagine the problems a traditional ICT infrastructure could face today with
n
ever increasing amounts of user data being generated. Also look at the demands applications
ar
have today that might exceed the potential of any single server.
L e
r e
A very important concept within ICT nowadays, and also the fundamental technology with Cloud
o
Computing, is Virtualization.

Virtualization
Concept of cloud computing: Virtualization
Storage virtualization.
The act of abstracting, hiding, or isolating the internal function of a storage
(sub) system or service from applications, compute servers or general
e n
network resources for the purpose of enabling application and network
/
independent management of storage or data.
o m
Compute virtualization.
e i .c
Software that enables a single server hardware platform to support multiple
aw
u
concurrent instances of an operating system and applications.
g .h
ni n
r
lea
: //
There are two kinds of virtualization: storage and compute.
t t p
s :h
Storage virtualization is the goal to have storage become a resource (or commodity) that is
c e
available to the user. The user itself has no idea about the technical aspect of managing the
r
ou
hardware. The only thing the user specifies is the number of gigabytes he would need and the
s
performance requirements of the storage.
e
R
i n g
Compute virtualization (or sometimes called server virtualization) separates the operating
n
system and the applications from the physical hardware needed to run them. The traditional
ar
approach when setting up an ICT infrastructure is to take hosts, install operating systems and
L e
install applications on the hosts. There was almost always a one-application-per-server policy so
r ethe number of physical servers used was equal to the amount of applications a company needed.
o In most situations the application would only use a limited fraction of the resources (CPU, RAM,
M storage capacity) available.
With compute virtualization the goal is to emulate multiple virtual servers running on the same
physical hardware. Well known compute virtualization vendors are VMWare; XEN; KVM and
Virtuozzo.Huaweis implementation is positioned as FusionCloud. In FusionCloud functionalities
as FusionSphere, FusionStorage and FusionNetwork are present.

A good Cloud environment can support/offer both virtualization methods. Then the environment
will offer these specifications:
On the virtualized platforms, applications can be expanded, migrated, and backed up.
Dynamic expansion: Applications can be dynamically expanded. More servers can be added
into existing server clusters in real time to increase the computing capability.
e n
/
On-demand deployment: The cloud computing platform allocates resources and computing
capabilities to applications on demand.
o m
High reliability: Virtualization scatters applications and computing resources to different
e i .c
physical servers. If one server breaks down, a new server can be added using the dynamic
aw
expansion function, ensuring the proper operation of applications and computing.
u
g .h
High cost efficiency: Cloud computing employs a virtual resource pool to manage all
ni n
resources, posing low requirements on physical resources. The cloud formed using low-cost
r
lea
PCs can deliver higher performance than a mainframe computer.
: //
t t p
:h
Cloud computing:
s
a combination of business models and technologies
e
r c
s ou Cloud platform Cloud service
Re Distributed &
parallel software SaaS PaaS
g
Internet
n i n IaaS
r
Servers & storage
e a
e L
r
Cloud service Cloud platform
+
o
On-demand business models Distributed and parallel software systems
Huge Capability
M
In on-demand business models, user application software and data is stored in the cloud, and can
be accessed using clients. Cloud service providers offer services to customers based on their
needs and charge fees correspondingly.

Background of cloud computing
Software engineering has The interaction mode is becoming more

changed from machine or and more fine tuned to the users habits.
Interaction mode
language oriented to
requirement, network, and Keyboard Mouse Touch Voice
service-oriented.
e n
/
Computing device
m
1970S Process-oriented
1980S Object-oriented
.c o
i
1990S Component-oriented
e
2000S Field-oriented
w
2010S Service-oriented 1970s 1980s 2010s
1990s 2000s
Mainframe
computer
Midrange
computer
PC Desktop
Internet
u aMobile
Internet
g
Slide 8
.h
ni n
r
lea
Over the past fifty years there was a big change in computing devices: mainframe computers in
//
the 1960s; midrange computers in the 1970s; PCs and LANs in the 1980s and desktop Internet
:
and mobile Internet in the 1990s.
t t p
:h
Computing devices are changing from standalone computers to network connected devices.
e s
Communications technologies and networks are developing at a greater speed than predicted by
Moore's law.
r c
s ou
e
Secondly, in the last forty years, there was a change in the way software was engineered: In the
R
1970s, flowcharts were used in top-down programming styles. Later the focus was on object-
n g
oriented programming. Then in the 1990s the focus moved to service-oriented programming that
i
r n
we still see today. Software engineering is no longer oriented towards hosts, such as their
e a
machines, languages, and middleware, but is oriented towards requirements and services over
e L
networks. This is what we call Software as a Service (SaaS). The development of cloud
or computing software aims to provide services to customers to suit their needs.
M Thirdly, over the last half-century, the way humans interact with computers has changed. In the
beginning all programs required input via a keyboard. A big change was the move to the graphical
user interfaces that used a mouse to give inputs to the program. Today there are computers and
applications that can be operated based on touch, voice, and gestures. The interaction method is
no longer computer-centered but user-centered. On the cloud computing infrastructure, users are
not required to be computer engineers or IT specialists, but only need to focus on their core
applications.

Driving forces of cloud computing
Driving forces of cloud computing
Low investment, high performance and good user experience.
Customer
e n
/
requirements
o m
Development Changes in
e i .c
w
Diagram
of
Diagram Diagram
business
Diagram
22
a
technologies 33
models
u
Virtualization, distributed and parallel
computing, Internet and web technologies.
g .h
Cloud computing as a service.
ni n
r
lea
: //
t p
The popularity of cloud computing solutions of course has its reasons. Here are a few examples
t
:h
why cloud computing is used:
e s

r c
Government and enterprise users need high-performance information systems at low
ou
investment costs.
es

R
Individual users want to be able to access their data wherever they are. So often the
n g
requirements include that they should be able to use smart phones or tables. This is referred
i
n
to as BYOD which is short for Bring Your Own Device.
r
e a

L
The advanced technology used in cloud computing offers low cost storage. But there is more:
e
o rin the cloud all data protection options can be offered too (BaaS or Backup as a Service).
M The maturity of the broadband technology and the increased population of subscribers have
made Internet-based services mainstream. That not only applies to the performance but also
to the scalability in distance. There is high speed internet almost everywhere now.
In the age of Big Data it is almost a necessity to adopt Cloud computing. The success of
many cloud implementations have shown that it works! Examples are Googles Google Docs;
Microsofts Office 365 and Apples iCloud.

Cloud computing models
Deployment models of cloud computing
Private
cloud
e n
/
o m
Hybrid
Public
cloud
e i .c
w
cloud
u a
g .h
ni n
r
lea
: //
t p
Cloud computing has three deployment models: private cloud computing, public cloud computing,
t
:h
and hybrid cloud computing.
e s

r c
Private cloud computing: It is usually operated and used by the same organization.
ou
Huawei's data centers use this deployment model. Huawei is both the operator and end user
of the data centers.
es
R

i n g
Public cloud computing: It is like a public switch. It is operated by a telecommunications
n
carrier but used by the public.
ar
e
eL
Hybrid cloud computing: Its infrastructure is a combination of the previous two types of
or
clouds. Looking from the outside it appears to be one entity, one cloud. But it remains two
different environments. An enterprise using a hybrid cloud would store its important data
M (such as financial data) in its private cloud and unimportant data in the public cloud. Another
example is e-commerce websites. The service volume of an e-commerce website during
ordinary days is stable, so the website is able to operate these services in its private cloud.
However, during events such as sales promotion activities, the service volume surges and the
website has to rent servers from the public cloud to process its services. Resources in both
the public and private cloud can be scheduled in a unified manner, so this is a typical
application of a hybrid cloud.

Business models of Cloud computing
Business models of cloud computing
User SaaS
CRM, email, games, instant message
e n
/
PaaS
Developer Cloud service
Database, web server, IDE
o m
.c
IaaS
i
User Storage, network, server
Virtualization
we
Server Storage Network
u a
g .h
ni n
r
lea
: //
Data as a Service (DaaS)
t t p
:h
The user can access his data without really knowing where it resides. Office 365 and GoogleDocs
are examples.
e s
r c
ou
Infrastructure as a Service (IaaS)
s
IaaS providers offer all kinds of infrastructure resources to users, including processors, storage
e
R
devices, networks, and other basic computing resources. With IaaS, users can deploy and run
i n g
any software from operating systems to applications. Amazon Elastic Compute cloud (EC2) is a
n
typical representative of IaaS.
ar
L e
Platform as a Service (PaaS)
r e
PaaS providers offer application development platforms (such as Java and .net) running on the
o
cloud computing infrastructure to users. Microsofts Azure is a typical example of PaaS.
MSoftware as a Service (SaaS)

SaaS providers offer applications (such as CRM, ERP, and OA) running on the cloud computing
infrastructure to users. Salesforce online CRM is a typical application of SaaS.
Other than the previous three business models, there are some other business models: Backup
as a service (BaaS), Desktop as a Service (DaaS); Remote Management as a Service (RmaaS).

Categories of cloud computing
Categories of cloud computing
Dividing a big physical machine to small APP APP APP APP APP APP
virtual machines.
VM1 VM2 VMn VM1 VM2 VMn
e n
/
VMM VMM
Physical machine Physical machine
o m
Aggregating smaller physical machines
into a big physical machine.
APP1 APP1
e
APP1
i .c
w
MapReduce MapReduce MapReduce
a
Physical machine Physical machine Physical machine
u
.h
APP1
i n gPhysical machine
r n
lea
: //
t p
The deployment of cloud computing can be divided into two categories: The division of a big
t
:h
physical machine to small virtual machines and the aggregation of smaller physical machines into
a big physical machine.
e s
r c
ou
The division of a big physical machine into small virtual machines:
s
Virtualizes the resources of a high-performance physical machine, and uses these resources to
e
R
create a resource pool that combines the functions of computing, storage, and networking. Key
i n g
technologies used in this method include virtualization, surveillance, scheduling, and migration of
n
virtual machines. It is applicable in scenarios supporting time-division multiplexing. Amazon EC2
ar
is a typical application of this category.
L e
r eThe aggregation of smaller physical machines into a big physical machine:
o Group a number of multiple low-performance physical resources into a single logical high-
M performance physical resource. With this method, a task that requires a lot of resources can be
allocated to multiple small physical machines for processing. Key technologies used in this
method include task breakdown and scheduling, distributed communications bus, and global
consistency. Services like the ones provided by Google are a typical application of this category.

Compute Virtualization
Core technologies of Cloud Computing-Virtualization
Application
Operating system
e n
/
Virtualization layer
o m
e i .c
aw
u
Computing and storage
g .h
ni n
r
lea
: //
t p
Compute or Server Virtualization refers to the creation of a virtual machine with physical IT
t
:h
resources. It plays an important role in large-scale data center management and solution delivery.
s
It is the solid foundation for cloud computing. Using this technology, computing, storage, and
e
c
network resources can be virtualized as services required by users. A major player in the server
r
ou
virtualization market is VMware. It allows a physical server with its resources (CPU cycles, RAM,
s
network interfaces etc.) to be split up into multiple virtual servers. Each of the virtual servers (or
e
R
vms) has its own RAM, amount of CPUs, network cards and they can all run different operating
i n g
systems. Each of the vms lives isolated within the so-called hypervisor software of the
n
virtualization server. That means that if a vm runs into trouble and crashes the other vms living on
ar
the same physical virtualization server will not be impacted.
L e
r e
VMware offers many tools that allow an ICT infrastructure to be made with all characteristics of
o
the cloud: scalable, flexible, secure and manageable.
MA VMware administrator has control over all virtualization servers; over networking components
and storage resources. From one user interface the administrator can create new vms; make
backups of them; relocate them to other storage devices or even can even migrate them.
Migration is the feature where a running vm moves from one virtualization server to another.
This is done because the current server does not have enough resources, because the server is
down or when the server has to go down because of maintenance. All applications on the vms
will continue to run while the move takes place!

Storage Virtualization Thin provisioning
Core technologies of cloud computing-Thin provisioning
Client Client Client Client
e n
/
m
FusionCompute
.c o
Thick Thin Thin
e i
w
20 GB 40 GB 80 GB
u a
.h
Equipment room
20 GB 20 GB
n g
40 GB
i
r n
lea
: //
t p
An administrator can use various storage devices as storage for the virtualization environment.
t
:h
Storage is a very important factor within the VMware philosophy. That is because a virtual
s
machine (vm) is in fact represented by a file. That file has to be accessible to the virtualization
e
c
server. The storage assigned to VMware to keep vms is referred to as a datastore. So for many
r
ou
vms we need a lot of storage or in other words: we need a (lot of) big datastore(s). Datastores
s
are created and later on datastore capacity will be used to store vms on. Datastores that do not
e
R
have vms yet still consume physical storage space as the creating of a datastore implies that the
i n g
storage is allocated to the datastore.
r n
a
For cost effectiveness there is a feature called thin provisioning which is supported in both the
e
e L
hardware of the storage device as well as within VMware.
or Thin provisioning enables flexible, on-demand allocation of storage space, which improves
M storage utilization. This is done by not assigning physical storage to a datastore yet. VMware will
only claim storage capacity from the storage device at the time a vm is created and the space is
actually needed.

With thin provisioning, a system can be initially allocated with storage space that is actually
required by the services in the system, but it gives the appearance of having more storage space.
As time goes by and more vms are created more virtual disks can be added to expand the
storage space. After all configured storage space is allocated a thin disk is using the same
amount of storage capacity as a thick disk.
VMware in general can use storage capacity from different storage devices to be used to form
datastores. So inside the storage architecture different vendors and different types of storage
devices can be used.
e n
/
o m
.c
Space monitoring: This function provides alarms on storage space usage. If the space usage
e i
exceeds the preset threshold, an alarm will be generated. That could be the signal for the
administrator to ask for more budget for the expansion of physical storage capacity.
aw
u
.h
Space reclamation: This is a very useful feature of modern virtualization servers. Imagine that a
g
ni n
thin provisioned volume has been filled up to 80% of the capacity with vms. Now the
r
administrator has decided he wants to remove a number of vms that he created for testing
lea
purposes. The storage capacity allocated to the thin provisioned volume is now more than he
: //
actually needs. Space reclamation will now arrange for all excess space used to be released to
t p
the storage devices. Space reclamation is now supported with the latest versions of VMware and
t
:h
the latest versions of all major operating systems.
e s
r c
s ou
Re
i n g
r n
e a
e L
or
M

Cloud computing - Resource Planning
Core technologies of cloud computing-Quality of

service (QoS) control
BT downloading Web Oracle
e n
/
o m
Fusion Compute
e i .c
aw
u
g .h
ni n
r
lea
: //
t p
Resource planning is an important job within the virtualized environment. As the total of all vms
t
:h
uses resources on one or more virtualization servers it is important that no vm is able to claim all
s
available resources of a virtualization server. On the other hand a vm needs a specific amount of
e
c
resources so that the application on that vm performs well. The resources that have to be planned
r
ou
for are:
es
CPU resource
R
i n g
Every CPU in the virtualization server has a number of cores and each core has computing
n
abilities. The normal expression is: a CPU has so many cycles. The performance of a CPU is
ar
the product of the number of core times the individual number of cycles of a single core.
e
eL
Cycles are expressed in GHz. It shows how many calculations per second a core can do.
or
M

For resource planning on CPU two parameters are used: Limit and Reservation
The limit of a vm for CPU is the maximum number of cycles the vm can claim. Setting a value
for the limit prevents a virtual machine to use up all resources of a virtualization server.
The reservation sets the minimum computing capability needed by a virtual machine. In case
a virtualization server has too many vms it must run, resources might become scarce. At that
point starting a vm would succeed but the vm will have few resources. That would basically
e n
/
mean that the vm will perform poorly. Setting the reservation the vm has a specific amount of
m
cycles to run on. Unless, of course, there are not enough resources. At that point a
reservation will not allow a vm to start.
.c o
e i
Memory resource
aw
u
Again we have two parameters called Limit and Reservation. Most applications have specific
.h
requirements for RAM to have the application perform well. This would be the reservation.
g
i n
When the required RAM resources (expressed in GB) are not available; applications will
n
r
suffer. There are clever solutions built in VMware but it still is an important parameter. Limits
lea
again prevent an application that goes crazy to claim all RAM resources.
: //
Network resource
t t p
:h
This is one of the most complex problems in virtualized environments. Reason is the fact
s
that there are always two separate networks:
e
c
One network is physical and it connects virtualization servers and storage devices. The other
r
ou
network is physical and it allows vms to connect to other vms. Now in the last case the vms
s
might not be in the same physical virtualization server. So the traffic will then be across both
e
networks!
R
i n g
r n
e a
e L
o r
M

Cloud computing Load balancing
Core technologies of cloud computing-Load balancing
App App App App
n
20 GB
/ e
o m
.c
FusionCompute FusionCompute
e i
aw
u
g .h
ni n
r
lea
: //
t p
One of the most amazing features that VMware offers is dynamic resource scheduling or DRS.
t
:h
In a well-designed VMware environment there could be many virtualization servers that together
s
run hundreds of virtual machines. In the above picture there are just two servers and 4 virtual
e
c
machines used, but there is something illogical going on. Three of the vms are on one server and
r
ou
the fourth vm is on another server. DRS could now be setup in such a way that all vms are
s
arranged across the servers so every vm has the resources it needs. If on a server new vms
e
R
have to be created or started then the vm will look for the most suitable server to live on. If a vm
i n g
finds that it has not enough resources on a specific server it can automatically move to another
n
server that has more resources available. While the vm is moving from one server to the other the
ar
application is still working.
L e
r eIf we would translate DRS into the cloud computing environment it means that the application (i.e.
o your email program) could be running on a virtual machine on any of the physical virtualization
M servers.

Value of cloud computing
Value of cloud computing
APP1
Consolidation
of APP2 APP2 APP1
servers APP3 APP4 APP3 APP4
e n
/
Consolidation of resources, improving utilization Automated scheduling, reducing power consumption
o m
Data can
be freely
accessed
Central data
management
e i .c
w
by users.
u a
Traditional IT platform Cloud platform
g .h
i n
Central data management, enhancing information Efficient maintenance, reducing investment
security
r n
lea
: //

t p
A physical server can be virtualized into multiple virtual machines to process different
t
:h
applications.
e s

r c
The specifications (such as the CPU and memory) of a virtual machine can be flexibly
ou
adjusted, and the number of virtual machines in a system can be added or reduced, to suit
es
the changing requirements in computing resources.
n g
Automated scheduling, reducing power consumption.
i
n
To safe costs for power and cooling dynamic power management (DPM) is added. That could
r
a
mean that DRS might decide to consolidate the vms onto a smaller amount of servers. That
e
L
is of course if these servers have enough resources to run the vms. Once this is the case the
e
o rservers that are not required anymore will be switched of. This reduces power consumption
and emissions. Of course when there are more vms powered on or more resources are
M needed it would mean that the servers will be powered on again.
Central data management, enhancing information security.

On a traditional IT platform, data is scattered on different application servers, and this has the
risks of single points of failure. In a cloud system, resources (like vms and datastores) are
centrally managed.

Huawei FusionCloud solutions
In its entire portfolio Huawei of course has some solutions for building cloud computing
environments. In this section we will briefly discuss them.
HUAWEI FusionCloud solutions
e n
/
FusionAccess FusionCloud
o m
Installing VDI on a virtual
platform makes a standard
Installing VDI on
FusionCube make
the VDI FusionCube.
e i .c
w
desktop cloud solution.
a
Installing FusionShpere on
u
FusionCube specific hardware makes the
.h
FusionCube solution.
i n g
r n
FusionSphere virtualizes
lea
FusionSphere physical infrastructures, laying
a foundation for the other two
solutions.
: //
t t p
s :h
c e
Huawei provides three cloud computing solutions:
r

s ou
e
FusionSphere (infrastructure virtualization).

R
FusionCube (all in one).

n g
FusionAccess (desktop cloud).
i
r n
a
FusionSphere is the basis of the other two solutions, and it is used to virtualize the physical
e
e L
infrastructure. FusionSphere can be preinstalled on specific hardware to form the FusionCube
or solution for fast service deployment. A Virtual desktop infrastructure (VDI) can be deployed on
FusionCube or FusionSphere to form the FusionAccess solution.
M

Infrastructure virtualization - FusionSphere
Infrastructure virtualization FusionSphere
Enterprise IT O&M personnel

Third-party
FusionAccess SQL Server personnel
application
e n
/
m
Enterprise IT system
.c o
FusionSphere
FusionManager
e i
FusionCompute
aw
u
Server Storage
g .h
ni n
r
lea
: //
t p
Huaweis FusionSphere virtualizes hardware resources using the virtualization software deployed
t
:h
on physical servers, so that one physical server can function as multiple virtual servers. The
s
server workloads are consolidated and new applications and solutions are deployed on idle
e
c
servers to keep the consolidation rate high. FusionSphere has two main software components:
r
ou
FusionCompute and FusionManager.
es
R
FusionCompute consists mainly of virtual resource management (VRM) and host components. It
i n g
virtualizes physical resources and provides virtualized services to data centers.
r n
a
FusionManager consists of integrated resource management (IRM), self-service provisioning
e
L
(SSP), automatic management engine (AME), identity and access management (IAM), unified
e
or
portal (Uportal), intelligent data base (IDB), common service and bus (CSB), and unified hardware
management (UHM) systems. It is the management software of data center virtualization that
Mmanages virtual resources, hardware resources, and services.
FusionManager reports alarms to the upper-layer network management system (NMS) through
SNMP interfaces. Computing, storage, and network devices can access FusionManager through
SNMP, IPMI, or SSH.

FusionManager obtains configuration and alarm information about virtual resources using
FusionCompute, which manages virtual machines as instructed by FusionManager.
All in one - FusionCube
All in one FusionCube
e n
Cloud infrastructure Cloud
/
m
Computing
management
Network
Elastic
computing
Disaster
recovery Service
.c o
i
management
Storage Virtual
private
Elastic load
balancing
we
Service
protection
a
cloud
u
SSD card
Security
.h
management
Virtualized infrastructure
iNIC card
+ Compression
FusionCube
i n g
Virtualized resource scheduling Automation
n
card
r
Unified
Computing Storage Network
lea
hardware
virtualization virtualization virtualization
management
GPU&SNP
: //
t t p
s :h
c e
FusionCube consolidates computing, storage, and switching devices, and is preinstalled with
r
ou
FusionCompute, FusionManage, and FusionStorage. It virtualizes and centrally manages
hardware resources.
es
R
i n g
FusionCube is an open, scalable, and all-in-one virtual system. Its advanced features such as
n
unified resource management, automatic application deployment help users deploy and maintain
ar
different cloud applications at ease.
L e
r eFusionCube also allows users to customize, deploy, update, and manage service applications in
o both standalone machines and clusters, including Exchange, SharePoint, Enterprise Resource
M Planning (ERP), Customer Relationship Management (CRM), Virtual Desktop Infrastructure (VDI),
and SQL Server.

Desktop cloud - FusionAccess
Desktop cloud FusionAccess
Virtual desktop management layer
O&M management system

e n
Existing IT system
/
Access control layer
Cloud terminal
Cloud computing infrastructure
o m
.c
Virtualization infrastructure
Server virtualization / Network virtualization /
Storage virtualization
e i
aw
u
Hardware resources
.h
Server / Storage / Network
i n g
r n
lea
: //
FusionAccess delivers virtual desktop applications based on HUAWEI FusionCube and
t t p
:h
FusionSphere. By deploying software and hardware on these cloud platforms, users can access
s
cross-platform applications and even the entire desktop cloud using thin clients (TCs) or other
e
devices connected to the Internet.
r c
s ou
FusionAccess addresses challenges faced by PCs such as security issues, investment concerns,
Re
and work efficiency considerations. It is a wise choice for financial institutions, large- and medium-
i n g
sized enterprises, government departments, call centers, customer service centers, medical
n
organizations, military agencies, and dispersed, outdoor, or mobile offices. Logical architecture of
a
FusionAccess:r
L e

r e
Hardware resources
o Hardware refers to FusionAccess hardware infrastructure, including servers, storage devices,
M switching devices, racks, security devices, firewalls and power supply equipment.
Virtualization infrastructure platform

It virtualizes various physical resources in the desktop cloud based on resource requirements
of virtual desktops.

Cloud computing infrastructure platform
The cloud computing infrastructure platform includes the following:
Cloud resource management: FusionCloud manages virtual user desktop resources

including computing, storage, and network resources.
Cloud resource scheduling: FusionCloud migrates virtual machines from high-load

physical resources to low-load physical resources based on the current system running
status.
e n
Virtual desktop management layer.
/
o m
i .c
This layer authenticates virtual desktop users. This helps to ensure the security of the virtual
e
desktop application and to manage sessions of all virtual desktops in the system.
aw

u
.h
Access control layer
access gateway, firewall and load balancer.

i n g
This layer effectively controls access from terminals. Access control devices include the
r n
O&M management system
// lea
p :
This system incorporates service operation management as well as O&M management.
t t
:h
Service operation management is responsible for service processes such as account
creation and deletion.
e s

r c
O&M management is used to operate and maintain resources in the desktop cloud
system.
s ou

R
Cloud terminal.e
i n g
n
It is used to access the virtual desktop. It can be a PC, a Thin Client, software client or mobile
ar
terminal.
L e
r e
o
M

Questions
Questions
1. What three terms best describe cloud computing?
2. Name four reasons why a company could consider using a cloud

computing solution.
e n
/
m
3. What is compute virtualization?
.c o
e i
aw
u
g .h
ni n
r
lea
: //
Answers:
t t p
s :h
1. Storage virtualization, compute virtualization, parallel processing, dynamic and expandable.
r c e
ou
2. Reasons of considering cloud computing are:
-
s
No need to own and maintain much hardware.
e
-
R
No need to do software patches and updates.
-
g
Total cost of ownership is lower.
i n
n
- Cloud computing solutions can offer disaster recovery and backup.
-
ar
Lower education costs for ICT staff.
L e
e
3. With compute virtualization the resources of a physical server are subdivided to build
r
o smaller virtual servers that borrow parts of the resources of the physical server like CPU
M cycles, RAM memory and network interfaces.

Exam Preparation
Exercises
Multiple response questions
1. Which of the following are the deployment models of cloud computing?

Check all that apply.
e n
a. Private cloud. c. Hybrid cloud.
/
b. Public cloud. d. Desktop cloud.
o m
2. Which of the following models of cloud computing can be described as:
The cloud provider arranges the installation, configuration and updating of
e i .c
all operating systems and applications a user remotely connects to.
aw
a. IaaS. c. SaaS.
u
b. PaaS. d. DaaS.
g .h
ni n
r
lea
: //
Exercises t t p
s :h
c e
3. Statement 1: Huawei data centers are hosted in the public cloud.
r
Statement 2: The Huawei FusionCube solution provides such functions
ou
as computing, storage, and network.
es a. Statement 1 is true; statement 2 is true.
R b. Statement 1 is true; statement 2 is false.
ing
c. Statement 1 is false; statement 2 is true.
d. Statement 1 is false; statement 2 is false.
arn
L e
r e
o
Answers:
1. A, B, C.
2. C.

3. C.
Summary
Summary
The concept of cloud computing.
e n
Separate physical factors and resources for the user.
/
Deployment and business models of cloud computing.
o m
DaaS, SaaS, PaaS, IaaS.
Core technologies of cloud computing.

e i .c
Storage and compute virtualization.
aw
Public, private and hybrid clouds.
u
Huawei cloud computing solutions.
g .h
FusionSphere, FusionAccess, FusionCube.
ni n
r
// lea
p : Slide 25
t t
s :h
r c e
s ou
Re
i n g
r n
e a
e L
or
M

Thank you
www.huawei.com
e n
/
o m
e i .c
aw
u
g
Slide 26
.h
ni n
r
// lea
p :
t t
s :h
r c e
s ou
Re
i n g
r n
e a
e L
or
M

e n
/
o m
e i .c
aw
u
g .h
ni n
r
// lea
p :
t t
s :h
r c e
s ou
Re
i n g
r n
e a
e L
or
M

e n
/
o m
OHC1109109
e i .c
Huawei Storage Product Information
aw
u
and Licenses
g .h
ni n
r
lea
://
www.huawei.com
t tp
s:h
r c e
sou
Re
i n g
r n
e a
e L
or
M
e n
/
o m
e i .c
aw
u
g .h
ni n
r
// lea
p :
t t
s:h
r c e
sou
Re
i n g
r n
e a
e L
or
M
Introduction
In this module we will look at the specific products Huawei has in its portfolio for building any type
of ICT infrastructure. The focus of course will be on the various storage products Huawei offers.
The module however will start with the explanation of the RAID 2.0+ technology. RAID 2.0+ is the
basis for all enterprise class storage devices Huawei offers.
e n
/
Objectives
o m
e i .c

w
Describe the concepts behind Huaweis advanced RAID virtualization technology.
a
Understand how Hot Spare Space is used during data reconstruction.
u

g .h
List the convergence benefits of the new V3 generation storage devices of the OceanStor
series.
ni n

r
Identify the most important storage related products Huawei offers.
// lea
p :
Contents
t t
s :h

RAID 2.0+ concepts.
Hot Spare Space.
r c e

ou
OceanStor V3 products.
s

e
OceanStor Legacy products.
R
g
OceanStor Licenses.
n i n
ar
L e
r e
o
M
HCNA-storage V3 | OHC1109109 Huawei Storage Product Information & Licenses Page | 317
e n
/
o m
e i .c
aw
u
g .h
ni n
r
// lea
p :
t t
s :h
r c e
s ou
Re
i n g
r n
e a
e L
or
M
Page | 318 HCNA-storage V3 | OHC1109109 Huawei Storage Product information & Licenses
RAID 2.0+ Evolution
In module 5 the concepts of RAID were explained. That was the traditional way of working with
RAID that is still applied in some storage solutions and definitely in many server solutions. Huawei
Enterprise Class Storage Solutions use an advanced version of RAID. It is still the intention of
RAID to prevent data loss in case of a hardware failure. The RAID 2.0+ technology is based on
so-called storage virtualization. This type of virtualization implies that the data is split up in smaller
segments and those segments are stored on physical disks. The goal of RAID2.0+ is now to
e n
/
make sure that we do not lose a single segment of data!
o m
RAID 2.0+ Evolution
e i .c
aw
u
g .h
ni n
r
// lea
p :
t t
:h
Hot
spare
e s
c
Traditional RAID LUN virtualization RAID 2.0+
r
s ou
Re
i n g
n
The initial RAID technology combines several cheap and small-capacity physical disks into a
ar
large logical disk for a server to use. As the capacities of disks become increasingly large, RAID
L e
is not merely used to construct a large-capacity disk but to obtain higher data reliability and
r esecurity and improve storage performance.
o
M The number of disks combined into a RAID group can be divided into LUNs that are mapped to
servers for data read/write. The capacity of modern disks has gone up to be several terabytes.
With traditional RAID the rebuild of a failed disk takes a long time and if another disk fails during
the reconstruction, data could be lost. To resolve the problem, block virtualization is developed. A
traditional RAID group uses a single disk as a member disk. Block virtualization further divides
disk space into small blocks and uses the blocks as members to form RAID groups. This
technology is known as Huaweis RAID 2.0+.
HCNA-storage V3 | OHC1109109 Huawei Storage Product information & Licenses Page | 319
Principle of RAID 2.0+
With traditional RAID the first step was to create a RAID group. There are restrictions and
requirements to RAID groups: They should be of disks with the same size and rotational speed.
Secondly the advice is to have no more than twelve disks in a RAID group.
Disk Domain
e n
/
A Disk Domain has a maximum of three tiers.
o m
Physical Disks Disk domain #1
e i .c
Tier
aw
u
.h
High Performance
i n g Performance
Disk domain #2
r n
lea
Capacity
: //
t t p
:h
e s
r c
ou
Huawei storage devices that are based on RAID 2.0+ use another approach. The first step is to
s
create a Disk Domain. A Disk Domain is a group of physical disks that will work together. Disk
e
R
Domains look to be the same as RAID groups but there is a big difference. With Disk Domains the
i n g
number of disks per Disk Domain is much higher than with traditional RAID groups. Also: in a Disk
n
Domain a maximum of three different drive types (SATA; SAS; SSD) can be combined. The term
ar
TIER is used to indicate the disk drive type within a Disk Domain.
L e
r e Tier Disk Drive Type
o
M High Performance
Performance
Solid State Disks (SSD)
SAS disks (10,000 and 15,000 RPM)
Capacity NL-SAS disks (7,200 RPM)
The capacity of a Disk Domain is divided into space for Storage Pools and so-called Hot Spare
Space. The amount of hot spare space is determined automatically and it is related to the number
of disks in the Disk Domain.
Hot Space Space Policy
Minimum reserved capacity is equal to the size of one disk.

e n
/
m
Number of disks in Hot Spare Space Hot Spare Space
o
disk domain in HIGH policy in LOW policy
i .c
1 - 12 1 1
13 - 24
25 - 48
2
3
1
2
we
49 - 72 4 2
u a
.h
73 - 120 5 3
121 - 168 6
i n g 3
n
169 - 264 7 4
r
lea
265 - 360 8 4
: //
p
t t
s :h
In each Huawei storage device using RAID 2.0+ there is at least hot spare space to survive a
c e
single disk failure. This hot spare space can grow to a capacity equal to eight disks. This however
r
ou
does not automatically mean that up to eight disks can fail simultaneously without data loss. It just
s
means that there is room to rebuild eight disks that have failed with the following limitation: the
e
R
disks have not failed at the same time and between two disk failures there was enough time to
i n g
reconstruct all user data!
r n
a
So the raw capacity of an Disk Domain is equal to (#disks - hot spare space) * disk capacity
e
e L
r
The net capacity is depending on the selected RAID level. It requires us to look more closely at
o the concepts of the RAID 2.0+ technology.
M In the next slides we will see how user data will be divided into smaller parts and we will see how
these parts are stored on physical disks in a very clever way that allows us to:
Access the data (READ and WRITE) very quickly.
Reconstruct the data on a failed disk much quicker than with traditional RAID.
Have a more flexible and more enhanced data protection method that could sustain
multiple consecutive disk drive failures.
In the next slides new terms will be introduced:
Disk Group : Disks within a Disk Domain of the same type.
Chunk: A 64 MB section of space allocated on a disk.
Chunk Group: A number of Chunks, taken from multiple disks, and protected using RAID. All the
Chunks of a Chunk Group come from the same Disk Group.
Extent: A section of a Chunk Group. The smallest unit with which requested space,
e n
/
released space and relocated data is calculated. Extents are the building blocks
m
for Thick LUNs. Default size of an extent is 4 MB but they can be configurable
between 512 kB and 64 MB.
.c o
Grain: A subdivision of an extent used when creating Thin LUNs. A Grain is 64 kB in
e i
size.
aw
u
g .h
ni n
r
lea
Disk domain
Chunk (CK) Chunk Group (CKG)
: //
t t p
Disk Group SAS
s :h
e
RAID is set for CKG
r c Thick LUN 1
ou
Extent
Extent
Extent
s
Extent
Disk Group
Extent
e
NL-SAS
Extent
R
Thick LUN 2
Extent
Extent
g
Extent
Extent Extent
i n
Extent
r n
e L
or
Inside a Huawei storage device that holds different drive types (SSD, SAS and/or L-SAS) there
Mare multiple tiers and therefore multiple Disk Groups. A number of chunks taken from multiple
disks in the Disk Group are combined into a Chunk Group. Extents are subdivisions of a Chunk
Group and they are used to build thick LUNs. Extents are 4 MB by default.
From the user perspective the Disk Groups, Chunks and Chunk Groups are invisible and not
configurable entities. The Huawei RAID 2.0+ firmware handles all of these internally. Users can
configure the size of the Extent (512 kB through 64 MB).
Thick LUNs are built using Extents. This means that any LUN occupies a multiple of 4 MB of
storage capacity. Extents are assigned to a LUN at the time the LUN gets created. Although there
is no actual user data written to the LUN by any external application the storage is already pre-
allocated and could be considered to be used already.
e n
Disk domain
/
Chunk (CK) Chunk Group (CKG)
o m
i .c
Disk Group SAS
we
u a
RAID is set for CKG
g .h
Thin LUN 1
n
Extent Grain
i
Disk Group
Extent Grain Grain

NL-SAS
n
Extent Grain
r
Extent Grain Grain
a
Extent Grain Grain
le
Extent
//
Extent
p :
t t
s :h
c e
Within the Huawei storage devices there is an option to create so-called Thin LUNs. A thin LUN
r
ou
only allocates physical storage when actual user data is written to a LUN. That is why, in the case
s
of a Thin LUN, the extents are divided into smaller 64 kB Grains. Grains will be associated with
e
R
written user data and not entire Extents. This means that the storage consumption of a Thin LUN
i n g
is allocated with 64 kB increments when very small files are written to the Thin LUN.
r n
a
The RAID 2.0+ technology within the Huawei storage devices can handle multiple Disk Domains,
e
e L
up to 360 disks per Disk Domain, multiple tiers within a Disk Domain, Extents and/or Grains to
r
build LUNs and at the same time handle hot spare space!
o
M
e n
/
o m
e i .c
aw
u
g .h
ni n
r
lea
: //
t p
There is another object shown in the above image. A storage pool is a subdivision of a Disk
t
:h
Domain. Storage Pools are created within the user interface with two parameters: capacity and
s
RAID type. Within each Storage Pool three tiers may exist (if the Disk Domain has three different
e
c
disk types) and from each tier space can be allocated. Also for each tier inside the Storage Pool
r
ou
the administrator can select the required RAID protection level.
es
R
What RAID 2.0+ in fact does is to make sure that RAID like techniques are used on the level of
i n g
Chunks. So RAID 10 will now make a copy of a Chunk on another disk inside the same Disk
n
Group. That means that the term RAID actually is not very correct anymore. Maybe a better name
ar
would be RAIC or Redundant Array of Independent Chunks.
L e
r e
As it operates on chunk level and not on disk level there are other differences with traditional
o
RAID. For instance in RAID 5 there was the concept of N+1. For N data disks we needed the
Mcapacity of one extra drive to calculate and store the parity information.
In RAID 2.0+ there are options like 2D+1P; 4D+1P and 8D+1P. This implies that 2 (or 4 or 8) data
chunks with user data in them are used to calculate the parity. This now means a variable
overhead. With 2D+1P the overhead is 33%, with 4D+1P it is 20% and with 8D+1P the overhead
is 11%.
These variable overheads look like they are less efficient than with traditional N+1 RAID 5.
However in a twelve disk RAID 5 group we can only lose a single drive. When a second drive fails
this leads to data loss. Using 4D+1P with RAID 5 in RAID 2.0+ it means that the chunks of a
RAID 5 family (4D + 1P) are located on five out of the twelve physical disks. Now inside of that
twelve Disk Domain two drives can fail as long as they do not carry two out of the five chunks of a
specific RAID 5 family!
Automatic load balancing, reducing the system failure rate

e n
/
o m
e i .c
aw
u
g .h
n
Traditional RAID RAID 2.0+
ni
r
// lea
p :
t t
s :h
e
r c
s ou
The intelligence of the Huawei RAID 2.0+ technology will make sure that all chunks of all RAID
Re
groups are distributed across all the disks of the Disk Domain. This means that the workload of
i n g
storing and reading data is divided across all the disks. On top of adding to the performance of
n
the system RAID 2.0+ also adds to the fault protection rate.
ar
L e
r e
o
M
High System Reliability
High System Reliability
Traditional RAID
e n
/
m
RAID 2.0+
.c o
Traditional RAID RAID 2.0+
e i
w
Global or local hot spare disks must be Distributed hot spare space does not need to be
a
manually configured. separately configured.
u
Multi-to-one reconstruction is used. Multi-to-multi reconstruction is used.
.h
Reconstruction data blocks are written onto a Reconstruction data blocks are written onto
single hot spare disk in serial. multiple disks in parallel.
Reconstruction is prolonged due to hotspots.
n g
Reconstruction is shortened owning to load
balancing.
i
r n
lea
: //
t p
Maybe the greatest advantage of RAID 2.0+ is the rebuilding capability of the system. In
t
:h
traditional RAID the data of the failed disk could be reconstructed but it took a lot of time. Reason
s
is that all remaining disks had to be read to find all the data in the stripe. With the parity
e
c
information there was then the option to reconstruct the data. That reconstructed data now had to
r
ou
be written onto the one spare disk.
es
R
With RAID 2.0+ the data can be constructed by reading less disks (maximum with RAID 5 8D+1P
i n g
is eight disks). The second advantage is that RAID 2.0+ does not have hot spare disks but hot
n
spare space. This space is located across all the disks in the Disk Domain. So the reconstructed
ar
data can be stored on multiple drives. Therefore with reconstructing data there is no bottleneck in
L e
a single spare disk like with traditional RAID.
r e
o
Reconstructing a failed disk can be up to twenty times faster using RAID 2.0+ technology.
Fast Reconstruction
Fast Thin Reconstruction to Reduce Dual-Disk Failure Probability
e n
/
o m
e i .c
aw
u
g .h
ni n
r
lea
: //
t p
In the schematic diagram of traditional RAID, HDDs 0 to 4 compose a RAID 5 group, and HDD 5
t
:h
serves as a hot spare disk. If HDD 1 fails, an algorithm is used to reconstruct data based on
s
HDDs 0, 2, 3, and 4, and the reconstructed data is written onto HDD 5.
e
r c
ou
In the schematic diagram of RAID2.0+, if HDD 1 fails, its data is reconstructed based on a CK
s
granularity, where only the allocated CKs (CK12 and CK13 in the figure) are reconstructed. All
e
R
disks in the storage pool participate in the reconstruction. The reconstructed data is distributed on
i n g
multiple disks (HDDs 4 and 9 in the figure).
r n
a
RAID2.0+ fined-grained and efficient fault handling also contributes to reconstruction acceleration.
e
e L
If a traditional RAID group is reconstructed the entire disk will be reconstructed including empty
or sections. By efficiently identifying used space, RAID2.0+ implements thin reconstruction upon a
disk failure to further shorten the reconstruction time, mitigating data loss risks.
Dynamic Space Distribution
Dynamic Space Distribution to Flexibly Adapt to Service Changes
e n
/
o m
.c
SmartTier SmartThin SmartMotion SmartVirtualization
e i
aw
SmartVirtualization
u
g .h
ni n
r
lea
: //
t p
RAID2.0+ is implemented based on industry-leading block virtualization. Data and service load in
t
:h
a volume are automatically and evenly distributed onto all physical disks in a storage pool. RAID
s
2.0+ offers optimal data protection; optimal performances and extreme efficient reconstruction
e
performances.
r c
s ou
On top of that there are even more advantages to RAID 2.0+s block (or better Chunk)
virtualization.
Re
i n g
n
Huawei has created a number of enterprise level features that can be purchased in combination
r
a
with its storage devices. Examples are SmartTier and SmartVirtualization.
e
e L
or
In the next section of this module we will have an overview of the latest generation of Huawei
storage devices and their specifications. We will also list a number of features that are sold
Mseparate from the hardware.
Huawei Storage Products
In the previous modules we have explained the fundamentals of storage in a general way. We
saw concepts like DAS, NAS and SAN and we discussed RAID, iSCSI, Fibre Channel etcetera
from a neutral standpoint. This section will now discuss the latest generation of Huawei storage
products. The storage models are usually called OceanStor.
In 2015 the next generation of OceanStor is released: Generation V3.
e n
/
o m
.c
e i
w
Enterprise Unified Storage Solutions:
OceanStor 18000 series.
u a
.h
OceanStor 6800 V3 series.
OceanStor 5300/5500/5600/5800 V3 series.
i n g
n
OceanStor Dorado 2100 G2/5100.
r
lea
OceanStor S2200T series.
//
OceanStor S2600T/S5500T/S5600T/S5800T/S6800T.
OceanStor VIS6600T.
p :
Enterprise Storage Networking Solutions:
t t
OceanStor SNS2124/2224/2248.
s :h
r c e
OceanStor SNS3096/5192/5384.
s ou
Re
n g
As you can see in the above image not all OceanStor models are available as a release 3 version
i
n
yet, but in the upcoming months more and more models will become available in V3.
r
e a
e L
The image above also lists some legacy models for storage (the SxxxxT series). They will not be
or discussed in this section but legacy models are not End-Of-Life and will still be supported by
Huawei.
Massive Storage Solutions:

OceanStor 9000 Big Data.
OceanStor UDS Massive Storage.
OceanStor N8500 Clustered NAS system.
Data Protection Solutions:

e n
OceanStor VTL6900. /
OceanStor HDP3500E Backup Appliance.
o m
Storage Software:
e i .c
OceanStor ReplicationDirector.
aw
u
g .h
ni n
r
lea
With its portfolio of storage devices and storage related devices there is almost always a solution
//
Huawei can offer for the customers ICT infrastructure.
p :
t t
:h
Positioning Huawei Storage
e s
r c
s ou
Re
i n g
r n
e a
e L
or
M
The range of products starts with storage devices for Small and Medium Business companies
(SMBs) with a few servers and switches all the way up to a complete turnkey datacenter. With
the last Huawei can provide for all required equipment and facilities needed to build and configure
a complete working datacenter.
Enterprise Converged Storage
OceanStor V3 Enterprise Converged Storage
OceanStor V3 Key Features
e n
/
SSD & HDD
Convergence
o m
.c
High-End, Mid-Range, Primary & Backup Storage
i
Entry-Level Convergence Convergence
we
a
SAN & NAS Heterogeneous Storage
u
Convergence Unified & easy management Convergence
State of art hardware

g .h
ni n
r
lea
: //
SAN / NAS Convergence
t t p
:h
All V3 models of the OceanStor series are now built as Unified Storage devices. To explain what
s
unified storage is let us look at the definition of unified storage:
e
c
A single, integrated storage infrastructure that functions as unification engines to simultaneously
r
ou
support Fibre Channel, IP Storage Area Networks (SAN) and Network Attached Storage (NAS)
s
data formats. That means that all V3 OceanStor devices are shipped with the intelligence to
e
R
handle block based and file based storage. Block based will be assigned to hosts in the traditional
i n g
storage way. For file based data there is the option to access the files via the CIFS and/or the
n
NFS protocol.
ar
L e
High-End, Mid-range and Entry-Level Convergence
r eAll OceanStor V3 storage devices are now based on the same architecture which allows for easy
o upgrades and conversions. Also for DR solutions it is no longer required to have (near) identical
M hardware in the remote datacenter.
SSD and HDD Convergence

In Huawei V3 there will be a convergence of data on SSD and HDD. Traditionally data will be on
one of the two platforms. With RAID 2.0+ and V3 data will be at the optimal location which could
mean it is partly on SSD and partly on HDD.
Primary and Backup Convergence
Built in the Huawei OceanStor is snapshot technology as well as replication technology. That can
be used (for both file based data as well as block based storage) to implement a backup strategy.
Heterogeneous Convergence
Huawei is involved in the process to migrate data from storage devices (i.e. EMC, IBM) to Huawei
OceanStor V3 storage devices. Support for other vendors and more models is planned for the
coming period.
e n
/
OceanStor V3 Software Architecture
o m
Across almost all models of the OceanStor in the new V3 platform the functionalities are
applicable. The next image shows the software architecture for the OceanStor V3 models.
e i .c
aw
u
OceanStor V3 Software Architecture
g .h
Management function control software
ni n
r
OceanStor DeviceManager Syslog Syslog Syslog
lea
Basic function control Value-added function control software
://
software
Snapshot Remote replication LUN Copy
tp
Cache SPool
Clone Consistency Group SmartQoS
t
:h
SCSI SRAID SmartMotion SmartPartition SmartThin
s
SmartTier SmartMigration SmartVirtualization
e
File Quota
c
Protocol Manage SmartErase SmartMulti-Tennant HyperMirror
r
ment
ou
SmartDedupe&SmartCompression SmartCache
Volume Management
s
Module of File System WORM
Re Operating system layer of a storage system
i n g
r n
e a
L
Most of these licenses are applicable to all V3 models, just a few exceptions exist.
e
or
M
OceanStor Unified Storage Platform
OceanStor Unified Storage Platform
Controller Platform Disk Enclosure

Model
(SAN + NAS) Platform
5300 V3
2U Platform 2U 25*2.5 disk enclosure
e n
5500 V3
/
o m
.c
5600 V3
5800 V3
3U Platform
e i
4U 24*3.5 disk enclosure
aw
u
.h
6800 V3 6U Platform
4U 75*3.5 high-density
i n gdisk enclosure
r n
lea
: //
t p
The first two models (5300 / 5500) are based in a 2U chassis and in that chassis we find the
t
:h
controllers as well as a number of physical disks. In both models 5300 and 5500 additional
s
storage capacity can be added using SAS cables connected to one or more disk enclosures. The
e
c
models 5600 V3, 5800 V3 and 6800 V3 are in a 3U or 6U chassis with just controllers. All disk
r
ou
capacity will be created with SAS attached disk enclosures.
es
R
Currently three disk enclosure models are available:

i n g
A 2U disk enclosure that can hold up to 25 disks with a size of 2.5.

r n
A 4U disk enclosure that can hold up to 24 disks with a size of 3.5.

e a
A 4U high-density disk enclosure that can hold up to 75 disks of 3.5.
e L
or Note:
M In IT the unit U is used to indicate the dimension of components. Most devices are constructed to
be 19 inch wide. The height of servers is expressed in U units. Servers are usually 1, 2 of 3 U in
size. Storage devices are often 2, 3 or 4 U high. The racks that servers, storage devices etc are
mounted in are typically 42U in height.
( 1 U equals 1.75 inch or 4.45 cm).
OceanStor 5300 V3
5300 V3/5500 V3 Controller Platform (1)
e n
/
o m
System architecture
e i .c
The latest PANGEA hardware platform.
aw
Disk and controller integration (2 U controller enclosure: disk and controller
u
.h
integration).
Active-active dual controllers.
i n g
r n
lea
: //
t t p
:h
5300 V3/5500 V3 Controller Platform (2)
e s
Highlights
r c
ou
High performance: PCIe 3.0 high-speed bus and SAS 3.0 high-speed I/O channel.
es
Outstanding reliability: Full redundancy design.
R
Built-in BBU + data coffer.
A wide range of data protection technologies.
n g
Flexible scalability: Hot-swappable I/O interface modules.
i Four hot-swappable interface modules and two onboard.
r n interface modules (2 U controller enclosures).
e a Energy saving:
L
Intelligent CPU frequency control.
Delicate fan speed control.
r e
o
M
OceanStor 5300 V3 specifications
OceanStor 5300 V3 Specifications
Model 5300 V3
System Cache (expanded with the number of controllers) 32 GB to 256 GB
Maximum Number of Controllers 8
Supported Storage Protocols Fibre Channel, FCoE, iSCSI, InfiniBand, NFS, CIFS, HTTP, and FTP
e n
/
1 Gbit/s Ethernet, 10 Gbit/s FCoE, 10 Gbit/s TOE, 16 Gbit/s FC, and
Port Types
56 Gbit/s InfiniBand, SAS 3.0 (back-end, 4 x 12 Gbit/s per port)
m
Maximum Number of Disks Supported by Two Controllers 500
o
Maximum Number of Front-end Ports per Controller 12
.c
Maximum Number of I/O Modules per Controller 2
Maximum Number of Snapshots (LUN)
Maximum Number of LUNs
256
2048
e i
w
Maximum Number of Snapshots per file system 2048
Maximum Capacity of a single file
Disk Types
256 TB
SSD, SAS, and NL-SAS
u a
.h
RAID Levels RAID 0, 1, 3, 5, 6, 10, or 50
g
Key Software Features UltraPath, Cloud Service, ReplicationDirector, DeviceManager, eSight
i n
2 U controller enclosure: 86.1 mm x 447 mm x 750 mm
Dimensions
(3.39 in. x 17.60 in. x 29.53 in.)
r n
lea
: //
t t p
OceanStor 5300 V3 / 5500 V3 Controller Platform
s :h
r c e
s ou
Re
i n g
r n
e a
eL
Power-BBU-Fan modules SAS expansion ports
1+1. Two SAS expansion
Up to 94% of power ports per controller.
or
conversion efficiency. Interface modules
48 V DC and 240 V DC. Onboard ports Two slots for hot-swappable
5300 V3: four GE ports per interface modules.
M
controller. Port types: 8 or 16 Gbit/s Fibre
5500 V3: four 8 Gbit/s Fibre Channel, GE, 10GE TOE, 10GE
Channel ports per controller. FCoE, and 12 Gbit/s SAS.
Various controller models exist but they all have more or less the same layout. Shown is the
detailed view of a 5300 controller with the modules and indicators.
OceanStor 5300 V3 Detailed Rear View
e n
/
o m
e i .c
A B C D E F G H
aw
u
.h
A = On board 1 Gb/s Ethernet port. E = I/O modules (FC depicted).
B = Mini SAS HD expansion ports.
C = Alarm and Power status LEDs.
i n g
F = Management network port.
G = Maintenance network port.
D = USB port.
r
H = Serial port.
n
// leaSlide 23
p :
t t
:h
The first 4 disks in S5300/5500 V3 are called as Data Coffer. They are very important part of the
system.
e s
r c
ou
Inside each OceanStor model four disks are assigned to be coffer disks. It means next to user
s
data, the coffer disks hold safety copies of the controllers configuration. In case of a controller
e
R
replacement the information on the coffer disks will help to quickly restore the controller to
working condition.
i n g
r n
e a
e L
or
M
Icons and Status Indicators
Icons and Status Indicators
Power indicator for controller and disk enclosure (Front).
Alarm indicator for controller module and disk enclosure.
Depicts management interface port.

e n
/
m
Fan indicator for controller module and disk enclosure.
Depicts maintenance interface port.
.c o
Power indicator for disk enclosure (Back).
e i
BBUindicator for disk enclosure (Back).
aw
Location indicator for disk enclosure.
u
Enclosure ID display.
g .h
ni n
r
lea
: //
t p
BBU stands for Battery Backup Unit. This is a special module in controllers and disk enclosures
t
:h
that provides backup power to the RAM modules of the cache in the system.
e s
r c
Data that is written to a LUN will initially be stored\buffered in RAM memory of the cache module.
ou
This improves the response of the storage device when a host writes data to a LUN. The host
s
receives an acknowledgement of the write very quick as writing to RAM is much faster than
e
R
writing to a physical sector on a hard disk. However: if power fails for the enclosure the content of
i n g
the RAM will be lost. The host assumes it is stored (after the acknowledgement) but the data is
n
lost anyway. That is why the cache is protected with an additional battery pack that is inside the
ar
enclosure. The cached data will then be copied to a dedicated SSD disk, which is fitted inside the
L e
controller. The indicator shows what the status is of the BBU. These are the optional colors of the
r eindicator:
o
M
BBU LED Status
Steady Green BBU is fully operational
Blinking Green 1 Hz BBU battery is charging
Blinking Green 4 Hz BBU battery is being discharged
Red BBU is faulty
Model 5500 V3
System Cache (expanded with number of controllers) 48 GB to 512 GB
n
e
/
Port Types
Max. Number of Disks Supported by Two Controllers 750
Maximum Number of Front-end Ports per Controller 12
o m
.c
Max. Number of I/O Modules per Controller 2
i
Max. Number of Snapshots (LUN) 1024
e
Max. Number of LUNs 4096
Max. Number of Snapshots per file system 2048
Max. Capacity of a single file 256 TB
aw
u
Disk Types SSD, SAS, and NL-SAS
.h
g
Dimensions
n
(3.39 in. x 17.60 in. x 29.53 in.)
ni
r
lea
: //
t t p
s :h
r c e
s ou
Re
i n g
r n
e a
e L
or
M
OceanStor 5600 V3
OceanStor 5600 V3 / 5800 V3 Controller Platform (1)
BBU modules:
5600 V3: 1+1; 5800 V3: 2+1.
n
AC power failure protection.
Controller modules:
/ e
Dual controllers.
o m
.c
Automatic frequency adjustment for

reduced power consumption.
e i
Built-in fan modules (fan modules are
be maintained independently).
aw
integrated in controller modules, but can
u
g .h
ni n
r
lea
: //
t t p
:h
OceanStor 5600 V3 / 5800 V3 Controller Platform (2)
e s
r c
ou
Management modules:
1+1.
s
Hot-swappable.
e
Multi-controller scale-out and
R interconnection for establishing
g
heartbeats.
n i n Power modules:
ar 1+1.
Up to 94% of power conversion efficiency.
L e 240 V DC.
r e Interface modules:
o 16 slots for hot-swappable interface modules.
M
Port types: 8 or 16 Gbit/s Fibre Channel, GE, 10GE TOE, 10GE FCoE, and 12 Gbit/s SAS.
Model 5600 V3
Supported Storage Protocols
Fibre Channel, FCoE, iSCSI, InfiniBand, NFS, CIFS, HTTP, and FTP
n
1 Gbit/s Ethernet, 10 Gbit/s FCoE, 10 Gbit/s TOE, 16 Gbit/s FC, and 56
e
Port Types
Gbit/s InfiniBand, SAS 3.0 (back-end, 4 x 12 Gbit/s per port)
/
m
Max. Number of Front-end Ports per Controller 28
o
.c
Max. Number of LUNs
Max. Number of Snapshots per file system
4096
2048
e i
w
Max. Capacity of a single file 256 TB
Disk Types
RAID Levels
SSD, SAS and NL-SAS
RAID 0, 1, 3, 5, 6, 10, or 50
u a
.h
g
Dimensions
n
(5.14 in. x 17.60 in. x 29.53 in.)
ni
r
lea
: //
t t p
:h
OceanStor 5600 V3 / 5800 V3 Header Platform
e s
r c
s ou
Re
i n g
r n
e a 1. System enclosure
eL
2. BBU module
3. Controller
or
4. Power module
5. Management module
M
6. Interface module
Model 5800 V3
Supported Storage Protocols
n
Fibre Channel, FCoE, iSCSI, InfiniBand, NFS, CIFS, HTTP, and FTP
e
Port Types
/
m
.c o
i
e
Max. Number of Snapshots per file system 2048
Max. Capacity of a single file
Disk Types
256 TB
aw
u
.h
g
Dimensions
n
(5.14 in. x 17.60 in. x 29.53 in.)
ni
r
lea
Slide 30
: //
All OceanStor models 5300, 5500, 5600 and 5800 support up to eight controllers. The models
t t p
each have two controllers running in the so-called active-active mode. This means that both
:h
controllers within the chassis are active data movers. The expansion of the amount of controllers
e s
implies that more processing power as well as more cache memory is available.
r c
ou
The expansion itself can physically be done in two different ways. Both methods require additional
es
hardware to be installed. This additional hardware is the Smart I/O card and they should be
R
inserted in the controllers in specific slots.
i n g
r n
Direct Connection Mode.
e a
This expansion option is only possible when upgrading to 4 controllers (equals 2 chassis). In this
e L
mode there are fiber optic cables that run from one controller in chassis #1 directly to another
or controller in chassis #2.
M Switch Connection Mode.

In this mode the expansion can be from 2 4 controllers or from 2 8 controllers. The method
uses fiber optic cables from the Smart I/O cards in the controllers to two separate fabric switches.
OceanStor 6800 V3
OceanStor 6800 V3 Controller Platform (1)
BBU modules:
3+1.
n
AC power failure protection.
/ e
m
Controller modules:
o
2 or 4 controller configuration.
Automatic frequency adjustment for reduced

power consumption.
e i .c
w
Built-in fan modules (fan modules are
a
integrated in controller modules, but can be
u
maintained independently).
g .h
ni n
r
lea
: //
t t p
:h
OceanStor 6800 V3 Controller Platform (2)
e s
r c
ou
Power modules:
1+1.
es 240 V DC.
Up to 94% of power conversion efficiency.
R
ing
Management modules:
1+1.
rn
Hot-swappable.
Multi-controller scale-out and
e a interconnection for establishing heartbeats.
eL
Interface modules:
or
2-controller: 12 / 4-controller: 24.
Hot-swappable.
M
Port types: 8 or 16 Gbit/s Fibre Channel, GE, 10GE TOE, 10GE FCoE, and 12 Gbit/s SAS.
Model 6800 V3
n
e
1 Gbit/s Ethernet, 10 Gbit/s FCoE, 10 Gbit/s TOE, 16 Gbit/s FC, and 56
Port Types
/
Gbit/s InfiniBand, SAS 3.0 (back-end, 4 x 12 Gbit/s per port)
m
o
.c
Max. Number of LUNs
Max. Number of Snapshots per file system
65536
2048
e i
Max. Capacity of a single file
Disk Types
256 TB
aw
u
.h
g
Heterogeneous virtualization
Block Virtualization
i n
Virtualization Features Supports virtual machines: Vmware, Citrix, Hyper-V
Value-added features related to virtual environments: VAAI and
n
integration of vSphere and vCenter
r
lea
: //
t p
As mentioned before the 5300 and 5500 models are based on a chassis with both controllers as
t
:h
well as disk drives. The models 5600, 5800 and 6800 get their storage capacity always using
external disk enclosures.
e s
r c
ou
All disk enclosures are connected via mini SAS HD connectors and use SAS as an underlying
s
technology. The SAS used today by Huawei V3 is 12 Gb/s.
e
R
n g
Disk enclosures are available for all common drive types, formats and sizes.
i
r n
a
Supported are:
e
e L
or Disk Drive Type Physical Size 2,5 Physical Size 3,5
M Solid State Disks
SAS disks 10,000 rpm
SAS disks 15,000 rpm
NL-SAS disks 7,200 rpm
OceanStor 6800 V3 Header Platform
6
6
e n
/
1. System enclosure
o m
.c
2. BBU module
i
3. Controller
4. Power module
5. Management module
we
6. Interface module
u a
g
Slide 34 .h
ni n
r
// lea
p :
t t
s :h
r c e
s ou
Re
i n g
r n
e a
e L
or
M
OceanStor Disk Enclosure Platform
OceanStor Disk Enclosure Platform
2 U disk enclosure: 25 x 2.5-inch disks.
Disk module.
n
Expansion module.
Power module.
/ e
4 U disk enclosure: 24 x 3.5-inch disks.
o m
.c
Disk module.
e i
Fan module.
aw
u
.h
Expansion module.
Power module.
i n g
r n
lea
: //
t t p
:h
OceanStor High-density Disk Enclosure
e s
r c
4 U high-density disk enclosure: 75 x 3.5-inch disks.
s ou
Re
i n g
r n
e a
e L
or 1. System enclosure.
2. Power module. 4. Expansion module.
M
3. Fan Module. 5. Diskmodule.
The High-density disk enclosure is only available with 3.5 inch disk drives. They usually are filled
with NL-SAS drives with capacity starting from 1 TB. That makes a high-density enclosure hold at
least 75 TB of raw disk capacity. With the size of the disk capacity increasing constantly the
capacities offered by the high-density enclosures will be enormous in the future.
OceanStor 18000
OceanStor 18000 series
e n
/
o m
e i .c
aw
u
g .h
ni n
r
lea
: //
t p
The OceanStor 18000 series is the top of the range model. It is primarily designed for customers
t
:h
who have a very high demand for performance.
e s
r c
The amount of disks inside an OceanStor 18000 series model can be up to 3216 for the
ou
OceanStor 18800. The enormous performance capabilities lie in the fact that the 18000 series
s
have a very big amount of cache memory (up to 3 TB of RAM). Second factor for this high
e
R
performance is the number of controllers. There can be up to sixteen controllers working together!
n g
Benchmark tests have proved that the OceanStor 18000 series can reach more than 1 million
i
IOPS.
r n
e a
e L
or
M
OceanStor 18500 Specifications
Model 18500
Max. Cache Size 768 GB
Max. Number of Front-end Host Ports 128 (FC/iSCSI/FCoE)
n
Max. Number of Disks 1584
/ e
2.5-inch disks: SSD and SAS
Supported Disk Types
3.5-inch disks: SSD, SAS, and NL-SAS
m
RAID Levels RAID 5,6, and 10
o
Max. Number of hosts 65536
.c
i
Snapshot (HyperSnap), clone (HyperClone), copy (HyperCopy), and remote
Data Protection Software
e
replication (HyperReplication)
Thin provisioning (SmartThin), data relocation (SmartMotion), storage tiering
w
Data Efficiency Software (SmartTier), service quality control (SmartQoS), and heterogeneous
virtualization (SmartVirtualization), and cache partitioning (Smart Partition)
Host Software Suite
(UltraPath)
u a
Disaster recovery software (ReplicationDirector) and host multipathing
.h
Compatible Operating Systems AIX, HP-UX, Solaris, Linux, Windows, etc
Virtualization platforms: VMware, XenServer, and Hyper-V
g
Supported Virtual Environment Features Value-added virtualization features: VMware VAAI, VASA,SRM,and Hyper-V
n
Integration: vSphere and vCenter
ni
r
lea
Slide 38
: //
t t p
s :h
r c e
s ou
Re
i n g
r n
e a
e L
or
M
Model 18500
n
/ e
2.5-inch disks: SSD and SAS
Supported Disk Types
3.5-inch disks: SSD, SAS, and NL-SAS
m
o
.c
i
e
Thin provisioning (SmartThin), data relocation (SmartMotion), storage tiering
w
Data Efficiency Software (SmartTier), service quality control (SmartQoS), and heterogeneous
virtualization (SmartVirtualization), and cache partitioning (Smart Partition)
Host Software Suite
Disaster recovery software (ReplicationDirector) and host multipathing
(UltraPath)
u a
.h
g
n
ni
r
lea
Slide 38
: //
t t p
s :h
r c e
s ou
Re
i n g
r n
e a
e L
or
M
OceanStor 18800F Specifications
OceanStor 18800F Specifications
Model 18800F
e n
/
m
Supported Disk Types 2.5-inch disks: SSD
o
.c
i
Data Efficiency Software

we
SmartThin / SmartMotion / SmartQoS / SmartPartition / SmartVirtualization
Host Software Suite
u a
Disaster recovery software (ReplicationDirector) and host multipathing (UltraPath)
.h
g
ni n
r
lea
: //
t p
The OceanStor 18800F is the version where there are some restrictions. The 18800F cannot be
t
:h
used in combination with disk enclosure that hold 3.5disks. This automatically implies that the
s
high-density enclosures are not supported with the OceanStor 18800F. The OceanStor 18800F
e
c
also comes with more cache memory. It is always fitted with 192 GB of cache RAM whereas the
r
ou
OceanStor 18800 can also be fitted with 96 GB.
es
R
i n g
r n
e a
e L
or
M
I/O Modules for the OceanStor V3 series
Depending on the model type there are a number of I/O cards that can be used in combination
with the OceanStor controllers. The cards are typically used to connect the OceanStor controllers
to the front-end side: the switches or hosts in the storage network. Other I/O modules can be
used to connect disk enclosures to the OceanStor controller.
I/O Modules for the OceanStor series

e n
/
Various I/O modules exist to connect hosts, enclosures and
o m
controllers.
e i .c
aw
u
g .h
ni n
r
// lea
p :
t t
:h
es
r c
ou
The cards are often available in different speeds and/or generations. Huawei supports many of
es
these generations. Examples are the Fibre Channel Host Bus Adapters that are supported in 4
R
Gb/s, 8 Gb/s and 16 Gb/s speeds. Also 2 port and 4 port versions exist.
i n g
r n
e a
e L
or
M
In this module a very important I/O card will be discussed: the so-called Smart I/O card.
Smart I/O interface module

1 Power indicator/Hot Swap button
2 16 Gbit/s FC/8 Gbit/s FC/FCoE/iWARP (Scale-Out)
1 4
3 Port indicator (Link/Active/Mode indicator)
4 Module handle
5 Port working mode silkscreen
n
2
3
No. Indicator Status and Description
Green on: The module is working properly.
/ e
5
m
Blinking green: The module needs to be hot-swapped.
1 Power indicator
o
Red on: The module is faulty.
Off: The module is not powered on.
i .c
Blinking blue slowly: The module is working in FC mode with
link down.
e
Blinking blue quickly: The module is working in FC mode with
link up and data is being transmitted.
w
Steady blue: The module is working in FC mode with link up but
Port indicator
no data is being transmitted.
a
3 (Link/Active/
Blinking green slowly: The module is working in FCoE/iWARP
Mode indicator)
u
mode with link down.
Blinking green quickly: The module is working in FCoE/iWARP
.h
Note: Smart I/O interface modules mode with link up and data is being transmitted.
Steady green: The module is working in FCoE/iWARP mode
are supported by V3R2 only.
g
with link up but no data is being transmitted.
ni n
r Slide 42
// lea
:
The most important task of the Smart I/O card is to connect multiple OceanStor controller units
p
t t
together. This allows the OceanStor to scale up with groups of two controllers at a time. Two
:h
controllers are added as one OceanStor chassis of course houses two controllers!
e s
c
Up to 8 controllers can be present in an OceanStor V3 solution which means 4 chassis of
r
ou
OceanStor will be linked together. This requires the use of the Smart I/O card.
es
In some of the models the card must be enter in a special slot (shown in previous image) and
R
g
some OceanStor controllers already have a Smart I/O card onboard (next image).
n i n
ar
L e
r e
o
M
Onboard Smart I/O interface module
1 3
2 4 No. Indicator Status and Description
e n
1 16 Gbit/s FC/8 Gbit/s FC/FCoE 1 Port indicator Blinking blue slowly: The module is working in FC
/
m
(Link/Active/Mode mode with link down.
indicator) Blinking blue quickly: The module is working in
o
2 Port indicator (Link/Active/Mode FC mode with link up and data is being
.c
indicator) transmitted.
i
Steady blue: The module is working in FC mode
3 Module handle with link up but no data is being transmitted.
e
Blinking green slowly: The module is working in
FCoE mode with link down.
4 Port working mode silkscreen
w
Blinking green quickly: The module is working in
FCoE mode with link up and data is being
a
Note: Smart I/O interface modules transmitted.
u
Steady green: The module is working in FCoE
are supported by V3R2 only. mode with link up but no data is being transmitted.
g .h
ni n
r
lea
Notice that in the previous two images a comment was added in red text: Smart I/O cards are only
//
supported in V300R200 (or short V3R2) version firmware.
p :
t t
This is important to remember as the V3R2 firmware is the only one that supports the scale out to
:h
8 controllers!
e s
r c
s ou
Re
i n g
r n
e a
e L
or
M
OceanStor Dorado 2100 G2
The Huawei OceanStor Dorado systems are designed as all flash arrays and therefore can only
be equipped with Solid State Disks. This makes the OceanStor Dorado systems very useful in
high performance environments. Solid State Disks offer tremendous performances in IOPS but
the capacity of the disk is limited. On top of that: Solid State Disks are more expensive than
traditional rotating disks.
e n
/
Huawei offers two OceanStor Dorado models: The 2100 and 5100 models.
o m
.c
At this point in time the OceanStor Dorado systems are still generation 2.
e i
aw
OceanStor Dorado 2100 G2
u
g .h
ni n
r
// lea
p :
t t
s :h
r c e
s ou
Re
i n g
r n
e a
e L
or
M
OceanStor Dorado 2100 G2 Specifications
OceanStor Dorado 2100 G2 Specifications
Model Dorado 2100 G2

Number of controllers Dual active-active controllers
Front-end port types 8 Gbit/s FC, 10 Gbit/s iSCSI (TOE), 40 Gbit/s InfiniBand QDR
Back-end port types 6 Gbit/s SAS 2.0 wide port
Max. number of I/O modules 2
e n
/
Max. number of disk enclosures 3
m
Max. bandwidth 10 GB/s
o
Max. IOPS 600.000
.c
Access latency 500 s (microseconds)
i
RAID levels 0, 5, 10
e
Supported max. number of Hosts 512
w
Supported max. number of LUNs 2048
a
Dimensions 2 U controller enclosure: 86.1 mm x 446 mm x 582 mm (3.39 in. x 17.56 in. x 22.91 in.)
u
Key software features HyperThin (thin provisioning)
g .h
ni n
r
lea
Slide 45
: //
t t p
s :h
r c e
s ou
Re
i n g
r n
e a
e L
or
M
OceanStor Dorado 5100
OceanStor Dorado 5100
e n
/
o m
e i .c
aw
u
g .h
ni n
r
lea
Slide 46
: //
t t p
OceanStor Dorado 5100 Specifications
s :h
r c e
o u 5100 Specifications
OceanStor Dorado
es
R
i n g
Model
Number of controllers
Dorado 5100
Dual active-active controllers
rn
Front-end port types 8 Gbit/s FC, 10 Gbit/s iSCSI (TOE)
a
Back-end port types 6 Gbit/s SAS 2.0 wide port
e Max. number of I/O modules 12
eL
Max. number of disk enclosures 4
or
Max. bandwidth 12 GB/s
Max. IOPS 1.000.000
Access latency 500 s (microseconds)
M RAID levels
Supported max. number of Hosts
Supported max. number of LUNs

0, 1, 5, 10
1024
2048
Dimensions 4 U Controller enclosure: 175 mm x 446 mm x 502 mm
Key software features HyperImage (snapshot), HyperMirror (synchronous/asynchronous remote replication)
OceanStor VIS6600T
The OceanStor VIS or Virtual Intelligent Storage system is designed for mid-range and high-
end customers. It is built as a solution that can consolidate different storage devices and present
the capacity as one big storage pool. It offers all value-added functions like snapshot, mirroring,
and replication. The OceanStor VIS 6600T series was therefore used in for instance government
data centers, financial institutions, carriers and large enterprises and institutions.
e n
/
An OceanStor VIS6600T is not a storage device but acts as an intermediate between multiple
storage arrays and hosts that run applications that need storage capacity.
o m
e i .c
OceanStor VIS6600T Front
aw
u
g .h
ni n
r
// lea
p :
t t
s :h
r c e
s ou
Re
g
n i n
ar
The performance and scalability make the OceanStor VIS6600T a flexible solution. The
L e
expansion options were numerous for connecting to storage devices, to application servers and to
r e
remote OceanStor VIS6600T systems.
o
M
OceanStor VIS6600T Back
OceanStor VIS6600T Back
e n
/
o m
e i .c
aw
u
g .h
ni n
r
lea
: //
t t p
:h
OceanStor VIS6600T Specifications
e s
r c
ou
Model VIS6600T
Number of Nodes 2 to 8 active-active load-balanced nodes
es
Processors per Node Multiple 64-bit cores
R
Cache per Node 96 GB
Service Ports per Node Up to 20 x 8 GFC ports, 20 x 1 Gbit/s iSCSI ports, and 8 x 10 Gbit/s iSCSI ports
ing
Storage virtualization
Basic Features Load-balancing and failover among links
Multi-node clustering
rn
Value-Added Features Heterogeneous volume mirroring / Snapshot / Data replication
a
Huawei OceanStor family
IBM System Storage DS series, TotalStorage DS series, V series, and XIV series
e
NetApp FAS series
L
HP StorageWorks MSA series, EVA series, and XP series
Compatible Storage Systems
EMC CLARiiON CX series, Symmetrix DMX series, and VNX series
e
Fujitsu ETERNUS series
r
Hitachi AMS/WMS series, Lightning series, Thunder series, and USP/NSC series
Oracle/SUN StorageTek series
o Multipathing Software
UltraPath (Windows/Linux/AIX), STMS (Solaris), PV-Links (HP-UX), and VxDPM (all
operating systems)
M Compatible Host Operating Systems Windows, Linux, Solaris, HP-UX, AIX, VMware, Hyper-V, and Citrix XenServer
OceanStor 9000 Big Data Storage System
The OceanStor VIS6600T is now used less often as the evolution of storage has continued and
disk capacity and intelligent virtual storage are now packed together. Maybe the best example of
this new generation of storage devices is the OceanStor 9000 Big Data system.
It offers everything: centralized management, huge capacity and scalability, NAS (CIFS and NFS)
functions and all enterprise class data protection option needed.
e n
/
o m
.c
OceanStor 9000 Big Data Storage System
e i
aw
u
Performance node
Mini capacity node
g .h
Capacity node
ni n
r
// lea
p :
t t
s :h
r c e
s ou
Re
i n g
The OceanStor 9000s are shipped as units with a number of disks installed. This number varies
n
but the 9000 can hold SSD, SAS and NL-SAS. Up to 288 OceanStor 9000s (then referred to as a
r
a
node) can work together. Used as a NAS solution it now offers a file system size up to 40 PB.
e
e L
or
M
Sybsystem File Storage Subsystem

System Architecture Fully symmetrical distributed architecture
Number of Nodes 3 to 288
System Features
Wushan distributed file system, which supports global namespace and can be dynamically expanded
e n
/
up to 40 PB
Applications File storage
Network Types 10 GE Ethernet, 40 GE Infiniband, or 1 GE
o m
.c
Data Protection Levels N+1, N+2, N+3, and N+4
Data Disk Types SSD, SAS, SATA, and NL-SAS
e i
w
Dynamic-storage tiering (InfoTier)
Software Automatic client connection load-balancing (InfoEqualizer)
a
Space quota management (InfoAllocator)
Data Recovery Quick automated parallel data recovery at up to 1 TB per hour
u
.h
Supported Protocols NFS, CIFS, HDFS, NIS, Microsoft Active Directory, and LDAP
i n g
r n
lea
Slide 52
: //
t tp
: h
Sybsystem
e s Analysis Subsystem
r c
System Architecture Fully symmetrical distributed architecture Fully symmetrical distributed architecture
o u
Number of Nodes 3 to 32 3 to 32
es
System Features
WushanSQL distributed database, supporting
quick retrieval of a large amount of structured and
FusionInsight Hadoop, supporting Sqoop,
MapReduce, HBase, and Hive
R
unstructured data
Unstructured and semi-structured data analysis
g
Applications Enterprise Hadoop
and Hadoop
i n Network Types 10 GE or 1 GE 10 GE
rn
Data Protection
Mirror The same as file system
Levels
a
Data Disk Types SAS and SATA --
L e Software
The compression rate is automatically adjusted.
The average compression ratio reaches 3:1. --
e
Quick retrieval of massive files (InfoExplorer)
r
Quick automated parallel data recovery at up to 1 Quick automated parallel data recovery at up
Data Recovery
o
TB per hour to 1 TB per hour
FusionInsight Hadoop, supporting Sqoop,
Supported Protocols Database protocol JDBC and ODBC
M
MapReduce, HBase, and Hive
Cabling Diagrams
Most of the models of the OceanStor are designed to be flexible. The customer can decide to add
disk enclosures for more storage capacity or add controllers for more performance. Or he can do
both. This means that a Huawei storage solution can consist of multiple controllers working
together and many disk enclosures connected to them. In this section a few simple examples of
the cabling schemes used with Huawei are discussed.
e n
Cabling Diagrams
/
o m
.c
Displays the cabling required for connecting:
1. Controllers to disk enclosures.

e i
2. Disk enclosures with other disk enclosures in a loop or chain.
aw
u
g .h
n
A loop or chain has a maximum of disks.
ni
r
High density enclosures and density enclosures cannot co-exist in
lea
the same loop or chain.
Multiple loops or chains can exist in one OceanStor system.

: //

t t p
Cables between enclosures en controller are type mini SAS (HD).
s :h
c e
r
Slide 54
s ou
Re
The examples shown next are just about adding disk enclosures. For more detailed information
i n g
on adding controllers please visit the Huawei support site.
n
For Field Service Engineers and Installation Engineers there is a link to remember:
r
e a
http://support.huawei.com/onlinetool/datums/nettool/index.en.jsp
e L
Here they will find the so-called Huawei Storage Networking Assistant. It is possible to select the
or
required OceanStor model and the configuration type (number of controllers and enclosures). The
M
Networking Assistant will then show the cabling diagram.
In the next images you will see some of the results of the Networking Assistant. Optionally you
can ask your instructor for a live demonstration of the Networking Assistant.
OceanStor 5300 & 5500 V3
e n
/
m
1 2 3 4 5 6
1 Ethernet Ports 4 Management
.c o
2 Mini SAS 5
network port
Maintenance
e i
w
expansion ports network port
3 Fibre Channel host
ports
6 Serial port
u a
g
Slide 55 .h
ni n
r
// lea
SAS expansion ports Controller enclosure
p :
t t
s :h
r c e
s ou
Re
i n g
r n
e a
e L
or
The controllers in this example have on board expansion ports called EXP 0 and EXP 1.
SAS expansion ports Disk enclosure
e n
/
o m
e i .c
aw
u
g .h
ni n
r
Cabling 1
// lea
p :
t
Single OceanStor 5300/5500 V3 and single disk enclosure.
t
s :h
r c e
s ou
Re
i n g
r n
e a
e L
or Copyright 2015 Huawei Technologies., Ltd. All rights reserved. Slide 58
MThis example shows that the controller is connected via a red and a blue cable. It is not so that we
need both cables to connect the controller with the disk enclosure. The two cables are there for
redundancy reasons. If one of the cables fails, or if the enclosure module fails, there is still a
reserve path available.
Cabling 2
Single OceanStor
5300/5500 V3
and three disk
enclosures.
e n
/
o m
e i .c
aw
u
g
Slide 59 .h
ni n
r
The image above shows a more complex solution where there are 4 disk enclosures connected to
lea
the controller. As mentioned in the module that discussed SAS there is a maximum number of
//
disk enclosures that can be linked together in a single loop. If the solution requires more disk
enclosures additional loops must be created.
p :
t t
OceanStor 5600 & 5800hV3
s :
r c e
o u
s
Re
i n g
arn
L e 1 2 3 4
r e
o 1 SAS/FC/Ethernet 3 Maintenance
M
ports network port
2 Management 4 Serial port
network port
The OceanStor 5600/5800 series is an example of an OceanStor that has no onboard SAS
interface ports. There a SAS card must be inserted to be able to create SAS loops.
Cabling 1
Single OceanStor 5600/5800 V3 and single disk enclosure.
e n
/
o m
e i .c
aw
u
g .h
ni n
r
lea
: //
Cabling 2
t t p
Single OceanStor
s :h
5600/5800 V3
r c e
ou
and three disk
Enclosures.
es
R
i n g
r n
e a
e L
or
Huawei Licensed Software Features
Licensed features are additional options a customer can purchase. Some of these features can
be applied in very specific situations like SmartQoS and SmartPartitioning. Other features like
HyperSnap and HyperReplication can be used to create a better backup strategy and/or disaster
recovery strategy. Backup strategies and DR strategies are of course a 24 hour a day application
of the Huawei licensed features.
e n
/
In this section we will list the most common licensed features and briefly explain their functions. In
module 11 we will take a closer look at the most used licensed features HyperSnap, HyperClone,
o m
.c
SmartTier, SmartReplication and SmartThin. There will be lab exercises on some of the licensed
features there as well.
e i
aw
u
g .h
ni n
Licensed Software Features
r
// lea
HyperClone SmartCache
p : SmartPartition
HyperCopy
t t
SmartCompression
:h
SmartQoS
HyperMirror SmartDedupe
s
SmartThin
e
HyperReplication SmartErase
HyperSnap
r c SmartMigration
SmartTier
ou
SmartVirtualization
SmartMotion
es
R
g
Note: Not all licenses are applicable to all OceanStor models.
n i n
ar
e
eL
or
M
Licensed features descriptions
The previous image showed the various licenses that can be purchased for the OceanStor
models. Most licenses are applicable to all models from the smaller OceanStor 5300 all the way
up to the big OceanStor 18800 models. The licenses sometimes are depending on each other
and in that case a licensed feature can only be used if the co-depending feature is already
licensed as well.
e n
/
The list is in alphabetical order.
o m
.c
HyperClone:
e i
Provides the clone function. Clone generates a full data copy of the source data in the local
storage system.
aw
u
HyperCopy:
g .h
i n
Provides the LUN copy function. A LUN copy copies the source LUN data onto the target LUN,
n
r
addressing the requirements of tiered storage, application upgrade, and remote backup.
// lea
:
HyperMirror:
t p
HyperMirror backs up data in real time. If the source data becomes unavailable, applications can
t
:h
automatically use the data copy, ensuring high data security and application continuity.
e s
HyperReplication:
r c
ou
Provides the remote replication function. Remote replication creates an available data duplicate of
es
a local storage system almost in real time on a storage system that resides in a different region.
R
The duplicate is instantly available without data restore operations, protecting service continuity
n g
and data availability to the maximum.
i
r n
HyperSnap:
e a
L
Provides the snapshot function. A snapshot is not a full physical copy of data. It only provides a
e
r
mapping table for locating data to implement quick data access.
o
MSmartCache:
The SmartCache feature uses solid state drives (SSDs) as caching storage resources. It
accelerates system read performance in the case where hot data exists, random small I/Os and
more reads than writes.
SmartCompression:
SmartCompression reorganizes data to reduce storage space consumption and improve the
data transfer, processing, and storage efficiency without any data loss.
SmartDedupe:
SmartDedupe is a data downsizing technology that deletes duplicate data blocks in a storage
system to save physical storage capacity, meeting growing data storage needs.
SmartErase:
SmartErase erases unnecessary data on a specified LUN several times so that the data on the
LUN cannot be recovered in case of the theft of the disk media.
e n
/
SmartMigration:
m
SmartMigration migrates services on a source LUN transparently to a target LUN without
.c o
interrupting host services. After the migration, the target LUN can replace the source LUN to carry
the services.
e i
aw
SmartMotion:
u
.h
By analyzing services, SmartMotion evenly distributes data in the same type of medium for
g
dynamically balanced capacity and performance.
ni n
r
lea
SmartPartition:
: //
SmartPartition allocates the cache resources from storage system engines on demand to improve
t p
QoS for mission-critical applications and high-level users.
t
SmartQoS:
s :h
r c e
SmartQoS controls the storage performance of one or more LUNs and prioritizes the service
ou
quality of critical applications.
es
SmartThin:
R
n g
SmartThin allocates storage space on demand. Within a specified quota of storage space, the
i
n
OceanStor Enterprise Storage System provides storage space based on demands of applications
r
a
to save storage resources.
e
e L
or SmartTier:
SmartTier periodically detects hotspot data per unit time and promotes them from low-speed
M storage media to high-speed one, boosting the system performance at an affordable cost.
SmartVirtualization:
SmartVirtualization enables a local storage system to centrally manage storage resources of
third-party storage systems, simplifying storage system management and reducing maintenance
costs.
Questions
Questions
1. What is the difference between traditional RAID and Huaweis RAID 2.0+ ?
2. What are the three tiers the OceanStor models supports?
e n
/
3. What is hot spare space used for?
4. What is the difference between an Extent and a Grain?
o m
.c
5. List the five convergence levels that OceanStor V3 offers.
e i
aw
u
g .h
ni n
r
lea
: //
Answers:
t t p
:h
1. Traditional RAID offers protection on the level of physical disks. RAID 2.0+ uses storage
e s
virtualization and protects blocks (chunks) of data against data loss.
r c
2. High Performance (SSD), Performance (SAS) and Capacity (NL-SAS).
ou
3. Hot spare space is located across all disks in a disk domain. They hold reconstructed blocks
es
of data in case a physical disk in the disk domain fails.
R
4. An Extend is the administrative unit used to create a thick LUN with (Default size is 2 MB). A
i n g
Grain is a subdivision of an Extent in 64 kB blocks. Grains are used to build Thin LUNs.
r n
5. SAN & NAS, High-End & Mid-Range & Entry-Level, SSD & HDD, Primary & Backup Storage,
e a
Heterogeneous convergence.
e L
or
M
Exam preparation
Statement 1: RAID 2.0+ offers better protection against data loss than
traditional RAID but it performs a little bit slower.
Statement 2: To rebuild a RAID 2.0+ protected failed drive takes a lot of
e n
/
time as all drives are involved in the rebuild of the spare
disk.
o m
.c
a. Statement 1 is true; Statement 2 is true.
b. Statement 1 is true;
c. Statement 1 is false;
Statement 2 is false.
Statement 2 is true.
e i
aw
u
g .h
ni n
r
lea
: //
t t p
s :h
r c e
ou
2. Which of the following OceanStor models are available as generation v3?
Select all that apply.
es a. OceanStor 2600.
R b. OceanStor 5300.
ing
c. OceanStor 6600.
rn
d. OceanStor 6800.
a
e. OceanStor 9000.
L e
r e
o
M
Answers:
1. D.
2. B, D.
Summary
Summary
RAID 2.0+ uses storage virtualization.
Hot Spare Space replaces the use of spare disks.
e n
/
RAID 2.0+ offers higher protection rates and higher
m
performances in rebuilding.
OceanStor V3s main features are convergence and in special

.c o
with SAN & NAS convergence. All V3 OceanStor models
natively support block based and file based storage.
e i
Many licensed features exist that can be purchased separately.
aw
u
g .h
ni n
r
lea
: //
t t p
s :h
r c e
s ou
Re
i n g
r n
e a
e L
or
M
Thank you e n
/
www.huawei.com
o m
e i .c
aw
u
g .h
ni n
r
lea
: //
t t p
s :h
r c e
s ou
Re
i n g
r n
e a
e L
or
M
e n
/
o m
e i .c
aw
u
g .h
ni n
r
// lea
p :
t t
s :h
r c e
s ou
Re
i n g
r n
e a
e L
or
M
e n
/
o m
OHC1109110
e i .c
Huawei Storage Initial Setup and aw
u
Configuration g .h
ni n
r
lea
://
www.huawei.com
t tp
s:h
r c e
sou
Re
i n g
r n
e a
e L
or
M
e n
/
o m
e i .c
aw
u
g .h
ni n
r
// lea
p :
t t
s:h
r c e
sou
Re
i n g
r n
e a
e L
or
M
Introduction
In this module the initial setup and configuration of the OceanStor is discussed. That means that
the physical rack mounting procedure has been completed and all cabling is done.
The steps to set up an OceanStor for first time use will be discussed here as well as all necessary
steps to create a LUN. Once a LUN is created the process of mapping will be discussed. With
mapping we give access to the LUN to one or more servers. The lab exercises that come with this
e n
chapter will have you create LUNs and map them to Windows based and/or Linux based hosts.
/
o m
e i .c
Objectives
aw
u
g .h
n

ni
r
Configure Disk Domains, Storage Pools, LUNs, LUN Groups, Hosts, Host Groups, Port
lea
Groups and Mapping Views.

: //
Connect the created LUN to a Windows server as a new volume.

t p
Use Disk Management to prepare the volume for use in Windows.
t
s :h
Module Contents
r c e
s ou
Re
1. Create a Disk Domain.
2. Create a Storage Pool.
i n g
3. Create a LUN.
r n
4. Create a LUN Group.
e a
5. Create a Host.
eL
6. Create a Host Group.
or
7. Create a Port Group.
M
8. Create a Mapping View.
9. Perform OS specific steps.
HCNA-storage V3 | OHC1109110 Huawei Storage Initial Setup and Configuration Page | 375
e n
/
o m
e i .c
aw
u
g .h
ni n
r
// lea
p :
t t
s :h
r c e
s ou
Re
i n g
r n
e a
e L
or
M
Page | 376 HCNA-storage V3 | OHC1109110 Huawei Storage Initial Setup and Configuration
Initial Setup
Initial Setup
Initial Setup Create Host
Create Disk Domain Create Host Group

e n
/
Create Storage Pool Create Port Group
o m
Create LUN Create Mapping View
e i .c
aw
u
Create LUN Group OS Specific Steps
g .h
ni n
r
lea
: //
t t p
After the physical rack mounting procedure has been completed and all cabling is done, the first
:h
step is to set up an IP address that will be used to connect to the OceanStor device for
e s
management. This requires a serial cable connected to the serial interfaces of both of the
r c
controllers. The serial interface port is labeled: I0I0I
s ou
Re
Setting the Management IP addresses
i n g
r n
e a Serial cable used to connect to controller (115,200 Baud).
e L
or
M
Serial cable
Management cable
Default IP addresses : 192.168.128.101 and 192.168.128.102
Every OceanStor device is shipped with a universal IP address set for the management interfaces.
That address is set to 192.168.128.101 for the first controller and 192.168.128.102 for the second
controller. A terminal program that has the option to run serial communication can now be used to
connect to the individual controllers. Many of those terminal programs exist. In the labs a well-
known program called Putty is used.
The connection in Putty must be set to 115,200 Baud. After the connection is established the
login screen appears.
e n
/
o m
Initial Setup Commands
e i .c
aw
u
g .h
ni n
r
lea
Default login with:

Username = admin
: //
p
Password = Admin@storage
t t
s :h
r c e
s ou
Re
i n g
r n
a
L e
r e
o
On the command line prompt, indicated with admin:/>, the next steps should be taken the very
M
first time the OceanStor is going to be used.
For security reasons it is very important to change the password for the admin user (who has the
highest administrator level rights) from Admin@storage into something only the authorized
system administrators know.
As the default IP address is not always in the range the administrator uses for management we
probably have to change that as well. The new ip address that will be set is from then on used to
launch the web based user interface called DeviceManager.
Task 1: Change login password [recommended].

Task 2: Set management IP addresses.
CLI command:
admin:/>changesystemmanagement_ipeth_port_id=CTEO.SMM0.MGMT0
e n
ip_type=ipv4_addressipv4_address=172.16.190.2mask=255.255.0.0 /
gateway_ipv4=172.16.0.1
o m
Note: indicates a space. Command is typed as one line of text!
e i .c
aw
u
g
Slide 6
.h
ni n
r
lea
In the lab environment it is not a problem to use the default settings for the admin password. So
//
we do not change it here. Again in real life only a limited number of persons should have access
:
to the OceanStor.
t t p
s :h
In that respect it is best to create multiple user accounts with different levels. In the picture below
c e
there are some commands that show, create and delete users or change their level.
r
s ou
Re
i n g
r n Some useful CLI commands:
e a
L
admin:/> show port ip eth_port_id=ENG0.A2.P0
r e admin:/> show user <username>
o admin:/> change user_password
M admin:/> create user type=<> user_name=<> level=<>
admin:/> change user user_name=<> level=<> action=<>
admin:/> delete user user_name=<>
Note <....> depicts an input of a name, password or other parameter
More useful CLI commands:

admin:/> show system general
admin:/> show version all
admin:/> upgradesys i<host ip address>-u<username>-p

<password>-f<file name>[-force]
e n
/
o m
Note: <....> depicts an input of a name, password or other parameter
depicts a space
e i .c
w
[...] indicates an optional parameter
u a
g .h
ni n
r
lea
Although most of the day-to-day configuration will be done using the graphical user interface there
are some CLI commands that can be used to monitor the OceanStor.
: //
t t p
:h
Typing the command show system general offers a quick overview of the status of the controller,
s
the temperature, which controller is master (or slave), serial number etc.
e
r c
ou
The show version all command will display the version information of almost all components in the
s
OceanStor including controllers, expansion modules and BBUs..
e
R
i n g
r n
e a
e L
or
M
These are just a few examples of the CLI commands that can be used. For each firmware version
of the OceanStor there is an extended Command Line Reference guide available. In there we find
hundreds of commands. Some of these commands are used to create LUNs and create
mappings to host. As most administrators will perform these tasks in the graphical user interface
we will look at that now.
In the lab guide that comes with this course you will find that the initial configuration has been
done and management IP addresses have been determined and set.
e n
/
m
After the initial setup via the serial connection is completed, the graphical user interface will be
used to perform the next steps.
.c o
e i
aw
u
Launching the DeviceManager User Interface
g .h
ni n
r
aInterface
l e
//
Launching the DeviceManager User
:
t tp
h
In a supported webbrowser type: https://<management ip>:8088
:
e s
r c
o u
es
R Default password:
g
Admin@storage
n i n
ar
L e
r e
o Copyright 2015 Huawei Technologies., Ltd. All rights reserved. Slide 9
M
The default login information is :
User name = admin
Password = Admin@storage
After that the main window of DeviceManager will be shown.
OceanStor DeviceManager Main Window
e n
/
o m
e i .c
aw
u
g .h
ni n
r
lea
Home: Brings the user back to the main window.
: //
System:
t p
Rack and controller information. Restarting controller(s),
t
:h
configuration of IP addresses and configuration of FC ports.
e s
Provisioning
c
Various volume related tasks (create, expand, delete) and mapping of
r
ou
the volumes (host group, mapping view). Here also disk domains and
s
storage pools are managed.
e
R
Data Protection
i n gOptions for snapshots, clones and replications.
r n
Monitor
e a Monitoring information of the entire system (i.e. IOPS, network
eL
bandwidth).
or
Settings Initial configuration tasks, Export data, Restart/Power off devices,
M Basic settings (time, location), Alarm & Performance Monitoring

settings, User settings.
Create Disk Domain
Steps to map a LUN in Windows

e n
/
o m
e i .c
aw
u
g .h
ni n
r
lea
: //
t t p
:h
Create Disk Domain
e s
r c
ou
Go to the Create Disk Domain dialog box: Click the Provisioning button.
Click Disk Domain.
es
R
i n g
r n
e a
e L
or
M
The first step in the process of creating a volume is to allocate storage capacity. That storage
capacity has to come from physical disks. A disk domain must be created by grouping a number
of physical disks together (optionally with different disk types). That is a Provisioning task.
At the right navigation bar, click the Provisioning button.
In the Provisioning screen, click the Disk Domain button. You will find the Disk Domain button in
the Storage Configuration and Optimization area (bottom part of the Provisioning window).
A Disk Domain is a set of disks, consisting of identical and/or different disk types, that will be
grouped together. Multiple disk domains can co-exist. Each disk domain will then offer services
(capacity, performance, tiering) independent to other disk domains. To create a new disk domain
e n
/
perform these steps.
o m
e i .c
Disk Domain Wizard
aw
u
g .h
Disk Domain Wizard
ni n
r
// lea
:
Click the Create button.
t t p
s :h

r c e
Enter a Name and Description for the
ou
Disk Domain.
es

R
Select one option in the Select Disk area.
i n g
r n
e a
eL
or
M
1. Enter a Name and Description for the Disk Domain.
2. In the Name text box, enter a name for the Disk Domain.
3. In Description text box, enter the function and properties of the Disk Domain.
The descriptive information helps identify the Disk Domain.
4. Select one option in the Select Disk area. The following options are: All available disks,
Specify disk type and manually select.
All available disks:
When you select this option, the system will use all available disks. You can choose a Hot Spare
Policy for each storage tier. From the dropdown menu you can choose High, Low or None.
Choose one of these options.
Specify disk type:

When you select this option, the system will give you the possibility to select one or multiple
storage tiers, as well as a specific amount of disks (blocks) per storage tier and a Hot Spare
Policy for each storage tier. You specify the amount of disks per storage tier.
e n
/
o m
.c
Manually select:
When you select this option, you are able to select specific disks per storage tier and the Hot
e i
Spare Policy.
aw
u
NOTE: You need at least four disks per storage tier to create a Disk Domain.
g .h
ni n
r
lea
In the following image the screen is shown where the administrator can manually select the disks
that should be included in the disk domain.
: //
t t p
h Select Disks
Create Disk Domain: :Manual
e s
r c
o u
e s
R
i n g
r n
e a
e L
or
M
We can see that from the twelve available disks six have been selected for the disk domain. As
they are all the same type it would mean that the disk domain would represent a single tier disk
domain. (Here a performance tier with SAS disks).
The number of disks and the type of disks determine available capacity, performance
characteristics and the possibility for Smart Tiering.
Disk Domain created
The success box will show that the operation has succeeded.
e n
/
o m
e i .c
aw
u
g .h
ni n
r
// lea
Slide 15
p :
t t
:h
The success box will show that the operation has succeeded.
e s
c
NOTE: It is impossible to remove disks from an existing disk domain.
r
ou
So if you by mistake selected 60 disks for a disk domain when only 6 were planned the solution is
s
drastic: Delete the entire disk domain and start again. However, deleting a disk domain requires it
e
R
to be completely empty. In other words all storage pools, lun groups and luns should be deleted
i n g
first for the disk domain to be empty! It is therefore important that you seriously think about the
n
size of a disk domain.
ar
L e
r e
o
M
Create Storage Pool
Storage pools are subdivisions of disk domains and there can be multiple storage pools in a disk
domain. Important to remember is that a storage pool will be assigned with a RAID protection
method. All LUNs that will be created inside of that storage pool will inherit those RAID protection
settings.
e n
/
o m
e i .c
aw
u
Create Storage Pool

g
Create Port Group.h
ni n
Create LUN
r
Create Mapping View
lea
://
t tp
s :h
c e
r
Slide 16
s ou
e
In the next section we will show the steps needed to create a new storage pool.
R
i n g
r n
e a
e L
or
M
Create Storage Pool
Go to the Create Disk Domain dialog box: Click the Provisioning button.
Click Storage Pool.
e n
/
o m
e i .c
aw
u
g .h
ni n
r
lea
1. At the right navigation bar, click the Provisioning button.
//
2. In the Provisioning screen, click the Storage Pool button. You will find the Storage Pool
:
button in the Storage Configuration and Optimization area.
t t p
s :h
Storage Pool Window
r c e
s ou
Click Create.
Re
i n g
r n
a
An alternative way to open the Create Storage Pool wizard is via the flowchart-like
e
diagram at the top of the screen.
e L
or
M
3. In the Storage Pool window, click the Create button to start the Disk Domain wizard.
At this point the administrator should have a clear idea about the LUNs he needs to create later
on for this storage pools. The RAID properties he will select for this storage pool will determine
protection, overhead and rebuilding. The RAID types supported are: RAID 1, RAID 10, RAID 3,
RAID 5, RAID 50, RAID 6
With RAID 5 there are three settings to choose from:
2D+1P: Two chunks hold user data and one parity chunk is calculated across these
n
chunks. Overhead = 33%.
/ e
4D+1P Four chunks hold user data and one parity chunk is calculated across these
o m
e i .c
8D+1P Eight chunks hold user data and one parity chunk is calculated across these
aw
u
.h
i n
To use 4D+1P and 8D+1P there must be at least five respectively nine disks used to build theg
r n
lea
disk domain.
: //
Create Storage Pool wizard p
t t
: h
e s

r c
u
Enter a Name and Description
o
for the Storage Pool.

es
Select Usage type.

R Select a Disk Domain.
i n g
Select Storage Medium.
arn
L e
r e
o
Optional: Click Set Smart Tier Policy to
set the Service Monitoring Period and
M
Data Migration Plan.
1. Enter a Name and Description for the Storage Pool.

2. In the Name text box, enter a name for the Storage Pool.
3. In the Description text box, enter the function and properties of the Storage Pool. The
descriptive information helps identify the Storage Pool.
4. In the Usage box, you need to select a user type for the Storage Pool. The value can be
Block Storage Pool or File Storage Service.
NOTE: This usage type is not changeable once it is configured.
5. In Disk Domain, you need to select a Disk Domain from the dropdown list.
6. In the Storage Medium, select the storage Tiers and RAID Policy needed for the Storage
Pool. Choose a capacity per storage tier. You can choose GB or TB.
Optional: Click the Set SmartTier Policy button to set the Service Monitoring Period and
n
Data Migration Plan.
/ e
The Set SmartTier Policy button is highlighted as soon as more than one tier is being used in the
o m
.c
disk domain and storage pool. SmartTier is a method in which data will be moving from disks
from one tier to disks of another tier. The reason for moving is the usage level of the data. Data
e i
that is not used a lot is best stored at cheaper storage. Frequently used data is best located on
aw
higher performance disks. SmartTier can arrange for this to happen. However: data migration has
u
a certain impact on the performance of the system. That is why Huawei schedules the migration
g .h
jobs to be run at off-peak hours. To determine which periods are off-peak the system must be
ni n
monitored for I/O performance. In the Service Monitoring Period we determine when the
r
lea
OceanStor will do performance monitoring. Once the monitoring has provided the system with the
: //
off-peak periods we can use the Data Migration Plan option to have OceanStor only migrate data
during these off-peak periods.
t t p
s :h
As SmartTier is a licensed option, and not everybody uses this function, the settings here are
optional.
r c e
o u
s
Storage Pool created
e
R
i n g
The execution result box will display that the operation has succeeded.
arn
L e
r e
o
M
The execution result box will display that the operation has succeeded.
Create LUN

e n
/
o m
e i .c
aw
u
g .h
ni n
r
lea
: //
t t p
A LUN or Logical Unit Number is an amount of space that is allocated inside a storage pool for
:h
a host. A LUN has the same RAID protection as the storage pool. A LUN can be created as a
e s
thick or a thin LUN. A thick LUN pre-allocates all required GBs of storage capacity even though
r c
no user data is stored yet. Thin LUNs will only occupy physical storage when user data is written.
ou
For thin LUNs the SmartThin license must be acquired.
es
R
i n g
r n
e a
e L
or
M
Create LUN
Go to the Create LUN dialog box: Click the Provisioning button.

Click LUN.
e n
/
o m
e i .c
aw
u
g .h
ni n
r
lea
To create a LUN follow these steps:
: //
t t p
:h
2. In the Provisioning screen, click the LUN button. You will find the LUN button in the Block
s
Storage Service area.
r c e
LUN window
s ou
Re

i n g
Click Create.
r n
e a
e L
or
M
Create LUN wizard
Enter a Name and Description

for the LUN.
Fill in the Capacity.
e n
Fill in the Quantity.
/
o m
.c
Select the Owning Storage Pool.
Click the Advanced button.

e i
aw
u
g
Slide 24 .h
ni n
r
lea
1. Enter a Name and Description for the LUN.
2. In the Name text box, enter a name for the LUN.
: //
t p
3. In the Description text box, enter the function and properties of the LUN. The descriptive
t
:h
information helps identify the LUN.
e s
c
Optional If the SmartThin licensed feature is purchased, it is possible to create thin
r
ou
provisioned LUNs. To enable this feature, check the Enable checkbox. When the SmartThin
s
feature is enabled, the Create LUN wizard will show an option called Initially Allocated
e
R
Capacity. Example: When the total capacity is 50 GB and you fill in the Initially Allocated
i n g
Capacity with 10 GB, the LUN will take just 10 GB on the Storage Pool. This LUN can grow
n
until it reached 50 GB.
ar
L e
4. Fill in the Capacity for the LUN.
r e5. In the dropdown box, select one of the following options: Blocks, MB, GB and TB.
o
M 6. Fill in the Quantity.
It is possible to create a maximum of 500 LUNs at the same time. If the quantity is 5, the
system will create five LUNs with the same capacity. The names of the LUNs will be extended
with 001, 002 up to 005.
7. Select a Owning Storage Pool from the dropdown list. The LUN will be created in the
Storage Pool that is selected.
8. Set the advanced properties for the LUN by clicking the Advanced button.
Advanced settings 1
Click the Properties tab.
e n
/
o m
e i .c
aw
u
g .h
ni n
r
lea
In the Advanced menu there are options which could be useful based on your service needs.
: //
t t p
Properties tab
s :h
r c e
ou
The option Owning Controller ID allows the administrator to force the ownership of a LUN to a
s
specific controller. Default setting is automatic which means that LUNs will alternatively be owned
by the two controllers:
Re
-
g
First LUN to controller 0.
i n
n
- Second LUN to controller 1.
-
ar
Third LUN to controller 0 etc.
L e
r e
There are four options for the Initial Capacity Allocation Policy:
o
M Default: Automatic allocation.
Allocate from the high-performance tier first.
Allocate from the performance tier first.
Allocate from the capacity tier first.
In the Cache Policy area the Read and Write Policy can be changed. There are three options
available for the Read Policy as well as for the Write Policy:
Resident:
For random cache access. Data is retained in cache the longest to improve the read ratio.
Default:
For regular cache access. Keep balance between write hit ratio and disk access performance.
e n
/
Recycle:
o m
.c
For sequential cache access. The idle cache resources are released for other access
requests.
e i
aw
u
Select a Prefetch Policy from the Prefetch Policy area.
g .h
ni n
Prefetching is a technique that can be used to improve the read performance for data read from
r
lea
disks. The technique analyses data that was read before and determines if the data may be used
//
again soon. That data will be prefetched (loaded before the user requests the data) and stored in
p :
the READ AHEAD RAM cache of the controller. Next time the user requests the same data again
t t
it is read from RAM instead from disk. Next to the performance gain there is an additional benefit.
s :h
Disks have to do less seeks to find data which extends their lifespan slightly.
r c e
o u 2
s
Advanced settings
e
R
i n g Click the Tuning tab.
arn
L e
r e
o
M
Tuning tab
In the Tuning tab it is possible to configure some licensed features. Licensed features which are
available are as follow:
SmartTier.
SmartQoS.
SmartCache.
SmartDedupe & SmartCompression.
e n
/
m
SmartPartition.
.c o
e i
LUN created
aw
u
The execution result box will display that the operation succeeded.
g .h
ni n
r
// lea
p :
t t
s :h
r c e
s ou
Re
g
Slide 27
n i n
ar
Le
r e
o
M
Create LUN Group

e n
/
o m
e i .c
aw
u
g .h
ni n
r
lea
: //
t t p
With Huawei a LUN can be used by a host when it has been mapped to that host. This will be
:h
discussed in the next section. For the mapping to work, every LUN must be placed inside of a
e s
socalled LUN group. If a LUN group contains more than one LUN, than a host that has access
r c
priviliges to that LUN group automatically has access to all LUNs in that LUN group.
s ou
Re
i n g
r n
e a
e L
or
M
Create LUN Group
Go to the Create LUN dialog box: Click the Provisioning button.

Click LUN.
e n
/
o m
e i .c
aw
u
g .h
ni n
r
lea
//
2. In the Provisioning screen, click the LUN button. You will find the LUN button in the Block
:
t t p
s :h
Create LUN Group
r c e
s ou

e
Select the LUN Group tab. Click Create.
R
i n g
r n
e a
e L
or
M
Select LUNs from the
Available LUNs to move to
the Selected LUNs area.
3. When the LUN window is opened, click the LUN Group tab. Click the create button to start the
Create LUN Group wizard.
4. In the LUN window, click the Create button to start the Create LUN wizard.
5. In the Create LUN Group wizard, enter a Name and Description for the group.
6. Enter a Name and Description for the LUN.
7. In the Name text box, enter a name for the LUN.
8. In the Description text box, enter the function and properties of the LUN. The descriptive
information helps identify the LUN.
9. Select the LUN to add to the LUN Group.
10. In the Available LUNs area, select one or multiple LUNs based on your service needs.
11. Click the Right arrow button ( > ) to add the LUNs to the Selected LUNs area.
e n
/
o m
LUN Group created
e i .c
aw
u
.h
i n g
r n
// lea
p :
t t
s :h
r c e
s ou
Re
i n g
n
ar
L e
r e
o In module 11 we will show how a snapshot can be created of a LUN. A snapshot can be mapped
M to a host by adding the snapshot to the LUN Group that already has the original LUN.
Create Host

e n
/
o m
e i .c
aw
u
g .h
ni n
r
lea
: //
t t p
A host is the physical server that runs an application that generates data that should be stored on
:h
the LUN created in an OceanStor device. From the DeviceManager perspective a host consists of
e s
a number of I/O interfaces that the host uses to connect to the storage network.
r c
ou
When a host is created the I/O interfaces are identified but also the operating system that the host
es
runs. Also the IP address of the host may be entered in this process.
R
i n g
r n
e a
e L
or
M
Create Host
Go to the Create Host dialog box: Click the Provisioning button.

Click Host.
e n
/
o m
e i .c
aw
u
g
Slide 33
.h
ni n
r
lea
//
2. In the Provisioning screen, click the Host button. You will find the Host button in the Block
:
t t p
:h
3. Add initiators to hosts and add the hosts to host groups to establish a logical connection
s
between application servers and the storage system.
r e
c1
u
Create Host wizard
o
e s
R
g
On the Host tab: Click Create Manually Create.
n i n
ar
L e
r e
o Enter a Name and
M
Description for the
Host.
Select an OS from the
dropdown list.
Enter an IP address.
In the Host screen you can create Hosts and Host Groups.
To create a Host:
1. Click the Host tab.

2. Click the Create button and select the Manually Create option. This wil open the Create Host
wizard.
3. Then enter a name and description for the Host.
4. In the Name text box, enter a name for the Host.
5. In the Description text box, enter the function and properties of the Host. The descriptive
n
information helps identify the Host.
6. Select an Operating System from the dropdown list.
/ e
7. Enter the IP address for the Host.
o m
Optional Enter a Device Location
e i .c
aw
u
Create Host wizard 2
g .h
ni n
r
lea
Select one or multiple initiators
//
from the Available Initiators
:
and move the selected initiators
p
to the Selected Initiators area.
t t
s :h

r c e
Click the Create button if there
ou
is no initiator available.
es
R
i n g
r n
a
L e
r e
1. Select one or multiple initiators from the Available Initiators area and click the Down arrow
o
M
to move the selected initiators to the Selected Initiators area.
2. If there is no initiator available, click the Create button.
Create Initiator
Select the initiator Type.

When you choose for iSCSI, you will need to the use the IQN.
When you choose FC/IB, you will need the WWPN.
e n
/
o m
Note:
e i .c
w
IQN = iSCSI Qualified Name
WWPN = World Wide Port Name
u a
g
Slide 36
.h
ni n
r
lea
If the type for the iSCSI initiator is iSCSI you must enter the IQN. If you select Fibre Channel or
//
InfiniBand (IB) as an initiator type, you will need the WWPN to create a new initiator.
:
t
For the iSCSI initiator it is possible to enable CHAP authentication.
t p
s :h
e
CHAP or Challenge Handshake Authentication Protocol is a method that can be used to test a
r c
trusted relationship between two devices (called partners).
ou
It is in principle based on the fact that before a connection is set up between two devices a sort of
s
e
password check is held. At that point both devices or partners should reply to the question of the
R
g
other partner: what is my password. So it is a bidirectional password check that sets up the
i n
trusted relationship. CHAP has added some nice features like encryption. That means that the
n
r
password that is send from the partner to the other partner is encrypted so no-one listening in on
a
e
the conversation can detect the password. Optionally a CHAP password check can be repeated
L
e
at intervals even when the initial password check was successful and the connection was
or established.
Create Host wizard 3
e n
/
o m
e i .c
aw
u
g .h
ni n
Slide 37
r
// lea
Last part of the Create Host Wizard is the summary and the confirmation. IQNs should be unique
p :
t
for a host but they are not mechanically fixed inside a host. In fact, the IQN is a string that can be
t
:h
changed quite easily. It is therefore important that the administrator agrees with accepting the
s
consequences in the Danger window. Once the checkbox is checked and the OK button is clicked
the Execution Result will be shown.
r c e
s ou
Re
i n g
For every host that was created probably a number of LUNs are prepared for that host to access.
n
How the host finally accesses the LUN is explained later in the mapping section. Now imagine the
ar
situation where a number of different hosts all need access to a (number of) LUN(s). That would
L e
mean that all volumes individually should be mapped to every host. For that to be easier there is
r e
the concept of a Host Group. We will explain this in the next section.
o
M
Create Host Group

e n
/
o m
e i .c
aw
u
g .h
ni n
r
lea
: //
t t p
In a host group there can be one or more hosts. A LUN (or LUN Group) can be mapped to the
:h
host group. If multiple hosts are added to a host group it means that all hosts will see the mapped
e s
LUNs that are in the specified LUN Group. The system will warn you when you add multiple hosts
r c
to a Host Group. The warning states that, if the hosts do not belong to a cluster, there is a real
ou
possibility that data will become corrupt. If more than one hosts, without the intelligence of a
es
cluster/file-locking mechanism, can access and modify the same files on a LUN the data may
become corrupted.
R
i n g
r n
In environments were a lot of LUNs should be accessible by many hosts the concept of host
e a
groups saves the administrator a lot of work. He now maps a LUN to a host group instead of
e L
mapping a LUN multiple times to individual hosts.
or
M
Especially with server virtualization like VMware and Hyper-V using Host Groups is very
convenient for making shared storage (referred to as datastores).
With the advanced options, VMware and also Hyper-V offer, it is a necessity that all VMware or
Hyper-V hosts can see the datastores at the same time.
Create Host Group
Go to the Create Host dialog box: Click the Provisioning button.

Click Host.
e n
/
o m
e i .c
aw
u
g .h
ni n
r
lea
//
2. In the Provisioning screen, click the Host button. You will find the Host button in the Block
:
t t p
s :h
Create Host Group wizard
r c e
s ou

e
Open the Host Group tab and click Create.
R
i n g
r n
e a
e L
r
Enter a name for the
o
Host Group.
M Select a host from the

Available Hosts area and
move it to the
Selected Hosts area.
In the Host screen you can create Hosts and Host Groups.
To create a Host Group:
1. Click the Host Group tab.

2. Click the Create button. This will open the Create Host Group wizard.
3. In the Create Host Group wizard, enter a name and description for the Host Group.
4. In the Name text box, enter a name for the Host Group.
5. In the Description text box, enter the function and properties of the Host Group. The
descriptive information helps identify the Host Group.
6. Select one or multiple hosts from the Available Hosts area and click the Right arrow to
e n
/
m
move the selected host(s) to the Selected Hosts area.
.c o
e i
Host Group created
aw
u
g .h
n
ni
r
// lea
p :
t t
s :h
r c e
s ou
Re
g
n i n
ar
During the process of creating the Host the initiators are assigned to the host. Typically the
L e
interface card in the physical host has multiple ports. The host definition will then list all individual
r eports of the cards as part of the new host. All ports will then be used as paths when a LUN gets
o mapped to that host. Sometimes however we want to specify which ports should be used as
M active data paths in the mapping of a LUN. In that case a Port Group can be made. Inside a port
group we group interface ports together. When the mapping is done over the host it uses all
physically present interface port. When the mapping is done using a port group only the ports
listed in the port group will be used.
Create Port Group

e n
/
o m
e i .c
aw
u
g .h
ni n
r
lea
: //
t t p
:h
Create Port Group
e s
r c
ou
Go to the Create Port dialog box: Click the Provisioning button.
Click Port.
es
R
i n g
r n
e a
e L
or
M

2. In the Provisioning screen, click the Port button.
You will find the Port button in the Storage Configuration and Optimization area.In the Port
screen you can view and manage host ports, port groups, VLANs and logical ports.
Create Port Group wizard
Open the Port Group tab.

Click Create.
Enter a Port Group

name and description.
e n
Select a port from the
/
Available Ports area
and move it to the
o m
.c
Selected Ports area.
e i
aw
u
g
Slide 44 .h
ni n
r
lea
3. When the Port screen is opened, click the Port Group tab.
4. Click the Create button. This will open the Create Port Group wizard.
: //
t p
5. In the Create Port Group wizard, enter a name and description for the Port Group.
t
:h
6. In the Name text box, enter a name for the Port Group.
s
7. In the Description text box, enter the function and properties of the Port Group. The
c e
descriptive information helps identify the Port Group.
r
s ou
8. Select one or multiple ports from the Available Ports area and click the Right arrow to move
Re
the selected port(s) to the Selected Ports area.
i n g
9. Then click OK to finish the Port Group creation.
r n
e a
e L
r
The Execution Result windows is shown next.
o
M
Create Mapping View

e n
/
o m
e i .c
aw
u
g .h
ni n
r
lea
: //
t t p
:h
Create Mapping View
e s
r c
ou
Go to the Create Mapping View dialog box: Click the Provisioning button.
Click Mapping View.
es
R
i n g
r n
e a
e L
or
M

2. In the Provisioning screen, click the Mapping View button. You will find the Mapping View
button in the Block Storage Service area.
A Mapping View is a view that reflects the access restrictions and mapping among a LUN Group,
a Port Group and a Host Group.
Create Mapping View wizard
Click Create.
e n
/
Enter a Name and
o m
.c
Description for the Mapping
View.
e i
aw

u
.h
Click the triple dots button to
select a LUN Group, Host
Group and Port Group.
i n g
r n
//
lea Slide 47
p :
t t
:h
In the Mapping View screen:
1. Click the Create button.

e s
2. Name and describe the Mapping View.
r c
ou
3. In the Name text box, enter a name for the Mapping View.
es
4. In the Description text box, enter the function and properties of the Mapping View. The
R
descriptive information helps to identify the Mapping View.
n g
5. Click the triple dots button to select a LUN Group, Host Group and Port Group.
i
r n
e a
e L
or
M
Create Mapping View Wizard
Check the checkbox and click OK.
e n
/
o m
e i .c
aw
u
g .h
ni n
r
lea
Read the message, check the checkbox and click OK to create the Mapping View.
: //
Mapping View created
t t p
s :h
c e
r
s ou
Re
i n g
r n
e a
e L
or
Now all steps are completed to create a LUN and map it to an Operating System. In the upcoming
section we will show how the operating system (in this case Windows) can detect the new LUN
and use it as a volume to put data on.
OS Specific Steps

e n
/
o m
e i .c
aw
u
g .h
ni n
r
lea
: //
t t p
In most situations the host is physically connected to the storage network via switches using the
:h
FC or the iSCSI protocol. If the protocol used is iSCSI then the detection of new LUNs for
e s
Windows works a bit different than with the FC protocol.
r c
s ou
Re
i n g
r n
e a
e L
or
M
OS Specific Steps
Use the iSCSI Initiator to map

LUNs to a host.
Open the iSCSI Initiator.
Click the Discovery tab.

Click the Discover Portal button.
e n
/
o m
e i .c
aw
u
g .h
ni n
r
lea
We need a few more steps before we can use the iSCSI-based LUN as a new partition in our
Operating System:
: //
t t p
1. First we have to connect the LUN to the Operating System by using the iSCSI initiator. For
:h
that we need to open the iSCSI Initiator and click the Discovery tab.
s
2. Configure the Target Portal by clicking the Discover Portal button.
e
r c
3. Enter the IP address or DNS name. In this case we need to enter the IP address that is
ou
configured to one of the Huawei OceanStor V3 network ports.
es
R
NOTE: When the LUN is configured with Fibre Channel, the LUN will immediately be connected
i n g
to the Operating System after creating the Mapping View. You only need to use Disk
n
Management to create a new partition.
ar
L e
r e
o
M
iSCSI Initiators Properties
Click the Targets tab.
n
Select the Inactive target and click
e
the Connect button.
/
o m
e i .c
aw
u
g
Slide 52 .h
ni n
r
lea
After the new target portal is listed in the Discovery tab, click the Targets tab. Notice that a new
//
target is discovered. The status of the new target is Inactive. Select the target and click the
:
Connect button below the Discovered targets area.
t t p
s
At this point the target shows a status: Connected.
:h
r c e
ou
Now the newly discovered storage capacity will be forwarded to the disk management part of
s
the operating system. In our case to Windows disk management.
e
R
i n g
r n
e a
e L
or
M
Disk Management
For both iSCSI as well as FC connected LUNs the newly discovered LUN should be presented to
the operating system. This is done via the Disk Management module of Windows.
All new volumes (Windows uses the term volumes when a LUN is presented to it) will appear in
disk management. This is the case for LUNs created in Huawei OceanStor devices but also for
USB sticks, CD/DVDs as they also represent storage capacity.
e n
/
o m
Disk Management
e i .c
aw
Use the Disk Management to create a new disk partition
u
Open the Server Manager.
g .h
ni n
r
lea
Expand the Storage part.
//
Click Disk Management.
p :
t t
s :h
r c e
s ou
Re
i n g
The LUN is now connected to the operating system. Open the Server Manager, expand the
r n
Storage part and click Disk Management.
e a
e L
or
M
Rescan Disks
At the left top of the screen, click Action and select the Rescan Disks option.
e n
/
o m
e i .c
aw
u
g
Slide 54 .h
ni n
r
lea
If the LUN is not yet discovered by Disk Management, click the Action button at the top menu bar
//
and select the Rescan Disks option. This option will have the operating system do a new
:
t p
hardware scan for new disk devices. This may take some time to complete but after a while a new
t
:h
storage device will be shown.
e s
r c
New Partition Discovered
o u
e s

R
A new partition will show. Click the right mouse button and select Online.
i n g
r n
e a
e L
or
M
The new partition will now show up in Disk Management. The partition is Offline. To put it online,
click the right mouse button and select Online.
Initialize Disk
Click the right mouse button and select Initialize Disk.
e n
/
o m
e i .c
aw
u
g .h
ni n
r
lea
The partition is not yet initialized. To initialize the disk, click the right mouse button and select the
//
Initialize Disk option. This will open the Initialize Disk window.
p :
t t
:h
Initialize Disk
e s
r c
s ou
Re
i n g
r n
e a
e L
or
M
In the Initialize Disk window, select one of the partition styles and click OK. The partition is now
initialized. MBR is the most common one but the GPT type should be selected for LUNs that are
bigger than 2 TB. Initializing a disk means that Windows will create a unique identifier for the
partition and store that ID on the disk. In older versions of windows this was referred to as the disk
signature.
Create New Simple Volume
Click the right mouse button and select New Simple Volume
e n
/
o m
e i .c
aw
u
g
Slide 58
.h
ni n
r
lea
Although the disk has a signature now and is initialized there is not yet a file system on the
partition. That would be the next step.
: //
t t p
:h
Notice that the new storage partition is label as Basic. Windows has two types of partitions called
s
Basic and Dynamic. Dynamic disks were introduced in Windows NT in the 1990s. In that period
c e
Microsoft changed the file system they had then (FAT) into the NTFS. NTFS was short for New
r
ou
Technology File System. In NTFS dynamic disks were introduced because of the fact that
s
dynamic disks could be expanded. Another reason is the fact that Windows NTFS supports
e
R
software RAID. It means that Windows can handle two individual volumes and perform RAID
i n g
actions on them. Two dynamic disks could be spanned together which basically means they were
n
put in a RAID 0 configuration. Options as mirroring (RAID 1) and striping with parity (RAID 5)
ar
were also offered. However, in practice the majority of partitions used are Basic disks.
L e
r eThe space of the partition is still unallocated space. To create a new partition, click the right
o mouse button and select the New Simple Volume option. This will open the New Simple
M Volume Wizard.
New Simple Volume Wizard
Follow the steps of the New Simple Volume Wizard to create a new Simple Volume.
Images show Windows 2008 screenshots.
e n
/
o m
e i .c
Note: Windows 2003 used the term partition instead of Simple Volume
aw
u
g .h
ni n
r
lea
Important step in the New Simple Volume is the Specify Volume Size. Here the administrator
//
decides how much of the physical capacity will be assigned to the New Simple Volume. Mostly it
:
t p
is the total amount, but also less than the maximum is possible. The remaining space can be
t
:h
added to the volume in a later stage if necessary.
e s
r cWizard
u
New Simple Volume
o
e s
R
i n g
arn
L e
r e
o
M
Next step is to assign a drive letter to the new simple volume. Windows supports up to twenty-six
drive letters. If we need more than twenty-six volumes attached to the host mount points can be
used. Next window is the Format Partition window.
Here we select the file system to be used and the allocation unit size (or block size). This
allocation unit size is a software defined size and it has no relation to the block size (chunk or
stripe) of the physical disk drive.
e n
/
A volume label must be entered to identify the new volume next to the drive letter. The image
m
before shows the Format Partition settings to be:
.c o
- File System: NTFS.
e i
- Allocation unit size: Default.
aw
- Volume label: LUN001.
u
g .h
i n
Per default the Perform a quick format checkbox is checked. It means that, especially with large
n
r
LUNs\volumes, the time needed to format the disk is much shorter. A quick format will only write
lea
the minimal required information on the volume. A full format would write empty data blocks
across the entire volume.
: //
t t p
: h
s
New Simple Volume Wizard
e
r c
o u
es
R
i n g
r n
e a
e L
or
M
This last but one window allows you to check all the settings for the new partition and click the
Finish button to complete the New Simple Volume Wizard.
Depending on the size of the volume (and the checkbox with Quick Format) the process of
formatting a disk can take from 5 -10 seconds up to a couple of minutes.
When the process has finished the disk management window will show the new volume with its
drive letter and label name. It will also indicate the size of the volume.
New Simple Volume Ready
e n
/
The partition is now ready for use.
o m
e i .c
aw
u
g .h
ni n
r
// lea
p :
t t
:h
e s
r c
ou
The partition is now successfully created and ready for use.
es
R
In the Windows Explorer the volume will now be accessible as volume H:\ and the label name or
i n g
better volume name is LUN 001.
r n
a
Applications that run on the host can now select the volume to save data there.
e
e L
or
MThis concludes this module. We want to add to this that the process to map a LUN to a Linux
based host is almost identical. The biggest changes are in the discovery of the new LUN in the
operating system. The definition of a host is almost the same for a Windows host and a Linux
based host.
Questions
Questions
1. What are two reasons to create multiple disk domains within an

OceanStor device?
2. When would you put multiple LUNs into a single LUN Group?
e n
/
m
3. When would you put multiple hosts into a single Host Group?
4. What is the reason to use a Port Group?
.c o
5. Describe the difference between a LUN and an NTFS volume.
e i
aw
u
g .h
ni n
r
lea
: //
t t p
s :h
e
Answers:
r c
ou
1. The first reason is to isolate performance characteristics. LUNs are created inside Storage
s
Re
Pools and Storage Pools are created inside of a Disk Domain. Therefore a LUN can only
benefit from the performance offered by the physical disks inside the Disk Domain.
i n g
r n
Second reason is to separate hard disks based on type and size into multiple Disk Domains.
e a
This would then offer Disk Domains that differ in disk costs and performance.
e L
or 2. LUN groups can be created to group LUNs, with dependencies between them, together.
M
Mappings, snapshots and replication of LUN Groups will use all LUNs of the LUN Group.
3. Host Groups can be used if clustered Hosts should all have access to the same LUN (s).
4. A Port Group can be used to limit or specify the physical ports of a host that should be used
as a data path.
5. A LUN is an entity within the OceanStor device whereas an NTFS volume is defined within
the operating system.
Exam Preparation
1. Which of the following tasks are MANDATORY tasks in the process of

mapping a LUN to a host. (check all that apply)
a. Create Disk Domain.

e n
b. Create Storage Pool.
/
c. Create Lun Group.
o m
.c
d. Create Host.
e. Create Host Group.
e i
w
f. Create Port Group.
g. Create Mapping View.
u a
g .h
ni n
r
lea
: //
t t p
Exam preparation (2) h
s :
r c e
2. Situation:
o u
s
There are hundred disks put in one single Disk Domain. Just one LUN is
Re
created.
Statement 1: Splitting the disk domain up into two 50 disk disk domains
i n g does impact the performance of the LUN.

Statement 2: Initializing the file system as GPT is required for volumes
r n bigger than 2 TB.
e a a. Statement 1 is true, Statement 2 is true.
eL
b. Statement 1 is true, Statement 2 is false.
or
c. Statement 1 is false, Statement 2 is true.
M
d. Statement 1 is false, Statement 2 is false.
Answers:
1. A, B, C, D, E, G.
2. A.
Summary
Summary
Disk Domains and Storage Pools is where LUNs are created.

Disk Domains created with different disk types can offer Tiering.
e n
/
Storage Pools have a RAID protection level associated with them.
LUNs inherit the RAID protection fom the Storage Pool they live
o m
.c
in.
Hosts are created by assigning initiators to them.
e i
Mapping Views create the link between a LUN and a host for data
access.
aw
u
.h
iSCSI and FC connected host have a slightly different way of
discovering new storage LUNs.
i n g
r n
lea
: //
t t p
s :h
r c e
s ou
Re
i n g
r n
e a
e L
or
M
Thank you
www.huawei.com
e n
/
o m
e i .c
aw
u
g .h
ni n
r
// lea
p :
t t
s :h
r c e
s ou
Re
i n g
r n
e a
e L
or
M
e n
/
o m
OHC1109111
e i .c
Huawei Storage Firmware and Features
aw
u
g .h
ni n
r
lea
://
www.huawei.com
t tp
s:h
r c e
sou
Re
i n g
r n
e a
e L
or
M
e n
/
o m
e i .c
aw
u
g .h
ni n
r
// lea
p :
t t
s:h
r c e
sou
Re
i n g
r n
e a
e L
or
M
Introduction
In the previous module the initial setup and basic configuration of the OceanStor series were
discussed. It included the basic tasks like creating and mapping LUNs. In this module we will
discuss some of the licensed features Huawei offers. There is no room to discuss all of them so a
limited number is selected. The features HyperSnap, HyperClone, HyperReplication and
SmartTier will be discussed as they are very popular and they are used often by Huawei
n
customers. Also the firmware update procedures will be covered in this module.
/ e
o m
Objectives e i .c
aw
u
g .h
n
Use the HyperSnap licensed feature to create snapshots.

ni
r
Use snapshots to recover files.
lea
Use the SmartThin licensed feature to create thin provisioned LUNs.

: //
Use the SmartTier licensed feature to move data between multiple storage tiers.

t
Explain how the HyperClone feature works.
t p
:h
Understand the HyperReplication working modes.

s
Describe the Huawei firmware update procedures.
e
r c
s ou
Module Contents Re
i n g
r n
1. HyperSnap.
e a
2. Use snapshots to recover files.
eL
3. Rollback snapshot.
or 4. SmartThin.
M 5. SmartTier.
6. HyperClone.
7. HyperReplication.
8. Firmware updates.
HCNA-storage V3 | OHC1109111 Huawei Storage Firmware and Features Page | 429

e n
/
o m
e i .c
aw
u
g .h
ni n
r
// lea
p :
t t
s :h
r c e
sou
Re
i n g
r n
e a
e L
or
M
Page | 430 HCNA-storage V3 | OHC1109111 Huawei Storage Firmware and Features

HyperSnap
The HyperSnap license allows the user of the OceanStor to create snapshots of a LUN. A
snapshot is sometimes referred to as a Point-In-Time copy. What it essentially does, is to create a
copy of an existing LUN. The copy of the LUN can be used in a couple of situations:
We can use the copy for recovery. If something goes wrong with the data on the LUN we can
restore the data from the snapshot.
e n
/
Second application is the use of a snapshot to improve the backup strategy. Traditionally a
o m
backup administrator will make one backup per day, mostly in the evening. With snapshots we
can make multiple copies of a LUN and make backups of the snapshot LUNs.
e i .c
aw
u
.h
The good thing about a snapshot is that it can be created very quickly (in seconds) and they do
not consume a lot of space.
i n g
r n
lea
There are two mainstream techniques for making the snapshot: Copy-On-Write and Allocated-On-
//
Write. Huawei uses the Copy-On-Write method.
p :
t t
HyperSnap
s :h
r c e
ou
Copy-On-Write Snapshot technique
es
R
g
Active Active Active
Snapshot Snapshot
n
File System File System File System
n i F:\ S:\ F:\ S:\ F:\
ar 2. Write
e
eL
A B C D A B C D A B C D* D
or 1. Copy
M Before Snapshot. After Snapshot. After Block Updated.
In the above picture the technique is explained. Important again is to understand that a LUN for
the OceanStor is made up of small blocks (extents). The volume on the host holds files in the file
system directory (F:\ for instance 50 GB) but for the OceanStor there are only blocks. The
blocks are represented with A, B, C and D.

When the snapshot is created in the OceanStor it can be regarded as a new LUN. That new LUN
can be mapped to the same host as the original LUN. From that point on the host sees the
original LUN as F: and the snapshot of the LUN as S:\. At this point S: does not consume space
as the snapshot uses block A, B, C and D to represent F:\ as well as S:\.
The challenge is there when data on F:\ gets changed after the snapshot was created. F:\ should
then change but S:\ should still represent the data that was on F:\ at the time the snapshot was
created. With Copy-On-Write the first step to be taken when data changes, is to make a copy of
the block to preserve the original version of the block.
e n
/
o m
.c
This is represented in the picture with step 1: Copy. (D is the copy of the original block). Then the
e i
new data written on F:\ can modify the used block on F:\. In this example the new data changes
the content of block D. The changed block is labeled D*.
aw
u
.h
At this point F:\ points to the blocks A, B, C and D* where S:\ points to the blocks A, B, C and D.
g
ni n
r
F:\ contains the current version of the files and S:\ shows the files that were on F:\ at the time the
lea
snapshot was created. Combined the space consumed by F:\ and S:\ is not 2 x 50 GB. The size
: //
of a snapshot is basically equal to the number of changed blocks times the size of a block. In this
t p
example it would be 50 GB + 1 block to store the original LUN plus the snapshot.
t
s :h
A LUN can have multiple snapshots active where each mapped snapshot could be backed up.
r c e
This allows the SAN administrator to make multiple backups during the day. Snapshots have little
ou
impact on the performance of the OceanStor and it takes a very short time to create a snapshot.
es
R
In the Provision section of the DeviceManager user interface we already saw how to create a LUN.
n g
It is the same area of the user interface where the snapshots can be created. Of course this
i
n
requires that the HyperSnap feature is licensed.
r
e a
e L
or
M

Create Snapshot
Create Snapshot
Select a LUN.
Click More and select the Create Snapshot option.
e n
/
o m
e i .c
aw
u
g .h
ni n
r
lea
: //
To create a Snapshot for a LUN:
t t p
:h
1. Open the Provisioning screen and click the LUN button. This will show all LUN(s) that are
s
created on the storage system.
r c e
ou
2. Select a LUN.
s
3. Click the More menu button and select the Create Snapshot option. This will open the Create
Snapshot wizard.
Re
i n g
NOTE: It is also possible to select the Create Snapshot option by clicking the right mouse button
r n
on the selected LUN.
e a
e L
or
M

Create Snapshot wizard
Enter a Name and

Description.
Optionally click the
e n
Activate Now checkbox.
/
Click OK.
o m
e i .c
aw
u
g .h
ni n
r
lea
In the Create Snapshot Wizard that is displayed a default name for the snapshot is given. This is
//
a combination of the name of the originating LUN (here ThinLUN) and the creation time of the
:
snapshot (150303231945 or March 3rd of 2015 at 23:19:45)
t t p
s :h
In the Create Snapshot wizard, the user can modify the name in the Name text box. In the
c e
Description text box, enter the function and properties of the Disk Domain. The descriptive
r
ou
information helps to identify the Snapshot.
es
R
Optionally check the Activate Now checkbox and click OK to create the Snapshot. In this example
i n g
the Activate Now check box is checked.
r n
a
When the checkbox next to Activate Now is ticked the snapshot is active which means that all
e
L
changes to the original LUN will be recorded. From the point that the snapshot is active additional
e
r
storage capacity should be available to store the copies of the blocks that are changed in the
o
original LUN. That is why a warning message will appear. This is to make you aware of the fact
Mthat there should be enough free capacity available in the storage pool.

Warning message
Read the message.
Tick the checkbox.

e n
/
m
Click OK.
.c o
e i
aw
u
g
Slide 6
.h
ni n
r
lea
After reading the message, tick the checkbox and click OK to confirm that you have read the
message.
: //
t t p
Execution Result
s :h
r c e
s ou
The Execution Result box will display that the operation succeeded.
Re
i n g
r n
e a
e L
or
M

Snapshot tab overview
There can be many snapshots created of a LUN and they can be kept active at the same time. To
find out how many snapshots there are for each LUN we have to go to the Provisioning window
and find the LUN section again.
As soon as snapshots are created the bottom part of the LUN window, provided a LUN is selected,
will show all existing snapshots of that LUN under the Snapshot tab.
e n
/
o m
Snapshot tab overview
e i .c
aw
Look at the created Snapshot.
u
g .h
ni n
r
// lea
p :
t t
:h
The snapshot is active. The snapshot LUN
is not mapped yet.
e s
r c
s ou
Re
i n g
When the LUN is selected, click the Snapshot tab at the bottom part of the LUN window. Because
r n
the snapshot is set to active while creating, you will see that the Running Status is Active. The
e a
Mapping is Unmapped.
e L
or
Before the snapshot can be used for file recovery, you need to map the snapshot to a LUN Group.

Use Snapshot to recover files
Use Snapshot to recover files
Go to the LUN window.
Click the LUN Group tab.
Select a LUN Group.

e n
/
m
Click the Add Object button.
.c o
e i
aw
u
g .h
ni n
r
lea
: //
t t p
There are two ways to recover files using snapshots. One way is to map the snapshot to the
:h
Operating System and the other is to roll back the snapshot. First we are going to recover files by
e
mapping the snapshot to our Operating System.
s
r c
ou
Before we can use a snapshot to recover files, it needs to be added to a LUN Group.
es
R
Go to the Provisioning screen and select the LUN button.

i n g
In the LUN window, click the LUN Group tab. From the list of available LUN groups, select the
r n
LUN Group where the original LUN belongs to.

e a
At the menu bar, click the Add Object button. The Add Object wizard will show.
e L
or
M

Add Object Wizard
Add Object Wizard
Select a Snapshot from the Available Snapshots area and move it to the Selected
Snapshots area.
e n
/
o m
e i .c
aw
u
g .h
ni n
r
lea
: //
t t p
The Add Object wizard will now open. Click the Snapshots tab. The snapshot that was created
:h
earlier will be available in the Available Snapshots area.
e s
r c
Select the snapshot and click the right triangle to move it to the Selected Snapshots area and
ou
click OK.
es
R
The Execution Result box will display that the snapshot is successfully added to the LUN Group.
i n g
r n
In order to recover the files on the snapshot LUN, open the Server Manager.
e a
e L
In the Server Manager expand the Storage menu and click Disk Management.
or
M

Disk Management
Disk Management
Click Action.
select Rescan Disks.
e n
/
o m
e i .c
aw
u
.h
Click the right mouse button and select Online.
i n g
r n
lea
: //
t t p
If there is no new partition available when opening Disk Management, click the Action button at
:h
the top menu bar and select the Rescan Disks option. Now the new partition will show but the
e s
status is Offline. To put it online, click the right mouse button and select Online.
r c
ou
Notice that the partition already has a file system assigned to it. You can recognize this because
es
the partition in disk manager has a blue bar and is a Basic partition. Normally the system
R
automatically assigns a drive letter to the partition making it a volume for use in the operating
i n g
system. Copy the missing files from the new snapshot volume to the original volume.
r n
e a
e L
or
M

Rollback Snapshot
When all the data on the original LUN is destroyed (or corrupted) it is still possible to copy all the
files from the snapshot volume back to the original volume. Especially when there are thousands
of files on the volume this is a very lengthy process. But there is a faster (and easier) way: We
can use the Rollback function to restore a volume to a previous state.
Rollback Snapshot 1
e n
/
o m
.c
Open Disk Management.
Click the right mouse button.
e i
aw
u
Select Offline.
g .h
ni n
r
// lea
p :
t t
s :h
r c e
ou
Before we can roll back the Snapshot we need to take the original partition offline.

es
R
Open the Server Manager and expand the Storage option.

g
Click Disk Management. Select the partition, click the right mouse button and select Offline.
i n
r n
e a
e L
o r
M

Rollback Snapshot 2
1. If the Snapshot is Inactive, click the right mouse button and select Activate.
e n
/
m
2. If the Snapshot is Active, click the right mouse
o
button and select Start Rollback option.
e i .c
aw
u
g
Slide 13
.h
ni n
r
lea
Open the Provisioning screen and select the LUN button to go to the LUN window.

: //
Select the LUN you want to roll back from. At the bottom click the Snapshot tab.

t p
If the Running Status is Inactive, click the right mouse button and select Activate.
t
:h
When the Running Status is Active, click the right mouse button and select the Start Rollback
s
option. This will open the Rollback Snapshot window.
e
r c
ou
NOTE: The Snapshot Running Status must be Active before we can roll back a snapshot.
es
R
i n g
r n
e a
e L
or
M

Rollback Snapshot 3
Select the Rollback Speed.
Click OK.
e n
/
Read the message.
o m
Check the checkbox.
e i .c
Click OK.
aw
u
g .h
ni n
r
lea
The Rollback Snapshot window will open. Take a look at the Rollback Speed.
Choose one of the options that are available.

: //
These options are: Low, Medium, High and Highest.
t t p
:h
Select a Rollback Speed and click OK.
e s
r c
s ou
Re
i n g
r n
e a
e L
o r
M

Rollback Snapshot 4
Check the Running Status.
e n
/
o m
e i .c
aw
u
g .h
ni n
r
lea
: //
t p
The system will now roll back the Snapshot. Take a look at the Running Status. Once this is
t
:h
completed, open Disk Management and set the partition back Online. Take a look at the partition
s
and notice that all files have been recovered.
e
r c
ou
The Rollback function of course is only useful when all files must be/van be replaced with the
s
versions saved in the snapshot. For the restore of individual files, the first method (also referred to
e
R
as side-by-side recovery) must be used.
i n g
r n
e a
e L
or
M

Unmap Snapshot
When the snapshot is no longer needed (the files have been backed up or the restore was
completed) that snapshot can be deleted. These are the steps that need to be taken to do this.
Unmap Snapshot
e n
/
m
Click the right mouse button.
.c o
e i
aw
u
.h
Select Offline.
i n g
r n
// lea
p :
t t
:h
e s
r c
After the missing files are copied to the original partition, the snapshot needs to be unmapped.

s ou
Open Disk Management and select the snapshot partition.

Re
Click the right mouse button and select Offline to take the partition offline.
i n g
r n
e a
e L
o r
M

Remove Object
Remove object
Go to the LUN window.

Click the LUN Group tab.
n
Select a LUN Group.
Click the Remove Object button.
/ e
o m
e i .c
aw
u
g .h
ni n
r
lea
: //
t t p
To completely unmap the snapshot, it needs to be removed from the LUN Group. To remove it
:h
from the LUN Group, go to the Provisioning screen and select LUN. In the LUN window, click the
LUN Group tab.
e s
r c
ou
Select the LUN Group where the snapshot was added. At the menu bar, click the Remove Object
es
button. The Remove Object wizard will appear.
R
i n g
r n
e a
e L
or
M

Remove Object wizard
Select a Snapshot from the Available Snapshots area and move it to the Selected
Snapshots area.
e n
/
o m
e i .c
aw
u
g .h
ni n
r
lea
The Remove Object wizard will now open. Click the Snapshot tab. The snapshot that was added
//
earlier, will be available in the Available Snapshots area. Select the snapshot and click the right
:
triangle to move it to the Selected Snapshots area and click OK.
t t p
s :h
Warning message
r c e
s ou

e
Read the message.
R
i n g
r n
e a
e L Check the checkbox.
or Click OK.
M
A warning message will appear. Read this message. After reading the message, check the
checkbox and click OK to confirm that you have read the message.

A snapshot that is deleted cannot be recovered. If for whatever reason the user temporarily does
not want to keep track of all changes in the original LUN anymore, the option is there to de-
activate the snapshot. At that point the changes will be deleted and no new changes will be
tracked. The snapshot itself will still be visible in the Snapshot tab. It can be activated in a later
stage if needed.
e n
Execution Result
/
o m
Execution Result
e i .c
aw
u
g .h
ni n
r
// lea
p :
t t
s :h
r c e
s ou
Re
i n g
r n
The Execution Result box will display that the snapshot is successfully removed from the LUN
e
Group.
a
e L
or
M

SmartThin
In traditional storage solutions the administrator would create a LUN on the request of one of his
customers. Those customers are his colleagues from departments like Finance, Logistics, HRM
etcetera. The customer requests storage capacity and the administrator would provide that
storage. A problem with this traditional way of working is that the requested storage must be
physically present at the time the LUN is created. At that point there is no user data yet, and
n
maybe it will take the user weeks or months to actually create the user data. All this time the ICT
department has invested in hardware (disks, enclosures) and in additional costs like cooling and
/ e
electrical power. Huawei offers a space efficient version of a traditional LUN called a Thin LUN.
o m
For that the license SmartThin must be purchased.
e i .c
A SmartThin LUN or ThinLUN will be created without allocating physical storage resources to it
aw
u
.h
(or just a very small part for administrative reasons). However to the operating system the
mapped ThinLUN will appear to be the full size. So a ThinLUN of 100 GB initially consumes no
storage capacity until the user writes 100 GB of user data on it.
i n g
r n
// lea
SmartThin
p :
t t
s :h
r c e
s ou

R
Click Create.e

i n g
Enter a Name and Description for the
LUN.
r

n Tick the SmartThin Checkbox.
e a Fill in the Capacity.
eL
Fill in the Initially Allocated Capacity.
or
To create a thin provisioned LUN, open the Provisioning screen and click the LUN button.
Click the Create button. This will open the Create LUN wizard.
In the Create LUN wizard, enter a Name in the Name text box.
In the Description text box, enter the function and properties of the Disk Domain. The
descriptive information helps to identify the LUN.
Check the Enable checkbox for the SmartThin feature to create a thin provisioned LUN.

Fill in the Capacity for the LUN. This is what the size will be for the operating system.
Enter the Initially Allocated Capacity.
Example: When the total capacity is 50 GB and you fill in the Initially Allocated Capacity with
10 GB, the LUN will take just 10 GB on the Storage Pool. This LUN can grow till 50 GB. The
question is maybe why we would allocate physical space at the time creation. The answer is
simple. A Thin LUN can be created that is bigger than the physical available free space in the
OceanStor. Suppose we have 100 GB of free space in the storage pool. We want to create a
500 GB LUN here and immediately store 200 GB of files on it. The creation of the Thin LUN
e n
/
will work as initially we do not need storage capacity. The operating system would then see a
m
volume that can hold 500 GB of files (or so it thinks!). As we start copying 200 GB of files to
the new thin provisioned volume we will eventually run out of physical storage.
.c o
e i
If we would have pre-allocated 200 GB at the creation time in the wizard we would have gotten a
aw
message that 200 GB is not physically there. Probably the SAN administrator would have
u
purchased more disks and enclosures before he would actually create the Thin LUN.
g .h
ni n
r
Next option is: Fill in the Quantity. It is possible to create a maximum of 500 LUNs at the same
lea
time. If the quantity is 5, the system will create 5 LUNs with the same capacity. Select the Owning
Storage Pool where the thin provisioned LUN belongs to.
: //
t t p
:h
The final task is to click the OK button.
e s
r c
Execution Result
o u
es
R
i n g
The Execution Result box will show that the operation succeeded.
arn
e Le
o r
M

The execution result window will then be shown to indicate that the Thin LUN was created
successfully.
In the LUN window we can now track how much of the indicated capacity of a Thin LUN is
actually used with physical allocated storage resources. Below is an example of the properties of
a Thin LUN with a reported size of 5 GB for the capacity. Allocated is 64 MB as this is the
smallest amount we must invest in for a Thin LUN. As data will be written to the Thin LUN in the
future the orange section will expand.
e n
/
o m
e i .c
aw
u
g .h
ni n
r
// lea
p :
t t
s :h
r c e
s ou
Re
i n g
r n
e a
e L
or
M

SmartTier
The SmartTier can leverage two or three storage tiers in a storage pool for data relocation. Data
has a lifecycle. As data processes through its lifecycle, it experiences different levels of activity.
When data is just created, it will usually be used a lot. When data ages, it is accessed less often.
The SmartTier divides the disks into three storage tiers based on their performance levels. Each
storage tier contains only one type of disks and adopts one RAID policy.
e n
Tier Disk Type Application Data
/
o m
.c
High SSDs Applicable to Hot data: data that is promoted to a
performance applications with
i
high-performance tier with significantly
e
w
intensive random improved read performance.
access requests.
u a
Performance SAS Applicable to storage
.h
Warm data: data that can either be
g
applications with
i n
promoted or demoted depending on
n
moderate access
r
the precise workload levels and
lea
requests. configuration.
Capacity NL-SAS Applicable to storage

: // Cold data: data that is demoted to a
t t
applications with light p low-performance tier without any
:h
access requests. application performance reduction.
e s
r c
SmartTier
o u
es
R
i n g
SmartTier requires two or three tiers to be functional.
rn
SmartTier monitors usage level on individual chunks of data.
e a Depending on usage, data is: hot data, warm data or cold data.
e L
or Parameters to consider:
Initial location. Service Monitoring Period.

M Data Migration Speed. Data Migration Plan.
Data Migration Granularity. SmartTier Policy.

If a storage pool only contains one disk type then the SmartTier functionality is not available.
SmartTier does not monitor the usage of complete files, but of parts of a file (extents to be more
precise).
Data (or better extents) can be in three different statuses: hot data, warm data and cold data. It is
Huaweis algorithm that decides when extents are hot, warm or cold. Once that decision is made
the SmartTier function can conclude that extents are not on the appropriate type of disk and
relocate the extent.
e n
/
m
When using SmartTier the following parameters must be considered:
.c o
Initial allocation.
e i
w
This is a setting when creating a LUN. The default allocation is to use all available tiers when
a
u
new data is written to the LUN. Optionally one can decide to have new data written to a
.h
specific tier. For instance: if a lot of static data (images, audio files) must be written it is
g
i n
maybe an idea to force the data directly to the capacity tier as this is the location where it
n
r
would end up eventually anyway. This means no high performance space will be used for
lea
these static files.
: //
Data Migration Speed.
t t p
:h
Relocating extents has a little bit of impact on the system. Optionally the data migration speed
s
can be changed to a lower priority to even further minimize the impact.
e
r c
ou
Data Migration Granularity.
es
Here the size of the extents that will be monitored and relocated can be changed.
R

n g
Service Monitoring Period.
i
n
A setting that will tell the system at what times of the week or day the monitoring of the usage
r
a
of the extents should be done. It can help determine busy or quiet periods in the system.
e
e L

o rData Migration Plan.

The option is here to have a manual relocation/migration or to use the best time that the
M Service Monitoring Period has found.
SmartTier Policy.
This parameter is set on individual LUNs and must be set to enable. Per default the setting is
disabled which means no data relocation will take place.
The settings are: Automatic, Highest, Lowest and No relocation. The settings determine what
the preferences for the migration will be.

SmartTier Stages
SmartTier Stages
I/O monitoring module identifies

I/O monitoring
I/O activities on each data block.
e n
/
The data placement analysis module
o m
.c
Data placement analysis
i
indentifies between hot data and cold data.
we
The data relocation module relocates data
u a
.h
Data relocation
g
amongst tiers.
ni n
r
lea
: //
t t p
The above picture shows the three stages of the SmartTier process. The I/O monitoring can be
:h
configured using the Service Monitoring Period. That results in the identification of hot, warm and
e s
cold extents that then can be moved.
r c
o u Relocation
s
SmartTier Data
Re
i n g Initial allocation in
the storage pool
After data
relocation
arn
L e High Performance
r e
o
M Performance
Capacity

Remember that, although three separate tiers are indicated in the above picture, all capacity is
within the storage pool and user data typically is stored across all disks of the disk domain.
When the SmartTier license is purchased, the user will unlock the storage tiering feature in the
Huawei OceanStor V3 storage system. There is a maximum of three tiers per disk domain. Solid
State Disk will form the High-Performance Tier, SAS disks (both 10k and 15k RPM) will be in the
Performance Tier. Last the third tier called Capacity Tier will be containing NL-SAS disks (7200
RPM).
e n
/
m
LUNs are created in storage pools and that is the place to set up SmartTier. For that we go to the
Provisioning window and select to configure the Storage Pool.
.c o
e i
aw
SmartTier
u
g .h
ni n
r
// lea
p :
Create new Storage Pool.
t t
:h
Fill in a Name and Description.
Set Usage type.
e s
Select Disk Domain.
r c
ou
Select at least two tiers in the Storage
s
Medium section and enter capacity
e
and RAID policy.

R
Click Set SmartTier Policy.
i n g
r n
e a
L
To use the SmartTier feature, we create a new Storage Pool.
e
or
To create a Storage Pool, open the Provisioning screen and click the Storage Pool button. Click
Mthe Create button. This will open the Create Storage Pool wizard.
In the Create Storage Pool wizard enter a Name in the Name text box. In the Description text box,
enter the function and properties of the Disk Domain. The Usage type is set to Block Storage
Service. It is also possible to select File Storage Service. Select the Disk Domain where the
Storage Pool needs to be created. This Storage Pool needs at least two types of Storage Media
for the SmartTier feature to work. Select the available storage types, set the RAID Policy and fill in
the capacity of each storage type. Click the Set SmartTier Policy button.

Set SmartTier Policy
Set SmartTier Policy
Optionally set the Service Monitoring
n
Period.
/ e
o m
Set the Data Migration Plan.
e i .c
aw
u
g .h
ni n
r
lea
: //
t t p
In the Set SmartTier Policy menu, it is possible to enable the Service Monitoring Period. This
:h
feature forces the system to monitors hotspot data only within the set time period. These results
e s
can serve as reference for migration between storage tiers.
r c
ou
Set the Data Migration Plan to Manual or Periodical and click OK. In the Create Storage Pool
wizard click OK.
es
R
i n g
r n
e a
e L
or
M

Execution Result
The Execution Result box will show that the operation succeeded.
e n
/
o m
e i .c
aw
u
g .h
ni n
r
lea
The Storage Pool is successfully created. The next step is to create a new LUN in the Storage
Pool.
: //
t t p
:h
In the LUN window, click the Create button to start the Create LUN wizard.
e s
Create LUN wizard
r c
s ou
Re
i n g
r n
e a
eL
Enter a Name and Description for
or
the LUN.
Fill in the Capacity.
M

Click the Advanced button.
Enter a Name and Description for the LUN.

In the Name text box, enter a name for the LUN.

In the Description text box, enter the function and properties of the LUN. The descriptive
information helps to identify the LUN.
Optional If the SmartThin licensed feature is purchased, it is possible to create thin

provisioned LUNs. To enable this feature, check the Enable checkbox. When the SmartThin
feature is enabled, the Create LUN wizard will show an option called Initially Allocated
Capacity. Example: When the total capacity is 50 GB and you fill in the Initially Allocated
Capacity with 10 GB, the LUN will take just 10 GB on the Storage Pool. This LUN can grow
e n
/
until it reaches 50 GB.
o m
.c
Fill in the Capacity for the LUN.

e i
In the dropdown box, select one of the following options: Blocks, MB, GB and TB.
aw

u
It is possible to create a maximum of 500 LUNs at the same time. If the quantity is 5, the
system will create 5 LUNs with the same capacity.
g .h

i n
Select a Owning Storage Pool from the dropdown list. The LUN will be created in the
n
Storage Pool that is selected.
r
lea
Set the advanced properties for the LUN by clicking the Advanced button.
: //
t t p
s :h
r c e
s ou
Re
i n g
r n
e a
e L
or
M

Create LUN - Advanced Settings
Click the Tuning tab.
Set SmartTier Policy.
e n
/
o m
e i .c
aw
u
g .h
ni n
r
lea
Click the Tuning tab and choose the SmartTier Policy in the SmartTier area. In this example
we choose the option Relocate to low-performance tier.
: //

t p
Finish the Create LUN wizard, map the LUN to the Operating System and add some data to it.
t
Example:
s :h
r c e
In this example we chose Relocate to the low-performance tier. When creating a LUN the option
ou
is also available to select the Initial Capacity Allocation Policy. That is the way you define where
es
the new data written to a LUN will be stored. Default setting is Automatic which means that data
R
will be distributed across all available disk types i.e tiers. When the SmartTier Policy is scheduled,
i n g
and the data is not used very often, it will automatically relocate that data to the slower storage
r n
tier to save space in the high performance tier.
e a
e L
o r
M

Storage Pool Properties
It is possible to change SmartTier settings for the Storage Pool. Go to the Provisioning screen
and select the Storage Pool button. In the Storage Pool window, select the storage pool and click
the Properties button.
e n
/
o m
e i .c
aw
u
Click the SmartTier Policy tab.
g .h
ni n
r
// lea
p :
t t
:h
e s
c
The Storage Pool properties window will open.
r
ou
Click the SmartTier Policy tab. It is possible to set the Cache Mode, Service Monitoring Period
and Data Migration Plan.
es

R
Change the settings based on your service needs and click Apply, followed by clicking OK.

n g
The Execution Result window will appear showing that the changes were made successfully.
i
r n
e a
e L
or
M

Execution Result
e n
/
o m
e i .c
aw
u
g .h
ni n
r
lea
SmartTier Monitoring
: //
t t p
:h
SmartTier Monitoring
e s
r c
ou
Click the LUN.
s
Click the Properties button.
Re
i n g
r n
e a
e L
or
M
It is possible to monitor the SmartTier process. Go to the Provisioning screen and click the LUN
button. In the LUN window, select the LUN that has the SmartTier function enabled and click the
Properties button.

LUN Properties
LUN Properties
Click the SmartTier tab.
e n
/
o m
e i .c
aw
u
g .h
ni n
r
lea
: //
t t p
When the Properties window is opened, click the SmartTier tab. It is possible to select a
:h
SmartTier Policy. In this example we choose the Relocation to low-performance tier. You can
e s
monitor the Capacity Distribution between the storage tiers.
r c
ou
NOTE: This percentage will not update automatically. In the next slide we will show a live view
between two storage tiers
es
R
i n g
r n
e a
e L
or
M

Click the SmartTier

Status tab.
e n
/
o m
e i .c
aw
u
g .h
ni n
r
lea
: //
t t p
It is possible to get a live view of the SmartTier feature. Open the Provisioning screen and click
:h
the Storage Pool button. In the Storage Pool window, select the Storage Pool where the LUN
e s
belongs to. Click the Properties button. When the Storage Pool properties window is opened, click
r c
the SmartTier Status tab. In the Status area, you can monitor the following information:
Feature Status:
s ou
Re
Should be Active, otherwise the data will not move between the available storage tiers.

i n
Migration Status: g
r n
a
When it is relocating, it shows Relocating.
L e
e
To Be Moved Up:
o rThe amount of data that will move from a lower storage tier to a higher storage tier. For
M example from SAS disks to SSDs.
To Be Moved Down:
The amount of data that will move from a higher storage tier to a lower storage tier. For
example from SSDs to SAS disks.
Estimated Duration: Is the time before the data migration is completed.
In the Storage Tier Information area, you will see that the amount of data will grow at the other
storage tier.

HyperClone
HyperClone
n
To create an Splitting Automatically
e
available copy splitting the pair
/
after reverse
To restore synchronization
m
To update
data on the
the copy
o
primary LUN
Clone creation Synchronization

Reverse
synchronization
e i .c
aw
u
g .h
ni n
r
lea
: //
t t p
The clone feature allows you to obtain full copies of LUNs without interrupting host services.
:h
These copies apply to scenarios such as data backup and restoration, application testing, and
data analysis.
e s
r c
ou
Synchronization: Data is copied from the primary LUN to a secondary LUN. Then dual write is
es
performed to the primary LUN and secondary LUN.
R
i n g
r n
e a
e L
or
M

Synchronization
Synchronization
Dual Write
Synchronization
After the Synchronization
Primary LUN Secondary LUN
n
A A
e
B B
/
m
Case 1: Full copy performed in the initial Writing data D
o
synchronization to replace data A
Primary LUN
A
Secondary LUN
A
Primary LUN
D
Secondary LUN
D
e i .c
w
B B B B
a
C C C C
u
.h
Case 2: Incremental copy performed in the In a data write scenario, the same data is written
synchronization after a split to both primary and secondary LUNs (dual write)
A
A
B
B
C
C D
Data already stored
Data to be stored
i n
Host signal flow g
Internal signal flow in the storage system
r n
lea
: //
t p
Synchronization: Data is copied from the primary LUN to a secondary LUN. Then dual write is
t
:h
performed to the primary LUN and secondary LUN.
e s
Split
r c
s ou
Split Re
i n g
r n Splitting a Pair
Independent Use
a
of the Secondary LUN
L e Primary LUN Secondary LUN Primary LUN Secondary LUN
r e X A
B X A
B
o After a pair is split, dual write is no longer imple-
M
mented, and the secondary LUN stores a copy of The Secondary LUN can be accessed independently
all data on the Primary LUN at the time when the without affecting the Primary LUN.
pair was split.

Clone 1
A A
Clone 2 B X B
C DCL
Clone 3
Subsequent data changes made to the primary and second

Multiple pairs can be split in batches as long as LUNs are recorded by the DCL for incremental copy per-
each pair belongs to a unique clone. formed in later synchronization or reverse synchronization.
A B C Data already stored Internal signal flow in the storage system

DCL Data Change Log Host signal flow

Splitting: After a synchronization is complete, the pair can be split at a certain point in time. Then,
the secondary LUN becomes an available copy of the primary LUN and stores all the data on the
primary LUN at the time when the pair was split. After a pair is split, the secondary LUN is
accessible to hosts, allowing hosts to access data identical to that on the primary LUN at the
splitting time point without affecting the performance of the primary LUN. After a pair is split, a
synchronization or reverse synchronization can be performed again between the primary LUN
and the secondary LUN.
e n
/
o m
.c
Reverse Synchronization
e i
aw
u
.h
Reverse Synchronization (1)
i n g
n
r
1 Other pairs are automatically
lea
Another
Primary LUN Secundary LUN split if any exist.
//
1
A A
B
C
B
C
p :
t t
:h
2
s
Secundary LUN
e
3 A
c
B
r C
s ou
A B
R
C
e Data already stored Internal signal flow in the storage system
g
C Data to be stored Host signal flow
n i n
ar
L e
r e
o
M

Reverse Synchronization (2a)
Host I/O Processing During the

Case 1: If the data block to be accessed has been reverse synchronized split if any exist.
2 Reverse synchronization is
A A executed for the selected pair
B B
C C
(Incremental copy).
The Primary LUN is directly accessed.
e n
/
o m
e i .c
A B C Data already stored
aw
u
g
Slide 40
.h
ni n
r
Reverse Synchronization (2b)
// lea
p :
t t
:h
Host I/O Processing During the
es
Case 2: If the data block to be accessed is not reverse synchronized split if any exist.
Primary LUN
r c Secondary LUN 2 Reverse synchronization is
ou
A A executed for the selected pair
B 2 B 1 (Incremental copy).
s
C C
Re
In terms of a read request, reverse synchronization is completed
after the secondary LUN is read.
ing
A A
rn
2 B 1 B
C C
e a In terms of a write request, reverse synchronization is completed

before new data is written to the primary LUN.
eL
A B C Data already stored Internal signal flow in the storage system
or
M

Reverse Synchronization (3)
Another 1 Other pairs are automatically

Primary LUN Secundary LUN split if any exist.
1
A A 2 Reverse synchronization is
B B
executed for the selected pair
C C
(Incremental copy).
2 3 After the reverse
e n
/
Secundary LUN synchronization is complete,
the pair is automatically split.
m
3 A
o
B
.c
C
e i
A B C Data already stored
aw
u
gSlide 42
.h
ni n
r
lea
Reverse synchronization: To restore data on the primary LUN, a reverse synchronization to
//
copy data from the secondary LUN to the primary LUN can be executed. After the reverse
:
synchronization is complete, the pair is automatically split.
t t p
s :h
During a synchronization or reverse synchronization, hosts are still allowed to access the primary
LUN, ensuring service continuity.
r c e
s ou
Re
i n g
r n
e a
e L
or
M

HyperReplication: Synchronous mode
Replication is a feature associated with disaster recovery. Making backups is sometimes not
enough when the requirements are higher. For instance when identical copies of the data should
exist in a remote site. Also replication is an option when restore times are minutes and not hours
like with traditional tape backups.
Replication has the goal to have a standby copy of the data ready to be used in case of a serious
e n
disaster. Examples of such disaster would be fires, floodings or earthquakes.
/
o m
Two types of replication exist: Synchronous and Asynchronous mode.
e i .c
aw
u
.h
HyperReplication Synchronous mode
i n g
r n
lea
1
//
2
p :
5
t t 3
:h
es
4
r c
1
s ou
I/O from host stored at site A. 4 Acknowledgment across link.
2
3
Re
Data across intersite link to site B.
Data stored on site B.

5 Host receives message : I/O complete.
i n g
n
ar
L e
A synchronous remote replication session replicates data in real time from the primary storage
r e
o
system to the secondary storage system. The characteristics of synchronous remote replication
M
are as follows:
- After receiving a write I/O request from a host, the primary storage system sends the request
to the primary and secondary LUNs.
- The data write result is returned to the host only after the data is written to both primary and
secondary LUNs. However, if data fails to be written to the secondary LUN, the secondary
LUN returns a message indicating data write failure to the primary LUN. The controller

changes the dual-write mode to the single write mode at the same time. The remote
replication task enters the abnormal state.
After a synchronous remote replication pair relationship is set up between the primary LUN and
the secondary LUN, a manually triggered synchronization needs to be performed so that the two
LUNs have consistent data. Every time a host writes data to the storage system after the
synchronization, the data is copied from the primary LUN to the secondary LUN in real time.
e n
/
o m
.c
HyperReplication: Asynchronous mode
e i
aw
u
.h
HyperReplication Asynchronous mode
i n g
r n
lea
1
//
3
p :
2
t t 4
:h
es
5
r c
1
s ou
I/O from host stored at site A. 4 Data stored at remote site.
Re
Host receives message : I/O complete. 5 Acknowledgment across link.
g
3 Data via link to site B.
n i n
ar
L e
An asynchronous remote replication session periodically replicates data from the primary
r e
o
storage system to the secondary storage system. The characteristics of asynchronous remote
M
replication are as follows:
- Asynchronous remote replication relies on the snapshot technology. A snapshot is a point-in-

time copy of source data.
- When a host writes data to a primary LUN, the primary storage system returns a response
indicating a successful write to the host, as soon as the primary LUN returns a response
indicating a successful write.
- Data synchronization is triggered by a user manually or by the system periodically to keep

data consistent between the primary LUN and the secondary LUN.

After an asynchronous remote replication relationship is set up between a primary LUN and a
secondary LUN, initial synchronization is performed where all of the data from the primary LUN is
copied to the secondary LUN so that the two LUNs have consistent data. After the initial
synchronization is complete, the storage system processes host writes as follows:
When receiving a host write, the primary storage system sends the data to the primary LUN. As
soon as the primary LUN returns a response indicating a successful write, the primary storage
system returns a response indicating a successful write to the host. At the scheduled
synchronization time, new data on the primary LUN is copied to the secondary LUN.
e n
/
o m
.c
In the situation where the primary site is destroyed the administrator should initiate a failover. This
e i
essentially means that the replicated LUNs on the remote site will be activated. At that point hosts
w
on the remote site can pick up on the data again and business can be continued. Of course the
a
u
host at the remote site must be running the same applications as the local hosts did.
g .h
ni n
r
// lea
p :
t t
s :h
r c e
s ou
Re
i n g
r n
e a
e L
or
M

Firmware Updates
With almost all products Huawei will add new features and/or improve the current features. This is
done using so-called firmware updates. In most cases this is a process that is guided by a Huawei
engineer or by the Huawei support team.
The process itself is almost fully automated and to perform a firmware upgrade two things are
needed:
n
1. The OceanStor Toolkit.
2. The actual new firmware. / e

o m
.c
In the next section we will briefly explain the procedure. Here we assume that the OceanStor
Toolkit is available and the firmware is accessible. Firmware is a special file that can be
e i
downloaded from the support site. The format of the firmware file is often a file with the
aw
extension .TGZ. This is a Linux based compressed file. (TGZ=Tar Gzipped File). For some
u
products it is not even necessary to physically download the firmware file as the upgrade process
g .h
will download and install it as part of the upgrade.
ni n
r
lea
The first step is to start the OceanStor Toolkit.
: //
Firmware updates
t t p
s :h
e
Open the OceanStor Toolkit.

r c
Click the ToolCase tab.
ou
Click Upgrade from the left menu.
es
Click the Upgrade button.
R
i n g
r n
e a
e L
or
Once the OceanStor Toolkit is started, we need to download the Upgrade software features from
the ToolStore. Once these are installed, go back to the ToolCase tab. In the left hand menu click
Upgrade. At the right hand side, an Upgrade button will show. Click the Upgrade button. The
Upgrade page will open.

Upgrade page
Click the Add Device button.
e n
/
o m
e i .c
aw
u
g .h
ni n
r
lea
On the Upgrade page, we need to add the device. To do that, click the Add Device button. This
will open the add device wizard.
: //
t t p
Add device wizard (1)
s :h
r c e

s ou
Click on the Add Device text link.
Re
i n g
r n
e a
e L
or
M
The add device wizard is opened. In this example there is no device available. Read the text and
click the highlighted Add Device text.

Fill in the IP address.
e n
/
o m
e i .c
aw
u
Click Next.
g
Slide 48
.h
ni n
r
lea
Enter the IP address of the device that you want to add. Note that it is also possible to specify an
//
IP segment and to select a proxy. Once the IP address is added, click the Next. In the next screen
:
we need to add some additional login information.
t t p
s :h
r c e
s ou

e
Enter the Username.
R
g
Enter the Password.
n i

n Fill in the Port number.
ar
L e
r e
o
M
In this window we need to add the login information for the storage device. Fill in the Username,
Password and Port number. Click Finish.

The device is successfully added.
Select the array.
e n
/
o m
e i .c
aw
u
g .h
ni n
r
lea
The storage device is now successfully added. Now we can choose an array that we want to
//
upgrade. Select the checkbox that is located in front of the device model and click Next.
:
t t p
s :h
r c e

s ou
In Select Upgrade Package, click Browse.
Re
i n g
r n
e a
e L
or
M
We need to configure the Upgrade Settings. First we click the Browse button in the Select
Upgrade Package area. The upgrade package has a .tgz file extension and is downloadable from
the Huawei support website.

Choose a backup path.
Click Browse.
e n
/
o m
e i .c
aw
u
g
Slide 52
.h
ni n
r
lea
Select a Backup data path. Click the Browse button. Once the correct backup location is selected,
click the Save button.
: //
t t p
Add device wizard (7): h
e s
r c

o u
s
Select the Upgrade Mode.
Re
i n g
arn
L e
r e
o
M
After selecting the upgrade package and data backup path, we need to select an upgrade mode.
It is possible to do the upgrade while the system is online, but also to do the upgrade offline.

Online upgrade
Online upgrade features high reliability and availability without service interruption. It is applicable
to the scenario where services cannot be interrupted. Before starting an online upgrade, ensure
that the upgrade package supports online upgrade from the current version to the target version.
During an online upgrade, the controllers are upgraded in sequence. In the dual-controller
scenario, the secondary controller is upgraded first, and then the primary controller is upgraded.
In the multi-controller scenario, one controller (experimental controller) is upgraded first. Then, all
the controllers (excluding the experimental controller) on the peer plane of the primary controller
e n
/
m
are upgraded. After that, all controllers (excluding the experimental controller) on the plane where
the primary controller resides are upgraded. Before controllers on one plane are upgraded, the
.c o
system switches services from these controllers to the controllers on the peer plane, and then the
e i
system automatically detects firmware to be upgraded and upgrades it. After these controllers are
aw
u
upgraded, the system restarts them. After they are powered on, services that belong to them are
switched back to them. Then, the system upgrades the controllers on the other plane in the same
g .h
way.
ni n
r
lea
Offline upgrade
: //
t p
Offline upgrade requires users to stop host applications before upgrading controller software.
t
:h
During an offline upgrade, the primary and secondary controllers are upgraded simultaneously.
s
Therefore, the upgrade period is much shorter. Because all host services are stopped before the
e
c
upgrade, data loss and service interruption risks are reduced during the upgrade.
r
s ou
Re
i n g
r
n Tick the Enable professional mode checkbox.
e a
e L
or
M

In this example we choose to enable the professional mode. Check the checkbox and click the
Finish button.
In the Professional Mode, if a node fails to be upgraded, the cluster upgrade is suspended. Then
the operators have three options: Roll back, Retry, and Continue. After the upgrade is
suspended, Huawei R&D engineers need to locate the causes of the upgrade failure. Then R&D
engineers instruct operators to roll back the upgrade, perform the upgrade again or ignore the
node upgrade failure.
e n
/
o m
.c
Upgrade page
e i
Select the storage array.
aw
u
.h
Click the Perform Upgrade button.
Check the checkbox and click OK.
i n g
r n
// lea
p :
t t
s :h
r c e
s ou
Re
i n g
Select the storage array that needs to be updated. Check the checkbox in front of the device
n
name. Once the storage array is selected, click the Perform Upgrade button. The Upgrade
ar
Confirm window will show. Check the settings and check the checkbox that youve read the
L e
previous information and understood the consequences of the operation. Click OK. The upgrade
r eprocess will now start.
o
M

Upgrade process (1)
Monitor the Upgrade Package Import process.
e n
/
o m
e i .c
aw
u
g .h
ni n
r
lea
The system will now automatically import the upgrade package. You can monitor the process at
//
the bottom part of the screen. When a step is completed the system will automatically go to the
:
t p
other tab. The progress bar at the top will finally show 5 green dots when the upgrade process is
t
:h
completed.
e s
Upgrade process (2)c
u r
s o

Re
Monitor the Pre-Upgrade Check.
i n g
arn
L e
r e
o
M
After the upgrade package is imported, the system automatically starts to perform a pre-upgrade
check.

Upgrade process (3)
Monitor the Data Backup process.
e n
/
o m
e i .c
aw
u
g
Slide 58
.h
ni n
r
lea
The system will now back up the controller data.
: //
t t p
:h
Upgrade process (4)
e s

r c
ou
Monitor the Upgrade process.
es
R
i n g
r n
e a
e L
or
M
The system is now executing the upgrade process.

Upgrade process (5)
Monitor the Post-Upgrade Verification.
e n
/
o m
e i .c
aw
u
g .h
ni n
r
Upgrade process (6)
// lea
p :
t t
:h
Monitor that the upgrade process has succeeded.
e s
r c
s ou
Re
i n g
r n
e a
e L
or
M
Take a look at the progress bar and notice that there are five green dots showing that the status is
succeeded.

Questions
Questions
1. Explain the difference between a snapshot and a clone.
n
2. What two methods can be used to restore data using a
snapshot?
/ e
3. How much storage capacity is consumed when a Thin LUN of
o m
.c
500 GB is created?
4. Name the three stages of the SmartTier process.

e i
5. Describe what is meant with synchronous replication.
aw
u
g .h
ni n
r
lea
: //
Answers:
t t p
:h
1. Snapshots initially do not consume space. Snapshot size is equal to the number of changed
s
r c e
blocks. Clones are identical copies of a LUN and consume just as much space.
s ou
2. Method one is side-by-side recovery: a mapping view of the snapshot LUN is created for the
e
host that sees the original LUN. Data can then be copied on the operating system level.
R
g
Method two is the Rollback function. Here the volume is almost instantly restored to the state
i n
of the snapshot LUN.
n
ar
e
3. At creation time a single block of 64 MB is created for administrative purposes. If we ignore
eL
that small amount then a Thin LUN does not consume space until user data is written.
or
M 4. Stage 1: I/O monitoring Stage 2: Data Placement Analysis Stage 3: Data relocation.
5. Synchronous replication: the host first writes to its local LUN. This will be stored in the local
OceanStor. No confirmation of the write will be given. The second step is to copy the written
data to the remote site. There the data will be stored. A confirmation will be sent from the
remote OceanStor to the local OceanStor. Then, finally, will the host receive an
acknowledgement of the write.

Exam Preparation
1. Which of the licensed features can be described as: the, almost

instant, creation of a full copy of an active LUN without impacting
the access to the active LUN?
e n
a. HyperSnap.
/
b. HyperMirror.
o m
c. HyperClone.
e i .c
d. HyperReplication.
aw
u
g .h
ni n
r
lea
: //
t t p
Exam preparation (2) h
s :
r c e
u
2. Which of the following statements about the SmartTier feature is
o
s
true? (check all that apply)
a.
Re
Saves space in the disk domain.
i n
b.
g Lowers the cost of storing aged data.
r n c. Data relocating data is a heavy burden on the system and should
e a only be executed in quiet time of the system.
eL
d. SmartTier needs all three tiers to be filled with disks.
or
e. SmartTier works on individual LUNs.
M
Answers:
1. C.
2. B, E.

Summary
Summary
HyperSnap is the Copy-On-Write snapshot implementation.

HyperClone is the instant creation of a synchronize full copy of a
LUN.
e n
/
m
SmartTier is the feature that relocates extents from disks in a tier
o
to disks of another tier. Goal is to store extents on appropriate
.c
disk types .
HyperThin creates LUNs that only consume space when actual
e i
user data is written to it.
aw
HyperReplication is offered in synchronous and asynchronous
u
.h
modes and is a disaster recovery feature that offers a near-
identical copy of a LUN on a remote OceanStor.
i n g
r n
lea
: //
t t p
s :h
r c e
s ou
Re
i n g
r n
e a
e L
or
M

Thank you
www.huawei.com
e n
/
o m
e i .c
aw
u
g .h
ni n
r
// lea
p :
t t
s :h
r c e
s ou
Re
i n g
r n
e a
e L
or
M

The privilege of HCNA/HCNP/HCIE:
With any Huawei Career Certification, you have the privilege on http://learning.huawei.com/en to enjoy:
n
1e-Learning Courses Logon http://learning.huawei.com/en and enter Huawei Training/e-Learning
/e

o m
If you have the HCNA/HCNP certificateYou can access Huawei Career Certification and Basic Technology e-Learning
courses.
e i .c
If you have the HCIE certificate: You can access all the e-Learning courses which marked for HCIE Certification Users.
aw

Methods to get the HCIE e-Learning privilege : Please associate HCIE certificate information with your Huawei account, and
hu

email the account to Learning@huawei.com to apply for HCIE e-Learning privilege.

g .
2 Training Material Download
i n

arn
Content: Huawei product training material and Huawei career certification training material.

//le
MethodLogon http://learning.huawei.com/en and enter Huawei Training/Classroom Training ,then you can download
training material in the specific training introduction page.
p :
3 Priority to participate in Huawei Online Open Class (LVC)
t t

s :h
The Huawei career certification training and product training covering all ICT technical domains like R&S, UC&C, Security,
4Learning Tools: rc e
Storage and so on, which are conducted by Huawei professional instructors.
s o
eNSP Simulate single Router&Switch device and large network.

R e
WLAN Planner Network planning tools for WLAN AP products.
n g
In addition, Huawei has built up Huawei Technical Forum which allows candidates to discuss technical issues with Huawei experts ,
ni
share exam experiences with others or be acquainted with Huawei Products.
a r
Statement:
L e
r e
This material is for personal use only, and can not be used by any individual or organization for any commercial purposes.
o
M
HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 1

HCNA-Storage V3 BSSN Building The Structure of Storage Network Training Material

Uploaded by

Document Information

Original Title

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

HCNA-Storage V3 BSSN Building The Structure of Storage Network Training Material

Uploaded by

Copyright:

Available Formats

The privilege of HCNA/HCNP/HCIE:

email the account to Learning@huawei.com to apply for HCIE e-Learning privilege.

Copyright Huawei Technologies Co., Ltd. 2015. All rights reserved.

Trademarks and Permissions

Huawei Certification System

Readers Knowledge Background

Know server fundamental and application.

Know SAN, NAS, DR concepts and technology.

Understand mainstream OS and DB operation and management .

Icons Used in This Book

Account for Experiment environment

Experiment network introduce

The experiment environment aims to provide guidance to participants in learning contents

Module 1: Data Management

HCNA V3 | Table of Contents Page | 3

Page | 4 HCNA V3 | Table of Contents

Module 8: Cloud Computing

o Cabling Diagrams 360

M Huawei Licensed Software Features

HCNA V3 | Table of Contents Page | 5

Page | 6 HCNA V3 | Table of Contents

HCNA-storage V3 | OHC1109101 Data Management Introduction Page | 9

Page | 10 HCNA-storage V3 | OHC1109101 Data Management Introduction

SNIA definition: Data is the digital representation of anything in

A company needs/creates a large amount of data to run its

es web design, software.

e a marketing, management, IT staff.

HCNA-storage V3 | OHC1109101 Data Management Introduction Page | 11

arn Information can :

L e provide a company with marketing information and customer behavior.

r e help to run the business more effectively.

o help to determine risk factors.

Copyright 2015 Huawei Technologies., Ltd. All rights reserved. Slide 7

Page | 12 HCNA-storage V3 | OHC1109101 Data Management Introduction

HCNA-storage V3 | OHC1109101 Data Management Introduction Page | 13

Where is the data?

Page | 14 HCNA-storage V3 | OHC1109101 Data Management Introduction

HCNA-storage V3 | OHC1109101 Data Management Introduction Page | 15

Page | 16 HCNA-storage V3 | OHC1109101 Data Management Introduction

Information Life Cycle Management

a. What data is needed for every person in the organization ?

HCNA-storage V3 | OHC1109101 Data Management Introduction Page | 17

Information Life Cycle Management

What is the format in which data should be available for the

1. For physical parameters.

Copyright 2015 Huawei Technologies., Ltd. All rights reserved. Slide 13

Page | 18 HCNA-storage V3 | OHC1109101 Data Management Introduction

We typically identify three types of files:

r esize that deletes image information and is therefore not lossless.

HCNA-storage V3 | OHC1109101 Data Management Introduction Page | 19

Page | 20 HCNA-storage V3 | OHC1109101 Data Management Introduction

HCNA-storage V3 | OHC1109101 Data Management Introduction Page | 21

Information Life Cycle Management

What are the retention periods?

Mstored data survive?.

Page | 22 HCNA-storage V3 | OHC1109101 Data Management Introduction

Information Life Cycle Management

How to remove obsolete information?

Who is responsible for data ?

HCNA-storage V3 | OHC1109101 Data Management Introduction Page | 23

Definition according to the SNIA organization:

Applies to physical and operational procedures.

Page | 24 HCNA-storage V3 | OHC1109101 Data Management Introduction