Job Management Partner 1/Automatic Job Management System 3 Administration Guide

[Contents][Glossary][Index][Back][Next]

2.2.2 Backing up the JP1/AJS3 - Manager setup information

If you back up JP1/AJS3 - Manager, you must also back up JP1/Base at the same time.

The following lists the tasks required to back up the JP1/AJS3 - Manager setup information.

The following describes how to perform these tasks.

Organization of this subsection
(1) Backing up the files used in JP1/AJS3
(2) Backing up the execution agent information
(3) Backing up the execution environment definition for QUEUE jobs and submitted jobs
(4) Backing up the unit definition
(5) Backing up the JP1/AJS3 Console setup information

(1) Backing up the files used in JP1/AJS3

Use any method to back up the files used in JP1/AJS3 - Manager either by physical host or by logical host.

The files you need to back up in Windows and UNIX are different. The following subsections describe the files that need to be backed up in each system.

(a) In Windows

The following table lists the JP1/AJS3 - Manager files you need to back up in Windows.

Table 2-2 JP1/AJS3 - Manager files to be backed up (in Windows)

File name Description
JP1/AJS3-folder#1\jp1ajs_env.conf JP1/AJS3 environment definition file
JP1/AJS3-folder#1\jp1ajs_spmd.conf JP1/AJS3 process management definition file
JP1/AJS3-folder#1\jp1ajs_service_0700.conf Extended startup process definition file
JP1/AJS3-folder#1\jp1ajs_spmd_pre.conf#2 JP1/AJS3 pre-start process definition file
JP1/AJS3-folder#1\Agent.conf Agent management control settings file
JP1/AJS3-folder#1\Profiles#3 Folder containing the customization information for windows and dialog boxes used in JP1/AJS3 - View
JP1/AJS3-folder#1\jpqsetup.conf#4 Configuration definition file for the execution environment for QUEUE jobs and submitted jobs
JP1/AJS3-Manager-installation-folder\conf\jpoov.conf#2 Definition file for linkage with HP NNM

#1
Substitute the following folder for JP1/AJS3-folder:
  • For a physical host: JP1/AJS3-Manager-installation-folder\conf
  • For a logical host: shared-folder\jp1ajs2\conf

#2
This file exists only if the function is used.

#3
If you are using the common user profile, back up the entire folder.

#4
If you use a definition file to execute the jpqimport command, back up the execution environment definition for QUEUE jobs and submitted jobs described later, and then back up the file.

(b) In UNIX

The following table lists the JP1/AJS3 - Manager files you need to back up in UNIX.

Table 2-3 JP1/AJS3 - Manager files to be backed up (in UNIX)

File name Description
JP1/AJS3-directory#1/jp1ajs_env.conf JP1/AJS3 environment definition file
JP1/AJS3-directory#1/jp1ajs_spmd.conf JP1/AJS3 process management definition file
JP1/AJS3-directory#1/jp1ajs_service_0700.conf Extended startup process definition file
JP1/AJS3-directory#1/jp1ajs_spmd_pre.conf#2 JP1/AJS3 pre-start process definition file
JP1/AJS3-directory#1/Agent.conf Agent management control settings file
JP1/AJS3-directory#1/Schedule.conf Scheduler service environment settings file
JP1/AJS3-directory#1/EVAction.conf Definition file for the event and action execution environment
JP1/AJS3-directory#1/profiles#4 Directory containing customization information for windows and dialog boxes used in JP1/AJS3 - View
JP1/AJS3-directory#1/Queue.conf Execution environment settings file for QUEUE jobs and submitted jobs
JP1/AJS3-directory#1/jpqsetup.conf#3 Configuration definition file for the execution environment for QUEUE jobs and submitted jobs
JP1/AJS3-directory#1/Queueless.conf Queueless job execution environment settings file
/etc/opt/jp1ajs2/jajs_start Automatic start script#5
/etc/opt/jp1ajs2/jajs_stop Automatic stop script#5
/etc/opt/jp1ajs2/jajs_start.cluster Logical host start script#5
/etc/opt/jp1ajs2/jajs_stop.cluster Logical host stop script#5
/etc/opt/jp1ajs2/jajs_killall.cluster Logical host forced stop script#5
/etc/opt/jp1ajs2/conf/jpoov.conf#2 Definition file for linkage with HP NNM

#1
Substitute the following directory for JP1/AJS3-folder:
  • For a physical host: /etc/opt/jp1ajs2/conf
  • For a logical host: shared-directory/jp1ajs2/conf

#2
This file exists only if the function is used.

#3
If you use a definition file to execute the jpqimport command, back up the execution environment definition for QUEUE jobs and submitted jobs described later, and then back up the file.

#4
If you are using the common user profile, back up each directory.

#5
Back up the script as required.

(2) Backing up the execution agent information

The following describes how to back up the execution agent information.

Execute the following command to back up the definition information for an execution agent or an execution agent group to any execution agent definition file. Specify the -l option to back up the definition information of all execution agents or execution agent groups.

Definition information includes the execution agent name, execution host name, and the maximum number of concurrently executable jobs.

 
ajsagtprint [-h manager-host-name] {-a execution-agent-name | -g execution-agent-group-name | -l} 
> execution-agent-definition-file

Cautionary note
Before starting the backup of execution agent information, make sure that the JP1/AJS3 service is running.

(3) Backing up the execution environment definition for QUEUE jobs and submitted jobs

If a definition file has been used for the jpqimport command that creates the execution environment for QUEUE jobs and submitted jobs, the definition in the file might be inconsistent with the actual environment. If the file and the environment are inconsistent, output the actual execution environment for QUEUE jobs and submitted jobs, copy the definition to the jpqsetup.conf file, and then back up the file.

To back up the execution environment definition:

  1. Execute the following command to output the definition of the execution environment for QUEUE jobs and submitted jobs.
     
jpqexport -dt isam -co file-name -mh logical-host-name#

    #
    For a physical host, do not specify -mh logical-host-name.

    Cautionary note
    For centralized management, we recommend that you use jpqsetup.conf as the file to be set by the jpqimport command.
    To back up the definition of a logical host, specify the logical host name in the -mh option.

  2. Copy the contents of the output file to jpqsetup.conf.
    The definition of the execution environment for QUEUE jobs and submitted jobs is output to the file specified by file-name in step 1. Copy the contents of the output file to jpqsetup.conf.

(4) Backing up the unit definition

The following describes the tasks required to back up the definition information for a jobnet and calendar. Back up the information for each scheduler service.

Cautionary note
For this backup procedure only, the unit for backup is by scheduler service rather than by logical host. Accordingly, back up the information for each scheduler service separately.
Before starting backup, make sure that the JP1/AJS3 service is running.

For details about how to back up the jobnet definition information, see 4. Backing Up and Restoring Jobnets.

(a) Backing up the definition information for units other than the root job group

Execute the following command to back up the definition information for the units in the scheduler service. The definition information includes the base time, comments, and all other definitions for each unit, but does not include information about the root job group (/), such as the base time, base day, and base month. To back up the root job group information, use the procedures in (b) and (c) below.

To back up the definition of many units, consider splitting the unit definition by job group or jobnet. Execute the following command for each unit you want to back up.

 
ajsprint -F scheduler-service-name -a /unit-name > unit-name_backup.txt

Cautionary note
When you use the ajsprint command to back up the definition information, specify no for the AJSPRINTNETSCHPRF environment setting parameter. For details about this parameter, see 2.2 Setting up the scheduler service environment in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 2.

(b) Backing up the information about the root job group

Record the following information about the root job group:

(c) Backing up the calendar information for the root job group

Execute the following command to back up the calendar information (open days and close days) for the root job group.

 
ajsprint -F scheduler service-name -d / > rootcal.txt

Cautionary note
If no calendar information is output to rootcal.txt, recovery is not needed.

(5) Backing up the JP1/AJS3 Console setup information

When the JP1/AJS3 Console functionality is used, back up the JP1/AJS3 Console setup information by copying it or by using another appropriate method.

Cautionary note
To back up the JP1/AJS3 Console data directory, be sure to stop the JP1/AJS3 Console Manager service first.

(a) In Windows

The following table lists the files you need to back up in Windows.

Table 2-4 JP1/AJS3 Console files to be backed up (in Windows)

File name Description
JP1/AJS3-Console-folder#\database JP1/AJS3 Console data directory
JP1/AJS3-Console-installation-folder\conf\ajs2cm.conf JP1/AJS3 Console Manager environment settings file
JP1/AJS3-Console-installation-folder\conf\ajs2ca.conf JP1/AJS3 Console Agent environment settings file

#
Substitute the following folder for JP1/AJS3-Console-folder:
  • For a physical host
    In Windows Server 2008:
    %ALLUSERSPROFILE%\HITACHI\JP1\JP1_DEFAULT\JP1AJS2
    (The default of %ALLUSERSPROFILE% is system-drive\ProgramData.)
    In Windows Server 2003:
    JP1/AJS3-Console-installation-folder
  • For a logical host
    shared-folder\jp1ajs2cm

(b) In UNIX

The following table lists the files you need to back up in UNIX.

Table 2-5 JP1/AJS3 Console files to be backed up (in UNIX)

File name Description
JP1/AJS3-Console-directory#1/database JP1/AJS3 Console data directory
/etc/opt/jp1ajs2cm/conf/ajs2cm.conf JP1/AJS3 Console Manager environment settings file
/etc/opt/jp1ajs2cm/jajscm_start Script for automatically starting JP1/AJS3 Console Manager#2
/etc/opt/jp1ajs2cm/jajscm_stop Script for automatically stopping JP1/AJS3 Console Manager#2
/etc/opt/jp1ajs2/conf/ajs2ca.conf JP1/AJS3 Console Agent environment settings file
/etc/opt/jp1ajs2/jajsca_start Script for automatically starting JP1/AJS3 Console Agent#2
/etc/opt/jp1ajs2/jajsca_stop Script for automatically stopping JP1/AJS3 Console Agent#2

#1
Substitute the following directory for JP1/AJS3-Console-directory:
  • For a physical host: /var/opt/jp1ajs2cm
  • For a logical host: shared-directory/jp1ajs2cm

#2
Back up the automatic start and stop scripts as required.

[Contents][Back][Next]

[Trademarks]

Copyright (C) 2009, 2010, Hitachi, Ltd.
Copyright (C) 2009, 2010, Hitachi Solutions, Ltd.