Go to main content

Oracle® Solaris Cluster 4.3 System Administration Guide

Exit Print View

Updated: June 2017

Deployment Example: Configuring Host-Based Data Replication Between Clusters With Availability Suite Software

This appendix provides a method of using host-based replication without the use of Oracle Solaris Cluster Geographic Edition. Use Oracle Solaris Cluster Geographic Edition for host-based replication to simplify the configuration and operation of host-based replication between clusters. See Understanding Data Replication.

The example in this appendix shows how to configure host-based data replication between clusters that use the Availability Suite feature of Oracle Solaris software. The example illustrates a complete cluster configuration for an NFS application that provides detailed information about how individual tasks can be performed. All tasks should be performed in the global cluster. The example does not include all of the steps that are required by other applications or other cluster configurations.

If you use role-based access control (RBAC) to access the cluster nodes, ensure that you can assume a role that provides authorization for l Oracle Solaris Cluster commands. This series of data replication procedures requires the following Oracle Solaris Cluster authorizations:

  • solaris.cluster.modify

  • solaris.cluster.admin

  • solaris.cluster.read

See the Securing Users and Processes in Oracle Solaris 11.3 for more information about using roles. See the Oracle Solaris Cluster man pages for the authorization that each Oracle Solaris Cluster subcommand requires.

Understanding Availability Suite Software in a Cluster

This section introduces disaster tolerance and describes the data replication methods that Availability Suite software uses.

Disaster tolerance is the ability to restore an application on an alternate cluster when the primary cluster fails. Disaster tolerance is based on data replication and takeover. A takeover relocates an application service to a secondary cluster by bringing online one or more resource groups and device groups.

If data is replicated synchronously between the primary and secondary cluster, then no committed data is lost when the primary site fails. However, if data is replicated asynchronously, then some data may not have been replicated to the secondary cluster before the primary site failed, and thus is lost.