Table of Contents
Advertisement
End Keyword
End is a required keyword, indicating the end of the block.
HotspareDrives Keyword
Hotspare Drives is an optional keyword, specifying the hot spares to assign to the array. The
syntax for listing hot spares is the same as the
not specified, no hot spares are assigned to the array.
For example:
HotspareDrives=0:0:0,0:1:0
The same disk drive can be assigned to protect multiple arrays (as a pool spare). Once a pool
spare is used by a failed disk drive, however, it is no longer available to protect the other arrays
its assigned to.
This keyword does not verify that the available space on the specified hot spares is sufficient to
serve as failover for the array.
When assigning hot spares to a multilevel array, Hotspare Drives assigns all the hot spares in
the list to all arrays within the multilevel array.
InitializeAll Keyword
If you want the ACU to initialize all drives connected to the controller and delete any existing
arrays before any new arrays are created, even those that are not specified in any Drives
keyword definition, specify InitializeAll=Yes. Otherwise, the ACU initializes only those drives
specified by the Drives keyword.
Caution:
Initializing a disk drive automatically deletes any existing arrays with that disk
!
drive as their member.
Possible values:
Yes—Initialize all drives.
No (default)—Do not initialize all drives; only those drives specified with the
keyword are initialized.
For example:
Type=Volume
Type=RAID1
InitializeAll is a global keyword that you need to specify only once.
InitializeAll is always performed prior to array creation regardless of its position in the script.
If both InitializeAll=Yes and InitializeAll=No are specified in the same script file,
InitializeAll=Yes is always the overriding value.
If an array is deleted during a Build/Verify process, the process is automatically terminated.
Appendix D: Using the Array Configuration Utility for DOS
Drives Keyword on page
91
90. If Hotspare Drives is
Drives
Advertisement
Table of Contents
