Hitachi

Job Management Partner 1 Version 10 Job Management Partner 1/Automatic Operation Administration Guide


12.4 Restoring data in a JP1/AO system (cluster configuration)

After performing tasks such as replacing a host in a JP1/AO system or performing database maintenance, restore the JP1/AO and JP1/Base data you backed up.

Important note
  • When you back up and restore data in a JP1/AO system, some aspects of the data do not survive the backup process. For example, some of the detailed task information (step lists and progress information) is lost, and some task statuses are changed.

    Before backing up data, you can execute the listtasks command to output detailed task information. In addition, you can re-register scheduled tasks and recurring tasks (with the same settings) as other tasks in a batch, by using the output detailed task information and executing the submittask command after restoration.

  • Execute the restoresystem command on the primary server (the server whose mode is set to online in the cluster.conf file).

  • Execute the backupsystem command to create backup data.

  • Make sure that the following attributes on the host from which the backup was obtained and on the host to which the backup is being restored are consistent:

    Installation folder path, host name#, IP address, JP1 users to OS users, and system locale

    #

    The host name need not be consistent if you are changing the host name of the JP1/AO server or you are restoring the information as part of a migration to an environment with a different host name.

Who can perform this task:

Domain user with Administrator permissions for the OS and administration permission for the cluster

To restore a JP1/AO system (cluster configuration):

  1. Make sure that there are no tasks in In Progress, Waiting for Response, Abnormal Detection, or Terminated status. If there are such tasks in the system, either stop the tasks, or wait until they enter Completed or Failed status.

  2. Take the following services and scripts registered in the cluster software offline:

    • stopcluster command

    • HAutomation Engine logical-host-name

    • HAutomation Engine Web Service

    • HBase Storage Mgmt Web Service

    • HBase Storage Mgmt Common Service

    • Services of Hitachi Command Suite products

  3. Shut down the JP1/AO system by executing the hcmdssrv command with the /stop option specified.

  4. In the cluster software, take the registered HiRDB/ClusterService _HD0 service offline.

  5. Disable failover of the services and scripts registered in the cluster software listed below.

    Configure JP1/AO not to restart if resources enter Failed status in the cluster software.

    • JP1/Base_logical-host-name

    • JP1/Base Event logical-host-name

    • HiRDB/ClusterService _HD0

    • HBase Storage Mgmt Common Service

    • HBase Storage Mgmt Web Service

    • HAutomation Engine Web Service

    • HAutomation Engine logical-host-name

    • stopcluster command

    • Services of Hitachi Command Suite products

  6. Restore the configuration information and database information for JP1/Base.

    When restoring JP1/AO while replacing hosts, if JP1/AO on the origination host is version 10-00 or later, you do not need to perform this step.

  7. Bring the shared disk on the active server online.

  8. On the primary server, execute the restoresystem command to restore the database and configuration information for JP1/AO.

    Tip

    The following files are not restored by executing the restoresystem command. Relocate them manually if necessary.

    • SSL server certificate file for HTTPS connection

    • Private key file for HTTPS connection

    • Private key file for public key authentication

    Store the files for HTTPS connection in the location defined in the httpsd.conf file, and the files for public key authentication in the location defined in the property file (config_user.peroperties).

  9. Shut down the JP1/AO system by executing the hcmdssrv command with the /stop option specified.

  10. On the primary server, reconfigure the following definition files to match the environment to which the data is being restored.

    These definition files are backed up but not restored.

    • Configuration file for external authentication server linkage (exauth.properties)

    • Security definition file (security.conf)

    • Port number settings (httpsd.conf, hsso.conf)

    The definition files can be found in the following folders:

    • backup-folder\HBase\base\conf

    • backup-folder\HBase\base\httpsd.conf

  11. If you changed the port number used for communication between JP1/AO and the Web browser or the port number used to communicate with task-processing engine on the primary server, make the same changes again in the target environment by following the procedure for changing port numbers.

  12. Enable HTTPS connection on the active server if HTTPS connection is used for communication between JP1/AO and the Web browser.

  13. Perform steps 9 to 12 on the standby server.

  14. Enable failover of the services and scripts listed below registered in the cluster software.

    Configure the cluster software to restart resources on the current node if they enter Failed status, and to fail over the applicable resources if they could not be restarted.

    • JP1/Base_logical-host-name

    • JP1/Base Event logical-host-name

    • HiRDB/ClusterService _HD0

    • HBase Storage Mgmt Common Service

    • HBase Storage Mgmt Web Service

    • HAutomation Engine Web Service

    • HAutomation Engine logical-host-name

    • stopcluster command

    • Services of Hitachi Command Suite products

  15. Bring the following services and scripts registered in the cluster software online:

    • HiRDB/ClusterService _HD0

    • HBase Storage Mgmt Common Service

    • HBase Storage Mgmt Web Service

    • HAutomation Engine Web Service

    • HAutomation Engine logical-host-name

    • stopcluster command

    • Services of Hitachi Command Suite products

Data is restored to the specified host.

Related topics