How to Set Up an RGOffload Resource

Steps

1. Become superuser on a cluster member.

2. Determine whether the RGOffload resource type is registered.

   The following command prints a list of resource types.

   # scrgadm -p|egrep SUNW.RGOffload

3. If necessary, register the resource type.

   # scrgadm -a -t SUNW.RGOffload

4. Set the Desired_primaries property to zero in each resource group that the RGOffload resource is to be offload.

   # scrgadm -c -g offload-rg -y Desired_primaries=0

5. Add the RGOffload resource to the critical failover resource group and set the extension properties.

   Do not place a resource group on more than one resource's rg_to_offload list. Placing a resource group on multiple rg_to_offload lists might cause the resource group to be taken offline and brought back online repeatedly.

   For a description of RGOffload extension properties, see Configuring RGOffload Extension Properties.

   # scrgadm -aj rgoffload-resource \ -t SUNW.RGOffload -g critical-rg \ -x rg_to_offload=offload-rg-1, offload-rg-2, ... \ -x continue_to_offload=TRUE \ -x max_offload_retry=15

   ---

   Note –

   Extension properties other than rg_to_offload are shown with default values here. rg_to_offload is a comma-separated list of resource groups that are not dependent on each other. This list cannot include the resource group to which the RGOffload resource is being added.

   ---

6. Enable the RGOffload resource.

   # scswitch -ej rgoffload-resource

7. Set the dependency of the critical failover resource on the RGOffload resource.

   # scrgadm -c -j critical-resource \ -y Resource_dependencies=rgoffload-resource

   You can also use Resource_dependencies_weak. Using Resource_dependencies_weak on the RGOffload resource type allows the critical failover resource to start even if errors are encountered during offload of offload-rg.

8. Bring online the resource group that is to be offloaded

   # scswitch -z -g offload-rg, offload-rg-2, ... -h [nodelist]

   The resource group remains online on all nodes where the critical resource group is offline. The fault monitor prevents the resource group from running on the node where the critical resource group is online.

   In Step 4, Desired_primaries for resource groups that are to be offloaded was set to 0. Therefore, the -Zoption cannot bring these resource groups online.

9. If the critical failover resource group is not online, bring it online.

   # scswitch -Z -g critical-rg

Example 2–39 Configuring an RGOffload Resource

This example shows how to configure the RGOffload resource rgofl as follows:

• The critical resource group oracle_rg contains the RGOffload resource.

• The critical resource is oracle-server-rs.

• The scalable resource groups IWS-SC and IWS-SC-2 are to be offloaded when the critical resource group comes online.

• The resource groups oracle_rg, IWS-SC, and IWS-SC-2 can be mastered on any node of cluster triped, namely: phys-triped-1, phys-triped-2, or phys-triped-3.

[Determine whether the SUNW.RGOffload resource type is registered.]
# scrgadm -p|egrep SUNW.RGOffload
 
[If needed, register the resource type.]
# scrgadm -a -t SUNW.RGOffload

[Set the Desired_primaries to zero in each resource group to be 
offloaded by the RGOffload resource.]
# scrgadm -c -g IWS-SC-2 -y Desired_primaries=0
# scrgadm -c -g IWS-SC -y Desired_primaries=0

[Add the RGOffload resource to the critical resource group and set 
the extension properties.]
# scrgadm -aj rgofl -t SUNW.RGOffload -g oracle_rg \
-x rg_to_offload=IWS-SC,IWS-SC-2 -x continue_to_offload=TRUE \
-x max_offload_retry=15

[Enable the RGOffload resource.]
# scswitch -ej rgofl

[Set the dependency of the critical failover resource to the RGOffload resource.]
# scrgadm -c -j oracle-server-rs -y Resource_dependencies=rgofl

[Bring online on all nodes the resource groups that are to be offloaded.]
# scswitch -z -g IWS-SC,IWS-SC-2 -h phys-triped-1,phys-triped-2,phys-triped-3

[If the critical failover resource group is not online, bring it online.]
# scswitch -Z -g oracle_rg