The Sun StorEdge Availability Suite 3.2.1 volume sets can be enabled in two ways:
Automatically, when the device group is added to the protection group, avspg
Use the automatic procedures to prepare the device-group-name-volset.ini file when you are setting up Sun StorEdge Availability Suite 3.2.1 software for the first time. After you have prepared the file, when you add the device group to the protection group, set the device group's Enable_volume_set property to True. The information in the device-group-name-volset.ini file will be read by the Sun StorEdge Availability Suite command 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 already been configured.
In this example, the cluster-paris cluster is the primary and avsset is a device group that contains a Solaris Volume Manager diskset.
This example has the following entries in /var/cluster/geo/avs/avsset-volset.ini:
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 g - C avsset |
The avsset-volset.ini file contains the following entries:
lh-paris-1 is the primary host.
/dev/md/avsset/rdsk/d100 is the primary data.
/dev/md/avsset/rdsk/d101 is the primary bitmap.
lh-newyork-1 is the secondary host.
/dev/md/avsset/rdsk/d100 is the secondary data.
/dev/md/avsset/rdsk/d101 is the secondary bitmap.
ip is the protocol.
async is the mode.
g is the G flag.
- is the IO group.
C is the C tag.
avsset is the diskset.
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.
In this example, the cluster-paris cluster is the primary and avsdg is a device group that contains a VERITAS Volume Manager disk group.
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 g - C avsdg |
The avsdg-volset.ini file contains the following entries:
lh-paris-1 is the primary host.
/dev/vx/rdsk/avsdg/vol-data-paris is the primary data.
/dev/vx/rdsk/avsdg/vol-bitmap-paris is the primary bitmap.
lh-newyork-1 is the secondary host.
/dev/vx/rdsk/avsdg/vol-data-newyork is the secondary data.
/dev/vx/rdsk/avsdg/vol-bitmap-ny is the secondary bitmap.
ip is the protocol.
async is the mode.
g is the G flag.
- is the IO group.
C is the C flag.
avsdg is the 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.
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.
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 g - C rawdg |
The rawdg-volset.ini file contains the following entries:
logicalhost-paris-1 is the primary host.
/dev/did/rdsk/d3s3 is the primary data.
/dev/did/rdsk/d3s4 is the primary bitmap.
logicalhost-newyork-1 is the secondary host.
/dev/did/rdsk/d3s5 is the secondary data.
/dev/did/rdsk/d3s6 is the secondary bitmap.
ip is the protocol.
async is the mode.
g is the G flag.
- is the IO group.
C is the C flag.
rawdg is the 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.
After you have added the device group to the protection group, avspg, you can manually enable the Sun StorEdge Availability Suite 3.2.1 volume sets.
The following example illustrates how to manually enable a Solaris Volume Manager volume set:
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 |
The following example illustrates how to manually enable a VERITAS Volume Manager volume set:
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 |
The following example illustrates how to manually enable a raw device volume set:
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 sndradm command execution is printed in the Sun StorEdge Availability Suite 3.2.1 log file, /var/opt/SUNWesm/ds.log. Refer to this file if you encounter errors while manually enabling the volume set.