Upgrade Guide: Version 10.0.2

note

It is crucial to have Motadata ObserveOps baseline version of 10.0.0 to upgrade to Motadata ObserveOps version 10.0.2.

note

Ensure the TCP port 9433 is open in the Motadata ObserveOps application with bidirectional access to allow a seamless upgrade to version 10.0.2.

Latest Motadata ObserveOps Installation Links

Motadata ObserveOps	Link	MD5 Checksum
Ubuntu-24	Download	573c5dc4d99a8275739063824d31d67c
Ubuntu-26	Download	fa4bcca2630476bd2e6bb8a4731c3e18
RHEL (.tar)	Download	9eadd5febe8cd6f2fb4bfa18fd43d635

MotaAgent Installation Links

info

You need to upgrade to latest MotaAgent version 10.0.2 while upgrading the Motadata Application.

Operating System	Version	Link	MD5 Checksum
Linux	All	Download	3202859618549296e09b4bf327f2d2e3
Windows	All	Download	f3039f63d146e0a88e4c763ff7b2e025
IBM-AIX	7.x	Download	3f08ae21435461a992ef7b9382514c8d

Upgrade Patches for 10.0.2

Operating System	Link	MD5 Checksum
Ubuntu/RHEL	Download	59b325e851ba4c2282aa39864600bfe4

Motadata Agent Upgrade Patches for 10.0.2

Operating System	Version	Link	MD5 Checksum
Windows and Linux	All	Download	cb6462933efddd8c2e6a8adc633629ff

note

After upgrading the Motadata Agent Manager using the link above, the system will wait for 30 seconds before automatically initiating the Agent upgrade.

Prerequisites

1. Take a VM Snapshot/Backup: Before proceeding with the upgrade, ensure you take a VM snapshot or backup of all servers.
2. Free Disk Space: Ensure at least 60% free disk space on the /motadata partition to perform the patch. (Very Important)
3. 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

1. Take a VM Snapshot/Backup: Before proceeding with the upgrade, ensure you take a VM snapshot or backup of all servers.

2. Stop Motadata Services: Stop the motadata services for the Observer server, Primary server, Secondary server, Database server, and Collectors.

   service motadata stop

3. Download OBSERVEOPS_UPGRADE.zip: Download and place the OBSERVEOPS_UPGRADE.zip file in the /motadata directory on all servers.

4. Unzip the Upgrade Patch:

   unzip OBSERVEOPS_UPGRADE.zip

5. Run the Upgrade Script: After unzipping the patch, run the upgrade script:

   sudo ./observeops-upgrade.sh
   note

   If 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.

6. 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.

7. 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.

HA Deployment

Pre-Upgrade Validation

note

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.

note

Ensure 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.

Applying Upgrade Patch

1. Take a VM Snapshot/Backup: Before proceeding with the upgrade, ensure you take a VM snapshot or backup of all servers.

2. Stop Motadata services on all servers in the following sequence: You will required to first stop services on Other Servers, then Primary App Server, and finally the Observer Server.

   sudo service motadata stop 

   sudo service motadata-observer stop

3. 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 and Secondary App).

   sudo cp -r /motadata/motadata/config/ /tmp/ 

4. Remove JSON files from the temporary folder and create a tar file in the Primary App server:

   sudo rm /tmp/config/*json 

   sudo tar -cvf /tmp/config.tar /tmp/config/ 

5. 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 Secondary App server.

   sudo scp -r /tmp/config.tar motadata@<App_server_IP>:/tmp/ 

note

Kindly replace the <App_server_IP> placeholder with actual IP address of your App servers.

6. Overwrite the non-JSON files on other App servers: Execute the below-mentioned commands one by one on all other app servers (Secondary App server).

   cd /tmp/

   sudo tar -xvf /tmp/config.tar 

   sudo cp /tmp/tmp/config/* /motadata/motadata/config 

7. Perform the Upgrade on all Servers: You can now start upgrading all servers (Observer, Primary App. Primary DB, Secondary App, Secondary DB, and Collectors)

   • Download OBSERVEOPS_UPGRADE.zip: Download and place the OBSERVEOPS_UPGRADE.zip file in the /motadata directory on all servers.

   • Unzip the Upgrade Patch:

     unzip OBSERVEOPS_UPGRADE.zip

   • Run the Upgrade Script: After unzipping the patch, run the upgrade script:

     sudo ./observeops-upgrade.sh

Post-Upgrade Validation

note

Kindly wait for the python3 /motadata/motadata/metricagent/bootstrap.pyc to spawn on Primary App server before proceeding to next step.

sudo watch service motadata status

8. Start Motadata services on Observer server, Primary App server, and all other servers: Once the upgrade process has been completed, start the services on Motadata Observer server, then Primary App server, and then all other servers in the sequence.

sudo service motadata-observer start

sudo service motadata start

9. 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.

HA-DR Deployment

Pre-Upgrade Validation

note

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.

note

Ensure 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..

Applying Upgrade Patch

1. Take a VM Snapshot/Backup: Before proceeding with the upgrade, ensure you take a VM snapshot or backup of all servers.

2. Stop Motadata services on all servers in the following sequence: You will required to first stop services on Other Servers, then Primary App Server, and finally the Observer Server.

   sudo service motadata stop 

   sudo service motadata-observer stop

3. 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, and Failover App).

   sudo cp -r /motadata/motadata/config/ /tmp/ 

4. Remove JSON files from the temporary folder and create a tar file in the Primary App server:

   sudo rm /tmp/config/*json 

   sudo tar -cvf /tmp/config.tar /tmp/config/ 

5. 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 Secondary/ Failover App server.

   sudo scp -r /tmp/config.tar motadata@<App_server_IP>:/tmp/ 

note

Kindly replace the <App_server_IP> placeholder with actual IP address of your App servers.

6. Overwrite the non-JSON files on other App servers: Execute the below-mentioned commands one by one on all other app servers (Secondary/Failover App server).

   cd /tmp/

   sudo tar -xvf /tmp/config.tar 

   sudo cp /tmp/tmp/config/* /motadata/motadata/config 

7. Perform the Upgrade on all Servers: You can now start upgrading all servers (Observer, Primary App, Primary DB, Secondary App, Secondary DB, Failover App, Failover DB, and Collectors)

   • Download OBSERVEOPS_UPGRADE.zip: Download and place the OBSERVEOPS_UPGRADE.zip file in the /motadata directory on all servers.

   • Unzip the Upgrade Patch:

     unzip OBSERVEOPS_UPGRADE.zip

   • Run the Upgrade Script: After unzipping the patch, run the upgrade script:

     sudo ./observeops-upgrade.sh

Post-Upgrade Validation

note

Kindly wait for the python3 /motadata/motadata/metricagent/bootstrap.pyc to spawn on Primary App server before proceeding to next step.

sudo watch service motadata status

8. Start Motadata services on Observer server, Primary App server, and all other servers: Once the upgrade process has been completed, start the services on Motadata Observer server, then Primary App server, and then all other servers in the sequence.

sudo service motadata-observer start

sudo service motadata start

9. 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, RHEL/CentOS)

1. Download MOTADATA-MANAGER_UPGRADE.zip: Download the agent file from the above link and Upload the file on the Agent upgrade screen.
2. Run Compatibility Check: Click 'Run Compatibility Check' and then click on 'Upgrade Now' for the agent that need to be upgraded.
3. Wait for few moments: Kindly wait for a few moments for the upgrade to be completed.
4. Download the Agent Upgrade Zip: Download the appropriate agent upgrade zip from the above link corresponding to the OS version of your system.
5. Run Compatibility Check: Click 'Run Compatibility Check' and then click on 'Upgrade Now' for the agent that need to be upgraded.