HP ProLiant 2500 Compaq ProLiant Cluster HA/F100 and HA/F200 Administrator Gui - Page 34

Designing the Compaq ProLiant Clusters HA/F100 and HA/F200

Page 34 highlights

Designing the Compaq ProLiant Clusters HA/F100 and HA/F200 2-3 An active/active configuration has two primary designs: s The first design uses Microsoft Cluster Server (MSCS) failover capabilities on both nodes, enabling Node1 to fail over clustered applications to Node2 and enabling Node2 to fail over clustered applications to Node1. This design optimizes availability since both nodes can fail over applications to each other. s The second design is a one-way failover. For example, MSCS may be set up to allow Node1 to fail over clustered applications to Node2, but not to allow Node2 to fail over clustered applications to Node1. While this design increases availability, it does not maximize availability since failover is configured on only one node. When designing cluster nodes to fail over to each other, ensure that each server has enough capacity, memory, and processor power to run all applications (all applications running on the first node plus all clustered applications running on the other node). When designing your cluster so that only one node (Node1) fails over to the other (Node2), ensure that Node2 has enough capacity, memory, and CPU power to execute not only its own applications, but to run the clustered applications that can fail over from Node1. Another consideration when determining your servers' hardware is understanding your clustered applications' required level of performance when the cluster is in a degraded state (when one or more clustered applications is running on a secondary node). If Node2 is running near peak performance when the cluster is in a normal operating state, and if several clustered applications are failed over from Node1, Node2 will likely execute the clustered applications more slowly than when they were executed on Node1. Some level of performance degradation may be acceptable. Determining how much degradation is acceptable depends on the company.

  • 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

Designing the Compaq ProLiant Clusters HA/F100 and HA/F200
2-3
An active/active configuration has two primary designs:
The first design uses Microsoft Cluster Server (MSCS) failover
capabilities on both nodes, enabling Node1 to fail over clustered
applications to Node2 and enabling Node2 to fail over clustered
applications to Node1. This design optimizes availability since both
nodes can fail over applications to each other.
The second design is a one-way failover. For example, MSCS may be
set up to allow Node1 to fail over clustered applications to Node2, but
not to allow Node2 to fail over clustered applications to Node1. While
this design increases availability, it does not maximize availability since
failover is configured on only one node.
When designing cluster nodes to fail over to each other, ensure that each
server has enough capacity, memory, and processor power to run all
applications (all applications running on the first node plus all clustered
applications running on the other node).
When designing your cluster so that only one node (Node1) fails over to the
other (Node2), ensure that Node2 has enough capacity, memory, and CPU
power to execute not only its own applications, but to run the clustered
applications that can fail over from Node1.
Another consideration when determining your servers’ hardware is
understanding your clustered applications’ required level of performance when
the cluster is in a
degraded state
(when one or more clustered applications is
running on a secondary node). If Node2 is running near peak performance
when the cluster is in a normal operating state, and if several clustered
applications are failed over from Node1, Node2 will likely execute the
clustered applications more slowly than when they were executed on Node1.
Some level of performance degradation may be acceptable. Determining how
much degradation is acceptable depends on the company.