Post-upgrade steps

Follow these steps to perform the post-upgrade tasks for an upgrade to Moogsoft AIOps v7.3 from v7.0.x, v7.1.x, or 7.2.x.

Refer to Upgrade Moogsoft AIOps for general information and upgrade instructions for other components and versions.

Upgrade the historic database

You must upgrade the historic database. This can be done after the main upgrade process has been completed and while the system is running.

The upgrade process runs in the background. This process is separate from the main schema upgrade because for very large databases it can take several hours to complete. You can upgrade the historic database either before or after you migrate from MySQL to Percona XtraDB Cluster.

The Events Analyser utility should not run at the same time as the migration utility. To temporarily disable the Events Analyser:

Disable the events_analyser crontab:

(crontab -l | sed -e 's/^\(.*events_analyser.*\)$/#\1/') | crontab -

Stop the events_analyser if it is running:

kill $(ps -ef | grep events_analyser | grep -v grep | grep java | awk '{print $2}')

To upgrade the historic database schema:

Run the moog_historic_post_migration script with the valid arguments for your system, on a terminal dedicated to the process. Use the -h flag to see all available options. Allow the process time to finish - it is recommended that this script is run during a period of low event throughput (For example at midnight). For example:
```
$MOOGSOFT_HOME/bin/utils/moog_historic_post_migration.sh -H localhost -P 3306 -u root
```
This script will attempt to add indexes to a number of tables to improve performance. Check the script output for errors. If any are seen contact Moogsoft Support.
Validate the migration is complete using the database validator utility:
```
$MOOGSOFT_HOME/bin/utils/moog_db_validator.sh
```
Optionally, enable compression on the historic database snapshots table. Moogsoft recommends this if disk space is a concern.

This utility is documented here: Table Compression Utility

Note

This utility requires a number of Perl dependencies to run. The following commands can be run to install these dependencies (root required for the final 'yum' command):

for PACKAGE in perl-Compress-Raw-Bzip2-2.061-3.el7.x86_64.rpm perl-Compress-Raw-Zlib-2.061-4.el7.x86_64.rpm perl-DBD-MySQL-4.023-6.el7.x86_64.rpm perl-DBI-1.627-4.el7.x86_64.rpm perl-Data-Dumper-2.145-3.el7.x86_64.rpm perl-Digest-1.17-245.el7.noarch.rpm perl-Digest-MD5-2.52-3.el7.x86_64.rpm perl-IO-Compress-2.061-2.el7.noarch.rpm perl-Net-Daemon-0.48-5.el7.noarch.rpm perl-PlRPC-0.2020-14.el7.noarch.rpm perl-IO-Socket-IP-0.21-5.el7.noarch.rpm perl-IO-Socket-SSL-1.94-7.el7.noarch.rpm perl-Mozilla-CA-20130114-5.el7.noarch.rpm perl-Net-LibIDN-0.12-15.el7.x86_64.rpm perl-Net-SSLeay-1.55-6.el7.x86_64.rpm
do
	curl -L -O http://mirror.centos.org/centos/7/os/x86_64/Packages/${PACKAGE};
done;

Then install the packages downloaded:

yum -y install *.rpm

After you have run these steps, you can re-run the Database Validator utility to confirm that the schemas are now in sync. See Validate the upgrade: Database components for details on how to run the utility.

You can now re-enable the Events Analyser utility. If the current deployment does not use entropy, you should not re-enable the Events Analyser because this utility is a CPU and memory-intensive process.

(crontab -l | sed -e 's/^\#\+\(.*events_analyser.*\)/\1/') | crontab -

Migrate the databases to Percona XtraDb Cluster and HA Proxy

To perform the migration, refer to the appropriate instructions, depending on your deployment type:

Update the Workflow Engine

Download and deploy the latest version of the Workflow Engine so any existing WFE behaviours will function in the upgraded system. Refer to Update the Workflow Engine for more information.

The upgrade is now complete.

In this section: