Upgrade Moogsoft Onprem
The topics in this section describe how to upgrade Moogsoft Onprem to v9.x from any of the following versions:
v8.x.x.x
SAML Configuration Requirements
New security enhancements in v9.0.1 require enabling the Sign Response As Required option on the IDP side, if configurable. We kindly request your SAML team to do this for the <PROD/UAT> environment before the upgrade. If you are unsure after communicating with your SAML team whether this option applies to your setup, please contact Moogsoft support.
If a new IDP is generated after this change, SAML team should provide its metadata file to the team taking care of the upgrade. During the upgrade, the existing IDP file will be replaced with the one provided. In all cases, the SP metadata file will be regenerated and should be shared with SAML team. They may need to import the new SP metadata or configure the relevant fields with the information supplied in the file to complete the trust configuration.
Moogsoft Hosted customers can contact support to request an upgrade. For more information, see Upgrading and Updating Your Moogsoft Hosted Instances.
For information on how to upgrade from other versions, see Moogsoft Releases.
For instructions on how to install a distributed high availability (HA) configuration, see Fully Distributed HA Installation.
Your upgrade path depends on your preferred mode of deployment:
RPM: Use this method if you have root access to your Moogsoft Onprem servers and you do not want to change the default installation locations.
Tarball: Use this method if you need to run the process as a non-root user, or if you want to deploy to a non-default location and install all components under one directory.
The tarball installer is hosted on the Moogsoft "speedy" Yum repository: https://speedy.moogsoft.com/v9/installer/. Contact Moogsoft Support for access if you do not already have an account.
If you have root access but your Moogsoft Onprem servers do not have access to the internet, see "Prepare for an offline upgrade" in Prepare to Upgrade (RPM).
Minimize upgrade downtime
To minimize the amount of downtime required for the upgrade process, follow this process:
Disable historic data retention.
Perform the upgrade according to your chosen method of deployment.
Re-enable the Historic Data Utility.
Let the historic data retention utility process any alerts that have accumulated. This should not take long if the process has been disabled for only a few hours.