Both servers in this example are powered separately, ensuring that if one fails, the other can continue processing without interruption. This comprehensive approach provides failover protection for hardware and software from the client tier to back-end data stores. If a process fails, Precision Failover automatically stops and restarts it. This failover policy allows developers to implement a high availability strategy at the most basic levels without complete system shutdown. Tranlogs contain compressed representations of committed state-change, which are designed to be replayed in the case of failure.
Extents store persistent and state data in their native object format.
This is a normal configuration setting, enabling the system to minimize the size of individual tranlogs and reduce recovery time. If the primary machine in the cluster fails, a secondary is given control of the extent and tranlog files and takes over as the primary. The following is an overview of the system failover process. VCS detects a non-recoverable failure of one of the components of the primary machine, machine A. VCS orders an agent to shut down any remaining processes running on machine A, if it is still running. The Web servers automatically re-connect to these servlet engines when they become available.