Skip Navigation Links | |
Exit Print View | |
Oracle Solaris Cluster Concepts Guide Oracle Solaris Cluster 4.1 |
2. Key Concepts for Hardware Service Providers
3. Key Concepts for System Administrators and Application Developers
Device IDs and DID Pseudo Driver
Cluster Configuration Repository (CCR)
Local and Global Namespaces Example
Using the cldevice Command to Monitor and Administer Disk Paths
Using the clnode set Command to Manage Disk Path Failure
Adhering to Quorum Device Requirements
Adhering to Quorum Device Best Practices
Recommended Quorum Configurations
Quorum in Two-Node Configurations
Quorum in Greater Than Two-Node Configurations
Characteristics of Scalable Services
Data Service API and Data Service Development Library API
Using the Cluster Interconnect for Data Service Traffic
Resources, Resource Groups, and Resource Types
Resource and Resource Group States and Settings
Resource and Resource Group Properties
Support for Oracle Solaris Zones
Support for Zones on Cluster Nodes Through Oracle Solaris Cluster HA for Solaris Zones
Criteria for Using Oracle Solaris Cluster HA for Solaris Zones
Requirements for Using Oracle Solaris Cluster HA for Solaris Zones
Additional Information About Oracle Solaris Cluster HA for Solaris Zones
Data Service Project Configuration
Determining Requirements for Project Configuration
Setting Per-Process Virtual Memory Limits
Two-Node Cluster With Two Applications
Two-Node Cluster With Three Applications
Failover of Resource Group Only
Public Network Adapters and IP Network Multipathing
SPARC: Dynamic Reconfiguration Support
SPARC: Dynamic Reconfiguration General Description
SPARC: DR Clustering Considerations for CPU Devices
SPARC: DR Clustering Considerations for Memory
SPARC: DR Clustering Considerations for Disk and Tape Drives
SPARC: DR Clustering Considerations for Quorum Devices
SPARC: DR Clustering Considerations for Cluster Interconnect Interfaces
SPARC: DR Clustering Considerations for Public Network Interfaces
Oracle Solaris zones provide a means of creating virtualized operating system environments within an instance of the Oracle Solaris OS. Oracle Solaris zones enable one or more applications to run in isolation from other activity on your system. The Oracle Solaris zones facility is described in Part II, Oracle Solaris Zones, in Oracle Solaris Administration: Oracle Solaris Zones, Oracle Solaris 10 Zones, and Resource Management. For information on zone clusters, see Zone Cluster Membership and Performing Zone Cluster Administrative Tasks in Oracle Solaris Cluster System Administration Guide,
The Oracle Solaris Cluster HA for Solaris Zones data service manages each zone as a resource that is controlled by the RGM.
Use the Oracle Solaris Cluster HA for Solaris Zones data service if any of following criteria is met:
You require delegated root access.
The application is not supported in a cluster.
You require affinities between resource groups that are to run in different zones on the same node.
If you plan to use the Oracle Solaris Cluster HA for Solaris Zones data service for an application, ensure that the following requirements are met:
The application is supported to run on non-global zones.
The application is integrated with the Oracle Solaris OS through a script, a run-level script, or a Solaris Service Management Facility (SMF) manifest.
The additional failover time that is required to boot a zone is acceptable.
Some downtime during maintenance is acceptable.
For information about how to use the Oracle Solaris Cluster HA for Solaris Zones data service, see Oracle Solaris Cluster Data Service for Oracle Solaris Zones Guide.