storage configuration

Adaptec SCSI RAIDContainer Configuration UtilityUsers Guide

Adaptec Array Controller

ii

Copyright 2000 - 2002 Adaptec, Inc. All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, photocopying, recording or otherwise, without the prior written consent of Adaptec, Inc., 691 South Milpitas Blvd., Milpitas, CA 95035.

Trademarks

Adaptec and the Adaptec logo are trademarks of Adaptec, Inc., which may be registered in some jurisdictions.

Windows 95, Windowtrademarks of Microsolicense.

All other trademarks a

ChangesThe material in this dowithout notice. Whiledocument to assure iterrors or omissions inherein.

Adaptec reserves the rand without notificati

DisclaimerIF THIS PRODUCT DPERMISSION FROM VIOLATING THE LAREMEDIES.s 98, Windows NT, Windows 2000, and Windows Me, are ft Corporation in the US and other countries, used under

re the property of their respective owners.

cument is for information only and is subject to change reasonable efforts have been made in the preparation of this s accuracy, Adaptec, Inc. assumes no liability resulting from this document, or from the use of the information contained

ight to make changes in the product design without reservation on to its users.

IRECTS YOU TO COPY MATERIALS, YOU MUST HAVE THE COPYRIGHT OWNER OF THE MATERIALS TO AVOID W WHICH COULD RESULT IN DAMAGES OR OTHER

Adaptec Software License Agreement

PLEASE READ CAREFULLY: THE USE OF THIS SOFTWARE IS SUBJECT TO THE SOFTWARE LICENSE TERMS OF ADAPTEC, INC. AND OTHER LICENSORS WHOSE SOFTWARE MAY BE BUNDLED WITH THIS PRODUCT.

BY YOUR USE OF THE SOFTWARE INCLUDED WITH THIS PRODUCT YOU AGREE TO THE LICENSE TERMS REQUIRED BY THE LICENSOR OF THAT SOFTWARE, AS SET FORTH DURING THE INSTALLATION PROCESS. IF YOU DO NOT AGREE TO THE LICENSE TERMS APPLICABLE TO THE SOFTWARE, YOU MAY RETURN THE ENTIRE UNUSED PRODUCT FOR A FULL REFUND.

In return for acquiring a license to use the Adaptec software (Software) and the related documentation, you agre

1. License. This Agreem

a. Use the Softwareservers which incusers from multipneeded, but musan Adaptec RAID

b. Make one copy oprovided you rep

2. Restrictions. You mayotherwise make availYou may not use the applications. The Sofdecompile, reverse enperceivable form. YORESELL FOR PROFITUPON THE SOFTWA

3. Ownership of Softwaor fixed, but Adaptecthe original media anin which or on whichSoftware or any copy

4. Confidentiality. You adisclose the Softwarefurther agree to take the Software.

5. Term. This license is terminate the licensedocumentation) togeright to terminate outhis Agreement. UpoSoftware (including tany form.

6. Special Terms Applicacknowledge that it icreation, and that theconfidence in accordarights to distribute or

7. Limited Warranty. AdSoftware is furnishedand service for a periITS LICENSORS DOYOU MAY OBTAIN FOREGOING STATELICENSORS WILL PFOREGOING LIMITWARRANTIES, EXPRINFRINGEMENT OFiii

e to the following terms and conditions:

ent grants you, the Licensee, a license to:

on a single computer system or on multiple workstations, systems and orporate an Adaptec RAID controller and may be accessed by multiple le locations. You may make as many installations of the Software as

t restrict such installation only to systems, workstations or servers using controller.

f the Software in machine readable form solely for back-up purposes roduce Adaptecs copyright notice and any proprietary legends.

not distribute copies of the Software to others. You may not post or able the Software, or any portion thereof, in any form, on the Internet. Software in a computer service business, including in time sharing tware contains trade secrets and, in order to protect them, you may not gineer, disassemble, or otherwise reduce the Software to a human-U MAY NOT MODIFY, ADAPT, TRANSLATE, RENT, LEASE, LOAN, , DISTRIBUTE, NETWORK OR CREATE DERIVATIVE WORKS BASED RE OR ANY PART THEREOF.

re. As Licensee, you own the media upon which the software is recorded and its licensors retain title and ownership of the Software recorded on d all subsequent copies of the Software, regardless of the form or media the original and other copies may exist. This license is not a sale of the .

gree to maintain the Software in confidence and that you will not to any third party without the express written consent of Adaptec. You all reasonable precautions to preclude access of unauthorized persons to

effective until January 1, 2045, unless terminated earlier. You may at any time by destroying the Software (including the related ther with all copies or modifications in any form. Adaptec will have the r license immediately if you fail to comply with any term or condition of n any termination, including termination by you, you must destroy the he related documentation), together with all copies or modifications in

able to Databases. Where a database is included with the Software, you s licensed only in connection with the use of the Software to perform disc database and all data derived therefrom must be maintained in nce with the provisions of Section 4. This license does not grant you any disclose such database or data.

aptec and its Licensor warrant only that the media upon which the will be free from defects in material or workmanship under normal use od of thirty (30) days from the date of delivery to you. ADAPTEC AND NOT AND CANNOT WARRANT THE PERFORMANCE OR RESULTS BY USING THE SOFTWARE OR DOCUMENTATION. THE S THE SOLE AND EXCLUSIVE REMEDIES ADAPTEC AND ITS ROVIDE FOR BREACH OF WARRANTY. EXCEPT FOR THE ED WARRANTY, ADAPTEC AND ITS LICENSORS MAKE NO

ESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED, AS TO NON- THIRD PARTY RIGHTS, MERCHANTABILITY OR FITNESS FOR A

iv

PARTICULAR PURPOSE. Some states do not allow the exclusion of implied warranties or limitations on how long an implied warranty may last, so the above limitations may not apply to you. This warranty gives you specific legal rights and you may also have other rights which vary from state to state.

8. The entire liability of Adaptec and its licensors, and your exclusive remedy for a breach of this warranty, shall be:

a. The replacement of any media not meeting the above limited warranty which is returned to Adaptec; or:

b. If Adaptec or its distributor is unable to deliver replacement media which is free from defects in materials or workmanship, you may terminate this Agreement by returning the Software and your money will be refunded.

9. Limitation of LiabilitYOU FOR ANY INCINCLUDING ANY LADAPTEC OR A LICDAMAGES, OR FORexclusion or limitatiolimitation or exclusio

10. Export. You acknowlcountries may restricexport or re-export thUnited States and for

11. Government RestrictSoftware is acquired subject to the restrictacquired under the teby the Government is12.212 of the Federal DoD FAR Supplemen

12. General. You acknowusing the Software yois the complete and esupersedes any propbetween Adaptec andany different terms wconsent, including anofficer of Adaptec. Yothe Software legally aexcept as to copyrighentered into at Milpitdeclared unenforceabfrom this Agreementspecifically granted i

Should you have any queto:

Adaptec, Inc.Legal Department691 South Milpitas BouleMilpitas, California 95035y. IN NO EVENT WILL ADAPTEC OR ITS LICENSORS BE LIABLE TO IDENTAL, CONSEQUENTIAL OR INDIRECT DAMAGES, OST PROFITS, LOST SAVINGS, OR LOSS OF DATA, EVEN IF ENSOR HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH ANY CLAIM BY ANY OTHER PARTY. Some states do not allow the n of special, incidental, or consequential damages, so the above n may not apply to you.

edge that the laws and regulations of the United States and other t the export and re-export of the Software. You agree that you will not e Software or documentation in any form in violation of applicable eign law.

ed Rights. The Software is subject to restricted rights as follows. If the under the terms of a GSA contract: use, reproduction or disclosure is ions set forth in the applicable ADP Schedule contract. If the Software is rms of a DoD or civilian agency contract, use, duplication or disclosure subject to the restrictions of this Agreement in accordance with 48 C.F.R.

Acquisition Regulations and its successors and 49 C.F.R. 227.7202-1 of the t and its successors.

ledge that you have read this Agreement, understand it, and that by u agree to be bound by its terms and conditions. You further agree that it xclusive statement of the agreement between Adaptec and you, and osal or prior agreement, oral or written, and any other communication you relating to the subject matter of this Agreement. No additional or ill be enforceable against Adaptec unless Adaptec gives its express express waiver of the terms of this Agreement, in writing signed by an u assume full responsibility for the use of the Software and agree to use nd responsibly. This Agreement shall be governed by California law, t matters, which are covered by Federal law. This Agreement is deemed as, California by both parties. Should any provision of this Agreement be le in any jurisdiction, then such provision shall be deemed severable

and shall not affect the remainder hereof. All rights in the Software not n this Agreement are reserved by Adaptec.

stions concerning this Agreement, you may contact Adaptec by writing

vard.

Contents

1 IntroductionInteractivShared CRunning

2 InteractCreating

SelecAssig

ManagingViewAssigRemoInitiaMakiDeletHot-S

3 Script MPlayback

InitiaRecord M

DeterSS

Script FileConta

TTv

e Versus Script Mode 1-1hannels 1-2the CCU 1-2

ive Modea Container 2-1ting Partitions for the New Container 2-1ning Container Properties 2-2 Containers 2-4

ing Container Properties 2-4ning Failover Drives 2-5ving Failover Drives 2-5lizing a Disk Drive 2-6ng a Container Bootable 2-6ing Containers 2-7wapping Adapters 2-8

odeMode 3-3lizing Drives 3-5ode 3-6mining Scrub/Clear Status 3-6crub Operations on RAID 10 Containers 3-8crub Operations on RAID 50 Containers 3-8 Syntax 3-8iner Definition Block Properties 3-9

he Container Keyword 3-12he Drives Keyword 3-12

vi

Adaptec SCSI RAID Container Configuration Utility Users Guide

The Type Keyword 3-12The End Keyword 3-13The FailoverDrives Keyword 3-13The InitializeAll Keyword 3-14The Method Keyword 3-15The ReadCache Keyword 3-15The Size Keyword 3-16TTTT

ChanError HanPlaybackExample

Indexhe StripeSize Keyword 3-16he Wait Keyword 3-17he WaitForScrub Keyword 3-17he WriteCache Keyword 3-17nel Definition Block Properties 3-18dling 3-19

and Record Notes 3-213-22

1-1

IntroduThe Adaptec Coapplication used tcontrollers BIOS controllers BIOS,startup, then selecmenu. To run the

This guide describSee the installatioinformation on usnoted, the CCU, aDOS.

Interactive VWhen used in MSCCU offers the sacan use the CCU tto initialize disk dInteractive Mode, finterface.

In addition, the Cenables you to creplain-text script ficontroller channecontainer and chaallowing you to econfiguration basMode for informatctionntainer Configuration Utility (CCU) is an o create and manage containers (arrays) from the or from MSDOS. To access the CCU within a type Ctrl/A to enter the BIOS during system t Container Configuration Utility from the main CCU from MSDOS, execute the CCU program.

es how to use the CCU running under MSDOS. n guide (included with your controller) for ing the CCU within the BIOS. Unless otherwise s described within this guide, refers to the CCU for

ersus Script ModeDOS mode (also known as interactive mode), the me interface and features as the BIOS version. You o create, display, and delete containers, as well as rives for use by the controller. See Chapter 2,

or information on how to use the CCUs interactive

CU offers a special command-line interface that ate containers based on parameters specified in a le. It also enables you to configure certain l properties. You can record a controllers current nnel configuration in a plain-text script file, asily restore your configuration or create a ed on a script template. See Chapter 3, Script ion on how to use the CCUs scripting features.

1-2


Shared ChannelsYou can use the CCU to enable or disable a channel as a shared channel. The CCU displays a shared channel in a different color than a nonshared channel.

Running the CCUCCU.exe is normrun CCU from a bCCU.exe into yousure your system the DOS prompt (or more optional

If you issue the cothe CCU displays(interactive modethe CCU commandinteraction (comm

The remainder of both interactive a

ally distributed on a bootable floppy diskette. To ootable floppy, insert the diskette containing r floppy disk drive and restart your system. (Be

is configured to boot from drive A by default.) At A:\>), type the command CCU, followed by one command line switches, and press Enter.

mmand CCU without any command-line switches, its main window and awaits your menu selection ). If you include any command-line switches with , CCU processes your command with no further and-line or script mode).

this guide explains in detail how to use the CCU in nd script modes.

2-1

InteractWhen you issue tcommand-line swwaits for your me and keys to seselecting an optiobetween the fieldprevious menu at

This chapter desc

Creating a CBefore creating comembers of the co(or enclosure). Reconnected drives or drives to be usproperties to the c

Selecting PartitTo select one or mcontainer:

1 Use the a

2 Use the ancontainer, thusable freespfreespace froive Modehe CCU command at the DOS prompt without any itches, the CCU displays its main window and nu selection. To select a CCU menu option, use the lect an option, then press Enter. In some cases, n displays another menu. Press Tab to navigate s within a dialog box. You can return to the any time by clicking Esc.

ribes how to use the main options of the CCU.

ontainerntainers, make sure the drives to be used as ntainer are connected and installed in your server

boot your system if necessary to ensure that all are detected. To create a container, select the drive ed in the container, then assign the desired ontainer.

ions for the New Containerore partitions to assign as members of the new

nd arrow keys to select a channel.

d keys to select the drives to assign to the new en click Insert. The CCU displays the largest ace available for each drive. You can use available m multiple drives for the new container.

2-2


To deselect a drive, highlight the drive and click Delete.

Note that drives containing DOS partitions, drives with no available free space, or uninitialized drives (see Initializing a Disk Drive on page 2-6) appear dimmed and cannot be selected when creating a new container.

3 Click Enter when all partitions for the new container are selected. The CCU displays the Container Properties menu.

Assigning ContTo assign various

1 From the Coand click Enaccording toTable 2-1 de

T

TypeMinimDrives

Volume 1

RAID 0(stripe set)

1

RAID 1(mirror set)

2ainer Properties properties to the new container:

ntainer Properties menu, select a container type ter. Note that only those container types available the number of drives selected are displayed. scribes the supported container types.

able 2-1. Supported Container Types

um Description

A container made up of one or more partitions concatenated together to form a single logical volume.

A container where data is striped across the partitions, allowing for faster I/O performance than a single disk drive or volume. Be aware that RAID 0 containers do not maintain any redundant data; if any disk drive in the container fails, all data is lost.

A container where data is mirrored on two equal-sized partitions that reside on two different disks. If one disk fails, data is available from the other disk. The actual capacity of the container equals half the available disk space.

Interactive Mode

Note: Theexceed 32

See the Cominformation

2 Type in an o

3 Enter the deavailable baautomaticalsize, type th(megabytes)down list. Ifis greater thbe available

4 Select the deamount of d

RAID 5 3 A container with redundant (parity) data distributed across all partitions in the container. If any one disk fails, data can be reconstructed from the parity information. If a second disk fails before the container has been

RAID 10(stripe of mirrors)

4

RAID 50(stripe of RAID 5)

6

Table 2-1. Supported Container Types

TypeMinimum Drives Description2-3

number of drives used for each RAID level cannot drives.

mand Line Interface Reference Guide for more on considerations when selecting a RAID level.

ptional label for the container and click Enter.

sired container size. The maximum container size sed on the partitions you selected is displayed ly. If you want to designate a different container e desired container size and select MB , GB (gigabytes), or TB (terabytes) from the drop- the available freespace from the selected partitions an the size specified, the remaining freespace will for use in other containers.

sired container stripe size. Stripe size is the ata written to one partition in a stripe, RAID 5,

reconstructed, all data is lost. The actual usable data capacity of the container is equal to one less than the total number of partitions. (One partitions worth of capacity is needed to hold the parity information.)

A container where parity data is striped across two or more mirror sets. If one disk in a pair fails, data is available. The actual data capacity of the container equals half the total available partition space.

A container where data is striped across two or more sets of RAID 5 sets.

2-4


RAID 10, or RAID 50 container before the I/0 data stream switches to the next partition. The allowable stripe sizes are 8, 16, 32 (the default), and 64 KBytes. For RAID 50 containers, 64 KBytes is the only stripe size allowed. The default stripe size gives the best overall performance in most network server environments.

5 Specify whether you want to enable read caching for the container.

6 Specify the wvalues are a

Disable

Enable wcache onlcharge sta

Enable aeven if nonot OK. Nto Enablpower to the batter

7 When you a

Managing CoUse the Manage Cinitialize containecontainers. The fogreater detail.

Viewing ContaiTo view the prope

1 Select Mana

2 On the List want to view

3 The Containshows detaidisks associarite caching setting for the container. The possible s follows:

Disables use of the write cache.

hen protectedIf supported, enables the write y when a battery is present and the batterys tus is OK.

lwaysIf supported, enables the write cache battery is present or the batterys charge status is ote that setting a containers write cache property e always might result in data loss or corruption if the controller is lost when no battery is present or y loses its charge.

re finished, click Done.

ntainersontainer option to view container properties,

rs, make a container the boot container, or delete llowing sections describe these operations in

ner Propertiesrties of an existing container:

ge Container from the Main menu.

of Containers dialog box, select the container you information for, then click Enter.

er Properties dialog box is displayed, which led information about the container. The physical ted with the container are displayed here, except

Interactive Mode

in the case of RAID 10 containers. For RAID 10 containers, highlight the displayed member and click Enter to display the physical disks associated with that member of the container. (Note that a failed drive is displayed in a different text color.)

4 Click Esc to return to the previous menu.

Assigning Failover DrivesTo assign a failov

1 Select Mana

2 On the List want to assiFailover Mawhich show

3 Select a drivfailover. Thefailover driv

4 Click Enter following pr

Have you

5 Click Y (yes)

Removing FailoTo remove an assi

1 Select Mana

2 On the List want to remCtrl/s. The Fdisplayed, wfailover drivdrives.

3 From the Asremoved, thspecified dri2-5

er drive to a container:

ge Containers from the Main menu.

of Containers dialog box, select the container you gn a failover drive to, then click Ctrl/s. The nagement for Container dialog box is displayed, s the drives that can be assigned as failover drives.

e and click the Ins key to assign the drive as a specified drive is displayed in the Assigned es list.

to save the failover drive assignment. The ompt is displayed:

finished managing failover drives?

to return to the Main menu.

ver Drivesgned failover drive from a container:

ge Containers from the Main menu.

of Containers dialog box, select the container you ove the assigned failover drive from, then click ailover Management for Container dialog box is hich shows a list of drives that can be assigned as es, and a list of drives that are assigned as failover

signed failover drives list, select the drive to be en click Del to remove the drive as a failover. The ve is displayed in the Select failover drives list.

2-6


4 Click Enter to save the removed failover drive assignment. The following prompt is displayed:

Have you finished managing failover drives?

5 Click Y (yes) to return to the Main menu.

Initializing a Disk DriveWhen you are crethe disk selectioninitialize the drive

Caution: Idrive is aable to usis part of 00 in the Containerdetermincontainer

To initialize a driv

1 Select Initia

2 Use the a

3 Select the di

4 Click Enter.

5 Read the wathe correct d

Making a ContaYou can make a ccontainer instead

To make a contain

1 Select Mana

2 Select the coCtrl/B. This making it th

!ating a new container, if a disk drive is not listed in list or if it is grayed out (not available), you must before you can use it as part of a container.

nitializing a disk deletes all data on the disk. If the member of an existing container, you might not be e that container again. Do not initialize a disk that a boot container. The boot container is numbered List of Containers dialog box. See Viewing Properties on page 2-4 for information on ing which disks are associated with a particular .

e:

lize Drives from the Main menu.

nd arrow keys to select a channel.

sk you want to initialize, then click Insert.

rning message and ensure that you have selected isk drives to initialize. Click Y to continue.

iner Bootableontainer bootable so the server boots from the of from a stand-alone (single) disk drive.

er bootable:


ntainer you want to make bootable, then click changes the selected containers number to 00, e controllers boot container.

Interactive Mode

3 Reboot the system.

If you are using SCSI disks, bear in mind the following behavior:

The server will always attempt to boot from any installed non-SCSI disks (for example, any IDE disk at drive C). You must disable or remove all non-SCSI disks if you want the server to boot from a SCSI disk or container.

You must baas part of a cthey can be you do not b

If containersprioritized t

If there are nprimary boonew containbe the prima

Deleting ContaiTo delete an exist

Caution: Byou deletlost.

1 Select Mana

2 Select the co

3 On the Contthen click En

Warning!!containerDo you st

4 Click Yes to previous me

5 Click Esc to

!2-7

ck up the data on any SCSI disks that will be used ontainer. Because disks must be initialized before

added to the array, the existing data will be lost if ack it up.

already exist, a SCSI disk drive cannot be o be the primary booting drive.

o containers, you can set a SCSI drive to be the ting drive. However, if you subsequently create ers, you cannot set any of these new containers to ry booting device.

nersing container:

e sure to back up the data on a container before e it. When you delete a container, all the data is


ntainer you want to delete, then click Delete.

ainer Properties dialog box, select Delete again, ter. The following prompt is displayed:

Deleting will erase all data from the .ill want to continue? (Yes/No):

delete the container, or No to return to the nu.

return to the previous menu.

2-8


Hot-Swapping AdaptersHot-swaps are hardware replacements performed without removing power from the system. Hot-swapping adapters presents some conditions that you should consider.

One way that a hot-swap differs from a cold-swap is the way the system recognizes the new hardware. In a cold-swap, BIOS detects the new hardware and requests a confirmation input. In a hot-swap, the system does nconfirmation if it

When performingslot occupied by tsystem will treat treplacement for th

ot make an announcement or request any determines the changes are not risky.

a hot-swap, install the new adapter into the same he adapter you have just removed. Otherwise, the he new hardware as a new adapter, not as a e one you removed.

3-1

Script MTo use the CCU scof the following r

/PPlaybacchannel sett

/R Recordand channelplayback.

On the CCU commfile to record the sCCU records in th

When running thstores the status ovariable ERRORLEbatch file. See Errerror handling.

Table 3-1 lists the switches.oderipting features, issue the command CCU with one

equired switches:

k mode. This mode configures containers and ings from a specified script file.

mode. This mode saves a controllers container configuration in a specified script file for later

and line, you can also specify the name of a log tatus of the playback or record operation. The e log any errors or warnings encountered.

e CCU in playback or record mode, the utility f the playback or record operation in the DOS VEL on exit, allowing it to be used within a DOS

or Handling on page 3-19 for more information on

required and optional CCU command-line

3-2


Table 3-1. Command-Line Switches

Switch Description

/P Indicates playback mode. In this mode, the CCU reads the contents of the specified script file and creates containers and configures channel settings based on the properties defined in the script.

/R The is the name of the script file. It can include a drive, directory, and file name and extension, but only the file name and extension (.CCU) are required. If no drive is specified, the current default drive is used. If no directory is specified, the current default directory is used.Note that the CCU exits with an error if you do not include either the /P or /R switch (but not both) on the command line.

Indicates record mode. In this mode, the CCU scans the controllers current container and channel configuration and creates the specified script file based on the configuration. The is the name of the script file. It can include a drive, directory, and file name and extension, but only the file name and extension (.MLC) are required. If no drive is specified, the current default drive is used. If no directory is specified, the current default directory is used. Note that the CCU exits with an error if you do not include either the /P or /R switch (but not both) on the command line.

Script Mode

Playback MoPlayback mode enon the properties configure certain

When you create listed in Table 3-2

/L Optional log file name. If you include this switch, the CCU records its activity, and any errors it encounters, in the log file. If no /L switch is specified, the CCU displays any status and errors on the screen.The is a standard DOS file, which can include a

/C

Table 3-1. Command-Line Switches

Switch Description3-3

deables you to create one or more containers based

defined in a script file. It also enables you to properties for each channel on the controller.

a container, you can specify any of the properties .

drive, directory, file name and extension. Only the file name and extension (.LOG) are required. If no drive is specified, the current default drive is used. If no directory is specified, the current default directory is used.

Optional controller number. In systems with more than one controller, this switch specifies the controller on which to operate. Controllers are numbered from 0 to number of controllers minus 1.If no /C switch is specified, controller 0 is used.Note that the number assigned to a particular controller is dependent on the controllers physical PCI slot and the order in which your system scans its PCI slots.

3-4


In addition, therecontrol the variouDefinition Block Prcontainer propert

Table 3-2. Container Properties

Property Description

Type The container type. The following container types are supported: Volume set

Size

Label

StripeSize

Cache settings

Drives

FailoverDrives are other container properties that enable you to s container settings during creation. See Container operties on page 3-9 for the complete list of ies.

RAID 0 (stripe) set RAID 1 (mirror) set RAID 5 set RAID 10 (stripe of mirrors) set RAID 50 (stripe of RAID 5) set

The size of the container to be created. Size can be specified in megabyte (MB), gigabyte (GB), or terabyte (TB) units, or Maximum to specify the maximum size based on the given type and disks.

An alphanumeric string uniquely identifying the container.

The size, in Kbytes, of contiguous data distributed across a striped container (RAID 0, RAID 5, RAID 10, or RAID 50).

The cache settings of the container. You can specify the following values for the caches: ReadCacheYes (enable), or No (disable) WriteCacheOne of the following values:

-YesEnable when protected-NoDisable -AlwaysEnable always

The disk drives to use in creating the container. Drives are identified by their channel number, ID number, and logical unit number (LUN).

The disk drives to assign as failover drives for this container. Drives are identified by their channel number, ID number, and LUN.

Script Mode

Note that you can configure each individual channel on the controller using the ControllerID property, which specifies the SCSI ID number of the controller on the channel

Initializing DrivesBy default, when you use playback mode to create containers, the CCU initializes only those drives specified by the Drives property keywords within creating any new two new containeproperty Drivescontainer with theCCU initializes albefore creating ancontroller are not

Initializing a drivwith that drive as0:0:0 in a contaibe part of a RAIDcontainer when itwith drive membwithin the script a

In some cases, yoconnected to the cscripts Drives pand any existing care created. You ccontainer definitiocontainer propertCCU setting and definition it appeInitializeAllproduce the desir

Because the CCUcontainers, the powithin the script iexample, if the Insecond RAID 5 cobefore creating th3-5

the script file. It does this initialization step before containers. For example, if your script file defines rs, the first a RAID 1 (mirror) container with the =0:0:0, 1:0:0 and the second a RAID 5 property Drives=0:1:0, 0:2:0, 0:3:0, the

l five of the drives comprising the two containers y containers. Any other drives connected to the affected.

e automatically deletes any existing containers their member. For example, if you specify drive ners Drives property and that drive happens to 0 (stripe) container, the CCU deletes the stripe initializes the drive. Note that existing containers ers that are not specified in any Drives property re not affected.

u might want the CCU to initialize all drives ontroller, even those that are not specified in a roperty. This ensures that all drives are initialized ontainers are deleted before any new containers an specify InitializeAll=Yes within any n to instruct the CCU to do this. Unlike most

ies, the InitializeAll=Yes property is a global does not apply only to the container whose ars in. Therefore, you need only specify =Yes once, within any container definition, to ed action.

reads the entire script file before creating any sition of the InitializeAll=Yes property s not significant. Continuing the previous itializeAll=Yes property is specified in the ntainers definition, the CCU initializes all drives e first RAID 0 container.

3-6


Note that any container scrub in progress when a container is deleted will automatically be terminated.

See Container Definition Block Properties on page 3-9 for details on the syntax of the InitializeAll property.

Record ModeRecord mode writes an existing controllers container configuration to a specified scriconfiguration by rresulting script. Inproperties that ca

Because the CCU through the CLI aconfigurations. If create itselffor edisplays a warninswitch is used) anin its script file.

The script file is liconfiguration filesingle system, youassociated containcontrollers, use thcontroller. Your enwith one file corre

Determining ScWhen using playbwhether to wait foto continue while(See the Wait coninstruct the CCU check the status owhen it is comple

The CCU providerecord a controlleswitch), the CCU about each contaipt file, enabling you to create the same unning the CCU in playback mode with the addition, record mode records certain controller

n be set in playback mode.

supports only a subset of container types available nd GUI, it cannot record all the possible container the CCU encounters a container that it cannot xample, a volume of mirrors containerit g (and records the warning in its log file, if that d does not record any properties for that container

mited to one controller and its associated container s. Although you can have multiple controllers on a

cannot record all of the controllers and their er configurations in one file. To record multiple e CCU record mode once for each individual d result will be multiple files on the same diskette, sponding to each controller.

rub/Clear Statusack mode to create a container, you can specify r a containers initial scrub or clear to complete or

the scrub or clear proceeds in the background. tainer property in Table 3-2 on page 3-4.) If you to continue (Wait=No), you need to be able to f a background scrub or clear task and determine te.

s a way to do this. When you use record mode to rs configuration and you specify a log file (/L writes to the log scrub and clear status information ner in the configuration. An application or batch

Script Mode

file can then parse the resultant log file to determine whether a containers scrub or clear is complete, in progress (a percentage of the task is complete), or failed.

The following example shows a log file of a recorded configuration consisting of three containers:

Reading container information ...Passed

Scanning for Drives ...Passed

Reading c

Container

Container

Container

Each status line cowhere is the status values are a

OK

Indicates a nredundant c

SCRUB CLEAR

Indicates a sis the percenpercentage i

SCRUB/CLE

Indicates a serror or othe

When a scrub taskoccurs on the chilConsequently, theindicates 0% to 10container, the cleachild containers. Cand the child task3-7

ache values...Passed

#0 Status : OK

#1 Status : SCRUB 30%

#2 Status : SCRUB/CLEAR FAILED

nsists of the prefix Container # Status :, container ID, followed by the status. The possible s follows:

onredundant container (no scrub required) or a ontainer whose scrub task completed successfully.

%%

crub (or clear) is currently in progress, where tage of the operation that is complete. The s an integer between 0 and 99, inclusive.

AR FAILED

crub or clear that did not complete due to a data r unexpected problem.

runs on a multilevel container, the scrubbing d containers and not on the parent container. parent task always indicates 0% and the child task 0%. When a clear task runs on a multilevel ring occurs on the parent container and not on the onsequently, the parent task indicates 0% to 100%

s always indicates 0%.

3-8


Scrub Operations on RAID 10 Containers

RAID 10 containers can be created by scrubbing only.

For a RAID 10 container, the status message indicates the percent of the scrub completed for the parent and child tasks. The status updates to OK when the tasks complete.

A sample RAID 10 scrub status is as follows:Container #

Scrub Operations

RAID 50 containe

For a RAID 50 conthe scrub completupdates to OK wh

A sample RAID 5Container #

Script File SyA CCU script file

Container defcontainer, subegins with keyword En

Channel definchannel, suckeyword Ch

Each container orand assigned valumust be on its owblock (other than and the ending En

Some container pothers are optionawhat default valu

All keywords canlowercase charact1 Status : PARENT = SCRUB 0%, CHILD = SCRUB = 30%

on RAID 50 Containers

rs can be created by scrubbing only.

tainer, the status message indicates the percent of ed for the parent and child tasks. The status en the tasks completes.

0 scrub status is as follows:1 Status : PARENT = SCRUB 0%, CHILD = SCRUB = 30%

ntaxconsists of one of the following:

inition blockSpecifies the properties of a ch as type, size, and cache settings. The block the keyword Container and ends with the d.

ition blockSpecifies the properties of a controller h as ControllerID. The block begins with the annel and ends with the keyword End.

channel property consists of a property keyword e, separated by an equal sign (=). Each property

n line in the script. The order of properties within a the starting Container or Channel keyword, d keyword) is not significant.

roperties, such as Type, are required, whereas l. Table 3-3 lists which properties are optional and e is used when that property is not specified.

be written in any combination of upper- or ers. Script lines can include any number of spaces

Script Mode

and tabs both within keywords, or when separating keywords and their values. Blank lines are ignored.

The pound character (#) indicates the start of a comment. The CCU ignores all characters on a line that begins with a pound sign. You can use comments following container property assignments, or on their own lines. See Example on page 3-22 to see a sample script that includes comments.

Container DefinTable 3-3 lists the definition block. Tis required, and itarranged so the re

Table

Keyword

Container

Drives

Type3-9

ition Block Propertiesproperties that can be specified within a container he table lists each propertys keyword, whether it

s default value (if any). Note that the keywords are quired keywords are listed first.

3-3. Container Definition Block Properties

Required? Default Value Description

Yes None Indicates the start of a container definition block. See page 3-12 for more information.

Yes None Specifies the disk drives used in creating the container.See page 3-12 for more information.

Yes None Indicates the type of container to create.See page 3-12 for more information.

3-10


End Yes None Indicates the end of a container definition block.See page 3-13 for more

FailoverDrive

InitializeAll

Method

ReadCache

Table 3-3. Container Definition Block Properties

Keyword Required? Default Value Descriptioninformation.

s No None Specifies the failover drives to assign to this container.See page 3-13 for more information.

No No Indicates whether to initialize all the drives connected to the controller.See page 3-14 for more information.

No Scrub Indicates which method (scrub or clear) to use when creating a RAID 5 container.See page 3-15 for more information.

No Yes Indicates whether read caching is enabled for this container.See page 3-15 for more information.

Script Mode

The following sec

Size No Maximum Specifies the size of the container.See page 3-16 for more information.

StripeSize

Wait

WaitForScrub

WriteCache

Table 3-3. Container Definition Block Properties

Keyword Required? Default Value Description3-11

tions describe each of these keywords in detail.

No 32 Specifies the size of contiguous I/O, in bytes.See page 3-16 for more information.

No Yes Indicates whether the CCU should wait for the new containers scrub or clear to complete before continuing.See page 3-17 for more information.

No Yes Is provided for backward compatibility only.See page 3-17 for more information.

No Yes Indicates whether write caching is enabled for this container.See page 3-17 for more information.

3-12


The Container Keyword

The Container keyword indicates the start of a container definition block. It accepts an optional container label value.

This keyword is required.

Examples:ContainerContainer

The Drives Keywo

The Drives keywcontainer.

This property is r

A drive is identifiseparated by colomultiple drive ide

Note: Anyinitializedspecified script, it w

Examples:Drives=0:Drives=0:

The Type Keyword

The Type keywor

This keyword is r

The possible valu

VolumeVo

RAID 0RA

RAID 1RA

RAID 5RA=MyData

rd

ord specifies the disk drives to use in creating the

equired; there is no default value.

ed by its channel number, ID (target), and LUN, ns. For example, 0:0:0 or 1:2:0. Separate ntifiers with commas.

drive specified within the script file will first be , destroying any data on that drive. If a drive is

in more than one container definition block in a ill be initialized only once.

0:00:0,0:1:0,0:2:0

d indicates the type of container to create.

equired; there is no default value.

es are as follows:

lume (JBOD) set

ID 0 (stripe) set

ID 1 (mirror) set

ID-5 set

Script Mode

RAID 10RAID 10 (stripe of mirrors) set

RAID 50RAID 50 (stripe of RAID 5) set

The minimum number of disk drives required to create each type of container is as follows:

Volume1

RAID 01

RAID 12

RAID 53

RAID 104

RAID 506

Examples:Type=VoluType=RAID

Note: Theexceed 32

The End Keyword

The End keyword

This keyword is r

Example:End

The FailoverDrives

The FailoverDrassign to this contway as the Drive

The FailoverDrfailover drives are3-13

me1

number of drives used for each RAID level cannot drives (16 drives for RAID 5).

indicates the end of a container definition block.

equired.

Keyword

ives keyword specifies the failover drives to ainer. Failover drives are specified in the same s property.

ives property is optional; if not specified, no assigned to this container.

3-14


Note the following:

When assigning failover drives to a RAID 10 container, the CCU assigns all the drives in the list to all the mirror set containers within the RAID 10 container.

The CCU makes no checks to ensure that the amount of freespace on the specified failover drives is sufficient to serve as failover for the given container.

Example:FailoverD

The InitializeAll Ke

The Initializeconnected to the ccontainers deletedapplies to all driv

The possible valu

YesInitial

NoDo notwith the Dri

The Initializevalue No is used.

The Initializeindependent within any container dto the controller adeleted before ancreated.

If there is no Initthe script, the CCDrives propertyfor more details.

Note that it is notmore than one coInitializeAllrives=1:0:0,1:1:0

yword

All keyword indicates that all the drives ontroller should be initialized, and any existing , before creating a new container. This property

es on all channels of the controller.

es are as follows:

ize all drives.

initialize all drives; only those drives specified ves property keyword are initialized.

All property is optional; if it is not specified, the

All keyword is both global and position-in a script file. If InitializeAll=Yes appears efinition block within the file, all drives connected re initialized and any existing containers are y new containers (defined within the script) are

ializeAll=Yes property specified anywhere in U initializes only those drives specified with the keyword. See Initializing a Disk Drive on page 2-6

necessary to specify InitializeAll=Yes in ntainer definition block. If both =Yes and InitializeAll=No are specified

Script Mode

within a script file, regardless of their position within the file, InitializeAll=Yes is the overriding value.

Examples:InitializeAll=YesInitializeAll=No

The Method Keyword

The Method keywa RAID 5 containe

The possible valu

ScrubScr

ClearCle

Overall, the Scruyou to begin usinalthough faster, mcontainer.

The Method propScrub is used.

Note that the MetOther redundant the scrub methodthe definition bloc

Examples:Method=ScWaitForCl

The ReadCache K

The ReadCache kcaching.

The possible valu

YesEnabl

NoDisable3-15

ord indicates which method to use when creating r.

es are as follows:

ub the container.

ar the container.

b method takes longer than Clear, but it enables g the container immediately. The Clear method, ust complete before you can begin using the

erty is optional; if not specified, then the value

hod property applies only to RAID 5 containers. container types (RAID 1 and RAID 10) always use . The CCU ignores any Method property within k of any container type other than RAID 5.

rubear=No

eyword

eyword indicates whether this container uses read

es are as follows:

e read caching.

read caching.

3-16


If no ReadCache property is specified, the value Yes is used.

Example:ReadCache=Yes

The Size Keyword

The Size keyword specifies the size of the container. Specify the size as an integer or a decimal number, followed by the unit keyword MB (mekeyword is requirspecified, the CCU

Specify the keywomaximum availabselected. If no Sizused.

Examples:Size=2.5GSize=300MSize=Maxi

The StripeSize Key

The StripeSizeKbytes, written toswitching to the n

This property appRAID 50, and RAis specified for an

The possible valuspecify a unit keyKbytes.

If no StripeSizsupports this prop

Example:StripeSizgabytes), GB (gigabytes), or TB (terabytes). A unit ed with a numeric size value. If no unit keyword is exits with an error.

rd Maximum to create a container using the le space, based on the container type and drives e property is specified, the value Maximum is

B

Bmum

word

keyword specifies the size of contiguous I/O, in each member of a striped container before ext member.

lies only to container types RAID 0, RAID 5, ID 10. The CCU exits with an error if this property y other container types.

es for StripeSize are 8, 16, 32, and 64. Do not word for the stripe size because all values are in

e property is specified and the container type erty, the value 32 is used by default.

e=64

Script Mode

The Wait Keyword

The Wait keyword indicates whether the CCU should wait for the new container's scrub or clear to complete before continuing.

The Wait property is optional; if not specified, the CCU waits for the containers scrub or clear to complete before continuing. Specify Wait=No to allow the CCU to continue while the scrub or clear completes in the background.1

Examples:Wait=YesWait=No

The WaitForScrub

The WaitForScrcompatibility onlyWaitForScrub kinterchangeably w

The WriteCache K

The WriteCachefor this container.

The possible valu

YesEnablbattery and

NoDisable

AlwaysEor the batter

1 Container scrubs and do not dependIf the controller is then restarted, theintervention.3-17

Keyword

ub keyword is provided for backward . Use the Wait keyword instead. The eyword is still recognized and can be used ith the Wait keyword.

eyword

keyword indicates whether write caching is used

es are as follows:

e the write cache if the cache is protected by a the batterys status is OK.

the write cache.

nable the write cache even if no battery is present, ys status is not OK.

and clears are tasks executed entirely on the controller, on the CCU or any other host application to complete.

powered off before the scrub or clear completes and is scrub or clear task resumes without any user

3-18


Note: Setting a containers WriteCache property to Always might result in data loss or corruption if power to the controller is lost when no battery is present or the battery loses its charge.

If no WriteCache property is specified, the value Yes is used.

Examples:WriteCachWriteCach

Channel DefinitTable 3-4 lists the definition block. Tdescription of the

Note that channeldefault values. If corresponding coSimilarly, if no chacurrent controller

Table

Keyword

Channel

Ende=Yese=Always

ion Block Propertiesproperties that you can specify within a channel he table lists each propertys keyword and a

property.

properties, unlike container properties, have no a Channel property keyword is not specified, the ntroller setting for that channel is not changed. nnel definition block is specified for a channel, the

settings for that channel are not changed.

3-4. Channel Definition Block Properties

Description

Specifies the channel number to which the channel properties apply. This keyword begins a channel definition block. Buses are numbered from zero to the maximum number of channels on the controller minus one.You can include multiple channel definition blocks within a script file, each beginning with a Channel keyword and value.Example:

Channel=0

Indicates the end of a channel definition block.Example:

End

Script Mode

Error HandlinBecause the CCUinteraction, the CCsimply exiting im

Whenever the CCfor example, an unerror and exits. If page 1-2), the CCUOtherwise, it disp

Upon exit, the CCzero error code asvariable ERRORLEfile, that batch filecommand IF ERRto test the CCU suspecific error usin

Table 3-5 lists the

ControllerID Specifies the SCSI ID of the controller on the channel. Normally, the controller is assigned SCSI ID 7 on each of its channels. You can specify any ID value between 0 and 15.If you do not specify a ControllerID keyword for the channel, the channels current controller ID setting is not changed.

Code Error/Infor

0 You ran Cmade no

1 No Contr

Table 3-4. Channel Definition Block Properties3-19

g scripting feature is designed to run without user

U handles error during record and playback by mediately whenever an error is detected.

U encounters an error during record or playbackrecognized keyword in a script fileit reports the

a log file is opened (see Running the CCU on writes the error message to the log file.

lays the message on the screen.

U returns its exit status (zero for success or a non-sociated with an error) in the DOS environment VEL. When the CCU is run within a DOS batch can examine the CCUs exit status using the DOS ORLEVEL n. The batch file can use this command ccess or failure status. The batch file can test for a g a series of If ERRORLEVEL n commands.

possible status codes returned by the CCU.

Example:

ControllerID=15

Table 3-5. Error Codes

mation Meaning

CU and changes.

This exit code indicates success (that is, the CCU exited with no errors) and that no report is required.

oller Found. The CCU did not detect any controllers in the system.

3-20


2 Syntax or logical error in the script file.

The CCU encountered an invalid command or keyword in the specified script file.

3 Unable to open file. The CCU was unable to open the specified script or log file.

4 Error in thline param

5 Unable toconfigura

6 No drives

7 Specifiedfound in

8 Specifiedsize too s

9 Specifiedsize too b

10 Number not matchcontainer

11 Unable todrive.

12 Error occcreating c

13 Too manydrives ass

14 Insufficieto run the

15 Incorrect number.


Code Error/Information Meaninge command eters.

You passed an invalid command-line switch to the CCU. (See Script Mode on page 3-1 for the list of valid command switches.)

read system tion.

The CCU was unable to get the configuration information from the specified controller.

detected. The CCU did not detect any disk drives attached to the selected controller.

drive not system.

The disk drive you specified does not exist on the selected controller.

container mall.

You specified a container size that is smaller than the minimum size allowed for this container.

container ig.

You specified a container size that is larger than the maximum size allowed for this container.

of drives do the

type.

The number of drives you selected is invalid for the type of container specified.

initialize The CCU was unable to initialize one or more disk drives.

urred while ontainer.

The CCU encountered an error creating a container.

failover igned.

You attempted to assign more than the maximum number of failover drives allowed for the specified container.

nt memory application.

There is not enough memory to run the CCU.

controller The controller number you specified is invalid or out-of-range.

Script Mode

Playback andWhen using CCU

When recordkeyword wi

When playinrecord optiosetting Waitedit the scripcontainers d

When recordCCU cannotmirror set coscript file; thfailover driv

In this case, the drives aswithin the Rthe CCU assthe mirror seHowever, thdrive assign

When recordchannel defiEach block ireflecting thnecessary to

16 Controller not responding.

The controller has stopped responding to the CCU.

17 Scrub/Clear failed The scrub or clear running on one or more containers has failed.

100 You ran CCU and made cha

The exit code indicates success (that is,


Code Error/Information Meaning3-21

Record Notes in playback or record mode:

ing a container, the CCU does not create a Wait thin a containers definition block in a script file.

g back any script file generated from the CCU n, be aware that the CCU will use the default =Yes when creating a container unless you first t file and include a Wait=No line in the efinition block.

ing a RAID 10 (stripe of mirrors) container, the map failover drives assigned to the individual ntainers to the FailoverDrives list in the resultant e script file syntax allows only a single list of es to be assigned to any given container.

the CCU creates the FailoverDrives list using all signed to the lower-level mirror set containers AID 10 container. When playing back this script, igns all the drives in the FailoverDrives list to all t containers making up the RAID 10 container. is might not exactly match the original failover ments to the mirror set containers.

ing a container, the CCU creates a separate nition block for each channel on the controller. ncludes all the property keywords and values e channels current settings. Edit the script file as change any of the channels settings or delete

nges. CCU exited with no errors) and that a reboot is required.

3-22


keywords to ensure the controllers corresponding channel setting is not changed.

ExampleThe following DOS command invokes the CCU and creates containers on controller 1 based on the container properties defined in the script file A:\RAID.CCU. It also configures the properties of channel 0 and savC:\RAID.LOG.

A:\> CCU

The following exaprevious CCU com500MB, single-dis(mirror) containercontainerand se

# Script # RAID-5 # Create # MySystContainerType=VoluSize=500MDrives=0:

# Assign FailoverDEnd

# Create ContainerType=RAID

Size=2GB

#Use drivDrives=0:es a log of the operation in the log file

/P A:\RAID.CCU /L C:\RAID.LOG /C1

mple is the RAID.CCU script file used in the mand. This script creates three containersa

k volume container; a 2GB, two-drive RAID 1 ; and a maximum size, three-drive RAID 5 ts the properties of channel 0.to create volume, mirror, andcontainersa 500MB volume set labeled em

=MySystemme B0:0

drive 1:0:0 as the failover drive.rives=1:0:0

a 2GB mirror set labeled MyMirror=MyMirror1

es on channels 0 and 11:0,1:1:0

Script Mode

# Disable write cacheWriteCache=No

#Assign 2 failover drivesFailoverDrives=1:2:0, 1:3:0End

# Create # MyDataContainerType=RAID

Size=Maxi

# Use theStripeSiz

# Clear tMethod=Cl

#Dont waWait=No

#Use drivDrives=0:

#Assign fFailoverDEnd

# Set ChaChannel=03-23

a maximum size RAID 5 set labeled=MyData5

mum

maximum stripe sizee=64

he container (dont scrub it)ear

it for clear to complete

es 2, 3, 4 on channel 02:0, 0:3:0, 0:4:0

ailover drivesrives=1:1:0,1:2:0

nnel 0 properties

3-24


# Set the controllers SCSI ID to 7ControllerID=7End

Index

/C switch 3-3/L switch 3-3/P switch 3-2/R switch 3-2

Aadapters

cold-swapping 2hot-swapping 2

Assigned failover dremoving drives

BBIOS

accessing the CCdetecting new ha

bootable containers

CCCU

/C switch 3-3/L switch 3-3/P switch 3-2/R switch 3-2accessing

from BIOS 1-from MS-DOS

command-line swexample 3-22interactive mode

overview 1-1overview 1-1playback mode

initializing drives 3-5Index-1

-8-8rives list 2-52-5

U 1-1rdware 2-82-6

11-1itches 3-2

2-1

3-2

properties 3-4record mode 3-2running 1-2script mode 3-1

overview 1-1playback mode 3-3 to 3-6record mode 3-6 to 3-24switches 3-2

shared channels 1-2supported container types 3-6user notes 3-21

channel definition blockChannel keyword 3-18ControllerID keyword 3-19End keyword 3-18overview 3-18

Channel propertychannel definition block 3-18

clear status 3-6cold-swapping adapters 2-8command-line switches 3-2comments, in script files 3-9container definition block

Container keyword 3-12definition 3-8Drives keyword 3-12End keyword 3-13FailoverDrives keyword 3-13InitializeAll keyword 3-14Method keyword 3-15properties 3-9ReadCache keyword 3-15required keywords 3-9Size keyword 3-16


Index-2

StripeSize keyword 3-11Type keyword 3-12Wait keyword 3-17WaitForScrub keyword 3-17WriteCache keyword 3-17

Container Properties dialog box 2-4deleting containers 2-7

Container Properties menu 2-2Container property

definition blockcontainers

bootable 2-6creating 2-1deleting 2-7displaying assocmanaging 2-4minimum drivesmultilevel, and sproperties 2-2

Drives 3-4FailoverDriveLabel 3-4ReadCache 3Size 3-4StripeSize 3-4Type 3-4WriteCache 3

read caching 2-4selecting partitiosize 2-3stripe size 2-3types 3-6types of 2-2viewing propertwrite caching 2-

controller number, ControllerID prope

channel definitiodescription 3-5

creating containers

Ddeleting containers 2-7deselecting drives 2-2disks

displaying associated 2-5initializing drives 2-6

DOS, accessing the CCU 1-1, container 3-12

iated disks 2-5

2-2crub tasks 3-7

s 3-4

-4

-4

ns 2-1

ies 2-44specifying 3-3rtyn block 3-19

2-1

drivesdeselecting 2-2failover 2-5initializing 3-5minimum required 2-2

Drives propertycontainer definition block 3-12initializing drives 3-5overview 3-4

EEnd property

channel definition block 3-18container definition block 3-13

error handlinglist of codes 3-19script mode 3-19

ERRORLEVEL variable 3-19

Ffailover drives 2-5Failover Management for Container

dialog box 2-5FailoverDrives keyword

container definition block 3-13FailoverDrives property 3-4freespace, displaying 2-1

Hhot-swapping adapters 2-8

Index

Iinitialize

disk drivesinteractive mode 2-6script mode 3-5

Initialize Drives option 2-6InitializeAll property

container definitdescription 3-5

interactive mode 2-overview 1-1

LLabel property 3-4List of Containers d

assigning failoveremoving failove

log filessample 3-7switch 3-3

MManage Container

deleting containmaking a contain

Manage Containersassigning and re

drives 2-5removing failove

managing containerMethod property, c

definition blockmirror set, descripti

Ppartitions 2-1playback mode

clear status 3-6initializing drive

properties 3-4scrub status 3-6switch 3-2user notes 3-21

propertiescontainer 2-2

viewing 2-4container definition block 3-9Index-3

ion block 3-14

1

ialog box 2-4r drives 2-5r drives 2-5

option 2-4ers 2-7

er bootable 2-6 dialog boxmoving failover

r drives 2-5s 2-4

ontainer 3-15on 2-2

s 3-5

ControllerID 3-5Drives 3-4FailoverDrives 3-4InitializeAll 3-5Label 3-4playback mode 3-4ReadCache 3-4Size 3-4StripeSize 3-4, 3-16Type 3-4WriteCache 3-4

RRAID 0 container, description 2-2RAID 1 container, description 2-2RAID 10 containers

description 2-3scrub operations on 3-8

RAID 5 container, description 2-3RAID 50 containers

description 2-3scrub/clear operations on 3-8

RAID10 containersdisplaying associated disks 2-5

read caching 2-4ReadCache property

container definition block 3-15description 3-4

record modecontainer definition block 3-8script file syntax 3-8switch 3-2user notes 3-21


Index-4

removing failover drives 2-5running the CCU 1-2

Sscript files

syntax 3-8comments in 3-9

script mode 3-1command-line sw

error handling 3overview 1-1

scrub tasks

determining staton multilevel con

Select failover driveshared channels 1-2

Size propertycontainer definitdescription 3-4

status, of scrub or cstripe of mirrors, destripe of RAID5, destripe set, descriptio

stripe size 2-3StripeSize property

description 3-4

supported containesyntax of script files

TType property

container definit

description 3-4

Vvolume container 2

WWait property, container definition

block 3-17WaitForScrub property, container

definition block 3-17write caching 2-4WriteCache property

container definition block 3-17itches 3-2

-19

us 3-6tainers 3-7s list 2-5

ion block 3-16

lear 3-7scription 2-3

scription 2-3n 2-2

3-16

r types 3-63-8

ion block 3-12

-2

description 3-4

2000 2002 AdaptecAll rights reserved. Adaptec and the Adaptec logoare trademarks of Adaptec which may be registered in some jurisdictions.

Part Number: 513131-06, Ver. AA SEF 01/02

Adaptec, Inc.691 South Milpitas BoulevardMilpitas, CA 95035 USA

R

Adaptec SCSI RAIDContainer Configuration Utility Users GuideContents1 Introduction2 Interactive Mode3 Script ModeIndex

IntroductionInteractive Versus Script ModeShared ChannelsRunning the CCU

Interactive ModeCreating a ContainerManaging Containers

Script ModePlayback ModeRecord ModeScript File SyntaxError HandlingPlayback and Record NotesExample

IndexABCDEFHILMPRSTVW

storage configuration

Documents

adaptec software software

trademarks of adaptec

adaptec logo

musan adaptec raid

adaptec raid controller

license terms applicable

following terms

product dpermission