HP MSA 1040 HP MSA 1040 SMU Reference Guide (762784-001, March 2014) - Page 54

Deleting remote systems, Configuring a vdisk, Managing dedicated spares

Page 54 highlights

Deleting remote systems You can delete the management objects for remote systems. After establishing replication to a remote system, if you choose to delete the remote system you can safely do so without affecting replications. However, because the remote system's name and IP address will no longer appear in user interfaces, record this information before deleting the remote system so that you can access it at a later time, such as to delete old replication images or for disaster recovery. To delete remote systems 1. In the Configuration View panel, either: • Right-click the local system and select Configuration > Remote System > Delete Remote System. • Right-click a remote system and select Configuration > Delete Remote System. 2. In the main panel, select the remote systems to remove. To select or clear all remote systems, toggle the checkbox in the heading row. 3. Click Delete Remote System(s). A confirmation dialog appears. 4. Click Delete to continue; otherwise, click Cancel. If you clicked Delete, a processing dialog appears. If the task succeeds, the System Overview panel and a success dialog appear. 5. Click OK. As processing completes, the deleted items are removed from the Configuration View panel. Configuring a vdisk Managing dedicated spares You can assign a maximum of four available disks to a fault-tolerant vdisk (RAID 1, 3, 5, 6, 10, 50) for use as spares by that vdisk only. A spare must be the same type (enterprise SAS or midline SAS) as other disks in the vdisk, and have sufficient capacity to replace the smallest disk in the vdisk. NOTE: If you upgraded from an earlier release that did not distinguish between enterprise and midline SAS disks, you might have vdisks that contain both types of disks. For such a vdisk, whose RAID-level label has the suffix -MIXED in the Configuration View panel, you can designate either or both types of disks to be spares. If a disk in the vdisk fails, a dedicated spare is automatically used to reconstruct the vdisk. A fault-tolerant 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 Disks column of the SPARE row shows how many spares you can add to the vdisk. • In the Graphical or Tabular view, only existing spares and suitable available disks are selectable. 2. Select spares to remove, disks to add as spares, or both. To add a spare, select its checkbox. To remove a spare, clear its checkbox. 3. Click Modify Spares. If the task succeeds, the panel is updated to show which disks are now spares for the vdisk. 54 Configuring the system

  • 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
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190

54
Configuring the system
Deleting remote systems
You can delete the management objects for remote systems.
After establishing replication to a remote system, if you choose to delete the remote system you can safely do so
without affecting replications. However, because the remote system’s name and IP address will no longer appear in
user interfaces, record this information before deleting the remote system so that you can access it at a later time,
such as to delete old replication images or for disaster recovery.
To delete remote systems
1.
In the Configuration View panel, either:
Right-click the local system and select
Configuration > Remote System > Delete Remote System
.
Right-click a remote system and select
Configuration > Delete Remote System
.
2.
In the main panel, select the remote systems to remove. To select or clear all remote systems, toggle the checkbox
in the heading row.
3.
Click
Delete Remote System(s)
. A confirmation dialog appears.
4.
Click
Delete
to continue; otherwise, click
Cancel
. If you clicked
Delete
, a processing dialog appears. If the task
succeeds, the System Overview panel and a success dialog appear.
5.
Click
OK
. As processing completes, the deleted items are removed from the Configuration View panel.
Configuring a vdisk
Managing dedicated spares
You can assign a maximum of four available disks to a fault-tolerant vdisk (RAID 1, 3, 5, 6, 10, 50) for use as spares
by that vdisk only. A spare must be the same type (enterprise SAS or midline SAS) as other disks in the vdisk, and
have sufficient capacity to replace the smallest disk in the vdisk.
NOTE:
If you upgraded from an earlier release that did not distinguish between enterprise and midline SAS disks,
you might have vdisks that contain both types of disks. For such a vdisk, whose RAID-level label has the suffix
-MIXED
in the Configuration View panel, you can designate either or both types of disks to be spares.
If a disk in the vdisk fails, a dedicated spare is automatically used to reconstruct the vdisk. A fault-tolerant 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 Disks column of the SPARE row shows how many spares
you can add to the vdisk.
In the Graphical or Tabular view, only existing spares and suitable available disks are selectable.
2.
Select spares to remove, disks to add as spares, or both. To add a spare, select its checkbox. To remove a spare,
clear its checkbox.
3.
Click
Modify Spares
. If the task succeeds, the panel is updated to show which disks are now spares for the vdisk.