Last updated on JUNE 12, 2017
Applies to:Sun Storage Availability Suite - Version 4.0 and later
Solaris Cluster - Version 3.2 12/06 to 3.3 [Release 3.2 to 3.3]
Information in this document applies to any platform.
How to Configure a Remote Mirror Network Data Replication Volume Set between Two Oracle Solaris Clusters
Availability Suite (AS) Introduction
Sun Storage Availability Suite (AS) incorporates two distinct modules :
StoreEdge Network Data Replication (SNDR) also known as Remote Mirror (RM) or Remote Data Copy (RDC)
Instant Image (II) also known as Point-in-Time Copy (PiTC)
StoreEdge Network Data Replication (SNDR) is used to replicate disks, disk slices and logical volumes across a network to a remote server.
Instant Image (II) is used to take local shadow copies (instant images/snapshots) of disks, disk slices and logical volumes.
A logical volume can be under the control of either Solaris Volume Manager (SVM) or Symantec's Veritas Volume Manager.
Outline of this StorEdge Network Data Replication (SNDR) Example: Copy an active filesystem from one cluster to another.
Taking an active mounted filesystem that resides on Cluster Boston
Master Volume MV Mount Point: /boston/MASTER_VOLUME SVM Volume: /dev/md/proddg/dsk/d1
and replicate the above filesystem to Cluster Newton using host based data replication (SNDR)
Remote Mirror RM Mount Point: /newton/REMOTE_MIRROR SVM Volume: /dev/md/proddgr/dsk/d1
Description of the underlying cluster configuration in this example.
Built upon Solaris 10, Oracle Solaris Cluster 3.3 with latest patches
Two Oracle Solaris Clusters each comprised of two nodes.
Cluster Boston First Node phys-boston-1 Second Node phys-boston-2
Cluster Newton First Node phys-newton-1 Second Node phys-newton-2
Replicating from Cluster Boston to Cluster Newton via a private network using Availability Suite Software Version 4.0 with latest patches
Cluster Boston Logical Host for replication: lh-boston-sndr-pri
Cluster Newton Logical Host for replication: lh-newton-sndr-sec
Solaris Volume Manager (SVM) volumes and filesystems built upon Shared Storage.
The Master Volume (MV) and its associated filesystem on the primary cluster is configured as a failover cluster resource group.
The secondary cluster volume remote mirror (RM) is configured as a failover resource; however, manual intervention is required to mount the RM filesystem on Cluster Newton.
Diagram showing an AS configuration including Cluster Nodes, Filesystems, Master and Remote Mirror Volumes and Shadow copies.
Note: The data path this document focuses on in the diagram is "A - Remote Mirror Replication MV -> RM"
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms