What is the recommended approach for providing a failover mechanism for Essbase Server in Release 11
There are two approaches that have led to successful implementations:
The first approach is based on VM failover. This approach can be effective as long as the VM infrastructure is in place and can support complete failover, and the file system storage is an enterprise-grade Storage Area Network.
The second approach is to configure an active-passive node for Essbase Server.
On Linux/Unix systems, we recommend using OPMN-based failover with a shared file system. For best performance, Oracle recommends a symmetric enterprise-grade solution using a Storage Area Network. The shared storage should be accessible for read and write on both active and passive systems during the normal operations of the server. This process is documented in the
The first approach is based on VM failover. This approach can be effective as long as the VM infrastructure is in place and can support complete failover, and the file system storage is an enterprise-grade Storage Area Network.
The second approach is to configure an active-passive node for Essbase Server.
On Linux/Unix systems, we recommend using OPMN-based failover with a shared file system. For best performance, Oracle recommends a symmetric enterprise-grade solution using a Storage Area Network. The shared storage should be accessible for read and write on both active and passive systems during the normal operations of the server. This process is documented in the
0