XP12000 Replication Monitor Rootsan Technologies PVT LTD

HP StorageWorks XP Replication Monitor
User Guide
Part number: TI784-96001
First edition: November, 2005

Legal and notice information
© Copyright 2005 Hewlett-Packard Development Company, L.P.
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.
Microsoft and Windows,are regiestered trademarks and Windows Server is a trademark of Microsoft Corporation.
Mozilla is a trademark of the Mozilla Foundation in the U.S and other countries.
Netscape is a registed trademark of Netscape Communications Corporation.
Java, JavaScript, Solaris, and Sun are trademarks of Sun Microsystems, Inc.
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.
HP StorageWorks XP Replication Monitor User Guide
Part number: TI784-96001

First edition: November, 2005
Contents
Revision history (start here)
Revision tables ..................................................................................................................................................... 11
1 Overview of Replication Monitor
1-1 Replication Monitor Overview.................................................................................................................... 12
1-1-1 Replication Monitor Features.......................................................................................................... 12
1-1-2 Target Users................................................................................................................................... 13
1-1-3 Key Terms ...................................................................................................................................... 13
1-2 Replication Monitor Functions ................................................................................................................... 14
1-2-1 Checking the Status of a Copy Pair................................................................................................ 14
1-2-2 Monitoring a Copy Pair ................................................................................................................... 17
1-2-3 Changing the Status of a Copy Pair ............................................................................................... 18
1-2-4 Setting Up a Copy Pair ................................................................................................................... 18
1-3 System Configuration Using Replication Monitor ...................................................................................... 18
1-3-1 Components for Systems Using Replication Monitor ..................................................................... 18
1-3-2 System Configuration Models of Systems Using Replication Monitor............................................ 20
1-4 Programs Related to Replication Monitor.................................................................................................. 24
1-4-1 Command View XP AE Suite Common Component ...................................................................... 24
1-4-2 Device Manager ............................................................................................................................. 25
1-4-3 Software Provided by Storage Subsystems ................................................................................... 25
1-5 Applied Examples for Replication Monitor................................................................................................. 26
1-5-1 Example 1: Resolving Problems from the Storage Subsystem Perspective .................................. 26
1-5-2 Example 2: Resolving Problems from the Host Perspective .......................................................... 29
2 Installation and Uninstallation
2-1 Installation and Uninstallation in Windows®.............................................................................................. 33
2-1-1 System Requirements .................................................................................................................... 33
2-1-2 Installing Replication Monitor.......................................................................................................... 34
2-1-3 Upgrading or Re-installing Replication Monitor .............................................................................. 39
2-1-4 Uninstalling Replication Monitor ..................................................................................................... 42
2-1-5 Troubleshooting in Installation and Uninstallation .......................................................................... 43
2-2 Installation and Uninstallation in a Cluster Environment ........................................................................... 45
2-2-1 Installation ...................................................................................................................................... 45
2-2-2 Upgrade Installation and Re-installation......................................................................................... 47
2-2-3 Uninstallation .................................................................................................................................. 48
2-3 Notes on Installation and Uninstallation .................................................................................................... 49
2-3-1 Notes on Uninstalling Device Manager .......................................................................................... 49
2-3-2 Notes on Stopping Command View XP AE Suite software Services and Daemons ...................... 49
3 Environment Settings
3-1 Setting Up the Operating Environment...................................................................................................... 50
3-1-1 Prerequisites for Setting Up an Operating Environment................................................................. 50
3-1-2 Parameters Required for Operating Replication Monitor................................................................ 50
3-2 Building a Cluster Configuration Environment........................................................................................... 55
3-2-1 Specifying Cluster Environment Settings in the Executing Node (When Using MSCS)................. 55
3-2-2 Specifying Cluster Environment Settings in the Standby Node (When Using MSCS) ................... 58
3-2-3 Troubleshooting for Building a Cluster Environment ...................................................................... 60
3-2-4 Notes on Using Replication Monitor in a Cluster Environment....................................................... 60
3-3 Starting and Terminating Replication Monitor ........................................................................................... 61
3-3-1 Starting Replication Monitor ........................................................................................................... 61
3-3-2 Terminating Replication Monitor..................................................................................................... 62
3-3-3 Checking Operation Status of Replication Monitor......................................................................... 62
3-4 Environment Setting Command ................................................................................................................ 63
3-4-1 Setting or Viewing the Parameters Related to Device Manager .................................................... 63
3-5 Backing Up Operating Environment Information ....................................................................................... 65
3-5-1 Backing Up Operating Environment Information ............................................................................ 65
3-5-2 Restoring Databases ...................................................................................................................... 66
3-6 Changing the Host Name for the Management Server ............................................................................. 67
4 Operation
4-1 Functions of Web Client ............................................................................................................................ 70
4-1-1 Monitoring and Notification of a Pair Status ................................................................................... 71
4-1-2 Determining and Displaying the Most Significant Pair Status......................................................... 74
Contents 3
4-2 Starting and Terminating Web Client ........................................................................................................ 77
4-2-1 Starting Operation of Web Client.................................................................................................... 77
4-2-2 Terminating Operation of Replication Monitor ................................................................................ 78
4-2-3 Calling a Different Command View XP AE Suite software ............................................................. 78
4-3 Window Configuration and Displayed Items of Web Client ....................................................................... 78
4-3-1 Configuration of Web Client's Main Window .................................................................................. 79
4-3-2 Web Client Dialog Boxes................................................................................................................ 86
4-3-3 Icons Displayed in the Web Client Window .................................................................................... 87
4-3-4 Notes on Replication Monitor Operations....................................................................................... 89
4-3-5 Displaying Cascaded Copy Pairs ................................................................................................... 90
4-3-6 Languages Displayed While Web Client Is Operating.................................................................... 91
4-3-7 Displaying Multiple Items of Information for a Particular Node....................................................... 91
4-3-8 Error and Warning Messages......................................................................................................... 92
4-4 Setting a Monitoring Configuration ............................................................................................................ 94
4-4-1 Considerations before Setting Monitoring Configurations .............................................................. 96
4-4-2 Adding, Editing and Deleting Monitoring Configurations ................................................................ 98
4-5 Identifying an Error Location ................................................................................................................... 106
4-5-1 Confirming and Operating on a Pair Status Using the Hosts View............................................... 107
4-5-2 Confirming and Operating on a Pair Status Using the Subsystems View .................................... 110
4-5-3 Confirming and Operating on a Pair Status Using the Pair Configurations View ......................... 113
4-6 Changing a Pair Status ........................................................................................................................... 118
4-6-1 Changing a Status ........................................................................................................................ 118
4-6-2 Changing the Copy Pace.............................................................................................................. 119
4-6-3 Pair Status Changing Procedure .................................................................................................. 120
4-6-4 Notes on Changing a Pair Status ................................................................................................. 125
4-7 Calling Device Manager .......................................................................................................................... 125
4-8 Registering and Viewing License Information ......................................................................................... 126
4-8-1 License Key .................................................................................................................................. 126
4-8-2 Registering and Viewing License Information .............................................................................. 126
4-9 Replication Monitor Security Management.............................................................................................. 127
4-9-1 Necessary User Permissions for Login ........................................................................................ 127
4-9-2 Inheriting User Permissions in Link-and-Launch Operations ....................................................... 127
4-9-3 Access Security for the Device Manager Server .......................................................................... 128
4-9-4 Network Access Security.............................................................................................................. 128
4-10 Notes on Operating the Refresh Function .................................................................................... 128
5 Troubleshooting
5-1 Error Countermeasures........................................................................................................................... 130
5-1-1 Log File Output from Replication Monitor ..................................................................................... 130
5-1-2 Error Countermeasure Procedure ................................................................................................ 130
5-1-3 Maintenance Information Batch Collection Command ................................................................. 131
6 Messages
6-1 Message Types and Formats.................................................................................................................. 133
6-1-1 Replication Monitor Messages ..................................................................................................... 133
6-1-2 Detailed Messages ....................................................................................................................... 134
6-1-3 Other Messages ........................................................................................................................... 134
6-1-4 Collecting Log Information for Installation and Uninstallation Errors ............................................ 134
6-2 KAVN00000 - KAVN00199...................................................................................................................... 135
6-3 KAVN00200 - KAVN00399...................................................................................................................... 139
6-4 KAVN00400 - KAVN00599...................................................................................................................... 149
6-5 KAVN00600 - KAVN00799...................................................................................................................... 154
6-6 KAVN01200 - KAVN01399...................................................................................................................... 156
6-7 Detailed Messages.................................................................................................................................. 166
6-8 Action for Detailed Message RPM-00824 ............................................................................................... 177
6-8-1 Check the Disk Space .................................................................................................................. 177
6-8-2 Transferring Data from the Common Component Database........................................................ 177
6-9 Action for Error Message KAVN01281-E ................................................................................................ 178
Appendix A Information Available in System Configuration Models
A.1 System Configuration Diagrams ................................................................................................................. 179
A.1.1 Local Copy Configurations ......................................................................................................... 179
A.1.2 Continuous Access XP Configurations......................................................................................... 181
A.2 Node Display in Navigation Frame ............................................................................................................. 183
A.3 Information Displayed in the Information Frame or Dialog Box by Method Selected ................................. 184
A.4 Information Displayed in the Information Frame (Hosts View) ................................................................... 185
A.4.1 Hosts Node................................................................................................................................... 185
Contents 4
A.4.2 host-name Node ........................................................................................................................... 186
A.4.3Port/HSD/LUN Node............................................................................................................................. 188
A.5 Information Displayed in the Information Frame (Subsystems View)........................................... 190
A.5.1 Subsystems Node ...................................................................................................................... 190
A.5.2 subsystem-name Node............................................................................................................... 191
A.5.3 Port/HSD/LUN Node................................................................................................................... 193
A.6 Information Displayed in the Information Frame (Pair Configurations View) .............................................. 195
A.6.1 Pair Configurations Node ........................................................................................................... 195
A.6.2 pair-management-server Node..................................................................................................... 195
A.6.3 RAID Manager XP-configuration-definition-file-name Node ....................................................... 197
A.6.4 copy-group-name Node ...................................................................................................................... 198
A.6.5 pair-name Node.......................................................................................................................... 200
A.6.6 LDEV LDEV-number Node......................................................................................................... 201
Appendix B Glossary
Index
Contents 5
Figures
Figure 1-1 Window Configuration of Replication Monitor........................................................................................... 13
Figure 1-2 List of Copy Pairs When the Hosts View Is Used ..................................................................................... 15
Figure 1-3 List of Copy Pairs When the Subsystems View Is Used .......................................................................... 15
Figure 1-4 List of Copy Pairs When the Pair Configurations View Is Used ............................................................... 16
Figure 1-5 Example of Determining and Displaying the Most Significant Pair Status................................................ 17
Figure 1-6 Example of Changing the Status of a Copy Pair ...................................................................................... 18
Figure 1-7 Control and Data Flow in a System Using Replication Monitor ................................................................ 20
Figure 1-8 Usual Configuration .................................................................................................................................. 21
Figure 1-9 Pair Management Server and Host Combined Configuration .................................................................. 22
Figure 1-10 Pair Management Server and Host Combined (Agents Not Installed on Hosts) Configuration.............. 23
Figure 1-11 Agent-less Configuration ........................................................................................................................ 24
Figure 1-12 System Configuration for Example 1 (Resolving Problems from the Storage Subsystem Perspective) 27
Figure 1-13 System Configuration for Example 2 (Resolving Problems from the Host Perspective) ........................ 30
Figure 3-1 Relation between Replication Monitor Restart Time and the Refreshing Time ........................................ 53
Figure 4-1 Timing for Sending Email ......................................................................................................................... 73
Figure 4-2 Concept of Determining the Most Significant Pair Status ......................................................................... 74
Figure 4-3 Scope for Determining the Most Significant Pair Status (Hosts View) ..................................................... 75
Figure 4-4 Scope for Determining the Most Significant Pair Status (Subsystems View) ........................................... 76
Figure 4-5 Scope for Determining the Most Significant Pair Status (Pair Configurations View) ................................ 77
Figure 4-6 Configuration of the Web Client Window .................................................................................................. 79
Figure 4-7 Menu-bar Frame....................................................................................................................................... 79
Figure 4-8 Navigation Frame ..................................................................................................................................... 80
Figure 4-9 Tree Structure below Hosts ...................................................................................................................... 81
Figure 4-10 Tree Structure below Subsystems.......................................................................................................... 82
Figure 4-11 Tree Structure below Pair Configurations............................................................................................... 83
Figure 4-12 Jump Buttons.......................................................................................................................................... 84
Figure 4-13 Refresh in the Navigation Frame............................................................................................................ 84
Figure 4-14 Method Frame ........................................................................................................................................ 84
Figure 4-15 Example of Displayed Information Frame .............................................................................................. 85
Figure 4-16 Example of the Information Frame with the Mouse Pointer Positioned on a Sortable Item ................... 85
Figure 4-17 Example Dialog Box 1 ............................................................................................................................ 87
Figure 4-18 Example Dialog Box 2 ............................................................................................................................ 87
Figure 4-19 Example Cascade Configuration ............................................................................................................ 90
Figure 4-20 Example View for a Cascade Configuration ........................................................................................... 90
Figure 4-21 View of LDEV Detailed Information (When There Are Multiple Items of Information) ............................ 92
Figure 4-22 Example of an Error Message Displayed in the Information Frame ....................................................... 93
Figure 4-23 Example of an Error Message Displayed in a Dialog Box (Values Can Be Re-entered)........................ 94
Figure 4-24 Example of an Error Message Displayed in a Dialog Box (Values Cannot Be Re-entered)................... 94
Figure 4-25 Difference Between Everytime and a Specified Number........................................................................ 97
Figure 4-26 Counting Method When the Number of Notifications is Specified .......................................................... 97
Figure 4-27 Example of the Set Monitoring Configurations Subwindow.................................................................... 98
Figure 4-28 Example of the Add Monitoring Configuration Dialog Box...................................................................... 99
Figure 4-29 Example of the Add Monitoring Configuration - Confirmation Dialog Box (Without SMTP Authentication)
................................................................................................................................................................................... 99
Figure 4-30 Example of List Objects Subwindow .................................................................................................... 100
Figure 4-31 Example of the Edit Monitoring Configuration Dialog Box.................................................................... 102
Figure 4-32 Example of the Edit Monitoring Configuration - Confirmation Dialog Box ............................................ 102
Figure 4-33 Example of Show Monitoring Configurations Subwindow .................................................................... 104
Figure 4-34 Example of Delete Monitoring Configuration - Confirmation Dialog Box .............................................. 105
Figure 4-35 Example of the Hosts view ................................................................................................................... 108
Figure 4-36 Example of a List of Information on Monitoring-Target Hosts .............................................................. 108
Figure 4-37 Example of a List of LUNs Which Are Connected to a Host and Comprise Pairs ................................ 109
Figure 4-38 Example 1 of Copy Pairs Cascaded and Associated with a LUN......................................................... 109
Figure 4-39 Example 1 of a List of Copy Pairs Cascaded and Associated with a LUN (List Objects (Detailed)
Subwindow) ............................................................................................................................................................. 110
Figure 4-40 Example 1 of a List of LUNs Assigned to an LDEV Included in a Cascade ......................................... 110
Figure 4-41 Example of the Subsystems View ........................................................................................................ 111
Figure 4-42 Example of a List of Information on Monitoring-Target Storage Subsystems ...................................... 111
Figure 4-43 Example of a List of LUNs Which Comprise Pairs and Are Stored in a Storage Subsystem ............... 112
Figure 4-44 Example 2 of a List of Copy Pairs Which Are Cascaded and Associated with a LUN ......................... 112
Figure 4-45 Example 2 of a List of Copy Pairs (List Objects (Detailed) Subwindow) Which Are Cascaded and
Associated with a LUN ............................................................................................................................................. 113
Figures 6
Figure 4-46 Example 2 of a List of LUNs Which Are Assigned to the LDEV Included in the Cascade.................... 113
Figure 4-47 Example of the Pair Configurations View ............................................................................................. 114
Figure 4-48 Example of a List of Information on Monitoring-Target Pair Management Servers .............................. 114
Figure 4-49 Example of a List of RAID Manager XP Configuration Definition Files Which Are Managed by a Pair
Management Server ................................................................................................................................................ 115
Figure 4-50 Example of a List of Copy Groups Which Are Included in a RAID Manager XP Configuration Definition
File ........................................................................................................................................................................... 115
Figure 4-51 List of Copy Pairs Which Are Included in a Copy Group ...................................................................... 116
Figure 4-52 Example of a List of LDEVs Which Comprise Pairs Indicated by a Copy Pair ..................................... 116
Figure 4-53 Example of a List of Cascaded Copy Pairs Associated with an LDEV................................................. 117
Figure 4-54 Example of a List of Cascaded Copy Pairs (List Objects (Detailed) Subwindow) Which Are Associated
with an LDEV ........................................................................................................................................................... 117
Figure 4-55 Example 3 of a List of LUNs Which Are Assigned to an LDEV Included in a Cascade........................ 118
Figure 4-56 Example 1 of the Change Pair Status - Step 1 of 2 Dialog Box ........................................................... 121
Figure 4-60 Version Information Dialog Box ............................................................................................................ 127
Figures 7
Tables
Table 1 Document Conventions.................................................................................................................................. 9
Table 2 Revisions ..................................................................................................................................................... 11
Table 1-1 Types of Pair Statuses............................................................................................................................... 16
Table 1-2 Refresh Functions by Type and Applied Range ........................................................................................ 17
Table 2-1 OSs and Web Browsers Required for the Management Server and Management Client......................... 33
Table 3-1 List of Parameters Required for Operating Replication Monitor ................................................................ 50
Table 3-2 List of Parameters Related To Device Manager........................................................................................ 51
Table 3-3 List of Parameters Related To Database Connections.............................................................................. 53
Table 3-4 List of Parameters Related To Log Output ................................................................................................ 54
Table 3-5 List of Parameters Related To Information Acquisition Interface............................................................... 55
Table 4-1 List of Replication Monitor Web Client Functions ...................................................................................... 70
Table 4-2 Items That Can Be Set in a Monitoring Configuration ............................................................................... 71
Table 4-3 Relationship between the Monitored Object and the Object Address Displayed in the List of Monitoring
Configurations ............................................................................................................................................................ 72
Table 4-4 Correlation between Pair Statuses in Replication Monitor and Pair Statuses in Device Manager ............ 72
Table 4-5 Rules for Determining the Most Significant Pair Status ............................................................................. 72
Table 4-6 Scope for Determining the Most Significant Pair Status (Hosts View)....................................................... 74
Table 4-7 Scope for Determining the Most Significant Pair Status (Subsystems View) ............................................ 75
Table 4-8 Scope for Determining the Most Significant Pair Status (Pair Configurations View) ................................. 76
Table 4-9 Display Format of the Last Update Time ................................................................................................... 86
Table 4-10 Node Icons in the Object Tree ................................................................................................................. 87
Table 4-11 Icons of Replication Monitor Execution Results....................................................................................... 88
Table 4-12 Copy Status Icons.................................................................................................................................... 88
Table 4-13 Primary Volume and Secondary Volume Icons (Pair Configuration) ....................................................... 88
Table 4-14 Pair Status Icons (Pair Configuration) ..................................................................................................... 89
Table 4-15 Monitoring Configuration Icon (Action) .................................................................................................... 89
Table 4-16 Correlation Between an Arrow Displayed in the Information Frame and the Device Manager Pair Status
................................................................................................................................................................................... 91
Table 4-17 Web Browser Language Setting and Displayed Language ..................................................................... 91
Table 4-18 List of Items Set for Monitoring Parameters ............................................................................................ 95
Table 4-19 When the Target Is a Copy Group......................................................................................................... 118
Table 4-20 When the Target Is a Copy Pair ............................................................................................................ 119
Table 4-21 Selectable Copy Paces.......................................................................................................................... 120
Table 5-1 Types of Log Files Output from Replication Monitor................................................................................ 130
Table 6-1 Replication Monitor Message Numbers and Corresponding Functions................................................... 133
Table 6-2 Message Types and Meanings................................................................................................................ 133
Table 6-3 Detailed Message Numbers and Corresponding Functions .................................................................... 134
Tables 8
About this guide
This guide provides information about:
• Installing HP StorageWorks XP Replication Monitor software.
Intended audience
This guide is intended for users who use Replication Monitor to operate and manage systems that incorporate
a storage subsystem (magnetic disk array device).
This guide assumes that the reader has the following:
• A basic knowledge of management tools unique to storage subsystems.
• A basic knowledge of SANs (Storage Area Networks).
• Knowledge of volume replication functionality (such as Business Copy and Continuous Access XP) of
storage subsystems.
• A basic knowledge of Device Manager.
• A basic knowledge of the prerequisite operating system being used (Windows), and of how to operate
web browsers.
If the user intends to use Device Manager Agent, the user must also have:
• A basic knowledge of the prerequisite Windows operating system being used for Device Manager Agent.
Prerequisites
Prerequisites for installing this product include:
• Reading through the user guide.
• Meeting all the minimum installation requirements.
• Reviewing the readme.txt file on the CD for any last-minute announcements.
Document conventions and symbols

Table 1 Document Conventions
Convention Element Convention Element
Medium blue text: Figure 1 Cross-reference links and e-mail addresses
Medium blue, underlined text Web site addresses

(http://www.hp.com)
Bold font • Key names

• Text typed into a GUI element, such as into a box
• GUI elements that are clicked or selected, such as
menu and list
italics font Text emphasis
Monospace font • File and directory names

• System output
• Code
• Text typed at the command-line
Monospace, italic font • Code variables

• Command-line variables
Monospace, bold font Emphasis of file and directory names, system output, code,
and text typed at the command-line
CAUTION: Indicates that failure to follow directions could result in damage to equipment or data.
IMPORTANT: Provides clarifying information or specific instructions.
About this guide 9

NOTE: Provides additional information.
TIP: Provides helpful hints and shortcuts.
HP technical support
Telephone numbers for worldwide technical support are listed on the HP web site:
http://www.hp.com/support/
Collect the following information before calling:
• Technical support registration number (if applicable)
• Product serial numbers
• Product model names and numbers
• Applicable error messages
• Operating system type and revision level
• Detailed, specific questions
For continuous quality improvement, calls may be recorded or monitored.
HP strongly recommends that customers sign up online using the Subscriber’s choice web site at
http://www.hp.com/go/e-updates
• Subscribing to this service provides you with email updates on the latest product enhancements, newest
versions of drivers, and firmware documentation updates as well as instant access to numerous other
product resources.
• After signing-up, you can quickly locate your products by selecting Business support and then Storage
under Product Category.
HP-authorized reseller
For the name of your nearest HP-authorized reseller:
• In the United States, call 1-800-345-1518.
• Elsewhere, visit http://www.hp.com and click Contact HP to find locations and telephone numbers.
Helpful web sites

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 10

Revision history (start here)
Revision tables
Table 2 Revisions
Date Edition Revision
November, 2005 First Initial release

1 Overview of Replication Monitor
This chapter gives an overview and explains the main functionalities of Replication Monitor, for those
considering installing Replication Monitor and those using it for the first time. This chapter also explains the
hardware and software needed to install Replication Monitor, and gives example system configurations using
such hardware and software. Finally, this chapter gives examples of how to solve problems that may arise
when Replication Monitor is installed, and shows several cases highlighting effective use of Replication
Monitor.
• 1.1 Replication Monitor Overview
• 1.2 Replication Monitor Functions
• 1.3 System Configuration Using Replication Monitor
• 1.4 Programs Related to Replication Monitor
• 1.5 Applied Examples for Replication Monitor
1-1 Replication Monitor Overview

Replication Monitor is software that supports management operations for storage administrators. Replication
Monitor can be used to check the configuration, as well as change the status, of copy pairs set up using the
volume replication functionality of the StorageWorks XP1024/XP128 and XP512/XP48 Series of magnetic disk
array devices.
1-1-1 Replication Monitor Features

Recently, with the increase of data handled by corporate information systems, the way in which storage
subsystems are used has changed, from standalone storage subsystems running in one location, to widely
linked storage subsystems that span multiple data centers. As such, more importance has been placed on
preparing environments for disaster recovery, in which several data centers are linked to protect data and
perform system recovery.
By installing Replication Monitor on such systems, you can visually check the configurations of multiple copy
pairs configured across multiple storage subsystems, from the standpoint of a host, storage subsystem, or
copy pair configuration definition. Also, you can check system-wide pair statuses and then drill-down to areas
where problems exist, to identify failure areas and expedite recovery. Finally, you can set Monitoring Actions
for certain copy pairs in advance, so that users are automatically notified when Replication Monitor is notified of
a failure occurrence.
Overview of Replication Monitor 12

Figure 1-1 Window Configuration of Replication Monitor
1-1-2 Target Users

Replication Monitor was designed for storage administrators and system administrators responsible for the
following storage operations:
• Setting up copy pairs
• Resolving problems that occur with copy pair statuses
• Managing copy pair statuses
Replication Monitor is particularly effective where:
• Environments include multiple storage subsystems or include multiple physical locations
• Environments in which various types of volume replication functionality (such as both Business Copy and
Continuous Access XP) are used
1-1-3 Key Terms

• LDEV
A logical device in a storage subsystem.
• LU or volume
A logical unit in a storage subsystem. Hosts can mount an LU in order to use storage devices on a
storage subsystem.

• LUN
A logical unit number used to map an LU (volume) in a storage subsystem.
• Storage subsystem volume replication functionality
A general name for functionality (such as Business Copy and Continuous Access XP) that provides high-
speed replication of volumes in a storage subsystem. The mirroring control functionality provided by the
storage subsystem is used to create volume replicas quickly, without going through the LAN.
• Primary volume (P-VOL)
The volume “from” which replication is performed, when the volume replication functionality of the storage
subsystem is used to perform copying to another volume.
• Secondary volume (S-VOL)
The volume “to” which replication is performed. The copy of the primary volume, when the volume
replication functionality of the storage subsystem is used to copy from the primary volume.
• Secondary - primary volume (SP-VOL)
A volume placed between the primary volume and secondary volume, when the volume replication
functionality of the storage subsystem is used in a cascade configuration. This indicates the secondary
volume for an upper copy pair, and the primary volume for a lower copy pair.
• Copy pair (Pair volume)
Pairing of a primary volume and a secondary volume that is linked by the volume replication functionality
of a storage subsystem. In this manual, copy pair may be written simply as pair.
• Copy group
A group containing multiple copy pairs. A copy group allows operations such as pair status changes
applied to multiple copy pairs.
1-2 Replication Monitor Functions

Replication Monitor allows you to perform the following:
• Check the status of a copy pair
• Monitor a copy pair
• Change the status of a copy pair
• Set up a copy pair
1-2-1 Checking the Status of a Copy Pair

Replication Monitor can be used to check the status of all copy pairs managed by Device Manager, Remote
Web Console or RAID Manager XP. It can be used to check the statuses of copy pairs that are in a cascade
configuration or check the statuses of those in the same copy group as the given pair.
Replication Monitor offers the following advantages.
1-2-1-1 View Selection

Replication Monitor facilitates the identification and analysis of status changes (failures), by allowing copy pair
statuses to be checked from the following three views.
• Hosts view
• Subsystems view
• Pair Configurations view
The following describes the features of these views:
Hosts view
The Hosts view displays copy pair statuses for a list of hosts (operation servers). The statuses of copy
pairs that are in a cascade configuration with respect to a given pair can be checked at the same time.

Figure 1-2 List of Copy Pairs When the Hosts View Is Used
Subsystems view
The Subsystems view displays copy pair statuses for a list of storage subsystems. The statuses of copy
pairs that are in a cascade configuration with respect to a given pair can be checked at the same time.
Figure 1-3 List of Copy Pairs When the Subsystems View Is Used
Pair Configurations view
The Pair Configurations view displays copy pairs for a list of servers. The servers in the list contain
configuration definition information including the RAID Manager XP that controls the pairs. The statuses
of copy pairs that are in a cascade configuration with respect to a given pair can be checked at the same
time.

Figure 1-4 List of Copy Pairs When the Pair Configurations View Is Used
The Pair Configurations view facilitates checking for those operating and monitoring a pair management
server in a configuration where an independent pair management server is used, such as storage
administrators.
For a detailed overview on views, see section 4-1 . For details about how to operate views, see section 4-5 .
1-2-1-2 Pair Status Types and Pair Statuses Determined as Most Significant
With Replication Monitor, copy pair statuses are indicated by the following four types.
Table 1-1 Types of Pair Statuses
Pair status Description Status of Device Manager pair Priority

error Indicates that an error has occurred for the copy pair. • Suspended 1
• Error in LUSE
• Suspending
• Deleting
suspend Indicates that the copy pair is in split status. Split 2
copying Indicates that copy processing is being performed for the copy • Copying 3
pair, either forward or in reverse. • Reverse-Copying
sync Indicates that the copy pair is in synchronized status. Pair 4
For quick identification of problems occurring on pairs that are being managed, Replication Monitor determines
and displays the most significant copy pair status (the highest-priority copy pair status) for each upper entity
(the host in the Hosts view, or the storage subsystem in the Subsystems view) containing each copy pair. This
is called determining and displaying the most significant pair status, and is performed for each Copy Type,
such as Business Copy and Continuous Access XP.
For example, in the Hosts view, when a given host (hostA) is selected and its copy status is viewed, the
statuses of the copy pairs related to all volumes mounted for hostA, as well as the statuses of the copy pairs
in a cascade configuration from those copy pairs, are displayed as pair statuses related to hostA. Here, if a
Business Copy copy pair in the copying status and a Business Copy copy pair in the error status both exist,
then the Business Copy copy pair status that is determined and displayed as being most significant is error.
This allows the system administrator to recognize failures on hostA that need to be resolved with the greatest
priority.

Figure 1-5 Example of Determining and Displaying the Most Significant Pair Status
For details about the rules for determining and displaying of the most significant pair status, see section 4-1 .
For details about how to view the determined display of the most significant pair statuses, see section 4-5 .
1-2-1-3 Refresh
When the status of a copy pair is checked, Replication Monitor provides the user with information that includes
configuration information for each view, the status that is determined as being most significant for each copy
pair, information kept by Replication Monitor itself, host and storage subsystem information, and information
obtained from Device Manager. This information is updated, or refreshed, to reflect the actual information, on a
set schedule.
Replication Monitor provides several refresh functions that differ with respect to applied range and timing.
Table 1-2 shows the refresh functions provided by Replication Monitor, by type and applied range.
Table 1-2 Refresh Functions by Type and Applied Range
Refresh type Applied range

Automatic refresh
(executed periodically at a pre-defined interval)
Refresh All information is updated.
Retrieve Replication Monitor information is updated to match the most recent Device
Manager information.
(Device Manager does not re-obtain information)
Manual refresh
(executed via Web Client, by the user)
Refresh All All information is updated.
Refresh Host Only information related to the selected host is updated.
Refresh Subsystem Information related to the selected storage is updated.
Refresh Pair Status Information related to the selected pair is updated. (Information related to the copy
group, or all pairs in a cascade configuration, can also be updated.)
Through combinations of these refresh functions you can reduce the load on each server by updating only the
necessary information.
For details on how to set up an automatic refresh, see section 3-1 . For details about how to perform a manual
refresh, see section 4-5 .
1-2-2 Monitoring a Copy Pair

Replication Monitor can be used to make sure that no problems exist with copy pairs, by monitoring the pair
status at a set interval and reporting any abnormalities that occur.
You can set Replication Monitor to monitor the status of a pair. Monitoring configurations consists of a
monitoring target, a check condition, and an action (to be taken when the monitoring status condition is
satisfied).
Monitoring target
The following items can be set as monitoring targets:
• Host in the Hosts view

• Storage subsystem in the Subsystems view
• Copy group in the Pair Configurations view
• Individual copy pairs can be made monitoring targets
Also, individual copy pairs can be made monitoring targets, in the monitoring range of servers, storage
subsystems, and configuration definition servers. This lets you set specific monitoring configurations for
certain copy pairs.
Check condition
Set the pair status that is to be considered a problem.
When a monitored copy pair satisfies the specified check condition, Replication Monitor executes the set
action. If the monitoring target is a host, storage subsystem, or copy group, and the pair status that is
determined and displayed as being most significant reaches the set status, then Replication Monitor
executes the set action.
Note that checking to determine whether the condition is satisfied is performed at the same time as the
automatic refresh, which is performed at a set interval. This applies to the Refresh and Retrieve refresh
functions shown in Table 1-2.
Action
Define the processing to be performed by Replication Monitor in the event of a problem.
Replication Monitor comes with functionality to perform email notification as an action. The recipients and
message content of these emails can be changed for each monitoring configuration. You can use this
functionality to create a system in which the appropriate administrator can be notified in accordance with
the location and severity of a problem.
For details about how to set and change monitoring configurations, see section 4-4 .
1-2-3 Changing the Status of a Copy Pair

Replication Monitor can be used to change the status of a copy pair in the event of a problem with the copy pair
status. For details, see section 4-6 .
Figure 1-6 Example of Changing the Status of a Copy Pair
1-2-4 Setting Up a Copy Pair

Replication Monitor can be used to call Device Manager Web Client to create new copy pairs and change the
settings of existing copy pairs. For details, see section 4-7 .
1-3 System Configuration Using Replication Monitor

This section explains the components, such as servers and storage subsystems, needed for systems using
Replication Monitor.
1-3-1 Components for Systems Using Replication Monitor

This subsection explains the necessary components for systems using Replication Monitor. Note that the
numbers used in the following descriptions correspond to the control and data flow shown in Figure 1-7.

1-3-1-1 Software Comprising the System
• Replication Monitor
The main Replication Monitor program. This uses Web Client to provide users with system information (3)
collected by the Device Manager server. (1) It notifies the Device Manager server (4) of a pair status
change request from a user (2), or a periodic information refresh request.
• The Device Manager server
Keeps the system information collected by the Device Manager agent (7, 9) or the information collected
directly from storage subsystems (5), and provides it to Replication Monitor. (3)
The Device Manager server issues instructions (8, 10), such as copy pair status changes, to a Device
Manager agent, in accordance with instructions issued by Replication Monitor (4), or performs processing
to acquire storage subsystem information. (6)
• The Device Manager agent
Collects host information (13), information about storage subsystems as provided by RAID Manager XP
(12), and copy pair configuration definition information described in the RAID Manager XP configuration
definition files (14), and provides them to the Device Manager server (7, 9). The Device Manager agent
issues instructions (11), such as copy pair status changes, to RAID Manager XP, in accordance with
instructions issued by the Device Manager server (10).
• RAID Manager XP
Collects information about storage subsystems (15), and provides it to the Device Manager server (12).
RAID Manager XP issues instructions, such as copy pair status changes, to storage subsystems (16).
1-3-1-2 Hardware Comprising the System

This manual uses the following terms to refer to the machines needed to use Replication Monitor.
Management server
The machine on which Replication Monitor and its prerequisite program, the Device Manager server, are
installed. The management server requests system configuration information from each host, and
provides the information collected to the management client.
Management client
The machine on which Web Client for Replication Monitor runs. This machine issues instructions to
Replication Monitor on the management server such as viewing pair configurations, monitoring and
changing pair statuses. Since Web Client for Replication Monitor runs in a Web browser, no applications
are installed on the management client.
Host (application server)
A machine on which the application program is installed. The host application server uses the storage
subsystem as an external storage device. To use Replication Monitor to view information about each
host, install the Device Manager agent on the host. If you also install RAID Manager XP on the host, then
the host can collect information from storage subsystems. In this case, the host also performs the
processing of a pair management server.
Pair management server
A server that is used to collect and manage copy pair status information. The Device Manager agent and
RAID Manager XP are installed on pair management servers.
Since pair management servers, which are independent of a host, take over processing to obtain copy
pair configuration information, they have the advantage of being able to reduce load on the hosts.
However, they have the disadvantage of not being able to obtain host configuration information.
Storage subsystem
An external storage device connected to a host. Any storage subsystem supported by Device Manager
can also be operated by Replication Monitor. For details, see the manual HP StorageWorks Command
View XP Advanced Edition Device Manager Server Installation and Configuration Guide.
1-3-1-3 Control and Data Flow

The following figure shows the control and data flow between program products in a system using Replication
Monitor. For details on the contents shown by each control or data flow, see section 1-3-1-1 .

Figure 1-7 Control and Data Flow in a System Using Replication Monitor
1-3-2 System Configuration Models of Systems Using Replication Monitor

The following shows system configuration models of representative systems using Replication Monitor.
1-3-2-1 Usual Configuration

This is the most common configuration, in which Device Manager Agent and RAID Manager XP are installed
on the hosts.
Replication Monitor and the Device Manager server are installed on the management server, and the system
information collected by hosts can be viewed.

Figure 1-8 Usual Configuration
(Advantages)
A host can collect all system information because both the Device Manager agent and RAID Manager XP
are installed on each host; therefore, it is not necessary to configure an independent pair management
server.
(Disadvantages)
Since the pair management server’s tasks, such as pair operations by RAID Manager XP, are executed
on a host, the load on the host is increased as compared to other configurations.
1-3-2-2 Pair Management Server and Host Combined Configuration

The Device Manager agent and RAID Manager XP are installed on the pair management server, which is
independent of a host, and manages copy pairs. Only the Device Manager agent is installed on the hosts.
Replication Monitor and the Device Manager server are installed on the management server, and system
configuration information collected from the pair management server and hosts can be viewed.

Figure 1-9 Pair Management Server and Host Combined Configuration
(Advantages)
A host can collect host information because the Device Manager agent is installed on each host.
Configuring an independent pair management server can distribute the processing related to pair
management, and reduce the load on the host.
(Disadvantages)
A pair management server that is independent of a host is required. Note that a pair management server
can be the same machine as a management server.
1-3-2-3 Pair Management Server and Host Combined (Agents Not Installed on Hosts)
Configuration
Both the Device Manager agent and RAID Manager XP are installed on the pair management server, and copy
pairs are managed independently. Neither RAID Manager XP nor the Device Manager agent is installed on the
hosts.
configuration information collected from the pair management server can be viewed.

Figure 1-10 Pair Management Server and Host Combined (Agents Not Installed on Hosts) Configuration
(Advantages)
The load on a host is reduced because no applications are added to the host.
(Disadvantages)
A pair management server that is independent of a host is required. The limitation associated with this
approach is that host information is not available.
1-3-2-4 Agent-Less Configuration

Neither RAID Manager XP nor the Device Manager agent is installed on the hosts, and no pair management
server is set up.
Replication Monitor and Device Manager are installed on the management server, and system configuration
information for storage subsystems can be viewed directly.

Figure 1-11 Agent-less Configuration
(Advantages)
The load on a host is reduced because no applications are added to the host. It is not necessary to
configure a pair management server that is independent of a host.
(Disadvantages)
The limitations associated with this approach are that no host information is available, copy pair
operations are not allowed and pair status is only determined by doing storage subsystem refresh.
1-3-2-5 Note on System Configuration

For the configurations (3) and (4), there are limitations with respect to the system configuration information that
can be obtained by Replication Monitor. For details, see Appendix A, Information Available in System
Configuration Models.
1-4 Programs Related to Replication Monitor

This section explains the programs related to Replication Monitor.
1-4-1 Command View XP AE Suite Common Component

Command View XP AE Suite Common Component is a package of various functions for shared use by all
Command View XP AE Suite software. This is installed as part of Replication Monitor and is also embedded in
each Command View XP AE Suite software that uses these functions.
Users of Replication Monitor can also use the following functions from Command View XP AE Suite Common
Component:
• Single Sign-On
Once you log on to Command View XP AE Suite software, the user ID and password already
authenticated are used whenever another Command View XP AE Suite software is called. Users do not
need to re-enter their user IDs and passwords. User permissions are maintained for the Command View
XP AE Suite software platform.
• Integrated logging and integrated database
The various kinds of information output by Command View XP AE Suite software are written to an
integrated log. The management information kept by Command View XP AE Suite software is aggregated

to one location and managed as an integrated database. Commands are provided to perform backup and
restoration of management information.
• Command View XP AE Suite Common Component
This is a service that implements the Web services (such as Web Client) provided by Command View XP
AE Suite software. Web Client for Replication Monitor is also provided by Command View XP AE Suite
Common Component.
1-4-2 Device Manager

Device Manager operates and manages the different HP manufactured storage subsystems. Replication
Monitor uses the information, such as copy pair configurations and pair statuses, collected by Device Manager.
The server functionality of Device Manager is a prerequisite program for Replication Monitor. For details about
Device Manager, see the Device Manager manuals.
1-4-3 Software Provided by Storage Subsystems

1-4-3-1 Software Related to Volume Replication Functionality
The StorageWorks XP Disk Array provides the Business Copy, Snapshot XP, Continuous Access XP, and
Continuous Access XP Journal volume replication functions. Replication Monitor can be used to obtain
information about the copy pairs defined using these volume replication functions, and to display pair statuses
for each kind of software.
Business Copy / Snapshot XP
Business Copy and Snapshot XP are software for creating replicas of volumes in the same storage
subsystem. For details, see the manuals for Business Copy and Snapshot XP.
In the Web Client window for Replication Monitor, Business Copy may be displayed as BC and Snapshot
XP may be displayed as Snapshot XP or SN.
Continuous Access XP
Continuous Access XP is software for creating replicas of volumes between storage subsystems. For
details, see the Continuous Access XP manual.
Continuous Access XP has two modes, Continuous Access XP(synchronous mode) and Continuous
Access Extension (asynchronous mode). In Replication Monitor Web Client, Continuous Access XP may
be displayed as CA-XP(Sync), and Continuous Access XP Extension may be displayed as CA-
XP(Async).
Continuous Access XP Journal
Continuous Access XP Journal is software for creating replicas of volumes asynchronously between
storage subsystems. Continuous Access XP Journal can be used to create replicas of multiple volumes
between storage subsystems. For details, see the Continuous Access XP Journal manual.
In Replication Monitor Web Client, Continuous Access XP Journal may be displayed as CA-XP(Jrnl).
1-4-3-2 RAID Manager XP

RAID Manager XP is software for controlling the Storage Works XP1024/XP128 and XP512/XP48 series. RAID
Manager XP can be used to issue commands from hosts to storage subsystems, to control the volume
replication functionality (such as Continuous Access XP and Business Copy) of the storage subsystem. It can
also be used to collect information about pair configurations in the storage subsystem. For details about RAID
Manager XP, see the RAID Manager XP manual.
Replication Monitor can be used to control RAID Manager XP via the Device Manager server or the Device
Manager agent, to collect information about storage subsystems, and to change pair statuses.
1-4-3-3 Operation Management Software for Storage Subsystems

The operation management software (such as StorageWorks XP12000 Remote Web Console and
StorageWorks XP1024 Remote Web Console) that comes with each storage subsystem. The operation
management software for storage subsystems can be used for greater control of functionality specific to each
storage subsystem.
1-4-3-4 Note on Using Software Provided by Storage Subsystems

When using software provided by storage subsystems, note the following points:

• When operation management software for storage subsystems is used to create a copy pair, the copy
pair information that can be obtained by Replication Monitor is limited. As such, when Replication Monitor
is used, we recommend that you use Device Manager to create copy pairs.
For details about the limitations when using operation management software for storage subsystems to
create a copy pair, see Appendix A, Information Available in System Configuration Models.
• When a user directly operates Device Manager, RAID Manager XP, or operation management software
for a storage subsystem (such as Remote Web Console) to perform the processing listed below, refresh
the Device Manager information on Web Client for Replication Monitor by executing the Refresh
Subsystem method for the storage subsystem that performed the processing, or by executing the Refresh
All method.
• When the user has changed the configuration for storage subsystems (for example, a new disk drive
has been added)
• When the user has created a copy pair, or performed any operation for copy pairs
If the Device Manager information is not refreshed, the latest configuration information will not be applied
to Replication Monitor.
1-5 Applied Examples for Replication Monitor

This section introduces the procedures to follow to resolve problems that occur when using Replication
Monitor.
1-5-1 Example 1: Resolving Problems from the Storage Subsystem

Perspective
The Subsystems view of Replication Monitor can be used to check, from the storage subsystem perspective,
where problems occur and the effects that the problems have had, so that the appropriate countermeasures
can be determined. This subsection explains the steps for resolving problems by examining problems from the
storage subsystem perspective. It also explains the advantages of using Replication Monitor at each step.
1-5-1-1 System Configuration

The following shows the system configuration for example 1 (resolving problems from the storage subsystem
perspective).

Figure 1-12 System Configuration for Example 1 (Resolving Problems from the Storage Subsystem
Perspective)
• The volumes of subsystem_A and subsystem_B are in a Continuous Access XP Extension
(asynchronous mode Continuous Access XP) pair configuration.
• The two volumes in subsystem_B are in a Business Copy pair configuration.
1-5-1-2 Monitoring Configurations
The following monitoring configurations are set in Replication Monitor:
Monitoring target Check condition Action when configuration is reached

LDEVs contained in subsystem_A The status of a related copy pair (including An email is sent to the storage
cascade configuration copy pairs) changes administrator.
to suspend.
LDEVs contained in subsystem_B
1-5-1-3 Flow of Problem Resolution

1-5-1-3-1Reception of Email from Replication Monitor
The storage administrator receives an email from Replication Monitor, and checks whether the status of the
monitored pair has changed to suspend.

• The storage administrator receives two emails from Replication Monitor, and recognizes that the
monitored pair status has changed to suspend.
• One of the emails shows that subsystem_A is in suspend status, and another shows that subsystem_B
is in suspend status.
(Advantages of using Replication Monitor)
You can use Replication Monitor to periodically execute monitoring processing and notify a storage
administrator when an error occurs, without need for the storage administrator to constantly monitor the
copy pair statuses.
1-5-1-3-2Identifying the Copy Pair Where a Failure Occurs, and Checking the Effective
Range of the Failure
To identify the cause of the failure in the copy pair, and determine its significance:
1. Log on to Replication Monitor.
2. Perform refresh processing to collect the most recent system information.
First, the storage administrator decides to determine whether a failure is actually occurring in the
subsystem indicated by Replication Monitor.
3. From the navigation frame on the left side of the Replication Monitor window, select the Subsystems node
to check the pair statuses of subsystem_A and subsystem_B.
After checking, the administrator discovers that the pair status for CA-XP(Async) (Continuous Access XP
Extension) of subsystem_A and subsystem_B is suspend, as indicated by the email.
Then, the storage administrator decides to determine which LU of subsystem_A and subsystem_B is in
the suspend status.
4. Expand the object tree, and select the subsystem_A node and the subsystem_B node under the
Subsystems node to check the pair statuses of those nodes.
By checking the statuses of subsystem_A and subsystem_B, the administrator discovers that a pair
related to LUN01 in subsystem_A, and a pair related to LUN21 in subsystem_B, are both in the suspend
status. The administrator also discovers that LUN01 is used by the host host_A as /apps.
Next, the storage administrator decides to check which copy pair configuration contains LUN01 and
LUN21.
5. Expand the object tree and select the LUN01 node of subsystem_A, to check the effects of the failure
occurring in the copy pair that contains LUN01.
Check the copy pair that contains LUN01, and the list of copy pairs that are connected from this pair, in a
cascade configuration.
By checking the copy pairs related to LUN01, the administrator discovers that two pairs (LDEV01 -
LDEV11 and LDEV11 - LDEV21) are in a cascade configuration.
6. Click the LDEV11 node to display a dialog box with a list of LUs assigned to LDEV11, in order to check if
any host is using a LDEV in this cascade configuration.
When checking the list of LUs, the administrator discovers that no LUs were displayed, so no hosts are
using LDEV11.
7. Click LDEV21 to display a dialog box with a list of LUs related to LDEV21.
When checking the list of LUs, the administrator realizes that host_B is using LDEV21 as LUN21.
When checking the list of LUs, the administrator discovers that host_B is using LDEV21 as LUN21, and
that the mount point is /mnt.
By using Replication Monitor to check statuses, you can drill down from the status of the entire storage
subsystem to the status of each copy pair. You can also check copy pairs that are connected, in a
cascade configuration, from a copy pair where a failure is occurring, and whether a host exists that is
using the LDEVs that comprise these copy pairs.
1-5-1-3-3Contacting the Database Administrator and Checking the Impact on Business

Operations
The storage administrator checks the impact on business operations, by conferring with the administrators who
manage the volumes related to the copy pair where the failure occurred, and considers appropriate actions to
be taken.

• The storage administrator contacts the database administrators of host_A and host_B, to notify them that
an error occurred in a volume to which host_A is connected on the mount point /apps, as well as in a
volume to which host_B is connected on the mount point /mnt. The system administrator asks them
about the purposes that each of the volumes serve.
• The database administrator of host_A responds that the target volume is being used as a database.
The storage administrator reports the status of the storage to the database administrator, and asks the
database administrator of host_A to stand by until recovery is performed.
• The database administrator of host_B responds that an attempt was made to split the LDEV11-LDEV21
pair to back up the data in the volume to tape.
The storage administrator asks the database administrator of host_B to cancel split processing until
system recovery is complete, so that the tape backup is not wasted.
• The storage administrator uses the operation management software for storage subsystems to
investigate the cause of the failure in detail, and then finds that the pair is in suspend status because the
sidefile used by Continuous Access XP is full. As such, the copy pair will be resynchronized and the pair
status will be recovered.
You can use Replication Monitor to collect information (such as the mount point) related to the copy pair
where an error is occurring, and provide this useful information to the administrators who manage the
hosts or databases.
1-5-1-3-4Resolving the Problem by Copy Pair Resynchronization

To recover the status of the pair:
1. From the information frame on the right side of the Replication Monitor window, click the location where
Copy Status is displayed as suspend.
The Change Pair Status dialog box is displayed.
2. In the Operation list box, select resync, and then click the Next button.
3. Check the contents displayed, and then click the Execute button.
The pair status is changed and copy pair resynchronization is performed.
Make sure that the pair status has changed to sync (synchronous mode).
5. Lastly, contact the database administrator of host_B, and grant permission to restart the tape backup.
One hour later, the database administrator of host_B responds that the tape backup has completed
successfully.
You can use Replication Monitor to change the status of the copy pair when an error is occurring. You
can check the changed status on Replication Monitor.
1-5-2 Example 2: Resolving Problems from the Host Perspective

The Hosts view of Replication Monitor can be used to check, from the host perspective, where problems occur
and the effects that the problems have had, so that the appropriate countermeasures can be determined. This
subsection explains the procedures for resolving problems by examining problems from the host perspective. It
also explains the advantages of using Replication Monitor at each step.
1-5-2-1 System Configuration

The following shows the system configuration for example 2 (resolving problems from the host perspective):

Figure 1-13 System Configuration for Example 2 (Resolving Problems from the Host Perspective)
• host_A is using volumes for online transaction processing.
• host_B is using volumes for batch jobs.
• The volumes of subsystem_A and subsystem_B are in a Continuous Access XP (synchronous mode
Continuous Access XP) pair configuration.
• The two volumes in subsystem_B are in a Business Copy pair configuration.
• The volumes of subsystem_B and subsystem_C are in a Continuous Access XP Extension
(asynchronous mode Continuous Access XP) pair configuration.
1-5-2-2 Monitoring Configurations
The following monitoring configurations are set in Replication Monitor:
Monitoring target Check condition Action when configuration is reached

LU on which host_A is mounted The status of a related copy pair (including An email is sent to the storage
cascade configuration copy pairs) changes administrator.
to suspend.
LU on which host_B is mounted

1-5-2-3 Flow of Problem Resolution
1-5-2-3-1Reception of Email from Replication Monitor
• The storage administrator receives two emails from Replication Monitor, and checks whether the status of
the monitored pair has changed to suspend.
• The first email indicates that host_A is in suspend status, and the second indicates that host_B is in
suspend status.
1-5-2-3-2Checking the impact on each host
To identify the cause of the failure in the copy pair, and determine its significance:
1. Log on to Replication Monitor.
First, the storage administrator decides to determine whether a failure is actually occurring in the
subsystem indicated by Replication Monitor.
3. From the navigation frame on the left side of the Replication Monitor window, select the Hosts node to
check the pair statuses of subsystem_A and subsystem_B.
After checking, the administrator discovers that the pair status for CA-XP(Async) (Continuous Access XP
Extension) of subsystem_A and subsystem_B is suspend, as indicated by the email.
Then, the storage administrator decides to determine which LU of subsystem_A and subsystem_B is in
suspend status.
4. From the navigation frame on the left side of the Replication Monitor window, in Hosts, select the host_A
node and the host_B node, and check their pair statuses.
By checking the error status of host_A and host_B, the administrator discovers that the statuses of pairs
related to LUN01 in host_A and LUN02 in host_B are suspend. The administrator also discovers that the
mount point for LUN01 in host_A is /app, and that the mount point for LUN02 in host_B is /app2.
By using Replication Monitor to investigate the status from the host perspective, you can check the
impact on each host before isolating the copy pair where a problem is occurring. This enables you to
consider appropriate actions to take for the affected business operations while investigating the error
causes.
1-5-2-3-3Contacting the Database Administrator and Determining the Priority of

Processing
The storage administrator checks the impact on business operations, by conferring with the administrators who
manage the volumes related to the copy pair where a failure occurred, and considers appropriate actions to be
taken.
• The storage administrator contacts the database administrators of host_A and host_B, to notify them that
an error occurred in a volume to which host_A is connected on the mount point /apps, as well as in a
volume to which host_B is connected on the mount point /mnt. The system administrator also asks them
about the purposes that each of the volumes serve.
• The database administrator responds that host_A is being used for online transaction processing, and
that host_B is being used for batch jobs. With this information, it is determined that copy pairs related to
host_A must be recovered quickly.
1-5-2-3-4Identifying the Copy Pair Where a Failure Occurs
To identify the failure occurring on host_A:
Expand the object tree, select the LUN01 node of host_A, and check the list of LDEVs related to LUN01.
By checking the pairs related to LUN01, the administrator discovers that three copy pairs (LDEV01 -
LDEV11, LDEV11 - LDEV21, and LDEV21 - LDEV31) are in a cascade configuration. Of these, the pair
LDEV21 - LDEV31 is in suspend status.
A detailed investigation with the operation management software for storage subsystems determines that
the pair is in suspend status because the sidefile used by Continuous Access XP is full. As such, the
copy pair will be resynchronized and the pair status will be recovered.
1-5-2-3-5Resolving the Problem by Copy Pair Resynchronization

To recover the status of the pair:

1. From the information frame on the right side of the Replication Monitor window, click the location where
Copy Status is displayed as suspend.
The Change Pair Status dialog box is displayed.
2. In the Operation list box, select resync, and then click the Next button.
3. Check the contents displayed, and then click the Execute button.
The pair status is changed and the copy pair is resynchronized.
Make sure that the pair status has changed to sync (in synchronized status).
5. Lastly, select the Hosts node, to make sure that the status of host_A is normal. Then, notify the database
administrator that recovery for pair statuses related to host_A was performed.
After recovering copy pairs related to host_A, make sure that you also determine the location where the failure
is occurring and recover copy pairs related to host_B, following the same order of steps in the procedure.

2 Installation and Uninstallation
This chapter explains how to install and uninstall Replication Monitor.
There are two installation modes: new installation and overwrite installation. A new installation is performed if
Replication Monitor has not yet been installed, whereas an overwrite installation is performed at an upgrade or
re-installation. The installer automatically determines whether to perform a new installation or overwrite
installation. When performing an overwrite installation, you cannot revert to a version earlier than the current
version.
• 2.1 Installation and Uninstallation in Windows
• 2.2 Installation and Uninstallation in a Cluster Environment
• 2.3 Notes on Installation and Uninstallation
2-1 Installation and Uninstallation in Windows®

This section explains how to install and uninstall Replication Monitor in the Windows.
2-1-1 System Requirements

Requirements for the Windows® OS are as follows:
• On the management server where Replication Monitor is to be installed, the Device Manager server of
Device Manager 1.1 must be installed and set up as a prerequisite program product (in a state where
communications between the management server, management client, and storage subsystem can be
established). For details about a Device Manager server installation and setup, see the manual HP
StorageWorks Command View XP Advanced Edition Device Manager Server Installation and
Configuration Guide.
Supplementary explanation:
When the Device Manager agent is installed on a host (application server) that is connected to the
#
storage subsystem, Replication Monitor functions can be utilized more effectively. For details about a
Device Manager agent installation, see the manual HP StorageWorks XP Advanced Edition Device
Manager Agent Installation Guide.
#
To link the Device Manager agent with Replication Monitor, all of the following conditions must be
satisfied:
- The Device Manager agent must be of Device Manager 1.1 or later.
- The Device Manager agent version is one that can be used under the Device Manager server,
which is a prerequisite of Replication Monitor.
However, if the Device Manager agent version is earlier than the Device Manager server version,
some of the Replication Monitor functions cannot be used. For details, see the manual HP
• The following OS and Web browser are required for the management server and management client. The
Web browser is used for GUI operations on the management client.
Table 2-1 OSs and Web Browsers Required for the Management Server and Management Client
Management server Management client

OS OS Web browser
Windows 2000 SP3, Windows Windows 2000 SP3, Windows 2000 SP4, Windows Internet Explorer 6.0 or
2000 SP4, Windows Server 2003 Server 2003 (32-bit), Windows Server 2003 SP1 Internet Explorer 6.0
(32-bit), Windows Server 2003 (32-bit), Windows XP SP1, or Windows XP SP2 SP1
®
SP1 (32-bit), or Windows XP Solaris 8 or Solaris 9 (for SPARC) Netscape Navigator
#
SP2 7.0 or Mozilla™ 1.4
HP-UX 11i V1.0 or HP-UX 11i V2. Mozilla 1.7.3_02
# If the management server runs in a cluster environment, there are restrictions on usable OSs. For details
about the OS requirements in a cluster environment, see section 3-2 .
• An Administrators group user ID is required to install Replication Monitor.
• A resolution of SVGA (800 x 600) or greater is required.
• A CD-ROM drive is required.
• A 10/100 Ethernet LAN card is required.
• The TCP/IP protocol must be in operation.
• Static IP addresses are required.
• Replication Monitor is an application used to execute operations such as referencing pair configurations,
monitoring pair statuses, and changing pair statuses. Thus, it is required that volumes be in copy pair
structures via the volume replication functions of the storage subsystem (such as Business Copy,
Continuous Access XP, Snapshot XP or Continuous Access XP Journal) and also be the management
targets of Device Manager. For details about requirements for managing copy pairs with Device Manager,
see the manual HP StorageWorks Command View XP Advanced Edition Device Manager Server
Installation and Configuration Guide.
2-1-2 Installing Replication Monitor

This subsection explains how to perform a new installation of the Replication Monitor in Windows.
Check the following before performing a new installation:
• Replication Monitor uses the functions of Device Manager. Thus, to install Replication Monitor, Device
Manager Server must be installed in advance. If you attempt to install Replication Monitor in a machine
with no Device Manager server installed, a window appears during installation to inform you that Device
Manager is not installed, and the installation terminates.
• Make sure that no other application is running.
• About 300 MB of free disk space is temporarily required to install Replication Monitor.
• When you install Replication Monitor in a folder other than the default, do not use a name that contains a
double-byte character (for example, Japanese characters) or a name reserved by the OS (such as CON,
AUX, NUL, PRN, CLOCK$, COM1 - COM9, or LPT1 - LPT9) for the installation folder. If you do, Replication
Monitor will not install properly.
• For new installations, the following information must be entered for steps 6 to 9. Acquire this information
in advance:
• Installation folder for Replication Monitor (step 6)
This information is required when the installation folder is not the default folder.
• The storage destination for the database files used by Replication Monitor (step 7).
This information is required when the storage location is not the default.
• The host name of the server where Replication Monitor is to be installed (step 8)
• The port number of the server where Replication Monitor is to be installed (step 8)
This information is required when using a port number that is not the default.
• The Device Manager user account (user name and password) (step 9)
The user account that is registered in Device Manager as System Administrator or Storage
Administrator is required.
• The port number that Device Manager uses for HTTP communications (step 9)
This information is required when using a port number that is not the default.
NOTE: Do not forcibly stop installation of Replication Monitor by any method other than clicking the
Cancel button (for example, do not stop installation by restarting the machine). If you do use some
other method to forcibly stop installation, installation and uninstallation operations can no longer be
performed.
NOTE: When using another Command View XP AE Suite software, back up the Command View XP
AE Suite software being used before installing Replication Monitor. For details about how to back up
other Command View XP AE Suite software, see the corresponding product manuals.
To perform a new installation of Replication Monitor:

®
1. Log on to Windows using a user ID that belongs to the Administrators group.
If you have logged on to Windows® using a user ID that does not belong to the Administrators group, a
window appears during installation informing you that the execution must be performed by a user that
belongs to the Administrators group, and the installation process terminates.
Installation and Uninstallation 34

2. When another Command View XP AE Suite software is in operation, terminate the service tasks of that
Command View XP AE Suite software and the services of Common Component (HiCommand Suite
Common Web Service and HiCommand Suite Single Sign On Service).
For details about how to terminate the services of other Command View XP AE Suite software, see the
corresponding product manuals.
To terminate HiCommand Suite Common Web Service and HiCommand Suite Single Sign On Service,
execute the following command:
Common-Component-installation-folder\bin\hcmdssrv /stop
When stopping Command View XP AE Suite software services, stop them in the following order. For
details, see the manual for each product:
(i) The services of other Command View XP AE Suite software
(ii) The Common Component service
3. Insert the Replication Monitor CD-ROM. Select Start, Run, and then Browse. Select the CD-ROM drive
and execute setup.exe from the files in the root folder.
A window appears informing you of the start of the installation. In the window informing you of the start of
the installation, a message appears prompting you to confirm that the services of all Command View XP
AE Suite software have been terminated. The message prompts you to confirm that the services of
Common Component (HiCommand Suite Common Web Service and HiCommand Suite Single Sign On
Service) have been terminated. These two services are activated and terminated during the installation.
NOTE: When you attempt to install Replication Monitor in a machine with no prerequisite version of the
Device Manager server installed, a message appears informing you that the prerequisite version of
Device Manager has not been installed, and the installation stops.
When canceling the installation in the procedures that follow hereafter, click the Cancel button, and
then click the Finish button in the Installation Stopped window that appears.
4. Click the Next button.
A window appears confirming the setup status of the embedded database HiRDB.
NOTE: When HiCommand Suite Common Web Service and HiCommand Suite Single Sign On Service
are not terminated, an error message appears instead of the window for confirming the setup status of
HiRDB.
There are four setup statuses for HiRDB, as shown below. The installer identifies the status and
guides you through the optimal installation for that status. When the setup status of HiRDB is not set,
an error message appears and the installation stops.
• Not setup: HiRDB is not set up.
• Non-cluster configuration: HiRDB has been set up in a non-cluster configuration.
• Cluster configuration (executing node): HiRDB has been set up on the executing system in a
cluster configuration.
• Cluster configuration (standby node): HiRDB has been set up on the standby system in a cluster
configuration.
5. Click the Next button when continuing installation with the displayed contents.
A window appears asking you to specify an installation folder for Replication Monitor.
6. When installing Replication Monitor in the default folder, click the Next button. When installing Replication
Monitor in any other folder, select the folder, and then click the Next button.

A window appears asking you to specify a location in which the database files for Replication Monitor are
to be stored.
NOTE: Clicking the Browse button displays a folder selection dialog box, which enables you to specify
the folder. (This dialog box is also displayed when you specify the folder for storing the database files.)
In a folder selection dialog box, if you manually specify a folder that does not exist, and then click the
OK button, the specified folder is created. The created folder will be deleted if the installation is
canceled or Replication Monitor is uninstalled. Among those created folders, the folders that are not
specified as the installation folder for Replication Monitor can be manually deleted.
If you change the case (for example, change an upper-case character to a lower-case character) when
you manually enter an existing folder name in a folder selection dialog box, the displayed value will use
the characters you entered, but the upper case and lower case characters in the folder name (used by
the OS) will not change. For example, when the folder C:\Program Files\CVXPAE exists in an
environment, if in a folder selection dialog box you manually enter C:\Program Files\CVXPAE, and
then click the OK button, the setting value viewed in the window displayed by clicking the View button is
C:\Program Files\CVXPAE; however, the actual folder is C:\Program Files\CVXPAE.
NOTE: When installing Replication Monitor in a cluster configuration system, specify the same
installation folder on both the executing and standby systems.
Specify an installation folder using no more than 90 characters, including all characters, starting with
the drive letter at the beginning, through to the last character. This maximum includes the characters
that separate the folder names. The following characters can be used for specifying the folder:
A to Z a to z 0 to 9 # + - . @ _ and single-byte spaces
If you specify a name that contains a double-byte character or a name reserved by the OS (such as
CON, AUX, NUL, PRN, CLOCK$, COM1 - COM9, or LPT1 - LPT9), an error might occur.
The Replication Monitor installation folder is as follows:
folder-specified-by-the-user\ReplicationMonitor
By default, the Replication Monitor installation folder is as follows:
system-drive\Program Files\CVXPAE\ReplicationMonitor
When Replication-Monitor-installation-folder appears in the descriptions hereafter, it
refers to either of the above. For instance, Replication-Monitor-installation-
folder\inst refers to either of the following:
folder-specified-by-the-user\ReplicationMonitor\inst
or
system-drive\Program Files\CVXPAE\ReplicationMonitor\inst
Installing Replication Monitor also installs a package called Command View XP AE Common
Component, which consists of functions shared among all the Command View XP AE Suite software.
The installation folder for Command View XP AE Common Component is:
user-specified-folder\Base
If another Command View XP AE Suite software that bundles Common Component (for example,
Device Manager) has been already installed, the portion user-specified-folder indicates the
installation folder specified when that Command View XP AE Suite software was installed.
The default installation folder for Common Component is:
system-drive\Program Files\CVXPAE\Base
In this manual, the installation folder for Common Component indicates one of the above folders.
7. To store the database files for Replication Monitor in the displayed default folder, click the Next button. To
store them in a different folder, enter that folder, and then click the Next button.

A window appears prompting you to specify information about the server (host name and port number) on
which Replication Monitor is installed.
NOTE: Once you specify the folder for storing database files and then click the Next button, changing
the settings of the installation folder will not automatically change the settings for the database files
folder. If you change the installation folder after specifying the default folder as the folder for storing the
database files, manually change the folder for the database files, or cancel the installation and start
installation again.
NOTE: When installing Replication Monitor in a cluster configuration system, specify a shared disk in
this step, and specify the same path on both the executing and standby systems. No default is
displayed.
When you install Replication Monitor in the standby system, if there is no database file under the user-
specified shared disk path (for example, if the specified shared disk path differs from the path specified
when installing Replication Monitor in the executing system, or if the specified path is the same but is not
a shared disk) an error message appears prompting you to re-enter the information. For details about
action to be taken in this case, see section 6-9 .
NOTE: The following characters can be used for specifying the database file location:
A to Z a to z 0 to 9 . _ and single-byte spaces

The following requirements also apply:
• The location must be 100 characters or less (this includes all characters from the drive letter to
the last character).
• An absolute path must be specified.
• A name reserved by the OS (such as CON, AUX, NUL, PRN, CLOCK$, COM1 - COM9, or LPT1 -
LPT9) cannot be used.
• The specified path must not end with the path delimiter.
• A location directly under the drive cannot be specified.
In a non-cluster configuration, depending on the length of the Replication Monitor installation path
name specified by the user, the default folder of the database file is as follows:
• When the installation path name is 72 bytes or less:
installation-path\ReplicationMonitor\database
• When the installation path name exceeds 72 bytes:
installation-path\
If the following folder is used for the storage destination of the database file, the Replication Monitor
installation path name must be 72 bytes or less:
installation-path\ReplicationMonitor\database
If the installation path name contains the following characters, the default value cannot be set for the
storage destination of the database file. Use specifiable characters to set a storage destination other
than the default.
# + - @
The location for the database file requires at least 50 MB of free space.
The window for specifying information about the server on which Replication Monitor is installed
appears only when the HiRDB setup status is non-cluster configuration or cluster configuration
(executing node). If the status is cluster configuration (standby node), a window confirming installation
information appears.
8. Enter the host name and port number (default value: 23015) of the Replication Monitor installation server,
and then click the Next button.
A window appears prompting you to set the information required for Replication Monitor to access Device
Manager.

NOTE: If the host name and port number are not entered, or if the port number is outside the
acceptable range, an error message appears prompting you to re-enter the information.
Do not use localhost for the host name. Doing so prevents the startup of related programs or the
GUI from other client machines.
The host name and port number set in this procedure are required for accessing Replication Monitor
on the management server, from the management client via a Web browser. When specifying an IP
address as the host name, specify it in the form xxx.xxx.xxx.xxx.
Do not change the port number unless it must be changed from the displayed default value, such as
when another application that uses the same port number exists on the same platform where
Replication Monitor will run.
The number 23015 is the default value of the port number used by Web Client for accessing
HiCommand Suite Common Web Service that does not support SSL. When using a port number
other than the default value, the port number allocated to Common Component must also be
changed. For details about changing the port used by Common Component, see the description on
ports in the manual HP StorageWorks Command View XP Advanced Edition Device Manager Server
Installation and Configuration Guide.
The port number can be specified using a number from 1 to 65535.
When installing in a cluster environment, specify a cluster administration IP address or a host name
allocated to the cluster administration IP address.
When setting SSL, you must specify a host name. When making changes to a host name after
completing the installation having specified a cluster administration IP address, see the description on
SSL settings in the manual HP StorageWorks Command View XP Advanced Edition Device Manager
Server Installation and Configuration Guide.
If you need to change the IP address (host name), port number, or protocol after the installation, use
the hcmdschgurl command of Common Component to execute the change. Immediately after
installation, the protocol is set to http. For details about how to use the hcmdschgurl command,
see the manual HP StorageWorks Command View XP Advanced Edition Device Manager Server
Installation and Configuration Guide. Also, for details on how to change the host name, see section 3-
6.
9. Enter the Device Manager user account (user name and password), and click the Next button. If you
need to change the displayed port number (default value: 2001) to another value, enter the user account
and the new port number, and then click the Next button. The password must be entered twice (the
second entry is compared with the first entry to confirm that they are identical).
The Pre-installation confirmation window appears indicating that preparation for the installation is
complete. This window displays installation information such as the installation destination.
NOTE: When the user account and port number required for Replication Monitor to access Device
Manager are not entered, or if the port number is outside the acceptable range, an error message
appears prompting you to re-enter the information.
The user account and port number set in this procedure are required for using Device Manager
functions from Replication Monitor. The user account is used when Replication Monitor accesses
Device Manager. To enable Replication Monitor to use Device Manager functions, a user account
whose Device Manager user type is either System Administrator or Storage Administrator is required.
Accordingly, specify a user account that is actually registered as a System Administrator or Storage
Administrator in Device Manager. Device Manager uses the port number for HTTP communications.

The user account specified here is also required to reference and set up a Device Manager related
parameter after operation of Replication Monitor is started.
When specifying a user name or password, use from 4 to 25 characters. Specifiable characters are
as follows:
Item Specifiable characters

User name A-Z a-z 0-9 # + - . @ _
Password A-Z a-z 0-9 ! # $ % & ' ( ) * + - . = @ \ ^ _ |
At this point, the user account specified in this procedure is not checked as to whether it is valid and
effective as a Device Manager user account. This will be checked when installation has completed
normally and Replication Monitor performs an automatic or manual refresh.
Enter the same password twice. If the first and second input values are not identical, an error
message appears prompting you to re-enter the information.
Execute the port number change only when you need to change the port number to values that are
different from the displayed default value, such as when another application that uses the same port
number exists on the platform that executes Replication Monitor.
The number 2001 is the default value for the port number used by Device Manager in HTTP
communications. If Device Manager has specified a port number other than the default, specify that
port number.
The port number can be specified using a number from 1 to 65535.
10. Check the displayed installation information, and then click the Execution button.
Installation processing begins, and several windows appear indicating various statuses during
processing.
When the installation has completed normally, the Installation complete window appears.
In the following cases, the Installation Stopped or Installation has stopped window appears:
• When the user instructs the installer to stop the installation by clicking the Cancel button.
• When the installation is terminated because of an error that occurred during the installation.
11. Click the Finish button to finish the installation.
The Installation complete window closes.
When the installation has completed normally, the operating statuses of the Common Component
services (HiCommand Suite Common Web Service and HiCommand Suite Single Sign On Service) are
as follows:
• When the setup status of HIRDB is non-cluster configuration
Services begin automatically and are in an operating status. The Device Manager service
(HiCommandServer) also starts automatically.
• When the setup status of HIRDB is cluster configuration
The startup type of the services is set to Manual and the services are in stopped status.
For details about actions to be taken when installation fails, such as cases where the user cancels the
installation via the Cancel button or when an error occurs during the installation, see section 2-1-5 .
2-1-3 Upgrading or Re-installing Replication Monitor

Check the following before executing an overwrite installation:
• For an overwrite installation, you cannot revert to a version earlier than the current version. Check that
the version of Replication Monitor for the overwrite installation is the same as or later than the existing
version of Replication Monitor.
• Make sure that no other application is running.

• About 300 MB of free disk space is temporarily required to install Replication Monitor.
• When performing an overwrite installation, you can reset the Device Manager user account (user name
and password) at step 7. When you reset this information to values different from the existing values,
obtain the information to be changed in advance. The user account must be registered as a System
Administrator or Storage Administrator in Device Manager.
NOTE: Do not forcibly stop installation of Replication Monitor by any method other than clicking the Cancel
button (for example, do not stop installation by restarting the machine). If you do use some other method to
forcibly stop installation, installation and uninstallation operations can no longer be performed.
NOTE: When using other Command View XP AE Suite software, back up the Command View XP AE Suite
software being used before installing Replication Monitor. For details about how to back up other Command
View XP AE Suite software, see the corresponding product manuals.
For an overwrite installation, the existing property files can be used without change.
We recommend that you back up the Replication Monitor operating environment information (property
files and database) before executing an overwrite installation of Replication Monitor. For details about
how to back up Replication Monitor operating environment information, see section 3-5 .
To perform an overwrite installation of Replication Monitor:
1. Log on to Windows® using a user ID that belongs to the Administrators group.
If you have logged on to Windows® with a user ID that does not belong to the Administrators group, a
window appears during installation informing you that the execution must be performed by a user that
belongs to the Administrators group and the installation process terminates.
3. Insert the Replication Monitor CD-ROM. Select Start, Run, and then Browse. Select the CD-ROM drive
and execute setup.exe from the files in the root folder.
A window appears informing you of the start of the installation. In the window informing you of the start of
the installation, a message appears prompting you to confirm that the services of all Command View XP
AE Suite software have been terminated. The message also prompts you to confirm that the services of
Common Component (HiCommand Suite Common Web Service and HiCommand Suite Single Sign On
Service) have been terminated. These two services are activated and terminated during the installation.
NOTE: When the version of Replication Monitor for the overwrite installation is earlier than that of the
existing Replication Monitor, a message appears informing you that the installation cannot proceed
because the version of the product to be installed is earlier than that of the existing Replication Monitor,
and the installation stops.
When canceling the installation in the procedures that follow hereafter, click the Cancel button, and
then click the Finish button in the Installation Stopped window that appears.
A window appears confirming the setup status of the embedded database HiRDB.
are not terminated, an error message appears instead of the window for confirming the setup status of
HiRDB.
There are four setup statuses for HiRDB, as shown below. The installer identifies the status and
guides you through the optimal installation for that status. When the setup status of HiRDB is not set,
an error message appears and the installation stops.
• Not setup: HiRDB is not set up.
• Non-cluster configuration: HiRDB has been set up in a non-cluster configuration.
• Cluster configuration (executing node): HiRDB has been set up on the executing system in a
cluster configuration.
• Cluster configuration (standby node): HiRDB has been set up on the standby system in a cluster
configuration.
5. Click the Next button when continuing installation with the displayed contents.
A window appears prompting you to select whether to reset the Device Manager user account information
necessary for Replication Monitor to access Device Manager.
A window for selecting whether to reset Device Manager user account information appears only when
the HiRDB setup status is non-cluster configuration or cluster-configuration (executing node).
6. If you want to reset Device Manager user account information, choose Change the settings and click the
Next button. If you do not want to reset the information, choose Do not change the settings and click the
Next button.
When Change the settings is selected, a window for setting Device Manager user account information
appears. Go to step 7.
When Do not change the settings is selected, the Pre-installation confirmation window appears indicating
that preparation for the installation is complete. Go to step 8. The Pre-installation confirmation window
displays installation information such as the installation destination.
7. Enter the Device Manager user account (user name and password), and click the Next button. The
password must be entered twice (the second entry is compared with the first entry to confirm that they are
identical).
The Pre-installation confirmation window appears indicating that preparation for the installation is
complete. This window displays installation information such as the installation destination.
NOTE: If a user account for Replication Monitor to access Device Manager is not entered, an error
The user account that is set in this procedure is required for Replication Monitor to use Device
Manager functionality. The user account is used when Replication Monitor accesses Device
Manager. To enable Replication Monitor to use the Device Manager functions, a user account whose
Device Manager user type is either System Administrator or Storage Administrator is required.
Accordingly, specify a user account that is actually registered as a System Administrator or Storage
Administrator in Device Manager.
A user account for Device Manager is also required to reference and set up a Device Manager
related parameter after operation of Replication Monitor is started.
When specifying a user name or password, use from 4 to 25 characters. Specifiable characters are
as follows:

Item Specifiable characters
User name A-Z a-z 0-9 # + - . @ _
Password A-Z a-z 0-9 ! # $ % & ' ( ) * + - . = @ \ ^ _ |
At this point, the user account specified in this procedure is not checked as to whether it is valid and
effective as a Device Manager user account. This will be checked when installation has completed
normally and Replication Monitor performs an automatic or manual refresh.
Enter the same password twice. If the first and second input values are not identical, an error
8. Check the displayed installation information, and then click the Execution button.
Installation processing begins, and several windows appear indicating various statuses during
processing.
When the installation has completed normally, the Installation complete window appears.
In the following cases, the Installation Stopped or Installation has stopped window appears:
• When the user instructs the installer to stop the installation by clicking the Cancel button.
• When the installation is terminated because of an error that occurred during the installation.
NOTE: Do not cancel an upgrade installation or re-installation once the Execution button has been
clicked. Doing so might damage files.
9. Click the Finish button to complete the installation.

The Installation complete window closes.
When the installation has completed normally, the operating statuses of the Common Component
services (HiCommand Suite Common Web Service and HiCommand Suite Single Sign On Service) are
as follows:
• When the setup status of HIRDB is non-cluster configuration
Services begin automatically and are in an operating status. The Device Manager service
(HiCommandServer) also starts automatically.
• When the setup status of HIRDB is cluster configuration
The startup type of the services is set to Manual and the services are in stopped status.
For details about actions to be taken when installation fails, such as cases where the user cancels the
installation via the Cancel button or when an error occurs during the installation, see section 2-1-5 .
2-1-4 Uninstalling Replication Monitor

Before executing the uninstallation, make sure that no other applications are running:
NOTE: When you uninstall Replication Monitor, its property files are deleted. Do not uninstall Replication
Monitor except in cases where you need to completely re-install the program due to problems in the
machine.
To uninstall Replication Monitor:

®
1. Log on to Windows using a user ID that belongs to the Administrators group.
If you have logged on to Windows® using a user ID that does not belong to the Administrators group, a
window appears during the uninstallation informing you that the execution must be performed by a user
that belongs to the Administrators group, and the uninstallation process terminates.

3. Select Start, Setting, Control Panel, Add/Remove Programs, select HP StorageWorks XP Replication
Monitor in the Add/Remove Programs window, and then click the Add/Remove button.
A window appears informing you of the start of the uninstallation. In the window informing you of the start
of the uninstallation, a message appears prompting you to confirm that the services of all Command View
XP AE Suite software have been terminated. The message also prompts you to confirm that the services
of Common Component (HiCommand Suite Common Web Service and HiCommand Suite Single Sign
On Service) have been terminated. These two services are activated and terminated during the
uninstallation.
The Pre-uninstallation confirmation window appears indicating that preparation for the uninstallation is
complete. This window displays the content of the processing that is executed during the uninstallation.
are not terminated, an error message appears instead of the Check before Uninstallation window.
5. Check the displayed uninstallation information, and then click the Execution button.
Uninstallation processing begins, and several windows appear indicating various statuses during
processing.
When the uninstallation has completed normally, the Uninstallation complete window appears.
In the following cases, the Uninstallation has stopped window appears:
• When the user instructs the uninstaller to stop the uninstallation by clicking the Cancel button.
• When the uninstallation is terminated because of an error that occurred during the uninstallation.
6. Click the Finish button to finish the uninstallation.
The Uninstallation complete window closes.
If the uninstallation has completed normally, the operating statuses of the Common Component
services (HiCommand Suite Common Web Service and HiCommand Suite Single Sign On Service)
are in the stopped status.
For details about actions to be taken when uninstallation fails, such as cases when an error occurs
during uninstallation, see section 2-1-5 .
2-1-5 Troubleshooting in Installation and Uninstallation

In the following cases, installation or uninstallation may terminate leaving the system in an incomplete state.
• When cancellation of an installation is attempted by clicking the Cancel button during file copy processing
of an upgrade installation.
• When the installation or uninstallation fails because of an error that occurred during the processing
2-1-5-1 Actions to be Taken When a New Installation Fails
In this case, actions to be taken depend on whether HP StorageWorks XP Replication Monitor is displayed in
Currently Installed Programs. This can be viewed by selecting Start, Setting, Control Panel, and then
Add/Remove Programs.

When HP StorageWorks XP Replication Monitor is not displayed:
Re-execute the installation.
When HP StorageWorks XP Replication Monitor is displayed:
Replication Monitor might not have been installed correctly. Examine the trace logs output during the
installation. After removing the causes of the failure, uninstall Replication Monitor, and then re-execute
the installation.
For details about the trace logs, see section 2-1-5-4 .
2-1-5-2 Actions to be Taken When an Overwrite Installation Fails

Examine the trace logs output during the installation. After removing the causes of the failure, re-execute the
installation.
2-1-5-3 Actions to be Taken When Uninstallation Fails

In this case, actions to be taken depend on whether HP StorageWorks XP Replication Monitor is displayed in
Currently Installed Programs. This can be viewed by selecting Start, Setting, Control Panel, and then
Add/Remove Programs.
When HP StorageWorks XP Replication Monitor is not displayed:
Replication Monitor might not have been uninstalled correctly. Examine the trace logs output during the
uninstallation. After removing the causes of the failure, re-install Replication Monitor, and then re-execute
the uninstallation.
When HP StorageWorks XP Replication Monitor is displayed:
Re-execute the uninstallation.
2-1-5-4 Trace Logs in Installation or Uninstallation

Records (trace logs) of installation or uninstallation processing and their results are output as the trace log file
of the installer.
The output folder, file name, and output format of the installer trace log file are as follows:
• Output folder
The output destination varies depending on whether the processing finished normally, or if an error
occurred during the processing.
• When the installation processing finishes normally
Replication-Monitor-installation-folder\logs
• When an error occurs during the installation or uninstallation processing
system-drive\
• When the uninstallation processing finishes normally

In this case, the trace log file is deleted as the last step of the uninstallation processing.
• File name
The file name differs depending on whether the log is for an installation or an uninstallation.
HRpM_xxxxxxLog.log
where xxxxxx is either Install (for installation) or Uninstall (for uninstallation).
• Output format
The output format to the trace log file is as follows:
*** Begin HP StorageWorks XP Replication Monitor (Windows) setup process

Trace Log
yyyy/mm/dd hh:mm:ss : (level) trace-information supplementary-information
:
*** End HP StorageWorks XP Replication Monitor (Windows) setup process Trace
Log
The meaning of the output information is as follows:

*** Begin HP StorageWorks XP Replication Monitor (Windows) setup process
Trace Log
A comment row showing the beginning of the trace log output.
yyyy/mm/dd hh:mm:ss
Processing date (yyyy/mm/dd hh:mm:ss: year/month/date hour:minute:second).
level
One of the following is output:
I: Trace information for the notification level
W: Trace information for the warning level
E: Trace information showing that an error occurred
trace-information
Parameter values for each executed process, and the specified formats of commands issued by the
installer and their response results.
supplementary-information
Supplementary information that is output as needed.
*** End HP StorageWorks XP Replication Monitor (Windows) setup process Trace
Log
A comment row indicating the end of the trace log output.
A standard InstallShield log is output in addition to the trace log of the installer. This InstallShield standard
log file is to be sent with customer inquiries, for when you cannot identify causes of problems during
installation or uninstallation by referring to the trace log file.
The InstallShield standard log file is as follows:
system-drive\Program Files\InstallShield Installation
Information\{ID}\Setup.ilg
ID: The ProductCode value determined by the installer.
2-2 Installation and Uninstallation in a Cluster Environment

This section describes how to install and uninstall Replication Monitor in a cluster configuration where Device
Manager has been installed. For details about how to change the configuration to a cluster configuration after
operation of Replication Monitor is started in a non-cluster environment, see section 3-2 . For details about how
to set up a cluster configuration for Device Manager, see the manual HP StorageWorks Command View XP
Advanced Edition Device Manager Server Installation and Configuration Guide.
The explanation in this section assumes the following conditions:
®
• In Windows , Device Manager has been installed in the default installation folder in the C drive both on
the executing and standby nodes.
• The Command View XP AE Suite software services are online on the executing node.
2-2-1 Installation
This subsection describes the procedures for a new installation of Replication Monitor.

2-2-1-1 In Windows®
2-2-1-1-1Installing on the Executing Node
To install Replication Monitor on the executing node when the OS is Windows®:
1. Choose Start, Settings, Control Panel, Administrative Tools, and then Cluster Administrator to open the
Cluster Administrator window, and then place the following services offline:
• HiCommandServer
• HiCommand Suite Common Web Service
• HiCommand Suite Single Sign On Service
NOTE: Do not place the following resources offline:
• Shared disk
• Cluster management IP address
• Virtual host name
If placed offline, the shared disk cannot be specified during installation.
If the cluster management IP address or virtual host name is placed offline, installation will fail.
2. Execute the following command to stop the Common Component services:
"C:\Program Files\CVXPAE\Base\bin\hcmdssrv" /stop
3. In the Cluster Administrator window, place the following service offline:

HiRDB/ClusterService_HD0
4. In the Cluster Administrator window, right-click the services that were placed offline in steps 1 and 3,
choose Property, click the Advanced tab, select Do not restart, and then click OK.
5. Install Replication Monitor.
For details, see section 2-1-2 .
6. Open the Services window by choosing Start, Settings, Control Panel, Administrative Tools, and
Services, and then make sure that Startup Type for each of the following services is set to Manual. If
Startup Type is set to Automatic, change it to Manual.
• HiCommandServer
• HiRDB/ClusterService_HD0
7. In the Cluster Administrator window, right-click the group to which the Device Manager service
(HiCommandServer) has been registered, and then choose Move Group to switch to the standby node.
2-2-1-1-2Installing on the Standby Node
To install Replication Monitor on the standby node when the OS is Windows®:
1. Execute the following command to make sure that the Common Component services have stopped:
"C:\Program Files\CVXPAE\Base\bin\hcmdssrv" /status
If any of the Common Component services is running, use the Cluster Administrator window to place the
HiRDB/ClusterService_HD0 service online, and then execute the following command:

After the services have stopped, use the Cluster Administrator window to place the
HiRDB/ClusterService_HD0 service offline.
For details, see section 2-1-2 .
3. Open the Services window by choosing Start, Settings, Control Panel, Administrative Tools, and
Services, and then make sure that Startup Type for each of the following services are set to Manual. If
Startup Type is set to Automatic, change it to Manual.
• HiCommandServer
4. In the Cluster Administrator window, right-click the following services, choose Property, click the
Advanced tab, select Restart, and then click OK.
• HiCommandServer
(HiCommandServer) has been registered, and then choose Move Group to switch to the executing node.
(HiCommandServer) has been registered, and then choose Online.
2-2-1-2 Registering License Information
In a cluster environment in Windows®, the license information must be registered on both the executing and
standby nodes.
To register license information:
1. On the executing node, display the Login window for Web Client, and then register license information.
2. Switch to the standby system.
3. On the standby node, display the Login window for Web Client, and then register license information.
4. Switch to the executing system.
For details about how to display the Login window, see section 4-2-1 . For details about how to register license
information, see section 4-8 . For details about how to switch between the executing and standby systems, see
step 7 in section 2-2-1-1 for Windows®.
2-2-2 Upgrade Installation and Re-installation

This subsection describes the procedures for upgrading or re-installing an existing Replication Monitor.
2-2-2-1-1Upgrading or Re-installing on the Executing Node
To upgrade or re-install Replication Monitor on the executing node when the OS is Windows®:
1. Open the Cluster Administrator window by choosing Start, Settings, Control Panel, Administrative Tools,
and then Cluster Administrator, and then place the following services offline:
• HiCommandServer
• Shared disk
If the shared disk, cluster management IP address, or virtual host name is placed offline, installation
will fail.

2. Execute the following command to stop the Common Component service:

5. Perform an overwrite installation of Replication Monitor.
For details about overwrite installation, see section 2-1-3 .
(HiCommandServer) has been registered, and then choose Move Group to switch to the standby node.
2-2-2-1-2Upgrading or Re-installing on the Standby Node
To upgrade or re-install Replication Monitor on the standby node when the OS is Windows®:
1. Perform an overwrite installation of Replication Monitor.
For details about overwrite installation, see section 2-1-3 .
2. In the Cluster Administrator window, right-click the following services, choose Property, click the
Advanced tab, select Restart, and then click OK.
• HiCommandServer
(HiCommandServer) has been registered, and then choose Move Group to switch to the executing node.
(HiCommandServer) has been registered, and then select Online.
2-2-3 Uninstallation
This subsection describes the procedures for an uninstallation of Replication Monitor.
1. On the executing node, choose Start, Settings, Control Panel, Administrative Tools, and then Cluster
Administrator to open the Cluster Administrator window, and then place the following services offline:
• HiCommandServer
• Shared disk
If the shared disk, cluster management IP address, or virtual host name is placed offline,
uninstallation will fail.
2. On the executing node, execute the following command to stop the Common Component services:

5. On both the executing and standby nodes, uninstall Replication Monitor.
For details about uninstallation, see section 2-1-4 .
6. Change the services that were set to Do not restart in step 4 back to Restart.
2-3 Notes on Installation and Uninstallation

2-3-1 Notes on Uninstalling Device Manager
Do not uninstall Device Manager in an environment where Replication Monitor is installed. When uninstalling
Device Manager, first uninstall Replication Monitor.
If Device Manager is uninstalled in an environment where Replication Monitor is installed, even if Device
Manager is re-installed, Replication Monitor cannot be used. To use Replication Monitor, you must first
uninstall Replication Monitor, install and set up Device Manger, and then re-install Replication Monitor.
2-3-2 Notes on Stopping Command View XP AE Suite software Services and

Daemons
This subsection gives notes on stopping a service or daemon by using the hcmdssrv command in an
environment where Device Manager has been installed.
• Executing the hcmdssrv command with the stop option specified stops the following services or
daemons:
• HiRDB
If Command View XP AE Suite software other than Device Manager or Replication Monitor has been
installed, the services or daemons of that Command View XP AE Suite software might also stop. For
details, see the relevant Command View XP AE Suite software manual.
• If the hcmdssrv command is executed with the stop option specified while another Command View XP
AE Suite software service or daemon (for example, HiCommandServer) is running, the following message
is displayed:
KAPM06445-E HiRDB cannot be stopped because a Suite product is connected to

HiRDB.
In such a case, stop the running Command View XP AE Suite software service or daemon, and then re-
execute the hcmdssrv command.
• In Windows, HiRDB/EmbeddedEdition_HD0 must always be running for Command View XP AE Suite
software. Check whether HiRDB/EmbeddedEdition_HD0 is running by viewing the list in the Services
window. If HiRDB/EmbeddedEdition_HD0 is not running, start HiRDB/EmbeddedEdition_HD0.
• In Windows, do not start or stop HiRDB/EmbeddedEdition_HD0 by using the Services window, which
is displayed by choosing Start, Setting, Control Panel, Administrative Tools, and then Services. Doing so
prevents the hcmdssrv command from operating normally. If you mistakenly perform the operation,
make sure that Startup Type for HiRDB/EmbeddedEdition_HD0 is set to Automatic, and then restart the
computer.
• In Windows, when the hcmdssrv command with the stop option is executed immediately after
HiCommandServer is stopped, the status of HiCommand Suite Single Sign On Service might change to
Stopping. In such a case, wait for a while, make sure that the displayed status of HiCommand Suite
Single Sign On Service changes to a blank (which indicates that the service is inactive), and then re-
execute the hcmdssrv command.

3 Environment Settings
This chapter explains how to set up an operating environment for using Replication Monitor, how to build an
environment in a cluster configuration, and how to start and terminate Replication Monitor.
This chapter explains the environment setting commands used as required after configuring the system, and
how to back up an operating environment that has been configured.
• 3.1 Setting Up the Operating Environment
• 3.2 Building a Cluster Configuration Environment
• 3.3 Starting and Terminating Replication Monitor
• 3.4 Environment Setting Command
• 3.5 Backing Up Operating Environment Information
• 3.6 Changing the Host Name for the Management Server
3-1 Setting Up the Operating Environment

3-1-1 Prerequisites for Setting Up an Operating Environment
Replication Monitor accesses the Device Manager server to use its functions. Therefore, a user account (user
name and password) is required for Replication Monitor to access the Device Manager server.
Replication Monitor has no user registration function of its own. Instead, it shares user accounts with the
Device Manager server installed on the same management server. This means that, in order to use Replication
Monitor, the Replication Monitor user’s name and password must be registered with Device Manager in
advance.
To access the Device Manager server from Replication Monitor, Replication Monitor users must be registered
as one of the following users who have Device Manager permissions:
• System Administrator
• Storage Administrator
For details about how to register Device Manager users, see the manual HP StorageWorks XP Advanced
Edition Device Manager Web Client User Guide.
3-1-2 Parameters Required for Operating Replication Monitor

A list of Replication Monitor parameters (and their default values) are shown below.
You can change these parameters, as required, after starting operation. We recommend that you use the
default values where appropriate because a careless change may cause an unexpected operation.
When you change a parameter setting, the changed value will go into effect after Replication Monitor restarts.
For details about how to start Replication Monitor, see section 3-3 .
Table 3-1 List of Parameters Required for Operating Replication Monitor
Classification Parameter Default value (unit)

Settings related to User Name None
Device Manager
Password None
Port Number 2001
Retrieve Information (Interval) None
Retrieve Information (Starts None
From)
Refresh Information (Interval) 24 (hour)
#
Refresh Information (Starts 03:02
From)
Settings related to dbm.driver JP.co.Hitachi.soft.HiRDB.JDBC.Prdb
database Driver
connections
dbm.url jdbc:hitachi:PrdbDrive://ENCODELANG
=
UTF-8
dbm.Connection.init 3 (number)
Table 3-1 List of Parameters Required for Operating Replication Monitor
Classification Parameter Default value (unit)

dbm.Connection.increment 2 (number)
dbm.Connection.increment.max 20 (number)
dbm.Connection.AliveTime 3600 (second)
dbm.Connection.create.timeout 600 (second)
dbm.Connection.retry.interval 240 (second)
dbm.Connection.retry.times 3 (times)
Settings related to logger.loglevel 20 (level)
log output
logger.sysloglevel 0 (level)
logger.MaxBackupIndex 10 (page)
logger.MaxFileSize 1 MB
Settings related to ssif.socketTimeout 3600 (second)
the information
acquisition interface
ssif.socketConnectTimeout 5 (second)
#
When a user selects the Daily operating schedule during setup of the Device Manager agent, the Device
Manager agent notifies the Device Manager server of the storage resource information acquired by the
Device Manager agent at 2:47 a.m. by default. Therefore, the default value of the time when Replication
Monitor requests Device Manager server to perform a refresh is set for 15 minutes later than the above
time. For details about the operating schedule of the Device Manager agent, see the manual HP
StorageWorks XP Advanced Edition Device Manager Agent Installation Guide.
The following subsections, which classify the parameters into general groups, list the meanings of each
parameter (contents to be set).
3-1-2-1 Parameters Related to Device Manager

The parameters related to Device Manager are used for accessing Device Manager from Replication Monitor
and automatically refreshing the Replication Monitor display (database). In Replication Monitor, automatic
refresh is performed based on the contents set as Retrieve Information or Refresh Information by a
user.
Parameters related to Device Manager are stored in the Replication Monitor database.
The following table shows the contents to be set in parameters related to Device Manager.
Table 3-2 List of Parameters Related To Device Manager
Parameter Contents to be set

User Name User name required for accessing the Device Manager server
Set a user name, using from 4 to 25 characters, that has been registered
in Device Manager in advance. The user name needs to be a registered
Device Manager system administrator or storage administrator.
Password Password required for accessing the Device Manager server
Set a string (using from 4 to 25 characters) that has been registered in
Device Manager in advance, as the password of the user set in User
Name.
Port Number Port number required for connecting to the Device Manager server
Set a port number used by the Device Manager server in HTTP
communication. You can set a value from 0 to 65535.
This value must match the value set for the Device Manager server.
Retrieve Information Interval for acquiring information from the Device Manager server (units:
(Interval) hours)
Specify 0, 0.5, 1, 6, 12, or 24.
When this value is set, Replication Monitor requests the Device Manager
server to acquire and provide information after the set interval. Based on
this request, Device Manager server returns information held in the
Device Manager server and related to copy pairs.
When 0 is set, no request to acquire information is made.
Hereafter, this value will be called the information acquisition interval.
Environment Settings 51
Table 3-2 List of Parameters Related To Device Manager

Retrieve Information Time to start acquiring information from the Device Manager server
(Starts From) Set in HH:MM (hour:minute) format.
When this value is set, a request (sent to the Device Manager server) to
acquire information is started at the set time.
However, when a hyphen (-) is set, no request to acquire information is
made.
Hereafter, this value will be called the information acquisition start time. If
you want to set the information acquisition start time to exactly 24 o'clock,
set 00:00. You do not need to set this item if 0 is specified in Retrieve
Information (Interval).
Refresh Information Interval for refreshing information on the Device Manager server (units: hours)
(Interval) Specify 0, 0.5, 1, 6, 12, or 24.
When this value is set, at the set interval a request to refresh information
on the Device Manager server is sent from Replication Monitor to the
Device Manager server. Based on this request, the Device Manager
server acquires information from its managed hosts and storage
subsystems to update the information it already holds. At the same time,
the Device Manager server returns information related to copy pairs to
When 0 is set, no request to refresh information is made.
Hereafter, this value will be called the refresh interval.
Refresh Information Time to start refreshing information on the Device Manager server
(Starts From) Set in HH:MM (hour:minute) format.
When this value is set, a request (sent to the Device Manager server) to
refresh information is started from the set time.
However, when a hyphen (-) is set, no request to refresh information is
started.
Hereafter, this value will be called the refresh start time. If you want to set
the refresh start time to exactly 24 o'clock, set 00:00. You do not need to
set this item if 0 is specified in Refresh Information (Interval).
In the parameters described above, User Name, Password, and Port Number are set to the values entered
by the user at installation.
You can use the hrpmsetup command to change parameters as required. Additionally, by executing the
hrpmsetup command with the -v option specified, you can reference set values except for those of
Password.
For details about the hrpmsetup command, see section 3-4 .
• About Retrieve Information and Refresh Information
In Replication Monitor, you can periodically acquire information from the Device Manager server by
setting Retrieve Information (Interval) and Retrieve Information (Starts From). You
can also refresh information on the Device Manager server periodically by setting Refresh
Information (Interval) and Refresh Information (Starts From). The refreshing of
information on the Device Manager server can be performed periodically as a function of Device Manager
in addition to the refreshing performed by a request from Replication Monitor.
• Relation between the Replication Monitor restart time and the value set for Retrieve Information or
Refresh Information
When the time set as the information acquisition start time or refresh start time is earlier than (previous to)
the Replication Monitor activation time, the interval set as the information acquisition interval or refresh
interval is successively added starting from the set start time, and the first request to acquire or refresh
information is made when the first time is reached. The request does not wait until the information
acquisition time or the refreshing time on the following day or until the corresponding time on that day.
See the figure shown below. In this case, the first refresh time is 15:02.
Figure 3-1 Relation between Replication Monitor Restart Time and the Refreshing Time
• Relation between the Replication Monitor operation and the value set for Retrieve Information or Refresh
Information
The table below shows the relation between the Replication Monitor operation and the value set for
Retrieve Information or Refresh Information:
Values set in the parameter Replication Monitor operation

Retrieve Information Refresh Information
Interval Starts Interval Starts From Request to acquire Request to
From information refresh
0 Not 0 Not required
required
0 Not 0.5, 1, 6, 12, or 24 —
required
0 Not 0.5, 1, 6, 12, or 24 Time Y
required
0.5, 1, 6, 12, or 24 — 0 Not required
0.5, 1, 6, 12, or 24 — 0.5, 1, 6, 12, or 24 —
0.5, 1, 6, 12, or 24 — 0.5, 1, 6, 12, or 24 Time Y
0.5, 1, 6, 12, or 24 Time 0 Not required Y
0.5, 1, 6, 12, or 24 Time 0.5, 1, 6, 12, or 24 — Y
0.5, 1, 6, 12, or 24 Time 0.5, 1, 6, 12, or 24 Time Y Y
Legend:
—: Indicates that the setting value is a hyphen (-).
(blank): Indicates that no request to acquire information and no refresh request is made.
Y: Indicates that a request to acquire information or a refresh request is made.
3-1-2-2 Parameters Related to Database Connections

Replication Monitor uses a HiRDB database as the storage destination of setting information, such as that of
monitoring functions. Parameters related to the database connections are pieces of information required for
using HiRDB and are set in the property file database.properties. When changing their content, use a text
editor.
database.properties is stored in the following directories:
®
In Windows :
Replication-Monitor-installation-folder\conf
Contents set in parameters related to database connections are shown below.
Table 3-3 List of Parameters Related To Database Connections

dbm.driver JDBC driver
Table 3-3 List of Parameters Related To Database Connections

Use the default value without change.
dbm.url A connection string (URL) to DBMS
Use the default value without change.
dbm.Connection.init Number of connections created initially
A value from 1 to 10 can be set.
dbm.Connection.increment Number of connections created when shortage of connections occurs in
the connection pool.
dbm.Connection.increment.max Maximum number of connections that can be held in the connection pool
dbm.Connection.AliveTime Connection alive time (units: seconds)
dbm.Connection.create.timeout Timeout time for connection creation (units: seconds)
dbm.Connection.retry.interval Retry interval between connection acquisition requests (units: seconds)
dbm.Connection.retry.times Retry times of connection acquisition request
In the parameters described above, do not change dbm.driver and dbm.url.

We recommend that the default values be used for the other parameters except when a specific problem
requires them to be changed.
3-1-2-3 Parameters Related to Log Output

Replication Monitor outputs various log types relating to the system operation. Parameters related to the log
output are pieces of information required for controlling log output and are set in the property file
logger.properties. When changing their contents, use a text editor.
logger.properties is stored in the following directories:
®
In Windows :
Contents set in parameters related to the log output are shown below.
Table 3-4 List of Parameters Related To Log Output

logger.loglevel An output threshold value of the trace log unique to Replication Monitor
#
Specify 0, 10, 20, or 30 . Log information equal to or less than the set
threshold value is output as a trace log unique to Replication Monitor.
logger.sysloglevel An output threshold value of logs output to the event log (Windows).
#
Specify 0, 10, 20, or 30 . Log information equal to or less than the set
threshold value is output to the event log.
logger.MaxBackupIndex Maximum value of the backup file of the trace log unique to Replication Monitor
(number of pages)
Specify an integer value from 1 to 16.
logger.MaxFileSize Maximum file size of the trace log unique to Replication Monitor
Specify a value in the range shown below depending on the specified format.
You can specify a value in kilobytes or megabytes by adding KB or MB to the
end of the value.
When specifying in an integer value: from 4096 to 2147483647
When specifying in KB format: from 4 KB to 2097151 KB
When specifying in MB format: from 1 MB to 2047 MB
# If a large value such as 30 is set, the detailed log is output, however, log output increases.
For the parameters described above, when a value is not set or the set value is outside the minimum or
maximum range, the default value is applied.
We recommend that the default values be used for parameters except when a specific problem requires them
to be changed.
3-1-2-4 Parameters Related to the Information Acquisition Interface
Parameters related to the information acquisition interface are pieces of information used to specify the
interface in acquiring information from the Device Manager server and are set in the property file
serverstorageif.properties. When changing their contents, use a text editor.
serverstorageif.properties is stored in the following directories:
®
In Windows :
Contents set in parameters related to the information acquisition interface are shown below.
Table 3-5 List of Parameters Related To Information Acquisition Interface

ssif.socketTimeout Time to block reading information from the Device Manager server (units:
seconds)
Specify a value from 1 to 86400. When 0 is set, wait until the reading of
information finishes.
ssif.socketConnectTimeout Waiting time for connection to the Device Manager server (units: seconds)
Specify a value from 1 to 3600. When 0 is set, wait until the connection is
established.
We recommend that the default values be used for the parameters described above except when a specific
problem requires them to be changed.
3-2 Building a Cluster Configuration Environment

Using Replication Monitor in a cluster environment enables you to enhance the availability of Replication
Monitor.
Requirements for cluster environments supported by Replication Monitor are as follows:
• Platform
• In Windows®:
Microsoft® Windows® 2000 Advanced Server Operating System (SP4),
Microsoft® Windows Server 2003, Enterprise Edition Operating System (32 bits) or
Microsoft® Windows Server 2003, Enterprise Edition Operating System (SP1) (32 bits)
• Cluster software
• In Windows®:
Microsoft Cluster Service (MSCS)
• Cluster configuration
Two-node Active - Standby configuration
Each of the following sections explains how to build a cluster configuration from an environment where
Replication Monitor is already in operation in a non-cluster configuration.
Also, when you are changing the environment from a non-cluster configuration to a cluster configuration,
always obtain a backup of the database. For details on how to backup, see section 3-5 .
To execute the commands and operations described in this section, the following user must be logged in to the
system:
In Windows®:
An administrator group user
3-2-1 Specifying Cluster Environment Settings in the Executing Node (When

Using MSCS)
This subsection explains how to specify settings for a cluster environment in the executing node in Windows.
The following procedures assume that cluster software and a shared disk are ready and that the management
server with Replication Monitor already set up is set to be the executing node in a cluster configuration. It is
also assumed that Common Component services have already started.
To specify settings for a cluster environment in the executing node in Windows:
1. Execute the following command to output the database contents to a file.
Common-Component-installation-folder\bin\hcmdsdbmove /export /datapath data-

input-and-output-folder
NOTE: Specify an absolute path for data-input-and-output-folder.
If you are using an existing folder for data-input-and-output-folder, either delete or empty it before
executing the command.
2. When other Command View XP AE Suite software are in operation, terminate the service tasks of those
Command View XP AE Suite software and services of Common Component (HiCommand Suite Common
Web Service and HiCommand Suite Single Sign On Service).
For details about how to terminate other Command View XP AE Suite software services, see the
corresponding product manual.
When stopping the Command View XP AE Suite software services, stop them in the following order.
For details, see the documentation for each product.
(i) Other Command View XP AE Suite software services
(ii) Common Component services
3. Create the cluster setting file cluster.conf using a text editor.
In the cluster setting file, specify whether the node is the executing or standby node, and specify the host
names of the virtual host, executing node, and standby node. Use the formats shown below:
mode = Specifies whether the node is the executing or standby node.

virtualhost = Specifies the host name of the virtual host.
onlinehost = Specifies the host name of the executing node.
standbyhost = Specifies the host name of the standby node.
In the following example, items are specified for an executing node:
mode = online
virtualhost = virt99
onlinehost = hrpm5
standbyhost = hrpm7
Store the created cluster file in Common-Component-installation-folder\conf.
NOTE: In the cluster setting file cluster.conf, you cannot use IP addresses to specify the host names of
the virtual host, executing node, or standby node.
The virtual host name specified for virtualhost must be valid for the corresponding IP address and
must be accessible.
4. Execute the following command to re-create a database system on a shared disk:
Common-Component-installation-folder\bin\hcmdsdbremake /cluster /databasepath

database-recreation-folder
NOTE: Specify an absolute path of no more than 63 bytes for database-recreation-folder. Note that a
file separator cannot be used at the end of a name for database-recreation-folder. If it is used, a
command error occurs. In this case, remove the file separator, and re-execute the command.
NOTE: When executing this command, the setting for the port number used by the embedded
database HiRDB returns to the default value (23032). Thus, when the system is running with a port
whose number is not the default value, you must reset the port number after executing this command.
For details on how to change a port number, see the manual HP StorageWorks Command View XP
Even if other Command View XP AE Suite software are in operation, you need to execute this step
once only.
5. Execute the following command to register the database contents output in step 1 in the database:
Common-Component-installation-folder\bin\hcmdsdbmove /import /datapath data-

input-and-output-folder
NOTE: Specify an absolute path for data-input-and-output-folder.
For countermeasures for a registration failure of a database, see section 3-2-3 .
6. Execute the following command to terminate Common Component services (HiCommand Suite Common
Web Service and HiCommand Suite Single Sign On Service) and databases:
7. Choose Start, Setting, Control Panel, Administrative Tools, and Services. Open the following service
properties in the Service window, and then change Startup Type from Automatic to Manual.
• HiCommandServer
When a Command View XP AE Suite software other than Replication Monitor and Device Manager is
operating on the same management server with Replication Monitor, see the manual for each product
to determine whether Startup Type of the Command View XP AE Suite software needs to be
changed.
8. Register the resources shown below (such as shared resources and services) into the cluster software.
For details on how to register resources into cluster software, see the manual HP StorageWorks
Command View XP Advanced Edition Device Manager Server Installation and Configuration Guide.
• IP address of cluster manager
• The shared disk where the database is created
• The following services:
• HiCommandServer
• HiRDBClusterService_HD0
When Command View XP AE Suite software other than Replication Monitor and Device Manager is
to determine whether the Command View XP AE Suite software service needs to be registered in the
cluster software.
3-2-2 Specifying Cluster Environment Settings in the Standby Node (When

Using MSCS)
The following procedures assume that cluster software and a shared disk are ready and that the management
server where Replication Monitor has been set up is set to be the standby node in a cluster configuration.
To specify settings for a cluster environment in the standby node in Windows®:
1. When other Command View XP AE Suite software are in operation, terminate the service tasks of those
Command View XP AE Suite software and services of Common Component (HiCommand Suite Common
Web Service and HiCommand Suite Single Sign On Service).
For details on the how to terminate other Command View XP AE Suite software’s services, see the
corresponding product manual.
Execute the following command to terminate HiCommand Suite Common Web Service and HiCommand
Suite Single Sign On Service:
details, see the documentation for each product.
(i) Other Command View XP AE Suite software services
2. Create the cluster setting file cluster.conf using a text editor.
In the cluster setting file, specify whether the node is the executing or standby node, and specify the host
names of the virtual host, executing node, and standby node. Use the formats shown below:
mode = Specifies whether the node is the executing or standby node.

virtualhost = Specifies the host name of the virtual host.
onlinehost = Specifies the host name of the executing node.
standbyhost = Specifies the host name of the standby node.
In the following example, items are specified for a standby node:
mode = standby
virtualhost = virt99
onlinehost = hrpm5
standbyhost = hrpm7
Store the created cluster setting file in Common-Component-installation-folder\conf.

In the cluster setting file cluster.conf, you cannot use IP addresses to specify the host names of
the virtual host, executing node, or standby node.
The virtual host name specified for virtualhost must be valid for the corresponding IP address
and must be accessible.
3. Execute the following command to change the setting in order to use a database on a shared disk:
Common-Component-installation-folder\bin\hcmdsdbremake /cluster /databasepath

database-recreation-folder
NOTE: For database-recreation-folder, use an absolute path of no more than 63 bytes to specify the
same folder that was specified when a database was re-created on the shared disk in the executing
node.
Note that a file separator cannot be used at the end of a name for database-recreation-folder. If it is
used, a command error occurs. In this case, remove the file separator, and re-execute the command.
NOTE: When executing this command, the setting for the port number used by the embedded
database HiRDB returns to the default value (23032). Thus, when the system is running with a port
whose number is not the default value, you must reset the port number after executing this command.
For details on how to change a port number, see the manual HP StorageWorks Command View XP
Even when other Command View XP AE Suite software are in operation, you need to execute this
step once only.
4. Execute the following command to terminate Common Component services (HiCommand Suite Common
Web Service and HiCommand Suite Single Sign On Service) and databases:
5. Choose Start, Setting, Control Panel, Administrative Tools, and Services. Open the following service
properties in the Service window, and then change Startup Type from Automatic to Manual.
• HiCommandServer
When Command View XP AE Suite software other than Replication Monitor and Device Manager are
to determine whether Startup Type of the Command View XP AE Suite software needs to be
changed.
6. Register the resources shown below (such as shared resources and services) into the cluster software.
However, if the resources have been registered on the executing node, you do not need to register the
resources on the standby node.
For details on how to register the resources into cluster software, see the manual HP StorageWorks
Command View XP Advanced Edition Device Manager Server Installation and Configuration Guide.
• IP address of cluster manager
• The shared disk where the database is created
• The following services:
• HiCommandServer
• HiRDBClusterService_HD0
When Command View XP AE Suite software other than Replication Monitor and Device Manager are
to determine whether the Command View XP AE Suite software service needs to be registered in the
cluster software.
3-2-3 Troubleshooting for Building a Cluster Environment

This subsection explains the countermeasures for when a database registration using the hcmdsdbmove
command fails. The countermeasures differ depending on whether the Replication Monitor database has been
backed up.
3-2-3-1 In Windows
3-2-3-1-1When a backup has been taken
To recover the system in Windows when a backup has been taken, perform the following procedure:
1. Stop the Device Manager server by selecting Start, Programs, HP Command View XP AE, Device
Manager, and then Stop Server.
2. Stop the Common Component services by executing the following command:
3. Restore the backup of the Replication Monitor database.

For details on the restoration methods, see section 3-5-2 .
4. Resume the cluster configuration by confirming that the Common Component services and the Device
Manager server have stopped, and then carry out step 5 and onwards described in section 3-2-1 .
3-2-3-1-2When a backup has not been taken
To recover the system in Windows when a backup has not been taken, reinstall Replication Monitor and Device
Manager by performing the following procedure:
1. Open the command prompt, and then restore the status of Replication Monitor by executing the following
command:
cd Common-Component-installation-folder\HDB\bin
pdntcmd.bat
pdrels -r HRPM_RDAREA
2. Uninstall Replication Monitor.

For details on how to uninstall Replication Monitor, see section 2-1-4 .
3. Uninstall and then reinstall Device Manager.
For details on how to uninstall and install Device Manager, see the manual HP StorageWorks Command
For details on how to install Replication Monitor, see section 2-1-2 .
5. In order to resume the cluster configuration, carry out step 2 and onwards described in section 3-2-1 .
3-2-4 Notes on Using Replication Monitor in a Cluster Environment

When executing the hrpmsetup command in a cluster environment, use a machine in an online mode.
If any changes are made to parameters that are required for Replication Monitor operations, the service or
daemon must be restarted to apply the configuration changes. Make sure that nobody is accessing services or
daemons of Command View XP AE Suite software, and then restart the services or daemons by performing the
following procedure:
3-2-4-1 In Windows
3-2-4-1-1When changes have been made to parameters associated with Device Manager
To restart services in Windows when changes have been made to parameters associated with Device
Manager, perform the following procedure:
1. Open the Cluster Administrator window by choosing Start, Settings, Control Panel, Administrative Tools,
and then Cluster Administrator, and then place the following services offline:
• HiCommandServer
2. Return the above services back to online.
3-2-4-1-2When changes have been made to parameters that are not associated with
Device Manager
To restart services in Windows when changes have been made to parameters that are not associated with
Device Manager, perform the following procedure:
1. Change the parameters in the settings files contained in the following folder so that both settings files for
the executing system and standby system are identical:
2. Start services by following the procedure described in section 3-2-4-1 .
3-3 Starting and Terminating Replication Monitor

Replication Monitor operates as part of HiCommand Suite Common Web Service, a service of Common
Component. Therefore, starting and terminating of Replication Monitor are performed via starting and
terminating of Common Component services.
To execute the commands described in this section, the following user must be logged in to the system:
In Windows®:
3-3-1 Starting Replication Monitor

To start Replication Monitor, execute the following command:
®
In Windows :
Common-Component-installation-folder\bin\hcmdssrv /start
NOTE: Device Manager must be started for Replication Monitor to operate normally.
However, Common Component services and Device Manager services must be started in a set order.
Start them in the following order:
(i) Common Component services
(ii) Device Manager services
For details on how to start the Device Manager services, see the manual HP StorageWorks Command
View XP Advanced Edition Device Manager Server Installation and Configuration Guide. For the start
order when other Command View XP AE Suite software are running, see the manual for the target
product.
When the hcmdssrv command is executed as described above, the embedded database HiRDB also
starts.
3-3-2 Terminating Replication Monitor
To terminate Replication Monitor, execute the following command:
In Windows®:
NOTE: Operations of other products are not guaranteed when services of Common Component are
terminated while other Command View XP AE Suite software such as Device Manager are operating on the
same server. Accordingly, do not terminate services of Common Component in an environment where other
Command View XP AE Suite software are operating except when all Command View XP AE Suite software
need to be terminated.
NOTE: Common Component services and Device Manager services must be stopped in a set order. Stop
them in the following order:
(i) Device Manager services

For details on how to stop Device Manager services, see the manual HP StorageWorks Command View
XP Advanced Edition Device Manager Server Installation and Configuration Guide. For details on the
stopping order when other Command View XP AE Suite software are running, see the manual
corresponding to each product.
If other Command View XP AE Suite software have stopped and the hcmdssrv command is executed as
described above, the embedded database HiRDB also stops.
3-3-3 Checking Operation Status of Replication Monitor

Execute the following command to check whether Replication Monitor is operating:
®
In Windows :
Common-Component-installation-folder\bin\hcmdssrv /status
In the following example, the results are for when Replication Monitor is operating:
>hcmdssrv /status
KAPM05007-I Already started service. service-name=HiCommand Suite Common Web Service
KAPM05007-I Already started service. service-name=HiCommand Suite Single Sign On Service
In the following example, the results are for when Replication Monitor is terminating:
>hcmdssrv /status
KAPM05009-I Already stopped service. service-name=HiCommand Suite Common Web Service
KAPM05009-I Already stopped service. service-name=HiCommand Suite Single Sign On Service
If the hcmdssrv command is executed as described above, you can also check whether the embedded
database HiRDB is running. If the embedded database HiRDB is running, the following message appears
in the execution result described above:
KAPM06440-I The HiRDB service has already started.
The following message appears if the embedded database HiRDB is inactive:
KAPM06441-I The HiRDB service has already stopped.

3-4 Environment Setting Command
This section explains how to use the hrpmsetup command to set or view the parameters for Replication
Monitor that impact Device Manager operations. Using the hrpmsetup command enables you to re-set
parameter values after the start of Replication Monitor Server.
The hrpmsetup command is stored in the directories shown below:
In Windows®:
Replication-Monitor-installation-folder\CLI\
3-4-1 Setting or Viewing the Parameters Related to Device Manager

3-4-1-1 Format
In Windows®:
hrpmsetup.bat [-v|-h]
3-4-1-2 Description
Executing this command without specifying an argument enables you to set parameter values interactively.
When you execute the command with the -v option specified, already set contents are displayed.
Parameters that can be set with this command are as follows. For details about the contents set in each
parameter, see section 3-1-2-1 .
Parameter Meaning
User Name User name for accessing the Device Manager server
#1
Password Password for accessing the Device Manager server
Port Number Port number for connecting to the Device Manager server
Retrieve Information (Interval) Interval for acquiring information from the Device Manager
server
Retrieve Information (Starts From)#2 Time to start acquiring information from the Device Manager
server
Refresh Information (Interval) Interval for refreshing information on the Device Manager
server
Refresh Information (Starts From)#2 Time to start refreshing information on the Device Manager
server
#1 If you execute the command without specifying an argument, you are requested to enter the password three
times; For the first entry, enter the password of the current user account for user authentication, which was set
during installation or when the hrpmsetup command was executed previously. For the second entry, enter a
new password for the user account. The third entry is to confirm the second entry. Therefore, make sure that
you enter the same password correctly both times.
#2 If 0 is specified for Retrieve Information (Interval) or Refresh Information (Interval),
entering a value for this parameter is not required.
3-4-1-3 Arguments
-v
Specify this argument to display the set parameter values other than Password.
-h
Use this argument to find out how to use the command or display the command usage.
3-4-1-4 Return Values

0: Normal termination
1: Termination with an error
3-4-1-5 Message
When the command terminates with an error, a message appears showing the content of the error. For details
about messages, see 6 .
3-4-1-6 Supplementary Explanation

• To execute this command, the following user must be logged in to the system:
In Windows®:
• The validity and correctness of the user name and password that were set as a Device Manager user
account are not checked when the command is executed. Therefore, if you specify the incorrect user
account, the incorrect user account is registered. In this case, an authentication error occurs when
restarting Replication Monitor and then accessing Device Manager.
If you re-execute the hrpmsetup command to set the correct user account, enter the password of the
incorrect user account for the first password that is used for user authentication. If you have forgotten the
password of the incorrect user account, re-install Replication Monitor and reset the user account.
• You do not need to stop Replication Monitor when executing this command.
• When the command is executed, the embedded database HiRDB must be running. For details on how to
check the operating status, see section 3-3-3 .
• When you have changed a set value, you need to restart Replication Monitor to make the changed setting
effective.
For details about starting and terminating Replication Monitor, see section 3-3 .
• If processing is canceled while the command is being executed, processing is forcibly canceled
regardless of any reply to the message asking you whether to continue processing. For example, when
pressing the C key together with the Ctrl key while the command is being executed, the message
Terminate batch job (Y/N)? appears. The batch job finishes even if you enter N.
3-4-1-7 Execution Examples
In the following example, no argument is specified:
>hrpmsetup
KAVN00161-I Enter the Device Manager password currently stored in the database.
: manager
KAVN00150-I Register the user name that the system uses to access the Device
Manager Server. : system
KAVN00151-I Register the password that the system uses to access the Device
Manager Server. : new_manager
KAVN00152-I Re-enter the registered password. : new_manager
KAVN00153-I Register the port number that the system uses to access the Device
Manager Server. : 2001
KAVN00154-I Select the time interval (0, 0.5, 1, 6, 12, or 24) for acquiring
information. : 0
KAVN00156-I Select the time interval (0, 0.5, 1, 6, 12, or 24) for refresh
operations. : 24
KAVN00157-I Register the time to start the refresh operation. (HH:MM) : 03:02
KAVN00158-I Parameter information was updated.
>
In the following example, the -v option is specified:
>hrpmsetup -v
Device Manager User Name : system
Device Manager Port Number : 2001
Retrieve Information Interval : 0
Retrieve Information Start Time : -
Refresh Information Interval : 24
Refresh Information Start Time : 03:02
>
3-5 Backing Up Operating Environment Information
This section explains how to back up operating environment information of Replication Monitor (property file
and database) and how to restore databases.
3-5-1 Backing Up Operating Environment Information

To back up operating Replication Monitor environment information, execute the hcmdsbackups command of
Common Component.
The hcmdsbackups command is stored in the directories shown below:
In Windows®:
Common-Component-installation-folder\bin\
NOTE: Back up the operating Replication Monitor environment information while the embedded database
HiRDB is running. For details on how to check the operating status, see section 3-3-3 .
3-5-1-1 Formats
In Windows®:
hcmdsbackups /dir backup-directory-name

[/type Command-View-XP-AE-Suite-product-name]
3-5-1-2 Description
Targets the data of Command View XP AE Suite software on the same management server for backup.
3-5-1-3 Arguments
dir backup-directory-name
Specify, using an absolute path, the name of the directory where the backup data is to be stored. If the
specified directory does not exist, it is created. If the specified directory is not empty, an error message is
output and backup stops.
In the specified directory, a directory with the name of the backed up Command View XP AE Suite
software and database directory are created. The directory with the name of the backed up Command
View XP AE Suite software data on a product basis and the database directory stores databases of
Command View XP AE Suite software containing Common Component.
You can specify characters other than ASCII code characters (from 0x20 to 0x7E) and some symbols (\
/ : , ; * ? " < > | $ % & ' `). Also, the following characters can be specified as delimiter
characters:
®
In Windows :
\ / :
type Command-View-XP-AE-Suite-product-name
Specify the product name of the Command View XP AE Suite software to be backed up. The database of
Common Component and the data of the specified product are backed up.
When this option is omitted, the database of Common Component and the data of all Command View XP
AE Suite software on the same management server are backed up.
When you back up the operating environment information of Replication Monitor, specify
ReplicationMonitor as the Command View XP AE Suite software name.

1: Error in the arguments
In Windows®:
• From the operating environment information for Replication Monitor, property files are stored as follows:
In Windows®:
directory-specified-in-/dir-option\ReplicationMonitor
• The database of Common Component is always backed up. The backup files for the databases of the
Command View XP AE Suite software containing Common Component are stored in the following
location and the following file names are assigned:
In Windows®:
directory-specified-by-/dir-option\database\backup.hdb
• Do not execute multiple instances of this command at the same time.
In the following example, the command backs up operating environment information of Replication Monitor:
>hcmdsbackups /dir C:\Backups /type ReplicationMonitor
In the following example, the command backs up data of all installed Command View XP AE Suite software:
>hcmdsbackups /dir C:\Backups
3-5-2 Restoring Databases

To restore databases of Replication Monitor, execute the hcmdsdb command of Common Component.
The hcmdsdb command is stored in the directories shown below:
In Windows®:
Common-Component-installation-folder\bin\
NOTE: Execute restoration after terminating services of Common Component and services of other
Command View XP AE Suite software.
3-5-2-1 Formats
In Windows®:
hcmdsdb /restore backup-file-name

/type Command-View-XP-AE-Suite-product-name
3-5-2-2 Description
For Command View XP AE Suite software on the same management server, the databases are restored from
the backup data.
3-5-2-3 Arguments
restore backup-file-name
Specify the absolute path of the backup file for the target Command View XP AE Suite software
database.
When the hcmdsbackups command is executed, specify the absolute path of the backup file
(backup.hdb) for the database stored in the database directory under the directory (specified in
the dir option).
Specify the name of the Command View XP AE Suite software to be restored. The database areas of the
specified Command View XP AE Suite software are recovered.
If ALL is specified for a Command View XP AE Suite software name, data of all Command View XP AE
Suite software on the same management server will be restored.
To restore the Replication Monitor database, specify ReplicationMonitor for the Command View XP
AE Suite software name.


In Windows®:
• Do not execute multiple instances of this command at the same time.
In the following example, the command restores the database of Replication Monitor:
>hcmdsdb /restore C:\Backups\database\backup.hdb /type ReplicationMonitor
In the following example, the command restores the database of all installed Command View XP AE Suite
software:
>hcmdsdb /restore C:\Backups\database\backup.hdb /type ALL
3-5-2-7 Notes
When using the hcmdsbackups command to back up the database, regardless of the ReplicationMonitor
specification in the type option, all databases of Command View XP AE Suite software are backed up.
However, when using the hcmdsdb command and specifying ReplicationMonitor in the type option to
restore the database, only the Replication Monitor database is restored. The databases of other Command
View XP AE Suite software containing Common Component are not restored. Therefore, inconsistency
between the Common Component database and the Replication Monitor database might occur and Replication
Monitor might not operate correctly.
When restoring the database by specifying ReplicationMonitor for the type option, execute the Refresh
All method, and then resume operation of the Replication Monitor. Executing the Refresh All method
synchronizes the latest information. For details on the Refresh All method, see section 4-3-1-3 .
If restoration is performed with ALL specified, all the databases of Command View XP AE Suite software at the
time backup was performed are restored. Therefore, information about Command View XP AE Suite software
installed after backup was performed is deleted. If you change the Command View XP AE Suite software
configuration on the same management server, always obtain a backup.
3-6 Changing the Host Name for the Management Server

To change the host name for the management server on which the Replication Monitor is installed, you must
edit several settings files beforehand.
NOTE: If you change the host name for the management server, an error might occur in other products
installed on the management server. Before you change the host name, make sure that an error will not
occur in other products.
To change the host name:

1. Stop all Command View XP AE Suite software services or daemons.
For details on how to stop the services or daemons, see step 2 in section 2-1-2 .
2. If the SSL settings have been configured, configure them again.
Use the host name after the change to configure the SSL settings. For details on how to configure SSL
settings, see the manual HP StorageWorks Command View XP Advanced Edition Device Manager
Server Installation and Configuration Guide.
3. Edit the httpsd.conf file.
Change the value for the ServerName parameter to the host name after the change.
The following describes the storage destination for the httpsd.conf file.
• For Windows:
installation-folder-for-Common-Component\httpsd\conf\
If SSL is set, you must also do the following:
• Change the host name specified for the <VirtualHost> tag to the host name after the change.
• Change the value for the ServerName parameter in the <VirtualHost> tag to the host name after
the change.
4. Edit the pdsys file and def_pdsys file.
Change the value for the –x option for the pdunit parameter to the host name after the change.
NOTE: Specify a virtual host name for a cluster configuration.
The following describes the storage destinations for the pdsys file and def_pdsys file.
• For Windows:
installation-folder-for-Common-Component\HDB\conf\pdsys
installation-folder-for-Common-Component\database\work\def_pdsys
5. Edit the pdutsys file and def_pdutsys file.
Change the value for the pd_hostname parameter to the host name after the change. If pd_hostname
does not exist, you do not need to edit these files.
NOTE: For a cluster configuration, edit the pdutsys file and def_pdutsys file on both the executing
node and standby node. In such a case, for pd_hostname, specify the host name for the executing
node.
The following describes the storage destinations for the pdutsys file and def_pdutsys file.
• For Windows:
installation-folder-for-Common-Component\HDB\conf\pdutsys
installation-folder-for-Common-Component\database\work\def_pdutsys
6. Edit the HiRDB.ini file.
Change the value for the PDHOST parameter to the host name after the change.
NOTE: Specify a virtual host name for a cluster configuration.
The following describes the storage destination for the HiRDB.ini file.
• For Windows:
installation-folder-for-Common-Component\HDB\conf\emb\HiRDB.ini
7. Edit the cluster.conf file (only for a cluster configuration).
From among the virtual host name, host name for the executing node, and host name for the standby
node, change the corresponding host name to the host name after the change.
The following describes the storage destination for the cluster.conf file.
• For Windows:
installation-folder-for-Common-Component\conf\cluster.conf
8. Change the host name for the management server, and then restart the machine.
9. Make sure that the Common Component service is running.
• For Windows:
installation-folder-for-Common-Component\bin\hcmdssrv /status
10. Execute the hcmdschgurl command to change the host name in the URL for starting Web Client.
For details on how to use the hcmdschgurl command, see the manual HP StorageWorks Command
4 Operation
This chapter describes the Replication Monitor Web Client, provides basic information about its window
configurations, and also gives explanations on how to operate it.
• 4.1 Functions of Web Client
• 4.2 Starting and Terminating Web Client
• 4.3 Window Configuration and Displayed Items of Web Client
• 4.4 Setting a Monitoring Configuration
• 4.5 Identifying an Error Location
• 4.6 Changing a Pair Status
• 4.7 Calling Device Manager
• 4.8 Registering and Viewing License Information
• 4.9 Replication Monitor Security Management
• 4.10 Notes on Operating the Refresh Function
4-1 Functions of Web Client

This section provides an overview of the functions of Replication Monitor Web Client.
Web Client is an application for viewing information managed by Replication Monitor, and for manipulating pair
statuses. Web Client allows you to visually check the statuses of multiple hosts, subsystems, pair management
servers, and their related copy pairs, as well as manipulate the statuses of the copy pairs as necessary. In
addition, by setting up check conditions in advance, errors can be reported via email.
To view or manipulate information in Web Client, use a Web browser.
Replication Monitor Web Client supports the following functions:
• Checking copy pair statuses
• Monitoring copy pairs
• Changing copy pair statuses
• Configuring copy pairs
• Other functions
Table 4.1 lists the functions.
Table 4-1 List of Replication Monitor Web Client Functions
Type of function Function Explanation Reference

Checks copy pair Display a host Displays a list of hosts, and the Section 4-3 Window
statuses configuration configuration and status of the copy Configuration and
pair allocated to each host. Displayed Items of Web
Client
Display a subsystem Displays a list of storage Section 4-5 Identifying
configuration subsystems, and the configuration an Error Location
and status of the copy pair allocated
to each storage subsystem.
Display a pair Displays a list of pair management
configuration servers, and the configuration and
status of the copy pair defined in
the configuration file of each pair
management server.
Display a pair Displays a list of mutually cascaded
connection copy pairs for a particular copy pair.
Determine and display Displays the most significant pair Section 4-1-2
the most significant pair status of the copy pair statuses of Determining and
status subordinate nodes. Displaying the Most
Significant Pair Status
Table 4-1 List of Replication Monitor Web Client Functions
Type of function Function Explanation Reference

Monitors copy pairs Monitor a pair status Sets check conditions or an e-mail Section 4-1-1 Monitoring
address so that the user is notified and Notification of a Pair
by email when the copy pair has Status
attained a certain status. Section 4-4 Setting a
Monitoring Configuration
Changes copy pair Change a pair status Changes a pair status by splitting Section 4-6 Changing a
statuses and resynchronizing (forward, Pair Status
backward) a copy pair
Configures copy pairs Call Device Manager Calls Device Manager for allocating Section 4-7 Calling
a LUN for a host and creating or Device Manager
deleting a copy pair.
Other Manage license keys Manages Replication Monitor Section 4-8 Registering
licenses. and Viewing License
Information
Authenticate users Authenticates users and prevents Section 4-9 Replication
unauthorized users from accessing Monitor Security
Replication Monitor. Management
4-1-1 Monitoring and Notification of a Pair Status

Replication Monitor has a function that monitors a pair status and notifies the user (system administrator or
storage subsystem administrator) by email when the pair attains a status not expected by the administrator.
Immediately upon receipt of the email, the user can identify the location of the error from the information
displayed in Replication Monitor, and take action.
To use the pair status monitoring and notification function, determine the object to be monitored, the details
(such as the email address) for the email to be sent, and the pair status to be monitored. Set this information in
4-1-1-1 Items Set in a Monitoring Configuration

Table 4-2 Items That Can Be Set in a Monitoring Configuration
Item Setting
Monitored object Specify the object whose pair status is to be monitored. You
can select the object from the following four options:
• Host
• Subsystem
• Copy group
• Copy pair
Check condition Specify the pair status that is to trigger an email.
Email information Specify detailed email information to be sent when the status
of the monitored copy pair satisfies the check condition.
The following explains each item that can be set.

• Monitored object
Specify the object to be monitored.
Objects that can be specified as monitoring targets are hosts, subsystems, copy groups, and copy pairs.
The monitoring configurations take effect on the specified object regardless of the node on which the
monitoring configurations are set up. For example, to monitor the copy pair Pair1 that consists of LUN01
and LUN02, from the Hosts view the user can set up monitoring on either LUN01 on the node HOST_A or
LUN02 on the node HOST_B. If the user adds monitoring configurations on LUN01 on the node HOST_A,
the same monitoring configurations also apply to LUN02 on the node HOST_B.
The following describes the way added monitoring configurations are displayed in a list of monitoring
configurations:
Operation 71
• When you display a list of monitoring configurations in the Hosts view or Subsystems view, the
monitoring configurations for the copy pairs managed by that host or subsystem are displayed,
regardless of the node on which the monitoring configurations were set.
• The object address displayed in the list of monitoring configurations differs depending on the target
object type. When monitoring configurations are added to a host or subsystem, host-name or
subsystem-name is displayed. When monitoring configurations are added to a copy pair, the storage
subsystem name and LDEV number for the primary and secondary volume are displayed (the same
information is displayed regardless of the node on which the configurations were set up, if the setup is
for the same copy pair). When a monitoring configuration is added to a copy group, the following is
displayed:
pair-management-server-name > RAID Manager XP-configuration-definition-file-name > copy-group-
name
The table below shows the relationship between the monitored object and the object address
displayed in the list of monitoring configurations:
Table 4-3 Relationship between the Monitored Object and the Object Address Displayed in the List of
Monitoring Configurations
Type of view Monitored Object address (displayed example)

object
Hosts view Host host_A
Copy pair Pair03-14[LDEV01(subsystem_A)-LDEV02(subsystem_A)]
Subsystems view Subsystem subsystem_A
Pair Configurations Copy group PairConfigurations > pms_A > horcm1000.conf > group1
view
• Check condition
Set the check condition.
You can set a copy pair status (error, suspend, copying, sync) in Replication Monitor as the check
condition. The pair statuses in Replication Monitor correspond to the pair statuses in Device Manager.
Table 4-4 shows this correlation.
Table 4-4 Correlation between Pair Statuses in Replication Monitor and

Pair Statuses in Device Manager
Pair status in Replication Monitor Pair status in Device Manager

error Suspended
Error in LUSE
Suspending
Deleting
suspend Split
copying Copying
Reverse-Copying
sync Pair
When you have set a host, subsystem, or copy group as the monitored object, Replication Monitor
monitors the pair status of the specified object and notifies the user when the pair status satisfies the
check condition. The pair status is obtained by determining the most significant of the pair statuses of all
nodes that can be checked by Replication Monitor. Table 4-5 lists the rules for determining the most
significant pair status.
Table 4-5 Rules for Determining the Most Significant Pair Status
Most significant pair status Pair statuses that exist amongst the pairs
error Suspend copying sync
error Yes — — —
suspend No Yes — —
copying No No Yes —
sync No No No Yes
Operation 72
Legend:
Yes: There is at least one pair among the pairs that has this pair status
No: There is no pair among the pairs that has this pair status
—: The system does not take into account whether there is a pair that has this pair status.
• Email information
Specify detailed information to be included in emails that are sent when the status of a monitored pair
satisfies the check condition. This information includes the SMTP mail server that is to receive the email,
the email address of the receiver, and comments to be added to the email. Use ASCII characters when
specifying comments to be added to the email.
The specified email address is regarded as the email address of the monitored administrator.
4-1-1-2 Notified Details

A notification email contains the following details:
• Name of the monitoring configurations
• Type of monitored object
• Object address of the monitored object
• Check conditions that were set beforehand, and the satisfied check condition
• User-specified comments (optional)
The sender is hrpmalerter. The monitoring function is executed at the same interval at which Replication
Monitor automatically refreshes information (automatic refreshes are executed regardless of user operations).
Thus, if a copy pair satisfies the condition immediately after an automatic refresh is performed, the notification
email is not sent until the next automatic refresh. For example, if the automatic refresh interval is set to 6 hours
and a copy pair satisfies the configurations five minutes after an automatic refresh, the notification email is sent
5 hours and 55 minutes later. (The user can set the automatic refresh interval.)
Figure 4-1 Timing for Sending Email

Since the monitoring function monitors the object at a fixed interval, the monitored pair status might
continuously satisfy the check condition. The monitoring function enables the user to set the number of
notifications by following one of the methods given below.
• To specify the number of notifications when the check condition is satisfied
In the Add Monitoring Configuration dialog box or the Edit Monitoring Configuration dialog box, for the
Number of notifications item, enter the number of times a notification is to be sent. In this case, while the
condition specified beforehand is satisfied, the system periodically sends notifications until the specified
number is reached.
• When no limit is to be set for the number of notifications to be made when the check condition is satisfied
In the Add Monitoring Configuration dialog box or the Edit Monitoring Configuration dialog box, for the
Number of notifications item, select Everytime. In this case, while the condition specified beforehand is
satisfied, the system periodically sends notifications.
Operation 73
4-1-2 Determining and Displaying the Most Significant Pair Status
To enable the user to easily check copy pair statuses, Replication Monitor determines and displays the most
significant pair status for each node. Among all of the copy pair statuses contained in the node, the most critical
pair status is displayed as the most significant pair status. For example, if all pair statuses are sync, sync is
displayed as the most significant pair status. If there are pairs whose status are sync, pairs whose status are
error, and pairs whose status are copying, then error is displayed as the most significant pair status. For the
rules for determining the most significant pair statuses, see section 4-1-1 .
By checking the most significant pair status, the user can easily check whether there is a copy pair whose pair
status is error (or an unexpected status).
Figure 4-2 illustrates the concept of determining the most significant pair status.
Figure 4-2 Concept of Determining the Most Significant Pair Status

The most significant pair status is determined for each view: the Hosts view, Subsystems view, and the Pair
Configurations view. The basic unit for determining the most significant pair status is the node shown in the
navigation frame. For example, when the user chooses a host-name node in the navigation frame, the copy
pair status that is determined to be the most significant is displayed in Object List in the information frame, for
each host.
The following explains the scope for determining the most significant pair status in each view.
4-1-2-1 Hosts View

Replication Monitor determines the most significant status for all copy pairs related to the host, including the
cascaded copy pairs.
The table and figure below show the scope of the pair statuses for which the most significant is to be
determined and displayed in Object List in the Hosts view.
Table 4-6 Scope for Determining the Most Significant Pair Status (Hosts View)
Node selected in the Unit of pair statuses Scope of pair statuses for which the most significant is to be
navigation frame determined and displayed in Object List
Hosts Host Pair statuses of all LUNs related to the host
host-name LUN Pair statuses of all LDEVs contained in a cascade
configuration related to the copy pair of the target LUN
Operation 74
Table 4-6 Scope for Determining the Most Significant Pair Status (Hosts View)
Port/HSD/LUN LDEV Not included in the scope
Figure 4-3 Scope for Determining the Most Significant Pair Status (Hosts View)
4-1-2-2 Subsystems View
Replication Monitor determines the most significant pair status amongst all copy pairs related to the subsystem.
The most significant pair status is determined for all cascaded copy pairs whose primary or secondary volumes
reside in the subsystem.
Table 4-7 Scope for Determining the Most Significant Pair Status (Subsystems View)
Subsystems Subsystem Pair statuses of all LUNs related to the subsystem
subsystem-name LUN Pair statuses of all copy pairs whose primary or secondary
volume is the corresponding LUN.
Port/HSD/LUN LDEV Not included in the scope
Operation 75
Figure 4-4 Scope for Determining the Most Significant Pair Status (Subsystems View)
4-1-2-3 Pair Configurations View
Replication Monitor determines the most significant pair status amongst all copy pairs related to the pair
configurations, including the cascaded copy pairs and the copy pairs in the same copy group.
Table 4-8 Scope for Determining the Most Significant Pair Status (Pair Configurations View)
Node selected in the navigation frame Unit of pair statuses Scope of pair statuses for which the
most significant is to be determined
and displayed in Object List
Pair Configurations Pair management server Pair statuses of all LUNs related to
the pair management server
(including the host that functions as
a pair management server)
pair-management-server-name RAID Manager XP Pair statuses of all LUNs defined in
configuration definition file the RAID Manager XP configuration
definition file of the pair
management server
RAID Manager XP-configuration-definition-file- Copy group Pair statuses of all LUNs related to
name the copy group
copy-group-name Pair name Not included in the scope
pair-name LDEV Not included in the scope
LDEV LDEV-number LDEV Not included in the scope
Operation 76
Figure 4-5 Scope for Determining the Most Significant Pair Status (Pair Configurations View)
4-2 Starting and Terminating Web Client

This section describes how to start and terminate Replication Monitor, and how to call other Command View
XP AE Suite software, by using Replication Monitor Web Client.
4-2-1 Starting Operation of Web Client

There are two methods for starting operation of Replication Monitor by using Web Client:
• In Replication Monitor’s Login window, enter your user ID and password to log in.
• Call Replication Monitor from a different Command View XP AE Suite software.
4-2-1-1 In Replication Monitor's Login Window, Enter Your User ID and Password to Log in
If no other Command View XP AE Suite software is active on the management client, enter your user ID and
password in Replication Monitor’s Login window to log in.
To enter your user ID and password in Replication Monitor’s Login window and log in:
1. Specify the Replication Monitor URL in the browser.
http://Replication-Monitor-address:port-number/ReplicationMonitor/
In Replication-Monitor-address, specify the IP address or host name of Replication Monitor.
Operation 77
In port-number, specify the port number for HiCommand Suite Common Web Service (default is
23015).
NOTE: For SSL, use https and the port 23016 (default).
The values of Replication-Monitor-address and port-number are those specified at installation.

Entering URL displays the Start Replication Monitor window and the Login window.
2. In the Login window, enter your user ID and password, and then click the Login button. Before your first
use of Replication Monitor after installing it, you must register license information. Click the License
button to register license information and then log in. For details on registering license information, see
section 4-8 .
NOTE: The user ID and password to be used for logging in to Replication Monitor must have been
registered under System Administrator or Storage Administrator for Device Manager. For details on setting
up user permissions, see section 4-9 .
4-2-1-2 Calling Replication Monitor from a Different Command View XP AE Suite software
If a different Command View XP AE Suite software is running on the management client, you can call
Replication Monitor from that product.
To call Replication Monitor from a different Command View XP AE Suite software:
1. In the menu-bar frame, click Tools. The Tools window is displayed.
2. Click HP StorageWorks XP Replication Monitor. The main window of Replication Monitor is displayed.
You do not need to enter your user ID or password.
4-2-2 Terminating Operation of Replication Monitor

To terminate the main window of Replication Monitor, click Logout or Close in the menu-bar frame.
Logout
This command logs you out of Replication Monitor.
To prevent illegal access to Replication Monitor, make sure that you log out from Replication Monitor
once operation has ended.
Clicking Logout also logs you out from all other Command View XP AE Suite software that can be called
from the Tools window. When you want to use a Command View XP AE Suite software again, you must
log in again.
Close
This command simply closes the window without logging you out from Replication Monitor or other active
Command View XP AE Suite software.
When operation of Replication Monitor has ended, click Logout rather than Close.
4-2-3 Calling a Different Command View XP AE Suite software

To call a different Command View XP AE Suite software from Replication Monitor:
1. In the menu-bar frame, click Tools. The Tools window is displayed.
2. Choose the Command View XP AE Suite software you want to call. A new main window for the chosen
Command View XP AE Suite software is displayed. You do not need to enter your user ID or password.
NOTE:
• If you start an application other than Command View XP AE Suite software from the Tools window, you must enter
your user ID and password.
• User authorization for Replication Monitor conforms to user authorization for Device Manager.
4-3 Window Configuration and Displayed Items of Web Client

This section gives the names of the frames that comprise the Web Client window, and describes the items
displayed in the frames.
Operation 78
4-3-1 Configuration of Web Client's Main Window
The Web Client window consists of the four frames listed below. An explanation of the name and functionality
of each frame is provided later in this subsection.
• Menu-bar frame
• Navigation frame
• Method frame
• Information frame
In this manual, any window that appears in the method frame or information frame is called a subwindow.
The following figure shows all four frames.
Figure 4-6 Configuration of the Web Client Window

4-3-1-1 Menu-bar Frame
The menu-bar frame enables you to execute commands relating to the overall operation of Replication Monitor,
such as commands for logging out, viewing version information, and displaying help. When you execute a
command, a relevant popup window is displayed.
The following figure shows the menu-bar frame.
Figure 4-7 Menu-bar Frame

The following explains the commands displayed in the menu-bar frame.
Tools
This command calls other Command View XP AE Suite software and starts user-specified applications.
For details on how to set up user-specified applications (hcmdslink command), see the manual HP
Logout
This command logs out from Replication Monitor.
Close
Operation 79
This command closes the Web browser.
Profile
This command displays user information.
About
This command displays information about the product version and license type.
Help
This command displays the online help.
4-3-1-2 Navigation Frame

The navigation frame displays the objects monitored by Replication Monitor. These objects are displayed as
items in a tree structure. This tree is called the object tree, and each item in a tree is called a node.
Choosing a node determines the object on which operations are to be performed. Choosing a node displays
methods, which indicate operations. In the information frame, the result obtained by selecting List Objects in
the method frame is automatically displayed.
The navigation frame displays the Jump button, which supports operations in the object tree, and the Refresh
link, which refreshes the object tree.
The following figure shows the navigation frame.
Figure 4-8 Navigation Frame

4-3-1-2-1Object tree
The object tree displays the objects subject to management by Replication Monitor as nodes in the tree
structure. The object tree consists of Replication Monitor (the top level), Hosts, Subsystems, Pair
Configurations, and their subordinate nodes. Replication Monitor, Hosts, Subsystems, and Pair Configurations
are called root nodes.
Nodes are displayed as icons. For icons displayed in the object tree, see section 4-3-3-1 .
When you click at the left of a root node, the root node’s subordinate nodes are displayed. When you click
at the left of a subordinate node, the nodes that are subordinate to that node are displayed. Even if there
are no nodes subordinate to the selected node, still appears. However, clicking does not display
anything. The following explains the root nodes and their subordinate nodes displayed in the object tree.
Replication Monitor
Replication Monitor indicates all objects subject to management by Replication Monitor. Replication
Monitor appears as the root node indicating all objects subject to management by Replication Monitor.
Beneath the root node are Hosts, Subsystems, and Pair Configurations. Choose Replication Monitor
when you want to update all information in Hosts, Subsystems, and Pair Configurations, or when you
want to view all monitoring configurations. When you choose Replication Monitor, the Hosts, Subsystems,
and Pair Configurations items appear in a subwindow. Clicking one of these items displays, as a
subwindow, the window displayed when selecting the same node in the navigation frame.
Hosts
Hosts indicates the hosts managed by Replication Monitor, and all LUs of the storage subsystems used
by those hosts. Hosts is the root node of the Hosts view.
When you choose Hosts, the method frame displays a list of operations for all hosts. Clicking on the
left side of Hosts displays the nodes subordinate to Hosts. If you choose a subordinate node, the method
Operation 80
frame displays a list of operations for the individual host and LUs. The following figure shows the tree
structure subordinate to Hosts.
Figure 4-9 Tree Structure below Hosts

• host-name
A host-name indicates a host managed by Replication Monitor. When you choose a host-name, the
method frame displays a list of operations for that host.
Clicking on the left side of host-name displays the subordinate Port/HSD/LUN(s) in the object
tree.
• Port/HSD/LUN
Port/HSD/LUN indicates an LU of the storage subsystem that comprises a pair and is used by the
host managed by Replication Monitor. When you choose a Port/HSD/LUN, the method frame
displays a list of operations for that LU.
You can identify an LU according to the combination of port, HSD, and LUN displayed in
Port/HSD/LUN. The figure below shows an actual example of how port (port ID), HSD (host storage
domain name), and LUN (LU number) are displayed.
Subsystems
Subsystems indicates the storage subsystems managed by Replication Monitor and all LUs of the
storage subsystems. Subsystems is the root node of the Subsystems view.
When you choose Subsystems, the method frame displays a list of operations for all storage subsystems.
Clicking on the left side of subsystem-name displays the nodes subordinate to Subsystems, and when
you choose a subordinate node, the method frame displays a list of operations for the individual storage
subsystem and LUs. The following figure shows the tree structure subordinate to Subsystems.
Operation 81
Figure 4-10 Tree Structure below Subsystems
• subsystem-name
A subsystem-name indicates a storage subsystem managed by Replication Monitor. When you
choose a subsystem-name, the method frame displays a list of operations for that storage subsystem.
Clicking on the left side of a subsystem-name displays subordinate Port/HSD/LUN(s) in the

object tree.
• Port/HSD/LUN
Port/HSD/LUN indicates the LU that comprises a pair on the storage subsystem managed by
Replication Monitor. When you choose a Port/HSD/LUN, the method frame displays a list of
operations for that LU. You can identify an LU according to the combination of port, HSD, and LUN
displayed in Port/HSD/LUN. The figure below shows an actual example of how port (port ID), HSD
(host storage domain name), and LUN (LU number) are displayed.
Pair Configurations
Pair Configurations shows all the pair management servers managed by Replication Monitor, and all LUs
and LDEVs defined in the RAID Manager XP configuration definition file stored in the pair management
servers. Pair Configurations is the root node of the Pair Configurations view.
When you choose Pair Configurations, the method frame displays a list of operations for all the pair
management servers.
Clicking on the left side of Pair Configurations displays the nodes subordinate to Pair Configurations.
When you choose a displayed node, the method frame displays a list of operations for the individual host
and RAID Manager XP configuration definition file. The following figure shows the tree structure
subordinate to Pair Configurations.
Operation 82
Figure 4-11 Tree Structure below Pair Configurations
• pair-management-server-name
pair-management-server-name indicates a server that satisfies the following conditions:
• The Device Manager agent and RAID Manager XP have been installed.
• The host recognizes the command device.
When you choose a pair-management-server-name, the method frame displays a list of operations
for that pair management server.
Clicking on the left side of pair-management-server-name displays the subordinate RAID Manager
XP-configuration-definition-file-name(s) in the object tree.
• RAID Manager XP-configuration-definition-file-name
RAID Manager XP-configuration-definition-file-name indicates a RAID Manager XP configuration
definition file stored in a pair management server managed by Replication Monitor. When you choose
a RAID Manager XP-configuration-definition-file-name, the method frame displays a list of operations
for that RAID Manager XP configuration definition file.
Clicking on the left side of RAID Manager XP-configuration-definition-file-name displays the

subordinate copy-group-name(s) in the object tree.
• copy-group-name
copy-group-name indicates a copy group of a RAID Manager XP configuration definition file stored in
a pair management server managed by Replication Monitor.
When you choose a copy-group-name, the method frame displays a list of operations for that copy
group defined in the RAID Manager XP configuration definition file.
Clicking on the left side of copy-group-name displays the subordinate pair-name(s) in the object
tree.
• pair-name
pair-name indicates a pair of a RAID Manager XP configuration definition file stored in a pair
management server managed by Replication Monitor. When you choose a pair-name, the method
frame displays a list of operations for information relating to the copy pair.
Clicking on the left side of pair-name displays the subordinate LDEV LDEV-number(s) in the
object tree.
• LDEV LDEV-number
LDEV LDEV-number indicates an LDEV of a RAID Manager XP configuration definition file stored in a
pair management server managed by Replication Monitor. When you choose an LDEV LDEV-
number, the method frame displays a list of operations for each LDEV number.
4-3-1-2-2Jump buttons
At the top of the navigation frame, there are jump buttons for Hosts, Subsystems, and Pair Configurations.
Using these buttons enables you to choose the target node without scrolling, even when the tree structure
displaying the nodes becomes long. The figure below shows the jump buttons.
Operation 83
Figure 4-12 Jump Buttons
4-3-1-2-3Refresh
Clicking Refresh in the navigation frame refreshes all information contained in the navigation frame, based on
data held in the Replication Monitor database.
Figure 4-13 Refresh in the Navigation Frame

Note that you cannot update pair status information by clicking Refresh in the navigation frame. When you want
to update the pair status, click the Refresh object-to-be-refreshed method in the method frame.
4-3-1-3 Method Frame

The method frame displays the operations (methods) you can execute for the node selected in the navigation
frame. When you choose a method, Replication Monitor executes the selected operation. The method can be
selected in the popup window or information frame.
The figure below shows the method frame.
Figure 4-14 Method Frame

The following explains the methods displayed in the method frame. Different methods are displayed depending
on the node selected in the navigation frame.
List Objects
This method displays a list of items (such as pair information) relating to the node selected in the
navigation frame. When you select a node in the navigation frame, List Objects becomes selected in the
method frame.
Refresh object-to-be-refreshed
This method updates information related to the selected node. The scope of the information to be
updated differs depending on the node.
• Refresh All
This option updates all information relating to the Hosts, Subsystems, and Pair Configurations nodes.
• Refresh Host
This option updates only information relating to the selected host.
• Refresh Subsystem
This option updates only information relating to the selected storage subsystem.
• Refresh Pair Status
This option refreshes information related to the selected copy pair, copy group, LUN, or LDEV.
Show Monitoring Configurations
This method displays the monitoring configurations for the selected node.
Set Monitoring Configurations
This method sets the monitoring configurations for the selected node.
Change Pair Status
This method changes the pair status of the selected node.
Operation 84
If either Port/HSD/LUN or LDEV LDEV-number is selected in the navigation frame, Change Pair Status
does not appear in the method frame. To change the pair status, perform the operation from the link in
the information frame.
4-3-1-4 Information Frame

The information frame displays information related to the method selected in the method frame. As an
example, the following figure shows an information frame that is displayed when you select a node by choosing
Hosts-host-name-Port/HSD/LUN in the navigation frame, and then select List Objects in the method frame.
Figure 4-15 Example of Displayed Information Frame

The information frame displays icons to indicate the status of processing executed in Replication Monitor, pair
statuses, and copy directions of the pairs. For details on icons displayed in the information frame, see section
4-3-3-2 , 4-3-3-3 , or 4-3-3-4 .
Replication Monitor displays copy pair information in a cascade configuration by a combination of multiple
icons. For details on the display of a cascade configuration, see section 4-3-5 .
Among the items displayed in Replication Monitor’s information frame, those that become highlighted when you
position the mouse pointer on them can be sorted in ascending or descending order. The following explains the
sorting method.
The following figure shows an information frame with the mouse pointer positioned on one of the sortable
items.
Figure 4-16 Example of the Information Frame with the Mouse Pointer Positioned on a Sortable Item
When you position the mouse pointer on an item name and click, the information items under that item name
are sorted alternately (for each click) in ascending and descending order. You can use the Tab key to select an
item instead of using the mouse pointer. If an item is selected by using the Tab key, the items are sorted when
Operation 85
the Enter key is pressed. A triangular icon appears to the right of an item name whose information items have
been sorted.
If the List Objects - Port/HSD/LUN subwindow is displaying pairs in a cascaded configuration and you sort an
item, the cascaded configuration is destroyed. If you want to display pairs in a cascaded configuration, click the
item (where the primary (or secondary) volume icon is displayed) in Port/HSD/LUN displayed in the object table
in the information frame.
The information frame subwindow displays the information (link and last update time) managed by Replication
Monitor.
Object property
Detailed information about the Replication Monitor management target (selected in the navigation frame)
is displayed.
Object table
A list of related information about the Replication Monitor management target (selected in the navigation
frame) is displayed.
Help
This node displays the online help.
Last Updated
The subwindow that appears when you click List Objects in the method frame displays the last update
time. If you have not yet refreshed information after installing Replication Monitor, a hyphen (-) is
displayed as the last update time.
When multiple users are using Replication Monitor concurrently and one user updates information, the
updated information and the last update time are also displayed in other users’ windows.
All the last update times in the information frame are refreshed regardless of the information frame where
the refresh operation was performed. For information frames where the refresh operation was not
performed, the last update time is followed by Incomplete. Incomplete indicates that the displayed
information is older than the information at the last update time.
The following table shows the display format of the last update time:
Table 4-9 Display Format of the Last Update Time
Refresh type Display format of the last update time

Automatic Refresh (executed periodically at pre-set intervals)
Refresh Incomplete does not appear.
Retrieve Incomplete appears in all the information frames.
Manual Refresh (executed by the user using Web Client)
Refresh All Incomplete does not appear.
Refresh Host Incomplete appears in the information frames where the refresh operation has not
Refresh Subsystem been performed.
Refresh Pair Status
4-3-2 Web Client Dialog Boxes

In this manual, popup windows are called dialog boxes. The following shows some examples of dialog boxes.
Operation 86
Figure 4-17 Example Dialog Box 1
Figure 4-18 Example Dialog Box 2

The dialog boxes display detailed pair information, items, messages, and icons for performing various
operations on Replication Monitor. Choosing Help displays online Help relating to that dialog box and enables
you to view an explanation of the items in that dialog box.
Icons displayed in the dialog boxes indicate the status of processing executed in Replication Monitor, and pair
statuses. For details on icons displayed in the dialog boxes, see section 4-3-3-2 or 4-3-3-3 .
4-3-3 Icons Displayed in the Web Client Window

4-3-3-1 Icons in the Object Tree
This subsection explains the meanings of the icons displayed in the object tree of the navigation frame. When
you choose a node indicated by one of these icons, information related to that node is displayed in the
subwindow.
Table 4-10 Node Icons in the Object Tree
Icon Name Explanation

Replication Monitor icon Indicates the root node of all of Replication Monitor.
Host group icon Indicates the root node of the Hosts view.
Host icon Indicates a host node managed by Replication Monitor.
LU icon Indicates an LU managed by Replication Monitor.
Subsystem group icon Indicates the root node of the Storage Subsystems view.
Subsystem icon Indicates a storage subsystem node managed by Replication

Monitor.
Pair Configurations icon Indicates one of the following nodes of the Pair
Configurations view:
• Root node
• RAID Manager XP configuration definition file name
• Copy group name
• Copy pair name
P-VOL icon Indicates an LU or LDEV node of the primary volume among
copy pairs managed by Replication Monitor.
S-VOL icon Indicates an LU or LDEV node of the secondary volume
Operation 87
Table 4-10 Node Icons in the Object Tree

among the copy pairs managed by Replication Monitor.
4-3-3-2 Icons in the Information Frame and Dialog Boxes

Table 4-11 Icons of Replication Monitor Execution Results

Wait icon Indicates that an operation executed by Replication Monitor is
currently processing.
Error icon Indicates an error in an operation executed by Replication

Monitor.
Information icon Indicates the processing result of an operation executed by

Warning icon Indicates a warning, confirmation, or error occurred on the

management client for an operation executed, or to be executed,
by Replication Monitor.
4-3-3-3 Copy Status Icons in the Information Frame and Dialog Boxes
This subsection explains the meanings of Copy Status icons displayed in the information frame and dialog
boxes. If you click one of these icons while it is displayed under Copy Type in the object table, you can change
the copy pair status.
Note, however, that you cannot change the copy pair status if the copy type is CA-XP(Jrnl) (Continuous Access
XP Journal) or there is a restriction in the system configuration.
Table 4-12 Copy Status Icons
Icon Name Description of the icon displayed in Description of the icon displayed
the information frame in a dialog box
Error icon Indicates that an error has occurred in Indicates that a monitoring
the pair. configuration has been set for the
error status.
Suspend icon Indicates that the pair is split. Indicates that a monitoring
configuration has been set for the
split status.
Copying icon Indicates that the pair is being copied Indicates that a monitoring
in the forward or reverse direction. configuration has been set for the
status in which copying is
processing.
Sync icon Indicates that the pair is synchronized Indicates that a monitoring
(paired). configuration has been set for the
synchronous (Pair) status.
Not Applicable Indicates that Copy Type is not being Indicates that a monitoring
icon used. configuration has not been set for
that copy type.
4-3-3-4 Object Table Icons in the Information Frame

This subsection explains the meanings of icons displayed in the object table of the information frame. These
icons are displayed under the Pair Configuration and Action items in the object table.
The following explains the meanings of Pair Configuration icons displayed in the object table of the information
frame. Use these icons to display information about cascaded copy pairs in the information frame. For more
information on how to display a cascaded configuration in the information frame, see section 4-3-5 .
The following table lists the icons that indicate a volume.
Table 4-13 Primary Volume and Secondary Volume Icons (Pair Configuration)
Operation 88
Table 4-13 Primary Volume and Secondary Volume Icons (Pair Configuration)

P-VOL icon Indicates a primary volume.
Highlighted P-VOL icon Indicates the primary volume corresponding to the node
selected in the tree in the navigation frame.
S-VOL icon Indicates a secondary volume.
Highlighted S-VOL icon Indicates the secondary volume corresponding to the node
selected in the tree in the navigation frame.
The following table lists the icons that indicate the copy status and copy direction.
Table 4-14 Pair Status Icons (Pair Configuration)

No Arrow icon Indicates that the pair is split, or an error has occurred.
Right Arrow icon Indicates that the pair is being copied in the forward direction
from the primary volume to the secondary volume.
Left Arrow icon Indicates that the pair is being copied in the reverse direction
from the secondary volume to the primary volume.
Continue icon (to the left) Indicates that there is another copy pair that is cascaded to
the primary volume of the copy pair.
Continue icon (to the right) Indicates that there is another copy pair that is cascaded to
the secondary volume of the copy pair.
The following explains the Configuration icon displayed in the object table of the information frame.
Table 4-15 Monitoring Configuration Icon (Action)

Monitoring Configuration icon Indicates that a monitoring configuration has been set for the
copy pair.
4-3-4 Notes on Replication Monitor Operations

4-3-4-1 Notes on Web Client Operations
If you have performed any of the following operations on Replication Monitor Web Client, operations performed
in the information frame might not execute properly.
• Used a tool bar, menu bar, or link bar provided by a Web browser
Do not use items such as tool bars, menu bars provided by a Web browser to perform operations such as
migrating, updating, or canceling loading. However, you can print a window or change the font size from a
menu bar.
• Displayed the context menu of a Web browser
Do not display a Web browser’s context menu, which is displayed by right-clicking the mouse.
• Used a short-cut key or function key
Do not use operations such as Back, Open browser in new window, or Refresh that are provided in Web
browsers.
4-3-4-2 Notes on Changing a Storage Subsystem Configuration

When a change is made to the storage subsystem configuration, information about the new configuration is not
immediately reflected in Replication Monitor. In Replication Monitor, if the storage subsystem configuration is
changed as in the following cases, execute Refresh All to refresh all the information:
• The storage subsystem is changed (for example, a new disk drive is added)
• A product such as Device Manager, Remote Console, Remote Web Console, or RAID Manager XP is
used to change the storage subsystem configuration (such as creating a pair or performing a pair
operation).
Operation 89
4-3-5 Displaying Cascaded Copy Pairs
This subsection explains how information about cascaded copy pairs is displayed in the information frame. The
following shows an example of a cascade configuration based on the explanation below.
Figure 4-19 Example Cascade Configuration

LDEV2 is the secondary volume of LDEV1 and is also the primary volume of LDEV5 and LDEV6.
The following figure shows an example of the information frame displayed when Replication Monitor has the
configuration described above. Information about cascaded copy pairs is displayed as icons indicating volumes
and icons indicating the copy statuses and copy directions.
Figure 4-20 Example View for a Cascade Configuration

Replication Monitor displays a cascade configuration in which a particular LDEV is set as the reference point,
as a list of copy pairs. To make it easier to identify concatenation of volumes (secondary-primary volumes)
within a displayed cascade, Replication Monitor adjusts the position in which each copy pair is displayed. For
example, in the example view, the LDEV2 nodes in the second and third rows are indented to appear under the
LDEV2 node of the first row.
Replication Monitor also indicates whether the data of a pair has been copied and the direction in which it was
copied. An arrow corresponds to the pair status of Device Manager. The following table shows the correlation
between the Replication Monitor display and the Device Manager pair status.
Operation 90
Table 4-16 Correlation Between an Arrow Displayed in the Information Frame and the
Device Manager Pair Status
Status of Replication Monitor pair Status of Device Manager pair Arrow used
error Suspended
Error in LUSE
Suspending
Deleting
suspend Split
copying Copying
Reverse-Copying
sync Pair
4-3-6 Languages Displayed While Web Client Is Operating

Replication Monitor supports English en and Japanese ja as display languages. The language used by
Replication Monitor is determined by the language setting of the Web browser being used. The following table
shows the relationship between the language setting of the Web browser and the language displayed in the
Replication Monitor window. Replication Monitor can display only languages that have characters in UTF-8
encoding.
Table 4-17 Web Browser Language Setting and Displayed Language
Language setting in the Web browser Language displayed in the

window
Both en and ja have been set en has been set to have priority en
over ja
ja has been set to have priority ja
over en
en can be set, but ja cannot be set en
ja can be set, but en cannot be set ja
Neither en nor ja can be set en
In the following cases, the display language is determined by the language version of the OS and Web
browser, and by OS locale information.
• Buttons and dialog boxes directly displayed by the OS are displayed in the language corresponding to the
language version of the OS and Web browser, regardless of locale information.
• The character encoding defined in OS locale information is used when messages output by Replication
Monitor are output to log files or other resources that users can identify.
• The language corresponding to the language setting of the OS and Web browser is used in the Windows®
event log.
4-3-7 Displaying Multiple Items of Information for a Particular Node

When there are multiple information items for a particular node, Replication Monitor displays them in the
information frame or dialog box.
For example, when you have created several mount points using Volume Manager, or when you are sharing a
single LU among multiple hosts, multiple information items are displayed for the mount point item or the host
item in the LDEV detailed information window. In this case, a separate line of information is displayed for each
host (the mount points for each host are displayed as a concatenated string that contains delimiter commas (,)
and is not broken by line feeds).
The following figure shows an example view.
Operation 91
Figure 4-21 View of LDEV Detailed Information (When There Are Multiple Items of Information)
4-3-8 Error and Warning Messages

This subsection explains the display of error and warning messages. There are two types of messages, error
messages and warning messages, which are output when an error occurs. Error messages are output when an
error occurs on the management server. In the window that displays an error message, is also displayed.
Warning messages are output when an error occurs on the management client. In the window that displays a
warning message, is also displayed.

For more information on output messages, see 6 .
4-3-8-1 Error Messages Displayed in the Information Frame

The following figure shows an example of a displayed error message.
Operation 92
Figure 4-22 Example of an Error Message Displayed in the Information Frame
If an error occurs when you perform any of the following operations, an error message is displayed instead of
the usual information (such as pair information) in the subwindow that appears in the information frame.
Depending on the error that occurs, a detailed message may be displayed.
• Selecting a node in the navigation frame, or clicking a jump button
• Clicking a method in the method frame
• Clicking a button in the information frame
• Executing an operation from a dialog box to refresh a subwindow
No OK button or Close button is displayed in the information frame. Thus, when you want to change the view in
the subwindow, either choose a node in the navigation frame, or select a method in the method frame. If
Replication Monitor encounters an error, Help will be displayed in a subwindow. Choose Help to view online
Help.
4-3-8-2 Error Messages in Dialog Boxes

This subsection explains error messages that are displayed in dialog boxes. If you enter or select a value
incorrectly when operating Replication Monitor, an error message will be displayed in a dialog box.
The error message displayed in a dialog box shown in the figure below includes a message ID, error message,
Back and Close buttons, and Help. If you want to re-enter a value, click the Back button. Doing so returns you
to the window for entering and selecting values. Both the entered and selected values are saved, so correct the
value that was entered incorrectly. If you do not want to re-enter a value, click the Close button. The window
will close. The entered and selected information will not be saved. If you click Help, Help appears.
Operation 93
Figure 4-23 Example of an Error Message Displayed in a Dialog Box (Values Can Be Re-entered)
The error message displayed in the dialog box shown in the following figure includes a message ID, error
message, Close button, and Help. Depending on the error that occurs, a detailed message may be displayed.
Click the Close button to close the window. The entered and checked information will not be saved. If you want
to re-enter a value, click the Close button, and then re-open the window for entering and selecting values. If
you click Help, Help appears.
Figure 4-24 Example of an Error Message Displayed in a Dialog Box (Values Cannot Be Re-entered)
4-3-8-3 Warning Messages
When the user refreshes information or changes a pair status, Replication Monitor outputs a warning message
immediately before (or after) executing the operation. The window displays a message ID and warning
message. Check the message, and then continue operation.
4-4 Setting a Monitoring Configuration

This section explains how to set the monitoring configuration to issue an email notification when a copy pair
monitored by Replication Monitor has attained a specific status.
The following items can be set for monitoring configurations:
• Monitoring target
Specify the target whose pair status is to be monitored. Specifiable targets include hosts, subsystems,
copy groups, or individual copy pair units.
When an individual copy pair is specified as the monitoring target, the target is limited to the copy pair.
However, when a host, subsystem, or copy group is specified, all copy pairs belonging to the specified
target are monitored under the same condition.
• Check conditions
Specify a copy pair status (error, suspend, copying, or sync) as the condition that is to trigger the
action on the monitored target.
• Email information
Specify the information (email recipient (email address), email text (message), number of notifications to
be transmitted, etc.) necessary for email notifications, which are to be sent as the action taken when the
check conditions are met.
The following lists the items that can be set as the monitoring parameters.
Operation 94
Table 4-18 List of Items Set for Monitoring Parameters
Item Description Requirement

#1
Configuration Name Set a name to identify the monitoring configuration, using Mandatory
from 1 to 100 characters. The name must be unique.
Check Conditions Specify conditions to trigger the email notification, from Mandatory
among the following four copy pair statuses. Multiple
statuses can be selected for one monitoring target. When
multiple statuses are selected and one of the statuses is
satisfied, an email notification is performed.
• error
An error occurred.
• suspend
The copy pair is in the split status (Split).
• copying
Copy processing is in progress in either the forward or
backward direction.
• sync
The copy pair is in the synchronized (Pair) status.
#1
Email Parameter Mail Server Set the host name of the mail server, using from 1 to 500 Mandatory
characters.
#2
To Set the email notification recipient (email address) , using Mandatory
from 3 to 320 characters.
#1
Subject Set the email subject header , using from 0 to 255 Optional
characters. This allows the user to change the email
subject as required, where the default subject header is HP
StorageWorks XP Replication Monitor Alert.
The email subject that is actually sent includes the
configuration name, and is displayed in the following
format:
email-subject (configuration-name)
#3
Message Set the email body text , using from 0 to 500 characters. Optional
Email Check Specify whether to use SMTP authentication for the email Optional
Authentication Authentication notification.
Do Not Authenticate (No Check) is selected by default.
When Authenticate (Check) is selected, user name and
password settings for SMTP authentication are required.
User Name When Check Authentication is selected, specify the user Optional
#4
name for SMTP authentication, using from 1 to 64
characters.
Password When Check Authentication is selected, specify the Optional
#4
password for SMTP authentication, using from 0 to 64
characters.
Number of Notifications Specify the number of times that email notifications are to Mandatory
be transmitted when the monitoring target satisfies the
same check conditions. Specify Everytime, or a value from
1 to 99. The default value is 3.
For details on this item, see section 4-4-1-4 .
#1
The following characters can be entered:
Single-byte spaces A-Z a-z 0-9 ` ~ ! " # $ % & ' ( ) * + , - . / : ; < = > ? @ [ \ ]
^ _ { | }
However, an entry that consists only of single-byte spaces cannot be accepted. Also, single-byte spaces
that precede or follow a character string are not registered.
#2
Only email addresses that comply with RFC2821 can be specified. Additionally, the email addresses must
comply with RFC822 for Replication Monitor to be able to transmit them.
The following alphanumeric characters and symbols can be entered:
Operation 95
A-Z a-z 0-9 ` ~ ! # $ % & ' * + - . / = ? @ ^ _ { | }
#3
The following alphanumeric characters and symbols can be entered.
Single-byte spaces carriage returns A-Z a-z 0-9 ` ~ ! " # $ % & ' ( ) * + , - . / : ; <
= > ? @ [ \ ] ^ _ { | }
A carriage return is counted as two characters.
#4
The following alphanumeric characters and symbols can be entered.
A-Z a-z 0-9 ! # $ % & ' ( ) * + , - . = @ \ ^ _ |
NOTE: A maximum of 100 monitoring configurations can be set.
• When either a host, subsystem, or copy group is specified as the monitoring target, the email notification
is transmitted each time the conditions are met by at least one copy pair belonging to the monitoring
target.
• If an email notification is not transmitted despite the conditions being met, check the trace log file and
carry out the countermeasures indicated by the output message. For details on the trace log file, see
section 5-1-1 .
• Email messages will be transmitted without using SMTP authentication even if the use of SMTP
authentication is specified when the mail server in use does not support it. If you are planning on
performing email transmissions, check the specifications of the mail server before setting the
monitoring configuration.
4-4-1 Considerations before Setting Monitoring Configurations

This subsection explains the necessary considerations before setting monitoring configurations.
4-4-1-1 Setting the Configuration Name

The configuration name must be unique in the Replication Monitor system. If the configuration name conflicts
with an existing configuration name, the configuration name cannot be registered.
4-4-1-2 Setting Check Conditions

Replication Monitor detects four statuses: error, suspend, copying, and sync. For example, if only
suspend is specified for Check Conditions, then no email notification is transmitted when the monitoring-target
copy pair is in error status, since Replication Monitor determines that the check conditions are not satisfied in
such a case. Thus, when an email notification is required for both the suspend and error statuses, both
suspend and error must be specified for Check Conditions.
4-4-1-3 Setting the Email Parameters

It is recommended that you set the email recipients as follows, depending on the monitoring target.
• When the monitoring target is a host:
Address the email to the system manager who is responsible for managing the host
• When the monitoring target is a subsystem:
Address the email to the storage manager who is responsible for managing the storage subsystem
• When a copy pair requires specialized monitoring for certain operations:
Address the email to the manager who is responsible for the operations
Also, it is recommended that you set the email subject and text to describe the status of the monitoring target in
as much detail as possible. In addition to identifying the status, when specifying the error status for Check
Conditions, it is helpful to include information to identify the monitoring target, so that it will be easier to identify
the location of the error.
4-4-1-4 Setting the Number of Notifications

Replication Monitor periodically checks whether the conditions are satisfied, at intervals specified by the user.
The timing of this check is defined as the monitoring point. The Number of Notifications specifies how the email
notification should be transmitted when the monitoring target continues to satisfy the same conditions at
Operation 96
successive monitoring points. When Everytime is specified, notifications are transmitted for each time the
conditions are satisfied. However, when a number is specified, notifications are discontinued once the specified
number of notifications have been transmitted. The difference between Everytime and a specified number is
illustrated in the following figure:
Figure 4-25 Difference Between Everytime and a Specified Number

The following figure illustrates how the number of notifications is counted when specified. When the conditions
are satisfied at successive monitoring points, Replication Monitor increments the counter, and the counter is
reset to 0 when the check conditions are not met.
Figure 4-26 Counting Method When the Number of Notifications is Specified

Replication Monitor checks whether the conditions are satisfied only at the monitoring points. Thus, as shown A
in Figure 4-26, if the conditions are satisfied at the monitoring point 2, but then the status changes such that the
conditions are not satisfied, and then at monitoring point 3 the status changes again to satisfy the conditions,
this does not cause a counter reset. In such cases, it is thus possible that email notifications are not transmitted
despite that intention when setting the number of notifications.
Initially it is recommended that you set the number of notifications to a minimum of 3 or consider the following
in determining the number of notifications to set.
Number of notifications = (t / T) × n + 1
t: The estimated maximum period needed to confirm the content of the email notification and recover the
copy pair to the normal status.
T: The parameter values set for Retrieve Information (Interval) or Refresh Information (Interval). The
monitoring point is determined by the parameter values of Retrieve Information and Refresh Information.
For details on Retrieve Information and Refresh Information, see section 3-1-2-1 .
n: The number of iterations to determine if the status of the copy pair is normal.
When Everytime is specified for Number of Notifications, notifications will be issued indefinitely (at each
monitoring point) for as long as the check is satisfied.
Operation 97
4-4-2 Adding, Editing and Deleting Monitoring Configurations
This subsection explains the steps for adding, editing and deleting monitoring configurations.
4-4-2-1 Adding Monitoring Configurations

The Add Monitoring Configuration dialog box is used to set a new monitoring configuration. The procedure
leading up to opening the Add Monitoring Configuration dialog box differs depending on the monitoring target.
• Host, subsystem or a copy group
• Copy pair
The following explains each procedure.
4-4-2-1-1Setting monitoring configurations for a host, subsystem, or a copy group

1. Select the monitoring-target host-name, subsystem-name, or copy-group-name node from the navigation
frame.
The method frame displays a list of methods that can be executed for the node selected from the
navigation frame.
2. Select the Set Monitoring Configurations method.
The Set Monitoring Configurations subwindow is displayed in the information frame. The Set Monitoring
Configurations subwindow displays a list of monitoring configurations that are already set, if there are
any.
Figure 4-27 Example of the Set Monitoring Configurations Subwindow

3. Click the Add button.
The Add Monitoring Configuration dialog box is displayed.
Operation 98
Figure 4-28 Example of the Add Monitoring Configuration Dialog Box
4. Specify Configuration Name, Check Conditions, Email Parameter, Email Authentication, and Number of
Notifications, and click the OK button.
The Add Monitoring Configuration - Confirmation dialog box is displayed, and prompts the user to confirm
the entries, and that the configuration is to be added.
Figure 4-29 Example of the Add Monitoring Configuration - Confirmation Dialog Box (Without SMTP
Authentication)
If SMTP Authentication is selected in Email Authentication then the User Name and Password for
SMTP authentication cannot be omitted.
Click the Cancel button to cancel the setting of a monitoring configuration. The Add Monitoring
Configuration dialog box closes.
5. Click the OK button if the displayed contents are correct. Click the Back button to modify the monitoring
configuration. Click the Cancel button to cancel the setting of a monitoring configuration.
When you click the OK button, the Add Monitoring Configuration - Confirmation dialog box closes, and the
set (added) monitoring configuration is displayed in the Set Monitoring Configurations subwindow under
Operation 99
If you click the Back button, the display returns to the Add Monitoring Configuration dialog box, which
displays each item as it was immediately after step 4.
If you click the Cancel button, the Add Monitoring Configuration dialog box closes.
When setting multiple monitoring configurations with various conditions on the same node, repeat
steps 3 through 5.
4-4-2-1-2Setting monitoring configurations for a copy pair

1. Select the monitoring-target Port/HSD/LUN or LDEV LDEV-number node from the navigation frame.
The List Objects method, which is one of the executable methods for the node selected from the
navigation frame, is automatically executed, and information about the selected Port/HSD/LUN or LDEV
LDEV-number is displayed in the List Objects subwindow under the information frame.
There is an Action column in the object table which is included in the displayed information.
Figure 4-30 Example of List Objects Subwindow

2. Select a copy pair to be monitored from the object table and click the Monitor button in the Action column.
The information frame display changes to the Set Monitoring Configurations subwindow. For details on
the Set Monitoring Configurations subwindow, see Figure 4-27.
The Set Monitoring Configurations subwindow displays a list of monitoring configurations which are
already set, if there are any.
When you click the Show Detailed List button on the object table, the List Objects (Detailed)
subwindow is displayed. Step 2 and the operations thereafter can also be performed if you click the
Monitor button in the Action column in the object table.
3. Click the Add button.
The Add Monitoring Configuration dialog box is displayed. For details on the Add Monitoring
Configuration dialog box, see Figure 4-28.
4. Specify Configuration Name, Check Conditions, Email Parameter, Email Authentication, and Number of
Notifications, and then click the OK button.
Operation 100
The Add Monitoring Configuration - Confirmation dialog box is displayed and prompts the user to confirm
the entries, and that the condition is to be added. For details on the Add Monitoring Configuration -
Confirmation dialog box, see Figure 4-29.
If SMTP Authentication is selected in Email Authentication, then the User Name and Password for
SMTP authentication cannot be omitted.
Click the Cancel button to cancel the setting of a monitoring configuration. The Add Monitoring
5. Click the OK button if the displayed contents are correct. Click the Back button to modify the monitoring
configuration. Click the Cancel button to cancel the setting of a monitoring configuration.
When you click the OK button, the Add Monitoring Configuration - Confirmation dialog box closes and the
set (added) monitoring configuration is displayed in the Set Monitoring Configurations subwindow under
If you click the Back button, the display returns to the Add Monitoring Configuration dialog box, which
If you click the Cancel button, the Add Monitoring Configuration dialog box closes.
When setting multiple monitoring configurations with various conditions on the same node, repeat
steps 3 through 5.
4-4-2-2 Editing Monitoring Configurations

The Edit Monitoring Configuration dialog box is used to change monitoring configurations that are already set.
The procedure leading up to opening the Edit Monitoring Configuration dialog box differs depending on the
monitoring target.
• Host, subsystem or a copy group
• Copy pair
4-4-2-2-1Editing monitoring configurations for a host, subsystem, or a copy group

1. Select a host-name, subsystem-name, or copy-group-name node from the navigation frame to edit its
monitoring configurations.
The method frame displays a list of methods which can be executed for the node selected from the
navigation frame.
The Set Monitoring Configurations subwindow displays a list of set monitoring configurations. For details
on the Set Monitoring Configurations subwindow, see Figure 4-27.
3. Select a monitoring configuration to edit and click the Edit button in the Edit Configuration column.
The Edit Monitoring Configuration dialog box displays the selected monitoring configuration settings.
Operation 101
Figure 4-31 Example of the Edit Monitoring Configuration Dialog Box
4. Edit the required items and click the OK button.
The Edit Monitoring Configuration - Confirmation dialog box is displayed and prompts the user to confirm
the edited monitoring configuration settings, and that the configuration is to be updated.
If the Configuration Name is changed to a name that differs from the original Configuration Name, a
new monitoring configuration is added as the end result.
Click the Cancel button to cancel the editing of a monitoring configuration. The Edit Monitoring
Figure 4-32 Example of the Edit Monitoring Configuration - Confirmation Dialog Box
5. Click the OK button if the displayed contents are correct. Click the Back button to further modify the
monitoring configuration. Click the Cancel button to cancel the editing of a monitoring configuration.
Operation 102
When you click the OK button, the Edit Monitoring Configuration - Confirmation dialog box closes and the
edited monitoring configuration is displayed in the Set Monitoring Configurations subwindow under the
information frame.
If you click the Back button, the display returns to the Edit Monitoring Configuration dialog box, which
If you click the Cancel button, the Edit Monitoring Configuration dialog box closes.
When editing multiple monitoring configurations on the same node, repeat steps 3 through 5.
4-4-2-2-2Editing monitoring configurations for a copy pair

1. Select a Port/HSD/LUN or LDEV LDEV-number node from the navigation frame to edit its monitoring
configurations.
LDEV-number node is displayed in the List Objects subwindow under the information frame.
There is an Action column in the object table which is included in the displayed information. For details on
the List Objects subwindow, see Figure 4-30.
2. Select a copy pair whose monitoring configurations are to be edited from the object table and click the
Monitor button in the Action column.
The display in the information frame changes to the Set Monitoring Configurations subwindow and
displays a list of set monitoring configurations. For details on the Set Monitoring Configurations
subwindow, see Figure 4-27.
When you click the Show Detailed List button in the object table, the List Objects (Detailed)
subwindow is displayed. Step 2 and the operations thereafter can also be performed if you click the
Monitor button in the Action column in the object table.
3. Select a monitoring configuration to edit and click the Edit button in the Edit Configuration column.
The Edit Monitoring Configuration dialog box displays the selected monitoring configuration details. For
details on the Edit Monitoring Configuration dialog box, see Figure 4-31.
4. Edit the required items and click the OK button.
The Edit Monitoring Configuration - Confirmation dialog box is displayed and prompts the user to confirm
the edited monitoring configuration details, and that the configuration is to be updated. For details on the
Edit Monitoring Configuration - Confirmation dialog box, see Figure 4-32.
If the Configuration Name is edited to a name that differs from the original Configuration Name, a new
monitoring configuration is added as the end result.
Click the Cancel button to cancel the editing of a monitoring configuration. The Edit Monitoring
5. Click the OK button if the displayed contents are correct. Click the Back button to further modify the
monitoring configuration. Click the Cancel button to cancel the editing of a monitoring configuration.
When you click the OK button, the Edit Monitoring Configuration - Confirmation dialog box closes and the
edited monitoring configuration is displayed in the Set Monitoring Configurations subwindow under the
information frame.
If you click the Back button, the display returns to the Edit Monitoring Configuration dialog box which
If you click the Cancel button, the Edit Monitoring Configuration dialog box closes.
When editing multiple monitoring configurations on the same node, repeat steps 3 through 5.
Operation 103
4-4-2-3 Deleting Monitoring Configurations
When deleting set monitoring configurations, the operation is performed from either the Set Monitoring
Configurations subwindow, or the Show Monitoring Configurations subwindow where a list of set monitoring
configurations are displayed.
The procedure leading up to opening the subwindows differs depending on the monitoring target to be deleted.
• Replication Monitor, Hosts, Subsystems or Pair Configurations node
• Host, subsystem, or a copy group
• Copy pair
4-4-2-3-1Deleting monitoring configurations for the Replication Monitor, Hosts,

Subsystems or Pair Configurations node
1. Select the Replication Monitor, Hosts, Subsystems or Pair Configurations node from the navigation frame.
navigation frame.
2. Select the Show Monitoring Configurations method.
The Show Monitoring Configurations subwindow in the information frame displays a list of set monitoring
configurations.
Figure 4-33 Example of Show Monitoring Configurations Subwindow

3. Select a monitoring configuration to be deleted from the Configuration Name column, and then click the
Delete button.
The Delete Monitoring Configuration - Confirmation dialog box is displayed, and prompts the user to
confirm the monitoring configuration details, and that the configuration is to be deleted.
Multiple monitoring configurations can be deleted at one time by selecting the check boxes for multiple
monitoring configurations and clicking the Delete button.
Operation 104
Figure 4-34 Example of Delete Monitoring Configuration - Confirmation Dialog Box
4. Click the OK button to delete the displayed monitoring configuration. Click the Cancel button to cancel the
deletion of a monitoring configuration.
When you click the OK button, the selected monitoring configuration is deleted, and the Show Monitoring
Configurations subwindow in the information frame then displays monitoring configurations after the
deletion.
If you click the Cancel button, the Delete Monitoring Configuration dialog box for determining whether to
perform deletion closes.
4-4-2-3-2Deleting monitoring configurations for a host, subsystem, or a copy group

1. Select a host-name, subsystem-name, or copy-group-name node from the navigation frame to delete its
navigation frame.
The Set Monitoring Configurations subwindow displays a list of set monitoring configurations. For details
on the Set Monitoring Configurations subwindow, see Figure 4-27.
Delete button.
confirm the monitoring configuration details and that the configuration is to be deleted. For details on the
Delete Monitoring Configuration - Confirmation dialog box, see Figure 4-34.
When you click the OK button, the selected monitoring configuration is deleted, and the Set Monitoring
deletion.
4-4-2-3-3Deleting monitoring configurations for a copy pair

1. Select a Port/HSD/LUN or LDEV LDEV-number node from the navigation frame to delete its monitoring
configurations.
LDEV-number is displayed in the List Objects subwindow under the information frame.
There is an Action column in the object table which is included in the displayed information. For details on
the List Objects subwindow, see Figure 4-30.
Operation 105
2. Select a copy pair whose monitoring configurations are to be deleted, and then click the Monitor button in
the Action column.
The display in the information frame changes to the Set Monitoring Configurations subwindow and
displays a list of set monitoring configurations. For details on the Set Monitoring Configurations
subwindow, see Figure 4-27.
When you click the Show Detailed List button, the List Objects (Detailed) subwindow is displayed.
Step 2 and the operations thereafter can also be performed if you click the Monitor button in the
Action column in the object table.
Delete button.
confirm the monitoring configuration details and that the configuration is to be deleted. For details on the
Delete Monitoring Configuration - Confirmation dialog box, see Figure 4-34.
When you click the OK button, the selected monitoring configuration is deleted, and the Set Monitoring
deletion.
4-5 Identifying an Error Location

Upon receiving an email notification from Replication Monitor, the manager logs in to Replication Monitor and
identifies the location using the view that best suits his/her own management perspective.
As was mentioned in chapter 1, Replication Monitor is equipped with the following three views, so that storage
managers and system managers can confirm or operate on copy pair statuses using a view that best suits their
roles:
• Hosts view
• Subsystems view
• Pair Configurations view
The following explains the basic operational procedure in the Hosts view in response to an email notification of
the monitoring configuration example shown.
Item Settings
Monitoring target Host
Check Conditions (which trigger an email notification) An error status
Email Recipient (email address) Host system manager
information
Email text (message) Reporting that a copy pair is in an error
status
Number of notifications 3
Email example:
Title: Replication Monitor Alert(Action1)

From:hrpmalerter
CONFIGURATION NAME: Action1

OBJECT TREE: Hosts
OBJECT ADDRESS: usscc.abc15.hds.com
CHECK CONDITIONS: error
MESSAGE: Error occurred.
Operation 106
To perform basic operations by using the Hosts view:
1. Select the Hosts node from the tree in the navigation frame.
A list of information about hosts which are monitoring targets of Replication Monitor is displayed. Use this
list to identify the host that is in an error status.
Skip this step when the host that is in an error status has already been identified by the contents of the
email.
2. From the hosts under the Hosts node in the tree in the navigation frame, select the host-name node of the
host, identified in step 1, that is in error status.
A list is displayed, consisting of the LUNs which are connected to the selected host and comprise pairs.
Use this list to identify the LUN that is in error status.
Skip this step when the LUN that is in an error status has already been identified by the contents of the
email.
3. From LUNs under the host-name node determined in step 1 in the tree in the navigation frame, select the
Port/HSD/LUN node, identified in step 2, that is in an error status.
A list is displayed, consisting of pairs#1 which are cascaded and associated with the selected LUN.
Use this list to check the following:
• The copy pair that is in an error status, and the Copy Type and the volume configuration of the copy
pair.
• Whether the copy pair that is in an error status is cascaded.
• If it is cascaded, the structure that it comprises.
If you click the Show Detailed List button, then the host name where the RAID Manager XP configuration
definition file of the copy pair is stored, the RAID Manager XP configuration definition file name, the copy
group name and the copy pair name are displayed.
4. If the copy pair is cascaded, select LDEV-number in either the Primary or Secondary column.
A list is displayed, consisting of the LUNs which are assigned to the LDEV included in the cascade.
Identify the hosts that are using the LDEV included in the cascade, and then check the location of the
mount points.
5. Confirm the information which can be obtained from different views such as the Pair Configurations view
as necessary, or perform detailed examinations by using the operation management software for storage
subsystems.
6. Based on the information from performing steps 1 to 5, analyze the significance and extent of the impact,
and then perform the necessary actions to recover from the error status. Also, notify concerned parties
such as the managers of the associated host and storage subsystem.
The copy pair status of the selected copy pair can be changed in the Change Pair Status dialog box,
which can be displayed by selecting a status (error, suspend, copying or sync) in the Copy
Status column in the list of LUNs which are assigned to the LDEV included in the cascade, as
described in step 4. For details on operations to change a copy pair status, see section 4-6 .
7. When the error status is resolved, notify all concerned parties and resume operation.
It is recommended that you manually refresh the display to confirm the latest status as necessary, when
recovering from an error status or before starting operation. Manual refreshing is performed by selecting
one of the four refresh methods displayed in the method frame. Please be aware that manual refreshing
may increase the load on Device Manager depending on the target range and frequency.
The following sections describe basic operations for each Replication Monitor view.
4-5-1 Confirming and Operating on a Pair Status Using the Hosts View
Status confirmation and operations in the Hosts view are performed by selecting a node, within the tree in the
navigation frame, under Hosts, which is the root node of the Hosts view.
The following shows an example of the Hosts view. This example is for selecting a host-name node under the
Hosts node.
Operation 107
Figure 4-35 Example of the Hosts view
The Hosts view allows the user to drill down to detailed information in the following order, thereby providing
overall information about the whole host, as well as detailed information if necessary.
1. A list of information about monitoring-target hosts
This is displayed in the information frame when the Hosts node, as the root node of the Hosts view, is
selected from the tree in the navigation frame.
Figure 4-36 Example of a List of Information on Monitoring-Target Hosts

This provides a list of monitoring-target hosts and the most significant pair status for copy pairs
associated with each host. The list contains names and IP addresses of monitoring-target hosts and copy
pair statuses (whether there are copy pairs with an error, suspend, copying, or sync status) on a
copy pair basis.
Operation 108
2. A list of LUNs which are connected to a host and comprise pairs
This is displayed in the information frame when a host-name node under the Hosts node is selected from
the tree in the navigation frame.
Figure 4-37 Example of a List of LUNs Which Are Connected to a Host and Comprise Pairs
This provides a list of LUNs associated with the selected host, and the most significant pair status for
copy pairs associated with each LUN. The list contains copy pair statuses (whether there are copy pairs
with an error, suspend, copying, or sync status) on a copy type basis, as well as assigned mount
points, names of the subsystems where the primary volumes reside, and capacities for the LUNs
associated with a specific host.
3. A list of copy pairs which are cascaded and associated with a LUN
This is displayed in the information frame when a Port/HSD/LUN node under the Hosts node is selected
from the tree in the navigation frame.
Figure 4-38 Example 1 of Copy Pairs Cascaded and Associated with a LUN
This list provides a list of copy pairs which are cascaded with the selected LUN, as well as their
configuration information and the status of each copy pair. The list provides information as to whether the
selected LUN comprises a cascade, and if so, the configuration information, as well as the status (error,
suspend, copying, or sync) of each copy pair on a copy type basis.
If you click the Show Detailed List button, the List Objects (Detailed) subwindow is displayed to show the
pair management server name where the RAID Manager XP configuration definition file on each copy
pair is stored, RAID Manager XP configuration definition file name, the copy group name and the copy
pair name.
Operation 109
In addition, the selected copy pair’s status can be changed (such as changing the suspend status to
sync status) using the Change Pair Status dialog box by selecting the status (error, suspend,
copying, or sync) displayed in the Copy Status column. For details on operations to change a copy pair
status, see section 4-6 .
Figure 4-39 Example 1 of a List of Copy Pairs Cascaded and Associated with a LUN (List Objects (Detailed)
Subwindow)
4. A list of LUNs that are assigned to the LDEV included in the cascade
This list is displayed in a popup when an LDEV-number is selected from either the Primary or Secondary
column in the object table in the information frame, through the operation in step 3.
Figure 4-40 Example 1 of a List of LUNs Assigned to an LDEV Included in a Cascade

This provides a list of LUNs assigned to the selected LDEV, and a list of associated mount points and
hosts. The list provides information about hosts and mount points that are using the LDEV that is included
in a cascade configuration.
4-5-2 Confirming and Operating on a Pair Status Using the Subsystems View
Status confirmation and operations in the Subsystems view are performed by selecting a node within the tree in
the navigation frame under Subsystems, which is the root node of the Subsystems view. The following shows
an example of the Subsystems view. This example is for selecting a Subsystems node.
Operation 110
Figure 4-41 Example of the Subsystems View
The Subsystems view allows the user to drill down to detailed information in the following order, thereby
providing overall information about the whole storage subsystem, as well as detailed information if
necessary.
1. A list of information about monitoring-target storage subsystems
This is displayed in the information frame when the Subsystems node, as the root node of the
Subsystems view, is selected from the tree in the navigation frame.
Figure 4-42 Example of a List of Information on Monitoring-Target Storage Subsystems

This provides a list of monitoring-target storage subsystems, and the most significant pair status for copy
pairs associated with each storage subsystem. The list contains names, IP address types, models,
available capacity, used capacity, and cache size of monitoring-target storage subsystems and copy pair
statuses (whether there are copy pairs with an error, suspend, copying, or sync status) on a copy
type basis.
2. A list of LUNs that comprise pairs which are stored in a storage subsystem
This is displayed in the information frame when a subsystem-name node under the Subsystems node is
selected, from the tree in the navigation frame.
Operation 111
Figure 4-43 Example of a List of LUNs Which Comprise Pairs and Are Stored in a Storage Subsystem
This provides a list of LUNs associated with the selected storage subsystem, and the most significant pair
status for copy pairs which have each LUN as either their P-VOL or S-VOL. The list contains copy pair
type basis, as well as assigned mount points, assigned host names, and capacities for LUNs associated
with a specific storage subsystem.
3. A list of copy pairs which are cascaded and associated with a LUN
This is displayed in the information frame when a Port/HSD/LUN node under the Subsystems node is
Figure 4-44 Example 2 of a List of Copy Pairs Which Are Cascaded and Associated with a LUN
This list provides a list of copy pairs which are cascaded with the selected LUN, and their configuration
information and the status of each copy pair. The list provides information as to whether the selected LUN
comprises a cascade, and if so, the configuration information, as well as the status (error, suspend,
copying, or sync) of each copy pair on a copy type basis.
pair management server name where the RAID Manager XP configuration definition for each copy pair is
stored, the RAID Manager XP configuration definition file name, the copy group name and the copy pair
name.
Operation 112
sync status) using the Change Pair Status dialog box, by selecting the status (error, suspend,
Figure 4-45 Example 2 of a List of Copy Pairs (List Objects (Detailed) Subwindow) Which Are Cascaded and
Associated with a LUN
Figure 4-46 Example 2 of a List of LUNs Which Are Assigned to the LDEV Included in the Cascade
in a cascade.
4-5-3 Confirming and Operating on a Pair Status Using the Pair Configurations
View
Status confirmation and operations in the Pair Configurations view are performed by selecting a node within the
tree in the navigation frame under Pair Configurations, which is the root node of the Pair Configurations view.
The following shows an example of the Pair Configurations view. This example is for selecting a pair-name
node under the Pair Configurations node.
Operation 113
Figure 4-47 Example of the Pair Configurations View
The Pair Configurations view allows the user to drill down to detailed information in the following order,
thereby providing overall information about the Pair Configurations node as a whole, as well as detailed
information if necessary.
1. A list of information about monitoring-target pair management servers
This is displayed in the information frame when the Pair Configurations node, as the root node of the Pair
Configurations view, is selected from the tree in the navigation frame.
Figure 4-48 Example of a List of Information on Monitoring-Target Pair Management Servers

This provides a list of monitoring-target pair management servers and the most significant pair status for
copy pairs associated with each pair management server. The list contains names and IP addresses of
monitoring-target pair management servers and copy pair statuses (whether there are copy pairs with an
error, suspend, copying, or sync status) on a copy type basis.
2. A list of RAID Manager XP configuration definition files which are managed by a pair management server
This is displayed in the information frame when a pair-management-server-name node under the Pair
Configurations node is selected from the tree in the navigation frame.
Operation 114
Figure 4-49 Example of a List of RAID Manager XP Configuration Definition Files Which Are Managed by a
Pair Management Server
This provides a list of RAID Manager XP configuration definition files associated with the selected pair
management server, and the most significant pair status for copy pairs associated with each configuration
definition file. The list contains file names and local UDP port numbers of RAID Manager XP configuration
definition files associated with a specific pair management server, and copy pair statuses (whether there
are copy pairs with an error, suspend, copying, or sync status) on a copy type basis.
3. A list of copy groups which are included in a RAID Manager XP configuration definition file
This is displayed in the information frame when a RAID Manager XP-configuration-definition-file-name
node under the Pair Configurations node is selected from the tree in the navigation frame.
Figure 4-50 Example of a List of Copy Groups Which Are Included in a RAID Manager XP Configuration
Definition File
This provides a list of copy groups associated with the selected RAID Manager XP configuration definition
file, and the most significant pair status for copy pairs associated with each copy group. The list contains
names of copy groups associated with a specific RAID Manager XP configuration file, and copy pair
type basis, as well as information (server name, IP address, and remote UDP port number) on the pair
management servers with which communications take place.
4. A list of copy pairs which are included in a copy group
This is displayed in the information frame when a copy-group-name node under the Pair Configurations
node is selected from the tree in the navigation frame.
Operation 115
Figure 4-51 List of Copy Pairs Which Are Included in a Copy Group
This provides a list of copy pairs associated with the selected copy group, the status of each copy pair,
and LDEVs that comprise each copy pair. The list contains statuses (error, suspend, copying, or
sync) on a copy type basis, for copy pairs that are associated with a specific copy group, and the LDEVs
that comprise each copy pair.
5. A list of LDEVs which comprise pairs indicated by a copy pair
This is displayed in the information frame when a pair-name node under the Pair Configurations node is
Figure 4-52 Example of a List of LDEVs Which Comprise Pairs Indicated by a Copy Pair
This provides a list of LDEVs associated with the selected copy pair, the detailed information about each
LDEV (LDEV number, capacity, RAID level, emulation type, subsystem name, and volume attribute).
6. A list of cascaded copy pairs which are associated with an LDEV
This is displayed in the information frame when a LDEV LDEV-number node under the Pair
Configurations node is selected from the tree in the navigation frame.
Operation 116
Figure 4-53 Example of a List of Cascaded Copy Pairs Associated with an LDEV
This list provides a list of cascaded copy pairs which include the selected LDEV, and their configuration
information and the status of each copy pair. The list provides information as to whether the selected
LDEV comprises a cascade, and if so, the configuration information, as well as the status (error,
suspend, copying, or sync) of each copy pair on a copy type basis.
pair management server name where the RAID Manager XP configuration definition for each copy pair is
stored, the RAID Manager XP configuration definition file name, the copy group name and the copy pair
name.
sync status) using the Change Pair Status dialog box, by selecting the status (error, suspend,
Figure 4-54 Example of a List of Cascaded Copy Pairs (List Objects (Detailed) Subwindow) Which Are
Associated with an LDEV
Operation 117
Figure 4-55 Example 3 of a List of LUNs Which Are Assigned to an LDEV Included in a Cascade
in a cascade configuration.
4-6 Changing a Pair Status

Replication Monitor allows the user to change a pair status for copy groups or copy pairs. However, the pair
status cannot be changed in the following cases:
• When the copy type is Continuous Access XP Journal
• When the storage subsystem is StorageWorks XP12000 and the copy type is Snapshot XP
• When there are restrictions due to the system configuration
4-6-1 Changing a Status

The following tables show executable operations when changing a status according to the current pair status
and copy type:
Table 4-19 When the Target Is a Copy Group
Copy type
#1
Current pair status Business Copy Continuous Continuous Snapshot XP
Access XP Access XP
Extension
copying (Copying) split split split Split
copying (Reverse-Copying) split (Not (Not applicable) Split
applicable)
sync (Pair) split split split Split
#2
suspend (Split) resync, restore resync resync resync, restore
#2
error (Suspended) resync, restore resync resync resync, restore
error (Error In LUSE) (Not applicable) resync resync (Not applicable)
error (Deleting or Suspending) (Not applicable) (Not (Not applicable) (Not applicable)
applicable)
Legend:
split: A pair can be split.
resync: A pair can be resynchronized.
restore: A pair can be restored (resynchronization from the secondary to the primary).
The Web Client subwindow and dialog box display the executable operations only.
NOTE: The pair status cannot be changed when the copy group contains copy pairs with different copy
types.
Operation 118
NOTE: If even one copy pair with the Suspended or Error In LUSE status exists in the group, the status
of the whole group is assumed to be Suspended. The executable operations for each pair are added to the
executable operations for the group.
#1
The description enclosed in parenthesis indicates the pair status in Device Manager. The Device
Manager pair status can be confirmed in the List Objects (Detailed) subwindow, displayed by individually
selecting all the LDEV LDEV-number nodes that make up the copy group and then clicking the Show
Detailed List button.
#2
The description enclosed in parenthesis indicates the pair status in Device Manager. If a copy pair that
has the same primary volume in the group exists, the executable operation is resync only.
Table 4-20 When the Target Is a Copy Pair
Copy type
#
Current pair status Business Copy Continuous Continuous Snapshot XP
Access XP Access XP
Extension
copying (Copying) split split split split
copying (Reverse-Copying) split (Not (Not applicable) split
applicable)
sync (Pair) split split split split
suspend (Split) resync, restore resync resync resync, restore
error (Suspended) resync, restore resync resync resync, restore
error (Error In LUSE) (Not applicable) resync resync (Not applicable)
error (Deleting or Suspending) (Not applicable) (Not (Not applicable) (Not applicable)
applicable)
Legend:
split: A pair can be split.
resync: A pair can be resynchronized.
restore: A pair can be restored (resynchronization from the secondary volume to the primary volume).
The Web Client subwindow and dialog box display the executable operations only.
#
The description enclosed in parenthesis indicates the pair status in Device Manager. The Device
Manager pair status can be confirmed in the Detailed Copy Status column in the List Objects (Detailed)
subwindow.
When the copy type is Continuous Access XP Extension, the copy operation is performed on a
consistency group basis.
NOTE: Some operations are not executable according to the configuration or status of a copy pair,
regardless of whether the target is a group or pair. After checking the following, see the manuals for storage
subsystems such as Continuous Access XP, Business Copy, Snapshot XP, so that you can check that the
intended operation is available.
• Current pair status

• Configurations, such as a cascade configuration
• Statuses of copy pairs that comprise a copy group
4-6-2 Changing the Copy Pace

The copy pace indicates the number of tracks copied by one operation. The copy pace can be changed when
changing a pair status, however, the selectable copy paces vary depending on the copy type, operation type,
and storage subsystem model as follows:
Operation 119
Table 4-21 Selectable Copy Paces
Copy type Operation types Storage subsystem models Selectable copy paces
Business Copy split, resync, StorageWorks XP1024/XP128 Select from slow speed
restore or StorageWorks XP12000 (Slower), medium speed
(Medium), or high speed
(Faster).
The default value is medium
speed (Medium).
Snapshot XP split, resync (Any) A copy pace cannot be

specified.
restore Specify a value from 1 to 15.
The default value is 15.
Continuous Access (Any) (Any) A copy pace cannot be
XP Journal specified.
Continuous Access split (Any) A copy pace cannot be
XP or Continuous specified.
Access XP
Extension
resync Specify a value from 1 to 15.
The default value is 15.
Legend:
(Any): Any operation or model is applicable.
Selecting a larger value (Faster or 15) for the copy pace reduces the copy duration, but might also affect I/Os
for the storage subsystem.
4-6-3 Pair Status Changing Procedure

This subsection explains the procedure for changing a pair status.
4-6-3-1 When Changing the Pair Status of a Copy Group

1. Select a copy-group-name node under the Pair Configurations node, from the tree in the navigation
frame.
2. Select the Change Pair Status method from the method frame.
The Change Pair Status - Step 1 of 2 dialog box is displayed.
If the copy pairs subject to the operation meet either of the following conditions, a message appears
indicating that the pair status change operation is not supported. In this case, to change the pair
status, use other software (such as Remote Web Console) that can perform the operation on the
copy pairs.
- When the copy type is Continuous Access XP Journal.
- When the storage subsystem is StorageWorks XP subsystem and the copy type is Snapshot XP.
Operation 120
Figure 4-56 Example 1 of the Change Pair Status - Step 1 of 2 Dialog Box
3. Select an operation to execute (resync, restore, or split) from Operation, specify Copy Pace, and then
click the Next button.
If you click the Cancel button, the dialog box closes and the processing is canceled.
Whether Operation is selectable depends on the copy type of the target pair, the pair status at the
time of the operation, and the model of the storage subsystem. Also, whether Copy Pace is
specifiable depends on the copy type of the target pair, the operation type to be executed, and the
model of the storage subsystem. For details, see section 4-6-1 and 4-6-2 .
If the operating target and conditions at the time of the operation are identical, the most recent Copy
Pace is displayed as the default.
Operation 121
4. Click the Execute button if the displayed items are correct.
A dialog box is displayed to indicate that the change processing is in progress, followed by a dialog box to
indicate the completion of the processing.
If you click the Back button, the display returns to the Change Pair Status - Step 1 of 2 dialog box.
5. Click the Close button. The dialog box indicating completion of the processing closes.
4-6-3-2 When Changing the Pair Status of a Copy Pair
When operating on a copy pair, the procedure is different for the following two cases:
• Using the Change Pair Status method
• Using a status (error, suspend, copying or sync) anchor displayed in the Copy Status column in the
object table
4-6-3-2-1Using the Change Pair Status method
To change the pair status of a copy pair by using the Change Pair Status method:
1. Select a pair-name node under the Pair Configurations node, from the tree in the navigation frame.
2. Select the Change Pair Status method from the method frame.
If the copy pair subject to this operation meets either of the following conditions, a message appears
indicating that the pair status change operation is not supported. In this case, to change the pair
status, use other software (such as Remote Web Console) that can perform the operation on the
copy pair.
- When the storage subsystem is StorageWorks XP12000 and the copy type is Snapshot XP.
Operation 122
selectable depends on the copy type of the target pair, the operation type to be executed, and the
model of the storage subsystem. For details, see section 4-6-1 and 4-6-2
Operation 123
indicate the completion of the processing.
5. Click the Close button.
The dialog box indicating completion of the processing closes.
4-6-3-2-2When using a status (error, suspend, copying or sync) anchor displayed in the
Copy Status column in the object table
To change the pair status of a copy pair by using a status anchor:
1. Select a Port/HSD/LUN node under the Hosts or Subsystems node, or an LDEV LDEV-number node or a
copy-group-name node under Pair configurations, from the tree in the navigation frame.
2. Select a copy pair for which to change the pair status, from among the copy pairs displayed in the
information frame, and left-click the status (error, suspend, copying or sync) anchor in the Copy Status
column.
The pair status cannot be changed in the following cases, so the status (error, suspend, copying,
or sync) anchor in the copy pair status column cannot be clicked.
- When the storage subsystem is StorageWorks XP12000 and the copy type is Snapshot XP
- When there are restrictions due to the system configuration
Operation 124
selectable depends on the copy type of the target pair, the operation type to be executed, and the
model of the storage subsystem. For details, see section 4-6-1 and 4-6-2 .
When an anchor is right-clicked in step 2, executable operations (resync, restore or split) for the
selected copy pair are displayed as a popup window. When an operation is selected from the menu,
the Change Pair Status - Step 2 of 2 dialog box is displayed. However, in this case the Copy Pace
displayed for the first operation is the default value. If the operating target and the conditions at the
time of the operation are identical, from the second Copy Pace onwards, the most recent value is
used as the default.
indicate completion of the processing.
5. Click the Close button.
The dialog box indicating completion of the processing closes.
4-6-4 Notes on Changing a Pair Status

• When the copy type is Continuous Access XP Extenion, the copy operation is performed in consistency
group units. However, the consistency group (copy group) units cannot be selected for nodes under the
Hosts node or Subsystems node. Thus, when the copy type is Continuous Access XP Extension, the
Change Pair Status dialog box for consistency group units is displayed even if a copy pair is selected. In
this case, a message is displayed to notify you that the copy pair operation can only be performed in
consistency group units.
• When change processing for the pair status is completed, the result is not displayed in the information
frame. To confirm that the pair status has been successfully changed, you must either manually refresh
the display, or wait for the display to be refreshed automatically. Update the information by manually
refreshing the display as necessary. However, manual refreshing might increase the load on Device
Manager, depending on the target range and frequency.
4-7 Calling Device Manager

This section explains how to start up Device Manager to call the Web Client of Device Manager from
Replication Monitor. When the Web Client of Device Manager is called, Device Manager operations can be
performed, such as creating a new copy pair or changing copy pair settings.
To call the Web Client of Device Manager:
1. Click Tools on the menu-bar frame. The Tools window is displayed.
Replication Monitor should be installed on the same server as Device Manager. The Tools window
should display HP StorageWorks XP Replication Monitor and Command View XP AE Device
Manager as Command View XP AE Suite software. Other Command View XP AE Suite software may
be displayed if they are installed on the same server.
2. Select Command View XP AE Device Manager from the displayed Command View XP AE Suite
software. The Main window of Device Manager is displayed in a separate window.
There is no need to enter the user ID and password, since the user ID and password used to log in to
Replication Monitor are passed on.
3. Start operating Device Manager. For details on operations on Device Manager, see the manual HP
StorageWorks XP Advanced Edition Device Manager Web Client User Guide.
Operation 125
A Replication Monitor user possesses System Administrator permissions or Storage Administrator
permissions for Device Manager. Thus, operations on Device Manager can be performed within these
held permissions.
4-8 Registering and Viewing License Information

This section explains how to view licence information registered in Replication Monitor, and how to register the
license key.
4-8-1 License Key

To use Replication Monitor, license information must be registered as a license key. License information is
registered by specifying a license key, or a license file which contains multiple license keys, from Replication
Monitor’s Web Client. The following license key types exist:
License Type: Permanent
A permanent license key allows permanent use of the relevant Replication Monitor product. This key is
provided per management-target storage subsystem.
License Type: Temporary
A temporary license key allows temporary use of the relevant Replication Monitor product. This key is
provided per system.
License Type: Emergency
An emergency license key allows temporary use of the relevant Replication Monitor product in an
emergency situation. This key is provided per system. If an emergency key is added in an environment
where a permanent key is already registered, the emergency key information will take precedence.
4-8-2 Registering and Viewing License Information

The license key must be registered when logging in from Web Client for the first time after Replication Monitor
is installed. The license information can be viewed, and license keys can be added or updated as necessary
during Replication Monitor operation.
To register or view license information:
1. Click the License button in the Replication Monitor Login window, or click About in the menu-bar frame in
the Replication Monitor Main window.
License information registered in Replication Monitor is displayed in the Version Information dialog box.
When license information is not registered, the License Type is displayed as Unregistered.
2. To register license information, select either License Key or License File and specify the license key or
license file to be registered.
Click the Browse button to specify the license file location.
3. Click the Save button to register license information.
Click the Close button to close the window without registering license information.
Operation 126
Figure 4-60 Version Information Dialog Box
4-9 Replication Monitor Security Management

This section explains security management for Replication Monitor.
4-9-1 Necessary User Permissions for Login

Replication Monitor Web Client is equipped with a security management function by means of user
authentication in the Login window.
Replication Monitor shares user accounts with Device Manager because they are both installed on the same
management server. To operate Replication Monitor, a user registered to Device Manager must be granted
one of the following sets of user permissions:
• System Administrator
• Storage Administrator
For details on user management operations on Device Manager, see the manual HP StorageWorks XP
Advanced Edition Device Manager Web Client User Guide.
4-9-2 Inheriting User Permissions in Link-and-Launch Operations

Replication Monitor Web Client provides the link-and-launch function, which allows the user to call Web Clients
from different Command View XP AE Suite software.
During link-and-launch operations, the user authentication information is inherited by the single sign-on function
provided by Common Component. Thus, once logged in to Command View XP AE Suite software that uses
Common Component, such as Device Manager, there is no need to re-enter a user ID and password when
performing link-and-launch operations.
When a user who is logging in to another Command View XP AE Suite software calls Replication Monitor by
using link-and-launch operations, the user permissions described in section 4-9-1 are required.
Operation 127
4-9-3 Access Security for the Device Manager Server
Replication Monitor obtains information about storage subsystems, and issues instructions for operations to
change copy pair statuses via the Device Manager server installed on the same management server. Even
when no user is logged in by using Web Client, Replication Monitor automatically accesses the Device
Manager server to automatically refresh information and monitor copy pairs.
Security management is also applied for such accesses from Replication Monitor to the Device Manager
server, using user authentication based upon the user permissions described in section 4-9-1 .
The user account information (user name and password) used by Replication Monitor to access the Device
Manager server is configured by the user during installation of Replication Monitor. If necessary, this user
account can be changed after operation has commenced, by using a Replication Monitor environment setup
command (hrpmsetup). For details on usage of environment setup commands, see section 3-4 .
4-9-4 Network Access Security

Network accesses between a management client (Web browser) and Replication Monitor on the management
server can be encrypted, by configuring SSL in HiCommand Suite Common Web Service. HiCommand Suite
Common Web Service is a function provided by Common Component.
For details on security procedures using HiCommand Suite Common Web Service, see the manual HP
StorageWorks Command View XP Advanced Edition Device Manager Server Installation and Configuration
Guide.
4-10 Notes on Operating the Refresh Function

Replication Monitor obtains information to display in Web Client from the following three resources:
• Information that Replication Monitor holds in a database
• Information that Device Manager holds in a database
• Information about the actual status of volumes in the storage subsystem device
Replication Monitor and Device Manager are equipped with a function to periodically update the above
information.
The refresh function of Device Manager updates the information in the Device Manager database based on
volume status or configuration information in the connected storage subsystem device. The duration of this
operation for a storage subsystem depends on the subsystem model type, and the number of LDEVs in the
subsystem. The refresh may take a few minutes or a long time (tens of minutes) per storage subsystem device.
The refresh function of Replication Monitor first updates the information kept in the Device Manager database
based on volume status or configuration information in all of the monitored storage subsystem devices. Then, it
updates the information in the Replication Monitor database based on the updated information on Device
Manager. It may take several minutes to update the information in the Replication Monitor database based on
the information in Device Manager. Thus, the refresh function of Replication Monitor might require a large
workload for several tens of minutes, on the management server and the machine where the Device Manager
agent is running.
Replication Monitor has a function (Retrieve) to only update information in the Replication Monitor database
based on information on Device Manager when an automatic refresh is executed.
When operating Replication Monitor, specify settings for automatic refresh (Refresh Information) and automatic
retrieve (Retrieve Information) taking the above into consideration. It is recommended that you use either of the
following settings. For details on settings for Refresh Information and Retrieve Information, see section 3-1-2-
1.
• For automatic refresh (Refresh) of Replication Monitor, specify a time period when the machine usage
rate is low.
• Use only the refresh function of Device Manager to update information in Device Manager, and specify
only automatic refresh (Retrieve) for Replication Monitor.
You can set Retrieve Information and Refresh Information concurrently. By setting the parameter value as
shown below, you can refresh information in the Device Manager server while preventing an increase in the
Device Manager workload caused by requests from Replication Monitor.
Retrieve Information (Interval) < Refresh Information (Interval)
Operation 128
When the information acquisition time and refresh time overlap when Retrieve Information and Refresh
Information are set concurrently, the request for refreshing information has priority and no request to acquire
information is made.
Operation 129
5 Troubleshooting
This chapter describes countermeasures for errors that might occur during execution of Replication Monitor.
• 5.1 Error Countermeasures
5-1 Error Countermeasures

When an error occurs while executing Replication Monitor, the user should first confirm the operating status
and messages output at the time of the error. For countermeasures for each message, see 6 .
If you cannot resolve the error by referring to the messages, analyze the cause of the problem by collecting log
files produced by Replication Monitor. The following subsections describe the types of log files, and log
collection methods using the maintenance information batch collection command.
For details on errors that might occur during installation or uninstallation, see 2 .
5-1-1 Log File Output from Replication Monitor

An output level, which corresponds to the importance of a message, is specified for messages output to log
files. Replication Monitor outputs (to the log file) only those messages that have an output level equal to, or
more important than, the specified log output level and its output threshold. For details on output levels of log
files, see section 3-1-2-3 .
The following table describes the types of output log files.
Table 5-1 Types of Log Files Output from Replication Monitor
Type of log file Log file name Description Output directory

(Windows)
Integrated trace hntr2n.log Detailed information related to server system-drive:\
log files startup is output to these files. Program
Use this log to confirm error details Files\Hitachi\HNT
when an error occurs during Replication RLib2\spool
Monitor operation.
®
Event log file Eventlog The Windows event log Event Viewer
Trace log files HRpMTracen Detailed information indicating the Replication-
.log program processing status is output to Monitor-
these files. installation-
Use this log to track the flow of the folder\logs
program processing when a problem
occurs during a Replication Monitor
operation.
#
Installation HRpM_xxxxxx Log.l Results of each processing performed Replication-
related trace log og by the installer and uninstaller (various Monitor-
files checks, file copies, command installation-
executions) are recorded in this file. folder\logs
Use this log to analyze the cause of an For trace logs produced
error that occurred during installation or during an installation,
uninstallation. For details on processing see section 2-1-5-4 .
performed by the installer or uninstaller,
see 2 .
Version HRpMVersion Version information for Replication Replication-
information log Monitor Monitor-
files installation-
folder\logs
#
Either Install or Uninstall replaces xxxxxx. For details on log file names in Windows®, see section
2-1-5-4 .
5-1-2 Error Countermeasure Procedure

To deal with an error:
1. Check any messages and problem details.
2. When you cannot resolve the error by checking the messages, execute the maintenance information
batch collection command to obtain the integrated trace log file and trace log file.
For details on how to execute this command, see section 5-1-3 .
3. Check the problem details by examining the integrated trace log file.
4. Track the operations executed by Replication Monitor by examining the trace log file to analyze the
cause.
5. If the cause of the error cannot be established by analyzing the trace log file, request technical support for
analysis of all information collected by the maintenance information batch collection command.
The following files are collected by the maintenance information batch collection command:
• Integrated trace log file
• Trace log file
• Installation-related trace log file
• Version information log file
• Log information from execution of the Common Component commands
• Property file. The following property files are collected by the maintenance information batch collection
command. For details on property files, see 3 .
• database.properties
• logger.properties
• serverstorageif.properties
• installation.properties
• monitor.properties
• client.properties
5-1-3 Maintenance Information Batch Collection Command

The maintenance information batch collection command allows the user to collect all the information used for
troubleshooting.
5-1-3-1 Format
In Windows®:
cvxpaegetlogs /dir directory-name

/type Command-View-XP-AE-Suite-product-name
/arc archive-file-name
5-1-3-2 Description
The command collects all Replication Monitor maintenance information at one time. The maintenance
information is output together into an archive file. The command also collects all maintenance information of
every Command View XP AE Suite software installed on the same host.
5-1-3-3 Arguments
dir directory-name
Specify the directory name where the collected maintenance information is to be stored. There is no need
to create the specified directory. The specified directory is created automatically. If the specified directory
already exists, make sure that there are no subdirectories or files in the directory. If there are any
subdirectories or files in the specified directory, an error message will be produced and the maintenance
information collection processing will be cancelled.
Specify the name of the target product from which the maintenance information is to be collected, from
among the Command View XP AE Suite software. If this option is omitted, all Command View XP AE
Suite software installed on the management server are deemed to be the target.
When specifying Replication Monitor, specify ReplicationMonitor.
To examine the cause of the problem, you need the maintenance information in Replication Monitor and
Device Manager. Use the maintenance information batch collection command twice to collect the
maintenance information from Replication Monitor and Device Manager, or omit the type option to collect
Troubleshooting 131
the maintenance information from every Command View XP AE Suite software. Note, however, that
collecting the maintenance information from all the Command View XP AE Suite software might require a
large capacity for the files.
arc archive-file-name
Specify the name of the archive file to be created. The name of the archive file is generated with the
specified name and an extension of .jar.
If this option is omitted, the archive file name will be cvxpae_logs.jar.

1: Invalid argument
5-1-3-5 Notes
To execute this command, the following user must be logged in to the system:
• In Windows®:
Do not concurrently execute more than one maintenance information batch collection command.
The following lists notes on arguments:
• The following characters cannot be used for specifying arguments:
• In Windows:
\ / : , * ? " < > | $ % ' `
However, a backslash (\), forward slash (/), and colon (:) can be used as a delimiter. Note that a
delimiter cannot be specified at the end of a directory name.
• The following characters can be used when the entire argument is enclosed in quotation marks. Note that
you cannot enclose only part of an argument in quotation marks.
• In Windows (double quotation marks (") can be used):
; = , & and the space character
The escape character (\) can be used immediately before each character instead of enclosing the
entire argument in quotation marks.

In the following example, the command collects the maintenance information of Replication Monitor:
®
In Windows :
> cvxpaegetlogs /dir C:\logfile /type ReplicationMonitor

In the following example, the command collects all maintenance information of Command View XP AE Suite
software (the output archive file name is Hitachi_log):
In Windows®:
> cvxpaegetlogs /dir "C:\Program Files\CVXPAE\log" /arc Hitachi_log
Troubleshooting 132
6 Messages
This chapter lists and describes the messages generated during Replication Monitor operation and the
appropriate actions to take in response to those messages.
• 6.1 Message Types and Formats
• 6.2 KAVN00000 - KAVN00199
• 6.3 KAVN00200 - KAVN00399
• 6.4 KAVN00400 - KAVN00599
• 6.5 KAVN00600 - KAVN00799
• 6.6 KAVN01200 - KAVN01399
• 6.7 Detailed Messages
• 6.8 Action for Detailed Message RPM-00824
6-1 Message Types and Formats

The three types of message that can be generated during Replication Monitor operation are:
• Replication Monitor messages
• Detailed messages
• Other messages
6-1-1 Replication Monitor Messages

Replication Monitor messages are generated by Replication Monitor to notify the user of Replication Monitor
errors, warnings, and operating statuses.
Replication Monitor messages use the following format:
KAVNnnnnn-Z message-text
The message ID consists of the following components:
KAVN
Indicates a message generated by Replication Monitor.
nnnnn
The message sequence number.
Table 6-1 Replication Monitor Message Numbers and Corresponding Functions
Message number Description

00000 - 00199 Common messages
00200 - 00399 GUI messages
00400 - 00599 Server function messages
00600 - 00799 Monitoring function messages
00800 - 00999 Replication Monitor database messages
01000 - 01199 Storage subsystem interface messages
01200 - 01399 Installer messages
Z
Indicates the severity of the message.
The following table indicates the severity of the message.
Table 6-2 Message Types and Meanings
Message type Description

I (Information) Processing executed normally.
W (Warning) Processing will continue but with certain restrictions.
E (Error) Processing cannot continue due to an error.
6-1-2 Detailed Messages
Detailed messages provide additional information about Replication Monitor messages generated immediately
beforehand.
Detailed messages use the following format:
RPM-nnnnn message-text
RPM
Indicates a detailed message generated by Replication Monitor.
nnnnn
The message sequence number.
Table 6-3 Detailed Message Numbers and Corresponding Functions
Message number Description

00000 - 00199 Common messages
00200 - 00399 GUI messages
00400 - 00599 Server function messages
00600 - 00799 Monitoring function messages
00800 - 00999 Replication Monitor database messages
01000 - 01199 Storage subsystem interface messages
01200 - 01399 Installer messages
6-1-3 Other Messages

The following message IDs are used to indicate messages generated by Common Component (where nnnnn
is the message serial number, and Z is an alphabetic character that indicates the message type).
• KAPMnnnnn-Z
• KDJEnnnnn-Z
The following message IDs are used to indicate messages generated by HiRDB (where nnnn is the message
serial number, and Z is an alphabetic character that indicates the message type).
• KFPAnnnn-Z
• KFPCnnnn-Z
• KFPDnnnn-Z
• KFPHnnnn-Z
• KFPLnnnn-Z
• KFPOnnnn-Z
• KFPRnnnn-Z
• KFPSnnnn-Z
• KFPXnnnn-Z
The above messages are generated in the event of a problem in Common Component or the database. For
details, contact technical support.
6-1-4 Collecting Log Information for Installation and Uninstallation Errors

As the action for an error, some installer messages (KAVN01200 to KAVN01399) contain a directive to acquire
the following log information:
• Installation related trace log file
• Log information for Common Component command execution
The following gives an overview of log information and output destinations.
Installation related trace log file:
Records the results of installer and uninstaller processing (checking, file copying, command execution).
Installation related trace log files are stored in the following locations:
®
In Windows :
• Installation log information
Messages 134
system-drive\HRpM_InstallLog.log
• Uninstallation log information
system-drive\HRpM_UninstallLog.log
Log information for Common Component command execution:
Records the results of Command View XP AE Suite software command execution. Common Component
command execution log information is stored in the following locations:
®
In Windows :
All files in or below
Common-Component-installation-folder\log
To collect the information described above, use the maintenance information batch collection command
(cvxpaegetlogs). For details on this command, see section 5-1-3 .
6-2 KAVN00000 - KAVN00199

This section describes messages generated by Replication Monitor, from KAVN00000 to KAVN00199, and the
corresponding actions.
KAVN00001-I Replication Monitor has started. Cause

Replication Monitor has started
successfully.
Action
No action is required.
KAVN00002-I Replication Monitor has stopped. Cause
Replication Monitor has stopped
successfully.
Action
KAVN00003-E An error occurred while Replication Monitor was Cause
starting. Replication Monitor could not start. An error occurred while Replication
Monitor was starting.
Action
Follow the instructions in the
accompanying detailed messages,
and then restart Replication Monitor.
If this message still appears or a
detailed message is not output,
contact technical support.
KAVN00004-E An error occurred while Replication Monitor was Cause
stopping. An error occurred while Replication
Monitor was stopping.
Action
accompanying detailed messages,
and then remove the error cause.
If this message still appears or a
detailed message is not output,
KAVN00100-I Replication Monitor will now start. Cause
Replication Monitor startup
processing has started.
Action
KAVN00101-I Replication Monitor will now stop. Cause
Replication Monitor stop processing
has begun.
Action
Messages 135
KAVN00150-I Register the user name that the system uses to Cause
access the Device Manager Server. : The hrpmsetup command was
executed.
Action
Enter the Device Manager user name.
KAVN00151-I Register the password that the system uses to Cause
executed.
Action
Enter the Device Manager password.
KAVN00152-I Re-enter the registered password. : Cause
The hrpmsetup command was
executed.
Action
Re-enter the Device Manager
password.
KAVN00153-I Register the port number that the system uses to Cause
executed.
Action
Enter the Device Manager port
number.
KAVN00154-I Select the time interval (0, 0.5, 1, 6, 12, or 24) for Cause
acquiring information. : The hrpmsetup command was
executed.
Action
Select and enter a time interval (from
0, 0.5, 1, 6, 12, or 24) for acquiring
information. If 0 is specified,
information is not acquired.
KAVN00155-I Register the starting time for acquiring Cause
information. (HH:MM) : The hrpmsetup command was
executed.
Action
Enter the time to start acquiring
information, in HH:MM format. Enter a
hyphen (-) if a specific time is not
required.
KAVN00156-I Select the time interval (0, 0.5, 1, 6, 12, or 24) for Cause
refresh operations. : The hrpmsetup command was
executed.
Action
Select and enter a time interval (from
0, 0.5, 1, 6, 12, or 24) for refreshing
operations. If 0 is specified, refresh
operations are not performed.
KAVN00157-I Register the time to start the refresh operation. Cause
(HH:MM) : The hrpmsetup command was
executed.
Action
Enter the time to start the refresh
operations, in HH:MM format. Enter a
hyphen (-) if a specific time is not
required.
KAVN00158-I Parameter information was updated. Cause
The hrpmsetup command was
executed.
Action
Restart Replication Monitor to apply
the set parameters.
Messages 136
KAVN00159-W The entered contents are invalid. Cause
The user response to the hrpmsetup
command is invalid. Possible causes
are as follows:
• The user name or password does not
contain from 4 to 25 characters.
• The user response to the
KAVN00151-I message differed from
the user response to the KAVN00152-
I message (password).
• An invalid numeric value or symbol
has been entered.
Action
Revise the entered command
response as necessary.
KAVN00160-E An error occurred while accessing a database. Cause
An error occurred with the
hrpmsetup command while
accessing a database.
Action
To remedy the problem:
1 Terminate Common Component by
using the hcmdssrv command.
2 Start the database by using the
hcmdsdbsrv command.
3 Restart the Common Component by
using the hcmdssrv command.
KAVN00161-I Enter the Device Manager password currently Cause
stored in the database. : The hrpmsetup command was
executed.
Action
Enter the user account password that
was specified during execution of the
last hrpmsetup command or during
installation, and that is used by
Replication Monitor for accessing
Device Manager.
KAVN00162-E The password is incorrect. The command will Cause
now end. An incorrect password was entered
during execution of the hrpmsetup
command.
Action
Enter the user account password that
was specified during execution of the
last hrpmsetup command or during
installation, and that is used by
Replication Monitor for accessing
Device Manager.
KAVN00163-E The data in the Common Component database is Cause
invalid. The data in the Common Component
database is invalid.
Action
Use Replication Monitor Web Client to
execute a system-wide information
refresh (execute the Refresh All
method). If this message is displayed
even after the refresh, re-install
KAVN00165-I Collection of maintenance information from Cause
Replication Monitor will now start. Collection of maintenance information
using the cvxpaegetlogs command
has started.
Action
Messages 137
KAVN00166-I Collection of maintenance information from Cause
Replication Monitor has ended. Collection of maintenance information
using the cvxpaegetlogs command
has ended successfully.
Action
KAVN00167-E An error occurred during collection of Cause
maintenance information from Replication An error occurred during collection of
Monitor. maintenance information via the
cvxpaegetlogs command.
Action
Carry out the action for the
Replication Monitor error message
that was output prior to this message.
KAVN00168-I Backup of the conf file from Replication Monitor Cause
will now start. Backup using the hcmdsbackups
command has started.
Action
KAVN00169-I Backup of the conf file from Replication Monitor Cause
stopped. Backup using the hcmdsbackups
command has ended successfully.
Action
KAVN00170-E An error occurred during backup of the conf file Cause
from Replication Monitor. An error occurred during backup
using the hcmdsbackups command.
Action
Carry out the action for the
Replication Monitor error message
that was output prior to this message.
KAVN00171-E The specified parameter value is invalid. Cause
The argument in the
cvxpaegetlogs or hcmdsbackups
command is invalid.
Action
Revise the argument as necessary.
KAVN00172-E The drive does not exist. Cause
The argument in the
command contains a non-existent
drive letter.
Action
Specify a drive that exists.
KAVN00173-E The copy source directory directory-name does Cause
not exist. The copy source directory used in the
command execution does not exist.
Action
Check whether the directory was
moved or deleted after installation.
KAVN00174-E A subdirectory or file exists in the specified Cause
directory. A subdirectory or file exists in the
directory specified in the argument
used for the cvxpaegetlogs or
hcmdsbackups command execution.
Action
Check for a subdirectory or file within
the directory specified in the
command argument. If a subdirectory
or file is found, either delete the
subdirectory or file, or specify a
different directory, which does not
contain a subdirectory or file, for the
command argument.
Messages 138
KAVN00175-I The information collected into directory-name has Cause
finished. Collection of information into the
directory specified in the
cvxpaegetlogs command has
finished.
Action
KAVN00176-E file-name cannot be accessed. Cause
An attempt to access the specified file
failed during execution of the
command.
Action
Revise the file access permissions.
KAVN00177-I The backup to directory-name has finished. Cause
Backup of information into the
directory specified in the
hcmdsbackups command has
finished.
Action
KAVN00178-E The user group permissions are not system Cause
administrator permissions. The user group does not have system
administrator permissions.
Action
Log in as a user who has
6-3 KAVN00200 - KAVN00399

This section describes the messages generated by Replication Monitor, from KAVN00200 to KAVN00399, and
the associated actions.
KAVN00202-I Do you want to refresh to acquire the latest Cause

information? An attempt was made to refresh the
latest Replication Monitor information.
Action
Check the information displayed
together with the message. If the
information is correct, click OK to
proceed with the operation. If the
information is incorrect, click Cancel
to cancel the operation.
KAVN00203-I Now refreshing ...This operation might take Cause
several minutes. OK was clicked in the confirmation
dialog box for updating Replication
Monitor information.
Action
Wait until Replication Monitor has
finished refreshing the information.
KAVN00204-I node-name was refreshed successfully. Cause
Replication Monitor has refreshed the
information successfully.
Action
Messages 139
KAVN00205-W The copy type of the specified copy pair is copy- Cause
type. Therefore the operation will be performed in An attempt was made to change a
units of consistency groups. pair status using the unit of a copy
pair, for a copy pair whose copy type
was Continuous Access XP
Extension.
Action
For copy pairs whose copy type is
Continuous Access XP Extension
(CA-XP(Async) is displayed in Copy
Type), the pair status can be changed
in units of consistency groups, but not
in units of individual copy pairs.
KAVN00206-I Now changing the copy pair status...This Cause
operation might take several minutes. Replication Monitor is now changing
the pair status.
Action
Wait until the pair status has been
changed.
KAVN00207-I The copy pair status has changed. Cause
Replication Monitor has successfully
changed the pair status.
Action
KAVN00208-I Are you sure you want to delete the following Cause
monitoring configurations? An attempt was made to delete the
monitoring configurations from
Action
Messages 140
KAVN00209-E An error that stopped processing occurred. Cause
(cause = cause) Errors associated with internal causes
are as follows:
• The Jump button is selected in the
navigation frame
• A method is selected in the method
frame
• There was a change in windows in
the information frame
• There was a change in dialog boxes
associated with a status change
Action
Based on information output as the
cause, check the OS and Command
View XP AE Suite log files for errors
related to the Replication Monitor
execution environment. If an error has
occurred, resolve the problem and
then try the operation again in
If there are no problems in the
Replication Monitor execution
environment but the message still
appears, collect log information by
using the maintenance information
batch collection command of
Command View XP AE Suite, and
then contact technical support.
KAVN00210-W {Configuration Name | Check Configurations | Cause
Mail Server | To | User Name | Password | The OK button was clicked in one of
Number of Notifications} is not specified. the following situations during addition
or deletion of monitoring
configurations:
• The Configuration Name, Mail Server,
or To box is left blank
• Check Configurations is not selected
• SMTP Authentication is selected but
either the User Name or Password
box is left blank
• Specify number of times is selected
but Number of Notifications box is left
blank
Action
Check the output information, and
then enter additional monitoring
configurations as necessary.
KAVN00211-E An unexpected error occurred. Cause
An unexpected GUI error occurred.
Action
Based on information output as the
cause, check the OS and Command
View XP AE Suite log files for errors
in the Replication Monitor execution
environment. If an error has occurred,
resolve the problem and then try the
operation again in Replication
Monitor.
batch collection Command View XP
AE Suite, and then contact technical
support.
Messages 141
KAVN00212-E Changing the pair status failed at node-name. Cause
An attempt to change a pair status in
Replication Monitor has failed.
Action
Check the status of the applicable
copy pair to see whether it can be
changed to the pair status specified.
KAVN00213-W A non-recommended value is specified for the Cause
copy pace. Make sure the value is correct. Do An attempt was made to change the
you want to continue processing? pair status while a non-recommended
value was specified for the copy pace.
Changing the pair status to a non-
recommended copy pace might cause
data duplication and affect host I/O
performance.
Action
Make sure that the copy pace value is
correct before proceeding with the
operation. If the value is incorrect,
revise it as necessary.
When this message is generated, use
of the default value (i.e., the
recommended value) is advised
unless there are special
circumstances.
KAVN00214-W Please enter your license key. Cause
The Replication Monitor Login window
was started without a license key
entered. Login to Replication
Manager is not permitted.
Action
Start the license registration window
(Version Information dialog box) and
enter an issued Replication Monitor
license key.
KAVN00216-E The specified monitoring configuration has Cause
already been deleted. (configuration name = An attempt was made to delete a
configuration-name) monitoring configuration that has
already been deleted.
Action
Check the configuration name
displayed in the message to see if the
monitoring configuration has already
been deleted.
KAVN00217-W A configuration name has not been selected. Cause
An attempt was made to delete the
monitoring configuration with no
monitoring configuration selected.
Action
Select the monitoring configuration to
be deleted, and then re-execute the
deletion operation.
KAVN00218-E An error occurred in HiCommand Suite Single Cause
Sign On Service. An error occurred in HiCommand
Suite Single Sign On Service
processing.
Action
Re-enter the Replication Monitor user
name and password. Also, make sure
that the service has started and is
operating normally.
Messages 142
KAVN00219-W The session has timed out. Please log in again. Cause
The session has timed out.
Action
In the Login window, re-enter the
Replication Monitor user name and
password, and then log in to
Replication Monitor again. Also, make
sure that the service has started and
is operating normally.
KAVN00220-W Enter a valid email address. Cause
While adding or editing a monitoring
configuration, an attempt was made
to register a monitoring configuration
that had an invalid value for To.
Action
Enter a valid value for To, and then
register the monitoring configuration.
KAVN00221-W An invalid character has been entered for the Cause
{Configuration Name | Mail Server | To | Subject | While adding or editing a monitoring
User Name | Password | Number of Notifications} configuration, an attempt was made
value. to register a monitoring configuration
containing an invalid value. Possible
causes are as follows:
• The character string that was entered
for the item value includes invalid or
multi-byte characters.
• Specify number of times was selected
but a non-numerical value was
entered in Number of times.
Action
Enter a valid value for the item
specified in the message, and then
KAVN00222-W Enter your {User ID | Password}. Cause
No value has been entered in User ID
or Password in the Replication
Monitor Login window.
Action
Enter a valid value in the item
specified in the message, and then
log in.
KAVN00223-W The session is invalid. Please log in again. Cause
The session becomes invalid.
Action
In the Login window, re-enter the user
name and password for Replication
Monitor, and then log in to Replication
Monitor again.
Also, make sure that the service has
started and is operating normally.
KAVN00224-W The value entered for 'Specify number of times' is Cause
outside the valid range. Enter a value from 1 to The value entered for the number of
99. notifications while adding or editing
the monitoring configuration is not a
value from 1 to 99.
Action
Enter a value from 1 to 99 for the
number of notifications, and then
Messages 143
KAVN00225-W The number of characters that can be entered for Cause
the {Configuration Name | Mail Server | To | While adding or editing a monitoring
Subject | Message | User Name | Password} configuration, one or more of the
value is in the range {4-25 | 4-25 | 1-100 | 1-500 | character strings contained more than
3-320 | 0-255 | 0-500 | 1-64 | 0-64}. the maximum number of characters.
Action
Verify the maximum number of
characters for each item identified in
the message, revise the character
strings as necessary, and then
KAVN00226-E The user ID or password is invalid. Cause
The value entered in User ID or
Password in the Replication Monitor
Login window is invalid.
Action
Enter a valid user ID and password,
and then log in.
KAVN00227-E An attempt to retrieve the copy pair information Cause
has failed. An attempt to retrieve the target copy
pair information has failed.
Action
An inconsistency might have occurred
in the information about the target
copy pair, or a problem might have
occurred in the copy pair. Make sure
that there is no problem in the target
copy pair. Then, execute the refresh
information method in the method
frame, and refresh the information by
using Replication Monitor.
KAVN00229-W The {Temporary | Emergency} license is valid for Cause
license-validity-period more days. It will expire on The Login window was started using
license-expiry-date. a license whose registered license
type was temporary or emergency.
Action
Check the validity period and expiry
date of the license shown in the
message, and then enter a valid
license before the temporary or
emergency license expires.
KAVN00230-W The {Temporary | Emergency} license expired on Cause
license-expiry-date. An attempt was made to start the
login window using an expired
temporary or emergency license.
Action
Start the license registration window
(Version Information dialog box), and
then enter your issued Replication
Monitor license key.
Messages 144
KAVN00231-E An attempt to acquire license information has Cause
failed because an unexpected error occurred. Replication Monitor failed to acquire
license information due to an
unexpected error. There might be a
problem in the OS running Replication
Monitor, or in the Command View XP
AE Suite environment.
Action
Check the OS and Command View
XP AE Suite log files for errors in the
Monitor.
If you cannot resolve the problem, the
component used to acquire license
information might be missing. Re-
install Replication Monitor, and then
perform setup again.
If the message appears again, collect
log information by using the
maintenance information batch
collection command of Command
View XP AE Suite, and then contact
technical support.
KAVN00232-W Replication Monitor requires JavaScript. Use a Cause
JavaScript-enabled browser. JavaScript is disabled in your Web
browser settings.
Action
Change your Web browser settings to
enable JavaScript.
KAVN00233-W Replication Monitor cannot be executed because Cause
the version of JavaScript is older than 5.5. Replication Monitor could not be
Update JavaScript to version 5.5 or later. executed because the computer is
using a version of JavaScript older
than 5.5.
Action
Upgrade the version of JavaScript
used in the environment to version
5.5 or later.
Messages 145
KAVN00234-E An attempt to register license information has Cause
failed because an unexpected error occurred. Replication Monitor failed to register
license information due to an
unexpected error. There might be a
problem in the OS running Replication
Monitor or in the Command View XP
AE Suite environment.
Action
Monitor.
If you cannot resolve the problem, the
component used to acquire license
information might be missing. Re-
perform setup again.
If the message appears again, collect
log information by using the
maintenance information batch
collection command of Command
View XP AE Suite, and then contact
technical support.
KAVN00235-I The license information was updated Cause
successfully. The license was registered
successfully in Replication Monitor.
Action
KAVN00236-W Enter the license key. Cause
The License Key box was left blank
during an attempt to register a license
by using a license key.
Action
Enter a valid license key, and then
register the license.
KAVN00237-W Enter the license file. Cause
The License File box was left blank
during an attempt to register a license
by using a license file.
Action
Enter a valid license file, and then
register the license.
KAVN00238-E The license file exceeds the maximum size. Cause
The license file you attempted to
register exceeds 512 KB.
Action
Make sure that the correct license file
is selected. If you cannot resolve the
problem, contact technical support.
KAVN00239-E The entered license key is invalid. Cause
An attempt was made to register an
invalid license key.
Action
Make sure that the license key is valid
and is not already registered.
KAVN00240-E The entered license file is invalid. Cause
An attempt was made to register an
invalid license file.
Action
Make sure that the license file is valid
and is not already registered.
Messages 146
KAVN00241-E The license key does not exist in the license file. Cause
An attempt was made to register a
license file that does not contain a
Replication Monitor license key.
Action
Check whether the specified license
file contains a Replication Monitor
license key. Specify a license file that
contains a valid license key.
KAVN00242-E An attempt to acquire Replication Monitor version Cause
information has failed. An attempt to acquire Replication
Monitor version information has failed.
Action
Monitor.
appears, re-install Replication
Monitor, and then perform setup
again.
KAVN00243-E An attempt to acquire information from the Cause
configuration file for Web Client has failed. An attempt to acquire information
from client.properties (the Web
Client configuration file supplied by
Replication Monitor) has failed.
Action
Make sure that
client.properties is stored in
the following location, and that the file
is readable:
• In Windows®:
Replication-Monitor-
installation-folder\conf
If you cannot resolve the problem, re-
perform the setup again.
KAVN00244-E The entered license file could not be found. Cause
An attempt to create a temporary file
for license registration has failed.
Action
Monitor.
batch collection command of
Command View XP AE Suite, and
then contact technical support.
Messages 147
KAVN00245-W During I/O processing for the primary volume, Cause
this processing might result in incomplete data in An attempt was made to change the
the secondary volume. Make sure that I/O copy pair status to Split.
processing for the primary volume is not being Action
performed. Make sure that I/O processing for the
primary volume is not being
performed, and then proceed with the
operation.
KAVN00246-E Operations for copy-pair-name/copy-group-name Cause
cannot be performed. Check whether the status No executable pair operation for the
of the operation target is normal. selected copy pair or copy group
exists.
Action
Check the status of the copy pair or
copy group, fix any problems, and
then try the operation again.
KAVN00247-I Are you sure you want to add the following Cause
monitoring configuration? An attempt was made to add a new
monitoring configuration to
Action
KAVN00248-I Are you sure you want to change the following Cause
monitoring configuration? An attempt was made to change the
settings for an existing monitoring
configuration in Replication Monitor.
Action
KAVN00249-W This window became invalid because a session Cause
time out occurred. Perform the operation again, No operation was performed within
and redisplay the window. the time limit (60 minutes).
Action
If this message appears in the
information frame, redisplay the
information frame from the navigation
frame or the method frame.
If this message appears in a popup
window, close the popup window and
repeat the entire operation from the
beginning.
KAVN00250-I Now modifying the Replication Monitor Cause
configuration... Processing to update Replication
Monitor configuration information was
executed.
Action
Wait until the processing to update
Replication Monitor configuration
information finishes.
KAVN00251-I The Replication Monitor configuration was Cause
modified successfully.(configuration = The Replication Monitor configuration
configuration-information) information was updated successfully.
Action
Messages 148
6-4 KAVN00400 - KAVN00599
KAVN00400-E An attempt to acquire the list of host information Cause

has failed. An attempt to acquire the list of host
information has failed.
Action
Try the operation again. If this does
not resolve the problem, follow the
instructions in the accompanying
detailed message, and then try the
operation again.
KAVN00401-E An attempt to acquire host information has failed. Cause
(host name = host-name) An attempt to acquire host information
has failed.
Action
operation again.
KAVN00402-E An attempt to acquire the list of LU information Cause
has failed. An attempt to acquire the list of LU
Action
operation again.
KAVN00403-E An attempt to acquire LU information has failed. Cause
(LU name = LU-name) An attempt to acquire LU information
has failed.
Action
operation again.
KAVN00404-E An attempt to acquire the list of pair information Cause
has failed. An attempt to acquire the list of pair
Action
operation again.
KAVN00405-E An attempt to acquire pair information has failed. Cause
(pair name = pair-name) An attempt to acquire pair information
has failed.
Action
operation again.
Messages 149
KAVN00406-E An attempt to acquire primary volume information Cause
has failed. (volume name = volume-name) An attempt to acquire primary volume
Action
operation again.
KAVN00407-E An attempt to acquire secondary volume Cause
information has failed. (volume name = volume- An attempt to acquire secondary
name) volume information has failed.
Action
operation again.
KAVN00408-E An attempt to acquire volume information has Cause
failed. (volume name = volume-name) An attempt to acquire volume
Action
operation again.
KAVN00409-E An attempt to acquire the list of subsystem Cause
information has failed. An attempt to acquire the list of
subsystem information has failed.
Action
operation again.
KAVN00410-E An attempt to acquire subsystem information has Cause
failed. (subsystem name : subsystem-name) An attempt to acquire subsystem
Action
operation again.
KAVN00411-E An attempt to acquire the list of pair management Cause
servers has failed. An attempt to acquire the list of pair
management servers has failed.
Action
operation again.
KAVN00412-E An attempt to acquire the pair management Cause
server has failed. (pair management server name An attempt to acquire the pair
= pair-management-server-name) management server has failed.
Action
operation again.
Messages 150
KAVN00413-E An attempt to acquire the list of configuration Cause
definition file information has failed. An attempt to acquire the list of
configuration definition file information
has failed.
Action
operation again.
KAVN00414-E An attempt to acquire configuration definition file Cause
information has failed. (configuration definition An attempt to acquire configuration
file name = configuration-definition-file-name) definition file information has failed.
Action
operation again.
KAVN00415-E An attempt to acquire the list of copy group Cause
information has failed. An attempt to acquire the list of copy
group information has failed.
Action
operation again.
KAVN00416-E An attempt to acquire copy group information has Cause
failed. (copy group name = copy-group-name) An attempt to acquire copy group
Action
operation again.
KAVN00417-E An attempt to acquire the list of copy pair Cause
information has failed. An attempt to acquire the list of copy
pair information has failed.
Action
operation again.
KAVN00418-E An attempt to acquire copy pair information has Cause
failed. (copy pair name = copy-pair-name) An attempt to acquire copy pair
Action
operation again.
KAVN00420-E An attempt to acquire pair operation information Cause
has failed. An attempt to acquire pair operation
Action
operation again.
Messages 151
KAVN00421-E An attempt to acquire the last update time has Cause
failed. An attempt to acquire the last update
time has failed.
Action
operation again.
KAVN00422-E An attempt to refresh data has failed. Cause
An attempt to refresh data has failed.
Action
If an error occurs when the refresh
operation is performed, do the
following:
• When a detailed message is output:
accompanying detailed message, and
then execute the Refresh All method.
• When a detailed message is not
output:
Execute the Refresh All method.
If this does not resolve the problem,
obtain maintenance information and
KAVN00423-E An attempt to acquire the refresh status has Cause
failed. An attempt to acquire the refresh
status has failed.
Action
Execute the Refresh All method. If
this does not resolve the problem,
follow the instructions in the
KAVN00424-E An attempt to change the pair status has failed. Cause
({pair-name | copy-group-name}:value) An attempt to change the pair status
has failed.
Action
Some operations cannot be
performed depending on the
configuration and status of the copy
pair. Make sure that the operation you
are attempting can be performed, by
checking the current status of the
copy pair, checking the pair
configuration (such as cascade),
checking the status of the copy pair
that makes up the copy group, and
then referring to the manuals for
volume replication functionality.
KAVN00439-E The specified pair operation is invalid. Cause
The specified pair operation is invalid.
Action
Make sure that the pair operation is
correct.
KAVN00440-E The specified copy pace is invalid. Cause
The specified copy pace is invalid.
Action
Make sure that the copy pace is
correct.
Messages 152
KAVN00441-E An attempt to acquire the list of path information Cause
has failed. An attempt to acquire the list of path
Action
operation again.
KAVN00442-E An attempt to refresh data has timed out. (time Cause
out = time-out-period (millisecond)) The time for Device Manager refresh
processing has exceeded the limit.
Action
Execute the Refresh All method. If
KAVN00443-E The specified information does not exist. It is Cause
possible that information in Replication Monitor This message is output when the
was already updated. specified navigation frame information
becomes old due to another client has
updating the information.
Action
Click Refresh on the navigation frame
to acquire the latest information.
KAVN00500-I Refresh processing will now start. Cause
Refresh processing has started.
Action
KAVN00501-W The next periodic refresh and condition Cause
monitoring has been cancelled because the last Possible causes are as follows:
periodic refresh or condition monitoring has not 1 The time for performing a periodic
finished. refresh and condition monitoring was
reached while the previous periodic
refresh and condition monitoring was
still in progress.
2 The hrpmsetup command was used
to set both Retrieve Information
(Interval) and Refresh Information
(Interval) to values other than 0, and
the set times overlapped.
Action
• For cause 1: Extend the monitoring
interval so that each refresh starts
after the previous refresh has
completed.
• For cause 2: No response is required.
KAVN00502-I The pair change operation for this copy pair is Cause
not supported. Use a different tool to change the An attempt was made to change the
pair status. pair status of a copy pair whose
status cannot be changed using
Action
Change the pair status using other
software that can perform the copy
pair operation.
An unexpected error occurred in the
Replication Monitor internal interface.
Action
Contact technical support.
Messages 153
6-5 KAVN00600 - KAVN00799
KAVN00601-I The email was sent. (configuration name = Cause

configuration-name) The email was sent.
Action
KAVN00701-E An attempt to acquire monitoring configuration Cause
information has failed. An attempt to access a database has
failed.
Action
then try again.
KAVN00702-E An attempt to acquire action definition Cause
failed.
Action
then try again.
KAVN00703-E An attempt to update a monitoring configuration Cause
has failed. An attempt to access a database has
failed.
Action
then try again.
KAVN00704-E An attempt to delete a monitoring configuration Cause
has failed. An attempt to access a database has
failed.
Action
then try again.
KAVN00705-E An attempt to add a monitoring configuration has Cause
failed. An attempt to access a database has
failed.
Action
then try again.
KAVN00706-E An attempt to acquire an object address for a Cause
monitoring configuration has failed. An attempt to access a database has
failed.
Action
then try again.
KAVN00707-E The monitoring configuration cannot be Cause
registered. Registration is not possible because
there are too many monitoring
configurations.
Action
Delete any unnecessary monitoring
configurations, and then try again.
KAVN00708-E The specified value is incorrect. Cause
An entered value is invalid.
Action
Revise the value as instructed in the
detailed message, and then try again.
Messages 154
KAVN00709-E An attempt to issue an alert has failed. Cause
(configuration name = configuration-name, detail An attempt to issue an alert has
code = detailed-code) failed.
Action
The accompanying detailed code is
the ID for the detailed message.
Follow the instructions in the detailed
message.
KAVN00710-E A monitoring configuration has already been Cause
registered with the same configuration name An attempt was made to register a
(configuration-name). new monitoring configuration by using
a configuration name that has already
been registered.
Action
Try again using a different
configuration name.
KAVN00711-E The monitoring configuration of the specified Cause
configuration name does not exist. (configuration An attempt was made to delete a
name = configuration-name) monitoring configuration that does not
exist.
Action
Check whether another administrator
has recently deleted the monitoring
configuration. Display the list of
monitoring configurations again and
check the registered monitoring
configurations.
KAVN00712-E An attempt to register action definition Cause
failed.
Action
1 Follow the instructions in the
accompanying detailed message.
2 Display the Set Monitoring
Configurations subwindow and select
the configuration Name that you want
to register.
3 Re-enter the settings information in
the Edit Monitoring Configuration
dialog box, and then either refresh or
delete the monitoring configuration in
the Set Monitoring Configurations
subwindow.
KAVN00713-E An attempt to acquire monitoring configuration Cause
information to distinguish configurations has An attempt to access a database
failed. failed while processing to acquire
monitoring configurations during a
refresh operation.
Action
accompanying detailed messages.
Monitoring will be newly performed
during the next monitoring period (i.e.,
after the monitoring interval has
elapsed).
Messages 155
KAVN00714-E An attempt to register the number of alert Cause
executions has failed. (configuration name = An attempt to access a database
configuration-name) failed while processing to distinguish
monitoring configurations during a
refresh operation. When this message
appears, the number of notifications
might exceed the specified maximum.
Action
accompanying detailed messages.
The specified number of notifications
will then be performed.
KAVN00715-E Data that remained when the error occurred. Cause
(configuration name = configuration-name) An attempt was made to reference
the registered data of a monitoring
configuration that remained in an
incomplete form. When this
monitoring configuration was
registered, a database error might
have occurred and some of the email
parameters might not have been
registered. This monitoring
configuration has been disabled.
Action
To enable this monitoring
configuration, enter the correct email
parameters in the Set Monitoring
Configurations subwindow, and then
update the monitoring configuration. If
this monitoring configuration is
unnecessary, delete it.
KAVN00716-E An attempt to add a monitoring configuration Cause
failed because other information was being Multiple administrators simultaneously
added at the same time. attempted to register additional
Action
Try again, taking care to avoid
simultaneous addition operations.
An unexpected error occurred during
internal Replication Monitor
monitoring processing.
Action
6-6 KAVN01200 - KAVN01399

KAVN01210-E The user group permissions are not system Cause

administrator permissions. The user group does not have system
Action
Log in as a user who has
KAVN01211-E Installation is not possible on the installed OS. Cause
Replication Monitor cannot be
installed on the OS.
Action
Install Replication Monitor on a
®
computer running Windows 2000 or
®
Windows Server 2003.
Messages 156
KAVN01212-E The video resolution is inadequate. (SVGA or Cause
higher is required.) The video resolution is inadequate.
Action
Set the video resolution to SVGA or
higher.
KAVN01215-E A Device Manager version that is a prerequisite Cause
version for Replication Monitor has not been A Device Manager version that is a
installed. prerequisite version for Replication
Monitor has not been installed.
Action
Install a prerequisite version of Device
Manager and then install Replication
Monitor. For details on prerequisite
Device Manager versions, see section
2-1-1 .
KAVN01216-E An attempt to read installed product version Cause
information from the registry has failed. Device Manager might not be
installed correctly.
Action
Re-install Device Manager, and then
install Replication Monitor.
KAVN01217-E The version to be installed is incorrect. Cause
An attempt was made to install an
incorrect version.
Action
Install a Replication Monitor version
that is the same or newer than the
version already installed.
KAVN01220-E An attempt to register product version information Cause
in the registry has failed. A disk access error might have
occurred.
Action
Check for problems in the installation
target disk.
KAVN01224-E An attempt to create trace information has failed. Cause
The computer to be setup has
insufficient memory resources.
Action
Close some applications to secure
more memory resources, and then re-
execute installation or uninstallation.
KAVN01226-W An attempt to store the trace information file has Cause
failed. An attempt to store the trace
information file has failed.
Action
No action is required if the setup
completed successfully.
If the setup did not complete
successfully, close some applications
to secure more memory resources,
and then re-execute setup.
KAVN01227-E An attempt to check a Common Component Cause
process has failed. Common Component might not be
Action
KAVN01228-E An attempt to start a Common Component Cause
process has failed. Common Component might not be
Action
Perform an overwrite installation of
Messages 157
KAVN01229-E An attempt to stop a Common Component Cause
process has failed. Other Command View XP AE Suite
software services might be running.
Action
Make sure that no other Command
View XP AE Suite software services
are running, and then re-install or
uninstall Replication Monitor.
KAVN01230-E An attempt to register a Web application has Cause
failed. Common Component might not be
Action
KAVN01231-E An attempt to cancel registration of a Web Cause
application has failed. Common Component might not be
Action
Replication Monitor, and then
An unexpected error occurred.
Action
Obtain the installation related trace
log file and log information for the
Common Component command
execution, and then contact technical
support.
KAVN01233-E An attempt to register the use of Common Cause
Component has failed. Common Component might not be
Action
Uninstall Replication Monitor, and
then re-install Replication Monitor.
KAVN01234-E An attempt to cancel registration of the use of Cause
Common Component has failed. An attempt to cancel registration of
the use of Common Component has
failed.
Action
Uninstall Replication Monitor again. If
collect the installation related trace
log file and the log information that
was output when the Common
Component command was executed,
and then contact technical support.
KAVN01235-E An attempt to create the property file has failed. Cause
An old property file for Replication
Monitor might remain in the specified
installation destination.
Action
Delete the old property file, and then
re-install Replication Monitor.
KAVN01239-E Please stop the services of Suite products. Cause
A service of the Command View XP
AE Suite software is running.
Action
Stop all of the services of Command
View XP AE Suite software.
KAVN01240-E Enter the host name (IP address). Cause
No host name (IP address) has been
entered.
Action
Enter a host name (IP address).
Messages 158
KAVN01241-E Enter the port number. Cause
No port number has been entered.
Action
Enter a port number.
KAVN01242-E Enter the user ID. Cause
No user ID has been entered.
Action
Enter a user ID.
KAVN01243-E Enter the password. Cause
No password has been entered.
Action
Enter a password.
KAVN01244-E Enter the installation folder. Cause
No installation folder has been
entered.
Action
Enter the installation folder.
KAVN01245-E The entered host name (IP address) is invalid. Cause
The length of the string entered for
the host name (IP address) is invalid.
The entered string exceeds 2,083
bytes.
Action
Enter a string whose length is within
the valid range.
KAVN01246-E The entered port number is invalid. Cause
The entered port number contains
non-numeric characters, or is not in
the valid range (from 1 to 65535).
Action
Enter a number from 1 to 65535.
KAVN01247-E The entered user ID is invalid. Cause
The user ID contains invalid
characters, or is outside the valid
range (from 4 to 25 characters).
Action
Enter a user ID containing from 4 to
25 valid characters. For more
information about valid characters for
user IDs, see 2-1-2 .
KAVN01248-E The entered password is invalid. Cause
The password contains invalid
characters or is outside the valid
range (from 4 to 25 characters).
Action
Enter a password containing from 4 to
25 valid characters. For more
information about valid characters for
passwords, see 2-1-2 .
KAVN01249-E The entered installation folder is invalid. Cause
The length of the specified installation
folder path exceeds 90 bytes.
Action
Using no more than 90 bytes, specify
an installation folder path. Only the
following characters can be used for
the path:
A to Z a to z 0 to 9 # + - . @ _
single-byte spaces
Messages 159
KAVN01250-E An attempt to create a batch file has failed. Cause
An old installation file for Replication
Monitor might remain in the specified
installation destination.
Action
Delete the old installation file, and
KAVN01251-E An attempt to install Common Component has Cause
failed. An attempt to install Common
Component has failed.
Action
Open the installation related trace log
file by using a text editor, and then
check the return code for the error.
If the return code is 2:
Common Component services might
be running. Restart the computer.
After all Command View XP AE Suite
software services stop, re-install
Replication Monitor. An error due to
insufficient free space might have
occurred while installing HiRDB.
Secure more disk space, and then re-
An error occurred during installation
of Common Component due to
insufficient free space. Secure more
disk space, and then re-install
An error occurred during installation
of HiRDB. Command View XP AE
Suite software services might be
running. Restart the computer. After
all Command View XP AE Suite
software services stop, re-install
If the return code is -80:
The Common Component installation
®
has timed out. In Windows , if any
InstallShield tasks still remain, finish
those tasks from the application tab in
®
the Windows task manager, restart
the computer, and then re-install
KAVN01252-E An attempt to uninstall Common Component has Cause
failed. An attempt to uninstall Common
Action
Command View XP AE Suite software
services might be running. Restart the
computer. After all Command View
XP AE Suite software services stop,
KAVN01253-E An attempt to register the log-acquisition Cause
command has failed. Common Component might not be
Action
Messages 160
KAVN01254-E An attempt to delete the log-acquisition Cause
command has failed. An attempt to delete the log-
acquisition command has failed.
Action
KAVN01256-E An attempt to set up a database has failed. Cause
An attempt to set up a database has
failed.
Action
1 Open the installation related trace log
file by using a text editor, and then
check the return code for the error.
2 If the return code is 251, the
specification of the database file
storage destination might be
incorrect. For details on conditions
specifiable for the database file
storage destination, see 2-1-2 .
Also, there might be insufficient free
space in the database file storage
destination. At least 50 MB of free
space is required for the database file
storage destination. Uninstall
Replication Monitor, and then re-
install it.
3 If the return code is 255, installation of
Device Manager might have failed.
Check whether installation of Device
Manager has ended correctly and
then take one of the following actions.
For details on how to install Device
Manager and how to check
installation, see the manual HP
StorageWorks Command View XP
Advanced Edition Device Manager
Server Installation and Configuration
Guide.
If installation of Device Manager
ended correctly, uninstall Replication
Monitor and then re-install it.
If installation of Device Manager
failed, uninstall Replication Monitor,
install Device Manager again and set
it up, and then re-install Replication
Monitor.
4 If the above actions do not resolve the
problem, collect the installation
related trace log file and the log
information that was output when the
Common Component command was
executed, and then contact technical
support.
Messages 161
KAVN01257-E An attempt to perform unsetup of a database has Cause
failed. A Command View XP AE Suite
software service might be running.
Action
Make sure that no other Command
View XP AE Suite software is running,
and then uninstall Replication Monitor
again.
KAVN01258-E An attempt to register repository information has Cause
failed. An attempt to register repository
Action
then re-install it. If this does not
resolve the problem, collect the
installation related trace log file and
the log information that was output
when the Common Component
command was executed, and then
KAVN01259-E An attempt to delete repository information has Cause
failed. An attempt to delete repository
Action
KAVN01260-E An attempt to register the backup command has Cause
Action
KAVN01261-E An attempt to delete the backup command has Cause
Action
uninstall it.
KAVN01262-E An attempt to register an alias for the manual has Cause
Action
KAVN01263-E An attempt to delete an alias for the manual has Cause
Action
uninstall it.
KAVN01264-E HiRDB setup has not finished. Cause
Device Manager might not be
Action
Messages 162
KAVN01265-E An attempt to insert data in the table created for Cause
HiRDB has failed. An attempt to set up the database
might have failed.
Action
then re-install it.
KAVN01266-E Resources are insufficient. Processing cannot Cause
continue. Resources are insufficient.
Action
Close some applications to secure
more memory resources, and then
execute the setup operation.
KAVN01267-E An attempt to create a table for HiRDB has failed. Cause
An attempt to set up the database
might have failed.
Action
then re-install it.
KAVN01268-E An attempt to delete a HiRDB table has failed. Cause
HiRDB might be unstable.
Action
Restart the computer, and then try the
operation again.
KAVN01269-E An attempt to acquire the setup status of the Cause
database has failed. The Common Component version
might be old.
Action
An attempt to install Device Manager
might have failed. Re-install Device
Manager, and then install Replication
Monitor.
KAVN01270-E An attempt to acquire login information for the Cause
database has failed. An attempt to acquire the database
login information has failed.
Action
In Windows:
Make sure that hcmdsUserMng.dll
was copied into Replication-
Monitor-
installation-folder\inst\. If
hcmdsUserMng.dll has not been
copied, re-install Replication Monitor.
KAVN01271-E An attempt to change the URL for Replication Cause
Monitor server information has failed. An attempt to convert the URL for
Replication Monitor server information
has failed.
Action
then re-install it. If this does not
resolve the problem, collect the
installation related trace log file and
the log information that was output
when the Common Component
command was executed, and then
KAVN01272-E An attempt to change the start type of the Cause
Common Component process has failed. Common Component might not be
Action
Messages 163
KAVN01273-E An attempt to create a shortcut to the start menu Cause
has failed. A disk access error might have
occurred.
Action
Make sure that the installation target
disk is correct.
KAVN01274-E An attempt to register uninstallation information Cause
into the registry has failed. A disk access error might have
occurred.
Action
Make sure that the installation target
disk is correct.
KAVN01275-E Enter the storage destination for the database Cause
file. No database file storage destination
has been entered.
Action
Enter the database file storage
destination.
KAVN01276-E The entry for the storage destination of the Cause
database file is invalid. Either the path length for the
database file storage destination
exceeds 100 bytes, or an invalid
character was used.
Action
®
In Windows :
Specify the absolute path of the
database file storage destination
using a maximum of 100 bytes. Only
the following characters can be used
for the folder name:
A to Z a to z 0 to 9 # + - . @ _
single-byte spaces
Also, you cannot specify a folder that
is directly below a drive.
Do not specify the path delimiter
character (\) at the end of the folder
path.
KAVN01277-E An attempt to update the database has failed. Cause
Action
operation again.
KAVN01278-E An attempt to start HiRDB has failed. Cause
Action
operation again.
KAVN01279-E An attempt to stop HiRDB has failed. Cause
Action
operation again.
KAVN01280-E Enter the shared disk. Cause
Information such as path information
has not been entered for the shared
disk.
Action
Enter information such as path
information for the shared disk.
Messages 164
KAVN01281-E The entry for the shared disk is invalid. Cause
The path length for the shared disk
exceeds 100 bytes or an invalid
character has been used.
Alternatively, no database file exists
in the shared disk specified at
installation of a cluster configuration
(standby system). The path specified
at installation of the standby system
and the path specified at installation
of the executing system might be
different, or the path specified at
installation of the executing system
might not be a shared disk.
Action
®
In Windows :
Specify the absolute path of the
shared disk using a maximum of 100
bytes. Only the following characters
can be used for the path name:
A to Z a to z 0 to 9 # + - . @ _
single-byte spaces
Also, you cannot specify a folder that
is directly below a drive.
Do not specify the path delimiter
character (\) at the end of the folder
path.
If you are installing a cluster
configuration (standby system), enter
the same path as the value specified
at installation of the executing system.
For details on the action to be taken if
the path specified at installation of the
executing system is not a shared disk,
see section 6-9 .
KAVN01282-W An older version than the currently installed Cause
version of Replication Monitor will be installed. An attempt was made to install a
regular version or corrected version of
Replication Monitor by using a version
that is earlier than the installed
managed version.
Action
To return to the previous version,
continue the installation processing.
To cancel the installation, cancel the
installation processing.
KAVN01283-W An attempt to start the HiCommandServer Cause
process has failed. The data used by Device Manager
might be corrupted.
Action
After Replication Monitor installation
completes, start the
HiCommandServer service manually.
For details on how to start the
HiCommandServer service, see the
manual HP StorageWorks Command
View XP Advanced Edition Device
Manager Server Installation and
Messages 165
6-7 Detailed Messages
This section describes the detailed messages generated by Replication Monitor to identify the causes of
problems.
RPM-00400 Access permission for the specified user is invalid. Cause

The user does not have permission
to access Device Manager.
Action
Make sure that the specified user
belongs to a Device Manager
System Administrator user group or
Storage Administrator user group. If
RPM-00401 An attempt to authenticate failed because an Cause
invalid user name or password was used. An attempt was made to perform
authentication to HiCommand Suite
Single Sign On Service using an
invalid user name or password.
Action
Retry authentication using a valid
user name and password. If this
does not resolve the problem,
RPM-00402 An attempt to connect to the HiCommand Suite Cause
Single Sign On Service has failed. An attempt to connect to
HiCommand Suite Single Sign On
Service has failed.
Action
An error occurred in HiCommand
Suite Single Sign On Service. Carry
out the following actions. The
hcmdssrv command can be used
to check the operating status of
each service.
1 Make sure that HiRDB is running.
2 Make sure that HiCommand Suite
Single Sign On Service is running.
3 Check the HiCommand Suite Single
Sign On Service settings and status,
and then revise them as necessary.
4 Make sure that Device Manager is
running (if required).
5 If the above steps do not resolve the
problem, obtain maintenance
information, and then contact
technical support.
Messages 166
Single Sign On Service has failed. Connection failed due to a
communication problem in
Service.
Action
A problem has occurred on the
remote Web server or proxy server.
Carry out the following actions. The
each service.
technical support.
Single Sign On Service has failed. Connection failed due to an
authentication failure in HiCommand
Suite Single Sign On Service.
Action
each service.
technical support.
Messages 167
Single Sign On Service has failed. Connection failed due to an error in
Service.
Action
each service.
technical support.
Single Sign On Service has failed. Connection failed due to a
connection error in HiCommand
Suite Single Sign On Service.
Action
each service.
For details, see the manual HP
StorageWorks Command View XP
Advanced Edition Device Manager
Server Installation and
technical support.
Messages 168
Single Sign On Service has failed. An attempt to acquire the
feature failed because a connection
could not be established with
HiCommand Suite Single Sign On.
Action
each service.
technical support.
RPM-00408 An invalid array family name was acquired. Cause
An acquired array family name is
invalid.
Action
not resolve the problem, contact
technical support.
RPM-00409 Invalid property information was acquired. Cause
Acquired property information is
invalid.
Action
Reset the values by using the
hrpmsetup command, and then try
the operation again. If this does not
resolve the problem, contact
technical support.
RPM-00410 An attempt to acquire property information has Cause
failed. An attempt to acquire the list of
property information has failed.
Action
Reset the values by the hrpmsetup
command, and then try the
operation again. If this does not
resolve the problem, contact
technical support.
RPM-00411 An attempt to acquire the array family name has Cause
failed. An attempt to acquire the array
family name failed because another
client deleted the storage settings.
Action
Use Replication Monitor Web Client
to execute a system-wide
information refresh (execute the
Refresh All method), and then try
the operation again.
Messages 169
RPM-00412 An attempt to acquire copy information has failed. Cause
An attempt to acquire copy pair
information failed because another
client deleted the storage settings.
Action
RPM-00413 An attempt to acquire copy pair information has Cause
failed. The information on the navigation
frame was updated first. The
information on the information frame
is currently being updated.
Action
Try the operation again. If the error
occurs again, perform a refresh, and
RPM-00414 An attempt to acquire information from Common Cause
Component has failed. An attempt to acquire information
from Common Component has
failed.
Action
occurs repeatedly, perform a
refresh, and then try the operation
again.
RPM-00415 An attempt to acquire information from Device Cause
Manager has failed. An attempt to acquire information
from Device Manager has failed.
Action
occurs again, perform a refresh, and
RPM-00601 The Configuration Name is incorrect. Cause
The value specified for
Configuration Name is invalid.
Action
Revise the specified value and then
try the operation again.
RPM-00602 The Check Conditions is incorrect. Cause
The value specified for Check
Conditions is invalid.
Action
RPM-00603 The Mail Server is incorrect. Cause
The value specified for Mail Server
is invalid.
Action
RPM-00604 The To is incorrect. Cause
The value specified for To is invalid.
Action
RPM-00605 The Subject is incorrect. Cause
The value specified for Subject is
invalid.
Action
Messages 170
RPM-00606 The Message is incorrect. Cause
There is an error in the mail text
(Message).
Action
Revise the mail text and then try the
operation again.
RPM-00607 The User Name is incorrect. Cause
The value specified for User Name
is invalid.
Action
RPM-00608 The Password is incorrect. Cause
The value specified for Password is
invalid.
Action
RPM-00609 The Number of Notifications is incorrect. Cause
The value specified for Number of
Notifications is invalid.
Action
RPM-00701 An attempt to send mail has failed. Cause
An attempt to send mail has failed.
Action
Check the email parameters
registered in the monitoring
configurations, and then re-register
any invalid parameters.
Also, make sure that the SMTP
server environment is set up to send
email. If necessary, fix any
problems.
RPM-00702 An attempt to create mail-send information has Cause
failed. An attempt to create information
required to send an email has failed.
Action
Check the email parameters
registered in the monitoring
configurations, and then re-register
any invalid parameters.
If the problem occurs again after re-
registration, contact technical
support.
RPM-00810 A connection with the Common Component cannot Cause
be established. A connection with the Common
Component cannot be established.
Action
Terminate Common Component by
using the hcmdssrv command, and
then restart the same component.
RPM-00811 An attempt to acquire data from the Common Cause
Component has failed. An attempt to acquire Replication
Monitor data from Common
Action
Messages 171
RPM-00812 An attempt to write Common Component data has Cause
failed. An attempt to write Replication
Monitor data in Common
Action
RPM-00813 The Common Component data is invalid. Cause
The Common Component data is
invalid.
Action
If the message appears again, re-
RPM-00820 A connection with the Common Component Cause
database cannot be established. The system cannot connect to the
Common Component database, or
the Common Component database
is not running.
Action
Terminate Common Component by
RPM-00821 An attempt to acquire data from the Common Cause
Component database has failed. An attempt to acquire Replication
Monitor data from the Common
Component database has failed.
Action
RPM-00822 An attempt to write data to the Common Cause
Component database has failed. An attempt to write Replication
Monitor data in the Common
Component database has failed.
Action
If the message appears again,
terminate Common Component by
If the message appears again,
uninstall then re-install Replication
Monitor. Note that this operation will
delete all Replication Monitor
settings data.
Messages 172
RPM-00823 The data in the Common Component database is Cause
invalid. The data in the Common
Component database is invalid.
Action
RPM-00824 The (logical storage) area for the Common Cause
Component database is full. The memory area allocated to
Replication Monitor in the memory
area for the Common Component
database is insufficient.
Action
Secure more memory in the
Common Component database as
described in section 6-8 .
RPM-00831 An unexpected error occurred. Cause
The data for internal processing is
invalid.
Action
RPM-00851 The number of set monitoring configurations Cause
exceeds the maximum. (maximum = the- Adding a new monitoring
maximum-number-of-settable-monitoring- configuration will cause the number
configurations) of registered monitoring
configurations to exceed the
maximum.
Action
Reduce the number of registered
monitoring configurations, and then
register the new monitoring
configuration.
RPM-00852 An attempt to acquire the user ID and password for Cause
Common Component has failed. An attempt to acquire the user
name and password that are used
for connecting to Common
Component, has failed.
Action
Check the parameter settings
related to Device Manager by using
the –v option with the hrpmsetup
command. If necessary, use the
hrpmsetup command to reset the
common parameters.
RPM-00853 The content of the definition information is Cause
incorrect. The content of a file created during
installation is invalid.
Action
Re-install Replication Monitor.
RPM-00854 An attempt to execute an internal command has Cause
failed. (command file name = command-file-name) An attempt to execute an internal
Replication Monitor command has
failed.
Action
Check the free memory space on
the computer running Replication
Monitor. If necessary, increase the
available memory by stopping any
unnecessary programs.
Messages 173
RPM-00855 A file required to execute processing does not Cause
exist. (file name = file-name) A file required for internal
Replication Monitor processing was
not found.
Action
Re-install Replication Monitor.
RPM-01000 The URL for calling the Device Manager Server Cause
function is invalid. (URL = URL) Either the URL for calling Device
Manager server functions is
incorrect, or the Device Manager
server is not running.
Action
Make sure that the Device Manager
server is running. Also, check the
value of Device Manager Port
Number displayed when the
hrpmsetup command was
executed with the -v option
specified. If the value is invalid, use
the hrpmsetup command to
specify the correct value.
If the above steps do not resolve the
problem, contact technical support.
RPM-01001 An attempt to authenticate the user for calling the Cause
Device Manager Server function has failed. Device Manager server
authentication failed.
Action
Check the user ID and password
used to access the Device Manager
server.
If you cannot resolve the problem,
RPM-01002 The request to the Device Manager Server Cause
function is invalid. The Device Manager server is
refusing requests. The function that
performs request processing might
be missing or execution might not
be permitted on the Device
Manager server.
Action
Make sure that the correct version
of the Device Manager server has
been installed correctly.
RPM-01003 The response from Device Manager Server could Cause
not be parsed. The response from the Device
Manager server could not be
analyzed. The response might be
unknown.
Action
been installed correctly.
Messages 174
RPM-01004 An attempt to call the Device Manager Server Cause
function has failed. (Device Manager Server's error An error occurred during Device
code = Device-Manager-error-code) Manager server processing.
Action
Contact technical support to
investigate the Device Manager
error code displayed in the dialog
box. The Device Manager server log
might also provide information about
the error.
RPM-01005 Information required to proceed with processing is Cause
lacking. Information required to execute
processing is insufficient. There
might be a version incompatibility
between Replication Monitor
modules.
Action
Make sure that Replication Monitor
is installed correctly.
RPM-01006 Processing could not proceed because information Cause
required to proceed with processing is invalid. Information used to execute
processing contains an error. There
might be a version incompatibility
between Replication Monitor
modules.
Action
RPM-01007 An attempt to call the Device Manager Server Cause
function has failed. (Device Manager Server's error A warning was issued during Device
code = Device-Manager-error-code) Manager server processing.
Action
Contact technical support to
investigate the Device Manager
error code displayed in the dialog
box. The Device Manager server log
might also provide information about
the error.
RPM-01008 The call for the Device Manager Server function Cause
timed out. A call for the Device Manager
server function timed out.
Action
Acquiring information can take
longer in large-scale configurations.
Increase the value of the
Replication Monitor setting
parameter ssif.socketTimeout
to provide sufficient time to acquire
information.
Messages 175
RPM-01009 The connection to the Device Manager Server has Cause
timed out. The Device Manager server
connection timed out.
Action
Connection processing can take
longer depending on the Device
Manager server load.
Increase the value of the
Replication Monitor setting
parameter
ssif.socketConnectTimeout to
provide sufficient time for
connection and/or reduce the
Device Manager server load.
RPM-01010 An unexpected error occurred. Cause
An internal error occurred. The
Replication Monitor library might be
invalid, or there might be a version
incompatibility between Replication
Monitor modules.
Action
been installed correctly. Also make
sure that Replication Monitor is
RPM-01011 An error occurred during user name and password Cause
encoding. The encoding is not supported. A
library used internally by Replication
Monitor might be invalid.
Action
RPM-01012 The response is invalid. Cause
The information returned from the
Device Manager server is invalid.
Action
of Device Manager server has been
installed correctly or check the value
of Device Manager Port
Number displayed when the
hrpmsetup command is executed
with the -v option specified. If the
value is invalid, set the correct value
by using the hrpmsetup command.
RPM-01013 An error occurred while connecting to the Device Cause
Manager Server. An error occurred while connecting
to the Device Manager server.
Action
Check the service status of the
Device Manager server. If the
service has stopped, restart it and
try connecting again.
Messages 176
RPM-01014 An error occurred while communicating with the Cause
Device Manager Server. An error occurred during data
transmission from the Device
Manager server.
Action
Check the service status of the
Device Manager server. If the
service has stopped, restart it and
try communicating again.
6-8 Action for Detailed Message RPM-00824

Detailed message RPM-00824 indicates that insufficient memory has been allocated to Replication Monitor
from the Common Component database memory area. In this case, take action as follows.
6-8-1 Check the Disk Space

Check the amount of space available on the disk on which Replication Monitor is installed. If necessary,
increase the available space by either:
• Deleting unnecessary files
• Transferring data out of the database and re-creating it on another disk
For details on how to transfer database data to another disk, see section 6-8-2 below.
6-8-2 Transferring Data from the Common Component Database

If deleting unnecessary files does not free up enough disk space, then data will need to be transferred from the
Common Component database onto another disk that has more free space.
To transfer data from a Common Component database (for this procedure, it is assumed that the Common
Component service is running):
1. Use the following command to output the contents of the database into files.
®
In Windows :
Common-Component-installation-folder\bin\hcmdsdbmove /export /datapath data-

input-and-output-destination-folder
NOTE: Specify an absolute path for the data input and output destination directory.
2. If other Command View XP AE Suite software is running, terminate any Command View XP AE Suite
software service tasks and Common Component services (HiCommand Suite Common Web Service and
HiCommand Suite Single Sign On Service).
For details on how to terminate other Command View XP AE Suite software services, see the individual
product manuals.
HiCommand Suite Common Web Service and HiCommand Suite Single Sign On Service can be
terminated by executing the following command.
®
In Windows :
3. Execute the following command to create a new database system on the target disk:
In Windows®:
Common-Component-installation-folder\bin\hcmdsdbremake /databasepath new-

database-destination-folder
Messages 177
NOTE: Specify an absolute path for a new database destination directory (or folder) up to 63 bytes.
A file delimiter cannot be specified for the last character in the destination name. If you specify a file
delimiter for the last character, a command error occurs. In such a case, remove the file delimiter, and
then re-execute the command.
NOTE: If you execute the hcmdsdbremake command, the setting for the port number used by the
built-in database HiRDB is changed back to the default (23032). Therefore, when using a port number
other than the default to perform an operation, the port number must be reset after that operation is
complete. For details on how to change the port number, see the manual HP StorageWorks Command
4. Execute the following command to register the database contents from step 1 into the database:
In Windows®:
Common-Component-installation-folder\bin\hcmdsdbmove /import /datapath data-

input-and-output-destination-folder
NOTE: Specify an absolute path for the data input and output destination directory.
6-9 Action for Error Message KAVN01281-E

This section explains the action to be taken when the error message KAVN01281-E is output at installation of a
cluster configuration (standby system). The cause of the output is that the path specified at installation of the
executing system is not a shared disk (no shared disk was specified).
6-9-1-1-1In Windows:
1. If the system is the standby system, switch to the executing system. Before doing this, make sure that the
following services are offline:
• HiCommandServer
If these services are online on the standby system, perform the following procedure to place them offline,
and then switch the system.
1. In the Cluster Administrator window, place the following services offline.
- HiCommandServer
- HiCommand Suite Common Web Service
- HiCommand Suite Single Sign On Service
2. Execute the following command on the standby node:
4. Switch to the executing system.
2. Uninstall Replication Monitor from the executing system.
For details on uninstallation, see section 2-2-3-1 .
3. Re-install Replication Monitor on the executing system. When doing so, specify a shared disk as the
storage destination of the database file.
For details on installation, see section 2-2-1-1 .
4. Install Replication Monitor on the standby system. Specify the same path to the storage destination of the
database file as that on the executing system.
For details on installation, see section 2-2-1-1 .
Messages 178
Appendix A Information Available in System
Configuration Models
The system configuration of the Replication Monitor Web Client determines which types of information can be
displayed and which cannot. This appendix lists the types of information displayed in four typical system
configurations. From section A.2 and onwards, the numbers (1) to (4) shown in the tables indicate the following
system configurations respectively:
(1) Usual configuration
This is the most common configuration. The Device Manager agent and RAID Manager XP are installed
on the hosts.
information collected by hosts can be viewed.
(2) Pair management server and host combined configuration
The Device Manager agent and RAID Manager XP are installed on the pair management server, which is
independent of a host, and manages copy pairs. Only the Device Manager agent is installed on the hosts.
configuration information collected from the pair management server and hosts can be viewed.
(3) Pair management server and host combined (agents not installed on hosts) configuration
Both the Device Manager agent and RAID Manager XP are installed on the pair management server, and
copy pairs are managed independently. Neither RAID Manager XP nor the Device Manager agent is
installed on the hosts.
configuration information collected from the pair management server can be viewed.
(4) Agent-less configuration
Neither RAID Manager XP nor the Device Manager agent is installed on the hosts, and no pair
management server is set up.
Replication Monitor and Device Manager are installed on the management server, and system
configuration information for storage subsystems can be viewed directly.
• When the system configuration is none of the above ((1) to (4)), the system configuration from the
perspective of each copy pair determines which types of information can be displayed by applying the
above patterns ((1) to (4)).
• When the system configuration is (1), (2), or (3) from the above, if the copy pair whose information is to
be displayed has been created without using Device Manager or RAID Manager XP (a copy pair
created by other tools, such as Remote Web Console), the displayed information is the same as
when the system configuration is (4).
System configuration diagrams for each copy function are shown below.
A.1 System Configuration Diagrams

Diagrams of four typical system configurations are shown for each copy function.
A.1.1 Local Copy Configurations

System configurations for local copy functions (Business Copy, Snapshot XP) are shown below:
Appendix A Information Available in System Configuration Models 179

Figure A.1 The Device Manager agent and RAID Manager XP on every host (Local Copy)
Figure A.2 Pair Management Server and Host Combined Configuration (Local Copy)

Figure A.3 Pair management Server and Host Combined (Agents Not Installed on Hosts) Configuration (Local
Copy)
Figure A.4 Agent-Less Configuration (Local Copy)
A.1.2 Continuous Access XP Configurations

System configurations for Continuous Access XP functions (Continuous Access XP or Continuous Access XP
Journal) are shown below:

Figure A.5 The Device Manager agent and RAID Manager XP on every host (Continuous Access XP)
Figure A.6 Pair Management Server and Host Combined Configuration (Continuous Access XP)

Figure A.7 Pair management Server and Host Combined (Agents Not Installed on Hosts) Configuration
(Continuous Access XP)
Figure A.8 Agent-Less Configuration (Continuous Access XP)
A.2 Node Display in Navigation Frame

The table below indicates which subordinate nodes are displayed when nodes are selected with the object tree
in the navigation frame.
Table A.1 Display of Subordinate Nodes When Nodes Are Selected with the Object Tree
Object tree node Subordinate node display
System configuration
Local copy Remote Copy
(1) (2) (3) (4) (1) (2) (3) (4)

Replication Monitor Y Y Y Y Y Y Y Y
+ Hosts Y Y Y Y Y Y Y Y
#1 #1, #1 #1,
+ host-name Y Y Y Y Y Y Y Y
#2 #3
#1 #1, #1 #1,
+ Port/HSD/LUN Y Y Y Y Y Y Y Y
#2 #3
+ Subsystems Y Y Y Y Y Y Y Y
#1, #1,
+ subsystem-name Y Y Y Y Y Y Y Y
#2 #3
#1 #1, #1 #1,
+ Port/HSD/LUN Y Y Y Y Y Y Y Y
#2 #3
+ Pair Configurations Y Y Y Y Y Y Y Y
#4 #4
+ pair-management-server-name Y Y Y -- Y Y Y --
#4 #4 #4 #4
+ RAID Manager XP- Y Y Y -- Y Y Y --
configuration-definition-
file-name
#4 #4 #4 #4
+ copy-group-name Y Y Y -- Y Y Y --
#4 #4 #4 #4
+ pair-name Y Y Y -- Y Y Y --
#4 #4 #4 #4
+ LDEV Y Y Y -- Y Y Y --
LDEV-
numbe
r
Legend:
Y: Can be displayed.
--: Cannot be displayed.
#1. Can be displayed when the host-addition function or LUN Scan function for Device Manager is used to set
the host information.
#2. Can be displayed in StorageWorks XP12000 and StorageWorks XP1024/XP128.
#4. Pair management server information can be displayed (while host information cannot be displayed).
A.3 Information Displayed in the Information Frame or Dialog

Box by Method Selected
The table below indicates which types of information are displayed in the information frame or dialog box when
different methods are selected.
Table A.2 Information Displayed by Method Selected
Object tree node Method name Displayed when method is selected

(1) (2) (3) (4) (1) (2) (3) (4)
Replication Monitor List Objects Y Y Y Y Y Y Y Y
Refresh All Y Y Y Y Y Y Y Y
Show Monitoring Y Y Y Y Y Y Y Y
Configurations
Hosts view
Hosts List Objects Y Y Y Y Y Y Y Y

Table A.2 Information Displayed by Method Selected
Object tree node Method name Displayed when method is selected

(1) (2) (3) (4) (1) (2) (3) (4)
Configurations
host-name List Objects Y Y Y Y Y Y Y Y
Set Monitoring Y Y Y Y Y Y Y Y
Configurations
Refresh Host Y Y Y Y Y Y Y Y
Port/HSD/LUN List Objects Y Y Y Y Y Y Y Y
Refresh Pair Status Y Y Y Y Y Y Y Y
Subsystems view
Subsystems List Objects Y Y Y Y Y Y Y Y
Configurations
subsystem-name List Objects Y Y Y Y Y Y Y Y
Set Monitoring Y Y Y Y Y Y Y Y
Configurations
Refresh Subsystem Y Y Y Y Y Y Y Y
Port/HSD/LUN List Objects Y Y Y Y Y Y Y Y
Refresh Pair Status Y Y Y Y Y Y Y Y
Pair Configurations view
Pair Configurations List Objects Y Y Y -- Y Y Y --
Configurations
pair-management- List Objects Y Y Y -- Y Y Y --
server-
name
RAID Manager XP- List Objects Y Y Y -- Y Y Y --
configuration-
definition-file-name
copy-group-name List Objects Y Y Y -- Y Y Y --
Change Pair Status Y Y Y -- Y Y Y --
Refresh Pair Status Y Y Y -- Y Y Y --
Set Monitoring Y Y Y -- Y Y Y --
Configurations
pair-name List Objects Y Y Y -- Y Y Y --
Change Pair Status Y Y Y -- Y Y Y --
LDEV LDEV-number List Objects Y Y Y -- Y Y Y --
Legend:
A.4 Information Displayed in the Information Frame (Hosts

View)
This appendix indicates the types of information displayed in the information frame, when different nodes are
selected in the Hosts view.
A.4.1Hosts Node
The figure below shows the information frame after selecting the Hosts node in the navigation frame and
clicking on the List Object method in the method frame, while the table indicates which types of information are
displayed.

Figure A.9 List of Hosts
Table A.3 Information Available in Object Table (When the Hosts Node Is Selected)
Item Information frame display

(1) (2) (3) (4) (1) (2) (3) (4)
Host Y Y Y Y Y Y Y Y
#1
Copy Type BC Y Y Y Y N/A N/A N/A N/A
#2
CA- N/A N/A N/A N/A Y Y Y Y
XP(Async)
#2
CA-XP(Sync) N/A N/A N/A N/A Y Y Y Y
#3 #3 #3 #3
Snapshot Y Y Y Y N/A N/A N/A N/A
#4 #4 #4 #4
CA-XP(Jrnl) N/A N/A N/A N/A Y Y Y Y
IP Address Y Y -- -- Y Y -- --
Legend:
N/A: Not applicable.
#3. Can be displayed in StorageWorks XP12000.
A.4.2 host-name Node

The figure below shows the information frame after selecting a host-name node in the navigation frame and
displayed.

Figure A.10 List of Port/HSD/LUNs (Hosts View)
Table A.4 Information Displayed in Object Properties (When a host-name Node Is Selected)

(1) (2) (3) (4) (1) (2) (3) (4)
IP Address Y Y -- -- Y Y -- --
#1
Business Copy XP Y Y Y Y N/A N/A N/A N/A
#2
Continuous Access XP Extension N/A N/A N/A N/A Y Y Y Y
#2
Continuous Access XP N/A N/A N/A N/A Y Y Y Y
#3 #3 #3 #3
Snapshot XP Y Y Y Y N/A N/A N/A N/A
#4 #4 #4 #4
Continuous Access XP Journal N/A N/A N/A N/A Y Y Y Y
Legend:
#1
Can be displayed in StorageWorks XP12000 and StorageWorks XP1024/XP128.
#2
#3
Can be displayed in StorageWorks XP12000.
#4
Table A.5 Information Available in Object Table (When a host-name Node Is Selected)

(1) (2) (3) (4) (1) (2) (3) (4)
#1 #2
Port/HSD/LUN Y Y Y Y Y Y Y Y
#1
#2
CA-XP(Async) N/A N/A N/A N/A Y Y Y Y
#2
#3 #3 #3 #3
#4 #4 #4 #4

Table A.5 Information Available in Object Table (When a host-name Node Is Selected)

(1) (2) (3) (4) (1) (2) (3) (4)
Mount Point Y Y -- -- Y Y -- --
#1 #2
Subsystem Y Y Y Y Y Y Y Y
#4 #4 #4 #4 #4 #4 #4 #4
SLPR Y Y Y Y Y Y Y Y
#5 #5 #5 #5 #5 #5 #5 #5
CLPR Y Y Y Y Y Y Y Y
#1 #2
Capacity Y Y Y Y Y Y Y Y
Legend:
A.4.3Port/HSD/LUN Node
The figure below shows the information frame after selecting the Port/HSD/LUN node in the navigation frame
and clicking on the List Object method in the method frame, while the table indicates which types of information
are displayed.
Figure A.11 List of Copy Pairs (Hosts View)

Table A.6 Information Available in Object Properties (Upper) (When a Port/HSD/LUN Node Is
Selected in the Hosts View)

(1) (2) (3) (4) (1) (2) (3) (4)
#1
Business Copy XP Y Y Y Y N/A N/A N/A N/A
#2
#2
#3 #3 #3 #3
#4 #4 #4 #4

Legend:
#1
#2
#3
#4
Table A.7 Information Available in Object Properties (Lower) (When a Port/HSD/LUN Node Is
Selected in the Hosts View)

(1) (2) (3) (4) (1) (2) (3) (4)
#1 #2
RAID Level Y Y Y Y Y Y Y Y
#3 #3 #3 #1, #3 #3 #3 #3 #2, #3
Emulation Type Y Y Y Y Y Y Y Y
#1 #2
Volume Attribute Y Y Y Y Y Y Y Y
#1 #2
Legend:
#1
#2
#3
Can be displayed in StorageWorks XP12000, StorageWorks XP1024/XP128, and StorageWorks
XP512/XP48.
Table A.8 Information Available in Object Table (When a Port/HSD/LUN Node Is Selected in the
Hosts View)

(1) (2) (3) (4) (1) (2) (3) (4)
#1 #2
Pair Y Y Y Y Y Y Y Y
Configurations
#1 #2
Copy Type Y Y Y Y Y Y Y Y
#1 #2
Copy Status Y Y Y Y Y Y Y Y
#1 #2
Detailed Copy Y Y Y Y Y Y Y Y
Status
#1 #2
Primary LDEV Y Y Y Y Y Y Y Y
#1 #2
Pair Y Y Y -- Y Y Y --
Management
Server
Config File Y Y Y -- Y Y Y --
Hosts View)

(1) (2) (3) (4) (1) (2) (3) (4)
Name
#1 #2
Secondary LDEV Y Y Y Y Y Y Y Y
#1 #2
Management
Server
Name
Copy Group Y Y Y -- Y Y Y --
Pair Name Y Y Y -- Y Y Y --
Action Y Y Y Y Y Y Y Y
Legend:
#1
#2
A.5 Information Displayed in the Information Frame

(Subsystems View)
selected in the Subsystems view.
A.5.1 Subsystems Node

The figure below shows the information frame after selecting the Subsystems node in the navigation frame and
displayed.
Figure A.12 List of Storage Subsystems

Table A.9 Information Available in Object Table (When the Subsystems Node Is Selected)

(1) (2) (3) (4) (1) (2) (3) (4)
#1
#2
CA- N/A N/A N/A N/A Y Y Y Y

Table A.9 Information Available in Object Table (When the Subsystems Node Is Selected)

(1) (2) (3) (4) (1) (2) (3) (4)
XP(Async)
#2
#3 #3 #3 #3
#4 #4 #4 #4
#1 #2
Type
#1 #2
RAW Y Y Y Y Y Y Y Y
Capacity
#1 #2
Allocated Y Y Y Y Y Y Y Y
Capacity
#1 #2
Cache Size Y Y Y Y Y Y Y Y
Legend:
A.5.2 subsystem-name Node

The figure below shows the information frame after selecting a subsystem-name node in the navigation frame
are displayed.
Figure A.13 List of Port/HSD/LUNs (Subsystems View)

Table A.10 Information Available in Object Properties (When a subsystem-name Node Is
Selected)

(1) (2) (3) (4) (1) (2) (3) (4)
#1 #2
Subsystem Type Y Y Y Y Y Y Y Y
#1 #2
RAW Capacity Y Y Y Y Y Y Y Y
#1 #2
Allocated Capacity Y Y Y Y Y Y Y Y
#1 #2
Cache Size Y Y Y Y Y Y Y Y
#1
Business Copy Y Y Y Y N/A N/A N/A N/A
#2
#2
#3 #3 #3 #3
#4 #4 #4 #4
Legend:
#1
Can be displayed in StorageWorks XP12000 and StorageWorks XP1024/XP128
#2
Can be displayed in StorageWorks XP12000 and StorageWorks XP1024.
#3
#4
Table A.11 Information Available in Object Table (When a subsystem-name Node Is Selected)

(1) (2) (3) (4) (1) (2) (3) (4)
#1 #2
Port/HSD/LUN Y Y Y Y Y Y Y Y
#1
#2
CA-XP(Async) N/A N/A N/A N/A Y Y Y Y
#2
#3 #3 #3 #3
#4 #4 #4 #4
#4 #4 #4 #4 #4 #4 #4 #4
SLPR Y Y Y Y Y Y Y Y
#5 #5 #5 #5 #5 #5 #5 #5
CLPR Y Y Y Y Y Y Y Y
#1 #2
Legend:
#1. Can be displayed in StorageWorks XP12000 and StorageWorks XP1024.
#2. Can be displayed in StorageWorks XP12000 and StorageWorks XP1024.

A.5.3 Port/HSD/LUN Node
The figure below shows the information frame after selecting the Port/HSD/LUN node in the navigation frame
are displayed.
Figure A.14 List of Copy Pairs (Subsystems View)

Table A.12 Information Available in Object Properties (Upper) (When a Port/HSD/LUN Node Is
Selected in the Subsystems View)

(1) (2) (3) (4) (1) (2) (3) (4)
#1 #2
#1
Business Copy Y Y Y Y N/A N/A N/A N/A
#2
#2
#3 #3 #3 #3
#4 #4 #4 #4
Legend:
#1
#2
#3
#4
Can be displayed in StorageWorks XP12000/XP10000.
Table A.13 Information Available in Object Properties (Lower) (When a Port/HSD/LUN Node Is
Selected in the Subsystems View)

(1) (2) (3) (4) (1) (2) (3) (4)
#1 #2
RAID Level Y Y Y Y Y Y Y Y
#3 #3 #3 #1, #3 #3 #3 #3 #2, #3
Emulation Type Y Y Y Y Y Y Y Y
#1, #2,
Volume Attribute Y Y Y Y Y Y Y Y
#1, #2,
Legend:
#1
Can be displayed StorageWorks XP12000 and StorageWorks XP1024.
#2
#3
XP512/XP48.
Subsystems View)

(1) (2) (3) (4) (1) (2) (3) (4)
#1 #2,
Pair Y Y Y Y Y Y Y Y
Configurations
#1 #2,
Copy Type Y Y Y Y Y Y Y Y
#1 #2,
Copy Status Y Y Y Y Y Y Y Y
#1 #2,
Detailed Copy Y Y Y Y Y Y Y Y
Status
#1 #2,
Primary LDEV Y Y Y Y Y Y Y Y
#1 #2,
Management
Server
Name
#1 #2,
Secondary LDEV Y Y Y Y Y Y Y Y
#1 #2,
Management
Server
Name
Action Y Y Y Y Y Y Y Y
Legend:
#1
#2
Can be displayed in StorageWorks XP12000, StorageWorks XP1024/XP128.

A.6 Information Displayed in the Information Frame (Pair
Configurations View)
selected in the Pair Configurations view.
A.6.1 Pair Configurations Node

The figure below shows the information frame after selecting the Pair Configurations node in the navigation
frame, while the table indicates which types of information are displayed.
Figure A.15 List of Pair Management Servers

Table A.15 Information Available in Object Table (When the Pair Configurations Node Is Selected)

(1) (2) (3) (4) (1) (2) (3) (4)
Management
Server
Copy Type BC Y Y Y -- N/A N/A N/A N/A
CA- N/A N/A N/A N/A Y Y Y --
XP(Async)
CA-XP(Sync) N/A N/A N/A N/A Y Y Y --
#1 #1 #1
Snapshot Y Y Y -- N/A N/A N/A N/A
#2 #2 #2
CA-XP(Jrnl) N/A N/A N/A N/A Y Y Y --
IP Address Y Y Y -- Y Y Y --
Legend:
A.6.2 pair-management-server Node

The figure below shows the information frame after expanding Pair Configurations and selecting a pair-
management-server-name under Pair Configurations in the navigation frame, while the table indicates which
types of information are displayed.

Figure A.16 List of RAID Manager XP Configuration Definition Files
Table A.16 Information Available in Object Properties (When a pair-management-server-name
Node Is Selected)

(1) (2) (3) (4) (1) (2) (3) (4)
Business Copy Y Y Y -- N/A N/A N/A N/A
Continuous Access XP N/A N/A N/A N/A Y Y Y --
Extension
#1 #1 #1
Snapshot XP Y Y Y -- N/A N/A N/A N/A
#2 #2 #2
Journal
Legend:
#1
#2
Table A.17 Information Available in Object Table (When a pair-management-server-name Node Is

Selected)

(1) (2) (3) (4) (1) (2) (3) (4)

Table A.17 Information Available in Object Table (When a pair-management-server-name Node Is
Selected)

(1) (2) (3) (4) (1) (2) (3) (4)
Config File Name Y Y Y -- Y Y Y --
CA- N/A N/A N/A N/A Y Y Y --
XP(Async)
#1 #1 #1
#2 #2 #2
CA-XP(Jrnl) N/A N/A N/A N/A Y Y Y N/A
Port Y Y Y -- Y Y Y --
Legend:
A.6.3 RAID Manager XP-configuration-definition-file-name Node

The figure below shows the information frame after expanding Pair Configurations and selecting a RAID
Manager XP-configuration-definition-file-name node under Pair Configurations in the navigation frame, while
the table indicates which types of information are displayed.
Figure A.17 List of Copy Groups

Table A.18 Information Available in Object Properties (When a RAID Manager XP-configuration-
definition-file-name Node Is Selected)

(1) (2) (3) (4) (1) (2) (3) (4)
Extension
#1 #1 #1
#2 #2 #2
Journal
Legend:
#1
#2
Table A.19 Information Available in Object Table (When a RAID Manager XP-configuration-
definition-file-name Node Is Selected)

(1) (2) (3) (4) (1) (2) (3) (4)
Copy Group Name Y Y Y -- Y Y Y --
CA-XP(Async) N/A N/A N/A N/A Y Y Y --
#1 #1 #1
#2 #2 #2
CA-XP(Jrnl) N/A N/A N/A N/A Y Y Y --
Paired Pair Y Y Y -- Y Y Y --
Information Management
Server
Legend:
A.6.4 copy-group-name Node

The figure below shows the information frame when a copy-group node is selected in the navigation frame,
while the table indicates which types of information are displayed.

Figure A.18 List of Copy Pairs (Pair Configurations View)
Table A.20 Information Available in Object Properties (When a copy-group-name Node Is
Selected)
Label Information frame display

(1) (2) (3) (4) (1) (2) (3) (4)
Pair Management Server Y Y Y -- Y Y Y --
Extension
#1 #1 #1
#2 #2 #2
Journal
Legend:
#1
#2
Table A.21 Information Available in Object Table (When a copy-group-name Node Is Selected)

(1) (2) (3) (4) (1) (2) (3) (4)

Table A.21 Information Available in Object Table (When a copy-group-name Node Is Selected)

(1) (2) (3) (4) (1) (2) (3) (4)
Copy Type Y Y Y -- Y Y Y --
Copy Y Y Y -- Y Y Y --
Status
Primary LDEV Y Y Y -- Y Y Y --
Subsystems Y Y Y -- Y Y Y --
Secondary LDEV Y Y Y -- Y Y Y --
Subsystems Y Y Y -- Y Y Y --
#1 #1 #1
MU# Y Y Y -- Y Y Y --
Legend:
A.6.5 pair-name Node

The figure below shows the information frame when a copy-pair node is selected in the navigation frame, while
the table indicates which types of information are displayed.
Figure A.19 List of LDEVs Comprising the Copy Pair

Table A.22 Information Available in Object Properties (When a pair-name Node Is Selected)

(1) (2) (3) (4) (1) (2) (3) (4)
Volume

Table A.22 Information Available in Object Properties (When a pair-name Node Is Selected)

(1) (2) (3) (4) (1) (2) (3) (4)
Subsystem Y Y Y -- Y Y Y --
Volume
#1 #1 #1
MU# Y Y Y -- Y Y Y --
Continuous Access XP Extension N/A N/A N/A N/A Y Y Y --
#2 #2 #2
#1 #1 #1
Continuous Access XP Journal N/A N/A N/A N/A Y Y Y --
Legend:
#1
#2
Table A.23 Information Available in Object Table (When a pair-name Node Is Selected)

(1) (2) (3) (4) (1) (2) (3) (4)
LDEV Y Y Y -- Y Y Y --
Capacity Y Y Y -- Y Y Y --
RAID Level Y Y Y -- Y Y Y --
#1 #1 #1 #1 #1 #1
Emulation Y Y Y -- Y Y Y --
Type
Volume Y Y Y -- Y Y Y --
Attribute
Legend:
#1
Can be displayed in StorageWorks XP12000, StorageWorks XP1024/XP128 and StorageWorks
XP512/XP48.
A.6.6 LDEV LDEV-number Node

The figure below shows the information frame when an LDEV LDEV-name node is selected in the navigation
frame, while the table indicates which types of information are displayed.

Figure A.20 List of Copy Pairs That are in a Cascade Configuration (Pair Configurations View)
Table A.24 Information Available in Object Properties (When an LDEV LDEV-number Node Is
Selected)

(1) (2) (3) (4) (1) (2) (3) (4)
Capacity Y Y Y -- Y Y Y --
RAID Level Y Y Y -- Y Y Y --
#1 #1 #1 #1 #1 #1
Emulation Type Y Y Y -- Y Y Y --
Volume Attribute Y Y Y -- Y Y Y --
Legend:
#1
XP512/XP48.
Table A.25 Information Available in Object Table (When an LDEV LDEV-number Node Is
Selected)

(1) (2) (3) (4) (1) (2) (3) (4)
Configurations
Copy Type Y Y Y -- Y Y Y --
Copy Status Y Y Y -- Y Y Y --
Detailed Copy Y Y Y -- Y Y Y --
Status
Management
Server
Name
Management
Server
Name

Table A.25 Information Available in Object Table (When an LDEV LDEV-number Node Is
Selected)

(1) (2) (3) (4) (1) (2) (3) (4)
Action Y Y Y -- Y Y Y --
Legend:

Appendix B Glossary
application server The machine on which application programs are installed. Also referred to as the host. The
host treats the storage subsystem as an external storage device. To view host information in
Replication Monitor, Device Manager Agent and RAID Manager XP must be installed on the
relevant host(s).
batch collection Software that collects necessary information such as log files and property files, related to a
command for problem that cannot be resolved at the user level, for forwarding on to technical support.
maintenance
information
Business Copy Software provided by the storage subsystem, used to duplicate volumes within the same
storage subsystem. For more information, see the Business Copy manual.
cascade structure A structure of consecutive copy pairs. In a cascade structure, the secondary volume of a
given copy pair coincides with the primary volume of another copy pair. This volume is called
the secondary/primary volume (SP-VOL).
cluster software Software that uses system multiplexing to boost overall availability in the system. When
cluster software is installed in the Replication Monitor operating environment, in the event of
a problem on the management server, Replication Monitor services will be transferred to an
alternate server.
Continuous Access Software provided by the storage subsystem, used to duplicate volumes between storage
XP subsystems. For more information, see the Continuous Access XP manual.
Continuous Access Software provided by the storage subsystem and used to asynchronously duplicate volumes
XP Journal between storage subsystems. For more information, see the Continuous Access XP Journal
manual.
copy group A group of multiple copy pairs. Operations such as pair status modification apply to all copy
pairs in the group.
copy pair Denotes a primary and secondary volume pair linked by the volume replication function of
the storage subsystem. Also known as a pair volume. In this manual, copy pair is sometimes
written simply as pair.
Device Manager Software used for the operation and/or management of a system that uses differing storage
subsystem types. Replication Monitor obtains required information (such as pair
configuration and pair status) by accessing the system configuration information held by
Device Manager.
failover The process of automatically switching to the reserve system, in the event of a problem in a
system that has been multiplexed using cluster software.
HP Command A package of standard features used by all Command View XP AE Suite software, including
View XP AE Suite login, output log and web services. Installed as part of Replication Monitor. For details, see
Common 1.4.1 Command View XP AE Suite Common Component.
Component
HiCommand Suite A log file for detailed information on events such as server startup. Used to check errors that
common log file occur during Replication Monitor operation.
host The machine on which application programs are installed. Also referred to as the application
server. The host treats the storage subsystem as an external storage device. To view host
information in Replication Monitor, Device Manager Agent and RAID Manager XP must be
installed on the relevant host(s).
installation related A log file of detailed processing information generated during installation and uninstallation of
trace log file Replication Monitor. Used to trace the source of errors that occur during installation and
uninstallation.
LDEV A logical device in the storage subsystem.
LU A logical unit in the storage subsystem. The host utilizes storage devices in the storage
subsystem by mounting LUs. Also called volumes.
Appendix B
LUN The number used to map the LU (or volume) in the storage subsystem.
management client The machine on which the Replication Monitor Web Client is executed. Issues instructions to
Replication Monitor on the management server for basic Replication Monitor operations,
such as pair configuration browsing, pair status monitoring and pair status modification.
management The machine on which Replication Monitor and its prerequisite program, Device Manager
server Server, are installed. Requests system configuration information from all hosts, and provides
this information to management clients.
monitoring Settings for using Replication Monitor to monitor copy pairs and execute an action if
configurations specified check conditions are satisfied. A monitoring configuration of Replication Monitor
has three components: the monitoring target, check conditions, and action definition.
most significant By displaying only the most significant copy pair status in the upper levels that contain the
pair status, copy pairs (such as at the host level from the host perspective, or at the storage subsystem
displaying level from the subsystem perspective), Replication Monitor allows viewers to quickly check
copy pair status. Replication Monitor determines the most significant copy pair status for
each copy function (such as Business Copy and Continuous Access XP) in turn.
pair In this manual, pair means copy pair.
pair management A server for collecting system information. Device Manager Agent and RAID Manager XP
server are installed on the pair management server.
Once a pair management server, which is independent of the host, is installed, the pair
management server assumes responsibility for obtaining system information, thereby
reducing the load on the host. However, there are certain types of information that cannot be
obtained by the pair management server.
pair status Indicates the current status of the copy pair. Replication Monitor uses four status values:
error, suspend, copying, and sync.
paired volume Denotes a primary and secondary volume pair linked by the volume replication function of
the storage subsystem. Also known as a copy pair. In this manual, copy pair is sometimes
written simply as pair.
primary volume (P- The source volume that is copied to another volume using the volume replication function of
VOL) the storage subsystem.
property files Generic term for the files that define the Replication Monitor operating environment. The
Replication Monitor operating environment can be modified by changing the appropriate
property files.
RAID Manager XP Control software for the StorageWorks XP1204/XP128 and XP512/XP48 series, used to
control storage subsystem volume duplication features (such as Continuous Access XP and
Business Copy) by issuing commands from the host to the storage subsystem, and also
used for gathering pair configuration information from the storage subsystem. For details on
RAID Manager XP, see the RAID Manager XP manual.
In Replication Monitor, storage subsystem information is gathered by controlling RAID
Manager XP via the Device Manager Server or Device Manager Agent.
secondary-primary The volume located in the middle of the cascade structure, when a cascade structure is used
volume (SP-VOL) by the volume replication function of the storage subsystem. Indicates the secondary volume
in an upper level copy pair and the primary volume in a lower level copy pair.
secondary volume The destination volume to which the primary volume is copied using the volume replication
(S-VOL) function of the storage subsystem.
Snapshot XP Software provided by the storage subsystem, used to duplicate volumes within the same
storage subsystem. For more information, see the Snapshot XP manual.
storage subsystem An external storage device connected to the host. Storage subsystems supported by
Replication Monitor are of the StorageWorks XP Disk Array.
subsystem An external storage device (storage subsystem) connected to the host. In this manual,
subsystem means storage subsystem.
Appendix B
system Generic term for the following information collected by Replication Monitor:
configuration
• Host configuration information
information
• Subsystem configuration information
• RAID Manager XP configuration definition file information
• Copy group configuration
• Copy pair configuration and pair status
• Information for LDEVs that configure copy pairs
trace log file A log file containing detailed program processing information, used to analyze program
processing in the event of an error during Replication Monitor operation.
volume A logical unit in the storage subsystem. The host utilizes storage devices in the storage
subsystem by mounting volumes. Also called LUs.
volume replication Generic term used in this manual to refer to high-speed volume replication functions in the
functions storage subsystem (such as Business Copy and Continuous Access XP). The mirror control
function provided by the storage subsystem can be used to quickly create a replica of the
volume without passing through the LAN.
Appendix B
Index
determining the most significant pair installation related trace log file, 132,
A status: rules for, 73 136
Device Manager, 25 integrated trace log file, 132
action, 18 dialog box: copy status icon, 89;
action for detailed message RPM- Web Client, 88 J
00824, 183 displaying: most significant pair
application server, 19 status, 75 jump button, 84
applied example of Replication displaying cascaded copy pairs, 91
Monitor, 26 displaying multiple items of
information for particular node, 93 K
automatic refresh, 17
E key terms, 13
B
environment setting command, 64 L
backing up operating environment
information, 66 environment settings, 51
error and warning messages, 93 language: Web Client, 92
BC, 25 LDEV, 13
Business Copy, 25 error countermeasure procedure,
133 license key, 128
error countermeasures, 132 log file: event log file, 132;
C error message displayed in installation related trace log file,
information frame, 93 132; integrated trace log file, 132;
calling Device Manager, 127 error message in dialog box, 94 trace log file, 132; Version
calling different Command View XP event log file, 132 information log files, 132
AE Suite software, 79 executing node (Windows): log file produced from Replication
calling operation: calling replication specifying cluster environment Monitor, 132
monitor from different Command settings, 57 log Information: collecting for install
View XP AE Suite software, 79 and uninstall errors, 136
CA-XP(Async), 25 F log information for Common
CA-XP(Jrnl), 25 Component command execution,
CA-XP(Sync), 25 136
changing pair status, 120; changing function: Web Client, 71 LU, 13
copy pace, 122; note, 127; when LUN, 14
target is copy group, 120; when G
target is copy pair, 121 M
check condition, 18 glossary: key terms, 13
cluster environments: requirements main window: Web Client, 80
for, 56 H maintenance information batch
collecting log information for install collection commands, 133
and uninstall errors, 136 hardware comprising system, 19 management client, 19
Command View XP AE Suite hcmdsbackups command, 66 management server, 19
Common Component, 24, 25 hcmdsdb command, 68 manual refresh, 17
commands: maintenance host, 19 menu-bar frame, 80
information batch collection, 133 Hosts view, 14 messages: detailed messages, 136,
component for system using hrpmsetup command, 64 171; of Replication Monitor, 135;
Replication Monitor, 19 other messages, 136; types and
configuration: Web Client window, formats, 135
80 I
method frame, 85
confirming and operating on pair monitoring and notification of a pair
status: Hosts view, 109; Pair icon: Web Client window, 88
icon in information frame and dialog statuses, 72
Configurations view, 115; monitoring and notifying pair status:
subsystems view, 112 box, 89
icon in object tree, 88 items to be set as monitoring
Continuous Access XP, 25 configurations, 72; notified details,
Continuous Access XP Journal, 25 identifying error location, 107
information available in system 74
copy group, 14 monitoring configurations: action,
copy pair, 14 configuration model: system
configuration diagrams, 186 18; adding, 99; check condition,
copy status icon, 89 18; check conditions, 95;
cvxpaegetlogs, 133 information displayed in information
frame (hosts view), 192 considerations before setting
information displayed in information monitoring configurations, 97;
D deleting, 105; editing, 102; email
frame (Pair Configurations view),
202 information, 95; items set, 72;
databases: restoring, 68 information displayed in information monitoring target, 18, 95; setting,
detailed message, 136 frame (Subsystems view), 197 95
detailed messages, 171 information displayed in information monitoring target, 18
determining: most significant pair frame or dialog box by method
status, 75 selected, 191 N
determining and displaying the most information frame, 86; copy status
significant pair status, 16 icon, 89; object table icon, 90 navigation frame, 81
Index 207
necessary components for system, Replication Monitor: checking system configuration model of
19 operation status, 63; log files, 132; system using Replication Monitor,
new installation: Windows, 34 starting, 62, 63; terminating, 62, 20
node display in navigation frame, 63 system configuration models, 18;
190 Replication Monitor feature, 12 agent-less configuration, 23;
note on operating Replication Replication Monitor function, 14; overview, 20; pair management
Monitor, 90 changing status of copy pair, 18; server and host combined (agents
notes: changing storage subsystem checking status of copy pair, 14; not installed on hosts)
configuration, 91; operating Web monitoring copy pair, 17; setting configuration, 22; pair
Client, 90 up copy pair, 18 management server and host
Replication Monitor messages, 135 combined configuration, 21
O Replication Monitor overview, 12 system configuration using
Replication Monitor security Replication Monitor, 18
object table icon, 90 management, 129 system requirements: Windows, 33
object tree, 81 restoring database, 68
operating environment: parameter RPM-00824: action for, 183 T
list, 51; prerequisites, 51; setting
Up, 51 S target user, 13
operating environment information: terminating operation, 79; Close, 79;
backing up, 66 secondary - primary volume, 14 Logout, 79
operation, 71 secondary volume, 14 terminating Replication Monitor, 63
operation management software for security: access security to Device trace log file, 132
storage subsystems, 25 Manager server, 130; inheriting troubleshooting, 132; installing in
other messages, 136 user permissions in link-and- Windows, 44; uninstalling in
launch operation, 129; necessary Windows, 44
P user permissions for login, 129;
network access, 130 U
Pair Configurations view, 15 setting up: prerequisites, 51
pair management server, 19 setting up: operating environment, uninstalling: Windows, 43
pair status: most significant, 75 51 upgrading installation: Windows, 40
pair status change procedure: when significant pair status: determining
changing pair status of copy and displaying, 75
Single Sign-On, 24 V
group, 122; when changing pair
status of copy pair, 124 SN, 25
Snapshot XP, 25 view selection, 14
pair status type, 16 volume, 13
parameters: related to database software comprising system, 19
software provided by storage volume replication function, 214
connections, 54; related to Device
Manager, 52; related to subsystem, 25
information acquisition interface, software related to volume W
56; related to log output, 55 replication functionality, 25
primary volume, 14 SP-VOL, 14, 213 warning message, 95
program related to Replication standby node (Windows): specifying Web Client: dialog box, 88;
Monitor, 24 cluster environment settings, 59 displayed item, 80; displayed
P-VOL, 14, 213 starting and terminating: Web Client, language, 92; function, 71; main
78 window, 80; notes on operation,
starting operation, 78; enter your 90; starting, 78; terminating, 78;
R user ID and password to log in, 78 window configuration, 80
starting Replication Monitor, 63 Web Client window: icon, 88
RAID Manager, 25 storage administrator, 13 Windows: new installation, 34; re-
refresh, 17, 85 storage subsystem, 20; notes on installing, 40; system
refresh function: notes on operating, changing configuration, 91 requirements, 33; uninstalling, 43;
130 storage subsystem volume upgrading installation, 40
registering and viewing license replication functionality, 14
information, 128 S-VOL, 14, 213
related program, 24 system administrator, 13
Index 208

XP12000 Replication Monitor Rootsan Technologies PVT LTD

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

XP12000 Replication Monitor Rootsan Technologies PVT LTD

Uploaded by

Copyright:

Available Formats

HP StorageWorks XP Replication Monitor

Part number: TI784-96001

First edition: November, 2005

Netscape is a registed trademark of Netscape Communications Corporation.

HP StorageWorks XP Replication Monitor User Guide

Part number: TI784-96001

Document conventions and symbols

Convention Element Convention Element

Medium blue text: Figure 1 Cross-reference links and e-mail addresses

Medium blue, underlined text Web site addresses

Bold font • Key names

italics font Text emphasis

Monospace font • File and directory names

Monospace, italic font • Code variables

IMPORTANT: Provides clarifying information or specific instructions.

About this guide 9

TIP: Provides helpful hints and shortcuts.

Helpful web sites

About this guide 10

Date Edition Revision

November, 2005 First Initial release

1-1 Replication Monitor Overview

1-1-1 Replication Monitor Features

Overview of Replication Monitor 12

1-1-2 Target Users

1-1-3 Key Terms

Overview of Replication Monitor 13

1-2 Replication Monitor Functions

1-2-1 Checking the Status of a Copy Pair

1-2-1-1 View Selection

Overview of Replication Monitor 14

Overview of Replication Monitor 15

Table 1-1 Types of Pair Statuses

Pair status Description Status of Device Manager pair Priority

Overview of Replication Monitor 16

Table 1-2 Refresh Functions by Type and Applied Range

Refresh type Applied range

1-2-2 Monitoring a Copy Pair

Overview of Replication Monitor 17

1-2-3 Changing the Status of a Copy Pair

Figure 1-6 Example of Changing the Status of a Copy Pair

1-2-4 Setting Up a Copy Pair

1-3 System Configuration Using Replication Monitor

1-3-1 Components for Systems Using Replication Monitor

Overview of Replication Monitor 18

1-3-1-2 Hardware Comprising the System

1-3-1-3 Control and Data Flow

Overview of Replication Monitor 19

1-3-2 System Configuration Models of Systems Using Replication Monitor

1-3-2-1 Usual Configuration

Overview of Replication Monitor 20

1-3-2-2 Pair Management Server and Host Combined Configuration

Overview of Replication Monitor 21

Overview of Replication Monitor 22

1-3-2-4 Agent-Less Configuration

Overview of Replication Monitor 23

1-3-2-5 Note on System Configuration

1-4 Programs Related to Replication Monitor

1-4-1 Command View XP AE Suite Common Component

Overview of Replication Monitor 24

1-4-2 Device Manager

1-4-3 Software Provided by Storage Subsystems