|Skip Navigation Links|
|Exit Print View|
|Oracle Solaris Cluster Geographic Edition Data Replication Guide for Oracle Solaris Availability Suite Oracle Solaris Cluster 4.0|
This section provides an overview of Availability Suite resource groups.
A device group that is controlled by the Availability Suite feature can be added to a protection group. The Geographic Edition software creates a lightweight resource group for each device group.
Note - Each device group controlled by the Availability Suite feature must exist on both partner clusters and must have the same name on both.
The name of a lightweight resource group has the following format:
For example, a device group named avsdg that is controlled by the Availability Suite feature has a lightweight resource group named avsdg-stor-rg.
The lightweight resource group collocates the logical host and the device group, a requirement of data replication with the Availability Suite remote mirror feature.
Each lightweight resource group contains two resources:
A logical hostname resource for the local logical host that is used for replication of the device group. One logical hostname resource is required for each cluster for each device group that will be replicated by Availability Suite. Thus if you have two clusters and three device groups that will be replicated, you will need six logical hostnames, three on the local area network of each cluster. The name of this resource has the following format:
An HAStoragePlus resource for controlling the location of the device group with the lightweight resource group. The name of this resource has the format AVSdevicegroupname-stor.
Note - Do not directly update a lightweight resource group or its resources or add them directly to a protection group. Doing so might lead to a failure in Geographic Edition operations.
For more information about lightweight resource groups, see the Availability Suite documentation on the Oracle Technology Network.
When a device group that is controlled by the Availability Suite feature is added to a protection group, the Geographic Edition software creates a special replication resource for that device group in the replication resource group. By monitoring these replication resource groups, the Geographic Edition software monitors the overall status of replication. One replication resource group with one replication resource is created for each protection group.
The name of the replication resource group has the following format:
The replication resource in the replication resource group monitors the replication status of the device group on the local cluster, which is reported by the Availability Suite remote mirror feature.
The name of a replication resource has the following format:
Note - Do not directly update a replication resource group or its resources or add them directly to a protection group. Doing so might lead to a failure in Geographic Edition operations.
During an outage, when a secondary replicated volume is unavailable, the Availability Suite feature logs changes made to the primary volume. Once replication is restarted the secondary volume is resynchronized with the primary volume.
A failure during the resynchronization might leave the secondary volume in an inconsistent state, which can result in file system corruption of that volume. To avoid this, you can configure the Geographic Edition software to automatically create a compact dependent shadow volume of a secondary replicated volume immediately prior to resynchronization. This is a “fallback snapshot” of the secondary volume, from which the secondary volume can be reconstructed in case there is a resynchronization failure.
If you decide to configure fallback snapshots of your replicated volumes, you will require two additional volumes on each cluster for each replicated volume, as described in Availability Suite Volume Sets. You can enable fallback snapshots automatically, as described in Automatically Enabling Fallback Snapshots, when you first add a device group to a protection group. You can also enable fallback snapshots manually at any time, as described in Manually Enabling Fallback Snapshots. It is much easier to enable fallback snapshots automatically, so if possible, set up fallback snapshots for the volumes in a device group when you first configure it and add it to a protection group.
Once a fallback snapshot is enabled, the Geographic Edition software automatically activates the snapshot when the cluster hosting an Availability Suite replicated volume is switched to secondary mode, and deactivates it when the cluster is switched to primary.