Upgrade SolarWinds NTA
This checklist details the steps for upgrading only NTA in your environment.
Upgrade Tip! If you upgrade multiple versions of the same product, skip the website optimization step in the Configuration Wizard. Only run this step with the last installation to save time.
|1. Installation step using the upgrade path (Repeatable)||
Following the upgrade path, download the NTA product installation file from your Customer Portal in the My Downloads area. Save this file to your systems.
If you are upgrading from NTA 4.2.2 to 4.2.3 using the new SolarWinds Orion Installer, see step 2.
Depending on the version, you may have a smart bundle of all install files per system, separate files to download, or the standalone installer.
After installing this product and version on your entire environment, check the product and version as done on your downloaded Upgrade Path PDF or list. If you have additional versions to install, repeat this step.
2. Upgrade NTA using the SolarWinds Orion Installer
Starting with version 4.2.2, SolarWinds NTA is available for installation through the new SolarWinds Orion Installer. To learn more about upgrading with the installer, see this article.
The Orion Installer generates and builds the upgrade path for you, directing the entire upgrade process. When you run the installer, it detects your installed Orion products and versions, verifies the latest available product versions available per your maintenance agreement, and builds the upgrade path for you.
While you can still use the Upgrade Product Advisor to see what your upgrade path may look like, we recommend always using the Orion Installer upgrade path.
When you upgrade an existing NTA installation with the NTA Flow Storage Database installed on a remote server, using the SolarWinds Orion Installer, Orion Installer cannot upgrade the remote Flow Storage Database. You must upgrade the remote NTA Flow Storage Database manually, using the stand-alone installer.
The Orion Installer shows a warning message if you upgrade the Main Poller before upgrading the remote NTA Flow Storage Database. For more information, see this article.
Steps for upgrading from NTA 4.2.2 and earlier with a remote NTA Flow Storage Database:
|3. Upgrade Orion Agents||
If you have the Global Agent Setting to Allow automatic updates (enabled by default), the Orion Agents automatically upgrade in the background. Agents are tied to their release version. You can skip manually upgrading agents if the option is enabled.
The upgrades take a bit of time to complete, but will not require any actions. Agents update at a throttled number of 10 to limit the impact on the polling engine. As soon as one agent completes upgrading, another agent takes its place so there are always 10 active threads until all agents are upgraded.
If automatic upgrades are disabled, upgrade the Orion Agents:
You can enable the option through Settings > All Settings > Agent Settings and click Define Global Agent Settings.
|4. Start the engines||
Start services in the Orion Service Manager on the main polling engine, all additional polling engines, and all web servers.
|5. Re-enable alert actions||
If you have alerts configured to notify you when certain entities haven't been polled for "X" number of minutes or similar, ensure that you have waited for at least two polling intervals before re-enabling alert actions so that polling has caught completely up, which prevents false alerts.
After the upgrade check your system
All product versions should be installed properly. Open the application and verify the versions displayed in the footer of the Web Console. Try current and new features with your system to check performance and expected functionality. If you run into issues, check the troubleshooting tips.
If you receive errors, try the following:
- If you experience issues and are not on the latest product versions, we recommend completing a full upgrade. Use the SolarWinds Orion Installer to create the upgrade path. Many of these updates solve issues you may experience part way through your upgrade.
- Check our Success Center for troubleshooting. We recommend searching the name of the product, the version number, any error codes or messages displayed, and the general issue you found.
- Check your Customer Portal for any new hot fixes.
- If you receive a (500) internal server error after an upgrade, use the Orion permission checker to make sure your Group Policy is not locked. See this article for full details.
- If your views do not load when first opening the console, run the Configuration Wizard again.
If an issue occurs you need additional help with, contact Support. We recommend gathering diagnostics, a screenshot of the issue, and any error codes you receive. Attach and add this information to your ticket. You may also want to gather additional diagnostics on your additional polling engines and web servers.