Under normal system conditions, the Hot Standby server operates as a secondary server, with Prinergy configuration files being copied over regularly. When failover occurs, the Hot Standby server takes over as the primary server.
The following Prinergy files are copied regularly from the Prinergy primary server to the Hot Standby server:
- The Oracle database is replicated continuously in real time. The Double-Take software performs the replication.
The databases are fully available when the system is put into Hot Standby failover mode.
- Configuration files are copied once daily, including process templates, the Prinergy license key, standard colors and fonts, and Business Link customer and process mapping files (if Business Link software is installed). The Prinergy software performs the replication.
While the Hot Standby server is operating as a Prinergy secondary server, any Prinergy component that it does not need for operation as a secondary, such as the Oracle database, is ignored.
When you switch the Hot Standby server to failover mode, the Hot Standby server takes over as the primary server and takes over the processing of jobs, at a slightly reduced capacity. If a Kodak InSite Prepress Portal and/or Creative Workflow server is connected to the Prinergy primary server, you can also redirect it to the Hot Standby server.
When to initiate failover
The decision to initiate a Hot Standby failover depends on the urgency of the situation. Typically, you switch to failover mode to ensure that jobs continue to move through production—for example, if a plate must be remade for a job on the press.
It is a also good idea to initiate a failover for periodic testing of the Hot Standby system. By simulating a failover, you learn what to expect in failover mode and you ensure that the system continues to operate properly.