How to Create a Failover Resource Group (Sun Cluster Data Services Planning and Administration Guide for Solaris OS)

Sun Cluster Data Services Planning and Administration Guide for Solaris OS

How to Create a Failover Resource Group

A failover resource group contains the following types of resources:

Network address resources, which are instances of the built-in resource types LogicalHostname and SharedAddress
Failover resources, which are the data service application resources for a failover data service

The network address resources and their dependent data service resources move between cluster nodes when data services fail over or are switched over.

Note –

Perform this procedure from any cluster node.

On a cluster member, become superuser or assume a role that provides solaris.cluster.modify RBAC authorization.

Create the failover resource group.
# clresourcegroup create [-n node-zone-list] resource-group
-n node-zone-list

Specifies a comma-separated, ordered list of nodes that can master this resource group. The format of each entry in the list is node:zone. In this format, node specifies the node name and zone specifies the name of a global-cluster non-voting node. To specify the global-cluster voting node, or to specify a node without global-cluster non-voting nodes, specify only node.

This list is optional. If you omit this list, the resource group is created on all nodes in the cluster.

Note –
To achieve highest availability, specify global-cluster non-voting nodes on different global-cluster voting nodes in a failover resource group's node list instead of different nodes on the same global-cluster voting node.

resource-group

Specifies your choice of the name of the failover resource group to add. This name must begin with an ASCII character.

Verify that the resource group has been created.
# clresourcegroup show resource-group

Example 2–4 Creating a Failover Resource Group

This example shows the creation of the failover resource group resource-group-1. The global cluster voting nodes phys-schost-1 and phys-schost-2 can master this resource group.

# clresourcegroup create -n phys-schost1,phys-schost-2 resource-group-1
# clresourcegroup show -v resource-group-1

=== Resource Groups and Resources ===          

Resource Group:                                 resource-group1
RG_description:                                 <NULL>
RG_mode:                                        Failover
RG_state:                                       Unmanaged
RG_project_name:                                default
RG_affinities:                                  <NULL>
RG_SLM_type:                                    manual
Auto_start_on_new_cluster:                      True
Failback:                                       False
Nodelist:                                       phys-schost-1 phys-schost-2
Maximum_primaries:                              1
Desired_primaries:                              1
RG_dependencies:                                <NULL>
Implicit_network_dependencies:                  True
Global_resources_used:                          <All>
Pingpong_interval:                              3600
Pathprefix:                                     <NULL>
RG_System:                                      False
Suspend_automatic_recovery:                     False

Next Steps

After you create a failover resource group, you can add application resources to this resource group. See Tools for Adding Resources to Resource Groups for the procedure.