Skip Navigation Links | |
Exit Print View | |
Oracle Solaris Cluster System Administration Guide Oracle Solaris Cluster 4.1 |
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
12. Backing Up and Restoring a Cluster
Configuring Host-Based Data Replication With Availability Suite Software
Understanding Availability Suite Software in a Cluster
Data Replication Methods Used by 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 Takeover
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 Secondary Cluster
Example of How to Perform Data Replication
How to Perform a Remote Mirror Replication
How to Perform a Point-in-Time Snapshot
How to Verify That Replication Is Configured Correctly
nodeA# lockfs -a -f
nodeA# clresourcegroup status nodeC# clresourcegroup status
Examine the state field of the resource group.
This step enables replication from the primary cluster to the secondary cluster. This step enables replication from the master volume (d200) on the primary cluster to the master volume (d200) on the secondary cluster. In addition, this step enables replication to the remote mirror bitmap on d203.
If the primary cluster and secondary cluster are unsynchronized, run this command for Availability Suite software:
nodeA# /usr/sbin/sndradm -n -e lhost-reprg-prim \ /dev/md/nfsset/rdsk/d200 \ /dev/md/nfsset/rdsk/d203 lhost-reprg-sec \ /dev/md/nfsset/rdsk/d200 \ /dev/md/nfsset/rdsk/d203 ip sync
If the primary cluster and secondary cluster are synchronized, run this command for Availability Suite software:
nodeA# /usr/sbin/sndradm -n -E lhost-reprg-prim \ /dev/md/nfsset/rdsk/d200 \ /dev/md/nfsset/rdsk/d203 lhost-reprg-sec \ /dev/md/nfsset/rdsk/d200 \ /dev/md/nfsset/rdsk/d203 ip sync
Run this command for Availability Suite software:
nodeA# /usr/sbin/sndradm -n -a on lhost-reprg-prim \ /dev/md/nfsset/rdsk/d200 \ /dev/md/nfsset/rdsk/d203 lhost-reprg-sec \ /dev/md/nfsset/rdsk/d200 \ /dev/md/nfsset/rdsk/d203 ip sync
This step enables autosynchronization. When the active state of autosynchronization is set to on, the volume sets are resynchronized if the system reboots or a failure occurs.
Use the following command for Availability Suite software:
nodeA# /usr/sbin/sndradm -P
The output should resemble the following:
/dev/md/nfsset/rdsk/d200 -> lhost-reprg-sec:/dev/md/nfsset/rdsk/d200 autosync: off, max q writes:4194304, max q fbas:16384, mode:sync,ctag: devgrp, state: logging
In logging mode, the state is logging, and the active state of autosynchronization is off. When the data volume on the disk is written to, the bitmap file on the same disk is updated.
Use the following command for Availability Suite software:
nodeA# /usr/sbin/iiadm -e ind \ /dev/md/nfsset/rdsk/d200 \ /dev/md/nfsset/rdsk/d201 \ /dev/md/nfsset/rdsk/d202 nodeA# /usr/sbin/iiadm -w \ /dev/md/nfsset/rdsk/d201
This step enables the master volume on the primary cluster to be copied to the shadow volume on the same cluster. The master volume, shadow volume, and point-in-time bitmap volume must be in the same device group. In this example, the master volume is d200, the shadow volume is d201, and the point-in-time bitmap volume is d203.
Use the following command for Availability Suite software:
nodeA# /usr/sbin/sndradm -I a \ /dev/md/nfsset/rdsk/d200 \ /dev/md/nfsset/rdsk/d201 \ /dev/md/nfsset/rdsk/d202
This step associates the point-in-time snapshot with the remote mirror volume set. Availability Suite software ensures that a point-in-time snapshot is taken before remote mirror replication can occur.
Next Steps