JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle Solaris Cluster Software Installation Guide     Oracle Solaris Cluster 4.1
search filter icon
search icon

Document Information

Preface

1.  Planning the Oracle Solaris Cluster Configuration

Finding Oracle Solaris Cluster Installation Tasks

Planning the Oracle Solaris OS

Guidelines for Selecting Your Oracle Solaris Installation Method

Oracle Solaris OS Feature Restrictions

System Disk Partitions

SPARC: Guidelines for Oracle VM Server for SPARC in a Cluster

Planning the Oracle Solaris Cluster Environment

Licensing

Software Updates

Public-Network IP Addresses

Console-Access Devices

Public Network Configuration

Quorum Server Configuration

NFS Guidelines

Service Restrictions

Network Time Protocol (NTP)

Oracle Solaris Cluster Configurable Components

Global-Cluster Name

Global-Cluster Node Names and Node IDs

Private Network Configuration

Private Hostnames

Cluster Interconnect

Transport Adapters

Transport Switches

Global Fencing

Quorum Devices

Zone Clusters

Global-Cluster Requirements and Guidelines

Zone-Cluster Requirements and Guidelines

Guidelines for Trusted Extensions in a Zone Cluster

Planning Global Devices, Device Groups, and Cluster File Systems

Planning Global Devices

Planning Device Groups

Planning Cluster File Systems

Choosing Mount Options for UFS Cluster File Systems

Mount Information for Cluster File Systems

Planning Volume Management

Guidelines for Volume Manager Software

Guidelines for Solaris Volume Manager Software

UFS Cluster File System Logging

Mirroring Guidelines

Guidelines for Mirroring Multihost Disks

Guidelines for Mirroring the ZFS Root Pool

2.  Installing Software on Global-Cluster Nodes

3.  Establishing the Global Cluster

4.  Configuring Solaris Volume Manager Software

5.  Creating a Cluster File System

6.  Creating Zone Clusters

7.  Uninstalling Software From the Cluster

Index

Planning Global Devices, Device Groups, and Cluster File Systems

This section provides the following information:

Planning Global Devices

For information about the purpose and function of global devices, see Global Devices in Oracle Solaris Cluster Concepts Guide.

Oracle Solaris Cluster software does not require any specific disk layout or file system size. Consider the following points when you plan your layout for global devices:

Planning Device Groups

For information about the purpose and function of device groups, see Device Groups in Oracle Solaris Cluster Concepts Guide.

Consider the following points when you plan device groups:

Planning Cluster File Systems

For information about the purpose and function of cluster file systems, see Cluster File Systems in Oracle Solaris Cluster Concepts Guide.


Note - You can alternatively configure highly available local file systems. This can provide better performance to support a data service with high I/O, or to permit use of certain file system features that are not supported in a cluster file system. For more information, see Enabling Highly Available Local File Systems in Oracle Solaris Cluster Data Services Planning and Administration Guide.


Consider the following points when you plan cluster file systems:

Choosing Mount Options for UFS Cluster File Systems

This section describes requirements and restrictions for mount options of UFS cluster file systems:


Note - You can alternatively configure this and other types of file systems as highly available local file systems. For more information, see Enabling Highly Available Local File Systems in Oracle Solaris Cluster Data Services Planning and Administration Guide.


Follow the guidelines in the following list of mount options to determine what mount options to use when you create your UFS cluster file systems.

global

Required. This option makes the file system globally visible to all nodes in the cluster.

logging

Required. This option enables logging.

forcedirectio

Conditional. This option is required only for cluster file systems that will host Oracle RAC RDBMS data files, log files, and control files.

onerror=panic

Required. You do not have to explicitly specify the onerror=panic mount option in the /etc/vfstab file. This mount option is already the default value if no other onerror mount option is specified.


Note - Only the onerror=panic mount option is supported by Oracle Solaris Cluster software. Do not use the onerror=umount or onerror=lock mount options. These mount options are not supported on cluster file systems for the following reasons:

  • Use of the onerror=umount or onerror=lock mount option might cause the cluster file system to lock or become inaccessible. This condition might occur if the cluster file system experiences file corruption.

  • The onerror=umount or onerror=lock mount option might cause the cluster file system to become unmountable. This condition might thereby cause applications that use the cluster file system to hang or prevent the applications from being killed.

A node might require rebooting to recover from these states.


syncdir

Optional. If you specify syncdir, you are guaranteed POSIX-compliant file system behavior for the write() system call. If a write() succeeds, then this mount option ensures that sufficient space is on the disk.

If you do not specify syncdir, the same behavior occurs that is seen with UFS file systems. When you do not specify syncdir, performance of writes that allocate disk blocks, such as when appending data to a file, can significantly improve. However, in some cases, without syncdir you would not discover an out-of-space condition (ENOSPC) until you close a file.

You see ENOSPC on close only during a very short time after a failover. With syncdir, as with POSIX behavior, the out-of-space condition would be discovered before the close.

See the mount_ufs(1M) man page for more information about UFS mount options.

Mount Information for Cluster File Systems

Consider the following points when you plan mount points for cluster file systems: