System Continuity is a core feature available for non-Legacy Customer Accounts where the Cloud-located Customer Database is synchronized to the on-site Cloud Node and then the Cloud Node goes offline. This allows the associated Cloud Nodes and Red-series Controllers to function without interruption for a configured timeframe. The behavior present during System Continuity mode varies depending on whether it is a Controller or Cloud Node.
- If a Red-series Controller loses connection with the associated Cloud Node, the Controller will function normally until the Ecard Fall-back time is exceeded. Once the Ecard fall-back timeframe has been exceeded, the local database will be disabled until the Controller connects to the Cloud Node.
- If a Cloud Node loses connection with PDK.io, the Cloud Node and connected Controllers will function normally until the Ecard Fall-back time is exceeded. Once the Ecard fall-back timeframe has been exceeded, the local database on the Cloud Node will be disabled until the Cloud Node connects to PDK.io again.
While the Cloud Node is operating in System Continuity, any changes made in PDK.io will not be synced until the Cloud Node and associated Red-Series Controllers are online again.
For more information regarding configuring System Continuity on a Customer Account, click here.
Comments
0 comments
Please sign in to leave a comment.