# Moogsoft Docs

## Upgrade - Migrate from RHEL6 to RHEL7

Red Hat Enterprise Linux 6/CentOS 6 (RHEL6/CentOS6) is not supported for Moogsoft AIOps v7.0.1. As a result, if you want to upgrade to Moogsoft AIOps v7.0.1, you need to install the same version of Moogsoft AIOps onto a Red Hat Enterprise Linux 7/CentOS 7 (RHEL7/CentOS7) platform and migrate your data across before upgrading to Moogsoft AIOps v7.0.1.

This document describes the recommended process for migrating the current version of AIOps from RHEL6 /CentOS6 to RHEL7 /CentOS7 . You can then use the standard upgrade documents linked at the bottom of this page to perform the upgrade itself.

This document only covers the RPM-based AIOps deployments, as the non-root version does not support RHEL6 /CentOS6 .

## Install the Existing Version of Moogsoft AIOps onto a New RHEL7/CentOS7 Server

• If you are using AIOps v6.4.0.x, please perform a clean install of this version on the new RHEL7/CentOS7 server using the following guides:
• If you are using AIOps v6.5.0.x, please perform a clean install of this version on the new RHEL7/CentOS7 server using the following guides:

## Migrate the Configuration Files and Data

### Migrate the Configuration Files

The following configuration files should be copied from their current location onto the same location on the new server. The ownership and permissions MUST be set to the same as they were on the original server.

•  $MOOGSOFT_HOME/config/  - You should migrate any customized files in this folder, as appropriate. • $MOOGSOFT_HOME/contrib/  - You should migrate any files used by LAMs or moolets in this folder.
•  /etc/init.d/apache-tomcat  - You should migrate this service script if it has been customized.
•  /etc/init.d/moogfarmd  - You should migrate this service script if it has been customized.
•  /etc/init.d/{restlamd,socketlamd,traplamd,...}  - If any of the default LAM service scripts have been customized or new LAM service scripts have been added to this folder, you should migrate them.
•  /etc/nginx/conf.d/moog-ssl.conf  - If this file or any other Nginx file has been customized, you should migrate it.
•  /var/lib/moogsoft/  - You should copy this entire directory across to the new server. Ensure folder permissions and ownership are the same as on the other server.
•  $MOOGSOFT_HOME/ui/integrations  - You should migrate this folder if UI-based integrations are being used. •  /etc/my.cnf  ### Migrate the Database You only need to follow these steps if the  moogsoft-db  package is installed alongside the MySQL package on a RHEL6/CentOS6 server. To migrate the database: 1. Stop all LAMs and moogfarmd. 2. Stop Apache Tomcat. 3. Run the following commands to perform a database dump: mysqldump --single-transaction --set-gtid-purged=OFF --routines --triggers moogdb > moogdb.sql mysqldump --single-transaction --set-gtid-purged=OFF --routines --triggers moog_reference > moog_reference.sql mysqldump --single-transaction --set-gtid-purged=OFF --routines --triggers historic_moogdb > historic_moogdb.sql 4. Copy the three SQL dump files onto the new RHEL7/CentOS7 server. 5. Import the database dumps into the new database: mysql moogdb < moogdb.sql mysql moog_reference < moog_reference.sql mysql historic_moogdb < historic_moogdb.sql ### Restart MySQL If the  my.cnf  file has been customized, restart the  mysqld  service: service mysqld restart ## Verify the Migration To verify the migration: 1. Validate migration of AIOps core binary files: $MOOGSOFT_HOME/bin/utils/moog_install_validator.sh
2. Validate migration of apache-tomcat webapps and configuration:

$MOOGSOFT_HOME/bin/utils/tomcat_install_validator.sh 3. Validate that the database schema has been migrated successfully: $MOOGSOFT_HOME/bin/utils/moog_db_validator.sh
4. Some schema differences may be valid (e.g.  custom_info  related). If there are more substantial differences, you should investigate further.