ELA Distribution Upgrade to Latest
How to: Upgrading EventLog Analyzer (*Distributed Edition) to the latest Service Pack.
Note: A folder backup or a snapshot of the Admin and the Managed Server VMs is MANDATORY. If the backend database is customer's MSSQL, it is recommended to take a backup/snapshot of the MSSQL Database. The backup/Snapshot of ELA Servers and MSSQL instance/Server should not be deleted before confirming the upgrade status. The upgrade process should not be cancelled or interrupted. If the upgrade fails, the customer should contact Support at the earliest.
|
Important: For distributed edition, only the Admin Server should be upgraded. This will in turn upgrade the Managed Servers automatically.
Point to be noted: The Automatic Upgrade process of Managed Servers is time-consuming.
PPM file download link: <PPM download link>
The steps given below are to be followed in the Admin Server:
Stop the ManageEngine EventLog Analyzer service in the Admin server.
Open a command prompt with administrative privileges.
In this cmd window, navigate to <dir>:\ManageEngine\EventLog Analyzer\bin and execute the following batch files to ensure that the instance is completely shut down.
shutdown.bat
stopDB.bat
stopSEC.bat
In the same location, execute "initPGSQL.bat". (wait until its completion)
In the same location, execute "UpdateManager.bat".
Click on "Browse" ⇾ select the appropriate ppm file. The below window will popup.
Click on "Install" and wait for it to complete.
Start the ManageEngine EventLog Analyzer service in the Admin Server.
Log onto the GUI, click on "?" at the right-top corner, and check the build number, or the build number can be checked in the <Dir>:\ManageEngine\EventLogAnalyzer\troubleshooting\Build.properties file.
Finally, the Admin Server will automatically upgrade the Managed Servers but this is a time-consuming process (~20min per Managed Server). Hence, this automatic process should not be disturbed.
New to ADSelfService Plus?
Related Articles
How to upgrade the EventLog Analyzer Agent?
Usually, an agent upgrade would happen automatically if the credentials provided for agents under the "Manage agents" section are valid or has the appropriate rights for accessing services or logs in the agent machine. However, in recent builds ...
What to do if the component inside Log360 is not loading?
Troubleshooting Steps: Please ensure that the connection is proper, if in case of a connection issue, the components will not load within Log360. Local Integration: It is less likely to be a connection issue, in case of local integration, because ...
STATUS_MARKED_ROLLBACK in export
Issue: STATUS_MARKED_ROLLBACK in export Steps to fix: i) For postgres Database, download attachment<StatusMarkedRollback.txt> and rename file extension to .bat. 1. Copy patch statusMarkedRollback.bat to <ELA-HOME>\pgsql\bin folder. 2. Open Command ...
Distributed Edition - Trobleshooting Doc [INTERNAL]
Check there is a Registration Issue exist: 1) In Managed Server, Run a RegistrationWithAdminServer.bat located on <Home_ela>/troubleshooting on comment prompt as administrator. note: 1) We need to open the webserver port bidirectionally both in admin ...
License file on a Log360 Instance
How to: Applying a License file on a Log360 Instance Open the Log360 UI and login using the default/super admin credentials. Go to the Admin tab ⇾ Administration ⇾ Log360 Integration ⇾ click on "Sync Now" and ensure that all the required components ...