Notice: No part of this publication may be
reproduced or transmitted in any form or by
any means, electronic or mechanical,
including photocopying and recording, or
stored in a database or retrieval system for
any purpose without the express written
permission of Hitachi Data Systems
Corporation (hereinafter referred to as
“Hitachi Data Systems”).
Hitachi Data Systems reserves the right to
make changes to this document at any time
without notice and assumes no responsibility
for its use. Hitachi Data Systems products
and services can only be ordered under the
terms and conditions of Hitachi Data Systems’
applicable agreements. All of the features
described in this document may not be
currently available. Refer to the most recent
product announcement or contact your local
Hitachi Data Systems sales office for
information on feature and product
availability.
This document contains the most current
information available at the time of
publication. When new and/or revised
information becomes available, this entire
document will be updated and distributed to
all registered users.
Hitachi, Hitachi logo, and Hitachi Data
Systems are registered trademarks and
service marks of Hitachi, Ltd. The Hitachi
Data Systems logo is a trademark of Hitachi,
Ltd.
Dynamic Provisioning, Hi-Track, TrueCopy,
ShadowImage, and Universal Star Network
are registered trademarks or trademarks of
Hitachi Data Systems.
All other brand or product names are or may
be trademarks or service marks of and are
used to identify products or services of their
respective owners.
This document describes and provides instructions for using the Universal
Volume Manager software to configure and perform Hitachi Universal Volume
Manager Operations on the Hitachi Universal Storage Platform V and Hitachi
Universal Storage Platform VM storage system.
Please read this document carefully to understand how to use this product,
and maintain a copy for reference purposes.
This preface includes the following information:
Intended Audience
Product Version
Document Revision Level
Changes in this Revision
Document Organization
Referenced Documents
Document Conventions
Convention for Storage Capacity Values
Getting Help
Comments
Notice: The use of Universal Volume Manager and all other Hitachi Data
Systems products is governed by the terms of your agreement(s) with Hitachi
Data Systems.
This document is intended for system administrators, Hitachi Data Systems
representatives, and Authorized Service Providers who are involved in
installing, configuring, and operating the Hitachi Universal Storage Platform V
and Hitachi Universal Storage Platform VM storage systems.
This document assumes the following:
• The user has a background in data processing and understands RAID
storage systems and their basic functions.
• The user is familiar with the Hitachi Universal Storage Platform V and
Hitachi Universal Storage Platform VM storage systems and has read the
Universal Storage Platform V and Universal Storage Platform VM User and
Reference Guide.
• The user is familiar with the Storage Navigator software for the Universal
Storage Platform V and Hitachi Universal Storage Platform VM storage
systems and has read the Storage Navigator User’s Guide.
Product Version
This document revision applies to USP V/VM microcode 60-02-4x and higher.
Document Revision Level
Revision Date Description
MK-96RD626-P February 2007 Preliminary Release
MK-96RD626-00 April 2007 Initial Release, supersedes and replaces MK-96RD626-P
MK-96RD626-01 May 2007 Revision 1, supersedes and replaces MK-96RD626-00
MP-96RD626-02 July 11, 2007 Revision 2, supersedes and replaces MK-96RD626-01
MP-96RD626-03 September 2007 Revision 3, supersedes and replaces MK-96RD626-02
MP-96RD626-04 September 2007 Revision 4, supersedes and replaces MK-96RD626-03
MK-96RD626-05 November 2007 Revision 5, supersedes and replaces MK-96RD626-04
MK-96RD626-06 January 2008 Revision 6, supersedes and replaces MK-96RD626-05
MK-96RD626-07 March 2008 Revision 7, supersedes and replaces MK-96RD626-06
• Added a chapter about spreadsheets (see Using Spreadsheets for Universal
Volume Manager Operations)
• Added descriptions about the spreadsheets in Universal Volume Manager
Operations
.
• Added descriptions about the VMA of Data Retention Utility in VMA of Data
Retention Utility
.
• Added descriptions about the default setting of the cache mode in
Configuring External Volume Attributes.
• Clarified information in Table 5-4 about the operation required before
disconnecting external volumes in
• Added the GET_ALL parameter in Saving Storage System Information.
• Deleted some parameters from Table 6-5 and Table 6-7.
.
Document Organization
The following table provides an overview of the contents and organization of
this document. Click the chapter title
The first page of each chapter provides links to the sections within that
chapter.
If you need to call the Hitachi Data Systems Support Center, be sure to
provide as much information about the problem as possible, including:
• The circumstances surrounding the error or failure.
• The content of any error messages displayed on the host system(s).
• The content of any error messages displayed by Storage Navigator.
• The USP V/VM Storage Navigator configuration information obtained by
using the FD Dump Tool
• The service information messages (SIMs), including reference codes and
severity levels, displayed by Storage Navigator and/or logged at the host.
The Hitachi Data Systems customer support staff is available 24 hours/day,
seven days a week. If you need technical support, please call:
• United States: (800) 446-0744
• Outside the United States: (858) 547-4526
Comments
Please send us your comments on this document. Make sure to include the
document title, number, and revision. Please refer to specific section(s) and
paragraph(s) whenever possible.
• E-mail: doc.comments@hds.com
• Fax: 858-695-1186
• Mail:
Technical Writing, M/S 35-10
Hitachi Data Systems
10277 Scripps Ranch Blvd.
San Diego, CA 92131
Thank you! (All comments become the property of Hitachi Data Systems
Corporation.)
Universal Volume Manager software provides the virtualization of a multitiered storage area network comprised of heterogeneous storage systems. It
enables the operation of multiple storage systems connected to a USP V/VM as
if they were all in one storage system and provides common management
tools and software. The shared storage pool comprised of external storage
volumes can be used with storage system-based software for data migration
and replication, as well as any host-based application. Combined with Hitachi
Volume Migration software, Universal Volume Manager provides an automated
data lifecycle management solution, across multiple tiers of storage.
The key features and benefits of Universal Volume Manager include:
• Universal Volume Manager virtualizes external storage attached to the
USP V/VM storage system
• Enables deployment of multi-tiered storage
• Integrates heterogeneous systems
• Creates pools of storage independent of physical location
• Creates new opportunities based on enhanced capability of existing
business continuity software and management tools to external storage
devices
Unifying Copy Operations between Different Storage
Systems
When you copy data between different storage systems, the copy operations
are usually different depending on the storage system which you use.
If you install Universal Volume Manager, you can perform the following copy
operations in the same way as when you copy data between volumes in the
USP V/VM storage system.
• To copy data between a volume in the USP V/VM storage system and a
volume in an external storage system.
• To copy data between a volume in an external storage system and a
volume in another external storage system.
Without UVM, different copy operations are required.
Storage
Navigator
Computer
External Storage System USP V/VM Storage System
UVM allows you to perform all copy operations in the same way.
Storage
Navigator
Computer
Legend
Volumes installed in the storage system
:
Virtual volumes that do not have physical memory space
:
Copy operation
:
Lines showing the concept of virtualization
:
External Storage System USP V/VM Storage System
Figure 1-1 Unifying Copy Operations between Different Storage
Unifying Connections from a Host to Different Storage
Systems
When a system has multiple storage systems, a host usually needs to connect
all storage systems. When a system administrator configures the connections
from a host to volumes, they need to follow the different instructions
depending on the storage systems.
If you install Universal Volume Manager, a system administrator only needs to
configure the connection from a host to the USP V/VM storage system. After
the configuration is completed, a host can manipulate volumes in the external
storage system in the same way as volumes in the USP V/VM storage system.
Without UVM, a host needs to connect all storage systems.
Host
USP V/VM
Storage System
External Storage System
UVM allows you to unify the connections from a host
to different storage systems.
Host
Legend
USP V/VM
Storage System
Volumes installed in the storage system
:
Virtual volumes that do not have physical memory space
:
Access
:
Lines showing the concept of virtualization
:
External Storage System
Figure 1-2 Unifying Connections from a Host to Different Storage
Universal Volume Manager enables you to use Hitachi storage systems,
original equipment manufacturer (OEM) storage systems, and other vendors'
storage systems (such as IBM or EMC) as connectable external storage
systems. Hosts will recognize these volumes as internal volumes of the
USP V/VM storage system. In this user's guide, the original USP V/VM storage
system is called "local storage system" and a connected storage system is
called the "external storage system".
External volume mapping is required for manipulating external volumes from
local storage system. “Mapping” means assigning the management numbers to
the external volumes. This management numbers are required for
manipulating external volumes from local storage system. By assigning the
management numbers to the external volumes, the system administrator will
be able to manipulate not only internal volumes of local storage system but
also external volumes using Storage Navigator. The management numbers
consist of "external volume group number - sequential number" (Example: E21, E50-3).
Figure 2-1 shows the idea of connection between a local storage system and
an external storage system which are connected by the Universal Volume
Manager function. In the
to the external port of the local storage system via a switch using the fibrechannel interface. The external port is a kind of port attribute, which is used
for Universal Volume Manager. In the
mapped as internal volumes.
Figure 2-1, the external storage system is connected
Figure 2-1, the external volumes are
Notes:
•Make sure that you do not access the external volume, which has been
mapped as an internal volume, from the host that is connected to the
external storage system. Also make sure that you do not access the
mapped external volume using the function (e.g., copy function) of the
external storage system. Once you have mapped an external volume as an
internal volume, you have to access the mapped external volume only from
the local storage system side.
•From the host, you can access the external storage system volumes that
have not been mapped as the internal volumes. There is no restriction.
Before using Universal Volume Manager, connect the fibre channel port of the
local storage system to the external storage system port with the fibre cable.
The route between ports, which is connected with the cable, is called the
"cross-subsystem path".
The fibre channel port of the local storage system is set to connect to the host
by default. The fibre channel port can be connected to an external storage
system if you change the attribute of the fibre channel port so that it is an
external port, which can be connected to an external storage system. The
external storage system port can be a target port, which can be connected to
a host.
To manipulate Universal Volume Manager, you need to install Universal
Volume Manager by using the license key. Use your Storage Navigator
computer to access the local storage system via SVP (web server) and perform
the Universal Volume Manager operations.
Volumes and Mapping Paths
Volumes in the external storage system (see C in Figure 2-2) are called
"external volumes". Mapping is necessary to manipulate an external volume
from the local storage system. The system administrator maps an external
volume as an internal volume (see B in
After the mapping, you can manipulate the external volume from the local
storage system in the same way as manipulating an internal volume.
Figure 2-2) in the local storage system.
Note: When external volumes in external storage systems are mapped as
internal volumes in your USP V/VM storage systems, the external volumes can
be accessed and copied by hosts connecting to your USP V/VM storage
systems, but not by hosts connecting to the external storage systems.
This document sometimes uses the term "an external volume" or "a mapped
external volume" to mention an internal volume where an external volume is
mapped (see B in
representation of an external volume.
When you perform mapping, a path is automatically created between an
internal volume and an external volume. This path is called "a mapping path",
which connects one volume with another volume. A cross-subsystem path is a
part of a mapping path.
About Universal Volume Manager Operations 2-5
Figure 2-2), because this internal volume is a virtual
To use the external volumes, which you mapped as an internal volume (see B
in
Figure 2-2), from the host or other program products, the system
administrator needs to create LDEVs in the external volume (see A in
Figure
2-2). To create LDEVs, use Universal Volume Manager at the time of mapping,
or use VLL function to an internal volume where an external volume is mapped
after mapping. The LDEVs created by these methods are called “LDEVs in the
external volume” in this document. These LDEVs are usually called “external
volumes” in other documents.
An external volume corresponds to a VLL VDEV (Virtual Device). An LDEV in
the external volume corresponds to a VLL LDEV. Therefore, you can use VLL
function to create custom-sized volumes in an external volume after mapping,
in the same way as creating custom-sized volumes in the normal internal
volumes. For details on VDEVs and LDEVs, see the Virtual LVI/LUN and Volume Shredder User's Guide.
Universal Volume Manager enables you to execute the following operations.
• Preparing to use external volumes
You can map external volumes, set port attributes, and set crosssubsystem paths.
• Preparing to manipulate the power supply of the storage systems
You must follow specific procedures if you want to manipulate the power
supply of the storage systems when external volumes are used. To turn on
or off the power supply of the external storage system after starting to use
the external volumes, you need to execute the commands of Universal
Volume Manager.
• Setting up and removing the cross-subsystem paths
When you set up or remove the path (cable) connecting the storage
systems, you need to use the Universal Volume Manager to make settings
on the path.
• Referring to the status of external volumes
You can refer to the status and the configuration of external volumes.
• Stopping the use of external volumes
You can cancel mapping of external volumes.
• Mapping external volumes by using spreadsheets
Universal Volume Manager supports the Configuration File Loader
spreadsheets. Spreadsheets allow you to configure the mapping of multiple
external volumes at one time, which is efficient when mapping a large
number of volumes.
• Setting the remote command device
By using the remote command device, you can manipulate volumes in the
external storage system from the Command Control Interface on host
computers.
Before configuring the Universal Volume Manager settings, you need to answer
the following:
• Which ports can be connected to external storage systems
• Which external storage system and volumes should be mapped as the
internal volumes
• How to configure external volume groups
• What external volume attributes to be configured
• How to configure cross-subsystem paths
• How to make volume usable from the local storage system
Choosing External Port
The port used for Universal Volume Manager must be set as the external port.
When the external storage system is connected to the external port of the
local storage system, you can view the information on the external storage
system from the Storage Navigator computer. The external storage system
cannot be connected to the ports other than the external port.
In order to set the port attribute to external, the LU paths set to the port must
be released. The attribute of the port where the LU paths are already set
cannot be changed to external. Therefore, you must identify ports whose
attributes can be changed to external before starting the Universal Volume
Manager operations.
Note: The ports whose attributes are set for remote copy software (e.g., RCU
target, initiator) or other features cannot be used as external ports for
Universal Volume Mana
the port attribute is set to other than external.
er. In addition, change the port attribute to external if
Choosing and Mapping External Volumes
When you connect an external storage system to an external port, volumes in
the external storage system (external volumes) become available for mapping
as volumes in the local storage system (internal volumes). Identify the
volumes in each external storage system that should be mapped as internal
volumes.
• You cannot access the data that is stored in an external volume beyond the
For example, if an external volume of 100 GB was mapped as an internal
volume of 70 GB, then 30 GB of the external volume would not be
accessible from the local storage system side.
• You cannot map an external volume whose capacity is smaller than the
minimum available capacity.
For example, you cannot map an external volume of 10 GB as an internal
volume which requires at least 30 GB.
The maximum or minimum available capacity of an external volume depends
on the emulation type that is set when the volume is mapped.
Registering a Volume to an External Volume Group (ExG)
When you map an external volume as an internal volume, you need to register
the external volume to an external volume group.
External volumes, which are set by Universal Volume Manager, can be
classified into groups by usage. Any group of this type is called an external
volume group (ExG). For instance, you can register multiple volumes in one
external storage system to one external volume group. Or you can register the
volumes in one external volume group and manage them in block, even
though the data you want to manage in a lump is stored in volumes in the
different external storage systems.
You need to assign numbers to external volume groups.
Configuring External Volume Attributes
When you map an external volume as an internal volume, you set the
attributes of the external volume. External volume attributes can be set using
the mapping policy or the Set External Volume Parameter dialog box of the
Universal Volume Manager.
The attributes of the external volume are as follows:
• Emulation type
Select an emulation type for the mapped external volume from the dropdown list.
The emulation type OPEN-V must be selected if, after the mapping, you
are planning to use the existing data in the external volume from the local
storage system. For example, if you want to migrate the existing data in
the external volume to the local storage system volume, you have to set
the OPEN-V emulation type when the external volume is mapped.
If you select the emulation type other than OPEN-V, the volume requires a
specific area provided for management data. Once this area is provided,
volume capacity after the mapping becomes less than the actual external
volume capacity for the area (volume).
Cache mode specifies whether the write data from the host to the external
storage system is propagated synchronously (Disable) or asynchronously
(Enable). By default, cache mode is set to Enable. All I/O to and from the
local storage system (either Enable or Disable) always uses cache. Write
operations are always backed up in duplex cache.
– If you select Enable, after receiving the data into the local storage
system cache memory, the local storage system signals the host that
an I/O operation has completed and then asynchronously destages the
data to the external storage system.
– If you select Disable, the local storage system signals the host that an
I/O operation has completed only after the local storage system has
synchronously written the data to the external storage system.
If you perform the Cache Residency Manager operation on the external
volume, which the Cache Mode is set to Disable, the bind mode of
Cache Residency Manager cannot be specified. For the Cache Residency
Manager operation, see the Cache Residency Manager User’s Guide.
Note: When you set the cache mode, note the following:
•Data that is not written by the host (for example, data written by
ShadowImage) is asynchronously destaged to the external storage
system regardless of the Cache Mode setting.
•If you set the emulation type for a mainframe system (such as 3390x), data that is written by a host using a command such as Format
Write is asynchronously destaged to the external storage system
regardless of the Cache Mode setting. Data that is written by a host
using a command such as Update Write is destaged to the external
storage system as configured in the Cache Mode setting.
•Inflow Control (Enable or Disable)
Inflow control specifies whether the writing operation to the cache memory
is stopped (Enable) or continued (Disable) when the writing operation to
the external volume is impossible. By default, inflow control is set to
Disable.
– If you select Enable, the writing operation to cache is stopped and the
I/O from the host is not accepted when the writing operation to the
external volume is impossible.
– If you select Disable, the I/O from the host during the retry operation
is written to the cache memory even after the writing operation to the
external volume is impossible. Once the writing operation to the
external volume becomes normal, all the data in the cache memory is
written to the external volume (all the data is destaged).