Enabling a Sun StorageTek Availability Suite Volume Set (Sun Cluster Geographic Edition Data Replication Guide for Sun StorageTek Availability Suite)

Sun Cluster Geographic Edition Data Replication Guide for Sun StorageTek Availability Suite

Previous: How to Configure a Sun StorageTek Availability Suite Volume in Sun Cluster
Next: How to Configure the Sun Cluster Device Group That Is Controlled by Sun StorageTek Availability Suite

Enabling a Sun StorageTek Availability Suite Volume Set

You can enable the Sun StorageTek Availability Suite volume sets in one of two ways:

Automatically, when the device group is added to the protection group, avspg

Use the automatic procedures to prepare the devicegroupname-volset.ini file when you are setting up Sun StorageTek Availability Suite software for the first time. After you have prepared the file, when you add the device group to the protection group, set the Enable_volume_set property of a device group to True. The Sun StorageTek Availability Suite software reads the information in the devicegroupname-volset.ini file to automatically enable the device group.
Manually, after the device group is added to the protection group, avspg

Use the manual procedures to enable the volume sets when you are creating volumes on a system that has been configured.

Automatically Enabling a Solaris Volume Manager Volume Set

In this example, the cluster-paris cluster is the primary and avsset is a device group that contains a Solaris Volume Manager disk set.

Example 1–1 Automatically Enabling a Solaris Volume Manager Volume Set

This example has the following entries in the /var/cluster/geo/avs/avsset-volset.ini file:

logicalhost-paris-1 /dev/md/avsset/rdsk/d100 /dev/md/avsset/rdsk/d101
logicalhost-newyork-1 /dev/md/avsset/rdsk/d100 /dev/md/avsset/rdsk/d101
ip async C avsset

The avsset-volset.ini file contains the following entries:

lh-paris-1 – Primary host
/dev/md/avsset/rdsk/d100 – Primary data
/dev/md/avsset/rdsk/d101 – Primary bitmap
lh-newyork-1 – Secondary host
/dev/md/avsset/rdsk/d100 – Secondary data
/dev/md/avsset/rdsk/d101 – Secondary bitmap
ip – Protocol
async – Mode
C – C tag
avsset – Disk set

The sample configuration file defines a volume set that replicates d100 from cluster-paris to d100 on cluster-newyork by using the bitmap volumes and logical hostnames that are specified in the file.

Automatically Enabling a VERITAS Volume Manager Volume Set

In this example, the cluster-paris cluster is the primary and avsdg is a device group that contains a VERITAS Volume Manager disk group.

Example 1–2 Automatically Enabling a VERITAS Volume Manager Volume Set

This example has the following entries in the /var/cluster/geo/avs/avsdg-volset.ini file:

logicalhost-paris-1 /dev/vx/rdsk/avsdg/vol-data-paris /dev/vx/rdsk/avsdg/vol-bitmap-paris 
logicalhost-newyork-1 /dev/vx/rdsk/avsdg/vol-data-newyork /dev/vx/rdsk/avsdg/vol-bitmap-ny 
ip async C avsdg

The avsdg-volset.ini file contains the following entries:

lh-paris-1 – Primary host
/dev/vx/rdsk/avsdg/vol-data-paris – Primary data
/dev/vx/rdsk/avsdg/vol-bitmap-paris – Primary bitmap
lh-newyork-1 is the secondary host.
/dev/vx/rdsk/avsdg/vol-data-newyork – Secondary data
/dev/vx/rdsk/avsdg/vol-bitmap-ny – Secondary bitmap
ip – Protocol
async – Mode
C – C flag
avsdg – Device group

The sample configuration file defines a volume set that replicates vol-data-paris from cluster-paris to vol-data-newyork on cluster-newyork. The volume set uses the bitmap volumes and logical hostnames that are specified in the file.

Automatically Enabling a Raw Device Volume Set

In this example, the cluster-paris cluster is the primary and rawdg is the name of the device group that contains a raw device disk group, /dev/did/rdsk/d3.

Example 1–3 Automatically Enabling a Raw Device Volume Set

This example has the following entries in /var/cluster/geo/avs/avsdg-volset.ini file:

logicalhost-paris-1 /dev/did/rdsk/d3s3 /dev/did/rdsk/d3s4 
logicalhost-newyork-1 /dev/did/rdsk/d3s5 /dev/did/rdsk/d3s6 
ip async C rawdg

The rawdg-volset.ini file contains the following entries:

logicalhost-paris-1 – Primary host
/dev/did/rdsk/d3s3 – Primary data
/dev/did/rdsk/d3s4 – Primary bitmap
logicalhost-newyork-1 – Secondary host
/dev/did/rdsk/d3s5 – Secondary data
/dev/did/rdsk/d3s6 – Secondary bitmap
ip – Protocol
async – Mode
C – C flag
rawdg – Device group

The sample configuration file defines a volume set that replicates d3s3 from cluster-paris to d3s5 on cluster-newyork. The volume set uses the bitmap volumes and logical hostnames that are specified in the file.

Manually Enabling Volume Sets

After you have added the device group to the protection group, avspg, you can manually enable the Sun StorageTek Availability Suite volume sets. Because the Sun Availability Suite commands are installed in different locations in the supported software versions, the following examples illustrate how to enable volume sets for each software version.

Example 1–4 Manually Enabling a Sun StorageTek Availability Suite 4.0 Volume Set

This example manually enables a Solaris Volume Manager volume set when using Sun StorageTek Availability Suite 4.0.

phys-paris-1# /usr/sbin/sndradm -e logicalhost-paris-1 \
/dev/md/avsset/rdsk/d100 /dev/md/avsset/rdsk/d101 \
logicalhost-newyork-1 /dev/md/avsset/rdsk/d100 \
/dev/md/avsset/rdsk/d101 ip async C avsset

Example 1–5 Manually Enabling a Sun StorEdge Availability Suite 3.2.1 Volume Set

This example manually enables a Solaris Volume Manager volume set when using Sun StorEdge Availability Suite 3.2.1.

phys-paris-1# /usr/opt/SUNWesm/sbin/sndradm -e logicalhost-paris-1 \
/dev/md/avsset/rdsk/d100 /dev/md/avsset/rdsk/d101 \
logicalhost-newyork-1 /dev/md/avsset/rdsk/d100 \
/dev/md/avsset/rdsk/d101 ip async C avsset

Example 1–6 Manually Enabling a VERITAS Volume Manager Volume Set

This example manually enables a VERITAS Volume Manager volume set when using Sun StorageTek Availability Suite 4.0.

phys-paris-1# /usr/sbin/sndradm -e logicalhost-paris-1 \
/dev/vx/rdsk/avsdg/vol-data-paris /dev/vx/rdsk/avsdg/vol-bitmap-paris \
logicalhost-newyork-1 /dev/vx/rdsk/avsdg/vol-data-newyork \
/dev/vx/rdsk/avsdg/vol-bitmap-newyork ip async C avsdg

This example manually enables a VERITAS Volume Manager volume set when using Sun StorEdge Availability Suite 3.2.1.

phys-paris-1# /usr/opt/SUNWesm/sbin/sndradm -e logicalhost-paris-1 \
/dev/vx/rdsk/avsdg/vol-data-paris /dev/vx/rdsk/avsdg/vol-bitmap-paris \
logicalhost-newyork-1 /dev/vx/rdsk/avsdg/vol-data-newyork \
/dev/vx/rdsk/avsdg/vol-bitmap-newyork ip async C avsdg

Example 1–7 Manually Enabling a Raw Device Volume Set

This example manually enables a raw device volume set when using Sun StorageTek Availability Suite 4.0.

phys-paris-1# /usr/sbin/sndradm -e logicalhost-paris-1 \
/dev/did/rdsk/d3s3 /dev/did/rdsk/d3s4 logicalhost-newyork-1 /dev/did/rdsk/d3s5 \
/dev/did/rdsk/d3s6 ip async C dsk/d3

This example manually enables a raw device volume set when using Sun StorEdge Availability Suite 3.2.1.

phys-paris-1# /usr/opt/SUNWesm/sbin/sndradm -e logicalhost-paris-1 \
/dev/did/rdsk/d3s3 /dev/did/rdsk/d3s4 logicalhost-newyork-1 /dev/did/rdsk/d3s5 \
/dev/did/rdsk/d3s6 ip async C dsk/d3

Information about the sndradm command execution is written to the Sun StorageTek Availability Suite log file at the following locations:

When using Sun StorageTek Availability Suite 4.0, /var/adm/ds.log
When using Sun StorEdge Availability Suite 3.2.1, /var/opt/SUNWesm/ds.log

Refer to this file if errors occur while manually enabling the volume set.