Siebel Deployment Planning Guide > Server Clustering Planning >
Best Practices for Server Clustering
The following best practices help promote failover protection for your deployment of Siebel Business Applications. However, these practices are neither exhaustive nor all-inclusive.
- If you have multiple Siebel Servers running that are not clustered, then load-balance these servers.
- Make clustering the Siebel database a high priority because it is a single point of failure. When clustering the Siebel database, have it already installed and running. Cluster the Siebel database server first.
- Install and configure clustering software on each node to detect failure of that node and to recover and manage all of the servers as a single system.
- Make sure all of the hardware used is certified for server clustering by the hardware vendor.
- The Siebel Enterprise Server installer allows you to install on a single computer all of the server modules for which you have a license. If you operate the Siebel Gateway Name Server and Siebel Servers as part of a cluster, then you must install and configure the Siebel Gateway Name Server and the Siebel Server individually as separate cluster services.
- On the copy that you made of the cluster deployment worksheet (which is located in an appendix of the Siebel Installation Guide for the operating system you are using), fill out the section related to server clustering, and refer to it during installation.
|