The following table lists the recovery mechanism for different failure types:
|
Failure type
|
Recovery mechanism
|
Notes
|
Example
|
|
Process Failure
|
Automatic
|
-
|
GigaSpaces PU failure, WebSphere process failure, and Nginx process failure
|
|
Virtual Machine Failure
|
Manual
|
If an Avaya Breeze® platform node in an Avaya Workspaces for Call Center Elite cluster becomes faulty or is shut down for testing, you must reboot all nodes in the cluster after the recovery of the node.
The reboot is mandatory to:
Rebooting all nodes in the cluster causes an outage of Avaya Workspaces for Call Center Elite. Therefore, you must plan the reboot during a maintenance window.
|
Accidental shutdown
|
|
Physical Server Failure
|
Automatic
|
After you clear the fault and restart the physical server and virtual machines.
|
Power failure on a physical server
|
|
Network Failure
|
Manual
|
Recommission the physical server or the virtual machine.
Note:
-
For agents with active interactions, you must reboot all clusters.
-
For an active agent and network failure on an active UAC node, you must reboot UAC cluster.
-
After recommission, the agents must refresh the page and re-login if required.
|
Accidental disconnection of all network cards of a physical server
|
With the Avaya Workspaces for Call Center Elite Release 3.8, you do not need to restart all the Avaya Workspaces for Call Center Elite clusters if you have to restart an individual cluster. If you want to restart Unified Agent Controller (UAC) cluster, the agents must not have any contacts. If the agents are having contacts and you restart UAC cluster, then you must restart the clusters in the following order:
-
Core cluster
-
UAC cluster
