使用搜索功能查看 Kepware 的信息库,其中包含 500 多篇知识库文章。缩小搜索结果范围,或在下面的搜索字段中输入您的查询。

或者,如果您无法找到解决方案,我们还有另一个资源:我们的 PTC eSupport Portal。 如果系统提示您登录 eSupport Portal,您可以使用“我的 Kepware”凭据。需要一个“我的 Kepware”帐户吗?在此处创建

搜索解决方案结果:
View All Solutions

Kepware Knowledge Base: Solution


What Are the Differences Between the Cold, Warm, and Hot Redundancy Connection Modes?


Last Update: 2018/11/12

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.

Related Products
RedundancyMaster