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.
-
Backing up the files used in JP1/AJS3
-
Backing up the execution agent information
-
Backing up the execution environment definition for QUEUE jobs and submit jobs (only if QUEUE jobs and submit jobs are used)
-
Backing up the unit definition
-
Backing up the JP1/AJS3 Console setup information (only when the JP1/AJS3 Console functionality is used)
The following describes how to perform these tasks.
- Organization of this subsection
(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.
- #1
-
Substitute the following folder for JP1/AJS3-folder:
-
For a physical host
In Windows Server 2012 or Windows Server 2008, if the installation folder is in the default folder or in a folder protected by the system
%ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2\conf
In Windows Server 2012 or Windows Server 2008, if an installation folder other than the above is used
JP1/AJS3-Manager-installation-folder\conf
In Windows Server 2003:
JP1/AJS3-Manager-installation-folder\conf
The default value for %ALLUSERSPROFILE% is system-drive\ProgramData.
A folder protected by the system is a folder under any of the following:
- system-drive\Windows
- system-drive\Program Files
- system-drive\Program Files (x86) (for 64-bit Windows)
-
For a logical host: shared-folder\jp1ajs2\conf
-
- #2
-
This file exists only if the function is used.
- #3
-
If you use the following files, back up the folder containing these files:
-
Common user profiles
-
Customize files (jajsDisableMenu) that disable menus in windows for JP1/AJS3 - View
-
Executable command settings files (jajsExecutableCommand)
-
- #4
-
If you use a definition file to execute the jpqimport command, back up the execution environment definition for QUEUE jobs and submit jobs described later, and then back up the file.
- #5
-
For profile-storage-folder, substitute the value set for the WaitInfFileOutDir environment setting parameter of the [{JP1_DEFAULT|logical-host-name}\JP1AOMAGENT] definition key. For details about the WaitInfFileOutDir environment setting parameter, see 2.4.2(14) WaitInfFileOutDir in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 2.
The folder and files exist only if JP1/AJS3 - Manager has been set up for sending emails without using Outlook.
(b) In UNIX
The following table lists the JP1/AJS3 - Manager files you need to back up in UNIX.
- #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
-
The backed-up environment settings file for compatibility with JP1/AJS2 - Manager is used only if the configuration of the JP1/AJS3 - Manager to be recovered is a compatible ISAM configuration. This file is not used when the JP1/AJS3 - Manager to be recovered is in the standard configuration.
- #4
-
If you use the following files, back up the directory containing these files:
-
Common user profiles
-
Customize files (jajsDisableMenu) that disable menus in windows for JP1/AJS3 - View
-
Executable command settings files (jajsExecutableCommand)
-
- #5
-
If you use a definition file to execute the jpqimport command, back up the execution environment definition for QUEUE jobs and submit jobs described later, and then back up the file.
- #6
-
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 logical-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 submit jobs
If a definition file has been used for the jpqimport command that creates the execution environment for QUEUE jobs and submit 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 submit jobs, copy the definition to the jpqsetup.conf file, and then back up the file.
To back up the execution environment definition:
-
Execute the following command to output the definition of the execution environment for QUEUE jobs and submit 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.
-
Copy the contents of the output file to jpqsetup.conf.
The definition of the execution environment for QUEUE jobs and submit 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.
-
In Windows:
C:\> ajsprint -F scheduler-service-name -a /* > unitbackup.txt
-
In UNIX:
# ajsprint -F scheduler-service-name -a '/*' > unitbackup.txt
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.2(79) AJSPRINTNETSCHPRF 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:
-
Comments
-
Owners
-
JP1 resource groups
-
Base time
-
Base day
-
Base month
(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.
- #
-
Substitute the following folder for JP1/AJS3-Console-folder:
-
For a physical host
For Windows Server 2012 or Windows Server 2008, if the installation folder is in the default folder or a folder protected by the system:
%ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2CM
The default of %ALLUSERSPROFILE% is system-drive\ProgramData.
A folder protected by the system is the path to a folder in any of the following:
- system-drive\Windows
- system-drive\Program Files
- system-drive\Program Files (x86) (for 64-bit Windows)
For Windows Server 2012 or Windows Server 2008 in which an installation folder other than the above is used:
JP1/AJS3-Console-installation-folder
For 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.
- #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.