2.4.2 Cold starting the agent hosts
If you elect not to cold-start the manager host, stop all scheduler services and ensure that all jobs are stopped on the agent host before performing the backup process. Note that the start conditions cannot be initialized on the agent host if a communication error or other problem prevents a job stop request from reaching the agent host. This can result in inconsistent job execution information between the manager host and agent host.
To avoid introducing inconsistencies into the start conditions or execution information of finished jobs, you need to cold-start the JP1/AJS3 services on the agent hosts.
- Organization of this subsection
(1) Perform full system backup
-
Stop the scheduler service on the manager host.
Execute the ajsstop command with the -n, -s, and -w options specified to stop the scheduler service after all jobnets have finished executing.
For details about the ajsstop command, see ajsstop in 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference.
-
Stop the JP1/AJS3 services.
Stop the JP1/AJS3 services on the manager host and all agent hosts in the system.
-
Perform a full system backup.
-
Start the JP1/AJS3 services.
Start the JP1/AJS3 services on the manager host and all agent hosts in the system.
(2) Perform full system recovery
-
Stop the scheduler service.
Execute the ajsstop command with the -n, -s, and -w options specified to stop the scheduler service after all jobnets have finished executing.
-
Stop the JP1/AJS3 services.
Stop the JP1/AJS3 services on the manager host and all agent hosts# in the system.
-
Restore the full system backup.
-
Cold-start the JP1/AJS3 services on all agent hosts.
Perform a cold start of the JP1/AJS3 services on all agent hosts# in the system.
-
Start the JP1/AJS3 services on the manager host.
- #
-
You do not need to restart the JP1/AJS3 services on agent hosts that are not specified as the execution agent for any jobs.