Go to main content

Planning and Administering Data Services for Oracle® Solaris Cluster 4.4

Exit Print View

Updated: November 2019
 
 

How to Migrate Existing Resources to a New Version of the Resource Type

The instructions that follow explain how to use the clresource command to perform this task. However, you are not restricted to using the clresource command for this task. Instead of the clresource command, you can use Oracle Solaris Cluster Manager or the Resource Group option of the clsetup command to perform this task. See clsetup(8CL) for more information.

Before You Begin

Consult the instructions for upgrading the resource type to determine when you can migrate resources to a new version of the resource type.

  • Any time

  • Only when the resource is unmonitored

  • Only when the resource is offline

  • Only when the resource is disabled

  • Only when the resource group is unmanaged

The instructions might state that you cannot upgrade your existing version of the resource. If you cannot migrate the resource, consider the following alternatives:

  • Deleting the resource and replacing it with a new resource of the upgraded version

  • Leaving the resource at the old version of the resource type

  1. On a cluster member, assume the root role that provides solaris.cluster.modify RBAC authorization.
  2. For each resource of the resource type that is to be migrated, change the state of the resource or its resource group to the appropriate state.
    • If you can migrate the resource at any time, no action is required.
    • If you can migrate the resource only when the resource is unmonitored, type the following command:
      # clresource unmonitor resource
    • If you can migrate the resource only when the resource is offline, type the following command:
      # clresource disable resource

      Note -  If other resources depend on the resource that you are migrating, this step fails. In this situation, consult the error message that is printed to determine the names of the dependent resources. Then repeat this step, specifying a comma-separated list that contains the resource that you are migrating and any dependent resources.
    • If you can migrate the resource only when the resource is disabled, type the following command:
      # clresource disable resource

      Note -  If other resources depend on the resource that you are migrating, this step fails. In this situation, consult the error message that is printed to determine the names of the dependent resources. Then repeat this step, specifying a comma-separated list that contains the resource that you are migrating and any dependent resources.
    • If you can migrate the resource only when the resource group is unmanaged, type the following commands:
      # clresource disable -g resource-group +
      # clresourcegroup offline resource-group
      # clresourcegroup unmanage resource-group

      The replaceable items in these commands are as follows:

      resource-group

      Specifies the resource group that is to be unmanaged

  3. For each resource of the resource type that is to be migrated, change the Type_version property to the new version.

    If necessary, set other properties of the same resource to appropriate values in the same command. To set these properties, specify the –p option in the command.

    To determine whether you are required to set other properties, consult the instructions for upgrading the resource type. You might be required to set other properties for the following reasons:

    • An extension property has been introduced in the new version of the resource type.

    • The default value of an existing property has been changed in the new version of the resource type.

    # clresource set -p Type_version=new-version \
    [-p extension-property=new-value] [-p standard-property=new-value] resource

    Note -  If the existing version of the resource type does not support upgrades to the new version, this step fails.
  4. Restore the previous state of the resource or resource group by reversing the command that you typed in Step 2.
    • If you can migrate the resource at any time, no action is required.

      Note -  After migrating a resource that can be migrated at any time, the resource probe might not display the correct resource type version. In this situation, disable and re-enable the resource's fault monitor to ensure that the resource probe lists the correct resource type version.
    • If you can migrate the resource only when the resource is unmonitored, type the following command:
      # clresource monitor resource
    • If you can migrate the resource only when the resource is offline, type the following command:
      # clresource enable resource

      Note -  If you disabled in Step 2 other resources that depend on the resource that you are migrating, enable the dependent resources also.
    • If you can migrate the resource only when the resource is disabled, type the following command:
      # clresource enable resource

      Note -  If you disabled in Step 2 other resources that depend on the resource that you are migrating, enable the dependent resources also.
    • If you can migrate the resource only when the resource group is unmanaged, type the following commands:
      # clresource enable -g resource-group +
      # clresourcegroup manage resource-group
      # clresourcegroup online resource-group
Example 5  Migrating a Resource That Can Be Migrated Only When Offline

This example shows the migration of a resource that can be migrated only when the resource is offline. The new resource type package contains methods that are located in new paths. Because the methods are not overwritten during the installation, the resource does not need to be disabled until after the upgraded resource type is installed.

The characteristics of the resource in this example are as follows:

  • The new resource type version is 2.0.

  • The resource name is myresource.

  • The resource type name is myrt.

  • The new RTR file is in /opt/XYZmyrt/etc/XYZ.myrt.

  • No dependencies on the resource that is to be migrated exist.

  • The resource that is to be migrated can be taken offline while leaving the containing resource group online.

This example assumes that the upgrade package is already installed on all cluster nodes according to the supplier's directions.

# clresourcetype register -f /opt/XYZmyrt/etc/XYZ.myrt myrt
# clresource disable myresource
# clresource set -p Type_version=2.0 myresource
# clresource enable myresource
Example 6  Migrating a Resource That Can Be Migrated Only When Unmonitored

This example shows the migration of a resource that can be migrated only when the resource is unmonitored. The new resource type package contains only the monitor and RTR file. Because the monitor is overwritten during installation, monitoring of the resource must be disabled before the upgrade package is installed.

The characteristics of the resource in this example are as follows:

  • The new resource type version is 2.0.

  • The resource name is myresource.

  • The resource type name is myrt.

  • The new RTR file is in /opt/XYZmyrt/etc/XYZ.myrt.

The following operations are performed in this example.

  1. Before the upgrade package is installed, the following command is run to disable monitoring of the resource:

    # clresource unmonitor myresource
  2. The upgrade package is installed on all cluster nodes according to the supplier's directions.

  3. To register the new version of the resource type, the following command is run:

    # clresourcetype register -f /opt/XYZmyrt/etc/XYZ.myrt myrt
  4. To change the Type_version property to the new version, the following command is run:

    # clresource set -p Type_version=2.0 myresource
  5. To enable monitoring of the resource after its migration, the following command is run:

    # clresource monitor myresource