Job Management Partner 1/Base User's Guide

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

2.5.3 Backup and recovery (in UNIX)

The following describes the backup and recovery of setup information and event databases in the UNIX version of JP1/Base.

Organization of this subsection
(1) Backing up JP1/Base setup information
(2) Backing up an event database
(3) Recovering JP1/Base setup information
(4) Recovering an event database

(1) Backing up JP1/Base setup information

JP1/Base setup information includes:

In a cluster system, back up physical hosts, and then logical hosts, for each environment.

(a) Definition files

The following table lists the definition files that users set in JP1/Base. You need to back up these files. You can use the tar or cpi command, or a more advanced backup command to back up these files. Choose any backup method.

Table 2-6 JP1/Base files to back up in UNIX

File names Contents
JP1/Base-directory#1/jp1bs_env.conf JP1/Base environment settings file
JP1/Base-directory#1/jp1bs_param.conf
JP1/Base-directory#1/jp1bs_param_V7.conf		 JP1/Base parameter definition file
JP1/Base-directory#1/jp1bs_spmd.conf JP1/Base process management definition file
JP1/Base-directory#1/jp1bs_service_0700.conf Extended startup process definition file
Files in JP1/Base-directory#1/route/ Configuration definition file
(used by JP1/IM)
JP1/Base-directory#1/user_acl/JP1_Passwd JP1 user definition file
JP1/Base-directory#1/user_acl/JP1_Group JP1 group definition file
JP1/Base-directory#1/user_acl/JP1_UserLevel JP1 permission levels definition file
JP1/Base-directory#1/user_acl/JP1_AccessLevel JP1 resource group definition file
JP1/Base-directory#1/user_acl/JP1_Accountaccess JP1 account access information file
JP1/Base-directory#1/user_acl/jp1BsUmap.conf User mapping definition file
JP1/Base-directory#1/evtgw/imevtgw.conf Action definition file for converting SNMP traps
JP1/Base-directory#1/evtgw/snmpfilter.conf Filter file for converting SNMP traps
JP1/Base-directory#1/event/index Event server index file
event-directory#4/conf Event server settings file
event-directory#4/forward Forwarding settings file
JP1/Base-directory#1/event/API API settings file
Any-file#2 or
JP1/Base-directory#1/jevlog.conf		 Action definition file for log file trapping
event-directory#4/[jev_forward.conf | any-file]#3 Distribution definition file (for forward setting file)
JP1/Base-directory#1/[jev_logtrap.conf | any-file]#3 Distribution definition file (for action definition file for log file trapping)
JP1/Base-directory#1/event/[jev_ntevent.conf | any-file]#3 Distribution definition file (for action definition file for event log traps)
/etc/opt/jp1base/conf/user_acl/JP1_UserLevel User permission level file
/opt/jp1base/plugin/conf/*.conf Adapter command settings file
JP1/Base-directory#1/jbshc/jbshc.conf Health check definition file
any-file Common definition settings file (health check function)
JP1/Base-directory#1/jp1hosts jp1hosts definition file
JP1/Base-directory#1/jbsdfts/*.conf Service management control definition file
any-file Local action environment variable file
JP1/Base-directory#1/lcact/jbslcact.conf Local action execution definition file
any-file Common definition settings file (local action function)
JP1/Base-directory#1/physical_ipany.conf Communication protocol settings file
JP1/Base-directory#1/logical_ipany.conf
JP1/Base-directory#1/physical_recovery_0651.conf
JP1/Base-directory#1/logical_recovery_0651.conf
JP1/Base-directory#1/physical_anyany.conf
JP1/Base-directory#1/physical_ipip.conf
JP1/Base-directory#1/logical_ipip.conf
JP1/Base-directory#1/jp1bs_baselog_setup.conf Operation log definition file

#1: Replace JP1/Base-directory with the following directory:

#2: You can assign any name to the action definition file for log file trapping. Remember to back up all the log files you are using. If you are not using the log file trapping function, no action definition file for log file trapping exists.

#3: You can create a distribution definition file using either the default file name or any other name. Remember to back up all the log files you are using. If you are not using the function for collecting and distributing definitions, no distribution definition file will exist.

#4: Replace event-directory with the following directory:

When you run JP1/Base in a cluster system, back up the relevant definition files stored in a directory you specified when setting up JP1/Base for the cluster system.

Note
Backup and recovery do not apply to integrated trace log settings. If you have modified integrated trace log settings, you must reconfigure them when setting up JP1/Base.

(b) Common definition information

In JP1/Base, you must back up common definition information as well as the definition files. This information includes common definition information for JP1/Base, JP1/IM, and JP1/AJS. It is not possible to collect definition information separately for each of these program products.

To back up the common definition file, execute the following command:

jbsgetcnf > backup-file

When you run JP1/Base in a cluster system, execute the following command:

jbsgetcnf -h logical-host-name > backup-file

(2) Backing up an event database

There are two modes of backing up event database files:

(a) Backup for data recovery

To back up the event database files:

  1. Stop all services that use JP1/Base.
  2. Stop JP1/Base.
  3. Copy or otherwise back up the event database files.
    Back up the following files:
    /var/opt/jp1base/sys/event/servers/default/IMEvent*.*#
    or
    shared-directory/event/IMEvent*.*#
    #: If a different path is specified in the event server index file (index) as the directory to be used by the event server, back up the files in that path.
  4. Start JP1/Base.
  5. Restart the services that use JP1/Base.

(b) Backup for error reporting

To back up an event database for error reporting purposes, use the jevexport command to output the database contents to a CSV-format file.

Each event server has two event databases. When one database is full (maximum 10 MB by default), the other event database is swapped in. The existing contents of the swapped-in database are erased. You should regularly check how large the event database has become, and execute the jevexport command before the event databases are swapped over.

(3) Recovering JP1/Base setup information

The following describes recovery for JP1/Base. In a cluster system, recover the physical hosts, and then the logical hosts for each environment.

(a) Recovering definition files

To recover the definition files, restore the backup files in the original locations. Make sure that the following conditions are satisfied before you start:

(b) Recovering the common definition information

To recover common definition information, you also need to restore the backup of common definition information in addition to the definition files described above.

Execute the following command:

jbssetcnf backup-file-name

For backup-file-name, specify the backup file generated by the jbsgetcnf command.

(4) Recovering an event database

The following conditions apply for successful recovery of backed-up event database files:

To recover the event database files:

  1. Stop all services that use JP1/Base.
  2. Stop JP1/Base.
  3. Move the backed-up files.
    Place the files in this directory:
    /var/opt/jp1base/sys/event/servers/default/#
    or
    shared-directory/event/#
    #: If a different path is specified in the event server index file (index) as the directory to be used by the event server, place the files in that path.
  4. Start JP1/Base.
  5. Restart the services that use JP1/Base.

[Contents][Back][Next]

[Trademarks]

All Rights Reserved. Copyright (C) 2009, Hitachi, Ltd.