{"id":31679,"date":"2018-01-17T13:39:00","date_gmt":"2018-01-17T21:39:00","guid":{"rendered":"https:\/\/ephesoft.com\/docs\/2019-1-2\/installing-upgrading\/licensing\/failover-service-and-configuration-tables\/"},"modified":"2020-08-06T14:36:12","modified_gmt":"2020-08-06T21:36:12","slug":"failover-service-and-configuration-tables","status":"publish","type":"docs","link":"https:\/\/ephesoft.com\/docs\/products\/transact\/install-and-upgrade\/system-requirements\/licensing\/additional-resources\/failover-service-and-configuration-tables\/","title":{"rendered":"Failover service and configuration tables"},"content":{"rendered":"
Overview<\/span><\/strong><\/p>\n This document describes the relationship between server_registry, service_status, and failover_service table. These tables hold information and status of all the servers as well as the services running on a standalone server, or on a specific server in a cluster. Ephesoft\u2019s failover mechanism provides high-availability support for services across servers and helps recover servers from crashes. If one of the servers fails, then the failover mechanism initializes another live server in a multi-server environment and starts to provide service through the newly initialized server.<\/p>\n The status of the server can be seen in the server_registry table and services can be seen in the service_status table along with the server ID which is currently assigned for that service. These tables are automatically populated.<\/p>\n <\/p>\n Server_Registry\u00a0\u00a0 –<\/span><\/strong> This table keeps a record of active and inactive servers. This contains details of server whether its clustered environment or standalone server, this will have entries of all the servers. Below is a brief description of columns in this table.<\/p>\n
\n