Choices for making Oracle Communications Calendar Server highly available include MySQL Async Replication and Oracle Data Guard. You can also configure the document store for high availability.
To provide high availability of Calendar front-end hosts, deploy the hosts behind a load balancer. The load balancer must use IP-based stickiness to distribute the load across the front-end hosts.
You can achieve a highly available, redundant MySQL back-end deployment by using asynchronous replication. You must configure the application server to use the replication driver, as explained in the MySQL Connector/J Developer Guide at:
http://dev.mysql.com/doc/connector-j/en/connector-j-reference-configuration-properties.html
See "Configuring a High-Availability Database" for instructions.
Note:
MySQL Cluster with Calendar Server does not work reliably under load. Additionally, MySQL Cluster's data recovery mechanism is not satisfactory with Calendar Server. For these reasons, use MySQL asynchronous replication to achieve a redundant, highly available Calendar Server deployment.For information on maximizing Oracle Database availability by using Oracle Data Guard and Advanced Replication, see the Oracle Database High Availability documentation at:
You can deploy a highly available document store. See "Configuring the Calendar Server Document Store" in Calendar Server Installation and Configuration Guide for details.