Overview
The Recovery Kit for JP1/AJS protects three JP1 products: JP1/Base, JP1/AJS3 – Manager, and JP1/AJS3 – Agent. Since the protection process flow is the same for these products despite differences in the commands used, this document explains them collectively.
Additionally, several processes are used internally across these operations. These are referred to as “JP1 Start Process,” “JP1 Stop Process,” “JP1 Status Check Process,” and “JP1 Process Termination Process.” Details for each process can be found in the section “About JP1/Base and JP1/AJS3 Process Operations” at the end of this page.
Bringing a Resource In Service (restore)
The JP1/AJS resource hierarchy is started in the following order:
- Set the timeout for Bringing a Resource In Service. The value of the Restore Timeout property is used.
- Execute JP1 status checking. If all related processes are already started, the process will terminate normally.
- If the state is incomplete (e.g., some related processes are not started), the JP1 termination process is called to terminate all running JP1 processes (only those associated with the logical host of the specified resource).
- If the call to the JP1 termination process fails, it terminates abnormally.
- If the call to the JP1 termination process succeeds, the JP1 Status Check is executed.
- If any JP1 processes were not completely terminated, it terminates abnormally.
- Execute JP1 restore processing.
- Execute JP1 Status Check.
- If it starts successfully, the process exits normally.
- If some processes were not started, it waits for the number of seconds set in the property’s retry interval, then returns to step 5 and repeats the process.
- If the JP1 Status Check process returns an error, execute the steps described in the [Error Handling] section.
- If the timeout set in step 1 occurs during the repeat process, execute the steps described in the [Error Handling] section.
[Error Handling]
- Resets the timeout. The value specified in the “Forced Termination Timeout” property is used for this setting.
- Executes the JP1 termination process. The overall operation will terminate abnormally regardless of the success or failure of this process.
Taking a Resource Out of Service (remove)
The Kit attempts to stop the JP1/AJS resource hierarchy in the following order:
- Set the timeout for the stop operation. The value from the “Remove Timeout” property is used.
- Execute JP1 Status Check. If all processes have already stopped, the operation exits normally.
- Execute JP1 remove processing. If this fails, the operation terminates abnormally.
- Execute JP1 Status Check.
- If all related processes have stopped, the operation exits normally.
- If some processes are still running, the system waits for the number of seconds specified in the “Retry Interval” property, then returns to step 4 to repeat the check.
- If JP1 Status Check returns an error, execute the steps described in the [Error Handling] section.
- If a timeout occurs during the repeat process, execute the steps described in the [Error Handling] section.
[Error Handling]
- Execute JP1 Process remove processing. The execution result of this process is not evaluated.
- Execute JP1 Status Check. If the processes have stopped, the operation exits normally. Otherwise, it terminates abnormally.
Monitoring (quickCheck)
Monitor the JP1/AJS resource hierarchy in the following order.
- Set Monitoring process timeout. The value of the QuickCheck Timeout property is used.
- Execute JP1 Status Check. If it has started normally, Monitoring will terminate normally.
- If an abnormality is detected or a timeout occurs, Monitoring will terminate abnormally.
Recovery (recover)
Only if the monitoring process terminates abnormally, the RK attempts to start the JP1/AJS resource using the same procedure as the restore operation.
Process Operations for JP1/Base and JP1/AJS3
As previously mentioned, this section describes the internal processes used within each resource operation. These processes are executed by running commands that specify a logical hostname. Note that the commands used differ between JP1/Base and JP1/AJS3. For detailed information on each command, refer to the JP1 documentation.
JP1 Startup Process
| Resource Component | Command to execute |
|---|---|
| JP1/Base | /etc/opt/jp1base/jbs_start.cluster [LogicalHostName] |
| JP1/AJS3 – Manager JP1/AJS3 – Agent |
/etc/opt/jp1ajs2/jajs_start.cluster [LogicalHostName] -HA |
JP1 Stop Process
| Resource Component | Command to execute |
|---|---|
| JP1/Base | /etc/opt/jp1base/jbs_stop.cluster [LogicalHostName] |
| JP1/AJS3 – Manager JP1/AJS3 – Agent |
/etc/opt/jp1ajs2/jajs_stop.cluster [LogicalHostName] |
JP1 Status Check Process
| Resource Component | Command to execute |
|---|---|
| JP1/Base | /opt/jp1base/bin/jbs_spmd_status -h [LogicalHostName]
/opt/jp1base/bin/jevstat [LogicalHostName] |
| JP1/AJS3 – Manager JP1/AJS3 – Agent |
/opt/jp1ajs2/bin/jajs_spmd_status -h [LogicalHostName] |
JP1 Kill Process
| Resource Component | Command to execute |
|---|---|
| JP1/Base | /etc/opt/jp1base/jbs_killall.cluster [LogicalHostName] |
| JP1/AJS3 – Manager JP1/AJS3 – Agent |
/etc/opt/jp1ajs2/jajs_killall.cluster [LogicalHostName] |



Post your comment on this topic.