...
In this case, the update procedure generally looks as follows:
...
| width | 50% |
|---|
Stop all UMS Servers except one (verify this
...
in the server list of the UMS Console connected to the last running server).
Update this UMS Server.
As soon as the update is complete, the productive database will be updated upon server startup.Update the remaining UMS Servers (simultaneously or one after another).
When the update is complete, they will automatically connect to the productive database.Update other components like separate UMS Load Balancers and/or UMS Consoles.
For detailed instructions, see How to Update a UMS HA Installation: With Downtime of the Servers.
| Column | ||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||
|
| Note |
|---|
IGEL recommends using this HA update method due to a number of advantages:
|
| Anchor | ||||
|---|---|---|---|---|
|
In this case, the update procedure generally looks as follows:
...
...
Update all UMS Servers to a new version, one server after another.
While being updated, a UMS Server disconnects itself from the productive database and stores a copy of it locally in an embedded Derby database. The copy is created for each server except the last. The last UMS Server also updates the schema of the productive database. After this, all other UMS Servers connect themselves again to the original productive database.Update other components like separate UMS Load Balancers and/or UMS Consoles.
For detailed instructions, see How to Update a UMS HA Installation: Without Downtime of the Servers.
...
| width | 50% |
|---|
...
| Note |
|---|
By this update method, all UMS Servers can be addressed by the endpoint devices at any time during the update process, e.g. to supply user-specific profiles (IGEL Shared Workplace). However, note the following:
|
...
| Child pages (Children Display) |
|---|
...