Sun Cluster HA for Netscape Overview

The Sun Cluster HA for Netscape data services consist of a group of Netscape^(TM) applications that can be made highly available by running them in the Sun Cluster environment. Table 8-1 displays the data service application and its associated highly available data service.

Table 8-1 Sun Cluster HA for Netscape Data Services

Netscape Application	Highly Available Data Service Name	HA DS Package Name
Netscape News Server	Sun Cluster HA for Netscape News	SUNWscnew
Netscape Mail Server and Netscape Messaging Server	Sun Cluster HA for Netscape Mail	SUNWscnsm
Netscape HTTP/Web Server	Sun Cluster HA for Netscape HTTP	SUNWschtt
Netscape HTTP Secure	Sun Cluster HA for Netscape HTTP	SUNWschtt
Netscape LDAP Server	Sun Cluster HA for Netscape LDAP	SUNWscnsl

See the Sun Cluster 2.2 Release Notes for a list of the supported release levels for the data services.

The procedures described in this chapter assume that you are familiar with the Sun Cluster concepts of disksets, logical hosts, physical hosts, switchover, takeover, and data services. See Chapter 1, Understanding the Sun Cluster Environment for a description of these concepts.

You should install and test the Netscape application software (DNS, Netscape HTTP Server, Netscape News, Netscape Mail or Messaging Server, and Netscape LDAP) independently of Sun Cluster. Refer to the Netscape application software installation documentation for installation instructions.

Table 8-2 describes the high-level procedures to set up Netscape data service applications to run with Sun Cluster.

Table 8-2 High-Level Steps to Set Up Netscape Data Service Applications

Task	Go To ...
Installing the Solaris and Sun Cluster environments, installing the Netscape data service packages, and installing all required patches	Chapter 3, Installing and Configuring Sun Cluster Software
Starting the cluster with the scadmin(1M) command	Chapter 3, Installing and Configuring Sun Cluster Software, and the scadmin(1M) man page
(Optional) Installing and setting up DNS for the Netscape data services to use	Chapter 12, Installing and Configuring Sun Cluster HA for DNS
Installing and configuring Sun Cluster HA for Netscape data services	See the section on installing your particular data service, and "Configuring the Sun Cluster HA for Netscape Data Services"
Registering and starting the Sun Cluster HA for Netscape data services	"Configuring the Sun Cluster HA for Netscape Data Services"

---

Note -

If you are running multiple data services in your Sun Cluster configuration, you can set up the data services in any order, with one exception: if you use Sun Cluster HA for DNS, you must set it up before setting up Sun Cluster HA for NFS. DNS software is included in the Solaris environment. See Chapter 12, Installing and Configuring Sun Cluster HA for DNS, for details. If the cluster is to obtain the DNS service from another server, then configure the cluster to be a DNS client first.

---

---

Note -

After installation, do not manually start and stop the Netscape data services. Once started, they are controlled by Sun Cluster.

---

---

Note -

Before you install the Netscape application software, refer to the section in this chapter describing the configuration procedures for each Netscape application. These sections describe Sun Cluster-specific configuration information that you must supply when you install the Netscape applications.

---

Choosing an Install Location for Netscape Binaries

The Netscape binaries and data directories can be installed on either the shared disk or on the local disk of each cluster node.

Installing the binaries and data directories on the shared disk eases administration and consumes less disk space, but increases down time during application upgrades, because the application must be brought down for the duration of the binary upgrade.

Installing the data directories on the shared disk and the binaries locally on each node preserves high availability during failover, and also reduces downtime during future upgrades of the application. You can upgrade the binaries on a node that is not currently hosting the application, switch the application over to that node, then upgrade the binaries on the original node. The application remains available except for during the brief switchover period.