Setting the spare activation mode, Spare management mode in hpssacli, Expanding an array – HP Smart Storage Administrator User Manual
Page 62
Operations 62
=> ctrl slot=4 array all add spares=1:5,1:7
=> ctrl slot=5 array A add spares=1:1–1:5
=> ctrl slot=5 array A remove spares=1:1–1:5
Setting the spare activation mode
The spare activation mode feature enables the controller firmware to activate a spare drive under the
following conditions:
•
When a data drive reports a predictive failure (SMART) status
•
When a data drive fails; this mode is the default.
In normal operations, and for older controllers, the firmware starts rebuilding a spare drive only when a data
drive fails. With the predictive failure activation mode, rebuilding can begin before the drive fails, reducing
the likelihood of data loss that could occur if an additional drive fails.
Use the spareactivationmode keyword to toggle the spare activation mode for the controller between
drive failure and drive predictive failure.
Syntax:
<target> modify spareactivationmode=[ failure | predictive ]
Example commands:
controller slot=1 modify spareactivationmode=predictive
controller slot=1 modify spareactivationmode=failure
Spare Management Mode in HPSSACLI
The sparetype keyword allows you to specify the spare type as "dedicated" (default) or "autoreplace." A
dedicated spare temporarily takes over for a failed drive and can be shared between arrays. An autoreplace
spare replaces a failed drive and cannot be shared between arrays.
Command example:
To add a spare with spare type of autoreplace:
=> ctrl slot=1 array A add spares=1e:1:5 sparetype=autoreplace
Expanding an array
You can increase the storage space on an array by adding physical drives. Any drive that you want to add
must meet the following criteria:
•
It must be an unassigned drive.
•
It must be of the same type as existing drives in the array (for example, SATA or SAS).
•
It must have a capacity no less than that of the smallest drive in the array.
IMPORTANT:
An array expansion, logical drive extension, or logical drive migration takes
about 15 minutes per gigabyte. While this process is occurring, no other expansion, extension,
or migration can occur simultaneously on the same controller. Controllers that do not support a
battery-backed write cache do not support this process.
Syntax:
<target> add drives=[#:]#:#,[#:]#:#,[#:]#:#–[#:]#:#,...|allunassigned
[forced]