Sun Cluster 3.1 Data Services Developer's Guide

Resource Type Upgrade

See “property_attributes” in Sun Cluster Data Services Guide for additional information on upgrading or migrating a resource type.

Resource Type Upgrade
  1. Read the upgrade documentation for the new resource type to find out the resource type changes and resource tunability constraints.

  2. Install the resource type upgrade package on all cluster nodes.

    The recommended practice for installing new resource type packages is in a rolling upgrade fashion: the pkgadd occurs while the node is booted in non-cluster mode.

    There are scenarios in which it would be possible to install new resource type packages on a node in cluster mode:

    • If resource type package installation leaves the method code unchanged and only updates the monitor, then it is necessary to stop monitoring on all resources of that type during the installation.

    • If resource type package installation leaves both the method and monitor code unchanged then it is not necessary to stop monitoring on the resource during the installation, because the installation is only putting a new RTR file on the disk.

  3. Register the new resource type version using the scrgadm (or equivalent) command, referencing the RTR file of the upgrade.

    The RGM creates a new resource type whose name is of the form


     vendor_id.resource_type:version
  4. If the resource type upgrade is installed on only a subset of the nodes, then an additional step must be taken; the Installed_nodes property of the new resource type must be set to the nodes on which it is actually installed. When a resource takes on the new type (either by being newly created or updated), the RGM requires that the resource group nodelist be a subset of the Installed_nodes list of the resource type.


    scrgadm -c -t <resource_type> -h <installed_node_list>
  5. For each resource of the preupgraded type that is to be migrated to the upgraded type, invoke scswitch to change the state of the resource or its resource group to the appropriate state as dictated by the upgrade documentation.

  6. For each resource of the preupgraded type that is to be migrated to the upgraded type, edit the resource, changing its Type_version property to the new version.


    scrgadm -c -j <resource> -y Type_version=<new version>

    If necessary, edit other properties of the same resource to appropriate values in the same command.

  7. Restore the previous state of the resource or resource group by reversing the command invoked in Step 5.