HP StorageWorks P2000 HP StorageWorks P2000 G3 MSA System SMU Reference Guide - Page 22

Related topics, About spares

Get HP StorageWorks P2000 - G3 MSA Array Systems PDF manuals and user guides View all HP StorageWorks P2000 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 22 highlights

• For maximum use of a dual-controller system's resources, each controller should own a similar number of vdisks. • Set the chunk size to match the transfer block size of the host application. Related topics • About RAID levels on page 30 • About spares on page 22 • About volumes on page 23 • Vdisk topics in Provisioning the system on page 57 • Configuring a vdisk on page 52 • Verifying a vdisk on page 81 • Scrubbing a vdisk on page 81 • Viewing information about a vdisk (page 88), all vdisks (page 87), or the system (page 85) • Removing a vdisk from quarantine on page 82 About spares A controller automatically reconstructs a redundant (fault-tolerant) vdisk (RAID 1, 3, 5, 6, 10, 50) when one or more of its disks fails and a properly sized spare disk is available. There are three types of spares: • Dedicated spare. Reserved for use by a specific vdisk to replace a failed disk. Most secure way to provide spares for vdisks but expensive to reserve a spare for each vdisk. • Global spare. Reserved for use by any redundant vdisk to replace a failed disk. • Dynamic spare. A properly sized available disk that is automatically assigned to replace a failed disk in a redundant vdisk. When a disk fails, the system looks for a dedicated spare first. If it does not find a properly sized dedicated spare, it looks for a global spare. If it does not find a properly sized global spare and the dynamic spares option is enabled, it takes any properly sized disk having Available status. If no properly sized spares are available, reconstruction cannot start. A best practice is to designate spares for use if disks fail. Dedicating spares to vdisks is the most secure method, but it is also expensive to reserve spares for each vdisk. Alternatively, you can enable dynamic spares or assign global spares. Related topics • Configuring dynamic spares on page 48 • Managing dedicated spares on page 52 • Managing global spares on page 60 • Using the Provisioning Wizard on page 57 • Creating a vdisk on page 59 • Viewing information about a vdisk (page 88) or all vdisks (page 87) 22 Getting started

  • 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
22
Getting started
•
For maximum use of a dual-controller system’s resources, each controller should own a similar number
of vdisks.
•
Set the chunk size to match the transfer block size of the host application.
Related topics
•
About RAID levels
on page 30
•
About spares
on page 22
•
About volumes
on page 23
•
Vdisk topics in
Provisioning the system
on page 57
•
Configuring a vdisk
on page 52
•
Verifying a vdisk
on page 81
•
Scrubbing a vdisk
on page 81
•
Viewing information about a vdisk (
page 88
), all vdisks (
page 87
), or the system (
page 85
)
•
Removing a vdisk from quarantine
on page 82
About spares
A controller automatically reconstructs a redundant (fault-tolerant) vdisk (RAID 1, 3, 5, 6, 10, 50) when one
or more of its disks fails and a properly sized spare disk is available.
There are three types of spares:
•
Dedicated spare
. Reserved for use by a specific vdisk to replace a failed disk. Most secure way to
provide spares for vdisks but expensive to reserve a spare for each vdisk.
•
Global spare
. Reserved for use by any redundant vdisk to replace a failed disk.
•
Dynamic spare
. A properly sized available disk that is automatically assigned to replace a failed disk
in a redundant vdisk.
When a disk fails, the system looks for a dedicated spare first. If it does not find a properly sized
dedicated spare, it looks for a global spare. If it does not find a properly sized global spare and the
dynamic spares option is enabled, it takes any properly sized disk having Available status. If no properly
sized spares are available, reconstruction cannot start.
A best practice is to designate spares for use if disks fail. Dedicating spares to vdisks is the most secure
method, but it is also expensive to reserve spares for each vdisk. Alternatively, you can enable dynamic
spares or assign global spares.
Related topics
•
Configuring dynamic spares
on page 48
•
Managing dedicated spares
on page 52
•
Managing global spares
on page 60
•
Using the Provisioning Wizard
on page 57
•
Creating a vdisk
on page 59
•
Viewing information about a vdisk (
page 88
) or all vdisks (
page 87
)