Updated: December 12th, 2016 | SolarWinds Upgrade Guide 1.0
Supports: VMAN 7.0 and earlier
This guide walks you through upgrading only your VMAN product. We include checklists to prepare and complete your upgrades, gotchas, and troubleshooting steps.
Important for VMAN 7.0 integrated: VMAN 7.0 requires Orion Platform 2016.2, NPM 12.0.1, SAM 6.3, NCM 7.5.1. VIM 7.0 released with VMAN 7.0 includes Orion 2016.2. You must upgrade to Orion Platform 2016.2 products to upgrade to VMAN 7.0.
Upgrading multiple products? See our SolarWinds multiple products upgrade guide!
This video walks through installing VMAN, integrating with the Orion Platform or VIM, and setting permissions.
This preflight checklist details a number of important steps to help plan and prep for your upgrade.
|Review release notes||Review product release notes and available documentation in our Success Center.|
|Review system requirements|| |
Make sure your environment has all of the required hardware and software needs for your installations. You can verify the requirements for products and multi-module environments guidelines.
|Review licenses||Review your current product licenses and determine if you need to make any changes. You can download any updated license keys for your upgrade through your Customer Portal. Verify any license upgrades and needs with your SolarWinds account manager or contact SolarWinds.|
|Do you need to migrate?|| |
You may need to migrate products and databases to new dedicated servers or to shared servers. Check if you need to migrate by reviewing new requirements, your products, and your current environment.
Migrating adds time to your upgrade, but you have the best opportunity to update to new servers during an upgrade.
|Gather credentials||Make sure you have all account credentials, SQL database credentials, your SolarWinds account, and local admin server credentials.|
|Build your upgrade path|| |
Determine your VMAN upgrade path. If upgrading from an older version, you may need to upgrade to specific versions in steps. For example, VMAN 6.0 and higher can directly upgrade to VMAN 7.0.
For VMAN integrated with an existing Orion Platform:
Determine your VIM upgrade path, first determining the supported version for VIM with NPM. Then use the Upgrade Product Advisor to build your upgrade path using the supported version of NPM with other products.
We recommend downloading a PDF of your upgrade path from the Product Upgrade Advisor tool. You can use it as a checklist as you complete upgrades.
|Run all Windows updates||Before upgrading, check for and run all Microsoft Windows Updates on your main poller, all additional pollers, and all additional web servers. As you upgrade, if a Windows update runs, your system may reboot as needed by Windows.|
|Schedule the upgrade||Set up the maintenance window, preferably off-peak hours. Depending on the number of products, size of database(s), and size of environment, you may need hours to complete your upgrade. |
Upgrades will require polling engines and SolarWinds services to be offline for a length of time, causing you to lose a portion of polling data.
|Notify your company||Send a message to your company of the upgrade schedule and maintenance window. If you need additional help, contact and allocate specific staff to be available.|
The time it takes to complete an upgrade depends on:
Since every configuration is different, we cannot predict exactly how long your upgrade will take. Coming soon, we are compiling feedback with the THWACK community about upgrade times to help give you a ballpark estimate. Through this guide, we include steps and tips to help reduce time for your upgrade.
When you are ready to upgrade, complete these steps. They include the common actions you need to complete before upgrading products.
If you have a test or staging environment, we highly recommend testing the upgrade first. You cannot roll back an installation once completed.
1. Back up the DB
Snapshot your VMs
Back up your SolarWinds SQL database. If you need help, please check your vendor's site for documentation and instructions.
If you have your database on a VM, create a snapshot or copy of your VM.
You cannot roll back an upgrade. Always create a database backup.
|2. Back up custom code (Optional)|| |
(Optional) Back up your custom code.
3. Back up Report Writer reports (Optional)
Upgrading to NPM 12.0 or later or SAM 6.2.4 or later? You can skip this step.
If you use Report Writer reports (NPM 10.5 and earlier) or still have legacy reports, back up the reports folder to save your custom reports:
|4. Exclude files on anti-virus software|| |
To ensure the best performance on your server host and provide full file access, exclude specific file paths and directories from anti-virus software scans. See this article for details.
You can also place your systems behind a firewall to completely disable your anti-virus software during an upgrade.
|5. Stop services||Stop services in the Orion Service Manager on the main polling engine, all additional polling engines, and all web servers.|
This checklist details the steps for upgrading the VMAN virtual appliance.
|1. Prepare|| |
Download the VMAN product ISO file from your VMAN product ISO file from your Customer Portal in the My Downloads area. Save this file to your systems.
2. Upgrade on vSphere 5.x or later
If you have VMAN hosted on Hyper-V, skip this section.VMAN hosted on Hyper-V, skip this section.
For more information, see Upgrade a virtual appliance.
When upgrading VMAN 7.0 on VMware vSphere 6.5 using the VMAN .ova, you need to upgrade the vSphere hardware version to the latest version. See this vSphere article for version details. You may receive errors until the hardware version is updated.
|3. Upgrade on Hyper-V|| |
For more information, see Upgrade a virtual appliance.
|4. Verify|| |
If VMAN displays unusual behavior after upgrading, clear the browser cache.VMAN displays unusual behavior after upgrading, clear the browser cache.
For VMAN integrated with the Orion Web Console, you need to upgrade to Virtual Infrastructure Monitor (VIM). Regardless of your installed Orion product version (such as VMAN integrated with the Orion Web Console, you need to upgrade to Virtual Infrastructure Monitor (VIM). Regardless of your installed Orion product version (such as NPM 12.0.1 or SAM 6.3), you should run the VIM upgrade. This upgrade includes additional feature additions and fixed issues.
You can find the VIM 7.0 installer zipped with the full VMAN product download in the Customer Portal (not a separate download).
|1. Upgrade other Orion products (optional)|| |
If the Orion Platform has additional Orion products such as NPM, SAM, or NCM, you may need to upgrade those products to upgrade VIM or integrate the upgraded VMAN.VMAN.
|2. Upgrade VIM|| |
You must upgrade on the main poller first, then each additional polling engine, then additional web servers. The versions must match across all servers as you upgrade.
|3. Start the engines|| |
Start services in the Orion Service Manager on the main polling engine, all additional polling engines, and all web servers.
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 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 pollers and web servers.
© 2016 SolarWinds Worldwide, LLC. All rights reserved.
This document may not be reproduced by any means nor modified, decompiled, disassembled, published or distributed, in whole or in part, or translated to any electronic medium or other means without the prior written consent of SolarWinds. All right, title, and interest in and to the software and documentation are and shall remain the exclusive property of SolarWinds and its respective licensors.
SOLARWINDS DISCLAIMS ALL WARRANTIES, CONDITIONS OR OTHER TERMS, EXPRESS OR IMPLIED, STATUTORY OR OTHERWISE, ON SOFTWARE AND DOCUMENTATION FURNISHED HEREUNDER INCLUDING WITHOUT LIMITATION THE WARRANTIES OF DESIGN, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND NONINFRINGEMENT. IN NO EVENT SHALL SOLARWINDS, ITS SUPPLIERS, NOR ITS LICENSORS BE LIABLE FOR ANY DAMAGES, WHETHER ARISING IN TORT, CONTRACT OR ANY OTHER LEGAL THEORY EVEN IF SOLARWINDS HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
The SolarWinds and other SolarWinds marks, identified on the SolarWinds website, as updated from SolarWinds from time to time and incorporated herein, are registered with the U.S. Patent and Trademark Office and may be registered or pending registration in other countries. All other SolarWinds trademarks may be common law marks or registered or pending registration in the United States or in other countries. All other trademarks or registered trademarks contained and/or mentioned herein are used for identification purposes only and may be trademarks or registered trademarks of their respective companies.