Upgrade Manager
The upgrade process for OpManager - installed servers across your network is simplified using the Upgrade Manager. It offers a centralised platform to manage and perform upgrades for OpManager Central, Probes, their Failover servers. The enhanced smart upgrade feature helps to overcome the bottlenecks faced during the upgrade process.
...
Note:
- In MSP Edition, all Probe services must be up and actively communicating with the Central server. For Failover setups, both the primary and secondary services should be up and running.
- For service Pack versions 12.8.344 and above, manual backup prerequisites are optional as the Upgrade Manager takes the backup automatically.
- The QPM, designed to deliver targeted patches, can be seamlessly applied across services using Upgrade Manager, following the same steps as a service Pack.
- If you are encountering issues caused by AV/EDR interactions during the upgrade process, please follow this exclusion guide.
...
...
....
- The service pack's download progress status for individual Probes will be displayed under the Current Status column.
While downloading the service pack, if slowness or network issues is encountered, you can manually stop the download using the Stop button in the Actions column. In that case, manually copy the service pack to the <OpManagerProbe>\UpgradeManager directory for OpManager service packs. Use the Refresh button to fetch the latest status of the respective Probe service.
- If a Probe goes offline or loses connection with Central during the service pack download, then the download will automatically resume once communication is restored.
....
...
...
- For Failover servers, the upgrade will start automatically for both the active and the standby server.
- All Probes will automatically begin upgrading simultaneously once the Central upgrade is successfully completed.
- Upgrade details for individual servers will be automatically updated under the Current Status column in Central.
....
...
- If you are encountering issues caused by AV/EDR interactions during the upgrade process, please follow this exclusion guide.
- Ensure that the user performing the upgrade has the required permissions for the OpManager folder.
...
| Edition |
Without Failover |
New Failover |
Old Failover |
| OPM MSP |
- Stop the OpManager Central and all the Probe services.
- Upgrade using UpdateManager.bat /.sh file.
- Once the upgrade is completed, start the Central service.
- Then, the Probes will detect the upgrade, perform it in all the Probes and start the services on its own.
|
- Stop both primary and secondary service in OpManager Central.
- Stop the secondary service and ensure only the primary service in running in all Probes.
- Follow the steps provides under UpdateManager.bat /.sh file to perform upgrade in Central.
- Once upgrade is completed start the OpManager Central service.
- Then, the Probes will detect the upgrade, perform automatically in all the Probe services.
- Start and stop the Standby service once as master across Central and Probe, then start the primary followed by the Standby service.
|
- Download the appropriate version
- Stop all primary services and secondary service across Central and all Probes.
- Perform upgrade on primary service and followed by secondary service in Central and all Probes using UpdateManager.bat /.sh file.
- Start the secondary service first, then followed by the primary Service.
- The secondary will switch to standby mode automatically once primary service is started completely.
|
...
Note: For old Failover model, the upgrade should be performed in both primary and secondary services.
...
How to identify the Failover model
Failover models that do not use Virtual IP and share folder are called Old Failover model, whereas, Failover models that use Virtual IP and share folder can be called as the New Failover model. There are two methods to identify the Failover model.
Method 1 (via UI)
- In OpManager UI, navigate to Settings -> General Settings -> Failover Details.
- If there is only a table, it is the old Failover.
- If the Failover architecture is displayed, it must be the new Failover model.
Method 2 (manual steps)
Old Failover
Connect to OpManager database. Or ensure that DB Query is enabled under System Settings -> Client settings tab, and click the Support icon from the OpManager UI, select DB Query and then execute the below query. If there are two rows, then it is the old Failover model.
- For Essential / Central - Select * from FailOverDetails where ID = -1;
- For Probe - Select * from FailOverDetails where ID = (Select MOID from ManagedObject where TYPE='Region');
New Failover
- If the file itom_fos.conf is present in both the primary and the secondary server, under <OpManagerHome>/conf directory, then it is the new Failover model.
...
