【everRun's Continuous Operation Mechanism】 The two IA servers with everRun installed are always synchronized in data and memory through the state point feature, and the network is set up with active-standby redundancy. Virtualization software is integrated, allowing applications to run on the guest OS within virtual machines. In the event of a server failure, the system automatically detects the failure, isolates the affected area, and continues processing on the other server. Since there is no failover of the virtual machine during this process, there is no impact on the OS or running applications, thus avoiding time lags and data loss. Maintenance can be performed on the failed server without stopping the system, achieving continuous operation of the system.

Differences in Redundancy Levels The everRun virtual machines have two availability modes: FT mode (non-stop type) and HA mode (high availability, failover type), which differ in the level of redundancy between two physical servers.

"Differences Between General HA Cluster Systems and everRun" ★ Standby Method - In the case of cold standby, it is necessary to switch the line, power on the standby side, start up, and confirm the operational status after startup. - In the case of hot standby, it is necessary to switch line addresses and confirm the operation of applications. ★ HA Cluster Configuration Initially, the introduction and configuration of shared disks are required, followed by cluster configuration and verification. Knowledge and skills in both areas are necessary. ★ Use of Shared Virtual Disks Both cluster and virtual shared disk technologies and knowledge are required, and operations will be conducted at each respective layer. ★ Fault-Tolerant Products Fault Tolerance (FT), unlike other availability technologies mentioned earlier, is designed not to minimize downtime but to achieve continuous availability and uninterrupted operation.