Hitachi

JP1 Version 12 JP1/Automatic Operation Configuration Guide 


6.5.2 Procedure to configure services before overwrite or upgrade installation (Windows)

You must configure services before installation.

To configure services before installation:

  1. In the Tasks window, check the tasks. If any tasks are in execution status (In Progress, Waiting for Input, In Progress (with Error), In Progress (Terminating), or Long Running), stop execution of the tasks or wait until the task status changes to the ended status.

  2. Use the cluster software to move the resource group where the JP1/AO service is registered to the active server.

  3. Use the cluster software to bring the above resource group online.

  4. Use the cluster software to bring the services and scripts offline.

    If the Hitachi Command Suite products are installed, bring all services and scripts offline except for the following services:

    • HiRDB/ClusterService _HD0 (for an upgrade installation in a cluster environment built with JP1/AO version 10)

    • HiRDB/ClusterService _HD1 (for an overwrite or upgrade installation in a cluster environment built with JP1/AO version 11 or later)

    • JP1/Base_logical-host-name (for an upgrade installation in a cluster environment built with a version of JP1/AO earlier than 11-10)

    • JP1/Base Event _logical-host-name (for an upgrade installation in a cluster environment built with a version of JP1/AO earlier than 11-10)

    If the Hitachi Command Suite products are not installed, bring the following services and script offline:

    • HAutomation Engine Web Service

    • HAutomation Engine logical-host-name (for an upgrade installation in a cluster environment built with a version of JP1/AO earlier than 11-10)

    • HBase Storage Mgmt Common Service (for an upgrade installation in a cluster environment built with JP1/AO version 10)

    • HBase Storage Mgmt Web Service (for an upgrade installation in a cluster environment built with JP1/AO version 10)

    • HBase 64 Storage Mgmt SSO Service (for an overwrite or upgrade installation in a cluster environment built with JP1/AO version 11 or later)

    • HBase 64 Storage Mgmt Web Service (for an overwrite or upgrade installation in a cluster environment built with JP1/AO version 11 or later)

    • HBase 64 Storage Mgmt Web SSO Service (for an overwrite or upgrade installation in a cluster environment built with JP1/AO version 11 or later)

    • stopcluster command#(for an upgrade installation in a cluster environment built with a JP1/AO version 10)

  5. On the active server, execute the hcmds64srv command with the /stop option specified to stop the JP1/AO service.

  6. Use the cluster software to bring the following services offline:

    • HiRDB/ClusterService _HD0 (for an upgrade installation in a cluster environment built with JP1/AO version 10)

    • HiRDB/ClusterService _HD1 (for an overwrite or upgrade installation in a cluster environment built with JP1/AO version 11 or later)

    • JP1/Base_logical-host-name (for an upgrade installation in a cluster environment built with a version of JP1/AO earlier than 11-10)

    • JP1/Base Event _logical-host-name (for an upgrade installation in a cluster environment built with a version of JP1/AO earlier than 11-10)

  7. Use the cluster software to move the resource group where the JP1/AO service is registered to the standby server.

  8. Use the cluster software to bring the above resource group offline.

  9. Use the cluster software to bring the services and scripts offline.

    If the Hitachi Command Suite products are installed, bring the services and scripts offline, except for the following services:

    • HiRDB/ClusterService _HD0 (for an upgrade installation in a cluster environment built with JP1/AO version 10)

    • HiRDB/ClusterService _HD1 (for an overwrite or upgrade installation in a cluster environment built with JP1/AO version 11 or later)

    • JP1/Base_logical-host-name

      (for an upgrade installation in a cluster environment built with a version of JP1/AO earlier than 11-10)
    • JP1/Base Event _logical-host-name (for an upgrade installation in a cluster environment built with a version of JP1/AO earlier than 11-10)

    If the Hitachi Command Suite products are not installed, bring the following services and script offline:

    • HAutomation Engine Web Service

    • HAutomation Engine logical-host-name (for an upgrade installation in a cluster environment built with a version of JP1/AO earlier than 11-10)

    • HBase Storage Mgmt Common Service (for an upgrade installation in a cluster environment built with JP1/AO version 10)

    • HBase Storage Mgmt Web Service (for an upgrade installation in a cluster environment built with JP1/AO version 10)

    • HBase 64 Storage Mgmt SSO Service (for an overwrite or upgrade installation in a cluster environment built with JP1/AO version 11 or later)

    • HBase 64 Storage Mgmt Web Service (for an overwrite or upgrade installation in a cluster environment built with JP1/AO version 11 or later)

    • HBase 64 Storage Mgmt Web SSO Service (for an overwrite or upgrade installation in a cluster environment built with JP1/AO version 11 or later)

    • stopcluster command#

      (for an upgrade installation in a cluster environment built with JP1/AO version 10)
  10. On the standby server, execute the hcmds64srv command with the /stop option specified to stop the JP1/AO service.

  11. Use the cluster software to bring the following services offline:

    • HiRDB/ClusterService _HD0 (for an upgrade installation in a cluster environment built with JP1/AO version 10)

    • HiRDB/ClusterService _HD1 (for an overwrite or upgrade installation in a cluster environment built with JP1/AO version 11 or later)

    • JP1/Base_logical-host-name

      (for an upgrade installation in a cluster environment built with JP1/AO version 10)
    • JP1/Base Event _logical-host-name (for an upgrade installation in a cluster environment built with JP1/AO version 10)

  12. In the cluster software, suppress failover for the resource group where JP1/AO is registered.

    Right-click a service or script in the cluster software, select Properties, and then Policies. Then, specify the settings so that a restart does not occur if the resource fails. Perform this action for all services and scripts registered in the resource group in order to suppress failover.

#

This command does not exist when an upgrade installation is performed in a cluster environment built with JP1/AO whose version is 10-12-01 or earlier or 10-13 (except version 10-13-01 or later) .