SERVERware 4 GUI Update
Introduction
Depending on the current version of SERVERware, there are two separate upgrade procedures: the SERVERware Core Upgrade and the SERVERware GUI Update.
For SERVERware versions below 4.3.0, a core upgrade is required, which is performed by the Support Team through the system's backend. Additional information on how to request a SERVERware core upgrade can be found at the following link:
How To Request SERVERware Core Upgrade
The SERVERware GUI Update is a simple procedure performed through the system’s GUI and can be carried out by system administrators themselves.
NOTE: No system downtime is expected during this procedure.
This guide is dedicated solely to the SERVERware GUI Update procedure, and all necessary steps for completing the update will be explained below.
Dependencies
From the v4.5. GUI update and onwards, some of the dependencies must be fulfilled before the update procedure itself can be conducted.
NOTE: The SERVERware GUI update cannot be performed if a Backup or Geo-Redundancy task is in progress or scheduled during the update time. Before starting the update, ensure that both backup and Geo-Redundancy tasks are disabled.
Backup → Schedule → Edit Backup Job → Disabled
Geo-Redundancy --> Servers --> Configure Replication --> Disabled
1 . Before any work, please check if the server processor supports virtualization. If does, verify that virtualization is enabled on the host:
lscpu | grep vmx
If the VMX flag is not present, it means that virtualization is not supported or enabled. Please enable virtualization in the server BIOS. Otherwise, the KVM SERVERware feature will not work. VMX must be enabled on every host on which KVM VPSs will run.
2. The second important detail is the api.tokens on storage hosts, due to previous updates failures are overwritten or even missing so this needs to be fixed before proceeding with the GUI installation.
Update Notification
The SERVERware controller will check for available package updates daily.
Once the update is available the notification pop-up message will appear on the top of the GUI screen every time the admin user log-in.
The pop-up dialogue window disappears after 10 seconds and provides a link to open the package update view if the administrator wants to proceed with updates.
Email notifications for newly available updates will be sent to the system administrators as well.
To update a SERVERware component, click the Update button for that component. The update process starts after the confirmation window.
The Update procedure
The Updates section of System Settings is used to update the various SERVERware components. The list on the right side shows the Name, Current Version, and Latest Version of the component that can be updated.
During the procedure, it is very important to follow the order of component updates. Below is a detailed explanation of which component should be updated by priority.
- You would first update the SERVERware Connector within the 'Updates' section, by just clicking on the Update button.
- Once done, the next step would be to update the sw-connetor on all hosts. The sw-connector service agent running on hosts is a crucial component for the proper functioning of the SERVERware environment, so it has to be updated if there are new features or bug fixes. Please follow this procedure to update the sw-connector:
1) In the Host view, select the host which sw-connector has to be updated.
2) Move the host into maintenance mode.
3) Click the Update SW-Connector button.
4) Open the System Logs view to track the progress of updating.
5) When the update is complete, click the Enable button to enable the host.
NOTE: Steps 1 to 5 should be repeated for every storage/processing/backup Host in SERVERware GUI.
- After sw-connector is updated within both sections and after you make sure that the hosts are out of maintenance mode, feel free to proceed with updating the SERVERware Web Control Panel under the 'Updates' section.