| Warning |
|---|
Do not attempt this procedure if the systems current state is unknown. Before work can begin, all cluster functions must be checkedvalidated. If any part of the cluser, for example the DRBD Replication on acd-store is not functioning properly, a failover will not might work and a systemwide shutdown will could be the result. Information can be found here: System Health Check |
...
This table describes the systems expected status under fully redundant operation
| VM-Host | machine | Active |
|---|---|---|
| 1 | acd-tel1 | Yes |
| 2 | acd-tel2 | Yes |
| 1 | acd-jb1 | Yes |
| 1 | acd-jb2 | Yes |
| 1 | acd-jb3 | Yes |
| 2 | acd-jb4 | Yes |
| 2 | acd-jb5 | Yes |
| 2 | acd-jb6 | Yes |
| 1 | acd-chat1 | Yes |
| 2 | acd-chat2 | Yes |
| 1 | acd-api1 | Yes |
| 2 | acd-api2 | Yes |
| 1 | acd-dbs1/dbr1 | Yes |
| 2 | acd-dbs2/dbr2 | Yes |
| 1 | acd-dbm1 | Yes |
| 2 | acd-dbm2 | Standby |
| 1 | acd-lb1 | Yes |
| 2 | acd-lb2 | Standby |
| 1 | acd-store1 | Yes |
| 2 | acd-store2 | Standby |
Shutdown
Various steps are required before the virtual machines can be shutdown.
...
If monitoring is installed on your system, schedule a downtime for 2 hours for the machines on VM-Host 2. The downtime for the machines on VM-Host 1 should be set to however long they will be inactive.
If your monitoring server is currently running on VM-Host 1, it has to be moved.
Step 3 - Shutting down all software
...
Checking for active database-sessions on the database master is a precautionary precaution, but necessary step to ensure that all services are stopped and no activity is present on the entire system.
...
Execute the following commands on acd-store2store1:
| Code Block |
|---|
# Set acd-store1 to standby pcs cluster standby acd-store1 # Check if acd-store2 was switched to primary pcs status # Set acd-lb1store1 back to unstandby pcs cluster unstandby acd-lb1store1 # Check if acd-lb2store2 is primary, and acd-lb2store1 is secondary pcs status |
Step 6 - Manual Failover to acd-lb2
...
Execute the following commands on acd-lb1:
| 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 |
...
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 this entire procedure, the configuration will have been be the same.
Configure the status "MAINT" for all machines on VM-Host 1
| Warning |
|---|
When the machine is booted and the HaProxy on acd-lb1 starts again, all "MAINT" statuses will be reset to default . No ,and the status of each machine will be in the status "MAINT"default state. |
Step 8 - Check the AcdGroupDistribute Daemon
...
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 | Steps 1 to N | machine |
|---|
| 1 | 1 | acd-tel1 |
| 1 |
| 2 | acd-jb1 |
| 1 |
| 3 | acd-jb2 |
| 1 |
| 4 | acd-jb3 |
| 1 |
| 5 | acd-chat1 |
| 1 |
| 6 | acd-api1 |
| 1 |
| 7 | acd-dbs1/dbr1 |
| 1 |
| 8 | acd-dbm1 |
| 1 |
| 9 | acd-lb1 |
| 1 |
| 10 | acd-store1 |
Step 10 - Start Software on all machines on VM-Host 2
| 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 |
...
If all tests are successful, the system is now running only on VM Host 2 and fully operational.
Startup
Table
VM-Host 1
...
| Warning |
|---|
These steps are work in progress |
...