HP P9000 RAID Manager User Guide Abstract This guide provides information on using HP P9000 RAID Manager Software on HP StorgeWorks P9000 disk arrays. Included is information on: command usage, configuration file examples, and information on High Availability failover and failback, Fibre Channel addressing, and Standard input (STDIN) file formats.
© Copyright 2010, 2012 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 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.
Contents 1 Overview..................................................................................................8 About RAID Manager...............................................................................................................8 RAID Manager functions available on the P9500 storage system....................................................8 Provisioning function.............................................................................................................
Logging raidcom command............................................................................................46 User-created files....................................................................................................................49 3 RAID Manager functions on P9500............................................................50 Command execution using in-band and out-of-band methods.......................................................
LDEV nickname function......................................................................................................94 Available provisioning operations.............................................................................................94 Available provisioning operation (specifying device group)........................................................100 Summary........................................................................................................................
Continuous Access Asynchronous, Continuous Access Synchronous, and Continuous Access Journal volumes..........................................................................................................................138 Sidefile cache for Continuous Access Asynchronous.........................................................140 Continuous Access Asynchronous transition states and sidefile control................................141 Continuous Access Asynchronous/Continuous Access Journal error state...
8 Examples of using RAID Manager commands............................................174 Group version control for mixed storage system configurations....................................................174 LDM volume discovery and flushing for Windows.....................................................................174 Volume discovery function.................................................................................................175 Mountvol attached to Windows systems..........................
1 Overview RAID Manager enables you to perform storage system configuration and data management operations by issuing commands to the RAID storage systems. About RAID Manager RAID Manager enables you to perform storage system configuration and data management operations by issuing commands to the RAID storage systems.
Item Description User authentication Supports the user authentication function in conjunction with the Remote Web Console/SVP. Once user authentication is enabled, a command can be executed in accordance with the authentication controlled by the Remote Web Console/SVP. User authentication is required in the following cases. • When executing replication or provisioning operation with out-of-band method. • When executing provisioning operation with in-band method.
The transaction mode can execute the following checking. • Context check: This check is executed when a script file is specified by the -zt option. It checks the context of preceding commands and determines whether a subsequent command can be executed. Specifying example: > raidcom -zt • Configuration check: This check verifies that the actual storage system confirmation is valid (implemented) for the resources specified in the commands (LDEVs, ports, pools, etc.).
LAN to the virtual command device, and the requested operations are then performed by the storage system. The following table illustrates in-band and out-of-band RAID Manager operations. Figure 1 Overview of out-of-band and in-band operations The following table provides a comparison of in-band and out-of-band operations.
LDEV nickname function A unique nickname with up to 32 characters can be given to an LDEV. LDEV grouping function In the RAID Manager before supporting P9500, it was required to define a copy group for the configuration definition file on each host. When changing copy group information, editing of the configuration definition file was required on each host. In the RAID Manager supporting P9500, the group information can be defined at a time and stored in the storage system.
Resource group locking function The resource group locking function prevents conflict among multiple users: User scripts cannot be guaranteed to work correctly when there are multiple users (Remote Web Console and SVP). You can use the Lock command while the script is running to ensure completion. To use the Lock command, user authentication is required. RAID Manager functions available on all RAID storage systems RAID Manager provides the following functionality on all HP RAID storage systems.
2 RAID Manager software environment The RAID Manager software environment involves components on the RAID storage system(s) and RAID Manager instance components on the host server(s). Overview of the RAID Manager software environment The RAID Manager software environment involves components on the RAID storage systems and RAID Manager instance components on the host server(s). The RAID Manager components on the storage systems include the command devices and the data volumes.
Each command device must be set using the LUN Manager software on Remote Web Console. In addition, for using a Provisioning command, user authentication is required. Set the security attribute of the command device with user authentication. For information and instructions on setting a command device, see the HP P9000 Provisioning for Open Systems User Guide. Each command device must also be defined in the HORCM_CMD section of the configuration file for the RAID Manager instance on the attached host.
Figure 2 Current assignment sequence Figure 3 Improved assignment sequence The command device performs the assignment of an instance through TWO phase that has "temporary allocation (1 0)" and "actual allocation (1 1)" to the instance assignment table.
subject to the LVM can use the alternate path PV-LINK. To avoid command device failure, RAID Manager supports an alternate command device function. • Definition of alternate command devices. To use an alternate command device, you must define two or more command devices for the HORCM_CMD item in the configuration definition file. When two or more devices are defined, they are recognized as alternate command devices. • Timing of alternate command devices.
commands is viewed as a normal disk by the SCSI interface, the OS can access its local control area. The RAID storage system must distinguish such accesses from the control command accesses. Normally, several megabytes of the OS control area are used starting at the initial LBA#. To avoid using this area, a specific LBA# area is decided and control commands are issued within this area. The command LBA# recognized by the storage system is shown below, provided the maximum OS control area is 16 MB.
Figure 7 Command flow Issuing commands for LDEVs within a LUSE device A LUSE device is a group of LDEVs regarded as a single logical unit. Because it is necessary to know the configuration of the LDEVs when issuing a command, a new command is used to specify a target LU and acquire LDEV configuration data (see figure).
Figure 9 HORCM operational environment RAID Manager instance configurations The basic unit of the RAID Manager software structure is the RAID Manager instance. Each copy of RAID Manager on a server is a RAID Manager instance. Each instance uses its own configuration definition file to manage volume relationships while maintaining awareness of the other RAID Manager instances. Each RAID Manager instance normally resides on separate servers (one node per instance).
Figure 10 RAID Manager instance configuration & components The four possible RAID Manager instance configurations are: • One host connected to one storage system. Connecting one host to one storage system allows you to maintain multiple copies of your data for testing purposes or as an offline backup. Each RAID Manager instance has its own operation manager, server software, and scripts and commands, and each RAID Manager instance communicates independently with the command device.
by different hosts. This guards against storage system failure as well as host failure. The RAID Manager instances of separate hosts are connected via the LAN so that they can maintain awareness of each other. Each RAID storage system has a command device that communicates with each RAID Manager instance independently.
Table 3 Supported RAID Manager (HORCM) communication HORCM 32 bit 64 bit MPE/iX HORCM 32 bit HORCM 64 bit MPE/iX little big little big big little AV AV AV - AV big AV AV AV - AV little AV AV AV - NA big - - - - - big AV AV NA - AV Configuration definition file Overview The RAID Manager configuration definition file is a text file that defines a RAID Manager instance.
# at the head of each line is used to insert a comment in the configuration file. Example 2 Configuration file example — UNIX-based servers HORCM_MON #ip_addressservicepoll(10ms)timeout(10ms) HST1horcm10003000 HORCM_CMD #unitID 0... (seq#30014) #dev_name dev_name dev_name dev/rdsk/c0t0d0 #unitID 1...
Table 4 Configuration (HORCM_CONF) parameters (continued) Parameter Default Type Limit timeout (10 ms) 3000 Numeric value* None dev_name for HORCM_DEV None Character string 31 characters dev_group None Character string 31 characters Recommended value = 8 char.
The command device must be mapped to the SCSI/fibre using LUN Manager. You can define more than one command device to provide failover in case the original command device becomes unavailable (see “Alternate command device function” (page 16)). The mapped command devices can be identified by the “-CM” of product ID field of the inqraid command.
Figure 14 Configuration and Unit IDs for Multiple Storage systems dev_name for Windows In Windows SAN environment, “Volume{guid}” will be changed on every re-boot under MSCS/Windows2k3, if Windows finds the same signature on the command device connected with Multi-Path.Therefore, find NEW “Volume{guid}”, and change “Volume{guid}” described in the RAID Manager configuration file.
HORCM_CMD #dev_name \\.\CMD-30095-250-CL1-A-1:/dev/rdsk/ dev_name dev_name once this name is specified, HORCM finds the “\CMD-Serial#-Ldev#-Port#” from the device file specified by the HINT at the time of HORCM startup. HINT must specifies to be end with “/” for the directory of the device file name or the directory that includes the pattern of device filename, as shown in the following.
The following values are defined in the HORCM_DEV parameter: • dev_group: Names a group of paired logical volumes. A command is executed for all corresponding volumes according to this group name. • dev_name: Names the paired logical volume within a group (i.e., name of the special file or unique logical volume). The name of paired logical volume must be different to the dev name in another group.
• Target ID: Defines the SCSI/fibre target ID (TID) number of the physical volume on the specified port. • LU#: Defines the SCSI/fibre logical unit number (LU#) of the physical volume on the specified target ID and port. NOTE: In case of fibre channel, if the TID and LU# displayed on the system are different than the TID on the fibre address conversion table, then you must use the TID and LU# indicated by the raidscan command in the RAID Manager configuration file.
Figure 15 Configuration for multiple networks (5) HORCM_LDEV The HORCM_LDEV parameter is used for specifying stable LDEV# and Serial# as the physical volumes corresponding to the paired logical volume names. Each group name is unique and typically has a name fitting its use (e.g., database data, Redo log file, UNIX file). The group and paired logical volume names described in this item must also be known to the remote server. • dev_group: This parameter is the same as the HORCM_DEV parameter.
(6) HORCM_LDEVG The HORCM_LDEVG parameter defines the device group information that the RAID Manager instance reads. For details about device group, see“LDEV group function” (page 66). The following values are defined. • Copy group: specifies a name of copy group. This is equivalent to the dev_group of HORCM_DEV and HORCM_LDEV parameters. RAID Manager operates by using the information defined here. • ldev_group: Specifies a name of device group that the RAID Manager instance reads.
Table 5 Mirror descriptors and group assignments HORCM_DEV parameter in configuration file HORCM_DEV #dev_group dev_name port# Oradb oradev1 CL1-D TargetID 2 LU# Business Copy Cnt Ac-J (Snapshot) only only Continuous Business Copy Access Synchronous/ Cnt Ac-J MU#1-#2 (MU#3-#63) MU#1-#3 oradev1 oradev1 - - oradev1 oradev1 oradev11 - MU# 1 HORCM_DEV TargetID MU#0 #dev_group dev_name port# Oradb oradev1 CL1-D 2 LU# 1 Oradb1 oradev11 CL1-D 2 1 1 Oradb2 oradev21 CL1-D 2
Figure 17 Business Copy cascade connection and configuration file Business Copy Since Business Copy is a mirrored configuration within one storage system, it can be described as a volume of the cascading connection according to two configuration definition files. For a Business Copy-only cascading connection, the specified group is assigned to the mirror descriptor (MU#) of Business Copy, specifically defining “0” as the MU# for Business Copy.
Figure 19 Pairdisplay on HORCMINST1 Figure 20 Pairdisplay on HORCMINST0 Cascading connections for Continuous Access Synchronous and Business Copy The cascading connections for Continuous Access Synchronous/Business Copy can be set up by using three configuration definition files that describe the cascading volume entity in a configuration definition file on the same instance.
Figure 21 Continuous Access Synchronous/Business Copy cascading connection and configuration file Figure 22 (page 36) through Figure 25 (page 37) show Continuous Access Synchronous/Business Copy cascading configurations and the pairdisplay information for each configuration.
Figure 23 Pairdisplay for Continuous Access Synchronous on HOST2 (HORCMINST) Figure 24 Pairdisplay for Business Copy on HOST2 (HORCMINST) Figure 25 Pairdisplay for Business Copy on HOST2 (HORCMINST0) RAID Manager instance components on the host server 37
RAID Manager software files The RAID Manager software consists of files supplied with the software, log files created internally, and files created by the user. These files are stored on the local disk in the server machine.
Title File name Configuration setting command HORCM/usr/bin/raidcom Command name Mode User*1 Group raidcom 0544 root sys A file for management HORCM/etc/Raidcom_Dic_Raid_RMXP_Patch.txt - 0644 root sys A file for management HORCM/etc/Raidcom_Help_Raid_RMXP.txt - 0644 root sys A file for management HORCM/etc/Raidcom_Dic_Raid_RMXP.txt - 0644 root sys NOTE: • The \HORCM\etc\ commands are used from the console window.
Title File name Command name Oracle Validation confirmation \HORCM\etc\raidvchkdsp.exe raidvchkdsp Oracle Validation confirmation \HORCM\etc\raidvchkscan.exe raidvchkscan Configuration setting command \HORCM\etc\raidcom.exe raidcom A file for management \HORCM\etc\Raidcom_Dic_Raid_RMXP_Patch.txt - A file for management \HORCM\etc\Raidcom_Help_Raid_RMXP.txt - A file for management \HORCM\etc\Raidcom_Dic_Raid_RMXP.txt - Tool \HORCM\Tool\chgacl.exe chgacl Tool \HORCM\Tool\svcexe.
Title File name Command name User Error notification $ROOT:[HORCM.usr.bin]pairmon.exe pairmon sys Volume checking $ROOT:[HORCM.usr.bin]pairvolchk.exe pairvolchk sys Pair configuration confirmation $ROOT:[HORCM.usr.bin]pairdisplay.exe pairdisplay sys RAID scan $ROOT:[HORCM.usr.bin]raidscan.exe raidscan sys RAID activity report $ROOT:[HORCM.usr.bin]raidar.exe raidar sys Connection confirmation $ROOT:[HORCM.usr.bin]raidqry.exe raidqry sys Trace control $ROOT:[HORCM.usr.bin]horcctl.
RAID Manager log files HORCM logs are classified into startup logs and execution logs. • The startup logs contain data on errors that occur before HORCM becomes ready to provide services. Thus, if HORCM fails to start up due to improper environment setting, refer to the startup logs to resolve the problem. • The HORCM execution logs (error log, trace, and core files) contain data on errors that are caused by software or hardware problems.
Table 6 Log file names and locations (continued) File UNIX-based systems Windows-based systems Trace HORCM trace: HORCM trace: $HORCM_LOG/horcmlog_HOST/horcm_PID.trc $HORCM_LOG\horcmlog_HOST\horcm_PID_trc.txt Command trace: Command trace: $HORCM_LOG/horcmlog_HOST/horcc_PID.trc $HORCM_LOG\horcmlog_HOST\horcc_PID_trc.
environment, it is possible to change the trace control parameters into the global parameters using this command. Table 8 (page 44) lists and describes the parameters of the trace control command. Table 8 Trace command parameters Parameter Function Trace level parameter Specifies the trace level, range = 0 to 15. Trace size parameter Specifies the trace file size in KB. Trace mode parameter Specifies the buffer mode or non-buffer mode for writing data in the trace file.
The masking feature is to enable the tracing without changing their scripts. And this feature is available for all RAID Manager commands (except inqraid or EX_xxx error code). For example, if you want to mask pairvolchk (returns 22) and raidqry, specify the following: pairvolchk=22 raidqry=0 You can track script performance, and then decide to mask by auditing the command logging file, as needed. • Relationship between an environment variable and horcc_HOST.
• Examples for execution /HORCM/log* directory [root@raidmanager log9]# ls l total 16 drwxr-xr-x 3 root root 4096 -rw-r--r-- 1 root root 3936 -rw-r--r-- 1 root root 2097452 -rw-r--r-- 1 root root 46 drwxr-xr-x 3 root root 4096 Oct Oct Oct Oct Oct 27 27 27 27 27 17:33 17:36 17:29 17:19 17:19 curlog horcc_raidmanager.log horcc_raidmanager.oldlog horcc_raidmanager.conf tmplog /HORCM/log*/horcc_HOST.
The conditions to support the output of syslog file The conditions to support this function are explained in the following: Supported OS This function is supported only when the OS of the host is one of the following (Windows is out of support): • Solaris 2.5 • Solaris 10/x86 • HP-UX 10.20/11.0/11.2x • AIX 4.3 • Red Hat Linux 6.0, 7.0, 8.0 AS/ES 2.1, 3.0, 4.0, 5.0 • AS/ES 2.1, 3.0 Update2, 4.0, 5.
Table 9 Display information of the title row Item Output example Syslog fixed output part (Including the host name) Jun 27 10:15:13 rmsolx86 raidcom: [ID 702911 user.info] Process ID PID:1234 Command status COMMAND NORMAL or COMMAND ERROR Separation : User name Title EUserId for HORC : User name of the host root (user ID) (0) Time that performed raidcom Wed Jun 27 10:15:13 2012 *It varies depending on the host OS.
Aug 24 12:24:27 raidmanager raidcom: PID:06857 [raidcom] User authentication has failed on Serial#(64568). Aug 24 12:24:27 raidmanager raidcom: PID:06857 [raidcom] [EX_ENAUTH] Authentication failed with User Aug 24 12:24:27 raidmanager raidcom: PID:06857 [raidcom] [exit(202)] User-created files RAID Manager supports scripting to provide automated and unattended copy operations.
3 RAID Manager functions on P9500 The RAID Manager functions available on the P9500 storage system are more comprehensive than on previous RAID storage systems. Command execution using in-band and out-of-band methods The methods of executing commands provided by RAID Manager can be classified into the in-band and out-of-band methods. • In-band method.
Setting command devices using in-band and out-of-band methods The setting contents of a command device or a virtual command device to be defined for a configuration definition file for executing the commands in the in-band and when executing commands using the methods are shown below. In-band method When executing a command using the in-band method, set an LU path in a configuration definition file and create a command device.
The user authentication function inputs a login command from the client (server) and, to authenticate the user ID and password sent from RAID Manager and the same types of information maintained by the storage system, issues an authentication request to the authentication module (SVP). If the user ID and password sent from RAID Manager are authenticated, RAID Manager, for the once authenticated user (the user on the client starting up RAID Manager), stores the user ID and password.
Controlling user resources RAID Manager verifies the user who executes the command has been authenticated already. After that, RAID Manager obtains the access authority of the resource groups that are configured on the user roles, and then compares the access authority of the relevant user and the specified resources.
• Host group • RAID group • External connection group The commands that are executed depending on the operation authorities managed by Remote Web Console and the SVP The commands and operation authority managed by Remote Web Console and SVP are listed in the following table. For information about creating the Remote Web Console user accounts, registering user accounts to user groups, and user group authorities, see HP P9000 Remote Web Console User Guide.
Table 13 Commands and operation authority managed by Remote Web Console and SVP (continued) Operation Operation target Authority Executable command Operation authority (Role) Thin Provisioning virtual volume Thin Provisioning virtual volume creation authority raidcom add ldev -pool Storage Administrator (Provisioning) Thin Provisioning virtual volume deletion authority raidcom delete ldev Storage Administrator (Provisioning) Snapshot virtual volume Snapshot virtual volume raidcom add ldev -pool
Table 13 Commands and operation authority managed by Remote Web Console and SVP (continued) Operation Operation target Authority Executable command Operation authority (Role) Attribute change External Volume External path setting authority raidcom add path Storage Administrator (Provisioning) Pool Pool setting authority raidcom modify pool Storage Administrator (Provisioning) Port Port attribute setting authority raidcom modify port -port_attribute Storage Administrator (System Resource Man
Figure 28 The relationship among user, command devices, and resource groups Table 14 The relationship between resource groups and command devices Login user Command device System administrator CM0 Operating range Reference Configuration Out-of-Band change OK: OK OK OK OK OK - OK OK - OK OK OK OK OK - Can operate all resource groups. CM10 OK: Can operate only in the range of resource group 10. CM20 OK: Can operate only in the range of resource group 20.
Table 14 The relationship between resource groups and command devices (continued) Login user Command device Operating range Reference CM10 NG: Operation Nothing is displayed or the operation authority authority error error. - CM20 OK: - OK Configuration Out-of-Band change OK Can operate only in the range of resource group 20. OK: Operable NG: Inoperable Shown in above table, the relationship among users, command devices, and operations of resource groups are the following.
performed, each configuration change command can be performed. However, the competition with the other application might cause an error. The commands for performing the exclusive control and exclusive control release (lock and unlock) of resource groups are as follows.
Table 15 Execution modes and options of the configuration setting command (line-by-line mode) Command syntax Syntax check Context check Configuration check Command execution with no error Remarks raidcom Executed Not executed Not executed Executed Default raidcom -checkmode precheck Executed Not executed Not executed Not executed Check only Table 16 Execution modes and options of the configuration setting command (transaction mode) Command syntax Syntax check Context check
raidcom -zt -load -checkmode precheck Details of check contents Details of Context check is described below. checking contents before issuing a script can reduce load for the debug operation in a way of executing script. LDEV check The check is performed from the following perspective. Note that checking for the object information that is related to the LDEV such as pool or device group, or an attribute of LDEV is not executed.
• raidcom check_ext_storage external_grp {-external_grp_id | -ldev_id | -grp_opt -device_grp_name []} • raidcom add device_grp -device_grp_name -ldev_id … [-cnt ] • raidcom delete device_grp -device_grp_name -ldev_id… [-cnt ] • raidcom modify ldev -ldev_id {-status [] | -ldev_name | -mp_blade_id | -ssid |
for /l %%i in (1,1,3) do ( raidcom add ldev -parity_grp_id 01-01 -ldev_id %%i -capacity 100M ) • Execution result (the text in bold indicates the contents of the error accompanying the invalid configuration definition in the script.) C:\HORCM\etc>raidcom get ldev -ldev_id 1 -cnt 65280 -store ldevconf_65 > ldevconf_65.txt C:\HORCM\etc>raidcom -zt 3_defined_ldev.bat -load ldevconf_65.
• raidcom disconnect path -path_grp -port -external_wwn • raidcom add rcu {-rcu -ssid | -cu_free } -mcu_port -rcu_port For example, if a path is attempted to be added to a port that does not exist, an error is detected. An example of the script where the error is detected and the execution result of the actual Context check are shown below.
It is checked whether the operation is performed for the existing host group. If the host group does not exist, an error is detected. If it is not clear whether the target port or host group exists (if the target port or host group information does not exist in the configuration definition file), the error is not detected. The command as the target of the check is shown below.
Check the operation for LDEV raidcom get ldev {-ldev_id … [-cnt ] | -grp_opt -device_grp_name []} -store Check the operation for Port raidcom get port –port –store Check the operation for Host group raidcom get host_grp –port –store After acquiring the configuration information, execute the script by specifying the configuration file.
Figure 29 LDEV grouping up to and including XP24000/XP20000 Disk Array For P9500 RAID storage systems, RAID Manager can be used to create a group of multiple LDEVs by defining device groups. This is accomplished by defining device groups in either the primary or secondary configuration definition file, but not both. By defining a device group, LDEV information can be changed or defined in one operation. It is not required to modify LDEV information in both configuration definition files.
Figure 30 LDEV grouping from P9500 (device group and copy group) However, for executing replication function commands in RAID Manager, two device groups must be combined and defined as a copy group. When defining a device group or copy group by a command, it can be used from multiple RAID Manager instances because the group information is defined in the storage system.
file to incorporate it into the RAID Manager instance. This can be executed at RAID Manager that supports P9500 or later. • Define a configuration definition file Defines HORCM_LDEV, HORCM_DEV, and HORCM_LDEVG of the configuration definition files of the primary and secondary volumes. For definition details, see “Configuration definition file” (page 23). A device name is a name given to an LDEV in each device group.This is equivalent to the dev_name definition of HORCM_DEV.
Notes when specifying a device name • Multiple device names can be defined in one LDEV (Max: 1,024names). • The length of a device name must be up to 32 characters. • In the device group that does not become an element of copy a group, the same device name can be used in the same device group. • In the device group that becomes an element of a copy group, a device group name must be unique in the device group.
Device group creation Creating a device group by specifying a subject of multiple LDEV IDs and device group names of the device groups to be created. • Use Cases The following shows use cases that can be created a device group. ◦ Creating a device group configured of simplex volumes with different LDEV names. In this example, the device group can be created. ◦ Creating a device group configured of a single volume and a paired volume with different LDEV names.
• Use Cases The following shows use cases that can be added an LDEV to a device group. ◦ Adding an LDEV (simplex volume) with a different device name to a device group. ◦ Adding an LDEV (paired volume) with a different device name to a device group. ◦ Adding an LDEV to a device group already including the same device name. The device name can be duplicated in the case of not creating the copy group by specifying a device group.
LDEV can be deleted from the device group associating a copy group. The pair status does not change even if the LDEV is deleted from the device group. • Use Cases The following shows use cases that can be deleted an LDEV from a device group. ◦ Deleting an LDEV (simplex volume) not associated with a copy group from a device group. • Deleting an LDEV (paired volume) not associated with a copy group from a device group.
from the device, the relevant device group is deleted. And, even if a device group is deleted, the pair status of the pair in the device group does not change. • Use Cases The following shows use cases that can be deleted an LDEV from a device group. ◦ Deleting a device group configured of simplex volumes and not associated with a copy group. • Deleting a device group configured of a simplex volume and a paired volume and not associated with a copy group.
When creating a copy group • In case of creating a copy group by executing a command, a copy group cannot be created through direct specification of multiple LDEVs. Create a copy group by specifying a device group. • In one device group associated as a copy group, the same device name cannot be defined. • Copy groups with the same name cannot be defined within the same storage system. • One device group cannot be defined to multiple copy groups.
Copy group creation Specifying two device groups and creating a copy group. The same device name must not be defined for any LDEVs in a specified device group. A copy group can be created whether the LDEV in the device group is paired status or not. • Use cases The following shows use cases that can be created a copy group. ◦ Creating a copy group in cases where two device groups are configured of simplex volumes and the device names and the LDEV numbers in the respective device groups are the same.
With the same device name, the operation for the device group associated with a copy group cannot be performed. • Use cases The following shows use cases that can be added an LDEV to the device group associating a copy group. ◦ Adding an LDEV with a different device name (simplex volume) to a device group forming a copy group. ◦ Adding an LDEV with a different device name (paired volume) to a device group forming a copy group.
It is not possible to delete LDEVs directly from the copy group. • Use cases The following shows use cases that can be deleted LDEVs from the device group forming a copy group. ◦ Deleting an LDEV (simplex volume) from a device group forming a copy group. ◦ Deleting an LDEV (paired volume) from a device group forming a copy group. Copy group deletion Deleting a copy group by specifying a defined copy group.
• Use cases A copy group can be deleted even if it is configured of simplex volumes or paired volumes. The following shows use cases that can be deleted a copy group. ◦ Deleting a copy group configured of simplex volumes. ◦ Deleting a copy group configured of paired volumes. Pair operation by specifying a copy group Specifying a copy group and creating a pair. Pairs are created for which the same device names of LDEV defined in respective device groups of the LDEVs.
If there is no target LDEV to be a pair in the copy group, the process is terminated by detecting an error.
• Use cases As an example of pair operation, the following shows use cases that can be created a pair by specifying a copy group. ◦ Creating a pair in cases where the device names and the numbers of LDEVs in two device groups in a copy group configured of simplex volumes are the same. In the following example, pairs are created with LDEVs that have the same device name, A to A and B to B.
◦ Creating a pair in cases where the numbers of LDEVs in two device groups in a copy group configured of simplex volumes are different. In the following example, pairs are created for the device name A to A and B to B. Pair operations with volumes for mainframe For the P9500 storage system, you can create a pair with LDEVs for mainframe by using RAID Manager.
Displayed pair statuses Pair statuses of mainframe LDEVs are displayed in a same way as those of open LDEVs. However, access permissions to mainframe P-VOLs or S-VOLs are different from those of open volumes. The pair statuses and access permissions to mainframe LDEVs are shown below. For more information about displayed pair statuses of open LDEVs, see (page 134).
Table 20 Pair statuses of Continuous Access Journal/Continuous Access Journal Z (continued) # Pair statuses in Remote Web Console Pair statuses in RAID Manager Access to mainframe P-VOL Open Mainframe Access to mainframe S-VOL Notes Open Mainframe 7 Deleting Deleting PAIR / COPY PAIR / COPY Read / Write Reject enabled pair / in copy 8 HOLD Hold PSUS PSUS Read / Write Reject* enabled suspend 9 HOLDING Holding PSUS PSUS Read / Write enabled suspend 10 PSUS (HLDE) Hlde PSUE PSUE R
Table 22 Comparing multi-platform volumes performance # LU path definition LU path information reported to RAID Manager Business Copy performance Continuous Access Synchronous performance Continuous Access Journal performance 1 LU path is defined. Actual LU path information is reported. Business Copy Z performance Commands are rejected. Commands are rejected. 2 LU path is not defined. Dummy LU number is Business Copy Z reported. performance Commands are rejected. Commands are rejected.
Table 23 Differences in replication commands (continued) # Command Option Description Performance in open system Performance in mainframe system Notes You cannot specify this option in Business Copy and Business Copy Z. *If the capacity of the secondary volume (S-VOL) is larger than that of the primary volume (P-VOL), you cannot create a pair with RAID Manager. To create a Continuous Access Synchronous Z pair with volumes that differ in capacity, use Business Continuity Manager or Remote Web Console.
4 Starting up RAID Manager After you have installed the RAID Manager software, set the command device, created the configuration definition file(s), and (for OpenVMS only) followed the porting requirements and restrictions, you can begin using the RAID Manager software. One or two instances of RAID Manager can be used simultaneously in the UNIX, Windows, and OpenVMS operating system environments. Starting up on UNIX systems One instance To start up one instance of RAID Manager on a UNIX system: 1.
3. 4. Execute the horcmstart.sh script manually to start the RAID Manager instances: # horcmstart.sh 01 Set an instance number to the environment that executes a command: For B shell: # HORCMINST=X X = instance number = 0 or 1 # export HORCMINST For C shell: # setenv HORCMINST X 5. 6. Set the log directory (HORCC_LOG) in the command execution environment as needed. If you want to perform Continuous Access Synchronous operations, do not set the HORCC_MRCF environment variable.
3. 4. Execute the horcmstart script manually to start RAID Manager: D:\HORCM\etc> horcmstart 0 1 Set an instance number to the environment that executes a command: D:\HORCM\etc> set HORCMINST=X X = instance number = 0 or 1 5. 6. Set the log directory (HORCC_LOG) in the command execution environment as needed. If you want to perform Continuous Access Synchronous operations, do not set the HORCC_MRCF environment variable.
Two instances To start up two instances of RAID Manager on an OpenVMS system: 1. Create the configuration definition files. For a new installation, the configuration definition sample file is supplied (SYS$POSIX_ROOT:[HORCM.etc]horcm.conf). Copy the file twice, once for each instance. $ COPY SYS$POSIX_ROOT:[HORCM.etc]horcm.conf SYS$POSIX_ROOT:[etc] horcm0.conf $ COPY SYS$POSIX_ROOT:[HORCM.etc]horcm.conf SYS$POSIX_ROOT:[etc] horcm1.
C:\HORCM\tool\>svcexe • Usage for adding [HORCM_START_SVC]: svcexe /A=command_path ◦ for deleting [HORCM_START_SVC]: svcexe /D ◦ for specifying a service: svcexe /S=service_name ◦ for dependent services: svcexe /C=service_name,service_name This command example uses HORCM0 for registering the service name for HORCM instance#0: • 1. 2. 3. 4. 5. Example for adding [HORCM0]: svcexe /S=HORCM0 “/A=C:\HORCM\tool\svcexe.
5 Provisioning operations with RAID Manager Provisioning operations can be performed using RAID Manager. About provisioning operations Provisioning operations can be performed using RAID Manager. For details about the provisioning, see HP P9000 Provisioning for Open Systems User Guide. NOTE: The operation of refreshing window on Remote Web Console or SVP might be delayed while executing provisioning operation on RAID Manager.
When executing an asynchronous command, execute a command or a script with the following procedures. 1. Execute a raidcom reset command_status command. Resets the error information of asynchronous command in the storage system. 2. Execute an asynchronous command. Executes the asynchronous command. 3. Execute a raidcom get command_status command. Checks if all the asynchronous command processing are done or if no error is occurred.
Table 24 Asynchronous commands of the configuration setting command (continued) Function Command syntax Creating Journal/ registering journal volume raidcom add journal -journal_id {-ldev_id …[-cnt ] the journal | -grp_opt -device_grp_name []} Deleting Journal/ Deleting journal volume from the journal raidcom delete journal -journal_id [-ldev_id | -grp_opt -device_grp_name
Operation type Description Corresponding command Display resource group information. raidcom get resource Add resource group. raidcom add resource -resource_name [-resource_id |-ldev_id | -port | -port | -parity_grp_id | -external_grp_id ] Delete resource group.
Operation type (See the manual: HP P9000 Provisioning for Open Systems User Guide or HP P9000 Provisioning for Mainframe Systems User Guide) Description Corresponding command -device_grp_name []}[-user_threshold [] ] Create pool for Snapshot.
Operation type Description Corresponding command -device_grp_name []}[-user_threshold [] ] LU path Extend the capacity of a pool for Snapshot.
Operation type Description Corresponding command Change cache mode of external volume. raidcom modify external_grp -external_grp_id -cache_mode < y|n > Control cache write of external volume. raidcom modify external_grp -external_grp_id -cache_inflow < y|n > Modify ownership MP Blade of external volume. raidcom modify external_grp -external_grp_id -mp_blade_id Add external path.
Operation type Description Corresponding command Delete LDEV from device group. raidcom delete device_grp -device_grp_name -ldev_id … [-cnt ] Display device group information. raidcom get device_grp [-device_grp_name ] Create copy group. raidcom add copy_grp -copy_grp_name [device group name] [-mirror_id -journal_id ] Delete copy group.
Operation type Description (See the following manuals: HP P9000 Continuous Access Synchronous User Guide Guide, HP P9000 Continuous Access Synchronous for Mainframe Systems User Guide, and HP P9000 Continuous Access Journal User Guide Corresponding command -grp_opt -device_grp_name []} [-mp_blade_id | -timer_type ] Delete journal volume from Journal/ Delete journal.
Operation method Specify the name of device group (max: 32 characters) and the device name in the device group (max: 32 characters), and execute a command. The following shows an example to map the LDEV to the LUN by specifying a device group. When the both of device group name and device name, the operation is executed for the LDEV that matches to the specified device name in the device group.
PORT GID HMD LUN NUM LDEV CM Serial# HMO_BITs CL8-A 0 LINUX/IRIX 0 1 17000 - 64577 CL8-A 0 LINUX/IRIX 1 1 17001 - 64577 CL8-A 0 LINUX/IRIX 2 1 17002 - 64577 CL8-A 0 LINUX/IRIX 3 1 17003 - 64577 The following shows the example for specifying device groups and creating a journal.
Resource group operations Creating resource groups To create resource groups, perform the following provisioning operations. Step Operation Description Command 1 Creating resource groups Creates resource groups. raidcom add resource -resource_name 2 Allocationg resources Specifies resources that are allocated to to resource groups meta_resource (resource group), and allocates resources to created resource groups.
Step Operation Description Command At that time, allocation of resources to the resource group: meta_resource must be finished. 3 Allocating resources to resource groups Specifies resources that are allocated to meta_resource (resource group), and allocates resources to resource groups.
Step Operation Description Command 3 Setting host mode Specify port and set host mode for host group. raidcom modify host_grp -port [] -host_mode < host mode> [-host_mode_opt … ] 4 Displaying host group information Display host group information and confirm raidcom get host_grp -port [] 5 Adding host to host group Register host to host group of the port.
Step Operation Description Command 5 Configuring MP blades of LDEVs Configures MP blades of created LDEVs. raidcom modify ldev -ldev_id -mp_blade_id 6 Displaying a LDEV information Displays an information of created LDEV, and confirms an execution result of the command. raidcom get ldev -ldev_id … [-cnt ] [-key ] Script examples The following shows the script examples of internal volume (mainframe volume) operations.
Figure 32 Script examples of internal volume (open volume) operation (1/2) Internal volume operations 107
Figure 33 Script examples of internal volume (open volume) operation (2/2) Script examples The following shows the script examples of internal volume (mainframe volume) operations.
Figure 34 Script examples of internal volume (mainframe volume) operation Virtual volume (Thin Provisioning) operations Creating virtual volumes (Thin Provisioning) to create LDEVs of virtual volumes (Thin Provisioning) and make the LDEVs available to the host, perform the following provisioning operations. Step Operation overview Description Executed command 1 Setting port Make enabled the LUN security of port. Modify setting such as port topology and data transfer speed as needed.
Step Operation overview Description Executed command mode> [-host_mode_opt … ] 4 Displaying host group information Display host group information and confirm raidcom get host_grp -port [] 5 Adding host to host group Register host to host group of the port.
Script examples The following shows the script examples of virtual volume (Thin Provisioning) operation.
Figure 36 Script examples of virtual volume (Thin Provisioning) operation (2/3) Figure 37 Script examples of virtual volume (Thin Provisioning) operation (3/3) 112 Provisioning operations with RAID Manager
Virtual volume (Thin Provisioning Z) operations Creating virtual volumes (Thin Provisioning Z) To create LDEVs of virtual volumes (Thin Provisioning Z) and make the LDEVs available to the host, perform the following Provisioning operations. Step Operation overview Description Executed command 1 SSID settings (arbitrarily) Configures the SSID unless it is configured.
Figure 38 Script examples of virtual volume (Thin Provisioning Z ) operation (1/2) Figure 39 Script examples of virtual volume (Thin Provisioning Z) operation (2/2) Virtual volume (Smart Tiers) operations Operational flow When using the V-VOL(Smart Tiers), create the pool first using a single tier type of pool volumes, then enable Smart tiering and add the remaining tier's pool volumes. You must monitor the performance of the pool before migrating.
Note *1: A multi tiered pool cannot be created initially using raid manager. You must first create the pool using a single tier type, then enable smart and add the additional tier pool volumes. Note *2: When the multiple tiering pool is enabled, the tiering control is set to "Manual" automatically. To change the setting to "Auto", it is required to execute from Remote Web Console. CAUTION: The operations are explained here are executable by the storage administrator only.
Creating virtual volumes (Smart Tiers) Use the following operations to create LDEVs of virtual volumes (Smart Tiers) and making the LDEVs available to the host. 116 Step Operation overview Description Executed command 1 Setting port Make enabled the LUN security of port. Modify setting such as port topology and data transfer speed as needed. raidcom modify port -port -security_switch y 2 Creating host group Specify port and create host group.
Step Operation overview Description Executed command 15 Creating LDEV (V-VOL) Specify pool and create LDEV (V-VOL). raidcom add ldev -pool { | | snap} -ldev_id -capacity [-emulation ][-location ][-mp_blade_id ] 16 Creating LDEV (V-VOL) nickname (arbitrary) Create nickname for created LDEV (V-VOL). raidcom modify ldev -ldev_id -ldev_name This operation is arbitrary.
Figure 40 Script examples of virtual volume (Smart Tiers) operation (1/3) 118 Provisioning operations with RAID Manager
Figure 41 Script examples of virtual volume (Smart Tiers) operation (2/3) Virtual volume (Smart Tiers) operations 119
Figure 42 Script examples of virtual volume (Smart Tiers) operation (3/3) External volume operations Creating external volumes Use the following provisioning operations to create LDEVs of external volumes and make the LDEVs available from the host.
Step Operation overview Description 5 Modifying external volume option Modify external volume option (cache raidcom modify external_grp mode, inflow mode, and MP blade setting). -external_grp_id {-cache_mode < y|n > | -cache_inflow < y|n > | -mp_blade_id } 6 Checking external volume information Display external volume information and confirm result of executing command. 7 Setting external path Set external path. Execute the required number of commands.
Figure 43 Script Examples of External Volume Operation (1/3) Figure 44 Script Examples of External Volume Operation (2/3) 122 Provisioning operations with RAID Manager
Figure 45 Script Examples of External Volume Operation (3/3) Cache Partition operations Cache Partition operations using RAID Manager include migrating LDEVs, parity groups, and external volume groups to other CLPRs. • For information about Cache Partition operations, including important warnings and restrictions, see the HP P9000 Cache Partition User Guide. • For details about the RAID Manager commands for Cache Partition operations, see the HP P9000 RAID Manager Reference Guide.
Displaying CLPR information The raidcom get clpr command lists and displays the status of the CLPRs in the storage system. If no CLPRs have been created, CLPR0 is displayed as entire cache.
6 Data replication operations with RAID Manager Data replication operations can be performed using RAID Manager.
Figure 46 Concept of paired volumes Addressing paired logical volumes: The correspondence of paired logical volumes to their physical volumes is defined by describing the paired logical volume names and group names in the configuration definition files of each server. It is possible to define a server for the paired logical volumes in units of group name. Each paired logical volume must belong to a group in order to determine the corresponding server.
Continuous Access Synchronous operations, please see the HP P9000 Continuous Access Synchronous User Guide for your storage system. Business Copy operations Figure 47 (page 127) illustrates a Business Copy configuration. The Business Copy commands also support the functionality that links the system operation for the purpose of volume backup among UNIX servers managed by the operating system.
Figure 48 Business Copy duplicated mirrors Business Copy cascading pairs Business Copy provides a cascading function for the Business Copy S-VOL. The cascading mirrors of the S-VOL are expressed as virtual volumes using the mirror descriptors (MU#1-2) in the configuration diagram as shown below. The MU#0 of a mirror descriptor is used for connection of the S-VOL.
Figure 49 Business Copy cascade volume pairs Restrictions for Business Copy cascading volumes Pair Creation. Pair creation of S-VOL (oradb1) can only be performed after the pair creation of S/P-VOL (oradb). If you create the oradb1 pair first without creating the oradb, the subsequent oradb creation will be rejected with EX_CMDRJE or EX_CMDIOE. Pair splitting.
Restriction for Continuous Access Synchronous/Business Copy cascading volumes Pair restore (resynchronization from S-VOL (oradb1) to S/P-VOL) can only be performed when the Continuous Access Synchronous S-VOL (oradb) and the P-VOL (oradb2) on the S/P-VOL are in the SMPL or PSUS(SSUS) state. If pairresync of S-VOL (oradb1) is performed when the S/P-VOL (oradb or oradb2) is in any other state, the pairresync -restore option command is rejected with EX_CMDRJE or EX_CMDIOE.
Figure 50 Server failover system configuration In an HA environment, a package is a group of applications that are scripted to run on the secondary host in the event of a primary host failure. When using the HA software (e.g., MC/ServiceGuard), the package can be transferred to the standby node as an operation executed by the system administrator (see Figure 51 (page 131)).
• Pair resynchronization command: Resynchronizes a split volume pair based on the primary volume. The primary volume remains accessible during resynchronization. ◦ Swaps(p) option (Continuous Access Synchronous only). Swaps volume from the S-VOL(P-VOL) to the P-VOL(S-VOL) when the S-VOL(P-VOL) is in the suspended state and resynchronizes the NEW_S-VOL based on the NEW_P-VOL.
Figure 53 Continuous Access Synchronous local system configuration Continuous Access Synchronous, Business Copy, and Continuous Access Journal operations Continuous Access Synchronous/Business Copy volumes Continuous Access Synchronous commands allow you to create volume pairs consisting of one primary volume (P-VOL) and one secondary volume (S-VOL). The Continuous Access Synchronous P-VOL and S-VOL can be in different storage systems.
Continuous Access Synchronous/Business Copy/Continuous Access Journal volume status Each Continuous Access Synchronous pair consists of one P-VOL and one S-VOL, and each Business Copy pair consists of one P-VOL and up to nine S-VOLs when the cascade function is used. Table 26 (page 134) lists and describes the Continuous Access Synchronous and Business Copy pair status terms. Table 27 (page 135) lists and describes the Continuous Access Journal pair status terms.
Table 27 Continuous Access Journal pair status Status Continuous Access Journal Pair Status Primary Secondary SMPL Unpaired volume R/W enabled R/W enabled PAIR The pair is synchronized. Updates to the P-VOL are duplicated on the S-VOL. R/W enabled R enabled COPY In paired state, but initial copy, pairsplit, or resync operation is not complete. Includes COPY(PD), COPY(SP), and COPY(RS) status.
Table 28 Pair status versus Continuous Access Synchronous and Continuous Access Journal commands - Continuous Access Synchronous command paircreate pairsplit pairresync # Status Copy Nocopy -r or -rw option -P option -S option Resync 1 SMPL Accepted 2 Accepted 3 Rejected Rejected Acceptable Rejected 2 COPY Acceptable Acceptable Accepted 4 Rejected.
NOTE: If the P-VOL does not have Write in the PAIR state, then data identical with an S-VOL is guaranteed. Therefore, when using the S-VOL with the SMPL state, after stopping Write to the P-VOL, generate a paired volume, and then split the paired volume after confirming that the paired volume has the PAIR status. In the PSUE state, Business Copy does not manage differential data at the P-VOL or S-VOL.
T2: P-VOL_PSUS from/to S-VOL_SSUS(WE) P-VOL_PSUS from/to S-VOL_SSUS(WE) • If you attempt the pairevtwait -s psus in P-VOL_PSUS & S-VOL_COPY state, then pairevtwait will return immediately even if the S-VOL is still in S-VOL_COPY state because P-VOL is already in P-VOL_PSUS state. If you want to wait the “S-VOL_SSUS” state, and then you must check the status of the S-VOL becomes “S-VOL_PSUS” via the return code using pairvolchk -ss command on S-VOL side or pairvolchk -ss -c command on P-VOL side.
Figure 54 Continuous Access Asynchronous consistency groups Restrictions • Group definition of Continuous Access Asynchronous/Continuous Access Journal/Continuous Access Synchronous volume: All volumes in a group must be contained within the same storage system. If two or more groups of RAID Manager include the same CT group (CTGID), then pair operation of the group specification is handled in CT group entirety.
Continuous Access Asynchronous and Continuous Access Journal volume characteristics Continuous Access Asynchronous/Continuous Access Journal volumes have the following characteristics: • PAIR state: A Continuous Access Asynchronous pair changes to the PAIR status as soon as all pending recordsets have been placed in the queue at the primary volume, without waiting for the updates to complete at the secondary volume.
to store the next new write data. The copy pending timeout group option is defined using Remote Web Console and specifies the maximum delay between the M-VOL update and the corresponding R-VOL update. The range for the copy pending timeout option is 1-255 seconds (600 seconds for Continuous Access Journal), and default value is 90 seconds (60 seconds for Cnt Ac-J).
Table 32 State table for Continuous Access Synchronous vs.
Continuous Access Synchronous/Continuous Access Asynchronous and Continuous Access Journal fence level settings Continuous Access Synchronous volume pairs are assigned a fence level for write I/Os to ensure mirroring consistency of critical volumes. When the secondary volume takes over from the primary volume, the takeover action is determined according to the pair status and fence level of the corresponding secondary volume.
Table 33 Relationship between Continuous Access Synchronous pair statuses and fence levels (continued) Continuous Access Synchronous pair status of volume Fence level and write response Data 1 Status 2 Never 3 Async 4 and are also noted in a bitmap for future transfer. Due to the use of a bitmap in the suspend state, data consistency is not assured during a copy state resync.
Figure 58 Snapshot and volume mapping Snapshot volumes The specifications for Snapshot volumes are: • Allowable type of paired volume: The supported volume type is OPEN-V only for P VOL, and OPEN-0V for S VOL. • Number of volumes (Snapshot) can be paired: This depends on P VOL capacity, Snapshot pool capacity, and shared memory capacity on the RAID storage system. • Duplicated writing mode: Copying on write. • Number of mirror volumes: Up to 64 secondary volumes can be defined for each P VOL.
A V-VOL has the following characteristics: • It appears as "OPEN-0V" to identify a V-VOL easily via the SCSI Inquiry or RAID Manager. • A V-VOL unmapped to the S-VOL of a Fast Snap or Snapshot will reply to a SCSI Inquiry, but Reading and/or Writing is not allowed. LDEV will reply the capacity setting as an LU to SCSI Read Capacity. • A V-VOL that has become the S-VOL of a Fast Snap or Snapshot will reply to a SCSI Inquiry, and Reading and/or Writing is allowed.
Table 35 Pair status relationship to Snapshot commands - Snapshot Command paircreate pairsplit pairresync Pair Status No -split -split -E option -C option -S option Resync 1 SMPL Accepted 2 Accepted*2 to 4 Rejected Rejected Acceptable Rejected 2 COPYRCPY Acceptable Accepted* Accepted* 5 Accepted* Accepted 1 Acceptable 3 PAIR Acceptable Accepted*4 Accepted* 5 Accepted 4 Accepted 1 Acceptable 4 PSUS (PFUS) Rejected Acceptable Accepted* 5 Acceptable Accepted 1 Accepted*
Figure 59 Auto LUN configurations (1) Command specification RAID Manager operates the volume migration by specifying to the horcm*.conf as same BC and Cnt Ac-S, because the volume migration using RAID Manager is necessary to be defined the mapping for the target volume. MU# (of SMPL as BC) that is not used because BC is used for Auto LUN operation. An original volume for the migration is defined as P-VOL. A target volume for the migration is defined as S-VOL.
(5) HORCM instance It is possible to describe the original and target volume for the volume migration to MU# as another group in horcm*.conf for HORCM instance of BC and /or Cnt Ac-S. Also, it is possible to define the original and target volume for the volume migration in the horcm*.conf as HORCM instance independent from BC/Cnt Ac-S. Commands to control Auto LUN (1) Command for Auto LUN RAID Manager supports the volume migration by adding an option (-m cc) to the paircreate command.
It is possible to confirm the status for Auto LUN by using “-fe” option of the pairdisplay command. pairdisplay -g -fe -fe This option is used to display the serial# and LDEV# of the external LUNs mapped to the LDEV and additional informations for the pair volume. This option displays the informations above by adding to last column, and then ignores the format of 80 column. This option is invalid if the cascade options (-m all,-m cas) are specified.
sdv sdw • CL2-G CL2-G 63528 63528 2768 2769 - s/s/ss s/s/ss 000B 000B U:00000 E:16384 OPEN-0V OPEN-V R:Group: This displays the physical position of an LDEV according to mapping of LDEV in the RAID storage system. LDEV mapping R: Group RAID Group RAID Level RAID Group number - Sub number 1 : RAID1 5 : RAID5 6 : RAID6 Snapshot S-VOL S PoolID number Unmapped U 00000 External LUN E External Group number Example in Linux: # ls /dev/sd* |.
Table 36 Command issues and pairing status transition Command: Pair Creation Pair Splitting Pairing Status CC: -m cc Simplex -S 1. 1 SMPL Accepted Acceptable 2 to 3 2 to 4 1. 2 COPY to 3 Acceptable Accepted 1. 3 PSUS Accepted 1 1. 4 PSUE PDUB Accepted 1 Legend: Accepted: A command is accepted and executed. When the command execution succeeds, the status changes to that of the shown number. Accepted: A command is accepted and executed.
Restrictions for Auto LUN Auto LUN must be used within the following restrictions: • Business Copy (HOMRCF). The operation for the volume migration must be operated at the “SMPL” or “PAIR” or “COPY” state. If not, paircreate -m cc command is rejected with EX_CMDRJE or EX_CMDIOE. Also Business Copy cannot be operated to CC_S-VOL moving in Auto LUN. In copying CC_S-VOL, the copy operation for the volume migration is stopped, if the Business Copy pairsplit command is executed.
Thus, RAID Manager supports Cnt Ac-J MxN for open systems in the four ways described in “Policy ” (page 154). Policy All data consistency of the CT group across multiple storage systems is maintained by RAID Manager. The storage system supports only basic functions; there is no relation between storage systems in order to simplify testing and configurations. RAID Manager supports Continuous Access Journal MxN in the following ways.
HORCM CTQM #groupinterval (10ms)mode(optional oradb300 where • group is to be allowed as a group across multiple storage system • interval is the interval for the CTQ-Marker, recommended as a few second. • mode is the run mode for the CTQ-Marker (timestamp). The default run mode is freeze/run. This does not normally need to be specified. If “run” is specified, then the timestamp is issued without freeze.
# pairdisplay -g ora -v jnlt JID MU CTG JNLS AP U(%) Q-Marker 001 1 0 PJNN 1 0 00000c76 60 300 40 002 1 0 SJNN 1 0 00000c62 60 300 40 001 1 0 PJNN 1 0 00000c3a 60 300 40 002 1 0 SJNN 1 0 00000c33 60 300 40 # pairdisplay -g horc0 -v jnl -fe JID MU CTG JNLS AP U(%) Q-Marker Num LDEV# CTQM 016 2 0 PJSN 1 0 0000bb1b 1 32768 018 2 0 SJSN 1 0 0000bb1b 1 32770 0000187f 017 2 0 PJSN 1 0 00000011 1 32769 019 2 0 SJSN 1 0 00000011 1 32771 0000187f NOTE: Q-CNT D-SZ(BLK) 20 1633672703 20 1633672703 Seq# DOW PBW APW
(3) pairsplit -S option • Issues Freeze to CT group on each MCU • Issues Delete & Run to make a deleting state for CT group on each MCU • Searches/commits a minimum matching point of the CTQ-Marker on RCU via MCU (in other words, do Journal Restore with CTQ-Marker) • Repeats above until detecting an EOM (End Of Marker) marked on MCU on all RCU via MCU • Issues End of Delete to terminate a deleting state, after committed with EOM (End Of Marker) on all RCU Exception: If an uncommitted state(that is
• Repeats above until detecting an EOM(End Of Marker) marked on all RCU via RCU • Issues End of Delete to terminate a deleting state Notice on system operation RAID Manager does not change the command options for supporting Continuous Access Journal MxN Open. However, the output of the command is added so that the command can display the CT group and Q-Marker for each DKC, because the CT group and Q-Marker are managed on each DKC.
To terminate this status, re-execute the RAID Manager command, then terminate suspending/deleting status after “JNL Consistency Restore”. (8) Detecting inconsistent CTQ-Marker The pairsplit command checks data consistency with CTQ-Marker across multiple DKCs. If an inconsistent CTQ-Marker is detected, then it returns with EX_VOLCUR after changed to suspend status. This error needs to confirm if CTQMs are the same on S-VOL on each DKC using the “pairdisplay -v jnl -fe” option.
(1) Cnt Ac-J 2x2 160 Data replication operations with RAID Manager
(2) Cnt Ac-J 2x1 Remote volume discovery In the configuration separating “Storage admin server (RAID Manager server)” and each production server, it is difficult to verify/check the volumes on the production servers and the volumes described to the horcm.conf on RAID Manager server. In this configuration, you cannot use the following RAID Manager capabilities.
Figure 60 Volume discovery Discovering a remote volume The inqraid command exports the device information discovered on the production servers. The device information includes "Keyword, Serial#, Ldev#, Device file name..". The raidscan -find inst command on RAID Manager server imports the device information, and registers it into the HORCM daemon. The inqraid command is needed only for discovering LUNs on the production server.
# ls /dev/rdsk/c1t* | inqraid -CLI -export | ssh raidscan -find verify DEVICE_FILE Group PairVol PORT TARG LUN M SERIAL LDEV /dev/rdsk/c1t0d0s2 - 64015 0 /dev/rdsk/c1t0d1s2 - 64015 1 /dev/rdsk/c1t0d2s2 G1 G1-000 CL4-G-1 57 2 64015 2 /dev/rdsk/c1t0d3s2 G1 G1-001 CL4-G-1 57 3 64015 3 /dev/rdsk/c1t0d4s2 - 64015 4 /dev/rdsk/c1t0d5s2 - 64015 5 /dev/rdsk/c1t0d7s2 - 64015 7 (3) A way to import with horcmstart.
7 Data protection operations with RAID Manager Data protection operations can be performed using RAID Manager. Data protection operations User data files are normally placed on a disk through a software layer such as a file system, LVM, disk driver, SCSI protocol driver, bus adapter, and SAN switching fabric. Data corruption can happen due to software layer bugs or human error. RAID Manager Data Protection Facility does not prevent these types of errors.
Restrictions on Data Retention volumes • • File systems using Data Retention ◦ When using UNIX file system volumes with Data Retention, the volumes must be mounted with the Read Only option by setting the Data Ret after the volumes are unmounted. ◦ When using a Windows file system, use the “-x mount” and “-x umount” RAID Manager command options with the above mentioned procedures. ◦ Data Retention volumes set to Write Protect Mode (Read ONLY) cannot be used for the Windows file system (NTFS, FAT).
Restrictions on Database Validator • • Oracle tablespace location ◦ File system-based Oracle files are not supported by Database Validator. All Oracle tablespace files must be placed on raw volumes (including LVM raw volumes) directly. ◦ If host-based striping is used on raw volumes, then the stripe size must be an exact multiple of the Oracle block size. ◦ Oracle redo log files (including archive logs) must be on separate volumes with respect to the data files (including control files).
an unmirrored HARD-enabled LV, then makes it mirrored on the fly without HARD-enabling all sides of the mirror, that entire LV is exposed to data corruption. • • LVM bad block relocation is not allowed on PVs that are HARD-enabled. Oracle and LVM (VxVM) on HA Cluster Server ◦ If HA Cluster software writes to LVM metadata at regular intervals to confirm whether its disks are available or not, then its LVM’s area must not be checked by Database Validator by using the “-vs SLBA ELBA” option.
Data Protection Facility specifications Only the permitted volumes can be registered in horcm.conf. When creating the horcm.conf file, describe volumes only from the view that the host shows. RAID Manager manages mirror descriptors (Continuous Access Synchronous, Business Copy/MU#0/1/2) as a unit. The Data Protection Facility has two specifications: one must be a volume that you can see from the host such as the Inquiry tool, and the other must be a mirror descriptor volume that was registered in horcm.
Figure 62 Example for the two-host configuration Figure 63 Example for the one-host configuration Target commands for protection The following commands are controlled by the Data Protection Facility: horctakeover, paircurchk, paircreate, pairsplit, pairresync, pairvolchk, pairevtwait, pairsyncwait, raidvchkset, raidvchkdsp (pairdisplay is not included). When the command is issued to non-permitted volumes, RAID Manager rejects the request with error code “EX_ENPERM”.
-find to make horcm.conf, because only permitted volumes are shown with host side view. Following is an example for HP-UX systems: # ioscan -fun | grep rdsk | raidscan -find DEVICE_FILE UID S/F PORT /dev/rdsk/c0t3d0 0 F CL1-D /dev/rdsk/c0t3d1 0 F CL1-D TARG 3 3 LUN 0 1 SERIAL 35013 35013 LDEV 17 18 PRODUCT_ID OPEN-3 OPEN-3 permission command RAID Manager recognizes permitted volumes at the result of the permission command. The permission command is the -find inst option of raidscan.
raidscan –f[d] This option shows the Device_File that was registered on the group of HORCM, based on the LDEV (as defined in the local instance configuration definition file). # raidscan -p cl1-d -fd Port# ,TargetID#,Lun#..Num(LDEV#....)...P/S, Status,Fence,LDEV#,Device_File CL1-D , 3, 0...1(17)............SMPL - - -,c0t3d0 CL1-D , 3, 1...1(18)............
/dev/rdsk/c0t3d1 /dev/rdsk/c0t3d2 /dev/rdsk/c0t3d3 oradb1 oradb - oradev2 oradev3 - c0t3d1 c0t3d2 - 1 1 1 35013 35013 35013 18 19 20 Naming of $HORCMPERM file on Windows systems $HORCMPERM is \WINNT\horcmperm.conf or \WINNT\horcmperm*.conf (* = instance number) by default. type $HORCMPERM | x:\HORCM\etc\raidscan.exe -find inst # The following are an example to permit the DB Volumes. # Note: a numerical value is interpreted as Harddisk#.
Environment variables $HORCMPROMOD This environment variable turns protection mode ON as specified in the following table. If your command device is set for non-protection mode, this parameter sets it to protection mode.
8 Examples of using RAID Manager commands Examples are provided to help you perform RAID Manager commands. Group version control for mixed storage system configurations Before executing each option of a command, RAID Manager checks the facility version of the storage system internally to verify that the same version is installed on mixed storage system configuration. If the configuration includes older storage systems (e.g.
Figure 65 LDM volume configuration Volume discovery function RAID Manager supports the volume discovery function on three levels showing the relationship between LDM volumes and the physical volumes. • Physical level. RAID Manager shows the relationship between PhysicalDrive and LDEV by giving $Physical as a KEY WORD for the discovery. • LDM volume level. RAID Manager shows the relationship between [LDM volume and PhysicalDrives] and LDEV by given $Volume as KEY WORD for the discovery.
G:\Dmt1\Dsk2 G:\Dmt1\Dsk3 CL2-K CL2-K 61456 61456 inqraid $Volume -CLI DEVICE_FILE PORT \Vol2\Dsk4 \Vol44\Dsk0 CL2-K \Vol45\Dsk0 CL2-K \Dmt1\Dsk1 CL2-K \Dmt1\Dsk2 CL2-K \Dmt1\Dsk3 CL2-K inqraid $Phy -CLI DEVICE_FILE PORT Harddisk0 CL2-K Harddisk1 CL2-K Harddisk2 CL2-K Harddisk3 CL2-K Harddisk4 - • - s/s/ss s/s/ss 0005 1:01-11 OPEN-3 0005 1:01-11 OPEN-3 SERIAL 61456 61456 61456 61456 61456 LDEV CTG 194 194 256 257 258 - H/M/12 s/s/ss s/s/ss s/s/ss s/s/ss s/s/ss SSID 0004 0004 0005 0005 0005 R:Gro
MOUNTVOL [drive:]path VolumeName MOUNTVOL [drive:]path /D MOUNTVOL [drive:]path /L \\?\Volume{56e4954a-28d5-4824-a408-3ff9a6521e5d}\ G:\ \\?\Volume{bf48a395-0ef6-11d5-8d69-00c00d003b1e}\ F:\ You can determine what \\?\Volume{guid}\ is configured, as follows: inqraid $Volume{bf48a395-0ef6-11d5-8d69-00c00d003b1e} -CLI DEVICE_FILE PORT SERIAL LDEV CTG H/M/12 SSID R:Group \Vol46\Dsk1 CL2-K 61456 193 - S/s/ss 0004 1:01-10 raidscan -pi $Volume{bf48a395-0ef6-11d5-8d69-00c00d003b1e} -find DEVICE_FILE UID S/F PORT
Offline backup using raidscan-find sync for Windows file system: The raidscan-find sync command flushes the system buffer associated with a logical drive through finding a Volume{guid} corresponding to a group of the configuration file, without using the -x mount and -x umount commands. The following examples are for group ORB. P-VOL Side S-VOL Side Close all logical drives on the P-VOL by application. • Flush the system buffer for NEW S-VOL data using raidscan -pi $Volume -find sync -g ORB.
The raidscan-find sync command flushes the system buffer through finding a logical drive corresponding to a group of the configuration file, without using the -x mount and -x umount commands. The following examples are for group ORB. P-VOL Side S-VOL Side Freeze DB on opening P-VOL by application. • Back up the S-VOL data. • Flush the system buffer for P-VOL using the raidscan -pi $LETALL -find sync -g ORB.
to avoid such problems is to transport to another host outside the cluster, but this enforces to set up a backup server, so RAID Manager supports a facility to put back the signature as a second way. The signature can be changed by using the dumpcfg.exe command attached to Windows resource kits, but if the S-VOL is created with the Noread option and the system is rebooted, then the dumpcfg.
GPT disk for Windows Windows supports the basic disk called GPT disk using GUID partition instead of the Signature. The GPT disk also can be used as an S-VOL of the BC. Therefore, RAID Manager supports saving/restoring the GUID DiskId of the GPT Basic disk to the inqraid command.
Directory mount facility for Windows systems The attached mountvol command into Windows supports the directory mount, but it does not support the directory mount function that flushes the system buffer associated to a logical drive such as in UNIX systems. The directory mount structure on Windows is only symbolical link between a directory and Volume{guid}, illustrated in Figure 68 (page 182) below.
Volume{cec25efe-d3b8-11d4-aead-00c00d003b1e}\Vol3\Dsk0 - OPEN-3-CVS-CM CL2-D 62496 256 [ Mount used DefineDosDevice() ] NOTE: This may forcibly dismount the mounted volume due to LOG-OFF of Windows. For example: C:\HORCM\etc>raidscan -x mount E: Volume{cec25efe-d3b8-11d4-aead-00c00d003b1e} E: <+> HarddiskVolume3 [ Mount used Directory mount ] NOTE: This prevents the forcible removal of a volume due to LOG-OFF of Windows.
CL1-An where n: unit ID for multiple RAID • Specifying the port name with a host group CL1-A-g where g: host group CL1-An-g where n-g: host group=g on CL1-A in unit ID=n Commands and options including a host group (1) Specifiable command for host group The following commands can specify a host group with the port strings: • raidscan -p , raidar -p , raidvchkscan -p # raidscan -p CL2-D-1 PORT# /ALPA/C,TID#,LU#.Num(LDEV#....)...
The purpose of RAID Manager SLPR security is to prevent RAID Manager from operating the volumes on another SLPR (SLPR#N) through the command device from the SLPR (SLPR#M) that is assigned to its Host. You can use RAID Manager SLPR Security by defining the command device through the Cache Partition feature, so that RAID Manager can protect the target volume. The following example represents the SLPR protection facility.
SLPR configuration examples Single host Figure 70 (page 186) provides an example of when control is denied to the paircreate and raidscan commands in the following cases: • The volume described on RMINST1 is different from the SLPR of the command device, so the paircreate command cannot control the paired volume. • The specified port is different from the SLPR of the command device, so the raidscan -p CL3-A command cannot scan any ports that are defined as SLPR#N.
Figure 72 Operation across SLPRs using a shared command device on a single host Dual Hosts In the following example, the paircreate command is unable to operate the paired volume because the volume described on HostB is different than the SLPR of the command device. Also, the raidscan -p CL3-A command (via both Hosts), is unable to scan a port because the specified port is different than the SLPR of the command device.
Figure 74 Operation across SLPRs using two command devices on dual hosts To operate SLPR#N, share the command device. If HostB has a shared command device for SLPR#N, the paircreate command is permitted. Also, the raidscan -p CL3-A command (via HostA), is allowed to scan a port because the shared command device has the Bitmap settings SLPR#M and SLPR#N.
Figure 76 Continuous Access Synchronous operation using SLPR Using RAID Manager SLPR security 189
9 Troubleshooting Troubleshooting information is provided to assist if you have trouble using RAID Manager. General troubleshooting If you have a problem with the RAID Manager software, first make sure that the problem is not being caused by the UNIX/PC server hardware or software, and try restarting the server. Problem Recommended action Deprecated SCSI ioctl RAID Manager currently uses the ioctl(SCSI_IOCTL_SEND_COMMAND) for sending the control command to the command device. However, in RHEL 4.
is detected, please collect the data in the error log file and trace data (all files in HORCM_LOG directory), and report the failure to your HP representative. Condition Recommended action Startup/shutdown restrictions When the server starts up, the secondary volume may be updated by the primary volume’s server. The secondary volume must not be mounted automatically in the startup sequence. If the secondary volume is used by the LVM, the volume group of the LVM must be deactivated.
Condition Recommended action Maintenance Restart of HORCM is required if the storage system configuration is changed (e.g., microcode exchange, cache memory install/uninstall). Continuous Access Synchronous only: In the case of an error (e.g., single error in cache memory) which made the pair volume is accompanied by maintenance work, the pairresync or paircreate command cannot execute copy rejection.
Condition Recommended action The command of second line will remove “/var/tmp/.lcm*” directory after 720 Hr from HORCM startup, even though RAID Manager command is used. Action: So administrator needs to add the following command in order to avoid this problem: ---------------------------------------------/bin/touch -c /var/tmp/.
Table 40 System log messages (continued) Message ID Condition Cause Recommended action HORCM_101 HORC/HOMRCF and the RAID Manager software communication fails. A system I/O error occurred or an error exists in the HORCM configuration file ($HORCM_CONF). Refer to the HORCM startup log to identify the cause of the error. HORCM_102 The volume is suspended. The pair status was suspended due to code XXXX. Call HP Technical Support.
Table 41 Command error messages (continued) Error code Error Condition Recommended action Value Verify the device or group name and 247 add it to the configuration file of the remote and local hosts. message EX_ENOENT No such device or group The designated device or group name does not exist in the configuration file. EX_ENODEV No such device The designated device name Verify the device name and add it 246 does not exist in the to the configuration file of the remote configuration file.
Table 41 Command error messages (continued) Error code Error Condition Recommended action Value message ($HORCM_LOG), and call HP Technical Support. EX_CMDRJE An order to the control/command device was rejected The request to the command Verify Continuous Access device failed or was Synchronous/Business Copy rejected. functions are installed. Note: This error code is sometimes caused by the operating system and reported as EX_CMDIOE instead of EX_CMDRJE (see next row).
Table 41 Command error messages (continued) Error code Error Condition Recommended action Value Please issue the pairresync 234 command manually to the identified failed paired volume to try to recover it. If the trouble persists, contact HP Technical Support. message EX_EWSUSE Pair suspended at WAIT state Detected a suspended status (PSUE) for the paired volume, before it made it to the designated status.
Table 41 Command error messages (continued) Error code Error Condition Recommended action Value 217 message EX_ENOCTG Not enough CT groups in the RAID CTGID could not be registered due to being beyond the max number of CT groups (0-255 for XP24000/XP20000 Disk Array, 0-255 for XP12000 Disk Array/XP10000 Disk Array, 0-127 for XP1024/XP128 Disk Array, 0-15 for 7700E)) for an async volume. Choose an existing CTGID (use pairvolchk to display CTGIDs).
Table 41 Command error messages (continued) Error code Error Condition Recommended action Value message EX_ESPERM Permission denied with the SLPR A specified command device Please make the SLPR so that the 207 does not have a permission target port and the command device to access other SLPR. belongs to the same SLPR. EX_ENOPOL Not enough Pool in RAID Could not retain the pool for executing a command due to be exceeded the threshold rate.
Table 41 Command error messages (continued) Error code Error Condition Recommended action argument of option exceeded the maximum. of option, or the total number of characters are to be appropriate number of characters. Value message EW_MAXARG Maximum argument The total number of option or the argument of option exceeded the maximum. Check the total number of option or 131 argument of option. EW_ENFILE No such file The specified file dies not exist.
Table 42 Generic error codes (horctakeover and pair commands) (continued) Category Error code Error message Value EX_ERANGE Result too large 244 EX_ENAMLG File name too long 243 EX_INVRCD Invalid return code 226 Configuration EX_ENOGRP No such group 239 (Unrecoverable) EX_ENOENT No such device or group 247 EX_ENODEV No such device 246 EX_ENLDEV No such LDEV within the RAID 227 EX_ENOUNT No such RAID unit 219 EX_INVMUN Invalid mu# with HORC or HOMRCF 220 EX_ENQSER Unmatched
Table 43 Generic error codes (raidscan, raidqry, raidar, horcctl) Category Error code Error message Value Syntax for Argument EX_REQARG Required Arg list 254 (Unrecoverable) EX_INVARG Invalid argument 253 EX_INVNAM Invalid name of option 249 EX_UNWOPT Unknown option 252 EX_UNWCOD Unknown function code 238 EX_UNWCMD Unknown command 230 EX_ERANGE Result too large 244 EX_ENAMLG File name too long 243 EX_INVRCD Invalid return code 226 Configuration EX_ENLDEV No such LDEV withi
Table 44 Specific error codes Category Error code Error message Value Volume Status EX_ENQVOL Unmatched volume status within the group 236 (Unrecoverable) EX_INCSTG Inconsistent status in group 229 EX_INVVOL Invalid volume status 222 EX_EVOLCE Pair Volume combination error 235 EX_INVSTP Invalid pair status 228 EX_VOLCUR S-VOL currency error 225 EX_VOLCUE Local Volume currency error 224 EX_VOLCRE Local and Remote Volume currency error 223 EX_EWSUSE Pair suspended at WAIT state
The following describes the SSB codes that are returned by the replication commands and the configuration setting command (raidcom). SSB code returned by a replication command When one of the replication commands returns an SSB code, refer to the troubleshooting information in the manual corresponding to the product in which it occurs.
Table 45 SSB codes that are returned by the configuration setting command (common) common Error message Executing/ Asynchronous Error code Description SSB1 SSB2 CMDRJE Executing/ 2E10 8000 Get Command Status Asynchronous Unavailable to operate because another application is in progress on Remote Web Console or SVP. CMDRJE Executing 2E11 2205 The resource group to which the operation object belongs is locked by the other user.
Table 46 SSB codes that are returned by raidcom add external_grp command (continued) raidcom add external_grp Error message Executing/ Asynchronous Error code Description SSB1 SSB2 Get Command Status Asynchronous 2E23 4102 Exceeded the number of mapping that can be set per 1 port. Get Command Status Asynchronous 2E23 4303 The operation cannot be done because the number of path in the path group exceeds 8.
Table 48 SSB codes that are returned by raidcom delete external_grp command raidcom delete external_grp Error message Executing/ Asynchronous Error code Description SSB1 SSB2 CMDRJE Executing 2E00 4100 The external volume group # is in the effective range. Get Command Status Asynchronous 2E10 0012 LDEVs in the external volume group are devices that have a CC/XRC attributes. CMDRJE Executing 2E11 0153 The specified external volume group is used in another operation.
Table 48 SSB codes that are returned by raidcom delete external_grp command (continued) raidcom delete external_grp Error message Executing/ Asynchronous Error code Description SSB1 SSB2 Get Command Status Asynchronous 2E30 4111 The external volume is used as a Auto LUN V2 VOL. Get Command Status Asynchronous 2E30 4112 The external volume is used as a Auto LUN V2 VOL.
Table 50 SSB codes that are returned by raidcom disconnect external_grp command raidcom disconnect external_grp Error message Executing/ Asynchronous Error code Description SSB1 SSB2 CMDRJE Executing 2E00 4100 The external volume group is not in the effective range. CMDRJE Executing 2E10 0000 The specified LDEV is used as a Business Copy pair. CMDRJE Executing 2E10 0001 It is used as a Continuous Access Synchronous or Continuous Access Journal pair.
Table 50 SSB codes that are returned by raidcom disconnect external_grp command (continued) raidcom disconnect external_grp Error message Executing/ Asynchronous Error code SSB1 Description SSB2 Call HP Technical Support. CMDRJE Executing 2EDA 0905 An internal error occurred by the operation of external volume. Call HP Technical Support.
Table 52 SSB codes that are returned by raidcom modify port -loop_id command raidcom modify port -loop_id Error message Executing/ Asynchronous Error code Description SSB1 SSB2 CMDRJE Executing B955 044C The specified AL-PA is invalid. CMDRJE Executing B955 054E The specified topology is invalid. CMDRJE Executing B955 05A6 The other than "fabric on" cannot be specified when specifying a topology of the package for Fibre Channel over Ethernet.
Table 54 SSB codes that are returned by raidcom modify port -security _switch command raidcom modify port -security _switch Error message Executing/ Asynchronous Error code Description SSB1 SSB2 CMDRJE Executing B955 044C The specified AL-PA is invalid. CMDRJE Executing B955 054E The specified topology is invalid. CMDRJE Executing B955 05A6 The other than "fabric on" cannot be specified when specifying a topology of the package for Fibre Channel over Ethernet.
Table 55 SSB codes that are returned by raidcom add ldev command (continued) raidcom add ldev Error message Executing/ Asynchronous Error code Description SSB1 SSB2 Get Command Status Asynchronous 2E00 1005 Failed to restore the LDEV that is created to external volume group. CMDRJE Executing 2E00 6000 The specified pool ID is not in the effective range. CMDRJE Executing 2E00 7000 The specified CLPR number is not in the effective range.
Table 55 SSB codes that are returned by raidcom add ldev command (continued) raidcom add ldev Error message Executing/ Asynchronous Error code Description SSB1 SSB2 CMDRJE Executing 2E20 8300 The specified MP Blade is not installed. CMDRJE Executing 2E21 9001 The program product is not installed. CMDRJE Executing 2E21 9002 The program product is not installed. CMDRJE Executing 2E21 9004 The program product is not installed.
Table 55 SSB codes that are returned by raidcom add ldev command (continued) raidcom add ldev Error message Executing/ Asynchronous Error code SSB1 Description SSB2 Call HP Technical Support. CMDRJE Executing 2EF3 0002 The specified parameter is invalid. Check the HP P9000 RAID Manager Reference Guide. ERANGE Result too large Executing - - The value of the capacity is invalid.
Table 57 SSB codes that are returned by raidcom add journal command raidcom add journal Error message Executing/ Asynchronous Error code SSB1 SSB2 CMDRJE Executing 2E00 0000 The value of LDEV number is invalid. CMDRJE Executing 2E00 0018 A new journal volume cannot be registered because the number of journal volume exceeds the maximum that can be registered. Get Command Status Asynchronous 2E00 0023 The specified volume capacity is too small.
Table 57 SSB codes that are returned by raidcom add journal command (continued) raidcom add journal Error message Executing/ Asynchronous Error code Description SSB1 SSB2 Get Command Status Asynchronous 2E23 0005 A new journal volume cannot be registered, or the number of selected volumes is too many. Get Command Status Asynchronous 2E23 003E The operation failed because the multiple LDKC numbers cannot be mixed in the journal.
Table 57 SSB codes that are returned by raidcom add journal command (continued) raidcom add journal Error message Executing/ Asynchronous Error code Description SSB1 SSB2 Get Command Status Asynchronous 2E30 0068 The specified volume cannot be used as a journal volume because it is used by Parallel Access Volumes.
Table 58 SSB codes that are returned by raidcom modify journal command (continued) raidcom modify journal Error message Executing/ Asynchronous Error code Description SSB1 SSB2 Get Command Status Asynchronous 2E30 0062 The specified volume cannot be used as a journal volume because it is an external volume that can execute the I/O suppression mode. CMDRJE Executing 2E30 5001 The timer type cannot be changed because the specified journal belongs to the extended CT group.
Table 61 SSB codes that are returned by raidcom add device_grp command raidcom add device_grp Error message Executing/ Asynchronous Error code Description SSB1 SSB2 CMDRJE Executing 2E00 0000 It exceeds the range of LDEV number. CMDRJE Executing 2E20 0000 LDEV is not installed. CMDRJE Executing 2E22 0009 The number of device group in the system has reached the maximum. CMDRJE Executing 2E22 000A The device name of an LDEV is duplicated in the system.
Table 63 SSB codes that are returned by raidcom initialize ldev command (continued) raidcom initialize ldev Error message Executing/ Asynchronous Error code Description SSB1 SSB2 Get Command Status Asynchronous 2E10 0012 The specified LDEV is a CC/XRC attribute device. Get Command Status Asynchronous 2E10 0100 The formatting operation cannot be done because the check sum of the encryption key is not coincident. Get Command Status Asynchronous 2E11 0007 The LDEV is in shredding.
Table 63 SSB codes that are returned by raidcom initialize ldev command (continued) raidcom initialize ldev Error message Executing/ Asynchronous Error code Description SSB1 SSB2 Get Command Status Asynchronous 2E31 0001 Maintenance work cannot be performed because the target LDEV is a ESAM Quorum disk. Get Command Status Asynchronous 2E31 0017 LDEV cannot be formatted because there is no normal external path. CMDRJE Executing 2EE8 00EE The command cannot be accepted.
Table 64 SSB codes that are returned by raidcom modify ldev -command_device (continued) raidcom modify ldev -command_device Error message CMDRJE Executing/ Asynchronous Error code Description SSB1 SSB2 Executing 2E30 0014 The command device cannot be set to the specified LDEV because of the following causes. • It is used as a Auto LUN. • The reserve attribute of a Auto LUN is configured.
Table 66 SSB codes that are returned by raidcom modify ldev -status nml command (continued) raidcom modify ldev -status nml Error message Executing/ Asynchronous Error code Description SSB1 SSB2 Get Command Status Asynchronous 2E11 0009 The operation cannot be done because LDEV is not expanding. Get Command Status Asynchronous 2E11 001E The operation cannot be done because the virtual disk space is blocked. CMDRJE Executing 2E11 0053 The specified LDEV is used in another operation.
Table 67 SSB codes that are returned by raidcom modify ldev -status blk command (continued) raidcom modify ldev -status blk Error message Executing/ Asynchronous Error code Description SSB1 SSB2 Get Command Status Asynchronous 2E11 0009 The operation cannot be done because LDEV is now expanding. Get Command Status Asynchronous 2E11 001E The operation cannot be done because the virtual disk space is blocked. CMDRJE Executing 2E11 0053 The specified LDEV is used in another operation.
Table 68 SSB codes that are returned by raidcom modify ldev -status enable_reallocation command (continued) raidcom modify ldev -status enable_reallocation Error message Executing/ Async Error code Description SSB1 SSB2 CMDRJE Executing 2E30 000B The specified LDEV is not a virtual volume of Thin Provisioning/Smart Tiers. CMDRJE Executing 2E30 0073 The specified LDEV is not a virtual volume of Smart Tiers.
Table 71 SSB codes that are returned by raidcom delete lun command raidcom delete lun Error message Executing/ Async Error code Description SSB1 SSB2 CMDRJE Executing B958 0155 The other than intermediate volume or OPEN volume is included in the specified LDEV. CMDRJE Executing B958 015D An used LDEV exists in the specified LDEV. CMDRJE Executing B958 0202 It cannot be deleted because it is the last path of Continuous Access Journal.
Table 72 SSB codes that are returned by raidcom add lun command (continued) raidcom add lun Error message Executing/ Asynchronous Error code SSB1 SSB2 CMDRJE Executing B958 015D An invalid LDEV exists in the specified LDEVs. CMDRJE Executing B958 015E It exceeds the maximum LUN under the port. CMDRJE Executing B958 0178 LDEV is set as a pool volume. CMDRJE Executing B958 017B LUN path cannot be set because the LDEV is a system disk.
Table 73 SSB codes that are returned by raidcom modify pool command raidcom modify pool Error message Executing/ Asynchronous Error code Description SSB1 SSB2 CMDRJE Executing 2E00 6000 The value of pool ID is invalid. CMDRJE Executing 2E00 6001 The specified pool is for Snapshot. CMDRJE Executing 2E00 6002 The value of maximum reserve ratio is out of range, or it falls below the maximum reserve ratio of the V-VOL.
Table 73 SSB codes that are returned by raidcom modify pool command (continued) raidcom modify pool Error message Executing/ Asynchronous Error code Description SSB1 SSB2 CMDRJE Executing 2E30 6000 The threshold value 1 is out of range. CMDRJE Executing 2E30 6005 The specified pool must be assigned two user-defined thresholds to. CMDRJE Executing 2E30 600D The specified pool is not the pool for Smart Tiers.
Table 75 SSB codes that are returned by raidcom delete pool command (continued) raidcom delete pool Error message Executing/ Asynchronous Error code Description SSB1 SSB2 Get Command Status Asynchronous 2E00 600B All pool volumes associated to a pool cannot be deleted. Get Command Status Asynchronous 2E10 0009 The specified LDEV is in the state of blocked. CMDRJE Executing 2E10 600D This pool cannot be deleted because a volume in the pool is being deleted.
Table 76 SSB codes that are returned by raidcom add snap_pool command raidcom add snap_pool Error message Executing/ Async Error code SSB1 SSB2 Get Command Status Async 2E00 0000 The value of LDEV number is out of range. CMDRJE Executing 2E00 6000 Pool ID is out of range. CMDRJE Executing 2E00 6001 The type of pool is invalid. CMDRJE Executing 2E00 6002 The maximum reserve ratio for V-VOL is out of range.
Table 76 SSB codes that are returned by raidcom add snap_pool command (continued) raidcom add snap_pool Error message Executing/ Async Error code Description SSB1 SSB2 Get Command Status Async 2E30 005D The specified LDEV is a volume of unsupported Smart Tiers. Get Command Status Async 2E30 005E The specified LDEV is used in another program product. CMDRJE Executing 2E30 006C An LDEV, whose emulation type is not available to be mixed, is in the specified LDEVs.
Table 77 SSB codes returned by raidcom add snapshot (continued) raidcom add snapshot Error message Executing/Async Error code Description SSB1 SSB2 CMDRJE Executing 2E10 0021 A pair cannot be created because the volume exceeded the support size is specified as the S-VOL of a Fast Snap or Snapshot pair. CMDRJE Executing 2E10 0022 A pair cannot be created because the V-VOL is specified as the P-VOL of a Fast Snap or Snapshot pair.
Table 77 SSB codes returned by raidcom add snapshot (continued) raidcom add snapshot Error message Executing/Async Error code Description SSB1 SSB2 CMDRJE Executing 2E10 0031 The command ends abnormally because the volumes in which the number of slots is different are specified as the P-VOL of a Fast Snap or Snapshot pair and S-VOL. CMDRJE Executing 2E10 0032 A pair cannot be created because the Thin Provisioning V-VOL is specified as the S-VOL of a Fast Snap or Snapshot pair.
Table 77 SSB codes returned by raidcom add snapshot (continued) raidcom add snapshot Error message Executing/Async Error code Description SSB1 SSB2 CMDRJE Executing 2E10 0041 A Fast Snap or Snapshot pair cannot be created because the Thin Provisioning V-VOL in capacity expanding is specified as the P-VOL of a Fast Snap or Snapshot pair.
Table 77 SSB codes returned by raidcom add snapshot (continued) raidcom add snapshot Error message Executing/Async Error code Description SSB1 SSB2 CMDRJE Executing 2E10 9706 A Fast Snap pair cannot be created because the maximum number of Snapshot IDs (MU numbers) has already been in use for the specified P-VOL.
Table 77 SSB codes returned by raidcom add snapshot (continued) raidcom add snapshot Error message Executing/Async Error code Description SSB1 SSB2 CMDRJE Executing 2E20 000B The command ends abnormally because an unmounted volume is specified as the S-VOL of a Fast Snap or Snapshot pair. CMDRJE Executing 2E20 000C The command ends abnormally because the blocked volume is specified as the S-VOL of a Fast Snap or Snapshot pair.
Table 77 SSB codes returned by raidcom add snapshot (continued) raidcom add snapshot Error message Executing/Async Error code Description SSB1 SSB2 CMDRJE Executing 2E30 007F The command ends abnormally because the volume that has no path definition is specified as the S-VOL of a Fast Snap or Snapshot pair. CMDRJE Executing 2E30 0080 The command ends abnormally because the external volume mapped for the online data migration is specified as the P-VOL of a Fast Snap or Snapshot pair.
Table 78 SSB codes returned by raidcom modify snapshot (continued) raidcom modify snapshot Error message Executing/Async Error code SSB1 SSB2 Description CMDRJE Executing 2E10 0044 A Fast Snap or Snapshot pair cannot be restored because the Continuous Access Journal pair status is other than PSUS or PSUE when the volume is shared between the P-VOL of a Fast Snap/Snapshot pair and the P-VOL of a Continuous Access Journal pair.
Table 78 SSB codes returned by raidcom modify snapshot (continued) raidcom modify snapshot Error message Executing/Async Error code SSB1 SSB2 Description CMDRJE Executing 2E10 8102 A pair cannot be created because there are not enough free shared memory space. CMDRJE Executing 2E10 9700 The command ends abnormally because other than the raidcom add snapshot command is issued for the volume other than the Fast Snap or Snapshot pair.
Table 78 SSB codes returned by raidcom modify snapshot (continued) raidcom modify snapshot Error message Executing/Async Error code Description SSB1 SSB2 CMDRJE Executing 2E21 8108 The command ends abnormally because the shared memory (SS3 or more) is not expanded for necessary capacity. CMDRJE Executing 2E21 9010 The program product is not installed.
Table 80 SSB codes returned by raidcom delete snapshot (continued) raidcom delete snapshot Error message Executing/Async Error code Description SSB1 SSB2 CMDRJE Executing 2E10 0036 The command ends abnormally because the Auto LUN reserved volume is specified as the P-VOL of a Fast Snap or Snapshot pair.
Table 80 SSB codes returned by raidcom delete snapshot (continued) raidcom delete snapshot Error message Executing/Async Error code Description SSB1 SSB2 CMDRJE Executing 2E21 8107 The command ends abnormally because the shared memory (FC, TPF, or Extension2) is not expanded for necessary capacity. CMDRJE Executing 2E21 8108 The command ends abnormally because the shared memory (SS2 or more) is not expanded for necessary capacity. CMDRJE Executing 2EC6 FEEC An internal error occurred.
Table 82 SSB codes that are returned by raidcom delete ssid command (continued) raidcom delete ssid Error message Executing/ Asynchronous Error code Description SSB1 SSB2 CMDRJE Executing 2E11 8004 The operation cannot be done because the microcode is being changed. CMDRJE Executing 2E20 3000 The serial number, the product ID, or the SSID of the remote storage system is invalid. CMDRJE Executing 2E20 3001 The command cannot be executed because the specified RCU is not registered.
Table 83 SSB codes that are returned by raidcom add thp_pool command (continued) raidcom add thp_pool Error message Executing/ Async Error code Description SSB1 SSB2 Get Command Status Async 2E21 8103 The operation cannot be performed because the memory capacity of the shared memory (SM) is insufficient. CMDRJE Executing 2E21 9007 Thin Provisioning program product is not installed. Get Command Status Async 2E22 0005 Exceeded the number of pool volume that can be registered in a pool.
Table 83 SSB codes that are returned by raidcom add thp_pool command (continued) raidcom add thp_pool Error message Executing/ Async Error code Description SSB1 SSB2 Get Command Status Async 2E31 0018 External volumes whose cache modes are different are included. CMDRJE Executing 2E31 6001 The POOL Name is duplicated with another pool. Get Command Status Async 2E31 6004 The pool cannot include volumes in different RAID levels because the pool cannot include those volumes.
Table 84 SSB codes that are returned by raidcom modify rcu command (continued) raidcom modify rcu Error message Executing/ Async Error code Description SSB1 SSB2 CMDRJE Executing 2E23 3101 The operation cannot be done because the number of paths become less than the least path number. Get Command Status Async 2E31 3001 Command cannot be executed because the RCU identification code of a path is invalid. CMDRJE Executing 2ED6 00EF An internal error occurred. Call HP Technical Support.
Table 85 SSB codes that are returned by raidcom delete rcu_path command (continued) raidcom delete rcu_path Error message Executing/ Asynchronous Error code Description SSB1 SSB2 Get Command Status Asynchronous 2E31 3101 Command cannot be executed because the serial number is not unified in the specified path. CMDRJE Executing 2ED6 00EE The command cannot be accepted. After a while, execute the same command. Get Command Status Asynchronous 2ED6 3005 An internal error occurred.
Table 86 SSB codes that are returned by raidcom add rcu_path command (continued) raidcom add rcu_path Error message Executing/ Asynchronous Error code Description SSB1 SSB2 Get Command Status Asynchronous 2E23 3100 An RCU path cannot be added because the number of valid paths exceeds the maximum. CMDRJE Executing 2E30 840A The port attribute is not Initiator (MCU).
Table 87 SSB codes that are returned by raidcom delete rcu command (continued) raidcom delete rcu Error message Executing/ Asynchronous Error code Description SSB1 SSB2 CMDRJE Executing 2ED6 00EE The command cannot be accepted. After a while, execute the same command. Get Command Status Asynchronous 2ED6 3005 An internal error occurred. Call HP Technical Support. CMDRJE Executing 2ED6 3300 The value of SSID on the remote storage system is invalid.
Table 88 SSB codes that are returned by raidcom add rcu command (continued) raidcom add rcu Error message Get Command Status Executing/ Asynchronous Error code Description SSB1 SSB2 Asynchronous 2E22 3002 The operation cannot be performed due to one of the following reasons: • The number of RCUs registered in MCU or RCU is more than four. • The number of RCUs registered in the system is more than 64 in the case of specifying the cu free.
Table 89 SSB codes that are returned by raidcom delete ldev command (continued) raidcom delete ldev Error message Executing/ Async Error code Description SSB1 SSB2 Get Command Status Async 2E11 0004 An LDEV that is in the state of formatting is included in the parity group of the target LDEV. Get Command Status Async 2E11 0005 An LDEV that is in the state of executing quick format is included in the parity group of the target LDEV.
Table 90 SSB codes that are returned by raidcom delete hba_wwn command raidcom delete hba_wwn Error message Executing/ Async Error code Description SSB1 SSB2 CMDRJE Executing B957 404F The program product is not installed. CMDRJE Executing B957 4087 The host group ID exceeds the maximum value. CMDRJE Executing B957 4089 The specified host group is not installed. CMDRJE Executing B957 408A The attribute of specified port is Initiator or External.
Table 93 SSB codes that are returned by raidcom reset hba_wwn command (continued) raidcom reset hba_wwn Error message Executing/ Async Error code Description SSB1 SSB2 CMDRJE Executing B957 408A The attribute of the specified port is Initiator or External. CMDRJE Executing B957 4385 The specified WWN does not exists.
Table 96 SSB codes that are returned by raidcom modify port -port_speed command (continued) raidcom modify port -port_speed Error message Executing/ Asynchronous Error code Description SSB1 SSB2 CMDRJE Executing B955 05A7 The other than "P-to-P (point to point)" cannot be specified when specifying a topology of the package for Fibre Channel over Ethernet. CMDRJE Executing B955 1039 The command device being used at the local RAID Manager exists under the port.
Table 98 SSB codes that are returned by raidcom delete host_grp command raidcom delete host_grp Error message Executing/ Asynchronous Error code Description SSB1 SSB2 CMDRJ Executing B956 302C The cancelling of the host mode option 61 setting was aborted. CMDRJE Executing B956 304F The program product is not installed. CMDRJE Executing B956 3071 The value of host group ID exceeds the maximum. CMDRJE Executing B956 3077 The attribute of the specified port is Initiator or External.
Table 101 SSB codes that are returned by raidcom disconnect path command raidcom disconnect path Error message Executing/ Asynchronous Error code Description SSB1 SSB2 CMDRJE Executing 2E00 4500 The path group is out of the enabled range. CMDRJE Executing 2E00 8400 The value of specified port is invalid. Get Command Status Asynchronous 2E10 4301 The specified external path has already disconnected the path, or is in the process of checking path.
Table 102 SSB codes that are returned by raidcom delete path command (continued) raidcom delete path Error message Executing/ Async Error code Description SSB1 SSB2 CMDRJE Executing 2E20 4500 There is no path group. Get Command Status /Async CMDRJE Executing 2E23 4300 Paths cannot be deleted because there are no normal paths. Get Command Status /Async CMDRJE Executing 2E30 8400 The port attribute is not External (ELUN). CMDRJE Executing 2EDA 00EE The command cannot be accepted.
Table 104 SSB codes that are returned by raidcom -logout command raidcom -logout Error message CMDRJE Executing/ Asynchronous Error code Description SSB1 SSB2 Executing 2E01 2200 Failed to release the resource lock. Table 105 SSB codes that are returned by raidcom monitor pool command raidcom monitor pool Error message Executing/ Async Error code Description SSB1 SSB2 CMDRJE Executing 2E00 6000 The value of pool ID is out of range.
Table 106 SSB codes that are returned by raidcom reallocate pool command (continued) raidcom reallocate pool Error message Executing/ Async Error code Description SSB1 SSB2 CMDRJE Executing 2E11 6003 The pool is not in the status of specifying the reallocation to start or stop. CMDRJE Executing 2E20 6000 The pool ID is not installed. CMDRJE Executing 2E21 8101 A SM for Thin Provisioning is not installed. CMDRJE Executing 2E21 8102 A SM for Smart Tiers is not installed.
Table 109 SSB codes that are returned by raidcom add resource command raidcom add resource Error message Executing/ Asynchronous Error code Description SSB1 SSB2 CMDRJE Executing 2E00 2200 The specified resource group name is against the naming rules. CMDRJE Executing 2E00 2202 The resource ID and the sub-resource ID are out of the effective range. CMDRJE Executing 2E10 2202 A resource to which an LU path is defined cannot be added because the virtual mode for a resource is set to on.
Table 111 SSB codes that are returned by raidcom unlock resource command raidcom unlock resource Error message CMDRJE Executing/ Asynchronous Error code Description SSB1 SSB2 Executing 2E10 2200 Cannot unlock because it is locked in another session. Table 112 SSB codes that are returned by raidcom modify clpr command raidcom modify clpr Error message Executing/ Async Error code Description SSB1 SSB2 CMDRJE Executing 2E00 0000 It exceeds the settable range of LDEV numbers.
Table 112 SSB codes that are returned by raidcom modify clpr command (continued) raidcom modify clpr Error message Executing/ Async Error code Description SSB1 SSB2 CMDRJE Executing 2EF3 0102 The specified parameter is invalid. Check the HP P9000 RAID Manager Reference Guide. CMDRJE Executing 2EF6 FEEC An internal error occurred. Call HP Technical Support.
Table 117 SSB codes that are returned by raidcom delete pfc_wwn command raidcom delete pfc_wwn Error message Executing/ Asynchronous Error code Description SSB1 SSB2 CMDRJE Executing B9D4 B9D0 Performance Control is being used by Remote Web Console. CMDRJE Executing B9D4 B9D2 The specified WWN or nickname does not exist. CMDRJE Executing B9D4 B9D4 Performance Control program product is not installed.
10 Support and other resources Contacting HP For worldwide technical support information, see the HP support website: http://www.hp.
HP websites For additional information, see the following HP websites: • http://www.hp.com • http://www.hp.com/go/storage • http://www.hp.com/service_locator • http://www.hp.com/support/manuals • http://www.hp.com/support/downloads • http://www.hp.
Table 119 Document conventions (continued) Convention Element Monospace text • File and directory names • System output • Code • Commands, their arguments, and argument values Monospace, italic text • Code variables • Command variables Monospace, bold text WARNING! CAUTION: IMPORTANT: NOTE: TIP: Emphasized monospace text Indicates that failure to follow directions could result in bodily harm or death. Indicates that failure to follow directions could result in damage to equipment or data.
Glossary AL Arbitrated loop. AL-PA Arbitrated loop physical address. A 1-byte value that the arbitrated loop topology uses to identify the loop ports. This value becomes the last byte of the address identifier for each public port on the loop. allocation The ratio of allocated storage capacity versus total capacity as a percentage. Allocated storage refers to those logical devices (LDEVs) that have paths assigned to them. Allocated storage capacity is the sum of the storage of these LDEVs.
HORCM_DEV A section of the RAID Manager instance configuration file that describes the physical volumes corresponding to the paired volume names. HORCM_INST A section of the RAID Manager instance configuration file that defines how RAID Manager groups link to remote RAID Manager instances.
RCU Remote control unit. remote instance The instance with which the local instance communicates, as configured in the HORCM_INST section of the RAID Manager instance configuration file. RIO Remote I/O. S-VOL Secondary or remote volume. The copy volume that receives the data from the primary volume. SMPL Simplex. SSB Sense byte. SVP Service processor. A computer built into a disk array. The SVP, used only by an HP service representative, provides a direct interface to the disk array.
Index A alternate command device, 16 defining, 17 asynchronous commands list of provisioning, 93 processing, 9, 92 authorities for commands and operations, 54 Auto LUN commands, 149 configurations, 147 controlling, 147 specifications, 147 C cascading connections and configuration files, 33 configuration files, 35 cascading pairs, 128 cascading volume pairs definition, 32 cascading volumes restrictions, 129 cluster manager, 130 command device, 14 alternate, 16 guarding, 15 instance number, 16 command execut
raidscan, raidqry, raidar, horcctl:troubleshooting, 201 troubleshooting, 193, 202 error messages troubleshooting, 193 examples directory mound for Windows, 182 GPT disk for Windows, 181 group version control for mixed storage system configurations, 174 LDM volume discovery and flushing for Windows, 174 mountvol attached to Windows, 176 signature changing facility for Windows, 179 SLPR configuration, 186 specify host group, 183 system buffer flushing, 177 volume discovery, 175 external volumes creating, 120
cascading volumes, 129 duplicated mirroring, 127 in-system , 13 local system configuration, 132 operations, 125, 133 pair status, 134 paired volumes, 138 remote, 13 remote system configuration, 131 requirements, 126 sidefile cache, 140 volume status, 134 resource group locking, 12, 13 resource lock function, 58 restrictions Auto LUN, 153 cascading volumes, 129 Data Retention, 165 Database Validator, 166 RAID Manager operations, 190 replication, 139 S script files, 49 content checking, 60 SCSI command inter
