5.2.2 Target files and backup timing

Perform a backup whenever changes are made to the settings information needed to run JP1/AJS3. In cases where it would be time-consuming to perform a full backup every time, you can back up just the information that was changed. Consider also whether a full backup should be performed periodically in case a user forgets to take backup after changing a setting.

The following table lists the settings information needed for running JP1/AJS3.

Table 5‒3: Essential settings for JP1/AJS3 operation

Type of information	Settings to back up
JP1/Base settings information	See the Job Management Partner 1/Base User's Guide.
JP1/AJS3 - Manager settings information	Files used by JP1/AJS3
	Execution agent information
	Execution environment definitions for QUEUE jobs and submit jobs
	Definitions of units other than root job groups
	Root job group information
	Calendar information for root job groups
	JP1/AJS3 Console settings information
	Registered execution-schedule for root jobnets
JP1/AJS3 - Agent settings information	Files used by JP1/AJS3
JP1/AJS3 - View settings information	Environment settings files
	Custom job icons
	Icon image folder
	Icon image files and background image files for JP1/AJS3 - Console View
Other settings information	Service account#1
	Login scriopt#2
	Adjustment values for kernel parameters#2
	Command for collecting data for troubleshooting
	Cluster support tools
	User-created tools for linking to a mail system#2

The settings needed to run JP1/AJS3 consist of both fixed information, such as information about the operating environment, and information that is frequently updated, such as jobnet definitions entered when configuring the system. Fixed information can be backed up whenever it is changed, but it would be unrealistic to back up information that is continually updated after every update. Plan to back up this type of variable information once per day.

Typical backup plans are as follows.

Example of a backup plan at the development phase:

• Back up jobnet definitions every day.

• Back up information other than jobnet definitions when a setting is changed.

• Back up all settings once a month.

Example of a backup plan when JP1/AJS3 is operational:

• Back up the changed information when a setting is changed.

• Back up jobnet definitions once a week.

• Back up all settings once a month.

For the backup tasks you need to perform in each program (JP1/Base, JP1/AJS3 - Manager, JP1/AJS3 - Agent, and JP1/AJS3 - View), see 2.2 Backing up the setup information for a system that uses JP1/AJS3 in the Job Management Partner 1/Automatic Job Management System 3 Administration Guide. For the necessary recovery tasks, see 2.3 Restoring the setup information for a system that uses JP1/AJS3 in the Job Management Partner 1/Automatic Job Management System 3 Administration Guide.

Supplementary note

You can back up and restore the scheduler database using the embedded database functionality. Consider the backup and recovery methods described in 5.4.1 Overview of database backups.

To Page Top