OceanStor Dorado 6.1.x SmartMove Feature Guide
OceanStor Dorado 6.1.x SmartMove Feature Guide
6.1.x
Issue 01
Date 2023-10-31
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and
the customer. All or part of the products, services and features described in this document may not be
within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,
information, and recommendations in this document are provided "AS IS" without warranties, guarantees
or representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Website: https://e.huawei.com
Vulnerability
Huawei's regulations on product vulnerability management are subject to "Vul. Response Process". For
details about the policy, see the following website:https://www.huawei.com/en/psirt/vul-response-process
For enterprise customers who need to obtain vulnerability information, visit:https://
securitybulletin.huawei.com/enterprise/en/security-advisory
Purpose
This document describes the SmartMove feature provided by storage systems in
terms of working principles, application scenarios, configuration examples, and
management operations.
The following table lists the product models that support the SmartMove feature.
NOTICE
This document is updated periodically with the software version. The operations
described in this document use the latest version as an example. Note that the
supported functions and features vary according to the software version. The
content in this document is for reference only.
Intended Audience
This document is intended for:
● Technical support engineers
● Maintenance engineers
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
Change History
Changes between document issues are cumulative. The latest document issue
contains all the changes made in earlier issues.
Issue 01 (2023-10-31)
This issue is the first official release.
Contents
C Glossary................................................................................................................................... 34
1 Feature Description
SmartMove migrates the source file system to a specified storage pool without
interrupting host services. In this way, service data can be properly allocated and
service performance can be improved. This chapter provides an overview of the
SmartMove feature and explains its license requirements and specifications,
working principle, impact and restrictions, and application scenarios.
1.1 Overview
1.2 License Requirements and Specifications
1.3 Working Principle
1.4 Impact and Restrictions
1.5 Application Scenarios
1.1 Overview
This section describes the background, definition, and benefits of SmartMove.
Background
In production environments, the storage pool to which a file system belongs may
experience insufficient capacity, low performance, or imbalanced controller load
issues. If such issues occur, the file system needs to be migrated to a storage pool
with a larger capacity, better performance, or light-load controllers. In this case,
SmartMove can be used to migrate file system data within a storage array without
interrupting services.
Definition
SmartMove developed by Huawei is also called intelligent file system migration. It
is a key technology for service migration, achieving data migration within a
storage system (of the vStore) without interrupting host services.
Benefits
Table 1-1 describes the benefits of SmartMove.
License Requirements
SmartMove requires a license.
Specifications
The specifications of SmartMove vary with products. For detailed specifications,
refer to the Specifications Query (https://info.support.huawei.com/storage/
spec/#/home).
Related Concepts
● Source file system
File system from which service data is migrated.
● Target file system
File system to which service data is migrated, that is, temporary file system
used during migration.
● Global volume
A temporary volume created during data synchronization. It is used to
perform dual-write on the source file system and target file system.
Working Principle
Based on the file system data synchronization technology, data and configurations
of different file systems in a storage system can be synchronized. After the
synchronization is complete, the source and target file systems exchange their
mapped data volumes but retain their attributes to hosts. The physical locations of
the source and target file systems are changed but their logical locations remain
unchanged after migration.
Host Host
● Initial synchronization
After service data synchronization starts on the source file system, all initial
service data is copied to the target file system, as shown in Figure 1-2.
A B C
D E F
A B C G H I A B C
D E F D E F
G H I Full data copy G H I
Global volume
I/O processing
Source Target
file file
Before mapped system system The host identifies
object exchange 1 the source file
Source data Target data system using the
File system volume ID File system volume ID source file system
ID ID ID. The file system
0 0 1 1
ID maps the data
volume ID.
Source Target
file file Source and target
During mapped system system data volume IDs are
object exchange 2 exchanged. The
Source data Target data
File system volume ID File system physical space of
volume ID
ID ID the source file
0 1 1 0 system becomes the
target data volum.
Data volume ID
exchange
Application Restrictions
● Before configuring SmartMove, ensure that the audit log function is disabled
for the vStore to which the file system belongs.
● If the source file system is configured with a clone file system and SmartMove
needs to be configured, split the clone file system first.
● During information exchange of SmartMove, creating or deleting dtrees or
snapshots of the source file system is not allowed.
This chapter describes how a system user configures and manages SmartMove.
2.1 Configuring SmartMove
2.2 Managing SmartMove
Start
End
Procedure
Step 1 Log in to DeviceManager.
Step 2 Choose Settings > License Management.
Step 3 In the middle function pane, ensure that SmartMove is displayed in the feature
list.
NOTE
● If no license file has been imported, import a license file by referring to the Initialization
Guide.
● If the license is different from the purchased one, contact technical support engineers.
----End
Prerequisites
● A target storage pool has been created, the capacity of the target storage
pool meets the migration requirements, and the health status of the target
storage pool is Normal.
● The source file system is not configured with features that are mutually
exclusive with SmartMove.
● The health status of the source file system is Normal.
Precautions
Target file systems become unavailable after storage pool exchange and need to
be deleted.
Procedure
Step 1 Choose Services > Resource Tuning > SmartMove.
Step 2 Select the vStore to which the desired file systems belong from the vStore drop-
down list in the upper left corner.
Step 3 Click Create.
The Create SmartMove Task page is displayed.
Step 4 Specify Object: select source file systems for data migration.
1. Select one or more file systems from Available File Systems to add them to
Selected File Systems.
2. Click Next.
Step 5 Select a storage pool for target file systems. The system automatically creates
target file systems in the target storage pool for the source file systems to be
migrated.
Step 6 Set the migration policy. For details about related parameters, see Table 2-1.
Parameter Description
Max. I/O Maximum time for suspending host services during data
Suspension Time exchange between a SmartMove pair. During the exchange
process, the host services may suspend for a short time. If
the suspension time exceeds the specified value, the
exchange task fails.
[Value range]
30s to 120s
----End
Context
● On the SmartMove management page, you can click to refresh
SmartMove pair information.
● On the SmartMove management page, you can click and select the
SmartMove pair parameters you want to view.
● On the SmartMove management page, you can click or next to a
parameter to change the display order of SmartMove pairs.
● On the SmartMove management page, you can click to export SmartMove
pair information to your local PC.
Procedure
Step 1 Choose Services > Resource Tuning > SmartMove.
Step 2 Select a vStore from the vStore drop-down list in the upper left corner.
Step 3 View the SmartMove pair information. Table 2-2 describes the parameters.
Parameter Description
Source Storage Pool Storage pool to which a source file system belongs.
Target Storage Pool Storage pool to which a target file system belongs.
ID ID of a SmartMove pair.
Owning vStore vStore to which a pair of source and target file systems
belong.
Parameter Description
Parameter Description
Max. I/O Suspension Maximum time for suspending host services during
Time data exchange between a SmartMove pair. During the
exchange process, the host services may suspend for a
short time. If the suspension time exceeds the specified
value, the exchange task fails.
----End
Prerequisites
● The running status of the SmartMove pair is Paused, Synchronizing, Normal,
or Faulty.
● The exchange status of the SmartMove pair is To be exchanged or Exchange
failed.
Procedure
Step 1 Choose Services > Resource Tuning > SmartMove.
Step 2 Select the desired vStore from the vStore drop-down list in the upper left corner.
Step 3 Click More on the right of the desired SmartMove pair and choose Modify.
The Modify SmartMove Task page is displayed.
Step 4 Set migration properties for the SmartMove pair. Table 2-3 describes related
parameters.
Exchange Policy Exchange policy of the SmartMove pair. Possible values are
Automatic and Manual.
● Automatic
After data synchronization is complete, the source and
target file systems automatically exchange the storage
pools.
● Manual
After data synchronization is complete, you need to
manually exchange the storage pools of the source and
target file systems.
NOTE
The exchange policy cannot be modified when the running status of
the SmartMove pair is Normal.
Parameter Description
Migration Rate Data migration rate of the SmartMove pair. Possible values
are Low, Medium, High, Highest, and Custom.
● Low
Migration takes a relatively long period of time. This value
is applicable when the service load is heavy.
The rate is normally from 0 MB/s to 5 MB/s.
● Medium
Migration takes a relatively short period of time. This value
is applicable when the service load is relatively heavy.
The rate is normally from 10 MB/s to 20 MB/s.
● High
Migration takes a short period of time. This value is
applicable when the service load is relatively light.
The rate is normally from 50 MB/s to 70 MB/s.
● Highest
Migration takes the shortest period of time. This value is
applicable when the service load is light.
If no host I/O is delivered to the storage system, the rate is
normally from 70 MB/s to 1024 MB/s. This value is
applicable when the service load is light.
● Custom
You can set the migration rate as required. The value
ranges from 1 MB/s to 4096 MB/s.
Max. I/O Maximum time for suspending host services during data
Suspension exchange between a SmartMove pair. During the exchange
Time process, the host services may suspend for a short time. If the
suspension time exceeds the specified value, the exchange
task fails.
[Value range]
30s to 120s
----End
Procedure
Step 1 Choose Services > Resource Tuning > SmartMove.
Step 2 Select the desired vStore from the vStore drop-down list in the upper left corner.
Step 3 Select one or more desired SmartMove pairs and click Modify Migration Rate.
The Modify Migration Rate page is displayed.
NOTE
You can click Selected Pairs and select LUNs again from the expanded list.
Step 4 Set the migration rate for the SmartMigration pairs. Possible values are Low,
Medium, High, Highest, and Custom.
● Low
Migration takes a relatively long period of time. This value is applicable when
the service load is heavy.
The rate is normally from 0 MB/s to 5 MB/s.
● Medium
Migration takes a relatively short period of time. This value is applicable when
the service load is relatively heavy.
The rate is normally from 10 MB/s to 20 MB/s.
● High
Migration takes a short period of time. This value is applicable when the
service load is relatively light.
The rate is normally from 50 MB/s to 70 MB/s.
● Highest
Migration takes the shortest period of time. This value is applicable when the
service load is light.
If no host I/O is delivered to the storage system, the rate is normally from 70
MB/s to 1024 MB/s. This value is applicable when the service load is light.
● Custom
You can set the migration rate as required. The value ranges from 1 MB/s to
4096 MB/s.
Step 5 Click OK.
----End
Prerequisites
● The running status of the SmartMove pair is Paused, Synchronizing, or
Faulty.
● The exchange status of the SmartMove pair is To be exchanged or Exchange
failed.
Procedure
Step 1 Choose Services > Resource Tuning > SmartMove.
Step 2 Select the desired vStore from the vStore drop-down list in the upper left corner.
Step 3 Select the desired SmartMove pair and choose More > Synchronize.
NOTE
Alternatively, click More on the right of the desired SmartMove pair and choose
Synchronize.
----End
Prerequisites
● The running status of the SmartMove pair is Paused, Synchronizing, Normal,
or Faulty.
● The exchange status of the SmartMove pair is To be exchanged or Exchange
failed.
Procedure
Step 1 Choose Services > Resource Tuning > SmartMove.
Step 2 Select the desired vStore from the vStore drop-down list in the upper left corner.
Step 3 Select the desired SmartMove pair and choose More > Pause.
NOTE
Alternatively, click More on the right of the desired SmartMove pair and choose Pause.
----End
Prerequisites
● The running status of the SmartMove pair is Normal.
● The exchange status of the SmartMove pair is To be exchanged or Exchange
failed.
● Dtrees and snapshots cannot be created or deleted during information
exchange of SmartMove.
Precautions
Target file systems become unavailable after storage pool exchange and need to
be deleted.
Procedure
Step 1 Choose Services > Resource Tuning > SmartMove.
Step 2 Select the desired vStore from the vStore drop-down list in the upper left corner.
Step 3 Select the desired SmartMove pair and choose More > Exchange.
NOTE
Alternatively, click More on the right of the desired SmartMove pair and choose Exchange.
----End
Prerequisites
● The exchange status of the SmartMove pair is not Exchanging.
● The running status of the SmartMove pair is not Creating, Synchronizing, or
Deleting.
NOTE
If the running status of a SmartMove pair is Creating or Deleting, you can only run the
delete smart_move general source_fs_id=? command on the CLI to forcibly delete it. For
details about this command, see Command/Event/Error Code Query.
Procedure
Step 1 Choose Services > Resource Tuning > SmartMove.
Step 2 Select the desired vStore from the vStore drop-down list in the upper left corner.
Step 3 Select one or more desired SmartMove pairs and click Delete.
NOTE
Alternatively, click More on the right of the desired SmartMove pair and choose Delete.
Step 4 (Optional) Select Delete target file systems to reclaim the space of the source
storage pool.
Step 5 Confirm your operation as prompted.
----End
This chapter describes how a system user configures and manages SmartMove.
3.1 Configuration Process
3.2 Creating a SmartMove Task
3.3 Managing SmartMove
Start
End
Prerequisites
● A target storage pool has been created, the capacity of the target storage
pool meets the migration requirements, and the health status of the target
storage pool is Normal.
● The source file system is not configured with features that are mutually
exclusive with SmartMove.
● The health status of the source file system is Normal.
Precautions
Target file systems become unavailable after exchange and need to be deleted.
Procedure
Step 1 Choose Services > Resource Tuning > SmartMove.
Step 2 Click Create.
The Create SmartMove Task page is displayed.
Step 3 Specify Object: select source file systems for data migration.
1. Select one or more file systems from Available File Systems to add them to
Selected File Systems.
2. Click Next.
Step 4 Select a storage pool for target file systems. The system automatically creates
target file systems in the target storage pool for the source file systems to be
migrated.
Step 5 Set the migration policy. For details about related parameters, see Table 3-1.
Parameter Description
Max. I/O During SmartMove data exchange, host services suspend for
Suspension Time a short period of time. The value of this parameter is the
maximum time of host service suspension during the
exchange. If the time exceeds the value of this parameter,
the exchange fails.
[Value range]
30s to 120s
----End
Context
● On the SmartMove management page, you can click to refresh
SmartMove pair information.
● On the SmartMove management page, you can click or next to a
parameter and enter a keyword or select a parameter value to search for the
desired SmartMove pairs.
● On the SmartMove management page, you can click and select the
SmartMove pair parameters you want to view.
● On the SmartMove management page, you can click or next to a
parameter to change the display order of SmartMove pairs.
● On the SmartMove management page, you can click to export SmartMove
pair information to your local PC.
Procedure
Step 1 Choose Services > Resource Tuning > SmartMove.
Step 2 View the SmartMove pair information. Table 3-2 describes the parameters.
Parameter Description
Source Storage Pool Storage pool to which a source file system belongs.
Target Storage Pool Storage pool to which a target file system belongs.
ID ID of a SmartMove pair.
Parameter Description
Parameter Description
----End
Prerequisites
● The running status of the SmartMove pair is Paused, Synchronizing, Normal,
or Faulty.
● The exchange status of the SmartMove pair is To be exchanged or Exchange
failed.
Procedure
Step 1 Choose Services > Resource Tuning > SmartMove.
Step 2 Click More on the right of the desired SmartMove pair and select Modify.
The Modify SmartMove Task page is displayed.
Step 3 Set migration properties for the SmartMove pair. Table 3-3 describes related
parameters.
Parameter Description
Migration Rate Data migration rate of a SmartMove pair. Possible values are
Low, Medium, High, Highest, and Custom.
● Low
Migration takes a relatively long period of time. This value
is used when the service load is heavy.
The rate is normally from 0 MB/s to 5 MB/s.
● Medium
Migration takes a relatively short period of time. This value
is used when the service load is relatively heavy.
The rate is normally from 10 MB/s to 20 MB/s.
● High
Migration takes a short period of time. This value is used
when the service load is relatively light.
The rate is normally from 50 MB/s to 70 MB/s.
● Highest
Migration takes the shortest period of time. This value is
used when the service load is light.
If no host I/O is delivered to the storage system, the rate is
normally from 70 MB/s to 1024 MB/s. This value is
applicable when the service load is light.
● Custom
You can set the migration rate as required. The value
ranges from 1 MB/s to 4096 MB/s.
Max. I/O During SmartMove data exchange, host services suspend for
Suspension a short period of time. The value of this parameter is the
Time maximum time of host service suspension during the
exchange. If the time exceeds the value of this parameter, the
exchange fails.
[Value range]
30s to 120s
----End
Procedure
Step 1 Choose Services > Resource Tuning > SmartMove.
Step 2 Select one or more desired SmartMove pairs and click Modify Migration Rate.
The Modify Migration Rate page is displayed.
NOTE
You can click Selected Pairs and select LUNs again from the expanded list.
Step 3 Set the migration rate for the SmartMigration pairs. Possible values are Low,
Medium, High, Highest, and Custom.
● Low
Migration takes a relatively long period of time. This value is used when the
service load is heavy.
The speed is normally from 0 MB/s to 5 MB/s.
● Medium
Migration takes a relatively short period of time. This value is used when the
service load is relatively heavy.
The speed is normally from 10 MB/s to 20 MB/s.
● High
Migration takes a short period of time. This value is used when the service
load is relatively light.
The rate is normally from 50 MB/s to 70 MB/s.
● Highest
Migration takes the shortest period of time. This value is used when the
service load is light.
If no host I/O is delivered to the storage system, the rate is normally from 70
MB/s to 1024 MB/s. This value is applicable when the service load is light.
● Custom
You can set the migration rate as required. The value ranges from 1 MB/s to
4096 MB/s.
----End
Prerequisites
● The running status of the SmartMove pair is Paused, Synchronizing, or
Faulty.
● The exchange status of the SmartMove pair is To be exchanged or Exchange
failed.
Procedure
Step 1 Choose Services > Resource Tuning > SmartMove.
Step 2 Select the desired SmartMove pair and choose More > Synchronize.
NOTE
Alternatively, click More on the right of the desired SmartMove pair and select
Synchronize.
----End
Prerequisites
● The running status of the SmartMove pair is Paused, Synchronizing, Normal,
or Faulty.
● The exchange status of the SmartMove pair is To be exchanged or Exchange
failed.
Procedure
Step 1 Choose Services > Resource Tuning > SmartMove.
Step 2 Select the desired SmartMove pair and choose More > Pause.
NOTE
Alternatively, click More on the right of the desired SmartMove pair and select Pause.
----End
Prerequisites
● The running status of the SmartMove pair is Normal.
● The exchange status of the SmartMove pair is To be exchanged or Exchange
failed.
● Dtrees and snapshots cannot be created or deleted during storage pool
exchange.
Precautions
Target file systems become unavailable after storage pool exchange and need to
be deleted.
Procedure
Step 1 Choose Services > Resource Tuning > SmartMove.
Step 2 Select the desired SmartMove pair and choose More > Exchange.
NOTE
Alternatively, click More on the right of the desired SmartMove pair and select Exchange.
----End
Prerequisites
● The exchange status of the SmartMove pair is not Exchanging.
● The running status of the SmartMove pair is not Creating, Synchronizing, or
Deleting.
NOTE
If the running status of a SmartMove pair is Creating or Deleting, you can only run
the delete smart_move general source_fs_id=? command on the CLI to forcibly
delete it. For details about this command, see Command/Event/Error Code Query.
Procedure
Step 1 Choose Services > Resource Tuning > SmartMove.
Step 2 Select one or more desired SmartMove pairs and click Delete.
NOTE
Alternatively, click More on the right of the desired SmartMove pair and select Delete.
Step 3 (Optional) Select Delete target file systems to reclaim the occupied space of the
source storage pool.
Step 4 Confirm your operation as prompted.
----End
This section provides certain CLI commands for configuring and managing
SmartMove.
NOTE
Start
Create a
SmartMove task.
End
Operation Command
Operation Command
C Glossary
A
AC power module The module that transfers the external AC power
supply into the power supply for internal use.
Application server A service processing node (a computer device) on the
network. Application programs of data services run
on the application server.
Asynchronous remote A kind of remote replication. When the data at the
replication primary site is updated, the data does not need to be
updated synchronously at the mirroring site to finish
the update. In this way, performance is not reduced
due to data mirroring.
Air baffle It optimizes the ventilation channels and improves
the heat dissipation capability of the system.
Audit log guarantee A mode for recording audit logs. This mode
mode preferentially ensures that the audit log function is
normal and no audit log is missing.
Audit log non- A mode for recording audit logs. In this mode,
guarantee mode services are running properly. Audit logs may be
missing.
B
Backup A collection of data stored on (usually removable)
non-volatile storage media for purposes of recovery
in case the original copy of data is lost or becomes
inaccessible; also called a backup copy. To be useful
for recovery, a backup must be made by copying the
source data image when it is in a consistent state.
The act of creating a backup.
C
Cache hit ratio The ratio of the number of cache hits to the number
of all I/Os during a read task, usually expressed as a
percentage.
Captive screw Specially designed to lock into place on a parent
board or motherboard, allowing for easy installation
and removal of attached pieces without release of
the screw.
Challenge Handshake A password-based authentication protocol that uses a
Authentication challenge to verify that a user has access rights to a
Protocol system. A hash of the supplied password with the
challenge is sent for comparison so the cleartext
password is never sent over the connection.
Compliance mode A protection mode of WORM. In compliance mode,
files within their protection period cannot be changed
or deleted by either the file user or by the system
administrator. Files with expired protection periods
can be deleted but not changed by the file user or
the system administrator.
Controller The control logic in a disk or tape that performs
command decoding and execution, host data transfer,
serialization and deserialization of data, error
detection and correction, and overall management of
device operations. The control logic in a storage
subsystem that performs command transformation
and routing, aggregation (RAID, mirroring, striping, or
other), high-level error recovery, and performance
optimization for multiple storage devices.
Controller enclosure An enclosure that accommodates controllers and
provides storage services. It is the core component of
a storage system and generally consists of
components, such as controllers, power supplies, and
fans.
Copying A pair state. The state indicates that the source LUN
data is being synchronized to the target LUN.
Container root Space used to store the metadata for running
directory container images and container instances.
Container image An image is a special file system, which provides the
programs, libraries, resources, and configuration files
required for running containers. It also contains
configuration parameters, for example, for
anonymous disks, environment variables, and users.
The image does not contain dynamic data, and its
content will not be modified after construction.
Containerized An image can start multiple containers, and an
application application can contain one or a group of containers.
D
Data compression The process of encoding data to reduce its size. Lossy
compression (i.e., compression using a technique in
which a portion of the original information is lost) is
acceptable for some forms of data (e.g., digital
images) in some applications, but for most IT
applications, lossless compression (i.e., compression
using a technique that preserves the entire content of
the original data, and from which the original data
can be reconstructed exactly) is required.
Data flow A process that involves processing data extracted
from the source system. These processes include:
filtering, integration, calculation, and summary,
finding and solving data inconsistency, and deleting
invalid data so that the processed data meets the
requirements of the destination system for the input
data.
Data migration A movement of data or information between
information systems, formats, or media. Migration is
performed for reasons such as possible decay of
storage media, obsolete hardware or software
(including obsolete data formats), changing
performance requirements, the need for cost
efficiencies etc.
Data source A system, database (database user; database
instance), or file that can make BOs persistent.
Deduplication The replacement of multiple copies of data — at
variable levels of granularity — with references to a
shared copy in order to save storage space and/or
bandwidth.
Dirty data Data that is stored temporarily on the cache and has
not been written onto disks.
E
eDevLUN Logical storage array space created by a third-party
storage array.
Expansion module A component used for expansion.
Expansion Connects a storage system to more disk enclosures
through connection cables, expanding the capacity of
the storage system.
F
Field replaceable unit A unit or component of a system that is designed to
be replaced in the field, i.e., without returning the
system to a factory or repair depot. Field replaceable
units may either be customer-replaceable or their
replacement may require trained service personnel.
Firmware Low-level software for booting and operating an
intelligent device. Firmware generally resides in read-
only memory (ROM) on the device.
Flash Translation Layer Flash Translation Layer (FTL) organizes and manages
host data, enables host data to be allocated to NAND
flash chips of SSDs in an orderly manner, maintains
the mapping relationship between logical block
addresses (LBAs) and physical block addresses
(PBAs), and implements garbage collection, wear
leveling, and bad block management.
Front-end port The port that connects the controller enclosure to the
service side and transfers service data. Front-end port
types are Fibre Channel and iSCSI.
Front-end interconnect On a storage device, all controllers share the front-
I/O module (FIM) end interface modules.
G
Garbage collection The process of reclaiming resources that are no
longer in use. Garbage collection has uses in many
aspects of computing and storage. For example, in
flash storage, background garbage collection can
improve write performance by reducing the need to
perform whole block erasures prior to a write.
Gateway A device that receives data via one protocol and
transmits it via another.
H
Hard disk tray The tray that bears the hard disk.
Heartbeat Heartbeat supports node communication, fault
diagnosis, and event triggering. Heartbeats are
protocols that require no acknowledgement. They are
transmitted between two devices. The device can
judge the validity status of the peer device.
Hit ratio The ratio of directly accessed I/Os from the cache to
all I/Os.
Hot swap The substitution of a replacement unit (RU) in a
system for a defective unit, where the substitution
can be performed while the system is performing its
normal functioning normally. Hot swaps are physical
operations typically performed by humans.
HyperMetro A value-added service of storage systems.
HyperMetro means two datasets (on two storage
systems) can provide storage services as one dataset
to achieve load balancing among applications and
failover without service interruption.
HyperMetro domain A HyperMetro configuration object generally; made
up of two storage arrays and one quorum server.
HyperMetro services can be created on a HyperMetro
domain.
I
In-band management The management control information of the network
and the carrier service information of the user
network are transferred through the same logical
channel. In-band management enables users to
manage storage arrays through commands.
Management commands are sent through service
channels, such as I/O write and read channels. The
advantages of in-band management include high
speed, stable transfer, and no additional
management network ports required.
Initiator The system component that originates an I/O
command over an I/O interconnect. The endpoint
that originates a SCSI I/O command sequence. I/O
adapters, network interface cards, and intelligent I/O
interconnect control ASICs are typical initiators.
L
Load balance A method of adjusting the system, application
components, and data to averagely distribute the
applied I/Os or computing requests to physical
resources of the system.
Logical unit The addressable entity within a SCSI target that
executes I/O commands.
Logical unit number The SCSI identifier of a logical unit within a target.
Industry shorthand, when phrased as "LUN", for the
logical unit indicated by the logical unit number.
LUN formatting The process of writing 0 bits in the data area of the
logical drive and generating related parity bits so that
the logical drive can be in the ready state.
LUN mapping A storage system maps LUNs to application servers
so that application servers can access storage
resources.
LUN migration A method for the LUN data to migrate between
different physical storage spaces while ensuring data
integrity and uninterrupted operation of host
services.
LUN snapshot A type of snapshot created for a LUN. This snapshot
is both readable and writable and is mainly used to
provide a snapshot LUN from point-in-time LUN
data.
M
Maintenance terminal A computer connected through a serial port or
management network port. It maintains the storage
system.
Management interface The module that integrates one or more
module management network ports.
Management network An entity that provides means to transmit and
process network management information.
Management network The network port on the controller enclosure
port connected to the maintenance terminal. It is provided
for the remote maintenance terminal. Its IP address
can be modified with the change of the customer's
environment.
N
NVM Express A host controller interface with a register interface
and command set designed for PCI Express-based
SSDs.
NVMe SSD A solid state disk (SSD) with a non-volatile memory
express (NVMe) interface. Compared with other
SSDs, such SSDs can deliver higher performance and
shorter latency.
O
Out-of-band A management mode used during out-of-band
management networking. The management and control
information of the network and the bearer service
information of the user network are transmitted
through different logical channels.
P
Power failure When an external power failure occurs, the AC PEM
protection depends on the battery for power supply. This
ensures the integrity of the dirty data in the cache.
Pre-copy When the system monitors a failing member disk in a
RAID group, the system copies the data from the disk
to a hot spare disk in advance.
Palm-sized NVMe SSD A palm-sized NVMe SSD is a type of NVMe SSD of
which the dimensions (H x W x D) are 160 mm x 79.8
mm x 9.5 mm (neither 3.5-inch nor 2.5-inch).
Q
Quorum server A server that can provide arbitration services for
clusters or HyperMetro to prevent the resource access
conflicts of multiple application servers.
Quorum Server Mode A HyperMetro arbitration mode. When a HyperMetro
arbitration occurs, the quorum server decides which
site wins the arbitration.
R
RAID level The application of different redundancy types to a
logical drive. A RAID level improves the fault
tolerance or performance of the logical drive but
reduces the available capacity of the logical drive.
You must specify a RAID level for each logical drive.
Ransomware file When launching attacks, ransomware usually
interception generates encrypted files with special file name
extensions. In light of this, the system intercepts the
write to files with specific file name extensions to
block the extortion from known ransomware and
protect file systems in the storage system.
Real-time ransomware Ransomware has similar I/O behavior characteristics.
detection By analyzing file I/O behavior characteristics, the
system quickly filters out abnormal files and
performs deep content analysis on the abnormal files
to detect files attacked by ransomware. Then, secure
snapshots are created for file systems where files
have been attacked, and alarms are reported to
notify the data protection administrator, limiting the
impact of ransomware and reducing losses.
S
Script A parameterized list of primitive I/O interconnect
operations intended to be executed in sequence.
Often used with respect to ports, most of which are
able to execute scripts of I/O commands
autonomously (without policy processor assistance).
A sequence of instructions intended to be parsed and
carried out by a command line interpreter or other
scripting language. Perl, VBScript, JavaScript and Tcl
are all scripting languages.
Serial port An input/output location (channel) that sends and
receives data (one bit at a time) to and from the CPU
of a computer or a communications device. Serial
ports are used for serial data communication and as
interfaces for some peripheral devices, such as mouse
devices and printers.
Service data The user and/or network information required for the
normal functioning of services.
Service network port The network port that is used to store services.
Simple network An IETF protocol for monitoring and managing
management protocol systems and devices in a network. The data being
monitored and managed is defined by an MIB. The
functions supported by the protocol are the request
and retrieval of data, the setting or writing of data,
and traps that signal the occurrence of events.
Single point of failure One component or path in a system, the failure of
which would make the system inoperable.
Slot A position defined by an upper guide rail and the
corresponding lower guide rail in a frame. A slot
houses a board.
Small computer system A collection of ANSI standards and proposed
interface standards that define I/O interconnects primarily
intended for connecting storage subsystems or
devices to hosts through host bus adapters. Originally
intended primarily for use with small (desktop and
desk-side workstation) computers, SCSI has been
extended to serve most computing needs, and is
arguably the most widely implemented I/O
interconnect in use today.
Snapshot A point in time copy of a defined collection of data.
Clones and snapshots are full copies. Depending on
the system, snapshots may be of files, LUNs, file
systems, or any other type of container supported by
the system.
Snapshot copy A copy of a snapshot LUN.
Source LUN The LUN where the original data is located.
Static Priority Mode A HyperMetro arbitration mode. When a HyperMetro
arbitration occurs, the preferred site always wins the
arbitration.
Storage system An integrated system that consists of the following
parts: controller, storage array, host bus adapter,
physical connection between storage units, and all
control software.
Storage unit An abstract definition of backup storage media for
storing backup data. The storage unit is connected to
the actual storage media used to back up data.
T
Target The endpoint that receives a SCSI I/O command
sequence.
Target LUN The LUN on which target data resides.
Thin LUN A logic disk that can be accessed by hosts. It
dynamically allocates storage resources from the thin
pool according to the actual capacity requirements of
users.
Topology The logical layout of the components of a computer
system or network and their interconnections.
Topology deals with questions of what components
are directly connected to other components from the
standpoint of being able to communicate. It does not
deal with questions of physical location of
components or interconnecting cables. The
communication infrastructure that provides Fibre
Channel communication among a set of PN_Ports
(e.g., a Fabric, an Arbitrated Loop, or a combination
of the two).
U
User interface The space where users interact with a machine.
U-shaped bracket It is an optional structural part like letter "U". It is
located between the mounting ear of a chassis and
the mounting bar of a cabinet or bay and is used to
adjust the locations of the chassis and mounting bar
of the cabinet or bay.
W
Wear leveling A set of algorithms utilized by a flash controller to
distribute writes and erases across the cells in a flash
device. Cells in flash devices have a limited ability to
survive write cycles. The purpose of wear leveling is
to delay cell wear out and prolong the useful life of
the overall flash device.
Write amplification Increase in the number of write operations by the
device beyond the number of write operations
requested by hosts.
Write amplification The ratio of the number of write operations on the
factor device to the number of write operations requested
by the host.
Write back A caching technology in which the completion of a
write request is signaled as soon as the data is in the
cache. Actual writing to non-volatile media occurs at
a later time. Write back includes inherent risks: an
application will take action predicated on the write
completion signal, and a system failure before the
data is written to non-volatile media will cause
media contents to be inconsistent with that
subsequent action. For these reasons, sufficient write
back implementations include mechanisms to
preserve cache contents across system failures
(including power failures) and a flushed cache at
system restart time.
Write Once Read Many A type of storage, designed for fixed content, that
preserves what is written to it in an immutable
fashion. Optical disks are an example of WORM
storage.
Write through A caching technology in which the completion of a
write request is not signaled until data is safely
stored on non-volatile media. Write performance
equipped with the write through technology is
approximately that of a non-cached system. However,
if the written data is also held in a cache, subsequent
read performance may be dramatically improved.
Z
Zone A collection of Fibre Channel N_Ports and/or
NL_Ports (i.e., device ports) that are permitted to
communicate with each other via the fabric. Any two
N_Ports and/or NL_Ports that are not members of at
least one common zone are not permitted to
communicate via the fabric. Zone membership may
be specified by: 1) port location on a switch, (i.e.,
Domain_ID and port number); or, 2) the device's
N_Port_Name; or, 3) the device's address identifier;
or, 4) the device's Node_Name. Well-known
addresses are implicitly included in every zone.