PRIMECLUSTER Global Disk Services Configuration and Administration Guide 4.1 (Solaris(TM) Operating System)

6.6.1.5 Configuring an Environment

Automatic Resource Registration
If the backup server resides in a cluster domain (called a backup domain), those disks that are registered as resources in the primary domain or are to be registered with a shadow class in the backup domain may not be involved in the resource registration in the backup domain. In the backup domain, those relevant disks must be described in the Excluded Device List prior to executing the automatic resource registration. For details on the automatic resource registration, see "PRIMECLUSTER Cluster Foundation (CF) Configuration and Administration."

 

1) Creating an application volume

Create a stripe volume used for the services on disks c1t1d1, c2t1d1, c3t1d1, and c4t1d1. The following settings are necessary on Node1 or Node2 in the primary domain.

1-1) Registering disks

Register disks c1t1d1, c2t1d1, c3t1d1, and c4t1d1 with shared class Class1 that is shared on Node1 and Node2, and name them Disk1, Disk2, Disk3, and Disk4 respectively.

# sdxdisk -M -c Class1 -a type=shared,scope=Node1:Node2 -d c1t1d1=Disk1,c2t1d1=Disk2,c3t1d1=Disk2,c4t1d1=Disk4

1-2) Creating a stripe group

Connect disks Disk1, Disk2, Disk3, and Disk4 to stripe group Group1.

# sdxdisk -C -c Class1 -g Group1 -d Disk1,Disk2,Disk3,Disk4 -a type=stripe,width=256

1-3) Creating a stripe volume

Create stripe volume Volume1 to stripe group Group1.

# sdxvolume -M -c Class1 -g Group1 -v Volume1 -s 1048576 -a pslice=off