To ensure data integrity, use multipathing and the proper RAID package. The following list includes considerations for implementing a campus cluster configuration that uses storage-based data replication.
Node-to-node distance is limited by the Sun Cluster Fibre Channel and interconnect infrastructure. Contact your Sun service provider for more information about current limitations and supported technologies.
Do not configure a replicated volume as a quorum device. Locate any quorum devices on an shared, unreplicated volume or use the quorum server.
Ensure that only the primary copy of the data is visible to cluster nodes. Otherwise, the volume manager might try to simultaneously access both primary and secondary copies of the data.
EMC Symmetrix Remote Data Facility and Hitachi TrueCopy allow the user to define groups of replicated devices. The replication device group and Sun Cluster global device group must be given the same name so that they may be moved between nodes as a single unit.
Refer to the documentation that was shipped with your storage array for information about controlling the visibility of your data copies.
Particular application-specific data might not be suitable for asynchronous data replication. Use your understanding of your application's behavior to determine how best to replicate application-specific data across the storage devices.
If configuring the cluster for automatic failover, use synchronous replication.
For instructions on configuring the cluster for automatic failover of replicated volumes, see Administering Storage-Based Replicated Devices.
Oracle Real Application Clusters (RAC) is not supported.
CVM and Solaris Volume Manager for Sun Cluster software are not supported.