In this chapter we will explain the ThinMan Primary and Secondary Server with Dual Database (FULL redundant configuration) software update procedure.
Due to replication both ThinMan Server as well ThinMan database, this ThinMan operation mode assure user business continuity even during the ThinMan Server software Update.
The guideline that inspire this procedure is to use the ThinMan Secondary Server and its related Slave Database instance in order to supply the client with ThinMan standard service while the Primary ThinMan Server and its relate master database instance are upgrading.
Once this first upgrade step is completed and both the ThinMan Primary server as well its related Master database instance are restarted, they will proceed with ThinMan Secondary server shutdown and upgrade, as now the just updated ThinMan Primary server and master database will take in charge the clients.
ThinMan Backup before update
Before update the ThinMan current version we suggest to perform a complete backup both of ThinMan Server and its database. Refer to your IT manager about backup procedure.
ThinMan primary and Secondary Server Installer files
Before to start with ThinMan Primary and Secondary Server with Dual Database (FULL redundant configuration) update, pay attention to have available both ThinMan Primary server and ThinMan Secondary server file, i.e. ThinMan_x.y.z.exe and ThinManSecondary_x.y.z.exe. About how retrive both distinct installer file refer to Download ThinMan installation and upgrade file.
ThinMan update file retrive
If you need more information about how retrive ThinMan date file, refer to Download ThinMan installation and upgrade file.
ThinMan Update Sequence
In order to carry out the ThinMan Server Software update in FULL redundant configuration follow strictly the sequence described below.
- Stop the database replica between MySQL Master database instance and the MySQL Secondary one. Connect as root, or else using an user with administrative privileges, to the MySQL Slave instance using MySQL Command Line Client and execute the following command:
> slave stop;
In order to check the successful real stop of the database replica run, using MySQL Command Line Client, the command:
> show slave status\G;
In the output command list you have to check the following outcomes (here we reported only the significant output result rows, only and abstract of the whole output):
Slave\_IO\_Running: No
Slave\_SQL\_Running: No
Last\_IO\_Errno: 0
Last\_IO\_Error:
Last\_SQL\_Errno: 0
Last\_SQL\_Error:
In case of different output, refer to your Database Administrator.
Error in database replica stopping
In case of error in the database replica stopping, suspend the ThinMan update until you will obtain a successful database replica start and stop.
- Proceed to update the ThinMan Primary Server. On the ThinMan Primary Server run the ThinMan Installer, executing the file ThinMan_x.y.z.exe.
The ThinMan Primary Server Installer detect the current ThinMan version installed and will inform you about the imminent update from the current release to the new one. Click Next to proceed.
The ThinMan Server update starts. A progress bar shows update increase.
ThinMan Services Managment
During the ThinMan Primary Server update, the ThinMan installer will manage by itself stop and restart of all ThinMan Services on Primary Server.
When the update process is completed, ThinMan installer will display the updated version.
It's possible a restart be needed. If requested, we suggest to restart your system before proceed with the update procedure.
Reboot Primary Server during Update
At this time, you can reboot your ThinMan Primary Server smoothly because the ThinMan Secondary Server is still running ThinMan previous version and can supply all standard ThinMan services to users.
ThinMan Primary Server check
Before proceed with next Update steps, check by the Services Microsoft Management Console that ThinMan Primary Server services (i.e. ThinManNaming, ThinMan Server and ThinMan Support) are running.Last, check the ThinMan full operation through ThinMan Local Console execution.
Only after a successful ThinMan Primary Server test, you can proceed with the next upgrade step.
- Now the ThinMan Primary server is updated and functioning supplying all services both for users and for Administrators. We can indeed proceed to stop and upgrade the ThinMan Secondary Server. On the ThinMan Secondary server, trough Services Microsoft Management Console, stop ThinMan Server service.
- Restart the database replica between MySQL Master database instance and the MySQL Secondary one. Connect as root, or else using an user with administrative privileges, to the MySQL Slave instance using MySQL Command Line Client and execute the following command:
> slave start;
In order to check the successful real start of the database replica run, using MySQL Command Line Client, the command:
> show slave status\G;
In the output command list you have to check the following outcomes (here we reported only the significant output result rows, only and abstract of the whole output):
Slave\_IO\_Running: Yes
Slave\_SQL\_Running: Yes
Last\_IO\_Errno: 0
Last\_IO\_Error:
Last\_SQL\_Errno: 0
Last\_SQL\_Error:
In case of different output, refer to your Database Administrator.
STOP THINMAN UPDATE
In case of error in the database replica starting, suspend the ThinMan Secondary Server update until you will obtain a successful database replica restart.
- Proceed to update the ThinMan Secondary Server. On the ThinMan Secondary Server run the ThinMan Installer, executing the file ThinManSecondary_x.y.z.exe.
The ThinMan Secondary Server Installer detect the current ThinMan version installed and will inform you about the imminent update from the current release to the new one. Click Next to proceed.
The ThinMan Secondary Server update starts. A progress bar shows update increase.
When the update process is completed, ThinMan Secondary Server installer will display the updated version. It's possible a restart be needed. If requested, we suggest to restart your system before proceed with the update procedure.
ThinMan secondary service check
On the ThinMan Secondary server, trough Services Microsoft Management Console, check the ThinManServer service be running, otherwise start it manually
Update terminated
If no errors are occurred and all services are running properly both on Primary as Secondary ThinMan Server, you can consider the ThinMan Primary and Secondary Server with Dual Database (FULL redundant configuration) update procedure successfully completed.