HP ProLiant 4500 Compaq ProLiant Cluster HA/F100 and HA/F200 Administrator Gui - Page 37

Active/Standby Configuration

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

Page 37 highlights

2-6 Compaq ProLiant Clusters HA/F100 and HA/F200 Administrator Guide If the node running the order entry database encounters a failure, the database fails over to its secondary node. The order entry clients experience a slight disruption of service while the database resources are failed over, the database transaction log is rolled back, and the information in the database is validated. When the database validation is complete, the order entry application is brought online on the file and print server and the clients can reconnect to it. While the database validation is occurring, file and print activities continue without disruption. If the file and print server encounters a failure, those services are not failed over to the order entry server. File and print services are offline until the problem is resolved and the node is brought back online. Active/Standby Configuration The primary difference between an active/active configuration and an active/standby configuration is the number of servers actively processing data. In active/standby, only one server is processing data (active) while the other (the standby server) is in an idle state. The standby server must be logged in to the Windows NT domain and MSCS must be up and running. However, no applications are running. The standby server's only purpose is to take over failed clustered applications from its partner. The standby server is not a preferred node for any clustered applications and, therefore, does not fail-over any applications to its partner server. Because the standby server does not process data until it accepts failed over applications, the limited use of the server may not justify the cost of the server. However, the cost of standby servers is justified when performance and availability are paramount to a business' operations. The standby server should be designed to run all of the clustered applications with little or no performance degradation. Since the standby server is not running any applications while the cluster is in a normal operating state, a failed-over clustered application will likely execute with the same speed and response time as if it were executing on the primary server.

  • 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
2-6
Compaq ProLiant Clusters HA/F100 and HA/F200 Administrator Guide
If the node running the order entry database encounters a failure, the database
fails over to its secondary node. The order entry clients experience a slight
disruption of service while the database resources are failed over, the database
transaction log is rolled back, and the information in the database is validated.
When the database validation is complete, the order entry application is
brought online on the file and print server and the clients can reconnect to it.
While the database validation is occurring, file and print activities continue
without disruption.
If the file and print server encounters a failure, those services are not failed
over to the order entry server. File and print services are offline until the
problem is resolved and the node is brought back online.
Active/Standby Configuration
The primary difference between an active/active configuration and an
active/standby configuration is the number of servers actively processing data.
In active/standby, only one server is processing data (active) while the other
(the standby server) is in an idle state.
The standby server must be logged in to the Windows NT domain and MSCS
must be up and running. However, no applications are running. The standby
server’s only purpose is to take over failed clustered applications from its
partner. The standby server is not a preferred node for any clustered
applications and, therefore, does not fail-over any applications to its partner
server.
Because the standby server does not process data until it accepts failed over
applications, the limited use of the server may not justify the cost of the server.
However, the cost of standby servers is justified when performance and
availability are paramount to a business’ operations.
The standby server should be designed to run all of the clustered applications
with little or no performance degradation. Since the standby server is not
running any applications while the cluster is in a normal operating state, a
failed-over clustered application will likely execute with the same speed and
response time as if it were executing on the primary server.