XP12000 Replication Monitor Rootsan technologies Pvt Ltd

8/6/2019 XP12000 Replication Monitor Rootsan technologies Pvt Ltd

1/208

HP StorageWorks XP Replication Monitor

User Guide

Part number: TI784-96001

First edition: November, 2005


2/208

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


3/208

Contents 3

Contents

Revision history (start here)Revision tables ..................................................................................................................................................... 11

1 Overview of Replication Monitor1-1 Replication Monitor Overview.................................................................................................................... 12

1-1-1 Replication Monitor Features.......................................................................................................... 12

1-1-2 Target Users................................................................................................................................... 131-1-3 Key Terms...................................................................................................................................... 131-2 Replication Monitor Functions ................................................................................................................... 14

1-2-1 Checking the Status of a Copy Pair................................................................................................ 141-2-2 Monitoring a Copy Pair ................................................................................................................... 171-2-3 Changing the Status of a Copy Pair ............................................................................................... 181-2-4 Setting Up a Copy Pair ................................................................................................................... 18

1-3 System Configuration Using Replication Monitor ...................................................................................... 181-3-1 Components for Systems Using Replication Monitor ..................................................................... 181-3-2 System Configuration Models of Systems Using Replication Monitor............................................ 20

1-4 Programs Related to Replication Monitor.................................................................................................. 241-4-1 Command View XP AE Suite Common Component ...................................................................... 241-4-2 Device Manager ............................................................................................................................. 251-4-3 Software Provided by Storage Subsystems ................................................................................... 25

1-5 Applied Examples for Replication Monitor................................................................................................. 261-5-1 Example 1: Resolving Problems from the Storage Subsystem Perspective .................................. 261-5-2 Example 2: Resolving Problems from the Host Perspective .......................................................... 29

2 Installation and Uninstallation2-1 Installation and Uninstallation in Windows.............................................................................................. 33

2-1-1 System Requirements .................................................................................................................... 332-1-2 Installing Replication Monitor.......................................................................................................... 342-1-3 Upgrading or Re-installing Replication Monitor .............................................................................. 392-1-4 Uninstalling Replication Monitor ..................................................................................................... 422-1-5 Troubleshooting in Installation and Uninstallation.......................................................................... 43

2-2 Installation and Uninstallation in a Cluster Environment ........................................................................... 452-2-1 Installation ...................................................................................................................................... 452-2-2 Upgrade Installation and Re-installation......................................................................................... 472-2-3 Uninstallation.................................................................................................................................. 48

2-3 Notes on Installation and Uninstallation .................................................................................................... 492-3-1 Notes on Uninstalling Device Manager .......................................................................................... 492-3-2 Notes on Stopping Command View XP AE Suite software Services and Daemons...................... 49

3 Environment Settings3-1 Setting Up the Operating Environment...................................................................................................... 50

3-1-1 Prerequisites for Setting Up an Operating Environment................................................................. 503-1-2 Parameters Required for Operating Replication Monitor................................................................ 50

3-2 Building a Cluster Configuration Environment........................................................................................... 553-2-1 Specifying Cluster Environment Settings in the Executing Node (When Using MSCS)................. 553-2-2 Specifying Cluster Environment Settings in the Standby Node (When Using MSCS) ................... 583-2-3 Troubleshooting for Building a Cluster Environment ...................................................................... 603-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 ........................................................................................................... 613-3-2 Terminating Replication Monitor..................................................................................................... 623-3-3 Checking Operation Status of Replication Monitor......................................................................... 62

3-4 Environment Setting Command ................................................................................................................ 633-4-1 Setting or Viewing the Parameters Related to Device Manager .................................................... 63

3-5 Backing Up Operating Environment Information....................................................................................... 653-5-1 Backing Up Operating Environment Information ............................................................................ 653-5-2 Restoring Databases...................................................................................................................... 66

3-6 Changing the Host Name for the Management Server ............................................................................. 67

4 Operation4-1 Functions of Web Client ............................................................................................................................ 70

4-1-1 Monitoring and Notification of a Pair Status ................................................................................... 714-1-2 Determining and Displaying the Most Significant Pair Status......................................................... 74


4/208

Contents 4

4-2 Starting and Terminating Web Client ........................................................................................................ 774-2-1 Starting Operation of Web Client.................................................................................................... 774-2-2 Terminating Operation of Replication Monitor................................................................................ 784-2-3 Calling a Different Command View XP AE Suite software ............................................................. 78

4-3 Window Configuration and Displayed Items of Web Client ....................................................................... 784-3-1 Configuration of Web Client's Main Window .................................................................................. 794-3-2 Web Client Dialog Boxes................................................................................................................ 864-3-3 Icons Displayed in the Web Client Window.................................................................................... 874-3-4 Notes on Replication Monitor Operations....................................................................................... 894-3-5 Displaying Cascaded Copy Pairs ................................................................................................... 90

4-3-6 Languages Displayed While Web Client Is Operating.................................................................... 914-3-7 Displaying Multiple Items of Information for a Particular Node....................................................... 914-3-8 Error and Warning Messages......................................................................................................... 92

4-4 Setting a Monitoring Configuration ............................................................................................................ 944-4-1 Considerations before Setting Monitoring Configurations .............................................................. 964-4-2 Adding, Editing and Deleting Monitoring Configurations ................................................................ 98

4-5 Identifying an Error Location ................................................................................................................... 1064-5-1 Confirming and Operating on a Pair Status Using the Hosts View............................................... 1074-5-2 Confirming and Operating on a Pair Status Using the Subsystems View .................................... 1104-5-3 Confirming and Operating on a Pair Status Using the Pair Configurations View .........................113

4-6 Changing a Pair Status ........................................................................................................................... 1184-6-1 Changing a Status........................................................................................................................ 1184-6-2 Changing the Copy Pace.............................................................................................................. 1194-6-3 Pair Status Changing Procedure.................................................................................................. 120

4-6-4 Notes on Changing a Pair Status ................................................................................................. 1254-7 Calling Device Manager .......................................................................................................................... 1254-8 Registering and Viewing License Information ......................................................................................... 126

4-8-1 License Key.................................................................................................................................. 1264-8-2 Registering and Viewing License Information .............................................................................. 126

4-9 Replication Monitor Security Management.............................................................................................. 1274-9-1 Necessary User Permissions for Login ........................................................................................ 1274-9-2 Inheriting User Permissions in Link-and-Launch Operations ....................................................... 1274-9-3 Access Security for the Device Manager Server .......................................................................... 1284-9-4 Network Access Security.............................................................................................................. 128

4-10 Notes on Operating the Refresh Function.................................................................................... 128

5 Troubleshooting5-1 Error Countermeasures........................................................................................................................... 130

5-1-1 Log File Output from Replication Monitor..................................................................................... 1305-1-2 Error Countermeasure Procedure ................................................................................................ 1305-1-3 Maintenance Information Batch Collection Command ................................................................. 131

6 Messages6-1 Message Types and Formats.................................................................................................................. 133

6-1-1 Replication Monitor Messages ..................................................................................................... 1336-1-2 Detailed Messages....................................................................................................................... 1346-1-3 Other Messages ........................................................................................................................... 1346-1-4 Collecting Log Information for Installation and Uninstallation Errors ............................................ 134

6-2 KAVN00000 - KAVN00199...................................................................................................................... 1356-3 KAVN00200 - KAVN00399...................................................................................................................... 1396-4 KAVN00400 - KAVN00599...................................................................................................................... 1496-5 KAVN00600 - KAVN00799...................................................................................................................... 1546-6 KAVN01200 - KAVN01399...................................................................................................................... 156

6-7 Detailed Messages.................................................................................................................................. 1666-8 Action for Detailed Message RPM-00824 ............................................................................................... 177

6-8-1 Check the Disk Space .................................................................................................................. 1776-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 ModelsA.1 System Configuration Diagrams................................................................................................................. 179

A.1.1 Local Copy Configurations ......................................................................................................... 179A.1.2 Continuous Access XP Configurations......................................................................................... 181

A.2 Node Display in Navigation Frame ............................................................................................................. 183A.3 Information Displayed in the Information Frame or Dialog Box by Method Selected ................................. 184A.4 Information Displayed in the Information Frame (Hosts View) ................................................................... 185

A.4.1 Hosts Node................................................................................................................................... 185


5/208

Contents 5

A.4.2 host-name Node........................................................................................................................... 186A.4.3Port/HSD/LUN Node............................................................................................................................. 188

A.5 Information Displayed in the Information Frame (Subsystems View)........................................... 190A.5.1 Subsystems Node ...................................................................................................................... 190A.5.2 subsystem-name Node............................................................................................................... 191A.5.3 Port/HSD/LUN Node................................................................................................................... 193

A.6 Information Displayed in the Information Frame (Pair Configurations View) .............................................. 195A.6.1 Pair Configurations Node ........................................................................................................... 195A.6.2 pair-management-server Node..................................................................................................... 195A.6.3 RAID Manager XP-configuration-definition-file-name Node....................................................... 197

A.6.4 copy-group-name Node...................................................................................................................... 198A.6.5 pair-name Node.......................................................................................................................... 200A.6.6 LDEV LDEV-number Node......................................................................................................... 201

Appendix B Glossary

Index


6/208

Figures 6

Figures

Figure 1-1 Window Configuration of Replication Monitor........................................................................................... 13Figure 1-2 List of Copy Pairs When the Hosts View Is Used..................................................................................... 15Figure 1-3 List of Copy Pairs When the Subsystems View Is Used .......................................................................... 15Figure 1-4 List of Copy Pairs When the Pair Configurations View Is Used ............................................................... 16Figure 1-5 Example of Determining and Displaying the Most Significant Pair Status................................................ 17Figure 1-6 Example of Changing the Status of a Copy Pair ...................................................................................... 18Figure 1-7 Control and Data Flow in a System Using Replication Monitor ................................................................ 20Figure 1-8 Usual Configuration.................................................................................................................................. 21Figure 1-9 Pair Management Server and Host Combined Configuration .................................................................. 22Figure 1-10 Pair Management Server and Host Combined (Agents Not Installed on Hosts) Configuration.............. 23Figure 1-11 Agent-less Configuration ........................................................................................................................ 24Figure 1-12 System Configuration for Example 1 (Resolving Problems from the Storage Subsystem Perspective) 27Figure 1-13 System Configuration for Example 2 (Resolving Problems from the Host Perspective) ........................ 30Figure 3-1 Relation between Replication Monitor Restart Time and the Refreshing Time ........................................ 53Figure 4-1 Timing for Sending Email .........................................................................................................................73Figure 4-2 Concept of Determining the Most Significant Pair Status.........................................................................74Figure 4-3 Scope for Determining the Most Significant Pair Status (Hosts View) .....................................................75Figure 4-4 Scope for Determining the Most Significant Pair Status (Subsystems View) ...........................................76Figure 4-5 Scope for Determining the Most Significant Pair Status (Pair Configurations View)................................77Figure 4-6 Configuration of the Web Client Window ..................................................................................................79Figure 4-7 Menu-bar Frame.......................................................................................................................................79Figure 4-8 Navigation Frame .....................................................................................................................................80Figure 4-9 Tree Structure below Hosts ...................................................................................................................... 81Figure 4-10 Tree Structure below Subsystems.......................................................................................................... 82Figure 4-11 Tree Structure below Pair Configurations............................................................................................... 83Figure 4-12 Jump Buttons.......................................................................................................................................... 84Figure 4-13 Refresh in the Navigation Frame............................................................................................................84Figure 4-14 Method Frame ........................................................................................................................................84Figure 4-15 Example of Displayed Information Frame .............................................................................................. 85Figure 4-16 Example of the Information Frame with the Mouse Pointer Positioned on a Sortable Item ...................85Figure 4-17 Example Dialog Box 1 ............................................................................................................................ 87Figure 4-18 Example Dialog Box 2 ............................................................................................................................ 87Figure 4-19 Example Cascade Configuration............................................................................................................90Figure 4-20 Example View for a Cascade Configuration........................................................................................... 90Figure 4-21 View of LDEV Detailed Information (When There Are Multiple Items of Information) ............................ 92Figure 4-22 Example of an Error Message Displayed in the Information Frame .......................................................93Figure 4-23 Example of an Error Message Displayed in a Dialog Box (Values Can Be Re-entered)........................ 94Figure 4-24 Example of an Error Message Displayed in a Dialog Box (Values Cannot Be Re-entered)...................94Figure 4-25 Difference Between Everytime and a Specified Number........................................................................ 97Figure 4-26 Counting Method When the Number of Notifications is Specified .......................................................... 97Figure 4-27 Example of the Set Monitoring Configurations Subwindow .................................................................... 98Figure 4-28 Example of the Add Monitoring Configuration Dialog Box......................................................................99Figure 4-29 Example of the Add Monitoring Configuration - Confirmation Dialog Box (Without SMTP Authentication)................................................................................................................................................................................... 99Figure 4-30 Example of List Objects Subwindow ....................................................................................................100Figure 4-31 Example of the Edit Monitoring Configuration Dialog Box.................................................................... 102Figure 4-32 Example of the Edit Monitoring Configuration - Confirmation Dialog Box ............................................102Figure 4-33 Example of Show Monitoring Configurations Subwindow .................................................................... 104Figure 4-34 Example of Delete Monitoring Configuration - Confirmation Dialog Box .............................................. 105Figure 4-35 Example of the Hosts view ................................................................................................................... 108Figure 4-36 Example of a List of Information on Monitoring-Target Hosts .............................................................. 108Figure 4-37 Example of a List of LUNs Which Are Connected to a Host and Comprise Pairs................................109Figure 4-38 Example 1 of Copy Pairs Cascaded and Associated with a LUN......................................................... 109Figure 4-39 Example 1 of a List of Copy Pairs Cascaded and Associated with a LUN (List Objects (Detailed)Subwindow) ............................................................................................................................................................. 110Figure 4-40 Example 1 of a List of LUNs Assigned to an LDEV Included in a Cascade .........................................110Figure 4-41 Example of the Subsystems View ........................................................................................................ 111Figure 4-42 Example of a List of Information on Monitoring-Target Storage Subsystems ...................................... 111Figure 4-43 Example of a List of LUNs Which Comprise Pairs and Are Stored in a Storage Subsystem............... 112Figure 4-44 Example 2 of a List of Copy Pairs Which Are Cascaded and Associated with a LUN ......................... 112Figure 4-45 Example 2 of a List of Copy Pairs (List Objects (Detailed) Subwindow) Which Are Cascaded andAssociated with a LUN.............................................................................................................................................113


7/208

Figures 7

Figure 4-46 Example 2 of a List of LUNs Which Are Assigned to the LDEV Included in the Cascade.................... 113Figure 4-47 Example of the Pair Configurations View ............................................................................................. 114Figure 4-48 Example of a List of Information on Monitoring-Target Pair Management Servers..............................114Figure 4-49 Example of a List of RAID Manager XP Configuration Definition Files Which Are Managed by a PairManagement Server ................................................................................................................................................ 115Figure 4-50 Example of a List of Copy Groups Which Are Included in a RAID Manager XP Configuration DefinitionFile ........................................................................................................................................................................... 115Figure 4-51 List of Copy Pairs Which Are Included in a Copy Group ...................................................................... 116Figure 4-52 Example of a List of LDEVs Which Comprise Pairs Indicated by a Copy Pair ..................................... 116Figure 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 Associatedwith an LDEV ........................................................................................................................................................... 117Figure 4-55 Example 3 of a List of LUNs Which Are Assigned to an LDEV Included in a Cascade........................ 118Figure 4-56 Example 1 of the Change Pair Status - Step 1 of 2 Dialog Box ........................................................... 121Figure 4-57 Example 1 of the Change Pair Status - Step 2 of 2 Dialog Box ........................................................... 122Figure 4-58 Example 2 of the Change Pair Status - Step 1 of 2 Dialog Box ........................................................... 123Figure 4-59 Example 2 of the Change Pair Status - Step 2 of 2 Dialog Box ........................................................... 124Figure 4-60 Version Information Dialog Box ............................................................................................................127


8/208

Tables 8

Tables

Table 1 Document Conventions..................................................................................................................................9Table 2 Revisions ..................................................................................................................................................... 11Table 1-1 Types of Pair Statuses............................................................................................................................... 16Table 1-2 Refresh Functions by Type and Applied Range ........................................................................................17Table 2-1 OSs and Web Browsers Required for the Management Server and Management Client.........................33Table 3-1 List of Parameters Required for Operating Replication Monitor ................................................................50Table 3-2 List of Parameters Related To Device Manager........................................................................................51Table 3-3 List of Parameters Related To Database Connections..............................................................................53Table 3-4 List of Parameters Related To Log Output ................................................................................................54Table 3-5 List of Parameters Related To Information Acquisition Interface............................................................... 55Table 4-1 List of Replication Monitor Web Client Functions ......................................................................................70Table 4-2 Items That Can Be Set in a Monitoring Configuration ............................................................................... 71Table 4-3 Relationship between the Monitored Object and the Object Address Displayed in the List of MonitoringConfigurations............................................................................................................................................................ 72Table 4-4 Correlation between Pair Statuses in Replication Monitor and Pair Statuses in Device Manager ............ 72Table 4-5 Rules for Determining the Most Significant Pair Status .............................................................................72Table 4-6 Scope for Determining the Most Significant Pair Status (Hosts View)....................................................... 74Table 4-7 Scope for Determining the Most Significant Pair Status (Subsystems View) ............................................75Table 4-8 Scope for Determining the Most Significant Pair Status (Pair Configurations View) .................................76Table 4-9 Display Format of the Last Update Time ...................................................................................................86Table 4-10 Node Icons in the Object Tree ................................................................................................................. 87Table 4-11 Icons of Replication Monitor Execution Results.......................................................................................88Table 4-12 Copy Status Icons.................................................................................................................................... 88Table 4-13 Primary Volume and Secondary Volume Icons (Pair Configuration) .......................................................88Table 4-14 Pair Status Icons (Pair Configuration) ..................................................................................................... 89Table 4-15 Monitoring Configuration Icon (Action) ....................................................................................................89Table 4-16 Correlation Between an Arrow Displayed in the Information Frame and the Device Manager Pair Status................................................................................................................................................................................... 91Table 4-17 Web Browser Language Setting and Displayed Language ..................................................................... 91Table 4-18 List of Items Set for Monitoring Parameters ............................................................................................ 95Table 4-19 When the Target Is a Copy Group ......................................................................................................... 118Table 4-20 When the Target Is a Copy Pair ............................................................................................................119Table 4-21 Selectable Copy Paces..........................................................................................................................120Table 5-1 Types of Log Files Output from Replication Monitor................................................................................ 130Table 6-1 Replication Monitor Message Numbers and Corresponding Functions...................................................133Table 6-2 Message Types and Meanings................................................................................................................ 133Table 6-3 Detailed Message Numbers and Corresponding Functions .................................................................... 134


9/208

About this guide 9

About this guide

This guide provides information about:

Installing HP StorageWorks XP Replication Monitor software.

Intended audienceThis 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.

PrerequisitesPrerequisites 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 symbolsTable 1 Document Conventions

Convention Element Convention Element

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

Medium blue, underlined text

(http://www.hp.com)

Web site addresses

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.


10/208

About this guide 10

NOTE: Provides additional information.

TIP: Provides helpful hints and shortcuts.

HP technical supportTelephone 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 Subscribers 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 supportand then Storageunder Product Category.

HP-authorized resellerFor the name of your nearest HP-authorized reseller:

In the United States, call 1-800-345-1518.

Elsewhere, visit http://www.hp.comand click Contact HPto 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/


11/208

Revision history (start here)

Revision tables

Table 2 Revisions

Date Edition Revision

November, 2005 First Initial release


12/208

Overview of Replication Monitor 12

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 OverviewReplication 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 FeaturesRecently, 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 fordisaster 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.


13/208


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.


14/208


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 pairmay be written simply aspair.

Copy groupA group containing multiple copy pairs. A copy group allows operations such as pair status changes

applied to multiple copy pairs.

1-2 Replication Monitor FunctionsReplication 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.


15/208


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 UsedPair 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.


16/208


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

Error in LUSE

Suspending

Deleting

1

suspend Indicates that the copy pair is in split status. Split 2

copying Indicates that copy processing is being performed for the copy

pair, either forward or in reverse.

Copying

Reverse-Copying

3

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, thestatuses of the copy pairs related to all volumes mounted forhostA, as well as the statuses of the copy pairsin a cascade configuration from those copy pairs, are displayed as pair statuses related to hostA. Here, if aBusiness 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.


17/208


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 informationobtained from Device Manager. This information is updated, orrefreshed, 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


18/208


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 withthe 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 PairReplication 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 MonitorThis 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.


19/208


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 .


20/208


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 systeminformation collected by hosts can be viewed.


21/208


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 servers 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.


22/208


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 servercan 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.

Replication Monitor and the Device Manager server are installed on the management server, and system

configuration information collected from the pair management server can be viewed.


23/208


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.


24/208


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, seeAppendix A, Information Available in System

Configuration Models.

1-4 Programs Related to Replication MonitorThis 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


25/208


26/208


27/208


Figure 1-12 System Configuration for Example 1 (Resolving Problems from the Storage SubsystemPerspective)

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

cascade configuration copy pairs) changes

to suspend.

An email is sent to the storage

administrator.

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.


28/208


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_Bis 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 EffectiveRange 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 inthe 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 suspendstatus. 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, andthat 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 BusinessOperations

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.


29/208


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 avolume to which host_B is connected on the mount point /mnt. The system administrator asks themabout 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-LDEV21pair to back up the data in the volume to tape.

The storage administrator asks the database administrator of host_B to cancel split processing untilsystem 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 thesidefile 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 completedsuccessfully.


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):


30/208


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

cascade configuration copy pairs) changes

to suspend.

An email is sent to the storage

administrator.

LU on which host_B is mounted


31/208


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 insuspend 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_Anode 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 themount 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 ofProcessing

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 avolume to which host_B is connected on the mount point /mnt. The system administrator also asks themabout 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, thecopy 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:


32/208


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.


33/208

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 WindowsThis 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 beestablished). 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

StorageWorks Command View XP Advanced Edition Device Manager Server Installation and

Configuration Guide.

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 2000 SP4, Windows

Server 2003 (32-bit), Windows Server 2003 SP1

(32-bit), Windows XP SP1, or Windows XP SP2

Internet Explorer 6.0 or

Internet Explorer 6.0

SP1

Solaris 8 or Solaris 9 (for SPARC) Netscape Navigator

7.0 or Mozilla 1.4

Windows 2000 SP3, Windows

2000 SP4, Windows Server 2003

(32-bit), Windows Server 2003

SP1 (32-bit), or Windows XP

SP2#

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.


34/208

Installation and Uninstallation 34

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 ServerInstallation 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, orLPT1 - 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 commu

XP12000 Replication Monitor Rootsan technologies Pvt Ltd

Documents

Transcript of XP12000 Replication Monitor Rootsan technologies Pvt Ltd