Use the search feature to view Kepware's repository of more than 500 Knowledge Base articles. Narrow your results or type your query into the search field below.

Alternatively, if you are unable to find a solution, we have an additional resource - our PTC eSupport Portal . If you are prompted to log into the eSupport Portal, you can use your My Kepware credentials. Need a My Kepware account? Create one here .

Descriptions of the redundancy connection modes are as follows:

• Cold: In this mode, the application will only connect to one underlying server at a time. A connection to the primary server will be made at startup and all client-related requests will be forwarded onto the primary. In the event that the connection to the primary server fails (or communications are lost), a connection will be made to the secondary server.
• Warm: In this mode, the application will attempt to maintain a connection to both the primary and secondary server at all times. The application will initialize data callbacks for the primary server on startup. In the event that the connection to the primary server fails (or communications are lost), a data callback will be initialized for the secondary server.
• Hot: In this mode, the application will attempt to maintain a connection to both the primary and secondary server at all times. The application will initialize data callbacks for both primary and secondary servers on startup so that both servers will send data change notifications. The data received from the primary will be forwarded onto the client. In the event that the connection to the primary server fails (or communications are lost), the data received for the secondary server will immediately be forwarded onto the client.

Note: For more information, refer to RedundancyMaster's Connection Mode.