Removing Ops Center Automator software in a cluster environment

Ops Center Installation and Configuration Guide

Version
11.0.x
Audience
anonymous
Part Number
MK-99OPS001-25

You can remove the Ops Center Automator software from the server in a cluster environment to migrate to a different server or stop Ops Center Automator processes.

Note: If you remove Ops Center Automator, the properties files, log files, and other product-related files are deleted.
  1. In the cluster management software, move the group in which the Common Component services are registered from the standby node to the active node by right-clicking the group, selecting Move, and then either Select Node or Move this service or application to another node.
  2. Take offline and disable failover for the group in which Common Component services including Ops Center Automator are registered by using the following command:

    Common-Component-installation-directory\ClusterSetup\hcmds64clustersrvstate /soff /r cluster-group-name

    where

    r - specifies the name of the group in which the Common Component product services including Ops Center Automator are registered. If the group name contains spaces, you must enclose the group name in quotation marks ("). For example, if the group name is Automator cluster, specify "Automator cluster".

  3. Delete the Common Component services including Ops Center Automator by using the following command:
    Note: Before deleting the services, delete the "customer script" from the cluster management software.

    Common-Component-installation-directory\ClusterSetup\hcmds64clustersrvupdate /sdel /r cluster-group-name

    where

    r - specifies the name of the group in which the Common Component product services including Ops Center Automator are registered. If the group name contains spaces, you must enclose the group name in quotation marks ("). For example, if the group name is Automator cluster, specify "Automator cluster".

    Note:
    • All Ops Center Automator and Common Component product services that are registered in the group specified by the r option are deleted.
    • If you plan to continue using Common Component products, reregister them after you remove Ops Center Automator. Deleting the Ops Center Automator service does not cause a problem.

      Remember that if you changed the service resource names, all resource names are reinitialized when the services are reregistered. Therefore, you must write down the resource names for the services that you are deleting, and change the names after reregistering those services.

  4. Use the following command to stop the Common Component products:
    Common-Component-installation-folder\bin\hcmds64srv /stop
  5. Remove Hitachi Ops Center Automator from the active node.
  6. On the active node, delete any files and folders that are no longer required (such as those files and folders created during installation in the cluster environment).
  7. In the cluster management software, move the Ops Center Automator service group to the standby node by right-clicking the group, selecting Move, and selecting either Select Node or Move this service or application to another node.
  8. Remove Ops Center Automator from the standby node.
  9. After performing the removal of the cluster installation, delete the Ops Center Automator folder and, if you no longer plan to use any other Common Component services, also delete the Base64 folder from the standby node.
  10. If the following resources are not in use by other applications, use the cluster management software to take them offline, and then delete them:
    • IP address
    • Shared disk
  11. On the standby node, delete any files and folders that are no longer required (such as those files and folders created during installation in the cluster environment).
  12. To continue using other Common Component products, use the following command to register the Common Component services in the cluster management software group:

    Common-Component-installation-folder\ClusterSetup\hcmds64clustersrvupdate /sreg /r cluster-group-name /sd drive-letter-of-shared-disk /ap resource-name-for-client-access-point

    where

    r - specifies the name of the group in which you to plan to register the Common Component product services. If the group name contains spaces, you must enclose the group name in quotation marks ("). For example, if the group name is Automator cluster, specify "Automator cluster".

    sd - specifies the drive letter of the shared disk that is registered to the cluster management software. You cannot specify multiple drive letters for this option. If the database of Common Component products is divided into multiple shared disks, run the hcmds64clustersrvupdate command for each shared disk.

    ap - specifies the name of the resource for the client access point that is registered to the cluster management software.

  13. To continue using other Common Component products, use the following command to bring online and enable failover for the group in which the Common Component services are registered:

    Common-Component-installation-folder\ClusterSetup\hcmds64clustersrvstate /son /r cluster-group-name

    where

    r - specifies the name of the group in which the Common Component product services are registered. If the group name contains spaces, you must enclose the group name in quotation marks ("). For example, if the group name is Automator cluster, specify "Automator cluster".

  14. In the cluster management software, move the group containing the Common Component resources to the active node by right-clicking the group, selecting Move, and then selecting either Select Node or Move this service or application to another node.
  15. If you are using Common Services, delete the Ops Center Automator information from Common Services.

Ops Center Automator is removed from both the active and standby nodes.

Microsoft Visual C++ 2015-2022 Redistributable (x64) is not automatically removed. Make sure that other programs are not dependent on it, and remove it manually.