Go to main content

Oracle® Solaris Cluster Geographic Edition Data Replication Guide for Hitachi TrueCopy and Universal Replicator

Exit Print View

Updated: July 2016
 
 

Configuration Requirements and Guidelines

Observe the following requirements and guidelines:

  • If you are using storage-based replication, do not configure a replicated volume as a quorum device. The Geographic Edition framework does not support using a Hitachi TrueCopy or Universal Replicator S-VOL and Command Device as an Oracle Solaris Cluster quorum device. See Using Storage-Based Data Replication Within a Campus Cluster in Oracle Solaris Cluster 4.3 System Administration Guide for more information.

  • If you use the Hitachi TrueCopy and Universal Replicator Command Control Interface (CCI) for data replication, you must use RAID Manager. For information about which version you should use, see the Oracle Solaris Cluster 4.3 Geographic Edition Installation and Configuration Guide.

  • All Hitachi TrueCopy or Universal Replicator data replication components with the same consistency group ID (CTGID) must be added to the same protection group.

  • The Geographic Edition framework uses the default CCI instance to manage the Hitachi TrueCopy or Universal Replicator devices. The Geographic Edition framework starts the default CCI instance whenever a Hitachi TrueCopy data replication component is managed by the Geographic Edition framework. Applications that are not under the control of the Geographic Edition framework can also use the default CCI instance or any other instances without risk to Geographic Edition or application processes or data.

  • The Geographic Edition framework supports the hardware configurations that are supported by the Oracle Solaris Cluster software. See the Oracle Solaris Cluster Interoperability Matrix for Hitachi Data Systems Enterprise Storage (http://www.oracle.com/technetwork/server-storage/solaris-cluster/hds-enterprise-matrix-4x-1726954.pdf) for information about current supported Oracle Solaris Cluster configurations.

  • The Oracle Solaris Cluster device groups that are listed in the Cluster_dgs protection group property must exist and have the same device group name on both the primary cluster and the secondary cluster.