(Click to open topic with navigation)
This topic provides instructions to upgrade Moab Insight to the latest release version using the RPM upgrade method. It includes instructions for migrating your database schema to a new version if necessary.
Because many system-level files and directories are accessed during the installation, the instructions in this guide should be executed with root privileges.
You will see that the instructions execute commands as the root user. Please note that the same commands will work for a non-root user with the sudo command.
3.22.1 Upgrade the Insight Server
Do the following:
[root]# mschedctl -s
[root]# service insight stop
[root]# cp -r /opt/insight /opt/insight-9.0.1-backup
[root]# su - postgres [postgres]$ pg_dump moab_insight > /tmp/moab_insight_9.0.1.dump [postgres]$ pg_dump moab_insight_reference > /tmp/moab_insight_reference_9.0.1.dump [postgres]$ exit [root]# mv /tmp/moab_insight_9.0.1.dump /opt [root]# mv /tmp/moab_insight_reference_9.0.1.dump /opt [root]# mongodump --username insight_user --password secret4 -d insight --out /opt/insight_9.0.1.mongo.dump
[root]# yum update moab-insight*
[root]# ls -l /opt/insight/etc/config.groovy -rw-r--r--. 1 insight insight 3787 Jan 24 17:51 /opt/insight/etc/config.groovy
JAVA_HOME="/usr/java/latest"
Optional. Postpone the database upgrade.
Upon starting, Insight will detect what version the PostgreSQL and Mongo Insight database schemas are. If the schemas are not compatible with the current version, Insight will upgrade the schemas, including all data contained therein.
If you cannot wait that long and you don't have immediate need for the old data, you can postpone the database upgrade and allow the Insight upgrade to continue.
To postpone the database upgrade, set the following in the /opt/insight/etc/config.groovy file.
insight.skip.database.migration = true
When you have time to perform the database upgrade, set this property back to "false" and restart Insight.
[root]# service insight start
If you decided not to postpone the database upgrade, then wait for and confirm the database upgrade completed. All data must be transferred before the upgrade is complete.
To track the upgrade process, view /opt/insight/log/insight.log file. You should output similar to the following:
2016-06-28T06:25:12.323-0600 main INFO com.ace.insight.data.service.dbinit.DbUpgradeService 0 Successfully transferred 21942 of 22101 node samples to MongoDB 2016-06-28T06:25:12.383-0600 main INFO com.ace.insight.data.service.dbinit.DbUpgradeService 0 Successfully transferred 21995 of 22101 node samples to MongoDB 2016-06-28T06:25:12.439-0600 main INFO com.ace.insight.data.service.dbinit.DbUpgradeService 0 Successfully transferred 22048 of 22101 node samples to MongoDB 2016-06-28T06:25:12.498-0600 main INFO com.ace.insight.data.service.dbinit.DbUpgradeService 0 Successfully transferred 22101 of 22101 node samples to MongoDB ... 2016-06-28T06:25:12.871-0600 main INFO com.ace.insight.data.service.dbinit.DbUpgradeService 0 Successfully upgraded 900 of 1140 workload_view entries in MongoDB 2016-06-28T06:25:12.911-0600 main INFO com.ace.insight.data.service.dbinit.DbUpgradeService 0 Successfully upgraded 1000 of 1140 workload_view entries in MongoDB 2016-06-28T06:25:12.945-0600 main INFO com.ace.insight.data.service.dbinit.DbUpgradeService 0 Successfully upgraded 1100 of 1140 workload_view entries in MongoDB 2016-06-28T06:25:12.959-0600 main INFO com.ace.insight.data.service.dbinit.DbUpgradeService 0 Successfully upgraded 1140 of 1140 workload_view entries in MongoDB
When the upgrade is completed, you will see the following lines in your /opt/insight/log/insight.log file:
2016-06-28T06:25:13.120-0600 main INFO com.ace.insight.data.service.dbinit.DbUpgradeService 0 Database has been upgraded to current version
mschedctl -r