JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle Solaris Cluster Data Services Planning and Administration Guide     Oracle Solaris Cluster 4.1
search filter icon
search icon

Document Information

Preface

1.  Planning for Oracle Solaris Cluster Data Services

Configuration Guidelines for Oracle Solaris Cluster Data Services

Identifying Data Service Special Requirements

Determining the Location of the Application Binaries

Verifying the nsswitch.conf File Contents

Planning the Cluster File System Configuration

Enabling Oracle Solaris SMF Services to Run Under the Control of Oracle Solaris Cluster

Relationship Between Resource Groups and Device Groups

Understanding HAStoragePlus

Determining Whether Your Data Service Requires HAStoragePlus

Data Services With Nodes That Are Not Directly Connected to Storage

Data Services That Are Disk Intensive

Considerations for Installing and Configuring a Data Service

Overview of the Installation and Configuration Process

Installation and Configuration Task Flow

Example of Configuring a Failover Data Service

Tools for Data Service Resource Administration

clsetup Utility

Oracle Solaris Cluster Maintenance Commands

Summary by Task of Tools for Administering Data Service Resources

Standard Properties

Cluster Properties

Resource Type Properties

Resource Properties

Resource Group Properties

Resource Property Attributes

Node List Properties

Legal RGM Names

RGM Legal Names

Rules for Names Except Resource Type Names

Format of Resource Type Names

RGM Values

2.  Administering Data Service Resources

Index

Configuration Guidelines for Oracle Solaris Cluster Data Services

This section provides configuration guidelines for Oracle Solaris Cluster data services.

Identifying Data Service Special Requirements

Identify requirements for all of the data services before you begin Oracle Solaris and Oracle Solaris Cluster installation. Failure to do so might result in installation errors that require that you completely reinstall the Oracle Solaris and Oracle Solaris Cluster software.

For example, the Oracle Data Guard option of Oracle Solaris Cluster Support for Oracle Real Application Clusters has special requirements for the hostnames that you use in the cluster. HA for SAP also has special requirements. You must accommodate these requirements before you install Oracle Solaris Cluster software because you cannot change hostnames after you install Oracle Solaris Cluster software.


Note - Some Oracle Solaris Cluster data services are not supported for use in x86-based clusters. For more information, see the release notes for your release of Oracle Solaris Cluster at .


Determining the Location of the Application Binaries

You can install the application software and application configuration files on one of the following locations.

Verifying the nsswitch.conf File Contents

The nsswitch.conf file is the configuration file for name-service lookups. This file determines the following information:

Some data services require that you direct “group” lookups to “files” first. For these data services, change the “group” line in the nsswitch.conf file so that the “files” entry is listed first. See the documentation for the data service that you plan to configure to determine whether you need to change the “group” line. The scinstall utility automatically configures the nsswitch.conf file for you. If you manually modify the nsswitch.conf file, you must export the new nsswitch configuration information.

Planning the Cluster File System Configuration

Depending on the data service, you might need to configure the cluster file system to meet Oracle Solaris Cluster requirements. To determine whether any special considerations apply, see the documentation for the data service that you plan to configure.

For information about planning cluster file systems, see Planning Global Devices, Device Groups, and Cluster File Systems in Oracle Solaris Cluster Software Installation Guide.

The resource type HAStoragePlus enables you to use a highly available local file system in an Oracle Solaris Cluster environment that is configured for failover. For information about setting up the HAStoragePlus resource type, see Enabling Highly Available Local File Systems.

Enabling Oracle Solaris SMF Services to Run Under the Control of Oracle Solaris Cluster

The Service Management Facility (SMF) enables you to automatically start and restart SMF services during a node boot or service failure. This feature is similar to the Oracle Solaris Cluster Resource Group Manager (RGM), which facilitates high availability and scalability for cluster applications. SMF services and RGM features are complementary to each other.

Oracle Solaris Cluster includes three SMF proxy resource types that can be used to enable SMF services to run with Oracle Solaris Cluster in a failover, multi-master, or scalable configuration. The SMF proxy resource types enables you to encapsulate a set of interrelated SMF services into a single resource, SMF proxy resource to be managed by Oracle Solaris Cluster. In this feature, SMF manages the availability of SMF services on a single node. Oracle Solaris Cluster provides cluster-wide high availability and scalability of the SMF services.

For information about how to encapsulate these services, see Enabling Oracle Solaris SMF Services to Run With Oracle Solaris Cluster.

You might require Oracle Solaris Cluster to make highly available an application other than NFS or DNS that is integrated with the Solaris Service Management Facility (SMF). To ensure that Oracle Solaris Cluster can restart or fail over the application correctly after a failure, you must disable SMF service instances for the application as follows:


Note - If you do not disable the SMF service instances of the application, both the Solaris SMF and Oracle Solaris Cluster might attempt to control the startup and shutdown of the application. As a result, the behavior of the application might become unpredictable.


For more information, see the following documentation: