HP StorageWorks 4000s NAS 4000s and 9000s Administration Guide - Page 199

Virtual Servers, Failover, Quorum Disk, original state

Page 199 highlights

Cluster Administration Virtual Servers A virtual server is a cluster group that consists of a static IP Address resource and a Network Name resource. Several virtual servers can be created. By assigning ownership of the virtual servers to the different server nodes, the processing load on the NAS devices can be distributed between the nodes of a cluster. The creation of a virtual server allows resources dependant on the virtual server to fail over and fail back between the cluster nodes. File Share and physical disks resources are assigned to the virtual server to ensure non disruptive service of file shares to the clients. Failover Failover of cluster groups and resources happens: ■ when a node hosting the group becomes inactive. A shutdown of cluster service or a loss of power can cause a failover. ■ when all of the resources within the group are dependent on one resource and that resource fails. ■ when an administrator forces a failover. A resource and all of its dependencies must be located in the same group so that if a resource fails over, all of its dependent resources fail over. When a resource is failed over, the cluster service performs certain procedures. First, all of the resources are taken offline in an order defined by the resource dependencies. Secondly, the cluster service attempts to transfer the group to the next node on the preferred owners list. If the transfer is successful, the resources are brought online in accordance with the resource dependency structure. The system failover policy defines how the cluster detects and responds to the failure of individual resources in the group. After a failover occurs and the cluster is brought back to its original state, failback can occur automatically based on the policy. After a previously failed node comes online, the cluster service can fail back the groups to the original host. The failback policy must be set before the failover occurs so that failback works as intended. Quorum Disk Each cluster must have a shared disk called the Quorum disk. This physical disk in the common cluster disk array plays a critical role in cluster operations. The Quorum disk offers a means of persistent storage. The disk must provide physical storage that can be accessed by any node in the cluster. If a node has control of the quorum resource upon startup, it can initiate the cluster. In addition, if the node can communicate with the node that owns the quorum resource, it can join or remain in the cluster. The Quorum disk maintains data integrity by: ■ storing the most current version of the cluster database. ■ guaranteeing that only one set of active communicating nodes is allowed to operate as a cluster. NAS 4000s and 9000s Administration Guide 199

  • 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
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246

Cluster Administration
199
NAS 4000s and 9000s Administration Guide
Virtual Servers
A virtual server is a cluster group that consists of a static IP Address resource and a Network
Name resource. Several virtual servers can be created. By assigning ownership of the virtual
servers to the different server nodes, the processing load on the NAS devices can be distributed
between the nodes of a cluster.
The creation of a virtual server allows resources dependant on the virtual server to fail over
and fail back between the cluster nodes. File Share and physical disks resources are assigned
to the virtual server to ensure non disruptive service of file shares to the clients.
Failover
Failover of cluster groups and resources happens:
when a node hosting the group becomes inactive. A shutdown of cluster service or a loss
of power can cause a failover.
when all of the resources within the group are dependent on one resource and that resource
fails.
when an administrator forces a failover.
A resource and all of its dependencies must be located in the same group so that if a resource
fails over, all of its dependent resources fail over.
When a resource is failed over, the cluster service performs certain procedures. First, all of the
resources are taken offline in an order defined by the resource dependencies. Secondly, the
cluster service attempts to transfer the group to the next node on the preferred owners list. If
the transfer is successful, the resources are brought online in accordance with the resource
dependency structure.
The system failover policy defines how the cluster detects and responds to the failure of
individual resources in the group. After a failover occurs and the cluster is brought back to its
original state, failback can occur automatically based on the policy. After a previously failed
node comes online, the cluster service can fail back the groups to the original host. The
failback policy must be set before the failover occurs so that failback works as intended.
Quorum Disk
Each cluster must have a shared disk called the Quorum disk. This physical disk in the
common cluster disk array plays a critical role in cluster operations. The Quorum disk offers a
means of persistent storage. The disk must provide physical storage that can be accessed by
any node in the cluster. If a node has control of the quorum resource upon startup, it can
initiate the cluster. In addition, if the node can communicate with the node that owns the
quorum resource, it can join or remain in the cluster.
The Quorum disk maintains data integrity by:
storing the most current version of the cluster database.
guaranteeing that only one set of active communicating nodes is allowed to operate as a
cluster.