(12.05.100-en) How to Update a UMS HA Installation: Without Downtime of the Servers
Before the update, see Updating the Installation of an HA Network.
To update the HA installation, follow these instructions in the order given.
Preparing the Update
Perform the following steps before updating a server:
Download the current version of IGEL Universal Management Suite from the IGEL Download Server and distribute the installer file to all systems with UMS components (UMS Server, UMS Load Balancer, UMS Consoles).
In the UMS Console, call up the list of UMS Servers and Load Balancers in the HA network under UMS Administration > UMS Network and check whether the listed components really exist in the network. Delete orphaned entries before starting the process for updating the components.
Â
Create a backup of your database before starting the update installation. Use the backup procedures recommended by the DBMS manufacturer. See also Creating a Backup of the IGEL UMS.
Â
Verify that the time on all servers is synchronized.
Updating UMS Servers
In the update mode, the UMS Servers run with a local copy of the database. This ensures that they can answer requests from the devices and transfer configuration settings and profiles to the devices.Â
In the update mode, you can connect to the servers via the UMS Console. All changes made in the UMS Console during this time will be lost after the update.
Â
Warning
Do not make changes in the productive database during the update process. This is because decoupled servers work with a copy of the database schema in the meantime. For this reason, the update of all components within the UMS HA network should be carried out immediately. Implement a test system for the first installation of new IGEL UMS versions and check their processes before transferring them to the productive system. This also applies to hotfixes, patches, etc. for server systems and databases.
Updating the First UMS Servers
You can select any UMS Server within the HA network to start the update procedure.
Â
Read and confirm the License Agreement.
Read the Information regarding the installation process.
Verify the components to be installed. (In this case: HA network with UMS Server and UMS Load Balancer installed individually)
Â
Confirm the system requirements dialog if your system fulfills them.
Under Select Additional Tasks, specify whether you would like to create shortcuts for the UMS Console and UMS Administrator on the desktop.
If the internal Windows firewall is active on your host: Review the settings under Windows firewall settings and change them where necessary. Each port that is activated here will be set as rule in the Windows firewall.Â
Â
Â
Read the summary and start the installation process.
During the installation, the UMS Server switches to update mode.Confirm the message
n of m servers updated
.
Example:Â
Close the UMS installer once the installation is complete.
Â
Continue with the update of the next UMS Server.
Updating the Last UMS Server
→ Repeat steps 1-9 on the last UMS Server to be updated.
The last UMS Server updated renews the schema of the productive database after the installation. All other UMS Servers within the network which run in the update mode will be informed that the installation has finished. They will restart and reconnect themselves to the productive database. Afterwards, they will run in normal mode.
Updating Further Components
After updating the UMS Servers within the HA network, you have to update all other current UMS components, e.g. separate UMS Load Balancers and UMS Consoles.
In order to do this, run the UMS installer on the systems.
Verify the components to be installed.
Â
See also Troubleshooting: Load Balancer Is Not Stopping during the Update of the HA Installation.
Checking the Installation
Check if all processes are running. For the list of UMS HA processes, see IGEL UMS HA Services and Processes.
In the UMS Administrator, go to Datasource to check if the database is activated.
Â
In the UMS Console, go to UMS Administration > UMS Network and check the items Server and Load Balancer.
All servers and load balancers must be:updated
running
in normal mode
Â