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

Example 2, Database/Database, File & Print/Database, File and Print, Services, Order Entry

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

Page 36 highlights

Designing the Compaq ProLiant Clusters HA/F100 and HA/F200 2-5 Example 2: Database/Database Another scenario has two distinct database applications running on two separate cluster nodes. One database application maintains Human Resources records, and its primary node is set to the HR database node. The other database application is used for market research, and its primary node is set to the Marketing database node. While in a normal state, both cluster nodes run at expected performance levels. If the Marketing server encounters a failure, the market research application and associated data resources fail over to their secondary node, the HR database server. The Marketing 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 market research application is brought online on the HR database node and the Marketing clients can reconnect to it. While the Marketing database validation is occurring, the HR clients do not experience any disruption of service. Example 3: File & Print/Database In this example, a business uses a single server to run its order entry department. The same department has a file and print server. While order entry is business-critical and requires maximum availability, the file and print server can be unavailable for several hours without impacting revenue. In this scenario, the order entry database is configured to use the file and print server as its secondary node. However, the file and print server will not be configured to fail over applications to the order entry server. Order Entry Database Shared Storage File and Print Services Capacity of Order Entry Database Node1 (Order Entry) Figure 2-2. Active/active example 3 Node2 (File and Print)

  • 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-5
Example 2:
Database/Database
Another scenario has two distinct database applications running on two
separate cluster nodes. One database application maintains Human Resources
records, and its primary node is set to the HR database node. The other
database application is used for market research, and its primary node is set to
the Marketing database node.
While in a normal state, both cluster nodes run at expected performance levels.
If the Marketing server encounters a failure, the market research application
and associated data resources fail over to their secondary node, the HR
database server. The Marketing 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 market research application is brought
online on the HR database node and the Marketing clients can reconnect to it.
While the Marketing database validation is occurring, the HR clients do not
experience any disruption of service.
Example 3:
File & Print/Database
In this example, a business uses a single server to run its order entry
department. The same department has a file and print server. While order entry
is business-critical and requires maximum availability, the file and print server
can be unavailable for several hours without impacting revenue. In this
scenario, the order entry database is configured to use the file and print server
as its secondary node. However, the file and print server will not be configured
to fail over applications to the order entry server.
File and Print
Services
Order Entry
Database
Capacity of
Order Entry
Database
Node1
Node2
Shared Storage
(Order Entry)
(File and Print)
Figure 2-2.
Active/active example 3