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 process runs in the background. It 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 perform the migration from MySQL to Percona XtraDB Cluster.

To upgrade the historic database schema:

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;

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.

Moogsoft AIOps uses Percona XtraDB Cluster which supports the Galera replication protocol to support high availability (HA). Percona XtraDB is similar to MySQL with improvements for HA, scalability, and usability.

Moogsoft strongly recommends you perform the migration from MySQL to Percona XtraDB Cluster and HAProxy. See Database Strategy for details behind the Moogsoft decision to use Percona and HAProxy.