The best practices below will 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 Server a high priority because it is a single point of failure. When clustering the Siebel Database Server, have it already installed and running.
The Siebel Database Server 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.
All hardware used should be certified for server clustering by the hardware vendor.
The Siebel installer allows you to install all servers at once for which you have a license. If you will be operating the 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 the appendices of the Siebel Installation Guide for the operating system you are using), fill out the section related to server clustering, so that you can refer to this during installation.