HP XP Continuous Access Software User Manual

HP StorageWorks

RAID Manager XP

User’s Guide

XP48 XP128 XP512

XP1024 XP10000 XP12000

ninth edition (November 2005)

part number: T1610-96004

This guide describes HP StorageWorks RAID Manager XP (RM) and provides installation and

configuration procedures, RM command usage, and troubleshooting instructions.

12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license.

The information contained herein 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, Windows, Windows XP, and Windows NT are U.S. registered trademarks of Microsoft Corporation. Oracle is a registered US trademark of Oracle Corporation, Redwood City, California. Linux is a U.S. registered trademark of Linus Torvalds. UNIX is a registered trademark of The Open Group.

HP StorageWorks Disk Array XP RAID Manager: User’s Guide

ninth edition (November 2005) part number: T1610-96004

2 HP StorageWorks Disk Array XP RAID Manager: User’s Guide

About this guide 9

Intended audience 9 Disk arrays 9 Related documentation 9 HP technical support 10 HP storage website 10 HP sales and authorized resellers 11

Document conventions 11 Revision history 12 Warranty statement 13 HP StorageWorks LUN Security XP Extension disclaime r 15

1 Description 17

RAID Manager features and environment 18

Continuous Access (CA) 19

Business Copy (BC) 20

Pairs and pair management 21 RAID Manager instances 23 RAID Manager command device 25

Manually switching command de vices 26

2 Installation and configuration 27

Disk array and host requirements 28

RAID Manager requirements with Continuous Access 28

Using RAID Manager with Business Copy 29 Installation and configuration outline 30 Installing RAID Manager on UNIX systems 31 Installing RAID Manager on Windows systems 33 Installing RAID Manager on MPE/iX systems 34

Contents 3

Installing RAID Manager on OpenVMS systems 37 Configuring the services and hosts files 39

Directory locations 39 Services file 40 Hosts file 40

Setting up the RM instance configuration file 41

RM instance configuration files 41 Creating an instance configuration file 42

RM instance configuration file parameters 43 HORCM_MON section 44 HORCM_CMD section 46 HORCM_DEV section 49 HORCM_LDEV section 52 HORCM_INST section 53 Starting the instances 54

Environment variables for BC 54

Environment variables for CA 56 Paired volume configuration 57

3 Using RAID Manager 59

RAID Manager pair commands 60 RAID Manager commands in scripts 61 Paired CA volume status definitions 62 Paired BC volume status definitions 64 Paired SnapShot volume status definitions 66 File types and structure 69 Log files 73

Log file format 73

Log directories 75

Output to host log file 75 User-created files 76 User-setta ble environm ent variables 77

RM environment variables 77

RM command environment variables 78

RM instance environment variable 79

4 HP StorageWorks Disk Array XP RAID Manager: User’s Guide

RM protection 80

Protection facility specification 81 Permission command 82 Protection facility support 82 Command device configuration 83 Commands controlled by RM protection 86 Permitting operations on protected volumes 87 Environment variables 91 Identifying a command device using protection mode 92

Using RAID Manager on a Windows 2000/2003 sys tem with “user” syste m

privileges 93 Windows System Administrator 93 RAID Manager user 98 Sample BAT file 100

LUN Securi ty Extension 102

Guarding options 102 Commands affected 102 Notes and Restrictions 103 Identifying Open LDEV Guard volumes 104

4 RAID Manager command reference 105

General commands 106 Windows NT/2000/2003 commands 107 Data integrity check comm ands 108 horcctl 109 horcmshutdown 112 horcmstart 113 horctakeover 114 inqraid 118 mkconf 131 paircreate 134 paircurchk 142 pairdisplay 145 pairevtwait 156 pairmon 162 pairresync 165 pairsplit 173 pairsyncwait 179 pairvolchk 186 raidar 197 raidqry 200

Contents 5

raidscan 202 Command Options for Windows NT/2000/2003 214 drivescan 215 env 217 findcmddev 218 mount 220 portscan 223 setenv 225 sleep 226 sync 227 umount 231 usetenv 233 Data Integrity Check Commands 235 raidvchkset 236 raidvchkdsp 243 raidvchkscan 250

5 Troubleshooting RAID Manager 263

Error reporting 264 Operational notes 265 Error codes 268 Command return values 270 Command errors 273

A Configuration file examples 279

Configuration definition for cascading volumes 280

Correspondence between a configuration file and mirror

descriptors 280

Cascading connection configuration files 281

CA configuration (remote CA, two hosts) 285

CA (remote CA, two host) command examples 288

CA configuration (local loopback, two hosts) 290

CA (local loopback, two hosts) command examples 292

CA configuration (two RM instances, one host) 294

CA (two RM instances, one host) command examples 296

BC configuration 298

BC command examples 301

Configuration for a BC cascaded connection 307

BC cascaded connection command examples 309

Configuration for a CA/BC cascaded connection 311

CA/BC cascaded connection command examples 314

Two-host BC configuration 317

6 HP StorageWorks Disk Array XP RAID Manager: User’s Guide

Two BC mirror configuration 319 Three-host BC configuration 321 Device group configuration 323

B HA Failover and failback 325

Using RAID Manager in HA environments 326

HA control script state transitions 326 Failback after SVOL-SMPL takeover 330 PVOL-PSUE takeover 335 S-VOL data consistency function 343 Takeover-switch function 346 Swap-takeover function 348 SVOL-takeover function 350 PVOL-takeover function 352

Recovery procedures of HA system configuration 353

Regression and recovery of CA 356 CA recovery procedures 357

C Fibre Channel addressing 359

Fibre Channel address conversions 360

D STDIN file formats 365

E Porting notice for MPE/iX 367

Porting notice for MPE/iX 368

Introduction 368 Restrictions in the current release 368 Known issues and concerns 371 MPE/iX startup procedures 373

F Porting notice for OpenVMS 377

Porting notice for OpenVMS 378

Introduction 378 Requirements and restrictions 378 Known issues and concerns 385 DCL command examples 391 Startup procedures on bash 396

Glossary 401

Index 409

Contents 7

8 HP StorageWorks Disk Array XP RAID Manager: User’s Guide

About this guide

This guide describes HP StorageWorks RAID Manager XP (RM) and provides installation and configuration procedures, RM command usage, and troubleshooting instructions. It also has configuration file examples and information about High Availability failover and failback, Fibre Channel addressing, and standard input (STDIN) file formats.

Intended audience

This guide is intende d for syst em administrator s with knowledge of the host server, the operating system, RAID technology, and XP disk arrays.

Disk arrays

Unless otherwise noted, the term disk array refers to these disk arrays:

HP Surestore Disk Array XP512 HP Surestore Disk Array XP48 HP StorageWorks Disk Array XP128 HP StorageWorks Disk Array XP1024 HP StorageWorks XP10000 Disk Array HP StorageWorks XP12000 Disk Array

HP technical support

In North America, call technical support at 1-800-633-3600, available 24 hours a day, 7 days a week.

Outside North America, call technical support at the location nearest you. The HP web site lists telephone numbers for worldwide technical support at:

Collect the following information before calling:

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 Subscribing to this service provides you with email updates on the latest product enhancements, newest drivers, and firmware documentation updates as well as instant access to numerous other product resources.

http://www.hp.com/support

• Technical support registration number (if applicable)

• Product serial numbers

• Product model names and numbers

• Applicable error message s

• Operating system type and revision level

• Detailed questions

. From this web site, select your country.

http://www.hp.com/go/e-updates

HP storage website

For the most current information about HP StorageWorks XP products, visit:

http://h18006.www1.hp.com/storage/arraysystems.html

For information about product availa bili ty, configuration, and connecti vity, contact your HP support representative.

10 HP StorageWorks Disk Array XP RAID Manager: User’s Guide

HP sales and authorized resellers

To reach HP sales or find a local authorized reseller of HP products, call 1-800-282-6672 or visit the HP How To Buy web site:

http://welcome.hp.com/country/us/en/howtobuy.html

You can also find HP sales and resellers at Contact HP.

http://www.hp.com

. Click

Document conventions

Convention Element

Blue text (Figure 1) Blue text represen ts a cro ss-refe rence. In the onlin e version of this guide,

the reference is linked to the target.

Bold Bold text represents application names, file names, menu items, dialog

box titles, buttons, key names, field names, and literal values that you type exactly as shown.

Italics Italic type indica te s that you must supply a valu e. It al ic type is also used

for manual titles.

Blue underlined sans serif font (www.hp.com

monospace font Monospace font deno tes use r inpu t and s ystem re spo nses, s uch as o utp ut

Example

)

Underlined, blue text represents a website on the Internet. In the online version of this guide, the reference is linked to the target.

and messages.

The word “example” in italics denotes an example of input or output. [ ] Square brackets indicate an optional parameter. { } Braces indicate that you must specify at least one of the listed options. | A vertical bar separates alternatives in a list of options.

About this guide 11

Revision history

September 1999 OPEN-8 emulation added.

January 2000 Content extensively revised and reorganized.

September 2000 Content extensively revised.

February 2001 Added support of MPE/iX. Content significantly

March 2001 Added mkconf command. Content enhanced.

November 2003 Added Oracle Data Validation. Added OpenVMS.

July 2004 General edit of content, layout, and language.General

enhanced.

Content significantly enhanced.

update to reflect recent changes. Modified installation procedure. Modified doc ument to refl ect HP12 000 disk arrays. Added “Using RAID Manager with ‘user’ system privileges on a Windows 2000/2003 system.” Added HP StorageWorks LUN Security XP Extension disclaimer.

March 2005 Added -fe option for the raidvchkdsp, raidscan, and

pairdisplay commands (display of information about external LUNs).

Clarified use of -l option in pairsplit command (applies to Continuous Access only).

Added CA-Journal description and operations. Added CA-Journal options to raidscan, pairdisplay, inqraid, raidscan, raidvchkdsp, raidvchkscan, pairdisplay, and pairsyncwait commands.

November 2005 Updated to include XP10000, Command View XP

Advanced Edition, Remote Web Console XP, SnapShot option for BC, and CA Journal updates.

12 HP StorageWorks Disk Array XP RAID Manager: User’s Guide

Warranty statement

HP warrants that for a period of ninety calendar days from the date of purchase, as evidenced by a copy of the invoice, the media on which the Software is furnished (if any) will be free of defects in materials and workmanship under normal use.

DISCLAIMER. EXCEPT FOR THE FOREGOING AND TO THE EXTENT ALLOWED BY LOCAL LAW, THIS SOFTWARE IS PROVIDED TO YOU “AS IS” WITHOUT WARRANTIES OF ANY KIND, WHETHER ORAL OR WRITTEN, EXPRESS OR IMPLIED. HP SPECIFICALLY DISCLAIMS ANY IMPLIED WARRAN TIES OR CONDITIONS OF MERCHANTABILITY, SATISFACTORY QUALITY, NON-INFRINGEMENT, TITLE, ACCURACY OF INFORMATIONAL CONTENT, AND FITNESS FOR A PARTICULAR PURPOSE. Some jurisdictions do not allow exclusions

of implied warranties or conditions, so the above exclusion may not apply to you to the extent prohibited by such local laws. You may have other rights that vary from country to country, state to state, or province to province.

WARNING! YOU EXPRESSLY ACKNOW LEDGE AND AGREE THAT USE OF THE SOFTWARE IS AT YOUR SOLE RISK. HP DOES NOT WARRANT THAT THE FUNCTIONS CONTAINED IN THE SOFTWARE WILL MEET YOUR REQUIREMENTS, OR THAT THE OPERATION OF THE SOFTWARE WILL BE UNINTERRUPTED, VIRUS-FREE OR ERROR-FREE, OR THAT DEFECTS IN THE SOFTWARE WILL BE CORRECTED. THE ENTIRE RISK AS TO THE RESULTS AND PERFORMANCE OF THE SOFTWARE IS ASSUMED BY YOU. HP DOES NOT WARRANT OR MAKE ANY REPRESENTATIONS REGARDING THE USE OR THE RESULTS OF THE USE OF THE SOFTWARE OR RELATED DOCUMENTATION IN TERMS OF THEIR CORRECTNESS, ACCURACY, RELIABILITY, CURRENTNESS, OR OTHERWISE. NO ORAL OR WRITTEN INFORMATION OR ADVICE GIVEN BY HP OR HP’S AUTHORIZED REPRESENTATIVES SHALL CREATE A WARRANTY.

About this guide 13

LIMITATION OF LIABILITY. EXCEPT TO THE EXTENT PROHIBITED BY LOCAL LAW, IN NO EVENT INCLUDING NEGLIGENCE WILL HP OR ITS SUBSIDIARIES, AFFILIATES, DIRECTORS, OFFICERS, EMPLOYEES, AGENTS OR SUPPLIERS BE LIABLE FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL, CONSEQUENTIAL, PUNITIVE OR OTHER DAMAGES (INCLUDING LOST PROFIT, LOST DATA, OR DOWNTIME COSTS), ARISING OUT OF THE USE, INABILITY TO USE, OR THE RESULTS OF USE OF THE SOFTWARE, WHETHER BASED IN WARRANTY, CONTRACT, TORT OR OTHER LEGAL THEORY, AND WHETHER OR NOT ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Your use of the

Software is entirely at your own ris k. Shoul d th e Soft war e prove defective, you assume the entire cost of all service, repair or correction. Some jurisdictions do not allow the exclusion or limitation of liability for incidental or conse quenti al damag es, so t he above limit atio n may not a pply to you to the extent prohibited by such local laws.

NOTE. EXCEPT TO THE EXTENT ALLOWED BY LOCAL LAW, THESE WARRANTY TERMS DO NOT EXCLUDE, RESTRICT OR MODIFY, AND ARE IN ADDITION TO, THE MANDATORY STATUTORY RIGHTS APPLICABLE TO THE LICENSE OF THE SOFTWARE TO YOU;

PROVIDED, HOWEVER, THAT THE CONVENTION ON CONTRACTS FOR THE INTERNATIONAL SALE OF GOODS IS SPECIFICALLY DISCLAIMED AND SHALL NOT GOVERN OR APPLY TO THE SOFTWARE PROVIDED IN CONNECTION WITH THIS W ARRANTY STATEMENT.

14 HP StorageWorks Disk Array XP RAID Manager: User’s Guide

HP StorageWorks LUN Security XP Extension disclaimer

HP StorageWorks LUN Security XP Extension provides the abil ity to place logical volumes into secure states. In these secure states, da ta on the volumes can not be modified until the retention time specified when the volume is placed in the secured state has elapsed. TO THE FULLEST EXTENT PERMITTED BY LAW, UNLESS EXPRESSLY PROVIDED OTHERWISE UNDER WRITTEN AGREEMENT BETWEEN HP AND CUSTOMER, HP WILL NOT BE LIABLE FOR ANY DIRECT, SPECIAL OR CONSEQUENTIAL DAMAGES (INCLUDING BUT NOT LIMITED TO LOSS OF PROFITS AND LOSS OF DATA) REGARDLESS OF WHETHER SUCH DAMAGES ARE BASED ON TORT, WARRANTY, CONTRACT OR ANY OTHER LEGAL THEORY, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES, ARISING OUT OF ANY PERFORMANCE OF OR IN FUR THERANCE OF UNLOCKING OR OTHERW IS E UNSECURING AT THE REQUEST OF THE CUSTOMER DATA THAT HAS BEEN SECURED USING HP StorageWorks LUN Security XP Extension BEFORE THE RETENTION TIME HAS EXPIRED.

About this guide 15

16 HP StorageWorks Disk Array XP RAID Manager: User’s Guide

Description

HP StorageWorks RAID Manager XP (RM) enables you to perform operations with HP StorageWorks Continuous Access XP (CA) and HP StorageWorks Business Copy XP (BC) by issuing commands from a host to the disk array. The RM software interfaces with the host sys tem software and host high availabili ty (HA) softwar e, as well as with th e BC and CA software on the disk array.

This book provides inst ructions for inst alling and usi ng the RM software on various versions of UNIX, Microsoft Windows, Open VMS, and MPE/iX. It has an extensive command reference and additional materials about configuration, failover, and failback.

Description 17

RAID Manager features and environment

RAID Manager lets you issue Bus in ess Copy ( BC) and Continuous Access (CA) commands from a host. These commands can be issued from the command line or built into a script (for example, a ksh, perl script, or an MS-DOS batch file).

You can execute a large number of BC and CA commands in a short period of time by using scripts containing RM commands. In MPE/iX, you can create POSIX command scripts. For more information about scripting, see “RAID Manager commands in scripts” (page 61).

RM also provides failover and operation commands that can support mutual hot standby when used with industry-standard failover software.

RM software consists of the following:

• RM instances (daemons)

• configuration files

• BC/CA commands and shell scripts

RM uses these entities:

• a special volume calle d a command device

• BC/CA volumes

RM runs in these (and other) environments :

UNIX RM runs on a UNIX host as the HORCM

daemon.

Windows NT/2000/2003 RM runs on a Windows NT/2000/2003 host as

a service.

MPE/iX RM runs in MPE/iX as a job stream. See

Appendix E,

OpenVMS RM runs on OpenVMS as a detached process.

See Appendix F,

OpenVMS” .

18 HP StorageWorks Disk Array XP RAID Manager: User’s Guide

“Porting notice for MPE/iX” .

“Porting notice for

Continuous Access (CA)

CA copies data from a local HP XP disk array to one or more remote HP XP disk arrays. You can use CA for da ta duplication, migration, and offsite backup.

RM displays CA volume or group information and allows you to perform CA operations through either the command line, a script (UNI X), or a batch file (Windows).

CA has a number of features that ensure reliable transfers in asynchronous mode, including journaling and protection against link failure.

For effective and complete disaster recovery solutions, CA (and therefore RM) is integrated with many cluster solutions, such as Cluster Extension (CLX) for Windows, Linux, Solaris and AIX, as well as MetroCluster and ContinentalCluster for HP-UX.

CA modes

CA can operate in 3 different modes:

CA-Synchronous (CA-Sync): With CA-Sync all write operation s on the primary (source) volume have to be replicated to the secondary (copy) volume before the write can be acknowledged to the host. This mode ensures the highest level of data concurrency possible. Host I/O performance is directly impacted by the di stance between the primary and secondary volumes and therefore CA-Sync is recommended for metropolitan distances.

CA-Asynchronous (CA-Async): With CA-Async all write operations on the primary volume are time stamped and stored in a the array system cache, also known as the side file, before the write is acknowledged to the host. The data is th en a synchronously replicated to the seconda ry ar ray and re-applied in seq uence to the se condary device s. W ith CA-Asyn c data is not always current, but due to the unique timestamp implementation data will always be consistent. The side file functions to protect host I/O performance from any temporary degradations of the communication link between the sites. It also acts as a buffer for temporary high write bursts from the host. CA-Async is ideal for long distance replication.

Description 19

Business Copy (BC)

CA-Journal: CA-Journal is supported on XP10000/XP12000 arrays. CA-Journal works in principal the same as CA-Async, but instead of buffering write I/Os in th e mo re ex pensive and limited XP array cac he (t he side file), CA-Journal wri tes data on special XP LUNS called journal pool s. Journal pools can con si st s of up to 16 physical LDEVs of any size, and can therefore buffer much larger amounts of data. CA-Journal also implements a unique read operation from the remote array, instead of the normal write (push) operation from t he local ( primary) ar ray, and is therefore much more tolerant of short communication link outages.

BC software allows you to c re at e an d mai ntain up to nine copies of data on the local disk array. You can use these copies for backup, data duplication, or testing.

BC duplicate volumes are created within the same disk array at hardw are speeds.

RM displays BC volume or group information and allows you to perform BC operations through e ither th e command lin e, a script ( UNIX), or a ba tch file (Windows).

When you use CA to make a duplicate copy of a volume on a remote disk array, and then make up to 9 internal BC copies on the remote disk array from that volume, you can effectively create up to 10 copies of a logical volume on the remote disk array.

SnapShot

SnapShot introduces a new capability within BC. It allows the user to create point-in-time copies of only changed data blocks (Copy-on-Write) and store them in a SnapShot storage pool, thus reducing the amount of required storage capacity.

SnapShot creates a virtual volume (V-VOL) for copy-on-write without designating a specific LUN as S-VOL. However, for the host to use the ShapShot volume, there must be a LUN mapped.

20 HP StorageWorks Disk Array XP RAID Manager: User’s Guide

SnapShot employs two techniques:

• creating or mapping a virtual volume (V- VOL)

• copy on write to a SnapShot pool volume (pool-VOL) identified by a pool ID.

SnapShot does not require any new RM commands, it uses current BC commands with new arguments.

Note: SnapShot is used in Unix and Windows environments only. SnapSho t does

not work in MPE/iX and OpenVMS environments.

The following figure illustrates the basic concept.

Pairs and pair management

Both BC (non-SnapShot) and CA continuously copy data from a primary source volume known as a P-VOL to a secondary volume known as an S-VOL.

Description 21

The relationship between a P-VOL and an S-VOL is called a pair.

You can use RM’s paircreate command to est ablish pairs. Once a pair is established, updates to the P-VOL are automatically and continuously copied to the S-VOL.

There are other commands to manage pairs. You can temporarily suspend copy operations, create a Sna pShot pai r, resync the pair , an d del et e the pai r relationship.

In addition, RM has many commands to display status, manage failover, manage failback, and set the conditions under which BC and CA execute.

Creating SnapShot pairs

-When a command is given that will generate a pair-volume, such as paircreate, its type (SnapShot or BC) is determined by the attributes of the S-VOL. If either of the following requirements are met, a SnapShot pair is created:

• If the S-VOL is specified as OPEN-0V (creates an unmapped V-VOL).

• If no S-VOL is specified.

V-VOL characteristics.

• Identified as OPEN-0V after a SCSI Inquiry or RAID Manager command.

• An unmapped V-VOL will reply to a SCSI Inquiry but does not have read/write ability. It will provide read capacity only. However, after a V-VOL is mapped as the S-VOL, read/write ability is enabled.

22 HP StorageWorks Disk Array XP RAID Manager: User’s Guide

RAID Manager instances

Each execution of RM is known as an RM instance. Instances are local or remote and can run on the same host or different hosts. Two RM instances are typically required to manage BC or CA pairs.

Local instance The RM instance currently being used, that is, the

Remote instance The RM instance that the l ocal instance communicates

There are four possible RM topologies:

• One host connected to one disk array

If you are using one host, both RM instances are located on the same host.

• One host connected to two or more disk arrays

instance to which commands are issued. Local instances link to remote instances by using UDP socket services.

with, as configured in the HORCM_INST section of an RM instance configuration file. (For further information on the RM instance configuration file see

page 41)

Using a single host connec ted to two or more dis k arrays al lows you to maintain duplicate da ta on two di ffe rent disk arrays. When you choose this option, the host Logical Volume Manager must not be able to see both sides of the same BC or CA pair or it will become confused.

• Two or more hosts connected to one disk array

Using two hosts connected to one disk array allows you to locate one RM instance on each host and thus maintain separate copies of the data controlled by independent hosts; primary volumes (P-VOLs) are used by one host while secondary volumes (S-VOLs) are used by the other host (for example, for backup, testing, or data duplication).

• Two or more hosts connected to two or more disk arrays

Using two or more hosts connected to two or more disk arrays allows the most flexib le CA disaster recovery plan. The rem ote and local sets

Description 23

of data are administered by different hosts, guarding against host and disk failure. This is the configurat ion used by high a vailabilit y (HA) softwa re (such as HP MetroCluster) in conjunction with RAID Manager’s horctakeover command (see

page 114) allowing for b oth fail over an d

failback.

24 HP StorageWorks Disk Array XP RAID Manager: User’s Guide

RAID Manager command device

You must designate a special volume on the disk array as the RAID Manager command device. Th e command devi ce acce pts BC or CA control operations. These are seen as in-band SCSI read and write commands, and are executed by the disk array. The volume designated as the command device is used only by RM and is blocked from other user access.

The command device can be any OPEN-x device that the host can access. An RM command device uses a minimum of 16 MB of space. The remaining volume space i s reserve d for RM and its utili ties. You cannot use a Logical Unit Size Expansion (LUSE) volume as a command device; however, you can use the Volume Size Configuration (VSC) feature of Command View XP, LUN Configuration Manager XP, Remote Web Console XP, or Command View XP Advanced Edition to make custom volumes as small as 35 accomplished using CVXP AE on XP12000/XP10000 disk arrays)

Caution Be certain that there is no data on the volume you select as the command

device. Data on the volume you select becomes inaccessible.

MB. (NOTE: VSC operations cannot be

Caution MPE/iX systems will need a dummy volume set. Create this through the

VOLUTIL utilit y pro gram and scratch the volume set befor e converting to a command device.

Caution OpenVMS systems need a LUN 0 device of 35 MB. Note that storage

assigned to the LUN 0 device is not accessible from OpenVMS.

RM issues SCSI read/write commands to the command device. If the command device fails for any reason, all BC and CA commands terminate abnormally and the host cannot issue RM commands to the disk array.

To avoid data loss and system downtime, you can designate an alternate command device. Then, sho uld RM receive an error notification in r ep ly to a request, RM automatically switches to the alternate command device.

Description 25

Manually switching command devices

To avoid having comman ds te rmi nat e abno rmal ly during a failure, RM has a command device alternating function, which allows you to manually switch devices.

• When the command device switches

When RM receives an e rror notifi cation fro m the operatin g system, the RM switches automatically to the alternate device.

You can also alternate command devices manually by issuing a RM

horcctl command. See

• When to issue the horcctl (alternate command device) command

Issue a horcctl command to switch command devices before a command device is blocked due to online maintenance.

After completing online maintenance, reissue the command. The first command device is then re-activated.

• How to define alternate command devices

You can define two or more command dev ices in t he HORCM_CMD section of the configuration definition file. If you specify two or more devices on the same line, they are recognized as alternating control devices for the same array. See

“horcctl” (page 109).

“HORCM_CMD section” (page 46).

26 HP StorageWorks Disk Array XP RAID Manager: User’s Guide

Installation and configuration

This chapter describes how to install and configure RAID Manager for UNIX, Windows, MPE/iX, and OpenVMS systems.

Installation and configuration 27

Disk array and host requirements

RM requires an activated installation of BC or CA on the disk array. For information on activating and operating these programs, refer to the following manuals:

• HP StorageWorks Business Copy XP: User’s Guide

• HP StorageWorks Continuous Access XP: User’s Guide

• HP StorageWorks Command View XP for XP Disk Arrays: User Guide

• HP StorageWorks Command View XP Advanced Edition Device Manager Web Client User's Guide

• HP StorageWorks XP Remote Web Console User Guide for the XP1024/XP128

• HP StorageWorks XP Remote Web Console User Guide for the XP12000/XP10000

RAID Manager requirements with Continuous Access

• Have your HP representative configure the disk arrays for CA functions.

• Install CA license keys on the disk arrays.

• Configure the sender ports (Initiator for Fibre Channel, RCP for ESCON) and receiver ports (RCU-Target for Fibre Channel and LCP for ESCON) on the local and remote disk arrays.

• Establish a path between the local and remote control units (CUs) using Continuous Access.

• Enable bidirectional swap between local and remote volumes. Verify that at least two physical links exist in each direction.

• Designate one or more RM command devices using Command View XP, LUN Configuration Manager XP, Remote Web Console XP, or Command View XP Advanced Edition. If none of these are available, ask your HP representative to configure the devices.

28 HP StorageWorks Disk Array XP RAID Manager: User’s Guide

• Plan the mapping of the CA disk volume pairs. Determine which volumes to access.

• Map the paths to be used for each host.

Using RAID Manager with Business Copy

• Have your HP representative configure the disk array for BC functions.

• Install the BC license key on the disk array.

• Plan the mapping of the BC disk volume pairs. Determine which volumes to access.

• Map the paths to be used for each host.

Installation and configuration 29

Installation and configuration outline

RM installation and configuration consists of the following tasks. Task details appear in the subsequent sections.

• Installing RAID Manager

Install the RM software on the hosts.

• Configuring the services and hosts files

Add a service name/number to the host services file (for example,

/etc/services) for each RM instance. Configure the hosts file.

• Setting up the RM instance configuration file

Configure paths to one or more RM command devices for each host. All hosts and RM instances can use the same command device for a given disk array. However, it is recommended that each host have its own command device.

• Starting the instan ces

Set the necesary environment variables to issue commands to the desired RM instance.

30 HP StorageWorks Disk Array XP RAID Manager: User’s Guide

+ 382 hidden pages