Upgrade Guide: Version 8.0.16
It is crucial to have Motadata AIOps baseline version of 8.0.14 to upgrade to Motadata AIOps version 8.0.16. Additionaly, ensure TCP ports 9471, 9472, 9473, 9474 are open in Motadata AIOps application bidirectionally to seamlessly upgrade to 8.0.16 version.
Latest Motadata AIOps Installation Links
Motadata AIOps | Link |
---|---|
Ubuntu 24.04 (.iso) | Download |
Ubuntu 24.04 (.ova) | Download |
RHEL 9.4 (.tar) | Download |
MotaAgent Installation Links
Operating System | Version | Link |
---|---|---|
Ubuntu | 18, 20, 22, 24 | Download |
RHEL & CentOS | 7, 8, 9 | Download |
Windows | Client OS 8 or Server OS 2012 | Download |
Windows | Client OS 10, 11 or Server OS 2016, 2019, 2022 | Download |
IBM-AIX | 7.x | Download |
SUSE Linux | 15.6 | Download |
Upgrade Patches for 8.0.16
Operating System | Link |
---|---|
Ubuntu/RHEL | Download |
Motadata Agent Manager Upgrade for 8.0.16
Operating System | Version | Link |
---|---|---|
Ubuntu/RHEL/Windows | All | Download |
Agent Upgrade Patches for 8.0.16
Operating System | Version | Link |
---|---|---|
Ubuntu | 18 | Download |
Ubuntu | 20 | Download |
Ubuntu | 22 | Download |
Ubuntu | 24 | Download |
RHEL | 7, 8, 9 | Download |
Windows | Client OS 8 or Server OS 2012 | Download |
Windows | Client OS 10, 11 or Server OS 2016, 2019, 2022 | Download |
Prerequisites for upgrading DB serverEnsure the Motadata AIOps service is not running before you perform this step.
- Take a VM Snapshot/Backup: Before proceeding with the upgrade, ensure you take a VM snapshot or backup of all servers.
- Contact Motadata: If the AIOPS version is 8.0.4 or below, please contact the Engineering team for assistance with the upgrade.
- Free Disk Space: Ensure at least 60% free disk space on the
/motadata
partition to perform the patch. (Very Important) - Disk IOPS Verification: Verify that the disk IOPS are greater than 250 Mbps before starting the server using the following command:
sudo dd if=/dev/mapper/vg0-motadata of=test1.img bs=1G count=1 oflag=dsync
Upgrade Steps
The upgrade steps varies for each deployment type. Please view the steps for your respective deployment architecture mentioned below.
- Standalone Deployment
- HA/DC-DR/HA Over WAN Deployment
Kindly refer Upgrade Guide in case you need to upgrade Ubuntu 20 to Ubuntu 24.
Take a VM Snapshot/Backup: Before proceeding with the upgrade, ensure you take a VM snapshot or backup of all servers.
Stop Motadata Services: Stop the motadata services for the Observer server, Primary server, Secondary server, Database server, and Collectors.
service motadata stop
Download AIOPS_UPGRADE.zip: Download and place the
AIOPS_UPGRADE.zip
file in the/motadata
directory on all servers.
Unzip the Upgrade Patch:
unzip AIOPS_UPGRADE.zip
Run the Upgrade Script: After unzipping the patch, run the upgrade script:
sudo ./aiops-upgrade.sh
noteIf the application and database are on the same server, proceed directly to Step 7. Otherwise, follow Step 6 first, and then move on to Step 7.
Master App Server Patch:
- Start the motadata service for the master application server.
- Wait for the patch to be applied.
- Verify the patch application by checking the patch-related logs.
- Ensure the GUI screen for the master server is accessible.
Final Steps:
- Start the motadata service for the database server.
- Start the motadata service for each collector, one by one.
- Verify that data is visible on the monitoring screen.
Kindly refer Upgrade Guide in case you need to upgrade Ubuntu 20 to Ubuntu 24.
Ensure there is no data sync backlog among Primary server, Secondary server, and Collector before proceeding to upgrade. Any data yet to be synced will be lost and cannot be recovered.
Take a VM Snapshot/Backup: Before proceeding with the upgrade, ensure you take a VM snapshot or backup of all servers.
Stop Motadata Services on select servers: Except Primary App and Observer server, stop Motadata services on all other servers.
sudo service motadata stop
Stop Motadata Services on Primary server: Once Motadata services has been stopped on all other servers, stop the service on the Primary server.
sudo service motadata stop
Stop Motadata Services on Observer server: Once Motadata services has been stopped on all servers including Primary, stop the services for Observer server.
sudo service motadata-observer stop
Rename the Events folder: You will need to rename the events folder for all App servers and Observer. (Observer, Primary App, Secondary App, and Replica App).
sudo mv /motadata/motadata/events /motadata/motadata/events_old
Perform the Upgrade on all Servers: You can now start upgrading all servers (Observer, Primary App. Primary DB, Secondary App, Secondary DB, Replica App, Replica DB, and Collectors)
Download AIOPS_UPGRADE.zip: Download and place the
AIOPS_UPGRADE.zip
file in the/motadata
directory on all servers.Unzip the Upgrade Patch:
unzip AIOPS_UPGRADE.zip
Run the Upgrade Script: After unzipping the patch, run the upgrade script:
sudo ./aiops-upgrade.sh
Start Motadata services on Observer server: Once the upgrade process has been completed, start the services on Motadata Observer server.
sudo service motadata-observer start
Start Motadata services on Primary server: Once Motadata services has been started on Observer server. Start the Motadata services on Primary App server.
sudo service motadata start
Ensure Motadata service has started on Primary App server: Wait to ensure motadata services has been properly started on Primary App server.
Kindly wait for the motadata-metric-agent-service
to spawn before proceeding to next step.
sudo watch service motadata status
Stop Motadata service on Primary App server:
sudo service motadata stop
Perform a backup of Configuration files for all App servers: Ensure you create a backup for configuration files on all the App server (Primary App, Secondary App, Replica App).
sudo cp -r /motadata/motadata/config/ /tmp/
Remove JSON files from the temporary folder located in the Primary App server:
sudo rm /tmp/config/*json
Create a tar file:
sudo tar -cvf /tmp/config.tar /tmp/config/
Replicate the Config folder with non-JSON files from Primary App server to other App servers: You will need to copy the config folder containing non-JSON files to all other App servers (Primary App, Secondary App, and Replica App).
Kindly replace the <App_server_IP>
placeholder with actual IP address of your App servers.
sudo scp -r /tmp/config.tar motadata@<App_server_IP>:/tmp/
Merge the non-JSON files on other App servers: Execute the below-mentioned commands one by one.
sudo tar -xvf /tmp/config.tar
sudo cp /tmp/tmp/config/* /motadata/motadata/config
Provide necessary permissions to the file on other App servers:
chmod -R 755 /motadata/motadata/config/
Start the Motadata service on the Primary App server:
sudo service motadata start
Once the server is up and running, navigate to Motadata health monitoring screen and ensure Primary App server is registered.
Start the Motadata services on all other servers: You can start Motadata services on all other servers including Primary DB, Secondary App, Secondary DB, Replica App, Replica DB, and Collectors one by one.
sudo service motadata start
Verify all servers are up and running: Once all servers are up and running, navigate to Motadata health monitoring screen to ensure all servers are operational and working as intended.
Agent Upgrade (Ubuntu, Windows, RHEL/CentOS)
- Download MOTADATA-MANAGER_UPGRADE.zip: Download the agent file from the above link and Upload the file on the Agent upgrade screen.
- Run Compatibility Check: Click 'Run Compatibility Check' and then click on 'Upgrade Now' for the agent that need to be upgraded.
- Wait for few moments: Kindly wait for a few moments for the upgrade to be completed.
- Download the Agent Upgrade Zip: Download the appropriate agent upgrade zip from the above link corresponding to the OS version of your system.
- Run Compatibility Check: Click 'Run Compatibility Check' and then click on 'Upgrade Now' for the agent that need to be upgraded.