HP ProLiant BL660c Configuring Arrays on HP Smart Array Controllers Reference - Page 68

Migrating a logical drive, Using Selective Storage Presentation

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

Page 68 highlights

If the operating system does not support logical drive extension, carrying out this command makes data on the logical drive unavailable. Therefore, the CLI displays a warning prompt as a safeguard in case you are using such an operating system. To prevent the prompt from appearing, use the forced parameter. Example commands: => ctrl slot=3 ld 1 modify size=max => ctrl slot=4 ld 1 modify size=? => ctrl slot=3 ld 2 modify size=500 forced Migrating a logical drive This command enables you to adjust the stripe size (data block size) or RAID level of a selected logical drive. For more information, see "Selecting a RAID method (on page 103)." Consider the following factors before performing a migration: • For some RAID-level migrations to be possible, you might need to add one or more drives to the array. • For migration to a larger stripe size to be possible, the array might need to contain unused drive space. This extra space is necessary because some of the larger data stripes in the migrated array are likely to be filled inefficiently. 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 [raid=0|1+0|1|5|6|adg|?] [ss=8|16|32|64|128|256|default|?] where is a logical drive. The following limitations apply to this command: • You cannot simultaneously query the RAID level and the stripe size of any given logical drive. • If you do not specify a RAID level for a query or migration, the CLI uses the existing value by default. • If you do not specify a stripe size, the CLI uses the default stripe size value for the RAID level that you specify. Example commands: => ctrl slot=3 ld 1 modify raid=1 => ctrl slot=4 ld 2 modify ss=16 => ctrl slot=2 ld 3 modify raid=5 ss=16 Using Selective Storage Presentation The SSP feature (also known as Access Control List commands) enables you to allow only specific adapter IDs or connection names to have access to particular logical drives. This functionality is useful for preventing the corruption of data that can occur when different servers using different operating systems access the same data. Syntax: Using SSP requires two commands: HP Array Configuration Utility 68

  • 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
HP Array Configuration Utility
68
If the operating system does not support logical drive extension, carrying out this command makes data
on the logical drive unavailable. Therefore, the CLI displays a warning prompt as a safeguard in case you
are using such an operating system. To prevent the prompt from appearing, use the
forced
parameter.
Example commands:
=> ctrl slot=3 ld 1 modify size=max
=> ctrl slot=4 ld 1 modify size=?
=> ctrl slot=3 ld 2 modify size=500 forced
Migrating a logical drive
This command enables you to adjust the stripe size (data block size) or RAID level of a selected logical
drive. For more information, see "Selecting a RAID method (on page
103
)."
Consider the following factors before performing a migration:
•
For some RAID-level migrations to be possible, you might need to add one or more drives to the
array.
•
For migration to a larger stripe size to be possible, the array might need to contain unused drive
space. This extra space is necessary because some of the larger data stripes in the migrated array
are likely to be filled inefficiently.
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 [raid=0|1+0|1|5|6|adg|?]
[ss=8|16|32|64|128|256|default|?]
where
<target>
is a logical drive.
The following limitations apply to this command:
•
You cannot simultaneously query the RAID level and the stripe size of any given logical drive.
•
If you do not specify a RAID level for a query or migration, the CLI uses the existing value by default.
•
If you do not specify a stripe size, the CLI uses the default stripe size value for the RAID level that you
specify.
Example commands:
=> ctrl slot=3 ld 1 modify raid=1
=> ctrl slot=4 ld 2 modify ss=16
=> ctrl slot=2 ld 3 modify raid=5 ss=16
Using Selective Storage Presentation
The SSP feature (also known as Access Control List commands) enables you to allow only specific adapter
IDs or connection names to have access to particular logical drives. This functionality is useful for
preventing the corruption of data that can occur when different servers using different operating systems
access the same data.
Syntax:
Using SSP requires two commands: