5.2.2 Target files and backup timing

Perform a backup whenever changes are made to the settings information needed to run JP1/AJS3. If performing a full backup every time is likely to be time consuming, you can back up only the information that was changed during operation or back up only the data of the embedded database. 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‒4: Essential settings for JP1/AJS3 operation
Type of information	Settings to back up
JP1/Base settings information	See the JP1/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
	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
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

#1: Windows only.
#2: UNIX only.

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. Consider backing up this type of information on a regular basis, such as once per day.

Typical backup plans are as follows.

Example of a backup plan at the development phase:

Back up the operating environment information, such as the environment setting parameters and files used in JP1/AJS3, when such information is changed.
Back up data in the embedded database once a week.
Back up all settings once a month.
Back up the entire system when the system configuration is changed.

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

Back up the operating environment information, such as the environment setting parameters and files used in JP1/AJS3, when such information is changed.
Back up data in the embedded database every day.
Back up all settings once a month.
Back up the entire system when the system configuration is changed.

Supplementary note

You can back up the information about the scheduler database and agent management database by backing up the embedded database. See 5.2.1(5) Backing up and restoring an embedded database and consider the backup and recovery method.

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 JP1/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 JP1/Automatic Job Management System 3 Administration Guide.

To Page Top