Hitachi

JP1 Version 12 JP1/Automatic Job Management System 3 Administration Guide


2.5.3 Recovery

The following describes how to recover the JP1/AJS3 - Manager by using the backup enhancement function.

Organization of this subsection

(1) Recovering data other than the embedded database

If a system environment that uses JP1/AJS3 has been damaged due to a corrupted disk or another problem, you must first recover the data other than the embedded database. At this time, use a backup of the entire system, if one is available, to recover the system environment. If you do not have a backup of the entire system, perform the following.

(a) Installing and setting up JP1/Base

Install JP1/Base and set up JP1/Base. For details about how to install and set up JP1/Base, see the JP1/Base User's Guide.

(b) Installing JP1/AJS3 - Manager

Install JP1/AJS3 - Manager. The JP1/AJS3 - Manager installation procedure varies depending on the OS. For details, see the following table:

No.

OS

Reference

1

Windows

2.2.3(1) New installation in the JP1/Automatic Job Management System 3 Configuration Guide

2

HP-UX

12.2.3 Installation in HP-UX in the JP1/Automatic Job Management System 3 Configuration Guide

3

Solaris

12.2.4 Installation in Solaris in the JP1/Automatic Job Management System 3 Configuration Guide

4

AIX

12.2.5 Installation in AIX in the JP1/Automatic Job Management System 3 Configuration Guide

5

Linux

12.2.6 Installation in Linux in the JP1/Automatic Job Management System 3 Configuration Guide

(c) Recovering the JP1/Base setup information

For details about recovering the JP1/Base setup information, see 2.3.3 Recovering the JP1/Base setup information.

(d) Recovering the physical host and logical host environments

You must set up the physical host and logical host for recovery in the same environment as the one in which the backup was created. When you recover the physical host and logical host, make sure that the following items match between the environment in which the backup was created and the environment to be recovered:

  • JP1/AJS3 - Manager version

  • Embedded database version

  • Configuration of the embedded database

  • Scheduler service configuration

  • Added database area (Only when the database area of the embedded database was expanded by using the ajsembdbaddarea command in the environment in which the backup was created.)

  • The system definition of embedded database

For details about how to enable the backup enhancement function and set up the physical host, see 21.6.1(1) When creating a new scheduler service and embedded database after performing a new installation in the JP1/Automatic Job Management System 3 Configuration Guide. For details about how to enable the backup enhancement function and set up the logical host, see 21.6.2(1) When creating a new logical host in the JP1/Automatic Job Management System 3 Configuration Guide.

(2) Recovering data of the embedded database

To recover data of the embedded database by using the jajs_dbrestore command:

  1. Store the backup data created by using the jajs_dbbackup command in the environment after recovery.

    Cautionary note

    Do not store the backup data on a network drive. If you specify backup data that is stored on a network drive, subsequent operation cannot be guaranteed.

  2. Stop the JP1/AJS3 services on the host to be recovered.

  3. Confirm the status of the embedded DB to be recovered.

    ajsembdbstatus -s ust -id embedded-database-setup-ID
  4. If the embedded DB to be recovered has started, stop the embedded DB normally. If the target embedded database is not running, start it, and then stop it normally.

    Example of the command used to start an embedded database:

    ajsembdbstart -id embedded-database-setup-ID

    Example of the command used to stop an embedded database normally:

    ajsembdbstop -id embedded-database-setup-ID
  5. Execute the jajs_dbrestore command.

    Execute the command with the following specified: the setup identifier of the embedded database to be recovered and the backup data used for recovery. The following shows an execution example.

    jajs_dbrestore -id embedded-database-setup-ID -i backup-data

    The specified backup data is recovered in the embedded database.

    For details about the jajs_dbrestore command, see jajs_dbrestore in 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference.

  6. Start the JP1/AJS3 services.

    Execute the jajs_spmd_status command to confirm that all processes are running normally.

(3) Perform necessary operations after recovery

To perform necessary operations after recovery, such as checking the statuses of jobnets and jobs and canceling suppression of job execution:

  1. Check the jobnets' and jobs' statuses existing when the failure occurred, and then change the statuses or rerun the jobnets and jobs as necessary.

    If you recover the embedded database by using the jajs_dbrestore command, the scheduler service will start in disaster recovery mode the next time the system starts after recovery. In this case, the scheduler service starts in the status in which execution is suppressed, and the statuses of jobs and jobnets are changed. Use JP1/AJS3 - View or a command to check the status of each job, and then, if necessary, change the statuses of jobs or rerun jobs.

    For details about the status in which jobnets and jobs are placed when JP1/AJS3 is started in disaster-recovery mode, see the description of the statuses of jobnets and jobs when a disaster recovery start is performed in 6.2.1(3)(a) Statuses when a JP1/AJS3 service on the manager host is restarted.

    For details about how to check and change job execution statuses and how to rerun a job, see the JP1/Automatic Job Management System 3 Operator's Guide.

  2. Delete the manager host information that is related to event jobs and remains on the agent host.

    Run the following command on the manager host to delete the manager host information that existed before recovery and remains on the agent host.

    For the -a option, specify the execution host name that corresponds to the target execution agent name.

    jpomanevreset -h logical-host-name -F scheduler-service-name -dh manager-host-name -a execution-host-name

    If the manager host to be recovered is a physical host, you do not need to specify the -h option.

    If the manager host to be recovered is a logical host, specify the manager host name of the logical host for the -h option and -dh option.

  3. Cancel suppression of job execution.

    Execute the following command to cancel suppression of job execution, and then resume work tasks.

    ajsalter -s none -F scheduler-service-name