HP ProLiant 3000 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
View all HP ProLiant 3000 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)