3.5.2 Backup and recovery (in Windows)

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 the event database

(1) Backing up JP1/Base setup information

JP1/Base setup information includes:

Definition files
Common definition information
jp1hosts2 information

For each environment in a cluster system, back up the physical hosts, and then the logical hosts.

(a) Definition files

The following table lists the definition files that users set in JP1/Base. Back up these files by copying them or by some other means.

Table 3‒8: JP1/Base files to back up in Windows
File name	Contents
`JP1/Base-folder`^#1`\boot\JP1SVPRM.DAT`	Start sequence definition file
`JP1/Base-folder`^#1`\boot\jp1svprm_wait.dat`	Service starting delay time / timer monitoring period definition file^#2
`JP1/Base-folder`^#1`\jp1bs_env.conf`	JP1/Base environment settings file
`JP1/Base-folder`^#1`\jp1bs_param.conf` `JP1/Base-folder`^#1`\jp1bs_param_V7.conf`	JP1/Base parameter definition file
`JP1/Base-folder`^#1`\jp1bs_spmd.conf`	JP1/Base process management definition file
`JP1/Base-folder`^#1`\jp1bs_service_0700.conf`	Extended startup process definition file
Files in `JP1/Base-folder`^#1`\route\`	Configuration definition file (used by JP1/IM)
`JP1/Base-folder`^#1`\user_acl\JP1_Passwd`	JP1 user definition file
`JP1/Base-folder`^#1`\user_acl\JP1_Group`	JP1 group definition file
`JP1/Base-folder`^#1`\user_acl\JP1_UserLevel`	User permission level file
`JP1/Base-folder`^#1`\user_acl\JP1_AccessLevel`	JP1 resource group definition file
`JP1/Base-folder`^#1`\user_acl\JP1_Accountaccess`	JP1 account access information file
`JP1/Base-folder`^#1`\user_acl\jp1BsUmap.conf`	User mapping definition file
`JP1/Base-folder`^#1`\passwdpolc\jp1bs_passwdpolc.conf`	Password policy definition file
`JP1/Base-folder`^#1`\ds\jp1bs_ds_setup.conf`	Directory server linkage definition file
`installation-folder\conf\event\index`	Event server index file
`event-folder`^#3`\conf`	Event server settings file
`event-folder`^#3`\forward`	Forwarding settings file
`installation-folder\suppress\forward_suppress`	Forwarding settings file for event forwarding suppression
`event-folder`^#3`\[recv_add_extattr \| send_add_extattr]`	Additional extended attribute settings file
`installation-folder\conf\event\api`	API settings file
`installation-folder\conf\event\ntevent.conf`	Action definition file for event log traps
`Any-file`^#4 or `installation-folder\conf\jevlog.conf`^#4	Action definition file for log file trapping
`installation-folder\conf\event\jevlog_start.conf`	Log-file trap startup definition file
`JP1/Base-folder`^#1`\event\jevlogd.conf`	Log information definition file
`event-folder`^#3`\[jev_forward.conf \|` `any-file]`^#5	Distribution definition file (for forward setting file)
`installation-folder\conf\[jev_logtrap.conf \|` `any-file]`^#5	Distribution definition file (for action definition file for log file trapping)
`installation-folder\conf\event\[jev_ntevent.conf \|` `any-file]`^#5	Distribution definition file (for action definition file for event log traps)
`installation-folder\conf\event\[jev_logstart.conf. \|` `any-file]`^#5	Distribution definition file (for action definition file for log file trap startup)
`any-file`	Password definition file (Windows only)
`any-file`	Directory server modification file (Windows only)
`installation-folder\plugin\conf\*.conf`	Adapter command settings file
`JP1/Base-folder`^#1`\jbshc\jbshc.conf`	Health check definition file
`any-file`	Common definition settings file (health check function)
`JP1/Base-folder`^#1`\jp1hosts`	`jp1hosts` definition file
`JP1/Base-folder`^#1`\jp1hosts2.conf`	`jp1hosts2` definition file
`JP1/Base-folder`^#1`\jbsdfts\*.conf`	Service management control definition file
`any-file`	Local action environment variable file
`JP1/Base-folder`^#1`\lcact\jbslcact.conf`	Local action execution definition file
`any-file`	Common definition settings file (local action function)
`JP1/Base-folder`^#1`\physical_ipany.conf`	Communication protocol settings file
`JP1/Base-folder`^#1`\logical_ipany.conf`
`JP1/Base-folder`^#1`\physical_recovery_0651.conf`
`JP1/Base-folder`^#1`\logical_recovery_0651.conf`
`JP1/Base-folder`^#1`\physical_anyany.conf`
`JP1/Base-folder`^#1`\physical_ipip.conf`
`JP1/Base-folder`^#1`\logical_ipip.conf`
`JP1/Base-folder`^#1`\jp1bs_baselog_setup.conf`	Operation log definition file

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

Physical host: installation-folder\conf
Logical host: shared-folder\jp1base\conf

#2: Back up these files if you have enabled settings for delaying or monitoring service startup.

#3: Replace event-folder with the following folder:

Physical host: installation-folder\conf\event\servers\default
Logical host: shared-folder\jp1base\event

#4: 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, no action definition file for log file trapping will exist.

#5: You can create a distribution definition file using the standard file name or a name of your choice. 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.

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. To back up common definition information, execute the following command to acquire only the common definition information for JP1/Base:

jbsgetcnf -c JP1BASE > backup-file

When you run JP1/Base in a cluster system, execute the following command to acquire only the common definition information for JP1/Base:

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

Note that the logical host name must be correctly specified with lower or upper case as specified when the logical host was set up.

Important: When the logical host in question is used in a cluster system, execute the command on the primary node. The backed-up common definition information must be restored on both the primary server and the secondary server.

(c) Backing up jp1hosts2 information

Execute the following command to back up jp1hosts2 information defined in your system.

jbshosts2export > backup-file

If you defined jp1hosts2 information for a logical host, execute the command as follows:

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

For a logical host in a cluster configuration, execute the command on the primary node.

To Page Top

(2) Backing up an event database

There are two modes of backing up event database files:

Backup for data recovery
Backup for error reporting purposes for later reference

(a) Backup for data recovery

To back up the event database files:

Stop all services that use JP1/Base.
Stop JP1/Base.
Copy or otherwise back up the event database files.

Back up the following files:
```
installation-folder\sys\event\servers\default\IMEvent*.*^#
```
or
```
shared-folder\jp1base\event\IMEvent*.*^#
```
#: If a different path is specified in the event server index file (index) as the folder to be used by the event server, back up the files in that path.
Start JP1/Base.
Restart the services that use JP1/Base.

(b) Backup for error reporting purposes for later reference

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 reaches the maximum size (10 megabytes 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.

If the event database is too large (1 GB or greater per file), it takes time to export all events by using the jevexport command. Furthermore, if the output csv file is too large, an attempt to reference it might fail.

The use of an event filter when backing up the event database on a regular basis allows you to back up only those events that occurred after the previous backup.

The following event filter backs up JP1 events that have occurred during the past two days:

B.TIME WITHIN D 2

Shown below is an example of the jevexport command execution result when an event filter file in which the above-mentioned event filter is specified is used. When you specify ON for the -t option, the event filter specified in filter.txt is applied, and the registration times and arrival times of JP1 events are output in Western calendar notation.

jevexport  -t ON  -f filter.txt  -o backup-file

For details about the jevexport command, see jevexport in 15. Commands.

To Page Top

(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:

JP1/Base is successfully installed.
JP1/Base is stopped.
JP1/Base in the logical host environment is set up (for a logical host).
The shared disk is online (for a logical host).

(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.

To recover common definition information on a set-up host, execute the following command to temporarily delete the common definition information for JP1/Base.

Physical host:

jbsunsetcnf -i -h JP1_DEFAULT -c JP1BASE

Logical host:

jbsunsetcnf -i -h logical-host-name -c JP1BASE

Note that the logical host name must be correctly specified with lower or upper case as specified when the logical host was set up.

Execute the following command:

jbssetcnf name-of-backup-file-backed-up-in-(1)(b)

Important: If the logical host in question is used in a cluster system, execute the command on both the primary node and the secondary node. The backed-up common definition information must be restored on both the primary server and the secondary server.

(c) Recovering jp1hosts2 information

If you backed up jp1hosts2 information by following the procedure in (1)(c) jp1hosts2 information, execute the following command to recover the information:

jbshosts2import -r name-of-backup-file-backed-up-in-section-(1)(c)

If you backed up jp1hosts2 information for a logical host, execute the command as follows:

jbshosts2import -h logical-host-name -r name-of-backup-file-backed-up-in-section-(1)-(c)

For a logical host in a cluster environment, execute the command on the primary node.

To Page Top

(4) Recovering the event database

When you recover the event database from a backup, the highest serial number recorded in the database will be the highest number at the time the backup was taken.

Event servers that receive forwarded JP1 events (typically environments where JP1/IM Manager is installed) keep a record of the highest serial number in the event database from which the event was forwarded. The event server uses this information as the basis for a duplication registration check. As long as the serial number of a new JP1 event is greater than the highest on record, the event server considers the event to be original and registers it without conducting any further checks. However, if a lower serial number is reported, the event server searches the database for the same JP1 event to rule out the possibility that the forwarded event is a duplicate. A larger event database means more information to search, which can cause delays when forwarding events and in features that use the event service.

(a) When the forwarding settings file is not configured to forward JP1 events to other hosts

Stop all products that use JP1/Base.
Stop JP1/Base.
Move the backed-up files.

Move the files to the following folder:
```
installation-folder\sys\event\servers\default\^#
```
or
```
shared-folder\jp1base\event\^#
```
#: If you specified a different location to be used by the event server in the event server index file (index), place the files in that location.
Start JP1/Base.
Start the products that use JP1/Base.

(b) When the forwarding settings file is configured to forward JP1 events to other hosts

If the forwarding target is JP1/Base 11-10 or later and the duplication prevention table is in the file format, recover the event database with the following procedure:

Stop all products that use JP1/Base.
Stop JP1/Base.
Move the backed-up files.

Move the files to the following folder:

installation-folder\sys\event\servers\default\^#

or

shared-folder\jp1base\event\^#

#: If you specified a different location to be used by the event server in the event server index file (index), place the files in that location.
Start JP1/Base.
Send a JP1 event for clearing the duplication prevention table (user event) to the forwarding target to clear the maximum value for the source event database serial number of the forwarding source from the forwarding target's duplication prevention table.
```
> jevsendd -i 7FFF8001 -m "DPT CLEAR EVENT" -d target-event-server-name
```
If the forwarding target is a sub manager of JP1/IM - Manager, also send to its higher manager a JP1 event for clearing the duplication prevention table (user event).
Start the products that use JP1/Base.

If the forwarding target is a JP1/Base version earlier than 11-10 or the duplication prevention table is in the memory format, recover the event database with one of the following procedures:

Initialize the event database.

Initialize the event database as described in 10.2.2 Initializing an event database while the event service is stopped. You can view the contents of a backed-up event database by using the jevexport command to output the contents to a CSV file.
Disable duplication registration checking on the event servers specified as forwarding destinations in the forwarding settings file.

Perform the following tasks on the forwarding destination:
1. Stop all products that use JP1/Base.
2. Stop JP1/Base.
3. Add the following line to the event server settings file (conf):
  
  repetition-noncheck-server event-server-to-be-recovered
4. Start JP1/Base.
5. Start the products that use JP1/Base.
Perform the following task on the forwarding source:

Recover the database by following the procedure in (a) When the forwarding settings file is not configured to forward JP1 events to other hosts.

When the forwarding target first receives a forwarded JP1 event, the event service resets the highest serial number recorded for the forwarding source. You can then re-enable duplication registration checking on the destination event server if you choose. Enable duplication registration checking on the target event server and re-create the duplication prevention table by executing the jevdbmkrep command before you start the event server.

To Page Top