5.3 Redundancy
This section discusses redundancy in JP1/AJS3. In addition to backing up the system, duplicating part of the system is another effective way of preparing for unexpected situations. Should a failure occur, a redundant system can be restored to normal operation with less trouble. JP1/AJS3 supports software redundancy (in a cluster system) and hardware redundancy (database and network).
The following figure shows an example of a JP1/AJS3 system with a partially redundant configuration. Consider implementing redundancy as required.
|
|
![[Figure]](GRAPHICS/ZH050001.GIF)
- Software redundancy
-
JP1/AJS3 supports cluster systems. A cluster system consists of a number of linked servers that operate as a single system, so that work tasks can continue processing should a failure occur.
For details about cluster systems, see the documentation for your OS and cluster software. For the processing flow when JP1/AJS3 is used in a cluster configuration, see 10. Operation in a Cluster System in the JP1/Automatic Job Management System 3 Administration Guide.
- Database redundancy
-
JP1/AJS3 uses a database to manage work task definitions and execution results. Consider implementing redundancy through the hard disk functionality. For example, you could implement database redundancy by configuring the hard disks into a RAID array.
- Network redundancy
-
JP1/AJS3 supports multi-LAN configurations: JP1/AJS3 - Manager, JP1/AJS3 - Agent, or JP1/AJS3 - View is installed on a host that has multiple NICs, and the host is connected to multiple LANs.
The communication settings for JP1/AJS3 are based on those for JP1/Base. For details about the communication settings for JP1/Base, see the JP1/Base communication protocol and explanation of how to set up JP1/Base communication according to the network configuration in the JP1/Base User's Guide.