Hitachi

JP1 Version 12 JP1/Integrated Management 2 - Manager Configuration Guide


7.7.3 Updating IM databases in a cluster environment (for Windows)

If you have upgraded JP1/IM - Manager or applied a corrected version of JP1/IM - Manager in a cluster environment while using IM databases, you must update the IM databases in the cluster environment. Use the procedure described below to update IM databases.

This procedure assumes that the host on which the JP1/IM - Manager of a logical host is running is the active host and the host on which the JP1/IM - Manager is not running is the standby host.

To update IM databases in a cluster environment:

  1. Check the following service statuses:

    If the status are different from the following status, stop the services to create the following status.

    • If JP1/IM - MO is being used, the JP1/IM - Message Optimizer service of JP1/IM - MO is stopped at the connection source.

    • If JP1/OA is receiving JP1 event from JP1/IM2 - Manager, JP1/OA is stopped at the connection source.

  2. By operating the cluster software on the active host, place the following services offline and stop them by order:

    • JP1/IM2 - Manager Service on the logical host (service name that is displayed: JP1/IM2-Manager_logical-hostname)

    • JP1/IM2 - Manager DB Cluster Service on the logical host (service name that is displayed: JP1/IM2-Manager DB Cluster Service_logical-host-name)

    • The IM database service on the logical host (service name that is displayed: JP1/IM2-Manager DB Server_logical-host-name)

  3. In addition to transferring the shared disk and the logical IP address assigned to the active host to the standby host, make sure that the shared disk and the logical IP address can be used on the logical host.

  4. On the standby host, start the following service from the service window of the OS by order:

    • The IM database service on the logical host (service name that is displayed: JP1/IM2-Manager DB Server_logical-host-name)

    • JP1/IM2 - Manager DB Cluster Service on the logical host (service name that is displayed: JP1/IM2-Manager DB Cluster Service_logical-host-name)

  5. On standby host, execute the jimdbstatus command.

    • Check that the IM database service is operational (the KNAN11182-I message is output).

      KNAN11182-I The IM database service is running.

    • If the IM database service is not operational, execute the jimdbstatus command every 10 seconds, and then wait until the service is operational.

      jimdbstatus -h logical-host-name

  6. Execute the jimdbstop command to stop the IM databases on the standby host:

    jimdbstop -h logical-host-name

  7. On the standby host, stop the following service from the service window of the OS:

    JP1/IM2 - Manager DB Cluster Service on the logical host (service name that is displayed: JP1/IM2-Manager DB Cluster Service_logical-host-name)

  8. In addition to transferring the shared disk and the logical IP address assigned to the standby host to the active host, make sure that the shared disk and the logical IP address can be used on the logical host.

  9. Execute the jimdbupdate command on the standby host:

    jimdbupdate -h logical-host-name

    • If the following message is output, perform the procedure beginning with step 11:

      KNAN11201-I The IM database service is the latest.

    • If the following message is output, perform the procedure beginning with step 10:

      KNAN11202-I The overwrite is necessary for the IM database.

      KNAN11211-I An update of the configuration files of an IM database service is required.

    The following message will be output on the standby host, but it is not a problem.

    KNAN11210-W The table schema could not be checked because a common disk could not be accessed.

  10. Execute the jimdbupdate command to update the IM databases on the standby host:

    jimdbupdate -h logical-host-name -i

    The following message will be output on the standby host, but it is not a problem.

    KNAN11210-W The table schema could not be checked because a common disk could not be accessed.

  11. On the standby host, stop the following service from the service window of the OS:

    The IM database service on the logical host (service name that is displayed: JP1/IM2-Manager DB Server_logical-host-name)

  12. On the active host, stop the following service from the service window of the OS:

    The IM database service on the logical host (service name that is displayed: JP1/IM2-Manager DB Server_logical-host-name)

  13. Execute the jimdbupdate command on the active host:

    jimdbupdate -h logical-host-name

    • If the following message is output, perform step 16:

      KNAN11201-I The IM database service is the latest.

    • If the following message is output, perform the procedure beginning with step 14:

      KNAN11202-I The overwrite is necessary for the IM database.

      KNAN11207-I An update of the table schema of an IM database service is required.

      KNAN11211-I An update of the configuration files of an IM database service is required.

  14. Execute the jimdbbackup command to back up the IM databases on the active host:

    jimdbbackup -h logical-host-name -o backup-file-name -m MAINT

  15. Execute the jimdbupdate command to update the IM databases on the active host:

    jimdbupdate -h logical-host-name -i

  16. On the active host, stop the following service from the service window of the OS:

    The IM database service on the logical host (service name that is displayed: JP1/IM2-Manager DB Server_logical-host-name)

  17. By operating the cluster software on the active host, place the following services online and start them by order:

    JP1/IM - Manager Service on the logical host (service name that is displayed: JP1/IM2-Manager_logical-host-name)

    JP1/IM - Manager DB Cluster Service on the logical host (service name that is displayed: JP1/IM2-Manager DB Cluster Service_logical-host-name)

  18. Start the services stopped in step 1.

    Important

    Do not restore any IM database backup data that was obtained before the jimdbupdate command was executed into an IM database obtained after the jimdbupdate command has been executed.

    After you have executed the jimdbupdate command, execute the jimdbbackup command again to make a new backup.