OceanStor Dorado 6.1.x SmartMigration Feature Guide for Block
OceanStor Dorado 6.1.x SmartMigration Feature Guide for Block
6.1.x
Issue 06
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 SmartMigration feature provided by storage systems
in terms of working principles, application scenarios, configuration examples, and
management operations.
NOTE
OceanStor Dorado 2000 supports only basic block storage services and does not support
services such as file systems and containers.
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:
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 06 (2023-10-31)
This issue is the sixth official release.
Issue 05 (2023-04-20)
This issue is the fifth official release.
Issue 04 (2022-11-15)
This issue is the fourth official release.
Issue 03 (2022-08-25)
This issue is the third official release.
Issue 02 (2022-01-25)
This issue is the second official release.
Added vStore view-related operations.
Issue 01 (2021-09-30)
This issue is the first official release.
Contents
2 Planning...................................................................................................................................12
3 Configuring and Managing SmartMigration (System View)..................................... 14
3.1 Configuring SmartMigration............................................................................................................................................. 14
3.1.1 Configuration Process...................................................................................................................................................... 14
3.1.2 Checking the License File................................................................................................................................................16
3.1.3 (Optional) Taking Control of a LUN from a Heterogeneous Storage System............................................. 16
3.1.4 Creating a SmartMigration Task.................................................................................................................................. 17
3.1.5 Splitting a SmartMigration Pair....................................................................................................................................22
3.1.6 Splitting Multiple SmartMigration Pairs Consistently...........................................................................................23
3.2 Managing SmartMigration................................................................................................................................................ 24
3.2.1 Viewing SmartMigration Pair Information............................................................................................................... 24
3.2.2 Modifying the Properties of a SmartMigration Task.............................................................................................25
3.2.3 Pausing Synchronization................................................................................................................................................. 27
3.2.4 Resuming Synchronization............................................................................................................................................. 27
3.2.5 Modifying the Migration Rate...................................................................................................................................... 27
3.2.6 Deleting a SmartMigration Task.................................................................................................................................. 28
5 Configuration Example........................................................................................................ 45
5.1 Using SmartMigration and SmartVirtualization to Migrate an Oracle ASM File System............................45
5.1.1 Requirement Analysis.......................................................................................................................................................45
5.1.2 Configuration Planning....................................................................................................................................................48
5.1.3 Configuration Operations............................................................................................................................................... 60
5.1.4 Configuration Verification.............................................................................................................................................. 66
C Glossary................................................................................................................................... 71
D Acronyms and Abbreviations............................................................................................. 87
1 Feature Description
SmartMigration allows users to migrate data from the source LUN to the target
LUN without interrupting host services. The process is invisible to users, and this
feature enables the target LUN to completely replace the source LUN and carry its
services. This chapter introduces SmartMigration and is organized into five
sections: overview, availability, working principle, restrictions, and application
scenarios.
1.1 Overview
1.2 Availability
1.3 Working Principles
1.4 Impact and Restrictions
1.5 Application Scenarios
1.1 Overview
This section describes the background, definition, and benefits of SmartMigration.
Background
With the development of storage technologies and digitalization in various
industries, legacy storage systems need to be replaced, storage resources need to
be reallocated, and service performance needs to be adjusted. This has placed
huge emphasis on the need for service data migration within a storage system
and between storage systems. In some critical areas, host service interruption may
cause data loss and huge economic impacts. Non-disruptive service data migration
becomes a top issue for users. SmartMigration is developed to address those
requirements. It migrates service data in a storage system without interrupting
host services and enables service data to be migrated between Huawei storage
systems and other compatible storage systems.
Definition
SmartMigration is a key technology for service migration. It can non-disruptively
migrate service data within a storage system and between storage systems.
Benefits
Table 1-1 describes the benefits of SmartMigration.
1.2 Availability
This section describes the license requirements and specifications of
SmartMigration.
License Requirements
SmartMigration requires a license.
NOTE
To obtain a license, contact your local Huawei representative office or Huawei authorized
distributor.
Specifications
The SmartMigration specifications depend on the product model. For detailed
specifications, refer to the Specifications Query (https://
info.support.huawei.com/storage/spec/#/home).
Concepts
● Data organization
The storage system uses a virtualization storage technology. Virtual data in
the storage pool consists of meta volumes and data volumes.
– Meta volume: records the data storage locations, including LUN IDs and
data volume IDs. LUN IDs are used to identify LUNs and data volume IDs
are used to identify physical space of data volumes.
– Data volume: stores user data.
● Source LUN
LUN from which service data is migrated.
● Target LUN
LUN to which service data is migrated.
● LM module
Manages SmartMigration in the storage system.
● Pair
In SmartMigration, a pair indicates the data migration relationship between
the source LUN and target LUN. A pair can have only one source LUN and
one target LUN.
● Dual-write
The process of writing data to the source and target LUNs at the same time
during service data migration.
● Log
Records data changes on the source LUN to determine whether the data is
written to the target LUN at the same time. Both systems can be written
simultaneously using the dual-write technology.
● Data change log (DCL)
Records differential data that fails to be written to the target LUN during the
data change synchronization.
● Splitting
The process of stopping service data synchronization between the source LUN
and target LUN, exchanging LUN information, and then removing the data
migration relationship between the source LUN and target LUN.
● Running Status of migration includes Normal, Interrupted, Paused, Faulty,
Migrating, and Migrated, as explained in the following table.
Status Explanation
Status Explanation
● Initial synchronization
After service data synchronization starts on the source LUN, all initial service data
is copied to the target LUN, as shown in Figure 1-1:
If data fails to be written to the target LUN, the storage system records the data
differences in the DCL and copies the data that fails to be written from the source
LUN to the target LUN according to the DCL. After the copy is complete, the
storage system returns a write success acknowledgment to the host.
If data fails to be written to the source LUN, the storage system returns a write
failure. Upon receiving the write failure, the host re-sends the data to the source
LUN only, but not to the target LUN. This mechanism ensures data consistency on
the source and target LUNs during migration.
Figure 1-2 shows how changed data is synchronized.
Splitting
Splitting is performed on a single pair. The splitting process is as follows: Service
data synchronization between the source LUN and the target LUN in a pair is
stopped. Then, the two LUNs exchange LUN information. After that, the data
migration relationship is canceled. During the split, host services are suspended.
After the information exchange, services are delivered to the target LUN. The
process is invisible to users.
Figure 1-3 illustrates the principle of splitting.
● Pair splitting
Pair splitting means that the data migration relationship between the source
LUN and target LUN is removed after LUN information is exchanged. After
the pair is split, if the host delivers an I/O request to the storage system, data
is only written to the source LUN (the physical space to which the source LUN
ID points is the target data volume). The target LUN will store all data of the
source LUN at the pair splitting point in time. After the pair splitting, no
connections can be established between the source LUN and target LUN.
In scenarios where multiple pairs are used, such as in medium- and large-size
database applications, data, logs, modification records, and other files are stored
on LUNs that are associated with one another in the storage system. Splitting
cannot ensure that information in one LUN is always associated with that in
another. If data in a LUN is unavailable, data in the other LUNs may become
invalid. Consistent splitting can resolve this problem. Figure 1-5 illustrates the
differences in processes and results between splitting and consistent splitting in a
scenario where multiple pairs are used.
Service data migration Before the migration, the target LUN does not
within a storage system need to be hosted and host services can be
running.
Application Restrictions
● Some parameters of storage systems supported by SmartMigration are
subject to storage system specifications such as the maximum number of
LUNs that can be configured for migration. For detailed specifications, refer to
the Specifications Query (https://info.support.huawei.com/storage/spec/#/
home).
● The source and target LUN cannot be faulty.
● The capacity of the target LUN must not be smaller than that of the source
LUN.
● Any LUN that has been mapped to an application server cannot be used as
the target LUN of a SmartMigration task.
● The implementation of a SmartMigration task for heterogeneous storage
systems depends on the LUN takeover function provided by
SmartVirtualization.
Compatibility
When using SmartMigration, ensure that the host operating system, multipathing
software, and the remote storage system are compatible with each other. You can
query the compatibility using the Huawei Storage Interoperability Navigator.
NOTE
SmartVirtualization takes over external LUNs offline or online. The online takeover does not
interrupt host services, however there is a short service suspension with offline takeover.
Figure 1-6 shows data migration from an existing storage system to a new
storage system.
Figure 1-6 Migrating data from a legacy storage system to a new storage system
LUN
New storage Legacy storage
system system
Data migration
(SmartMigration)
Mapping (SmartVirtualization)
eDevLUN External
LUN
NOTE
Figure 1-7 Migrating cold data from a new storage system to an existing storage
system
LUN
New storage Legacy storage
system system
Data migration
(SmartMigration)
Mapping (SmartVirtualization)
eDevLUN External
LUN
NOTE
2 Planning
This chapter describes how to plan the capacity, compatibility, and connection
between the local storage system and compatible heterogeneous storage system
before using SmartMigration to migrate data within a storage system or between
storage systems.
Capacity Planning
Before using SmartMigration for a LUN, reserve 5 per mill of the LUN capacity in
the storage pool where the LUN belongs to store metadata of the feature. To
apply multiple features to a LUN, reserve 1% of the LUN capacity in the storage
pool.
Compatibility Planning
SmartMigration works with SmartVirtualization to migrate data between storage
systems. Therefore, you need to know which storage systems (including Huawei
storage systems and mainstream third-party storage systems) are supported by
SmartVirtualization in advance. You can obtain the information at Huawei
Storage Interoperability Navigator.
Table 2-1 Connection modes between the local storage system and compatible
heterogeneous storage system
a: For versions earlier than 6.1.3, only Fibre Channel connections are supported
between the local storage system and third-party heterogeneous storage
system. For 6.1.3 and later, iSCSI connections are supported between the local
storage system and third-party heterogeneous storage system (HPE_3PAR 8450
or IBM Storwize V5000).
End
Start
End
NOTE
Context
● For migration within a storage system, ensure that the license file contains
the license information of SmartMigration whose feature name is displayed as
SmartMigration on the management page of DeviceManager.
● For migration between storage systems, ensure that the license file contains
the license information of SmartMigration and SmartVirtualization. Feature
names of the two features are displayed as SmartMigration and
SmartVirtualization on the management page of DeviceManager.
NOTE
Procedure
Step 1 Log in to DeviceManager.
Step 3 In the middle information pane, verify the information about active license files.
----End
Follow-up Procedure
If the SmartMigration or SmartVirtualization license is unavailable, apply for,
import and activate a license file. For details about how to apply for, import and
activate a license file, see Initialization Guide of the corresponding product model.
Context
The takeover of LUNs from a heterogeneous storage system includes scanning for
LUNs, creating a storage pool, and configuring an eDevLUN. For details, see
SmartVirtualization Feature Guide specific to your product model.
Prerequisites
● The storage system has available source and target LUNs, and those LUNs are
normal.
● The target LUN's capacity is not smaller than the source LUN's capacity, and
the target LUN has not been mapped.
Precautions
● LUNs that have been mapped to an application server cannot be configured
as target LUNs in any SmartMigration task.
● LUNs that are being migrated in a SmartMigration task cannot be configured
as source LUNs or target LUNs in another SmartMigration task.
● If the target LUN has a greater capacity than the source LUN, the excess
capacity of the target LUN will not be used. For proper use of service data,
ensure that no data exists in the excess capacity or use a target LUN with the
same capacity as the source LUN.
Procedure
Step 1 Choose Services > Resource Tuning > SmartMigration.
Step 2 Select the vStore to which a desired SmartMigration belongs from the vStore
drop-down list in the upper left corner.
Step 5 Establish pair relationships between the source LUNs and target LUNs and
configure the SmartMigration pairs.
1. You can create target LUNs in either Manual or Automatic mode.
– Automatic: The system automatically creates target LUNs that match the
source LUNs.
i. In the Pair Creation area, select the Automatic mode.
ii. Set the properties of the target LUNs. Table 3-1 describes the
parameters.
Parameter Description
– Manual: You must manually select a target LUN that matches a source
LUN.
i. In the Pair Creation area, select the Manual mode.
ii. Click Configure.
The Configure Pair page is displayed.
iii. Select the desired source and target LUNs and click Add to Pair.
The pair relationship between the source and target LUNs is created
and displayed in the SmartMigration Pairs area.
NOTE
You can click Remove to remove a pair from the pair list.
iv. Click OK.
2. Set SmartMigration properties. Table 3-2 describes the parameters.
Parameter Description
3. (Optional) Enable Specify Time to specify the migration rate for specified
time.
NOTE
– The migration rate for specified time applies to only the specified period. The
migration rate of other periods remains the default. This parameter takes effect
only when data is being migrated during the period.
Suppose that, from 2020-03-08 to 2020-04-24, you want to migrate data at a high
rate for one hour starting from 23:00 and at the default rate in other periods every
day. The parameter settings are as follows:
----End
Prerequisites
● A SmartMigration pair has been created.
● Running Status of a SmartMigration pair is Normal.
Precautions
● After a SmartMigration pair is split, write requests sent by production hosts to
the source LUN will not be synchronized to the target LUN.
● If the target LUN has been added to a LUN group and the target LUN is
configured with remote replication or HyperMetro, you need to manually
remove the target LUN from the LUN group and add the source LUN to the
corresponding LUN group after splitting the SmartMigration pair.
Procedure
Step 1 Choose Services > Resource Tuning > SmartMigration.
Step 2 Select one or more desired SmartMigration pairs and click Split.
NOTE
You can also click More on the right of a desired SmartMigration pair and select Split.
NOTE
If a target LUN is in a remote replication or HyperMetro pair, after the task is created, the
Execution Result page is displayed. You can view details about the current task on this
page.
----End
Prerequisites
● A SmartMigration pair has been created.
● Running Status of a SmartMigration pair is Normal.
Precautions
● After a SmartMigration pair is split, write requests sent by production hosts to
the source LUN will not be synchronized to the target LUN.
● If the target LUN has been added to a LUN group and the target LUN is
configured with remote replication or HyperMetro, you need to manually
remove the target LUN from the LUN group and add the source LUN to the
corresponding LUN group after splitting the SmartMigration pair.
Procedure
Step 1 Choose Services > Resource Tuning > SmartMigration.
Step 2 Select one or more desired SmartMigration pairs and click Consistency Split.
The Perform Consistency Splitting page is displayed.
Step 3 In Available Pairs, select one or more desired pairs, and they are added to
Selected Pairs automatically.
Step 4 Click OK.
Confirm your operation as prompted.
NOTE
If a target LUN is in a remote replication or HyperMetro pair, after the task is created, the
Execution Result page is displayed. You can view details about the current task on this
page.
----End
Procedure
Step 1 Choose Services > Resource Tuning > SmartMigration.
Step 2 View the SmartMigration pair information. Table 3-3 describes the parameters.
Parameter Description
----End
Prerequisites
The running status of a SmartMigration pair is Migrating, Paused, or
Interrupted.
Procedure
Step 1 Choose Services > Resource Tuning > SmartMigration.
Step 2 Click More on the right of the desired SmartMigration pair and select Modify.
The Modify SmartMigration Task page is displayed.
Step 3 Set SmartMigration properties. Table 3-4 describes the parameters.
Parameter Description
Step 4 (Optional) Enable Specify Time to specify the migration rate for specified time.
NOTE
● The migration rate for specified time applies to only the specified period. The migration
rate of other periods remains the default. This parameter takes effect only when data is
being migrated during the period.
Suppose that, from 2020-03-08 to 2020-04-24, you want to migrate data at a high rate
for one hour starting from 23:00 and at the default rate in other periods every day. The
parameter settings are as follows:
– Date: 2020-03-08 to 2020-04-24
– Start Time: 23:00
– Duration: 1 hours 0 minutes
– Migration Rate for Specified Time: High
● For details about Migration Rate for Specified Time, see the Default Migration Rate
parameter.
Prerequisites
Running Status of the SmartMigration pair is Synchronizing, Normal, or
Interrupted.
Procedure
Step 1 Choose Services > Resource Tuning > SmartMigration.
Step 2 Select one or more desired SmartMigration pairs, click More, and select Pause.
NOTE
You can also click More on the right of a desired SmartMigration pair and select Pause.
----End
Prerequisites
Running Status of the SmartMigration pair is Paused or Interrupted, and the
storage pool status is normal.
Procedure
Step 1 Choose Services > Resource Tuning > SmartMigration.
Step 2 Select one or more desired SmartMigration pairs, click More, and select Resume.
NOTE
You can also click More on the right of a desired SmartMigration pair and select Resume.
----End
Procedure
Step 1 Choose Services > Resource Tuning > SmartMigration.
Step 2 Select the desired SmartMigration pair, click More, and select 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 default migration rate for the SmartMigration 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 20 MB/s to 70 MB/s.
● Highest
Migration takes the shortest period of time. This value is used when the
service load is light.
The rate is normally above 100 MB/s.
● Custom
You can set the migration rate as required. The value ranges from 1 MB/s to
1024 MB/s.
NOTE
● The migration rate is affected by the LUN read and write performance and the link
bandwidth.
● Higher migration rates impose greater impact on host service performance. If you
choose Highest, the SmartMigration pair may be interrupted due to heavy service load.
You are advised to use the highest rate when the host service is not running.
----End
Procedure
Step 1 Choose Services > Resource Tuning > SmartMigration.
Step 2 Select one or more desired SmartMigration pairs and click Delete.
NOTE
You can also click More on the right of a desired SmartMigration pair and select Delete.
----End
4
Configuring and Managing
SmartMigration (vStore View, Applicable to
6.1.3 and Later)
This chapter describes how a vStore user configures SmartMigration for its
resources. Only OceanStor Dorado 6.1.3 and later versions allow vStore users to
configure SmartMigration for their resources.
4.1 Configuring SmartMigration
4.2 Managing SmartMigration
Figure 4-1 shows the flowchart for configuring SmartMigration within a storage
system.
Start
Create a SmartMigration
task.
End
Start
Create a SmartMigration
task.
End
NOTE
Context
The takeover of LUNs from a heterogeneous storage system includes scanning for
LUNs, creating a storage pool, and configuring an eDevLUN. For details, see
SmartVirtualization Feature Guide specific to your product model.
Prerequisites
● The storage system has available source and target LUNs, and those LUNs are
normal.
● The target LUN's capacity is not smaller than the source LUN's capacity, and
the target LUN has not been mapped.
Precautions
● LUNs that have been mapped to an application server cannot be configured
as target LUNs in any SmartMigration task.
● LUNs that are being migrated in a SmartMigration task cannot be configured
as source LUNs or target LUNs in another SmartMigration task.
● If the target LUN has a greater capacity than the source LUN, the excess
capacity of the target LUN will not be used. For proper use of service data,
ensure that no data exists in the excess capacity or use a target LUN with the
same capacity as the source LUN.
Procedure
Step 1 Choose Services > Resource Tuning > SmartMigration.
Step 2 Click Create.
The Create SmartMigration Task page is displayed.
Step 3 Specify source LUNs for data migration.
1. In Available LUNs, select one or more desired LUNs, and they are added to
Selected LUNs automatically.
2. Click Next.
Step 4 Establish pair relationships between the source LUNs and target LUNs and
configure the SmartMigration pairs.
1. You can create target LUNs in either Manual or Automatic mode.
– Automatic: The system automatically creates target LUNs that match the
source LUNs.
i. In the Pair Creation area, select the Automatic mode.
ii. Set the properties of the target LUNs. Table 4-1 describes the
parameters.
Parameter Description
– Manual: You must manually select a target LUN that matches a source
LUN.
i. In the Pair Creation area, select the Manual mode.
ii. Click Configure.
The Configure Pair page is displayed.
iii. Select the desired source and target LUNs and click Add to Pair.
The pair relationship between the source and target LUNs is created
and displayed in the SmartMigration Pairs area.
NOTE
You can click Remove to remove a pair from the pair list.
iv. Click OK.
2. Set SmartMigration properties. Table 4-2 describes the parameters.
Parameter Description
3. (Optional) Enable Specify Time to specify the migration rate for specified
time.
NOTE
– The migration rate for specified time applies to only the specified period. The
migration rate of other periods remains the default. This parameter takes effect
only when data is being migrated during the period.
Suppose that, from 2020-03-08 to 2020-04-24, you want to migrate data at a high
rate for one hour starting from 23:00 and at the default rate in other periods every
day. The parameter settings are as follows:
----End
Prerequisites
● A SmartMigration pair has been created.
● Running Status of a SmartMigration pair is Normal.
Precautions
● After a SmartMigration pair is split, write requests sent by production hosts to
the source LUN will not be synchronized to the target LUN.
● If the target LUN has been added to a LUN group and the target LUN is
configured with remote replication or HyperMetro, you need to manually
remove the target LUN from the LUN group and add the source LUN to the
corresponding LUN group after splitting the SmartMigration pair.
Procedure
Step 1 Choose Services > Resource Tuning > SmartMigration.
Step 2 Select one or more desired SmartMigration pairs and click Split.
NOTE
You can also click More on the right of a desired SmartMigration pair and select Split.
NOTE
If a target LUN is in a remote replication or HyperMetro pair, after the task is created, the
Execution Result page is displayed. You can view details about the current task on this
page.
----End
Prerequisites
● A SmartMigration pair has been created.
● Running Status of a SmartMigration pair is Normal.
Precautions
● After a SmartMigration pair is split, write requests sent by production hosts to
the source LUN will not be synchronized to the target LUN.
● If the target LUN has been added to a LUN group and the target LUN is
configured with remote replication or HyperMetro, you need to manually
remove the target LUN from the LUN group and add the source LUN to the
corresponding LUN group after splitting the SmartMigration pair.
Procedure
Step 1 Choose Services > Resource Tuning > SmartMigration.
Step 2 Select one or more desired SmartMigration pairs and click Consistency Split.
The Perform Consistency Splitting page is displayed.
Step 3 In Available Pairs, select one or more desired pairs, and they are added to
Selected Pairs automatically.
Step 4 Click OK.
Confirm your operation as prompted.
NOTE
If a target LUN is in a remote replication or HyperMetro pair, after the task is created, the
Execution Result page is displayed. You can view details about the current task on this
page.
----End
Context
● On the SmartMigration management page, you can click to refresh
SmartMigration pair information.
● On the SmartMigration management page, you can click or next to a
parameter and enter a keyword or select a parameter value to search for the
desired SmartMigration pairs.
● On the SmartMigration management page, you can click and select the
SmartMigration pair parameters you want to view.
● On the SmartMigration management page, you can click or next to a
parameter to change the display order of SmartMigration pairs.
● On the SmartMigration management page, you can click to export
SmartMigration pair information to your local PC.
Procedure
Step 1 Choose Services > Resource Tuning > SmartMigration.
Step 2 View the SmartMigration pair information. Table 4-3 describes the parameters.
Parameter Description
----End
Prerequisites
The running status of a SmartMigration pair is Migrating, Paused, or
Interrupted.
Procedure
Step 1 Choose Services > Resource Tuning > SmartMigration.
Step 2 Click More on the right of the desired SmartMigration pair and select Modify.
The Modify SmartMigration Task page is displayed.
Step 3 Set SmartMigration properties. Table 4-4 describes the parameters.
Step 4 (Optional) Enable Specify Time to specify the migration rate for specified time.
NOTE
● The migration rate for specified time applies to only the specified period. The migration
rate of other periods remains the default. This parameter takes effect only when data is
being migrated during the period.
Suppose that, from 2020-03-08 to 2020-04-24, you want to migrate data at a high rate
for one hour starting from 23:00 and at the default rate in other periods every day. The
parameter settings are as follows:
– Date: 2020-03-08 to 2020-04-24
– Start Time: 23:00
– Duration: 1 hours 0 minutes
– Migration Rate for Specified Time: High
● For details about Migration Rate for Specified Time, see the Default Migration Rate
parameter.
----End
Prerequisites
Running Status of a SmartMigration pair is Synchronizing, Normal, or
Interrupted.
Procedure
Step 1 Choose Services > Resource Tuning > SmartMigration.
Step 2 Select one or more desired SmartMigration pairs, click More, and select Pause.
NOTE
You can also click More on the right of a desired SmartMigration pair and select Pause.
----End
Prerequisites
Running Status of the SmartMigration pair is Paused or Interrupted, and the
storage pool status is normal.
Procedure
Step 1 Choose Services > Resource Tuning > SmartMigration.
Step 2 Select one or more desired SmartMigration pairs, click More, and select Resume.
NOTE
You can also click More on the right of a desired SmartMigration pair and select Resume.
----End
Procedure
Step 1 Choose Services > Resource Tuning > SmartMigration.
Step 2 Select the desired SmartMigration pair 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 default migration rate for the SmartMigration 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 20 MB/s to 70 MB/s.
● Highest
Migration takes the shortest period of time. This value is used when the
service load is light.
The rate is normally above 100 MB/s.
● Custom
You can set the migration rate as required. The value ranges from 1 MB/s to
1024 MB/s.
NOTE
● The migration rate is affected by the LUN read and write performance and the link
bandwidth.
● Higher migration rates impose greater impact on host service performance. If you
choose Highest, the SmartMigration pair may be interrupted due to heavy service load.
You are advised to use the highest rate when the host service is not running.
----End
Procedure
Step 1 Choose Services > Resource Tuning > SmartMigration.
Step 2 Select one or more desired SmartMigration pairs and click Delete.
NOTE
You can also click More on the right of a desired SmartMigration pair and select Delete.
----End
5 Configuration Example
Requirement Source
● Background
An enterprise has three storage systems: Huawei OceanStor Dorado, HDS
USP-V storage system, and Huawei OceanStor S5600T V100R005 storage
system. The OceanStor Dorado storage system is newly purchased and no
service is running on it. In addition, the assets management information
system and archive&backup system are running on the two storage systems
respectively.
– The asset management information system, which is served by an Oracle
database, records the enterprise's asset information.
– The archive&backup system archives service data that is infrequently
accessed.
Figure 5-1 shows the network where the two service systems are
deployed.
Fibre Channel
switch
● Service requirements
As the enterprise keeps growing, an ever-increasing amount of asset
management information needs to be recorded. The HDS USP-V has been
used for a long time. Its lifecycle is about to end, and its storage space is
about to be used up. The customer wants to migrate the asset management
information system to the OceanStor S5600T. The asset management
information system stores non-critical data. Therefore, the OceanStor S5600T
can meet the performance requirement, and existing storage resources can be
reused.
Specific customer requirements are as follows:
– Data should be migrated to the OceanStor S5600T non-disruptively.
– Data should be migrated during off-peak hours at night.
– After data is migrated, the OceanStor S5600T can take over the asset
management information system from the HDS USP-V.
The OceanStor Dorado storage system is used to describe configuration planning and
operations.
Network Planning
According to the requirement analysis, the OceanStor Dorado storage system is
used to host LUNs created on the HDS USP-V and the OceanStor S5600T. Before
configuring data migration, the customer needs to connect the OceanStor Dorado
storage system to the existing network. Figure 5-2 shows the transformed
network.
AIX application
server
Fibre Channel
switch
Table 5-5 lists the zones created to ensure normal communication among storage
systems and the application server.
Service Planning
According to the requirement analysis, the enterprise uses SmartVirtualization and
SmartMigration to migrate data. Figure 5-3 shows the configuration roadmap.
Start
Connect OceanStor Dorado
to the network.
Change the network.
Create zones on the Fibre
Channel switch.
Create target LUNs for the
data migration.
Set up a logical connection
between OceanStor Dorado
Set up a logical connection and HDS USP-V.
between storage systems. Set up a logical connection
between OceanStor Dorado
and S5600T.
Check the feature license.
Establish a mapping
Enable OceanStor Dorado to between the AIX application
take over services. server and the eDevLUNs
corresponding to the HDS
Scan for LUNs on the AIX
USP-V.
application server.
Create a SmartMigration
task for eDevLUN_HDS1 and
Use SmartMigration to set eDevLUN_Target_HDS1.
up a data migration
relationship. Create a SmartMigration
task for eDevLUN_HDS2 and
eDevLUN_Target_HDS2.
Establish a mapping
between the AIX application
Enable the S5600T to take server and the target LUNs
over services. created on S5600T.
Scan for LUNs on the AIX
application server.
End
application
server and
name of
the LUN
group to
which the
LUNs
belong
● Name of
the
mapping
view
created for
the host
group and
LUN group
a: The description in the brackets after a parameter indicates the object of the
parameter.
NOTE
Retain the default values for the parameters not mentioned in Table 5-6.
Procedure
Step 1 Change the network.
1. Connect the OceanStor Dorado storage system to the existing network
according to the network diagram shown in Figure 5-2.
2. Create zones on the Fibre Channel switch to ensure normal communication
among the HDS USP-V, OceanStor S5600T, OceanStor Dorado storage system,
and AIX application server.
NOTE
For details about how to create zones on the Fibre Channel switch, refer to the user manual
of the Fibre Channel switch.
Step 2 Log in to the OceanStor S5600T, and create target LUNs for data migration.
Navigation path: Choose Storage Resources > LUNs > Create > LUN.
NOTE
The preceding figure shows the parameter settings of Target_LUN_HDS1. When you create
Target_LUN_HDS2, set parameters as follows:
● Set Name to Target_LUN_HDS2.
● Set Capacity to 1 TB.
Navigation path: Choose SAN Services > Mappings > Host Groups >
Create.
c. Map the target LUNs created on the OceanStor S5600T to the host
corresponding to the OceanStor Dorado storage system.
Navigation path: Choose SAN Services > Mappings > Hosts, select the
host whose Name is Host_1, and choose Mapping > Add LUN Mapping
in the navigation bar.
Step 4 Log in to the OceanStor Dorado storage system, and check whether the
SmartVirtualization and SmartMigration licenses are valid.
Navigation path: Choose Settings > License Management.
Step 5 Use the OceanStor Dorado storage system to host LUNs created on the HDS USP-
V and the OceanStor S5600T.
1. Create a storage pool that is used to create eDevLUNs.
Navigation path: Choose System > Storage Pools > Create.
2. Initiate automatic LUN scanning.
Navigation path: Choose System > External Storage, select the remote device
whose Name is HDS USP-V, and click Scan for External LUN.
3. Create eDevLUNs.
Navigation path: Choose System > External Storage, select the remote device
whose Name is HDS USP-V, and click Create eDevLUN.
NOTE
The preceding operations are performed to enable the OceanStor Dorado storage system to
host LUNs created on the HDS USP-V. To enable the OceanStor Dorado storage system to
host LUNs created on the S5600T, set parameters as follows:
● Set Name of the remote device to S5600T.
● Set WWNs of the remote LUNs to 60:02:2A:11:00:06:8d:fe:07:a4:a4:6d:26:00:00:00:75
and 60:02:2A:11:00:06:8d:fe:07:a4:a4:6d:26:00:00:00:76.
● Set Name of eDevLUNs to eDevLUN_Target_HDS1 and eDevLUN_Target_HDS2.
● Set Storage Pool to which the eDevLUNs belong to StoragePool1.
Step 6 On the AIX application server, perform the following operations to stop services
running on the HDS USP-V:
1. Shut down the database and enable the file system to go offline.
2. Delete the LUNs mapped from the HDS USP-V and the multipathing software
delivered with the HDS USP-V.
rmdev -dl hdiskX//Delete the LUNs mapped to the application server.
smitty remove//Delete the multipathing software delivered with the HDS USP-V.
lslpp -l | grep -i dlmanager//Check whether the multipathing software is deleted. If no command
output is displayed, the multipathing software is successfully deleted.
3. Remove the AIX application server and the HDS USP-V from their joint zone.
4. Restart the AIX application server.
Step 7 Enable the OceanStor Dorado storage system to take over services.
1. Install Huawei UltraPath on the AIX application server.
NOTE
For details about the operation procedure, see the relevant UltraPath user guide
(applicable to the AIX operating system).
2. Log in to the OceanStor Dorado storage system, and set up a mapping
relationship between the AIX application server and eDevLUN_HDS1 as well
as between the AIX application server and eDevLUN_HDS2.
Perform the following operations:
a. Create a host.
Navigation path: Choose Services > Block Service > Host Groups >
Hosts > Create > Create Host.
b. Create a host group.
Navigation path: Choose Services > Block Service > Hosts Groups >
Host Groups > Create.
c. Create a LUN group.
Navigation path: Choose Services > Block Service > LUN Groups > LUN
Groups > Create.
d. Create a mapping.
Navigation path: Choose Services > Block Service > Hosts Groups.
3. On the AIX application server, scan for LUNs and start the database.
cfgmgr//Scan for mapped logical disks.
show vlun//Query LUN information.
importvg -y prod hdiskX//Import VG information into the ODM library.
mount /dev/prodlv /Oracle//Mount the file system.
Step 8 Use SmartMigration to set up a data migration relationship between source LUNs
(eDevLUN_HDS1 and eDevLUN_HDS2) and target LUNs (eDevLUN_Target_HDS1
and eDevLUN_Target_HDS2).
Navigation path: Choose Services > Resource Tuning >SmartMigration > Create.
NOTE
The preceding operations are performed to set up a data migration relationship between
eDevLUN_HDS1 and eDevLUN_Target_HDS1. To set up a data migration relationship
between eDevLUN_HDS2 and eDevLUN_Target_HDS2, set parameters as follows:
● Source LUN: eDevLUN_HDS2
● Target LUN: eDevLUN_Target_HDS2
● Migration speed: High
Step 9 After data migration is complete, stop services running on the OceanStor Dorado
storage system.
1. Shut down the database and enable the file system to go offline.
2. Remove the OceanStor Dorado storage system and the AIX application server
from their joint zone.
b. Create a host.
Navigation path: Choose SAN Services > Mappings > Hosts > Create.
----End
Procedure
Step 1 Log in to the AIX-based application server.
Step 2 Start the Oracle database and check whether it can successfully start.
su - oracle//Log in as user oracle.
echo $ORACLE_SID//View the current ORACLE_SID.
export ORACLE_SID=XXX//Specify a database instance.
sqlplus /nolog//Run the nolog command to enter the sqlplus environment.
conn as sysdba//Log in to the database as an administrator. (You must obtain the user name and password
of an administrator account.)
startup//Start the current database instance.
lsnrctl start//Start listening. If "Success" is displayed, the database successfully starts.
----End
A
Configuring and Managing
SmartMigration Using CLI Commands
NOTE
For more CLI commands and their description, refer to Command/Event/Error Code
Query.
Procedure Command
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.
A
ASM Automatic Storage Management
C
CPU Central Processing Unit
D
DCL Data Change Log
F
FC Fibre Channel
I
ID Identifier
I/O Input/Output
IP Internet Protocol
iSCSI Internet Small Computer Systems Interface
L
LM LUN Migration
LUN Logical Unit Number
R
RAID Redundant Array of Independent Disks
S
SAN Storage Area Network
V
VVol Virtual Volume
W
WWN World Wide Name