Recommendations for Server Clustering

The following recommendations help promote failover protection for your Siebel CRM deployment. 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.

• If you operate the Siebel Gateway and Siebel Servers as part of a cluster, then you must install and configure the Siebel Gateway and the Siebel Server individually as separate cluster services.

  Siebel CRM supports an optional native clustering feature for Siebel Gateway, to provide high availability benefits to Siebel CRM customers. This feature works at the software level and is the preferred and recommended approach for clustering the Siebel Gateway. For more information, see Defining High Availability Policies.

• On the copy that you made of the cluster deployment worksheet (which is located in Siebel Installation Guide), or your custom worksheet, fill out the section related to server clustering, and refer to it during installation.