| Warning |
|---|
Before work can begin, all cluster functions must be checked. If any part of the cluser, for example the DRBD Replication on acd-store is not functioning properly, a failover will not work and a systemwide shutdown will be the result. Information can be found here: System Health Check |
Introduction
A controlled fail-over might be required when one or more VM-Hosts in the cluster must be taken down for maintenance.
...
| Warning |
|---|
Only continue when no sessions are active |
Step 5 - Manual Failover to acd-store2
To execute a manual failover, the pcs cluster node acd-store1 is temporarily set into standby, which will cause acd-store2 to become the primary node. After acd-store2 is primary, an unstandby command is executed. After this, acd-store2 will be the primary node and acd-store1 will be secondary.
Execute the following commands on acd-store2
| Code Block |
|---|
# Set acd-store1 to standby pcs cluster standby acd-store1 # Check if acd-store2 was switched to primary pcs status # Set acd-lb1 back to unstandby pcs cluster unstandby acd-lb1 # Check if acd-lb2 is primary, and acd-lb2 is secondary pcs status |
Step 6 - Manual Failover to acd-lb2
To execute a manual failover, the pcs cluster node acd-lb1 is temporarily set into standby, which will cause acd-lb2 to become the primary node. After acd-lb2 is primary, an unstandby command is executed. After this, acd-lb2 will be the primary node and acd-lb1 will be secondary.
...
| Code Block |
|---|
# Set acd-lb1 to standby pcs cluster standby acd-lb1 # Check if acd-lb2 was switched to primary pcs status # Set acd-lb1 back to unstandby pcs cluster unstandby acd-lb1 # Check if acd-lb2 is primary, and acd-lb2 is secondary pcs status |
Step 6 7 - Configure HaProxy
Access the HaProxy admin page for both acd-lb1 and acd-lb2. The primarily important machine to configure is acd-lb2, but in case a fail-over happens during the entire procedure, the configuration will have been the same.
...
| Warning |
|---|
When the machine is booted and the HaProxy on acd-lb1 starts again, all "MAINT" statuses will be reset to default. No machine will be in the status "MAINT". |
Step 7 8 - Check the AcdGroupDistribute Daemon
If the Daemon AcdGroupDistribute.r5 is running on acd-tel1, it must be started on acd-tel2 to ensure that calls to acd-groups will still be routed by the routing-algorithm.
Step 8 9 - Shutdown the virtual machines on VM-Host 1
The correct order in which to shutdown must still be maintained. The following table displays the order
First shutdown acd-tel1, acd-jb1-3 as well as acd-chat1 and acd-api1 in no particular order. You do not have to wait until acd-tel1, acd-jb1-3 as well as acd-chat1 and acd-api1 are down before shutting acd-dbs1/dbr1 down. Wait until acd-dbs1/dbr1 is down until shutting acd-dbm1 down. Wait until acd-dbm1 is down before shutting down acd-lb1. Wait until acd-lb1 is down before shutting down acd-store1
| VM-Host | machine | Active |
|---|---|---|
| 1 | acd-tel1 | Yes |
| 1 | acd-jb1 | Yes |
| 1 | acd-jb2 | Yes |
| 1 | acd-jb3 | Yes |
| 1 | acd-chat1 | Yes |
| 1 | acd-api1 | Yes |
| 1 | acd-dbs1/dbr1 | Yes |
| 1 | acd-dbm1 | Yes |
| 1 | acd-lb1 | Yes |
| 1 | acd-store1 | Yes |
Step 9 10 - Start Software
| Machine(s) | Start what | It is installed if you are using | How to stop |
|---|---|---|---|
| acd-tel2 | 8-Server | ACD / IVR | Explorer to shell:startup - start the link to startup_launcher.cmd For service installations, start the robot5 service. |
| Platform UDP Listener | ACD / IVR | Explorer to shell:startup - start the link to startListener.bat For service installations, start the jtel Platform UDP Listener service. | |
| Presence Aggregator | A PBX or presence connector which uses the presence aggregator:
| Explorer to shell:startup - start the link to start-presence-aggregator.cmd For service installations, start the jtel Presence Aggregator service. | |
| Telephony Connector | A PBX which uses a custom connector:
| Explorer to shell:startup - start the link to JTELInnovaphonePBXService.exe or jtelTAPIMonitorService.exe For service installations, start the service, for example the jtel TAPI service or jtel Innovaphone Service. | |
| Exchange Connector | E-Mail with an Exchange or Office 365 Server | Start the jtelEWSMailService service. | |
| IMAP Connector | E-Mail with an IMAP(S) Server | Start the jtelIMAPMailService service. | |
| acd-jb4-6 | Wildfly | Anything | sudo systemctl start wildfly For installations not using systemctl: sudo service wildfly start |
| acd-chat2 | Chat Server | CHAT | sudo systemctl start jtel-clientmessenger For installations not using systemctl: sudo service jtel-clientmessenger start |
| acd-api2 | REST API | REST | sudo systemctl start jtelrest For installations not using systemctl: sudo service jtelrest start |
| acd-dbm2 | Platform UDP Listener | SOAP | sudo systemctl start jtel-listener For installations not using systemctl: sudo service jtel-listener start |
Step 10 11 - Ensure system functionality
Information can be found here: System Health Check
If all tests are successful, the system is now running only on VM Host 2 and fully operational.
...