5.2.5 Backing up and recovering an embedded database by using the backup enhancement function

(1) Characteristics of backup and recovery by using the backup enhancement function

In an environment in which the backup enhancement function is enabled, you can back up the embedded database while JP1/AJS3 is running.

The recovery process can restore the registered execution-schedule information, the execution statuses, the execution results of jobs and jobnets, and the values of parameters that change with each job execution (macro valuables and passing information), in addition to the definitions of units, schedules, and calendars. Because there is no need to register jobnets for execution after recovery, the time required for recovery after a failure can be reduced.

After the embedded database recovers, the scheduler service that runs on the recovered embedded database automatically starts in disaster recovery mode, when you next start the scheduler services. This means that the scheduler service starts with job execution suppressed, and the statuses of jobs and jobnets are changed. If job execution is suppressed, you can use JP1/AJS3 - View or a command to check the status of each job, and then change the statuses of jobs or rerun jobs as needed. For details about the statuses of jobnets and jobs when the start mode is disaster recovery, see the description about the disaster-recovery start in 6.2.1(3) Jobnet and job statuses for each start mode in the JP1/Automatic Job Management System 3 Administration Guide.

Cautionary notes

• Execution result details and temporary changes cannot be recovered.

• Note that, in an environment in which the backup enhancement function is used, the amount of data to be stored in the embedded database increases compared to an environment in which the backup enhancement function is not used because information required for recovery is stored in the embedded database. For this reason, the performance of processing accompanied by update of the embedded database such as job execution and registration for execution will decline. If the system requires the JP1/AJS3's processing performance, verify the performance in an actual environment before considering the use of the backup enhancement function.

To Page Top

(2) Target of backup and recovery

The backup enhancement function backs up and recovers all data stored in the embedded database. Data not stored in the embedded database, such as JP1/AJS3 environment setting information, is not backed up. When using the backup enhancement function, consider how to back up data that is not stored in the embedded database, for example, by backing up the entire system or backing up individual data items as needed.

To Page Top

(3) Settings for using the backup enhancement function

To use the backup enhancement function, you need to enable this function when setting up the embedded database. For details about how to do this, see 21.6 Settings for backing up and recovering an embedded database while JP1/AJS3 is running in the JP1/Automatic Job Management System 3 Configuration Guide.

You can enable or disable the backup enhancement function for each embedded database. When you set up multiple scheduler services on the same embedded database, make sure that the function is enabled or disabled identically for the embedded database and all of its scheduler services.

The following figure shows a configuration that can be used to enable the backup enhancement function and a configuration that cannot be used.

To Page Top

(4) Backup and recovery by using the backup enhancement function

To back up and recover an embedded database by using the backup enhancement function, use the jajs_dbbackup and jajs_dbrestore commands. For details about how to back up and restore, see 2.5 Backing up and recovering JP1/AJS3 - Manager by using the backup enhancement function in the JP1/Automatic Job Management System 3 Administration Guide.

To Page Top

(5) Considerations before using the backup enhancement function

Consider the following before you use the backup enhancement function:

• Job operation on the embedded database to be backed up stops during backup processing. Determine the backup intervals and when to perform backup, considering the operation status of JP1/AJS3 jobs. For the standard time required for backup, see (6) Standard time required for backup.

• During backup processing, the following operations on the embedded database to be backed up and the scheduler services that run on that embedded database are suspended until backup processing ends. Therefore, determine the backup intervals and when to perform backup, considering the operation status of JP1/AJS3. For the standard time required for backup, see (6) Standard time required for backup.

  • Starting a scheduler service

  • Executing a command that operates a unit defined in the scheduler service

  • Performing operations on a scheduler service from JP1/AJS3 - View

  • Executing a command that operates the embedded database

  • Executing a remote jobnet defined in a scheduler service (executive host)

  • Executing a remote jobnet defined in a scheduler service (execution target host)

  • Performing operations on a scheduler service from JP1/AJS3 - Web Console

  • Adding, deleting, or changing an execution agent or an execution agent group^#

  #

  If the agent management database is stored in the embedded database to be backed up.

• The backup enhancement function creates a backup of an embedded database. When you operate JP1/AJS3 in a configuration containing multiple embedded databases, specify whether to create a backup for each embedded database. Then, determine the backup intervals and when to perform backup.

• The disk must have sufficient free space to accommodate the embedded database to be backed up. For an estimate of the disk space required for backup, see jajs_dbbackup in 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference.

• The backup data can be recovered in an embedded database environment for which the following items match those of the environment in which the backup data was created:

  • The version of JP1/AJS3 - Manager

  • The version of the embedded database

  • 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

• Consider the procedure for recovering an environment in which the preceding items match that of the environment in which the backup data was created. For example, back up the entire system. For details about how to check each item, see 2.5.2(3) Obtaining information about the backup environment in the JP1/Automatic Job Management System 3 Administration Guide.

• You cannot use the backup enhancement function together with unload log files for the embedded database. For details about the unload log files for the embedded database, see F.1 Overview of database backups.

• If the backup enhancement function is enabled, you can no longer use the ajsembdbbackup and ajsembdbrstr commands. For details about ajsembdbbackup command, see ajsembdbbackup in 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference. For details about ajsembdbrstr command, see ajsembdbrstr in 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference.

• Operation with the unregistration mode set as asynchronous is highly recommended. When JP1/AJS3 is initially installed and set up, you do not need to change the unregistration mode because it is set to asynchronous. However, if JP1/AJS3 is installed as an upgrade installation, unregistration mode might be set to synchronous. For details about the unregistration mode, see 6.1.7 Changing the mode in which unregistration or generation management deletes the generations of a jobnet in the JP1/Automatic Job Management System 3 Configuration Guide and 15.1.7 Changing the mode in which unregistration or generation management deletes the generations of a jobnet in the JP1/Automatic Job Management System 3 Configuration Guide. In an environment where the backup enhancement function is enabled, there might be more impact on cancel registration time due to the increase in information stored in the database.

• If the backup enhancement function is enabled, you can no longer use the procedures described in 6.1.7(1)(b) When registration information for the jobnet that was being executed is necessary in the JP1/Automatic Job Management System 3 Configuration Guide and 15.1.7(1)(b) When registration information for the jobnet that was being executed is necessary in the JP1/Automatic Job Management System 3 Configuration Guide. Therefore, to change the unregistration mode from synchronous to asynchronous in an environment in which the backup enhancement function is enabled, you need to perform a cold start. If you want to enable the backup enhancement function, also consider operating the system by setting the unregistration mode to asynchronous.

• If you enable the backup enhancement function, you will need to make a new estimate regarding resources that are used. Make an estimate regarding the following items.

  • Memory requirements, disk capacity, kernel parameters

    For the estimates about memory requirements, disk capacity and kernel parameters, see 3.2 Estimating system performance.

  • Database area

    For the estimate about the database area, see 3.3 Estimating the database area.

  • Size-of-pool-used-for-locking

    For the estimate about the size of pool used for locking, see 23.1.1 Examining the embedded-database operating environment and operating method in the JP1/Automatic Job Management System 3 Configuration Guide.

• If the backup enhancement function is enabled, in addition to the information stored in the existing database, the values of parameters that change with each job execution (macro valuables and passing information) are stored in the new table area (AJS2DATA2) in the database. The size of these information stored in the database varies depending on the job execution results. Therefore, consider daily monitoring the utilization of the new table area (AJS2DATA2). The usage of the table area can be checked with the ajsembdbstatus command.

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

  The utilization of the table area can be calculated by the following formula:

  (Total Segment - Unused Segment) / (Total Segment) x 100

  If the utilization of the table area exceeds 60%, consider the following measures.

  • Perform maintenance of the embedded database

    If the maintenance is not performed regularly, the table area may be inefficient. For details, see 6.1.2 Considering maintenance methods.

  • Re-estimate and expand the database area

    Re-estimate the size of the required database area and, if necessary, expand the database area with the ajsembdbaddarea command. For details about ajsembdbaddarea command, see ajsembdbaddarea in 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference.

To Page Top

(6) Standard time required for backup

The time required for backup by using the backup enhancement function depends on the size of the data area used by the embedded database, operation status of JP1/AJS3, and disk performance of the environment where JP1/AJS3 is installed. Therefore, when you estimate the precise time required for backup, actually create a backup. To confirm the precise time required for backup, actually create a backup and then check the backup information file that shows the time it took for backup. For details about the backup information file, see jajs_dbbackup in 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference.

To Page Top