How to Configure the Sun StorEdge Availability Suite 3.2.1 Volume in Sun Cluster (Sun Cluster Geographic Edition System Administration Guide)

Sun Cluster Geographic Edition System Administration Guide

How to Configure the Sun StorEdge Availability Suite 3.2.1 Volume in Sun Cluster

This procedure provides an example of how to configure Sun StorEdge Availability Suite 3.2.1 volumes in Sun Cluster. These volumes can be Solaris Volume Manager volumes, VERITAS Volume Manager volumes, or raw device volumes.

The volumes are encapsulated at the Sun Cluster device-group level. The Sun StorEdge Availability Suite 3.2.1 software interacts with the Solaris Volume Manager disksets, or VERITAS Volume Manager disk group, or raw device through this device group interface. The path to the volumes depends on the volume type as described in the following table.

Volume Type	Path
Solaris Volume Manager	`/dev/md/diskset-name/rdsk/d#`, where `#` represents a number
VERITAS Volume Manager	`/dev/vx/rdsk/disk-group-name/volume-name`
Raw device	`/dev/did/rdsk/d#s#`

Steps

Create a diskset, avsset, by using Solaris Volume Manager or a disk group, avsdg, by using VERITAS Volume Manager or a raw device on cluster-paris and cluster-newyork.

For example, if you configure the volume by using a raw device, choose a raw device group, dsk/d3, on cluster-paris and cluster-newyork.

Create two volumes in the diskset or disk group on cluster-paris.

The Sun StorEdge Availability Suite software requires a dedicated bitmap volume for each data volume to track which modifications to the data volume when the system is in logging mode.

If you use a raw device to configure the volumes, create two partitions, /dev/did/rdsk/d3s3 and /dev/did/rdsk/d3s4, on the /dev/did/rdsk/d3 device on cluster-paris.

Create two volumes in the diskset or disk group on cluster-newyork.

If you use a raw device to configure the volumes, create two partitions, /dev/did/rdsk/d3s5 and /dev/did/rdsk/d3s6, on the /dev/did/rdsk/d3 device on cluster-paris.