Hewlett-Packard Company makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties
of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be liable for errors contained herein or for incidental or
consequential damages in connection with the furnishing, performance, or use of this material.
This document contains proprietary information, which is protected by copyright. No part of this document may be photocopied,
reproduced, or translated into another language without the prior written consent of Hewlett-Packard. The information is provided “as is”
without warranty of any kind and is subject to change without notice. The only warranties for HP products and services are set forth in the
express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an
additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.
BSAFE is a registered trademark or trademark of RSA Security Inc. in the United States and/or other countries.
Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States
and other countries.
Microsoft is a registered trademark of Microsoft Corp. in the U.S. and other countries.
Microsoft Internet Explorer is a product name of Microsoft Corp.
Mozilla is a trademark of the Mozilla Foundation in the U.S and other countries.
Netscape is a registered trademark of Netscape Communications Corporation in the United States and other countries.
RC2 is a registered trademark or trademark of RSA Security Inc. in the United States and/or other countries.
RC4 is a registered trademark or trademark of RSA Security Inc. in the United States and/or other countries.
RSA is a registered trademark or trademark of RSA Security Inc. in the United States and/or other countries.
HP StorageWorks XP Tiered Storage Manager includes RSA BSAFE Cryptographic software from RSA Security Inc.
Solaris is a trademark or registered trademark of Sun Microsystems, Inc. in the United States and other countries.
All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc., in the United
States and other countries. Products bearing SPARC trademarks are based upon an architecture developed by Sun Microsystems, Inc.
Sun is a trademark or registered trademark of Sun Microsystems, Inc. in the United States and other countries.
VERITAS Cluster Server is a product name of VERITAS Software Corporation in the United States and other countries.
Windows is a registered trademark of Microsoft Corp. in the U.S. and other countries.
Windows Server is a registered trademark of Microsoft Corp. in the U.S. and other countries.
This product includes software developed by the Apache Software Foundation (http://www.apache.org/).
This product includes software developed by Ben Laurie for use in the Apache-SSL HTTP server project.
This product includes software developed by Ralf S. Engelschall <rse@engelschall.com> for use in the mod_ssl project
(http://www.modssl.org/).
HP StorageWorks XP Tiered Storage Manager User Guide
1-1-4 Using the External Storage Connection Function .......................................................................... 13
1-1-5 Using HTSM With Clients ............................................................................................................... 13
1-2 Deciding When to Migrate Data ................................................................................................................13
1-2-1 When the Importance of Data Changes ......................................................................................... 13
1-2-2 When Improving Storage Performance ..........................................................................................14
1-2-3 When the Storage Environment Changes ...................................................................................... 16
1-3 How Migration Works ................................................................................................................................ 17
1-4 Methods of Migration................................................................................................................................. 18
1-4-1 Migration within a Domain Control Storage Subsystem ................................................................. 18
1-4-2 Migration Between Domain Control Storage and External Storage Subsystems........................... 19
1-4-3 Migration Between Two External Storage Subsystems.................................................................. 19
1-5 Required Components of Migration........................................................................................................... 20
1-6 Users of Tiered Storage Manager ............................................................................................................. 21
1-6-1 User Types for Tiered Storage Manager........................................................................................ 21
1-6-2 Changing User Information............................................................................................................. 21
1-6-3 Using Tiered Storage Manager with PSAs ..................................................................................... 22
1-7 Performing a Refresh ................................................................................................................................ 22
1-7-1 How Refresh Works........................................................................................................................ 22
1-7-2 When to Perform a Refresh............................................................................................................ 23
1-7-3 Refresh Types and Scopes ............................................................................................................23
1-7-4 Refresh Status Information............................................................................................................. 24
1-7-5 Using Refresh to Detect Inconsistencies........................................................................................ 24
1-8 Volumes Used for Migration ......................................................................................................................25
2 Getting Started with the GUI
2-1 Preparing for GUI Operations.................................................................................................................... 28
2-2 Guidelines for Using Tiered Storage Manager GUI................................................................................... 29
2-3 Logging Into Tiered Storage Manager....................................................................................................... 29
2-3-1 Logging In from the Login Dialog Box ............................................................................................29
2-3-2 Logging In from another Command View XP AE Suite Software ................................................... 30
2-4 Logging Out of Tiered Storage Manager................................................................................................... 30
4-3 Creating a Storage Tier by Selecting Storage Tiers Object from a Storage Domain ................................39
4-4 Creating a Storage Tier Based on Results of a Storage Domain Volume Search ....................................42
5 Applying Filter Conditions
6 Creating a Migration Group
6-1 About Migration Groups ............................................................................................................................ 49
6-2 Creating a Migration Group by Selecting Object in a Storage Domain .....................................................49
6-3 Creating a Migration Group based on Storage Domain Volume Searches............................................... 51
Contents 3
6-4 Creating a Migration Group based on a Storage Tier Volume Search...................................................... 53
7 Performing a Migration
7-1 About Migration Tasks............................................................................................................................... 57
7-1-1 Attributes of Migration Tasks .......................................................................................................... 57
7-1-2 Status of Migration Tasks ............................................................................................................... 57
8-6 Deleting a Storage Domain ....................................................................................................................... 69
9 Managing Storage Tiers
9-1 Viewing a List of Storage Tiers.................................................................................................................. 70
Figure 1-1 Scope of Data Eligible for Migration ......................................................................................................... 12
Figure 1-2 Data Migration according to Life Cycle Management............................................................................... 12
Figure 1-3 Migration Suited to the Life Cycle of Data ................................................................................................14
Figure 1-4 Migration in the Domain Controller ...........................................................................................................14
Figure 1-5 Migrating Data to Redistribute Access Load (before migration) ............................................................... 15
Figure 1-6 Migrating Data to Redistribute Access Load (after migration) .................................................................. 15
Figure 1-7 Migration by Rearranging Storage Subsystems ....................................................................................... 16
Figure 1-8 Migration from an External Storage Subsystem to the Domain Controller ............................................... 16
Figure 1-9 Migration Between Two External Storage Subystems ............................................................................. 17
Figure 1-10 Relationship between Volumes and LDEV Numbers ............................................................................18
Figure 1-11 Migration within a Domain Control Storage Subsystem .........................................................................19
Figure 1-12 Migration Between Domain Control Storage Subsystem and External Storage Subsystem .................. 19
Figure 1-13 Migration Between Two External Storage Subsystems.......................................................................... 20
Figure 1-14 Migration of LUSE Configuration ............................................................................................................27
Figure 2-1 Tiered Storage Manager Main Window ....................................................................................................30
Figure 2-2 Main Window with List Objects Subwindow ............................................................................................. 31
Figure 2-4 Information Frame with Subwindow ......................................................................................................... 33
Figure 7-1 Executing a Migration Task on Tiered Storage Manager clients .............................................................. 58
Figure 7-2 Migration and Operations at a Web client ................................................................................................ 59
Figure 7-3 List Objects-Migration Groups Subwindow............................................................................................... 60
Figure 7-4 Migrate-Step 1 of 4 Pop-up Window......................................................................................................... 60
Figure 7-5 Migrate-Step 2 of 4 Pop-up Window......................................................................................................... 61
For additional product information, see the following web sites:
• http://www.hp.com
• http://www.hp.com/go/storage
• http://www.hp.com/support/
About this guide 9
Revision history (start here)
Revision tables
Table 2 Revisions
Date Edition Revision
November 1, 2005 First
About this guide 10
1 Using Tiered Storage Manager
This chapter explains the features of Tiered Storage Manager, describes the objects and timing associated with
migration (which is a main function of Tiered Storage manager), lists volume filter conditions, and documents
the procedure for refresh operations.
• Functions of Tiered Storage Manager (section
• Deciding When to Migrate Data (section
• How Migration Works (section
• Methods of Migration (section
• Required Components of Migration (section
• Users of Tiered Storage Manager (section 1-6 )
• Performing a Refresh Operation (section
• Volumes Used for Migration (section
1-2-3 )
1-4 )
1-8 )
1-1 Functions of Tiered Storage Manager
Tiered Storage Manager is designed to relocate (migrate) data from one volume on a storage subsystem to
another volume. You can migrate data simply by specifying the relocation destination. (Tiered Storage
Manager does not migrate data to a tape device.) See
migrate using Tiered Storage Manager.
1-1 )
1-2 )
1-5 )
1-7 )
Figure 1-1 for an illustration of the scope of data you can
Using Tiered Storage Manager offers the following advantages:
• You can migrate data without interrupting the current application.
• You can migrate data without being aware of the storage configuration.
• You can migrate multiple volumes at once.
• You can reduce the preparation time for a migration.
• You can use multiple storage subsystems as though they were a single storage subsystem and centrally
manage different types of storage environments, since Tiered Storage Manager uses the StorageWorks
XP12000/10000.
•You can migrate data in line with the concept of Data Lifecycle Management (DLCM) so that data used
frequently is stored in high-performance storage and data used less frequently is stored in lowperformance storage. See
Figure 1-2 for an illustration of migrating data according to DLCM.
Using Tiered Storage Manager 11
Figure 1-1 Scope of Data Eligible for Migration
Figure 1-2 Data Migration according to Life Cycle Management
1-1-1 Migrating Data without Interrupting Your Current Application
When you use Tiered Storage Manager to migrate data, you do not have to be aware of changes to the storage
configuration or to the volume containing the data being migrated. You can access the migrated data in the
same way as before migration. Even during migration, you do not have to interrupt an application.
12
1-1-2 Grouping and Migrating Volumes
You can define a group of storage volumes in advance, so that they are migrated at the same time. By giving
the group an appropriate name , and by setting an explanation of the group as an attribute, you can easily
identify the group of volumes to be migrated.
You can also prevent a group of volumes from migrating accidentally by disabling migration for that group.
1-1-3 Defining Migration Target Volumes
You can define a group of target volumes in advance for a particular purpose, such as access speed, reliability
or bit cost. In response to a request from a user, you can also migrate data whose usage value has dropped
from a high-performance storage subsystem to a low-performance storage subsystem. You can select the
group you need when you are migrating data to suit your specific requirements without having to specify any
detailed conditions. Such volume groups can be created, for example, on a storage subsystem, CLPR, or array
group basis.
1-1-4 Using the External Storage Connection Function
Using the external storage connection function of StorageWorks XP12000/10000, you connect to various types
of storage subsystems using fiber channels, thereby integrating the subsystems into a single virtual storage
subsystem. You select volumes within this storage subsystem as the migration source or target. This means
you can migrate data without worrying about the different types of storage subsystems.
1-1-5 Using HTSM With Clients
You can use Tiered Storage Manager with two types of clients:
•Web client: This client enables you to operate Tiered Storage Manager on a browser. For details about
the window, click the Help button on the window and refer to the displayed Tiered Storage Manager GUI
Help.
•Command Line Interface (CLI) client: This client directly operates the command line, so you can batch
operations such as migration. Refer to the HP StorageWorks XP Tiered Storage Manager CLI Reference Guide for details.
1-2 Deciding When to Migrate Data
Migrating data helps increase the efficiency of an entire storage system. You can decide to migrate data:
• When the importance of data changes
• When storage performance needs to be improved
• When the storage environment changes
Tiered Storage Manager migrates data between storage subsystems.
NOTE: In this manual, the term domain controller refers to the following products
•
StorageWorks XP12000/10000
•StorageWorks XP10000
1-2-1 When the Importance of Data Changes
You can migrate data in line with the concept of Data Lifecycle Management (DLCM), so that data used
frequently is stored in high-performance, high-price storage and data used less frequently is stored in lowperformance, low-price storage. You can migrate data between high- and low-performance storage
subsystems, depending on how often it is used.
Using Tiered Storage
Manager
Figure 1-3 illustrates migration according to the life cycle of data.
13
Figure 1-3 Migration Suited to the Life Cycle of Data
1-2-2 When Improving Storage Performance
You can migrate data to improve storage performance if multiple volumes with high-access frequency in the
same array group become overloaded, if a storage subsystem reaches a bottleneck, or if data outlives the life
of the storage system.
Migration in a domain controller is illustrated by
Figure 1-4 Migration in the Domain Controller
Figure 1-5 and Figure 1-6 illustrate migrating data to redistribute access load and improve storage
performance.
Figure 1-4
14
Figure 1-5 Migrating Data to Redistribute Access Load (before migration)
Using Tiered Storage
Manager
Figure 1-6 Migrating Data to Redistribute Access Load (after migration)
Figure 1-7 illustrates migrating data by rearranging the storage subsystems.
15
Figure 1-7 Migration by Rearranging Storage Subsystems
After you have installed a higher performance storage subsystem, you can migrate data with a high usage
frequency to high-performance storage.
Figure 1-8 illustrates migration from an external storage subsystem to the domain controller.
Figure 1-8 Migration from an External Storage Subsystem to the Domain Controller
1-2-3 When the Storage Environment Changes
When data is to be held for a long period, the storage subsystem may reach the end of its life cycle before the
data does.
In this case, you can migrate the data to a different storage subsystem before the first storage subsystem
reaches the end of its life cycle.
16
Figure 1-9 Migration Between Two External Storage Subystems
1-3 How Migration Works
Tiered Storage Manager allows you to migrate data located on a volume within the scope eligible for migration
without being aware of the change in LDEV number. After performing a migration, Tiered Storage Manager
changes the LDEV number automatically so that you do not have to change the access path to the host, which
prevents any interruption of an application service. Tiered Storage Manager migrates data in units of volumes.
You can migrate data between any storage subsystems as long as they are within the migration scope.
Migration consists of five processing steps:
1. After you create a migration task, you reserve a migration target volume. The reserved volume is not
accessible from a host.
2. When the execution of a migration task starts, Tiered Storage Manager copies data from the migration
source volume to the migration target volume
3. Tiered Storage Manager switches the LDEV number of the migration source volume with the LDEV
number of the migration target volume. A volume reservation is performed for an LDEV number. Thus,
the volume reservation moves from the migration source volume to the migration target volume just as
the LDEV numbers are switched
4. The volume reservation is removed. A volume reservation is also removed when a migration task is
canceled, or a migration task fails to execute. If removal of the volume reservation fails, refresh the
storage domain to remove it.
5. Tiered Storage Manager erases the data from the migration source volume when you select that option.
Figure 1-10 shows the relationship between volumes and LDEV numbers in volume reservation, LDEV number
switching, and data erasure
Using Tiered Storage
Manager
17
Figure 1-10 Relationship between Volumes and LDEV Numbers
1-4 Methods of Migration
This section describes three methods of migration:
• Migration within a domain control storage subsystem.
• Migration between a domain control storage subsystem and an external storage subsystem.
• Migration between two external storage subsystems.
1-4-1 Migration within a Domain Control Storage Subsystem
You can migrate data within a control storage subsystem to distribute access load, as shown in Figure 1-11
below.
18
Figure 1-11 Migration within a Domain Control Storage Subsystem
1-4-2 Migration Between Domain Control Storage and External Storage
Subsystems
You can migrate data from a domain control storage subsystem to an external storage subsystem, or from an
external storage subsystem to a domain control storage subsystem. You do this when a high-performance
storage subsystem has been added. Figure 1-12 illustrates this method of migration.
Figure 1-12 Migration Between Domain Control Storage Subsystem and External Storage Subsystem
1-4-3 Migration Between Two External Storage Subsystems
You can migrate data between two external storage subsystems connected to separate domain control storage
subsystems. You do this when an external storage subsystem is full.
migration.
Figure 1-13 illustrates this method of
Using Tiered Storage
Manager
19
Figure 1-13 Migration Between Two External Storage Subsystems
1-5 Required Components of Migration
The following four components are required for migration in Tiered Storage Manager. Table 1-1 describes
these components and their related operations and refers you to chapters or sections in this manual where you
can find more detailed information.
Table 1-1 Required Migration Components
Required Component Operation Chapter or Section
Storage domain
Refers to either a domain control
storage subsystem, or a domain
control storage subsystem connected
to an external storage subsystem.
You can create only one storage
domain for each domain control
storage subsystem. You can migrate
data only between volumes in the
same storage domain.
Storage tier
A group of volumes that serve as
migration targets. When you migrate
data, you select a migration target
volume from a specified storage tier.
Migration group
A group of volumes you migrate at
the same time.
Migration task
Moving data from the source volume
to the target volume for each volume
in a migration group. Created by
linking a migration source volume in
the migration group with a migration
target volume in the storage tier and
specifying options.
IMPORTANT: Whenever you change storage configurations or migrate data using Tiered Storage
• Deleting a migration task
• Canceling a migration task before executing it
Manager, you must perform a refresh. Refresh is an operation that updates your information. (For more
information, see Section
1-7 ).
1-6 Users of Tiered Storage Manager
This section describes:
• User Types for Tiered Storage Manager.
• Changing User Information.
• Using Tiered Storage Manager with PSA Administrators.
1-6-1 User Types for Tiered Storage Manager
Tiered Storage Manager includes three levels of users (see Table 1-2 for a list of Tiered Storage Operations
and related users):
• System Administrator: Can access all functions and resources on Tiered Storage Manager.
• Storage Administrator: Configures and manages the storage subsystems. Can access all functions and
resources on Tiered Storage Manager.
•Guest: Can reference the resources of Tiered Storage Manager.
11-5
NOTE: Tiered Storage Manager includes the same types of users as Device Manager. For more
information, refer to the HP StorageWorks Command View XP Advanced Edition Device Manager Web Client User Guide.
1-6-2 Changing User Information
When using Device Manager, and you want to change the user ID or password for accessing Device Manager
that was specified when installing Tiered Storage Manager, execute the Tiered Storage Manager command for
changing user information (htsmmodhdvmuser). This command can be executed by a System Administrator or
Storage Administrator when Device Manager is active. For details about the command for changing user
information (htsmmodhdvmuser), see the manual HP StorageWorks XP Tiered Storage Manager Server Installation and Configuration Guide.
Table 1-2 Tiered Storage Manager Operations and Related User Types
Operation
Storage domain Create Y N
Reference List Y Y
Reference Properties Y Y
Change Attribute
Information
Refresh Y N
Delete Y N
Storage tier Create Y N
Reference List Y Y
Reference Properties Y Y
Change Attribute
Information
Delete Y N
Migration group Create Y N
Reference List Y Y
Reference Detailed
Information
Add Volume Y N
System Administrator or
Storage Administrator
Y N
Y N
Y Y
Guest
21
Tiered Storage
ge
Table 1-2 Tiered Storage Manager Operations and Related User Types
Operation
Delete Volume Y N
Change Attribute
Information
Delete Y N
Migration task Create Y N #
Reference Detailed
Information
Reference Search List Y Y
Execute Y N
Delete Y N
Cancel Y N
Legend:
Y ― Can operate N ― Cannot operate
# ― On a CLI client, you can create a migration task even when the user type is Guest.
System Administrator or
Storage Administrator
Y N
Y Y
1-6-3 Using Tiered Storage Manager with PSAs
Logical Partition (LPAR) is the generic name for the Cache Logical Partition (CLPR) and Storage Logical
Partition (SLPR) functions.
Tiered Storage Manager uses an SLPR administrator in addition to the administrator for the entire storage
subsystem. The SLPR administrator is called the Partition Storage Administrator (PSA).
In some cases, when a Device Manager user registered in Storage Navigator as a partition storage
administrator (PSA) adds a domain controller to Device Manager, the domain controller added to Device
Manager is called a domain controller for which the PSA is managing SLPR operations.
A domain controller for which the PSA is managing SLPR operations cannot be used as a storage domain for
Tiered Storage Manager.
Guest
Do not change a domain controller that Storage Administrator has registered in Tiered Storage Manager to a
domain controller for which the PSA is managing SLPR operations on Device Manager. In addition, in the
storage subsystem that performs LPAR operations, a candidate for the migration target volume is selected
from within the LPAR to which the migration source volume belongs. In a domain controller managed by the
Storage Administrator, a migration can be performed for volumes that have overlapping LPARs.
For details on the CLPR and SLPR, see the manual HP StorageWorks Command View XP Advanced Edition Device Manager Web Client User's Guide or the Virtual Partition Manager User's Guide.
1-7 Performing a Refresh
When you change storage configurations or finish performing a migration, you must update —meaning refresh
— information to reflect the latest status. You can view the latest refresh date and time in the List Objects –
Storage Domain Name subwindow of the Web client. You cannot perform most Tiered Storage Manager
operations during a refresh. This section describes the refresh operation, including:
• How Refresh Works
• When to Perform a Refresh
• Refresh Types and Scopes
• Refresh Status Information
• Using Refresh to Detect Inconsistencies
1-7-1 How Refresh Works
Performing a refresh takes time because it updates repositories and cache information.
The repositories are databases that manage setup information for Tiered Storage Manager, Device Manager,
and Command View XP AE Suite Common Component. The repositories are managed by Command View XP
AE Suite Common Component.
The repository types are:
•Repository for Tiered Storage Manager: Manages information defined for migration and the status of the
Tiered Storage Manager server.
22
•Repository for Device Manager: Manages system and hardware information about storage subsystems
managed by Device Manager.
•Repository for Command View XP AE Suite Common Component: Common to all Command View XP AE
Suite software. It manages data displayed in display areas common to Web client series products. If a
Web client or CLI client gives an instruction to perform a refresh, this repository does not change.
The cache is information that is imported from the Device Manager repositories to a database (repository) for
Tiered Storage Manager.
1-7-2 When to Perform a Refresh
You must perform a refresh:
• After changing logical device or hardware configurations (see section
• After registering or performing a migration task (see section
NOTE: Tiered Stored Manager automatically performs a refresh when you add or delete a storage domain.
You cannot perform a refresh:
• If a storage domain is managed with PSA permissions (an error message displays).
• During another operation, including another refresh (an error message displays).
NOTE: It takes some time to refresh the Tiered Storage Manager storage domain because the refresh
operation updates the database (repositories).
1-7-2-2 ).
1-7-2-1 After Changing Logical Device or Hardware Configurations
1-7-2-1 ).
If you do not perform a refresh after changing configurations, data will be migrated to the wrong location.
Example:
a. LDEV 2:01 is externally connected to StorageWorks XP1024.
b. A refresh is performed by using Tiered Storage Manager.
c. The external connection target of 2:01 is changed to StorageWorks XP512 by using Remote Web
Console.
d. 2:01 is migrated by using Tiered Storage Manager.
In the Web client display, 2:01 still matches StorageWorks XP1024. The migration target of 2:01 still
appears to be StorageWorks XP1024. However, migration to StorageWorks XP512 has actually been
performed.
1-7-2-2 After Registering or Performing a Migration Task
If you do not perform a refresh after registering or performing a migration task, an error might occur in the
subsystem.
NOTE: After you perform a refresh, the latest refresh data and time display in the List Objects – Storage
Domain Name subwindow. The information in the navigation frame is also updated.
1-7-3 Refresh Types and Scopes
There are four refresh operation types:
• Refresh to synchronize information in the storage subsystems with the repository for Device Manager
• Refresh to synchronize the repository for Device Manager with the repository for Tiered Storage Manager
• Refresh to synchronize the repository for Tiered Storage Manager with the HiCommand common
repository
•Refresh to synchronize the HiCommand common repository with the browser
Performing a refresh to synchronize information in the storage subsystems with the repository for Device
Manager
This refresh synchronizes information in the storage subsystems with the storage subsystem configurations
held by Device Manager.
If an attempt is made to refresh Tiered Storage Manager when an inconsistency exists between the
information in the storage subsystems, the storage configuration information held by Device Manager,
and the storage configuration information held by Tiered Storage Manager, a message asking whether
you want to refresh Device Manager is displayed. Click the OK button if you want to refresh Tiered
Storage Manager and Device Manager.
23
The refresh scope of Device Manager is the domain controllers that contain the storage domain that is the
refresh target of Tiered Storage Manager.
For details on performing a refresh to synchronize information in the storage systems with the repository
for Device Manager, see 1.6.4 Refreshing Device Manager Repositories.
Performing a refresh to synchronize the repository for Device Manager with the repository for Tiered Storage
Manager
This refresh synchronizes the storage subsystem configurations held by Device Manager with the storage
subsystem configurations held by Tiered Storage Manager.
This refresh is executed when a storage subsystem configuration (such as an LDEV configuration) is
changed in Device Manager or Remote Web Console. The refresh scope is the migration target storage
domain.
The refresh is the Refresh displayed in the method frame (Web client) or a refresh executed by the
Refresh command (CLI client).
Performing a refresh to synchronize the repository for Tiered Storage Manager with the Command View XP AE
Suite Common Component repository
This refresh synchronizes the storage domain and storage tier objects held by Tiered Storage Manager
with the Tiered Storage Manager objects (for tree display) held in the Command View XP AE Suite
Common Component repository.
A refresh is automatically executed when the Tiered Storage Manager server starts. When the Tiered
Storage Manager server is abnormally terminated during update processing of the repository for
Command View XP AE Suite Common Component, all storage domains in Tiered Storage Manager are
refreshed.
Performing a refresh to synchronize the HiCommand common repository and the browser
This refresh synchronizes the Tiered Storage Manager objects (for tree display) held in the Command
View XP AE Suite Common Component repository with the tree displayed by the browser.
Execute this refresh by choosing Refresh in the menu bar frame. The refresh scope is the added storage
domain.
1-7-4 Refresh Status Information
When you have created or deleted a storage domain, Tiered Storage Manager automatically refreshes
information. At this time, there are four possible refresh statuses:
•Status in which a refresh has not been performed: Indicates the status immediately after creating a
storage domain (before performing a refresh). After creating a storage domain, Tiered Storage Manager
automatically performs a refresh. If the automatic refresh fails, perform another refresh.
•Normal status (refresh-successful status): Indicates that the refresh was successful and that the
repository and cache are normal.
• Refresh in progress status: Indicates that a refresh is being performed.
• Cache abnormal status (refresh-failed status): Indicates that the refresh failed due to an error and that the
status of the repository or cache is abnormal.
1-7-5 Using Refresh to Detect Inconsistencies
If an error occurs in the network or storage device when a migration task is created, performed, or cancelled,
the following three types of information may become inconsistent:
• Information within the storage subsystems
• The repository for Device Manager
• The repository for Tiered Storage Manager
You can detect these inconsistencies, by refreshing the information after migration finishes (the status of the
migration task is Success, Failure, or Cancel.). If you try to refresh Tiered Storage Manager while the
repository is inconsistent, a message asking whether you want to refresh Device Manager is displayed. Click
OK if you want to refresh Tiered Storage Manager and Device Manager.
24
The refresh scope on Device Manager is the domain controllers that make up the storage domain that is the
refresh target on Tiered Storage Manager.
1-8 Volumes Used for Migration
Migration source and target volumes must satisfy the following conditions in a migration using Tiered Storage
Manager:
• The emulation types of the migration source volumes and migration target volumes match.
• The sizes of the migration source and migration target volumes match.
The emulation types of the migration source volumes and the migration target volumes are not OPEN-V,
but the volumes are both CVS or both normal.
You can check the emulation type and size of a volume in the Volume Detailed Information – Device Number
popup window. For details on this window, see the GUI Help.
•Volumes that cannot be migrated
For volumes that cannot be migrated, you can check the status from the Volume Detailed Information Device Number pop-up window - Can Migrate or Volume Status.
Can Migrate
When Yes is specified for Can Migrate, you can perform migration using the volume as a source
volume.
When No is specified, you cannot perform migration using the volume as a source volume. An error
occurs when you click the Migration button.
Volume Status
When Unused is specified for Volume Status, it is available as a source target.
When Used is specified, the volume will not be displayed as a candidate for the migration target
volume.
When No is specified for Can Migrate, or Used is specified for Volume Status, the reasons are displayed in
Reasons that a volume cannot become source/target volume in the Volume Detailed Information - Device
Number pop-up window. For details on the character strings to be displayed and their descriptions, see Table
1.5 Character Strings Representing Reasons a Volume Cannot Be a Migration Source or Target, and a
Description of those Character Strings.
•Volumes that cannot be checked for migration suitability
The following volumes cannot be checked for suitability by using Can Migrate or Volume Status. An error
occurs when executing a migration task with these volumes selected as a source volume. Also, an error
occurs when creating a migration task that has these volumes selected as migration target volumes.
• A volume that makes up a Cross-system Copy pair
• A volume that is the target of XRC (Extended Remote Copy, which is the IBM remote copy function)
• A volume that is the target of Concurrent copy
• A volume that cannot be accessed because it has a blocked status or is being formatted
An error occurs when executing a migration task using the following volumes together:
• For a migration source volume: volume made up of a TrueCopy pair
• For a migration target volume: externally connected volumes
• Information displayed as reasons that a volume cannot be a migration source or target
When migration suitability checks can be performed from Tiered Storage Manager, if volumes are
determined to be unsuitable as a migration source or target, the reasons are displayed in Reasons that a
volume cannot become source/target volume in the Volume Detailed Information - Device Number pop-up
window.
The following table shows the character strings representing the reasons that a volume cannot be a
migration source or target.
Volumes that can be checked by Tiered Storage Manager, and for which a migration task or data deletion task
is being executed, are not displayed in Reasons that a volume cannot become source/target volume. Such
volumes cannot be used as either migration source volumes or migration target volumes.
Table 1-3 Character Strings Representing Reasons a Volume Cannot Be a Migration Source or Target
25
Character string displayed Description Migration source
volume
Migration target
volume
Continuous Access XP (target) Volume that makes up a Continuous Access XP pair and whose
status is PSUS or PSUE
Continuous Access XP Status Volume that makes up a Continuous Access XP pair and whose
status is neither PSUS nor PSUE
Business Copy XP (target)
Business Copy XP
Configuration [Root]
Business Copy XP
Configuration [Node]
Business Copy XP
Configuration [Leaf]
Migration Group (target) Volume that is included in an migration group -- Y
Already Reserved#1 Volume reserved as a migration target Y Y
Continuous Access XP Journal Volume that makes up a Continuous Access XP Journal pair Y Y
Snapshot XP Volume that makes up a Snapshot XP pair Y Y
Cache LUN XP Volume for which Cache LUN XP is set Y Y
Command Device Volume used as a Command Device Y Y
LUSE (target) Volume that makes up LUSE -- Y
Path (target) Volume for which a path is set -- Y
Locked (target) Volume that is locked (not Read/Write) by LUN Security XP
NAS (target) NAS system volume -- Y
Externally Locked Volume that is using the external subsystem function and is
Not Acquired Volume
Information
Legend:
Y: Corresponds to the reason that the volume cannot be migrated (cannot be used as a volume for migration)
--: Does not correspond to the reason that the volume cannot be migrated (can be used as a volume for migration)
#1
Includes the volumes migrated by HP StorageWorks Auto LUN XP.
#2
LUN Security XP Extention is a product name. For details on this product, see the manual HP StorageWorks LUN Security XP Extention User Guide for the XP12000/XP10000/XP1024/XP128.
Volume that makes up a Business Copy XP pair -- Y
Volume that makes up a Business Copy XP pair (This is a PVOL that makes up a pair with three S-VOLs.)
Volume that makes up a Business Copy XP pair (This is an SPVOL that makes up a pair with two S-VOLs.)
Volume that makes up Business Copy XP pair (This is an S-VOL
that makes up a pair with an SP-VOL.)
#2
Extention
locked (not Read/Write) by LUN Security XP Extention
Volume whose volume information cannot be obtained Y Y
#2
-- Y
Y Y
Y Y
-- Y
Y Y
When the migration source volume is a LUSE, you can specify only those volumes that are not applicable to
Table 1-4 Character Strings Representing Reasons a Volume Cannot Be a Migration Source or Target. In
addition, the volume must satisfy the following conditions:
• All migration target volumes are made up of either internal or external volumes.
• If they are external volumes, the external volume attributes (emulation type, IO suppression mode, cache
mode, and CLPR) are identical.
Although they are not required, it is recommended that the following conditions be satisfied. If they are not
satisfied, errors might occur during operation after migration is performed.
• All migration target volumes have the same RAID level.
• All migration target volumes have the same drive type, either SATA or non-SATA.
• For external volumes, all volumes are in the same chassis.
When the migration source volume LUSE is migrated, each LDEV in the migration target volume will make up a
LUSE and be replaced with the migration source. Figure 1-14 shows migration of a LUSE configuration.
26
Figure 1-14 Migration of LUSE Configuration
27
2 Getting Started with the GUI
This chapter describes getting started using Tiered Storage Manger with the Web client GUI. It includes the
following sections:
• Preparing for GUI Operations (section
• Guidelines for Using the GUI (section
• Logging In (section
• Logging Out (section
• Starting Tiered Storage Manager (section
• Using Tiered Storage Manager Windows (section
2-3 )
2-4 )
2-1 )
2-2 )
2-5 )
2-1 Preparing for GUI Operations
Before starting Tiered Storage Manager operation, you must check the following:
Storage Subsystem
All the storage subsystems being managed by Tiered Storage Manager must be connected by a LAN,
and must be accessible from the Tiered Storage Manager's management server and management
clients.
A storage subsystem being used as a domain controller must be connected to the external subsystem,
and a logical device within that external subsystem must be mapped to the domain controller.
The term “domain controller” in this user’s guide refers to the StorageWorks XP12000 and the
StorageWorks XP10000.
Device Manager server
The Device Manager server must be installed and set up in advance so that it is fully ready for use. For
more information, refer to the HP StorageWorks Command View XP Advanced Edition Device Manager Server Installation and Configuration Guide.
2-6 )
Tiered Storage Manager server
The Tiered Storage Manager server must be installed and set up in advance so that it is fully ready for
use. For more information, refer to the HP StorageWorks XP Tiered Storage Manager Server Installation and Configuration Guide.
Browser
Check the name and version of the browser you are using:
®
• If your OS is Solaris
• If your OS is Windows
Internet Explorer with Windows
If you are using Internet Explorer with Windows
up window not opening. In such cases, do the following for the connection-target server:
1. From the Internet Explorer Tools menu, select Pop-up Blocker, and then Pop-up Blocker Settings.
2. Type the address (URL) of the connection-target server in the Address of Web site to allow box, and then
click Add.
If the registration processing ends successfully, the server will be added and displayed in the Allowed
sites box.
Internet Explorer and Displayed Fonts
If you specify a font size in Internet Explorer to one other than medium, it might display differently during
processing from what you have specified. When display processing finishes, the fonts will display in the
size you specified. This does not affect operations.
, verify that your browser is Netscape Navigator® 7.0 or Mozilla® 1.4 or later.
®
, verify that your browser is Internet Explorer 6.0 or later.
®
XP Service Pack
®
XP Service Pack 2, a problem can occur such as a pop-
Using Tiered Storage
Manager
Language Used for the Tiered Storage Manager GUI
The language you use for the Tiered Storage Manager GUI depends on the language setting for the
browser you are using. The date format also depends on the language setting for your browser.
The time is always displayed in 24-hour format, regardless of the browser's language setting.
Getting Started with the GUI 28
However, the language being used by the OS and browser determines the language used for the Browse
button, which is displayed in the Tiered Storage Manager version information dialog box, as well as the
language used for the license file selection dialog box, which you open by clicking the Browse button.
An error message might contain text that remains unchanged after being received from the Device
Manager server. The language type for these parts of a message is determined according to the location
of the machine where the Device Manager server is running. We recommend that you match the
language type for a Web client to the location on the server side.
2-2 Guidelines for Using Tiered Storage Manager GUI
To make sure that the Tiered Storage Manager GUI works correctly, you should avoid doing the following:
• Do not click the Next or Back buttons of the browser.
• Do not select an item in the menu opened by a right-click in a window.
• Do not use a shortcut key, such as Back Space or Tab.
• Do not select a menu-bar item in the browser window.
Note, however, that even if you inadvertently perform such an operation, the database (repository) that is used
internally by Tiered Storage Manager will not be corrupted. If you inadvertently perform one of the above
operations, do the following:
•If your browser is Internet Explorer, click Refresh on the View menu in the browser window. This re-
displays the window that was displayed immediately after login.
•If your browser is Netscape Navigator
window. This re-displays the window that was displayed immediately after login.
®
or Mozilla®, click Reload on the View menu from the browser
2-3 Logging Into Tiered Storage Manager
You can log into Tiered Storage Manager in either of two ways:
• From the login dialog box.
• From another Command View XP AE Suite software.
2-3-1 Logging In from the Login Dialog Box
To log in to Tiered Storage Manager:
1. Make sure you have registered the license information.
2. Start the browser and enter the URL of the Tiered Storage Manager server in the following format:
For Tiered-Storage-Manager-server-address, enter the IP address or host name of the Tiered Storage
Manager server. For port-number, enter the port number for Command View XP AE Suite Common Web
Service. For more information on the port number, refer to the HP StorageWorks Command View XP Advanced Edition Device Manager Server Installation and Configuration Guide.
When the IP address is 172.16.45.1 and the port number is 23015 (default), the URL is as follows:
http://172.16.45.1:23015/TieredStorageManager/
Entering the URL displays the Tiered Storage Manager title window and login window.
3. In the login window, enter your user ID and password.
For the User ID, enter the user name you specified in Device Manager.
When entering the password in Password, note that the password is case-sensitive. If you enter an
invalid password, an error message displays in the login dialog box. Enter the correct password.
4. Click the Login button.
The Tiered Storage Manager Main window displays (see Figure 2-1).
29
Figure 2-1 Tiered Storage Manager Main Window
2-3-2 Logging In from another Command View XP AE Suite Software
You can log into Tiered Storage Manager by performing the Link-and-Launch operation from a Web client of
another Command View XP AE Suite software (such as Device Manager or Tuning Manager). In this case, you
do not have to specify the user ID and password.
To log into Tiered Storage Manager from another product, do the following:
1. In the Menu-bar frame in the main window of the other Command View XP AE Suite software, click Tool.
The tool window displays.
2. In the tool window, select Tiered Storage Manager.
2-4 Logging Out of Tiered Storage Manager
To log out of Tiered Storage Manager:
1. In the Menu-bar of the main window, select one of the following:
•Logout: Terminates the Web client. You cannot use other Command View XP AE Suite software that
have been started by the Link-and-Launch operation from the terminated Web client. You can, however,
continue to use other Command View XP AE Suite software that have been logged into from the start
menu.
•Close: Closes the browser but does not log you out if you have logged into Tiered Storage Manager from
another Command View XP AE Suite software. You can continue to use other Command View XP AE
Suite software. If you close all other Command View XP AE Suite software, you will be automatically
logged out after a factory-set period of inactivity.
2. Click the OK button on the confirmation window.
2-5 Starting Tiered Storage Manager
Once you connect to the Tiered Storage Manager server, you can start Tiered Storage Manager operations.
After logging into Tiered Storage Manager, you can start using its functions from the Main window.
To start Tiered Storage Manager:
1. Log in to Tiered Storage Manager:
The Main window displays with the List Objects Subwindow (see
Getting Started with the GUI
Figure 2-2).
30
Loading...
+ 69 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.