1. Introduction to Administering Oracle Solaris Cluster
2. Oracle Solaris Cluster and RBAC
3. Shutting Down and Booting a Cluster
4. Data Replication Approaches
5. Administering Global Devices, Disk-Path Monitoring, and Cluster File Systems
7. Administering Cluster Interconnects and Public Networks
10. Configuring Control of CPU Usage
11. Patching Oracle Solaris Cluster Software and Firmware
12. Backing Up and Restoring a Cluster
13. Administering Oracle Solaris Cluster With the Graphical User Interfaces
Configuring Host-Based Data Replication With Sun StorageTek Availability Suite Software
Understanding Sun StorageTek Availability Suite Software in a Cluster
Data Replication Methods Used by Sun StorageTek Availability Suite Software
Replication in the Example Configuration
Guidelines for Configuring Host-Based Data Replication Between Clusters
Configuring Replication Resource Groups
Configuring Application Resource Groups
Configuring Resource Groups for a Failover Application
Configuring Resource Groups for a Scalable Application
Guidelines for Managing a Failover
Task Map: Example of a Data Replication Configuration
Connecting and Installing the Clusters
Example of How to Configure Device Groups and Resource Groups
How to Configure a Device Group on the Primary Cluster
How to Configure a Device Group on the Secondary Cluster
How to Configure the File System on the Primary Cluster for the NFS Application
How to Configure the File System on the Secondary Cluster for the NFS Application
How to Create a Replication Resource Group on the Primary Cluster
How to Create a Replication Resource Group on the Secondary Cluster
How to Create an NFS Application Resource Group on the Primary Cluster
How to Create an NFS Application Resource Group on the Secondary Cluster
Example of How to Enable Data Replication
How to Enable Replication on the Primary Cluster
How to Enable Replication on the Secondary Cluster
Example of How to Perform Data Replication
How to Perform a Remote Mirror Replication
Before You Begin
Complete the procedure How to Perform a Point-in-Time Snapshot.
Use the following command for Sun StorageTek Availability Suite software:
nodeA# /usr/sbin/sndradm -P
The output should resemble the following:
/dev/vx/rdsk/devgrp/vol01 -> lhost-reprg-sec:/dev/vx/rdsk/devgrp/vol01 autosync: on, max q writes:4194304, max q fbas:16384, mode:sync,ctag: devgrp, state: replicating
In replicating mode, the state is replicating, and the active state of autosynchronization is on. When the primary volume is written to, the secondary volume is updated by Sun StorageTek Availability Suite software.
Use the following command for Sun StorageTek Availability Suite software:
nodeA# /usr/sbin/sndradm -n -u lhost-reprg-prim \ /dev/vx/rdsk/devgrp/vol01 \ /dev/vx/rdsk/devgrp/vol04 lhost-reprg-sec \ /dev/vx/rdsk/devgrp/vol01 \ /dev/vx/rdsk/devgrp/vol04 ip sync
client-machine# umount /dir
nodeA# clresource disable -n nodeA nfs-rs nodeA# clresource disable -n nodeA nfs-dg-rs nodeA# clresource disable -n nodeA lhost-nfsrg-prim nodeA# clresourcegroup online -n "" nfs-rg
Run the following command for Sun StorageTek Availability Suite software:
nodeA# /usr/sbin/sndradm -n -l lhost-reprg-prim \ /dev/vx/rdsk/devgrp/vol01 \ /dev/vx/rdsk/devgrp/vol04 lhost-reprg-sec \ /dev/vx/rdsk/devgrp/vol01 \ /dev/vx/rdsk/devgrp/vol04 ip sync
When the data volume on the disk is written to, the bitmap file on the same disk is updated. No replication occurs.
nodeC# mount | grep /global/etc
nodeC# clresourcegroup online -n nodeC nfs-rg
You see a prompt that resembles the following:
client-machine#
client-machine# mount -o rw lhost-nfsrg-sec:/global/mountpoint /dir
client-machine# ls /dir
nodeC# clresource disable -n nodeC nfs-rs nodeC# clresource disable -n nodeC nfs-dg-rs nodeC# clresource disable -n nodeC lhost-nfsrg-sec nodeC# clresourcegroup online -n "" nfs-rg
nodeC# umount /global/mountpoint
nodeA# clresourcegroup online -n nodeA nfs-rg
Run the following command for Sun StorageTek Availability Suite software:
nodeA# /usr/sbin/sndradm -n -u lhost-reprg-prim \ /dev/vx/rdsk/devgrp/vol01 \ /dev/vx/rdsk/devgrp/vol04 lhost-reprg-sec \ /dev/vx/rdsk/devgrp/vol01 \ /dev/vx/rdsk/devgrp/vol04 ip sync
When the primary volume is written to, the secondary volume is updated by Sun StorageTek Availability Suite software.
See Also
Example of How to Manage a Failover
This section describes how to provoke a failover and how the application is transferred to the secondary cluster. After a failover, update the DNS entries. For additional information, see Guidelines for Managing a Failover.
This section contains the following procedures: