Adaptec 2410SA User Guide - Page 86

Record Mode, Determining Build/Verify/Clear Status, InitializeAll=Yes, Wait=No

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

Page 86 highlights

DOS Utilities Because the ACU reads the entire script file before creating any arrays, the position of the InitializeAll=Yes property within the script is not significant. Continuing the previous example, if InitializeAll=Yes is specified in the second RAID 5's definition, the ACU initializes all drives before creating the first RAID 0. Note: If a build/verify is in progress when an array is deleted, it is automatically terminated. See InitializeAll Keyword on page B-28 for details on the syntax of the InitializeAll property. Record Mode Record mode writes an existing controller's array configuration to a specified script file, enabling you to create the same configuration by running the ACU in playback mode with the resulting script. In addition, record mode lists certain controller properties that can be set in playback mode. Because the ACU supports only a subset of array types available through the CLI and the GUI, it cannot record all the possible array configurations. If the ACU encounters an array that it cannot create it displays a warning (and records the warning in its log file, if that switch is used) and does not record any properties for that array in its script file. The script file is limited to one controller and its associated array configuration files. Although you can have multiple controllers on a single system, you cannot record all of the controllers and their associated array configurations in one file. To record multiple controllers, use the ACU record mode once for each individual controller. Your result will be multiple files on the same disk with one file corresponding to each controller. Determining Build/Verify/Clear Status When using playback mode to create an array, you can specify whether to wait for an array's initial build/verify or clear to complete or to continue while the build/verify or clear proceeds in the background. If you instruct the ACU to continue (Wait=No), you need to be able to check the status of a background build/verify or clear task and determine when it is complete. B-22

  • 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
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
B-22
DOS Utilities
Because the ACU reads the entire script file before creating any
arrays, the position of the
InitializeAll=Yes
property within the
script is not significant. Continuing the previous example, if
InitializeAll=Yes
is specified in the second RAID 5
’
s definition,
the ACU initializes all drives before creating the first RAID 0.
Note:
If a build/verify is in progress when an array is deleted,
it is automatically terminated.
See
InitializeAll Keyword
on page B-28
for details on the syntax of
the
InitializeAll
property.
Record Mode
Record
mode writes an existing controller
’
s array configuration to
a specified script file, enabling you to create the same configuration
by running the ACU in playback mode with the resulting script. In
addition, record mode lists certain controller properties that can be
set in playback mode.
Because the ACU supports only a subset of array types available
through the CLI and the GUI, it cannot record all the possible array
configurations. If the ACU encounters an array that it cannot create
it displays a warning (and records the warning in its log file, if that
switch is used) and does not record any properties for that array in
its script file.
The script file is limited to one controller and its associated array
configuration files. Although you can have multiple controllers on
a single system, you cannot record all of the controllers and their
associated array configurations in one file. To record multiple
controllers, use the ACU record mode once for each individual
controller. Your result will be multiple files on the same disk with
one file corresponding to each controller.
Determining Build/Verify/Clear Status
When using playback mode to create an array, you can specify
whether to wait for an array
’
s initial build/verify or clear to
complete or to continue while the build/verify or clear proceeds in
the background. If you instruct the ACU to continue (
Wait=No
),
you need to be able to check the status of a background
build/verify or clear task and determine when it is complete.