HA server switch-over after a failure event

Last Updated : Apr 04, 2024 |
Prolog information
Metadata
Keywords:
For customers who require continuous access to their CMS data, HA systems allow for the redirection of LAN traffic related to CMS clients and peripheral devices from the primary server to the secondary server. Switch-over from the primary server to the secondary server can be performed when the primary server experiences a major failure event. However, an HA switch-over should be performed only when the anticipated down time for the primary server is expected to be significant.
Each call center network is configured according to its own unique specifications. Therefore, each HA customer must develop their own customized criteria and plans for server switch-over events.
The CMS HA option allows the following server switch-over options:
  • No switch-over
    If you do not require continuous access to your CMS data, you can elect not to switch-over to the secondary server after the primary server experiences a major failure event. When the primary server goes down, uninterrupted collection of call data will continue on the secondary server, but you may not be able to access that data until the primary server is restored.
  • Manual server switch-over
    If you require uninterrupted access to CMS data, server switch-over can be performed manually.
    At a minimum, manual switch-over entails the individual editing of CMS supervisor clients by their individual users in order to redirect them from the primary to the secondary server. Also, if the primary server is connected to one or more NTS servers, significant effort may be required to manually switch the NTS devices over to the secondary server. For more information about manual server switch-overs, see What to do if CMS server fails.