This section describes what to do to prepare for administering your cluster.
As your Sun Cluster configuration grows and changes, you need to document the hardware aspects that are unique to your site. Labeling cables and connections between the various cluster components also saves administration time when it becomes necessary to change or upgrade the cluster.
Keeping such a record of your cluster configuration will also come in handy when servicing the cluster. If you use a third-party service provider, such record keeping will make a service provider's job easier.
If you choose, you can use a dedicated SPARC workstation, known as the administrative console, to administer the active cluster. Typically, you install and run the Cluster Control Panel (CCP) and Sun Management Center server and console software on the administrative console. For more information on the CCP, see "1.5.1 How to Remotely Log In to Sun Cluster". For instructions on installing the Sun Management Center software, see the Sun Cluster 3.0 Installation Guide.
The administrative console is not a cluster node. The administrative console is used for remote access to the cluster nodes, either over the public network or through a network-based terminal concentrator. If your cluster consists of a Sun EnterpriseTM 10000 server, you must have the ability to log in from the administrative console to the System Service Processor (SSP) and connect by using the netcon command.
Sun Cluster does not require a dedicated administrative console, but using one provides these benefits:
Enables centralized cluster management by grouping console and management tools on the same machine
Provides potentially quicker problem resolution by Enterprise Services or your service provider
While not specifically discussed in this guide, it is important to back up your cluster on a regular basis. Even though Sun Cluster provides an HA environment, with mirrored copies of data on the storage devices, do not consider this a replacement for regular backups. Sun Cluster can survive multiple failures, but not a catastrophic failure in which all data is rendered unavailable. Therefore, you must have a backup procedure in place to protect against catastrophic data loss. Backups are also important to undo user or program errors.
The following information should be included as part of your backup.
All file system partitions
All database data if you are running DBMS data services
Disk partition information for all cluster disks
The md.tab file if you are using Solstice DiskSuiteTM as your volume manager