StorageWorks_RAID_Software_for_OpenVMS______________ Software Release Notes These release notes provide essential information about the V2.4 version of StorageWorks RAID Software for OpenVMS. Software Version: V2.4 OpenVMS Alpha Versions: V6.*, V7.0 and V7.1 OpenVMS VAX Versions: V5.5, V6.*, V7.0 and V7.1 Digital Equipment Corporation Maynard, Massachusetts ________________________________________________________________ April 1997 Possession, use, or copying of the software described in this documentation is authorized only pursuant to a valid written license from Digital, an authorized sublicensor, or the identified licensor. While Digital believes the information included in this publication is correct as of the date of publication, it is subject to change without notice. Digital Equipment Corporation makes no representations that the interconnection of its products in the manner described in this document will not infringe existing or future patent rights, nor do the descriptions contained in this document imply the granting of licenses to make, use, or sell equipment or software in accordance with the description. © Digital Equipment Corporation 1994, 1997. All rights reserved. Printed in the United States of America. OpenVMS, RA, RF, RZ, RD, VAX, VAXcluster, VAXsimPLUS, VMS, and the DIGITAL logo are trademarks of Digital Equipment Corporation. This document was prepared using VAX DOCUMENT, Version 2.1. _________________________________________________________________ Contents 1 New Support in V2.4.............................. 1 2 Problems remedied in V2.4........................ 1 3 Known Problems and Restrictions.................. 2 4 Supported OpenVMS Versions....................... 4 5 Supported Configuration Limits................... 4 6 Command Default Values........................... 5 7 Disk Space Requirements.......................... 6 8 SYSGEN Parameters................................ 6 9 Required OpenVMS Patches......................... 7 10 Contents of Installation Kit..................... 9 11 Licensing........................................ 10 12 Installing....................................... 10 13 Conversion from POLYCENTER[TM] Striping for OpenVMS VAX...................................... 11 14 Reporting Problems............................... 13 Tables 1 Remedial Kits Required for Specific OpenVMS Alpha Versions................................. 8 2 Remedial Kits Required for Specific OpenVMS VAX Versions....................................... 8 iii 1 New Support in V2.4 o Support for OpenVMS V7.1. ________________________ Note ________________________ Patch kits need to be installed before using RAID 0+1 (striping plus shadowing) on OpenVMS V7.1 or the OpenVMS V6.2 Cluster Compatibility Kit which comes with OpenVMS V7.1. See Section 9. StorageWorks RAID Software for OpenVMS V2.3 is not supported on OpenVMS V7.1 or the OpenVMS V6.2 Cluster Compatibility Kit. V2.4 is not supported on OpenVMS Alpha V1.5. ______________________________________________________ o The RAID array BIND times in the VMScluster have been improved. o A command procedure can be run in batch job depending on certain RAID events (s. new section in Guide to Operations under RAID Commands). o The RAID ANALYZE/ARRAY/REPAIR command will recover redundancy on a RAID 5 array. o The RAID ANALYZE/ARRAY and /UNITS command will create a formatted output of on-disk metadata. o New paragraphs in Guide to Operations in chapter Creating and Managing RAID Arrays. 2 Problems remedied in V2.4 o RAID server process dies producing a process dump file larger than 17,000 blocks. The reason was a virtual memory leak during multiple shadow set state changes for RAID 0+1 arrays. 1 o In some cases a system crash did not start a reconstruct operation by the remaining RAID servers potentionally leaving non-redundant areas on RAID 5 arrays. If such arrays later on went to reduced mode PARITY ERRORs were returned trying to read from these area. o RAID Server timeouts due to shadowing and controller mini-merge issues. o After having restarted the RAID server a RAID SHOW command fails with "RAID-F-DRIVER, Error resulting from RAID Driver QIO was detected". 3 Known Problems and Restrictions The following problems exist in the StorageWorks RAID Software V2.4. These problems also existed in StorageWorks RAID Software for OpenVMS V2.3. o RAID ADD/SHADOW commands can cause the RAID server to stay I/O bound for hours. This only happens with non- initialized disk volumes starting with OpenVMS V6.2 and is fixed in OpenVMS V7.1. o DECps and DPA allocation class: DEC Performance Solution (DECps) reports RAID virtual units (DPAnnn:) with an allocation class of 256 (e.g. $256$DPA1:). This is expected behavior. o The StorageWorks RAID Software will attempt to change a volume label on a device to be bound if it conflicts with any currently mounted device. It is not possible to do this if the device in question is a shadow set member. Thus, if a volume label on a shadow member of a RAID array conflicts with any mounted device, a system manager with suitable privileges must change the volume label of the RAID member so that the RAID BIND will succeed. To avoid this problem ensure that the first 9 characters of a RAID array ID are unique across all RAID arrays and across all mounted disk volume labels. 2 o When a node boots into a VMScluster system that is already running the StorageWorks RAID Software the new node will attempt to bind all existing RAID arrays automatically (implicit binds). During this phase the arrays show up in STARTUP state with no virtual devices (DPAnnn:) attached to them. Subsequent RAID BIND commands return the following response message: %RAID-I-ALREADYBOUND, RAID array is already bound This is expected behavior. The following example shows a DCL command sequence which can be added to the command procedure which is used to mount the virtual DPA devices. $! $ Wait_Times = 10 $! $ Wait_For_DPA_Devices: $! $ Wait_Times = Wait_Times - 1 ! count the wait $ IF Wait_Times .LE. 0 THEN GOTO Bind_Array $ IF F$DEVICE("DPA1:", "EXISTS") .AND. - F$DEVICE("DPA2:", "EXISTS") .AND. - F$DEVICE("DPA3:", "EXISTS") THEN GOTO Mount_DPA_Devices $ WAIT 0:0:30 ! wait 30 seconds $ GOTO Wait_For_DPA_Devices ! and check again o Some RAID commands may take several minutes to complete (such as RAID BIND). StorageWorks RAID Software processes all RAID commands sequentially so a command queued behind a long command may occasionally time out. A command timeout is indicated with the following error message: %RAID-F-NOSRVRSP, RAID Server did not respond within timeout period However, even though the command may seem to have failed, in most cases the request was queued successfully to the RAID server process and executed later. To avoid the timeout message the default timeout value for RAID commands of 15 minutes can be increased by setting the logical name RAID$CLI_COMMAND_TIMEOUT to an integer value (where the units are in minutes). This value may need to be increased if the StorageWorks RAID 3 Software is installed on several nodes in a VMScluster and is managing multiple RAID arrays. It is recommended that this value be at least 15 minutes. 4 Supported OpenVMS Versions StorageWorks RAID Software for OpenVMS supports operation under OpenVMS Alpha V6.1, V6.2 (s. note), V7.0 and V7.1 (s. note) and OpenVMS VAX[TM] V5.5, V6.0, V6.1, V6.2 (s. note), V7.0 and V7.1 (s. note). ________________________ Note ________________________ Patch kits need to be installed before using RAID 0+1 (striping plus shadowing) on OpenVMS V7.1 or the OpenVMS V6.2 Cluster Compatibility Kit which comes with OpenVMS V7.1. See Section 9. StorageWorks RAID Software for OpenVMS V2.3 is not supported on OpenVMS V7.1 or the OpenVMS V6.2 Cluster Compatibility Kit. V2.4 is not supported on OpenVMS Alpha V1.5. ______________________________________________________ 5 Supported Configuration Limits o V2.4 is certified to run on standalone systems or on a maximum of 20 VMScluster nodes o V2.4 supports up to 50 arrays per standalone system or VMScluster, subject to site-specific performance requirements o RAID arrays may contain a maximum of 32 members per array o RAID arrays may contain a maximum of 64 virtual units per array o Only Volume Shadowing Phase II is supported, and only with RAID 0 (striping) arrays - If Volume Shadowing will be used, a separate license must be purchased for that product 4 - RAID 5 (striping with parity) with Shadowing is not supported ________________________ Note ________________________ The following are not supported as RAID array members by the StorageWorks RAID Software: ______________________________________________________ o Stripe sets formed by POLYCENTER[TM] Striping for OpenVMS VAX o Files-11 bound volume sets formed by OpenVMS software o Bootable System disks o Quorum disks 6 Command Default Values The defaults are unchanged from StorageWorks RAID Software for OpenVMS V2.0. The following default values are used: o Chunk size The default chunk size of 120 blocks is used by the RAID INITIALIZE command if the /CHUNK_SIZE qualifier is not specified. o Timeout The default timeout value of 30 seconds is used when the RAID INITIALIZE, RAID BIND, and RAID MODIFY commands are entered if the /TIMEOUT or /NOTIMEOUT qualifiers are not specified. 5 7 Disk Space Requirements o On Alpha systems: - You must have a minimum of 5,000 free blocks on the system disk during installation for temporary file storage. - You must allow for 4,000 blocks of storage on the system disk for storage of permanent RAID software files after installation is complete. o On VAX systems: - You must have a minimum of 3,500 free blocks on the system disk during installation for temporary file storage. - You must allow for 2,500 blocks of storage on the system disk for storage of permanent RAID software files after installation is complete. 8 SYSGEN Parameters o On Alpha systems: - You must have at least 700 + size of SYS$SHARE:DCLTABLES.EXE units of GBLPAGES available to install and run the product. - You must have at least 4 units of GBLSECTIONS available to install and run the product. - You must have at least 700 units of GBLPAGES available to run the product. - You must have at least 3 units of GBLSECTIONS available to run the product. o On VAX systems: - Increase the SPTREQ SYSGEN parameter by 32 prior to installing the RAID software on OpenVMS VAX systems. If you are installing StorageWorks RAID Software for 6 OpenVMS to upgrade to a newer version you do not need to increase the SPTREQ parameter again. - You must have at least 500 + size of SYS$SHARE:DCLTABLES.EXE units of GBLPAGES available to install and run the product. - You must have at least 5 units of GBLSECTIONS available to install and run the product. - You must have at least 500 units of GBLPAGES available to run the product. - You must have at least 4 units of GBLSECTIONS available to run the product. Use DCL lexical functions to find out how many units are available. If F$GETSYI("FREE_GBLPAGES") returns a number less than the required GBLPAGES units or F$GETSYI("FREE_ GBLSECTS") returns a number less than the required GBLSECTIONS units increase the SYSGEN parameter(s) and reboot. Refer to the OpenVMS Guide to Performance Management in the OpenVMS documentation set for detailed instructions for using AUTOGEN to change system parameters. 9 Required OpenVMS Patches This section describes the remedial kits that you may need to install prior to installing StorageWorks RAID Software for OpenVMS. Some of these patches are mandatory. Others are necessary to support full RAID functionality. ________________________ Note ________________________ Digital continually provides updates for these patch kits as new problems are reported and fixed. It is recommended to contact your normal Digital support channel to obtain the most recent version of the patches required. ______________________________________________________ 7 Table 1 Remedial Kits Required for Specific OpenVMS Alpha ________Versions___________________________________________ Remedial_Kit__V6.*__________V7.0__________V7.1_____________ ALPSHADn recommended recommended ALPCLUSIOn_ V6.2 see V62 Note 1 ALPSHADn_V71 mandatory with RAID 0+1 n=most recent version____________________________________________________ Note 1: Mandatory for V6.2 with Cluster Compatibility Kit installed and using RAID 0+1 arrays. Table 2 Remedial Kits Required for Specific OpenVMS VAX ________Versions___________________________________________ Remedial_Kit__V5.5______V6.*_________V7.0_____V7.1_________ CSCPAT_0198 Note 2 CSCPAT_1026 Note 3 CSCPAT_1058 Note 4 CSCPAT_1161 Note 5 CSCPAT_1162 Note 6 VAXSHADn recommenderecommended recommended VAXCLUSIOn_ V6.2 see V62 Note 7 VAXSHADn_V71 mandatory with RAID 0+1 (continued on next page) 8 Table 2 (Cont.) Remedial Kits Required for Specific OpenVMS ________________VAX_Versions_______________________________ Remedial_Kit__V5.5______V6.*_________V7.0_____V7.1_________ n=most recent version____________________________________________________ Note 2: Recommended for V5.5 and V5.5-1. Solves multiple bugcheck and shadowing issues in DUDRIVER/DSDRIVER. Incorporated in V5.5-2. Note 3: Recommended if DECps is installed. Note 4: Recommended for all V5.5 versions. Fixes bugs in locking interface for fork-level processes. Note 5: Recommended for V5.5 and V5.5-1. Several miscellaneous fixes for F11BXQP. Incorporated in V5.5-2. Note 6: Recommended for V5.5-2 and V5.5-2H4. Several miscellaneous fixes for F11BXQP. Note 7: Mandatory for V6.2 with Cluster Compatibility Kit installed and using RAID 0+1 arrays. 10 Contents of Installation Kit The installation kit for this version of the StorageWorks RAID Software for OpenVMS includes the following: o The software media, which contains the following StorageWorks RAID Software for OpenVMS V2.4 savesets: RAID024.A (containing the Release Notes) RAID024.B (containing the Installation Guide) RAID024.C (only used for OpenVMS VAX V5.5-all) RAID024.D (only used for OpenVMS VAX V6.all) RAID024.E (only used for OpenVMS Alpha V1.5 - unsupported) RAID024.F (only used for OpenVMS Alpha V6.all) RAID024.G (only used for OpenVMS Alpha V7.0, V7.1) RAID024.H (only used for OpenVMS VAX V7.0, V7.1) 9 o Use the following comand to obtain a copy of the Installation Guide: $ BACKUP RAID024.B/SAVE/SELECT=RAID_INST_GUIDE.* * 11 Licensing OpenVMS LMF support is implemented in the StorageWorks RAID Software for OpenVMS. A license must be registered and activated on each node on which the software is to be installed and used. A single license Product Authorization Key (PAK) enables both RAID0 and RAID5 functionality. The LMF name for the Capacity License PAK for this version remains the same as the name for StorageWorks RAID5 Software for OpenVMS VAX V1.0, SW-RAID5, despite the fact that it also enables RAID0 functionality. The Concurrent Use License PAK, which allows a single disk, storage element or shadow set to be used in a RAID array from all VAX and Alpha systems in a VMScluster which are running the StorageWorks RAID Software, uses LMF name SW- RAID5-STG-USER. This license also enables both RAID0 and RAID5 functionality. Current licensed users of POLYCENTER[TM] Striping for OpenVMS VAX (earlier known as the VAX Disk Striping Driver) can use their STRIPING license with StorageWorks RAID Software to create and use RAID-0 arrays (stripe sets). Also shadow sets can be used as members of a RAID-0 array if Host Based Volume Shadowing is installed and licensed on all nodes running the StorageWorks RAID Software. 12 Installing Use the following command to install the product: $ @SYS$UPDATE:VMSINSTAL RAID024 For more details consult the StorageWorks RAID Software for OpenVMS Installation Guide for installation instructions. To obtain a copy of the Installation Guide refer to Section 10. 10 Rolling upgrades are supported from previous versions of this product. If you are currently using StorageWorks RAID Software for OpenVMS V2.* you may continue to use your RAID arrays while doing a rolling upgrade to V2.4. Unbinding and rebinding your arrays is not necessary. 13 Conversion from POLYCENTER[TM] Striping for OpenVMS VAX For license compatibility see Section 11. The on-disk information used to provide RAID0 functionality in this product is different and incompatible with that used by the POLYCENTER[TM] Striping for OpenVMS VAX (earlier known as the VAX Disk Striping Driver). If you wish to move data from POLYCENTER[TM] Striping stripe sets onto RAID0 arrays managed by StorageWorks RAID Software, you will need to back up the stripe set virtual unit, form a RAID0 array, and restore the data to the RAID0 virtual unit. Both POLYCENTER[TM] Striping for OpenVMS VAX and StorageWorks RAID Software may coexist on the same OpenVMS systems and in the same VMScluster. So, an alternative method of converting POLYCENTER[TM] Striping stripe sets to RAID0 arrays is to create a RAID0 array using RAID INITIALIZE and RAID BIND, and do a disk to disk BACKUP directly from the stripe set to the RAID0 array. ________________________ Note ________________________ StorageWorks RAID Software adds another name layer to RAID arrays called an ARRAY-ID. The ARRAY-ID is used in most commands where you used to specify a STAnnn device name with POLYCENTER[TM] Striping. The ARRAY-ID is the identifier for the RAID array an can be a 1- to 32-character string. ______________________________________________________ Below is an example of transferring data from a POLYCENTER[TM] Striping device "sta1" to a new StorageWorks RAID Software device "dpa1". 11 $! $! mount the POLYCENTER Striping device FILES-11 $! $ MOUNT sta1: user %MOUNT-I-MOUNTED, USER mounted on STA1: (RAIDON) $! $! initialize the StorageWorks RAID Software $! RAID-0 array named "raid0set" on disk devices $1$DUA2 and $1$DUA3 $! $ RAID INITIALIZE raid0set $1$DUA2,$1$DUA3/RAID=0 %RAID-I-VOLLABEL, device $1$DUA2: has a volume label of SCRATCH1 %RAID-I-VOLLABEL, device $1$DUA3: has a volume label of SCRATCH2 INIT will destroy existing data, do you want to continue [N]? yes %RAID-I-PRTCREATED, Array partition 1 created: 2426392 blocks $! $! bind the RAID-0 array named "raid0set" and assign it to the newly $! created virtual unit "dpa1" $! $ RAID BIND raid0set $1$DUA2,$1$DUA3 dpa1 %RAID-I-ISBOUND, unit $1$DUA2: is bound as a member of RAID array RAID0SET %RAID-I-ISBOUND, unit $1$DUA3: is bound as a member of RAID array RAID0SET %RAID-I-VUCREATE, virtual unit DPA0001: was created for partition 1 on RAID0SET $! $! mount new virtual disk device for BACKUP copy operation $! $ MOUNT/FOREIGN dpa1: %MOUNT-I-MOUNTED, mounted on DPA1: (RAIDON) $! $! copy from POLYCENTER Striping unit "sta1" to $! StorageWorks RAID-0 unit "dpa1" $! $ BACKUP/IMAGE sta1: dpa1:/VERIFY $! $! re-mount the new StorageWorks virtual unit "dpa1" $! as a FILES-11 volume $! $ DISMOUNT dpa1: $ MOUNT/SYSTEM dpa1: user %MOUNT-I-MOUNTED, USER mounted on DPA1: (RAIDON) $ 12 The next example shows how to transform the RAID-0 array into a RAID-0+1 array (striping plus shadowing) with 2 member shadow sets. $! $! Proceed here if members of the RAID-0 array $! should be shadowed $! $ DISMOUNT dpa1: $ RAID UNBIND dpa1 %RAID-I-RAUNBOUND, Array RAID0SET has been unbound from virtual unit DPA1 $! $! Re-BIND RAID-0 array with single member shadow sets $! $ RAID BIND raid0set $1$DUA2,$1$DUA3 dpa1 - /SHADOW /USE_SHADOW_DEVICES=(dsa1,dsa2) %RAID-I-ISBOUND, unit DSA1: is bound as a member of RAID array RAID0SET %RAID-I-INUSE, unit $1$DUA1: is a shadow set member of DSA1: %RAID-I-ISBOUND, unit DSA2: is bound as a member of RAID array RAID0SET %RAID-I-INUSE, unit $1$DUA2: is a shadow set member of DSA2: %RAID-I-VUCREATE, virtual unit DPA1: was created for partition 1 on RAID0SET $! $! and add more members to the shadow sets $! $ RAID ADD /SHADOW_MEMBER raid0set DUA3/DEVICE=dsa1 %RAID-I-SHADOWADD, unit $1$DUA3: added to shadow set DSA1: in RAID Array RAID0SET $ RAID ADD /SHADOW_MEMBER raid0set DUA4/DEVICE=dsa2 %RAID-I-SHADOWADD, unit $1$DUA4: added to shadow set DSA2: in RAID Array RAID0SET $! $! Redefine logicals pointing to sta1 and start applications using $! new dpa1 device $! 14 Reporting Problems If problems occur with this version of the StorageWorks RAID Software for OpenVMS, please report them through your official support channels. When reporting problems, the following information will assist the support team: o Configuration information 13 o Copy of SYS$MANAGER:RAID$DIAGNOSTICS_nodename.LOG file(s). o Copy of SYS$MANAGER:RAID$SERVER_MAIN.DMP, if the RAID server process (RAID$SERVER) has exited. o Output from the "$ RAID ANALYZE/ARRAY /OUTPUT=RAIDANALYZE.TXT array-ID" command. o Output from the "$ RAID ANALYZE/ERROR /OUTPUT=RAIDERRLOG.TXT" command. o Copy of OpenVMS crash dump, if applicable. o Output from RAID SHOW/FULL command after the problem occurred. If the problem is reproducible, please provide the RAID SHOW/FULL output while the problem exists. o Output from RAID ANALYZE/ARRAY or /UNITS of the array(s) with a problem. 14