HP ProLiant DL280 Configuring Arrays on HP Smart Array Controllers Reference G - Page 63

Replacing an array, Extending a logical drive, Example commands, Syntax

Get HP ProLiant DL280 PDF manuals and user guides View all HP ProLiant DL280 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 63 highlights

drives by specifying the new destination drives in the command (1e:1:12-1e:1:14). To maintain the same spare drive, be sure to designate the spare drive for the moved array. Example commands: => array a modify drives=1e:1:12-1e:1:14 spares=1e:1:9 => array b modify drives=1c:1:6-1c:1:7 Replacing an array Some controllers may not support this option or may require a license key to enable this feature. You can replace an array by designating different physical drives for the array. To replace the array, each of the physical drives where the array will reside must meet the following criteria: • The destination drives must all be the same type (for example, SATA or SAS), but do not have to be same type as the drives in the source array. • A destination drive does not have to be an unassigned drive, but if it is assigned, it must be a drive assigned to the array being replaced. • The destination drives must have sufficient capacity to hold all the logical drives present in the source array. Like array creation and expansion, the useable space in all drives is reduced to the size of the smallest physical drive in the destination disk set. Replacing an array automatically removes any previously assigned spare drives. If spares are assigned to the existing array, they must be designated for the array when it is moved. Syntax: modify drives spares where is an array, and the specified physical drives are the new destination for the array. For example, in an existing array, three 72-GB SAS drives (1e:1:4-1e:1:6) are the source. Another drive of the same size is the spare (1e:1:9). With all criteria met, you can move the array to three different 72-GB SAS or SATA drives by specifying the new destination drives in the command (1e:1:12-1e:1:14). To maintain the same spare drive, be sure to designate the spare drive for the moved array. Example commands: => array a modify drives=1e:1:12-1e:1:14 spares=1e:1:9 => array b modify drives=1c:1:6-1c:1:7 Extending a logical drive If the operating system supports logical drive extension, you can use any unassigned capacity on an array to enlarge one or more of the logical drives on 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: modify size=#|max|? [forced] where is a logical drive. HP Array Configuration Utility 63

  • 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
HP Array Configuration Utility
63
drives by specifying the new destination drives in the command (1e:1:12-1e:1:14). To maintain the same
spare drive, be sure to designate the spare drive for the moved array.
Example commands:
=> array a modify drives=1e:1:12-1e:1:14 spares=1e:1:9
=> array b modify drives=1c:1:6-1c:1:7
Replacing an array
Some controllers may not support this option or may require a license key to enable this feature.
You can replace an array by designating different physical drives for the array. To replace the array, each
of the physical drives where the array will reside must meet the following criteria:
•
The destination drives must all be the same type (for example, SATA or SAS), but do not have to be
same type as the drives in the source array.
•
A destination drive does not have to be an unassigned drive, but if it is assigned, it must be a drive
assigned to the array being replaced.
•
The destination drives must have sufficient capacity to hold all the logical drives present in the source
array.
Like array creation and expansion, the useable space in all drives is reduced to the size of the smallest
physical drive in the destination disk set.
Replacing an array automatically removes any previously assigned spare drives. If spares are assigned to
the existing array, they must be designated for the array when it is moved.
Syntax:
<target> modify drives=[#:]#:#-[#:]#:# spares=[#:]#:#-[#:]#:#
where
<target>
is an array, and the specified physical drives are the new destination for the array.
For example, in an existing array, three 72-GB SAS drives (1e:1:4-1e:1:6) are the source. Another drive of
the same size is the spare (1e:1:9). With all criteria met, you can move the array to three different 72-GB SAS
or SATA drives by specifying the new destination drives in the command (1e:1:12-1e:1:14). To maintain the
same spare drive, be sure to designate the spare drive for the moved array.
Example commands:
=> array a modify drives=1e:1:12-1e:1:14 spares=1e:1:9
=> array b modify drives=1c:1:6-1c:1:7
Extending a logical drive
If the operating system supports logical drive extension, you can use any unassigned capacity on an array
to enlarge one or more of the logical drives on 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> modify size=#|max|? [forced]
where
<target>
is a logical drive.