An active-passive Essbase cluster can contain two Essbase servers. To install additional Essbase servers, you must install an additional instance of Essbase. The application must be on a shared drive, and the cluster name must be unique within the deployment environment.
These types of shared drive are supported:
SAN storage device with a shared disk file system supported on the installation platform such as OCFS
NAS device over a supported network protocol.
Note: | Any networked file system that can communicate with an NAS storage device is supported, but the cluster nodes must be able to access the same shared disk over that file system. |
SAN or a fast NAS device is recommended because of shorter I/O latency and failover times.
You set up active-passive Essbase clusters with EPM System Configurator. You specify the Essbase cluster information for each Essbase instance. You define the cluster when you configure the first instance of Essbase. When you configure the second instance, you associate the instance with the cluster.
Note: | For a given physical Essbase server that Administration Services is administering, Administration Services displays only the name of the cluster to which that Essbase server belongs. |
For instructions, see “Clustering Essbase Server” in Chapter 4, “Configuring EPM System Products,” of the Oracle Hyperion Enterprise Performance Management System Installation and Configuration Guide.