Generating an upgrade path does not start the upgrade or affect your current environment.
Instead, uninstall the earlier version and then install the current version. (For more information, see this article.)īecause of this change, SolarWinds does not recommend upgrading from NTA 4.2.3 or earlier. If you upgrade from NTA 4.2.3 or earlier, flow data cannot be migrated. NTA: NTA 4.4 and later uses a different type of Flow Storage Database than NTA 4.2.3 and earlier. Orion Platform 2016.1 and later products have new port requirements: 5671 (Rabbit MQ messaging), and 17778 (SW Information Service, agent communication to 2012). You must have the same versions of SolarWinds products on your primary and secondary servers before you can reenable your HA pools. If you enabled SolarWinds High Availability, you must disable High Availability before you can upgrade. SolarWinds Support can provide the best advice for these upgrade scenarios. If upgrading from a very early or End of Life SolarWinds product version, you might want to install a new product instead of performing an upgrade or migrating data. The versions must match between the main and additional polling engines or you will receive a Database Configuration Failure Error. If you use downloaded installers or the installer bundle, you must install one product and version at a time. For details, please see this article.ĭuring your upgrade, use the Scalability Engine Installer. This security product causes issues with MSMQ starting. If you are upgrading Orion products with Dell Carbon Black installed to Orion Platform 2020.2.5 or earlier, we recommend stopping or removing Carbon Black. One unzipped installer can consume several GBs of space. See Upgrading if you have custom code.Īlways verify that you have enough hard drive space for zipped and unzipped installers.
js files, or you were directed to make changes by SolarWinds Support, the code might be overwritten during the upgrade. If you wrote your own code by changing SolarWinds. If you experience issues and are not on the latest product versions, upgrade all products to the latest versions. Considerations for upgrading older product versionsīefore you upgrade from an older product version, review the following upgrade considerations. Use the information in this topic to access system requirements, prepare your environment, and review the list of "gotchas". If you have earlier versions, use the Orion Installer to plan your upgrade, and then use a legacy product installer to upgrade to the earliest supported version, as described in the following sections. If you are upgrading VMAN, see the VMAN Upgrade Guide for information about the VMAN appliance. If you have the following product versions or later, you can use the Orion Installer to upgrade directly to the latest product version: Minimum product versions that can be upgraded with the Orion Installer