HP P2000 HP P2000 G3 MSA System SMU Reference Guide - Page 53

Configuring a vdisk, Managing dedicated spares, Changing a vdisk’s name

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

Page 53 highlights

Configuring a vdisk Managing dedicated spares You can assign a maximum of four available disks to a redundant vdisk (RAID 1, 3, 5, 6, 10, 50) for use as spares by that vdisk only. A spare must be the same type (SAS or SATA, small or large form-factor) as other disks in the vdisk, and have sufficient capacity to replace the smallest disk in the vdisk. If a disk in the vdisk fails, a dedicated spare is automatically used to reconstruct the vdisk. A redundant vdisk other than RAID-6 becomes Critical when one disk fails. A RAID-6 vdisk becomes Degraded when one disk fails and Critical when two disks fail. After the vdisk's parity or mirror data is completely written to the spare, the vdisk returns to fault-tolerant status. For RAID-50 vdisks, if more than one sub-vdisk becomes critical, reconstruction and use of assigned spares occur in the order sub-vdisks are numbered. To change a vdisk's spares 1. In the Configuration View panel, right-click a vdisk and select Configuration > Manage Dedicated Spares. The main panel shows information about the selected vdisk, its spares, and all disks in the system. Existing spares are labeled SPARE. • In the Disk Sets table, the number of white slots in the SPARE entry's Disks field shows how many spares you can add to the vdisk. • In the enclosure view or list, only existing spares and suitable available disks are selectable. 2. Select spares to remove, disks to add as spares, or both. 3. Click Modify Spares. If the task succeeds, the panel is updated to show which disks are now spares for the vdisk. Changing a vdisk's name To change a vdisk's name 1. In the Configuration View panel, right-click a vdisk and select Configuration > Modify Vdisk Name. The main panel shows the vdisk's name. 2. Enter a new name. A vdisk name is case sensitive; cannot already exist in the system; cannot include a comma, double quote, or backslash; and can have a maximum of 20 bytes. 3. Click Modify Name. The new name appears in the Configuration View panel. Changing a vdisk's owner Each vdisk is owned by one of the controllers, A or B, known as the preferred owner. Typically, you should not need to change vdisk ownership. When a controller fails, the partner controller assumes temporary ownership of the failed controller's vdisks and resources, becoming the current owner. If the system uses a fault-tolerant cabling configuration, both controllers' LUNs are accessible through the partner. CAUTION: • Before changing the owning controller for a vdisk, you must stop host I/O to the vdisk's volumes. • Because a volume and its snap pool must be in vdisks owned by the same controller, if an ownership change will cause volumes and their snap pools to be owned by different controllers, the volumes will not be able to access their snap pools. Changing the owner of a vdisk does not affect the mappings volumes in that vdisk. To change a vdisk's owner 1. In the Configuration View panel, right-click a vdisk and select Configuration > Modify Vdisk Owner. The main panel shows the vdisk's owner. 2. Select a new owner. 3. Click Modify Owner. A confirmation dialog appears. HP P2000 G3 MSA System SMU Reference Guide 53

  • 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
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
HP P2000 G3 MSA System SMU Reference Guide
53
Configuring a vdisk
Managing dedicated spares
You can assign a maximum of four available disks to a redundant vdisk (RAID 1, 3, 5, 6, 10, 50) for use
as spares by that vdisk only. A spare must be the same type (SAS or SATA, small or large form-factor) as
other disks in the vdisk, and have sufficient capacity to replace the smallest disk in the vdisk.
If a disk in the vdisk fails, a dedicated spare is automatically used to reconstruct the vdisk. A redundant
vdisk other than RAID-6 becomes Critical when one disk fails. A RAID-6 vdisk becomes Degraded when
one disk fails and Critical when two disks fail. After the vdisk’s parity or mirror data is completely written
to the spare, the vdisk returns to fault-tolerant status. For RAID-50 vdisks, if more than one sub-vdisk
becomes critical, reconstruction and use of assigned spares occur in the order sub-vdisks are numbered.
To change a vdisk’s spares
1.
In the Configuration View panel, right-click a vdisk and select
Configuration > Manage Dedicated
Spares
. The main panel shows information about the selected vdisk, its spares, and all disks in the
system. Existing spares are labeled SPARE.
•
In the Disk Sets table, the number of white slots in the SPARE entry’s Disks field shows how many
spares you can add to the vdisk.
•
In the enclosure view or list, only existing spares and suitable available disks are selectable.
2.
Select spares to remove, disks to add as spares, or both.
3.
Click
Modify Spares
. If the task succeeds, the panel is updated to show which disks are now spares for
the vdisk.
Changing a vdisk’s name
To change a vdisk’s name
1.
In the Configuration View panel, right-click a vdisk and select
Configuration > Modify Vdisk Name
. The
main panel shows the vdisk’s name.
2.
Enter a new name. A vdisk name is case sensitive; cannot already exist in the system; cannot include a
comma, double quote, or backslash; and can have a maximum of 20 bytes.
3.
Click
Modify Name
. The new name appears in the Configuration View panel.
Changing a vdisk’s owner
Each vdisk is owned by one of the controllers, A or B, known as the
preferred owner
. Typically, you should
not need to change vdisk ownership.
When a controller fails, the partner controller assumes temporary ownership of the failed controller’s vdisks
and resources, becoming the
current owner
. If the system uses a fault-tolerant cabling configuration, both
controllers’ LUNs are accessible through the partner.
CAUTION:
•
Before changing the owning controller for a vdisk, you must stop host I/O to the vdisk’s volumes.
•
Because a volume and its snap pool must be in vdisks owned by the same controller, if an ownership
change will cause volumes and their snap pools to be owned by different controllers, the volumes will
not be able to access their snap pools.
Changing the owner of a vdisk does not affect the mappings volumes in that vdisk.
To change a vdisk’s owner
1.
In the Configuration View panel, right-click a vdisk and select
Configuration > Modify Vdisk Owner
.
The main panel shows the vdisk’s owner.
2.
Select a new owner.
3.
Click
Modify Owner
. A confirmation dialog appears.