Siebel Deployment Planning Guide > Server Clustering Planning >

Best Practices for Server Clustering

The best practices below help promote failover protection for your system. However, these practices are neither exhaustive nor all-inclusive.

• If you have multiple Siebel Servers running that are not clustered, these should be load-balanced.
• 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. The Siebel Database should be the first server to be clustered.
• Install and configure clustering software on each node to detect failure of that node and to recover and manage all servers as a single system.
• Make sure all hardware used is certified for server clustering by the hardware vendor.
• The Siebel Enterprise Server installer allows you to install on a single machine all server modules for which you have a license. If you will be operating the Siebel Gateway Name Server and Siebel Servers as part of a cluster, you must install and configure the Siebel Gateway Name Server and the Siebel Server individually as separate cluster services.
• On the copy you made of the cluster deployment worksheet (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.