Adaptec 2820SA User Guide - Page 88

End Keyword, HotspareDrives Keyword, InitializeAll Keyword, If HotspareDrives is

Get Adaptec 2820SA - Serial ATA II RAID Controller PDF manuals and user guides
UPC - 760884148969
View all Adaptec 2820SA manuals
Add to My Manuals
Save this manual to your list of manuals

Page 88 highlights

Appendix D: Using the ACU for DOS ● 88 End Keyword End is a required keyword, indicating the end of the block. HotspareDrives Keyword HotspareDrives is an optional keyword, specifying the hot spares to assign to the array. The syntax for listing hot spares is the same as the Drives Keyword on page 87. If HotspareDrives is 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, HotspareDrives 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 Drives 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.

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
Appendix D: Using the ACU for DOS
●
88
End Keyword
End is a required keyword, indicating the end of the block.
HotspareDrives Keyword
HotspareDrives is an optional keyword, specifying the hot spares to assign to the array. The
syntax for listing hot spares is the same as the
Drives Keyword
on page 87
. If HotspareDrives is
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, HotspareDrives 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
Drives
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.
!