Submit a ticketCall us

WebinarDatabase Roundtable – Expert Database Professionals Feel Your Pain

In this video broadcast, Head Geek™ Tom LaRock is joined by Karen Lopez, Tim Chapman, and David Klee. They’ve known each other for many years, so this discussion was like four friends getting together to talk data and databases. They discussed diagnostic data collection, common performance root causes, reactive tuning versus proactive, and more. Join us for an engaging discussion on these topics! Plus, Tom LaRock will be available to answer your questions live.

Register now.

Home > Success Center > Storage Manager (STM) > STM - Knowledgebase Articles > Migrating Storage Manager to a different server

Migrating Storage Manager to a different server

Table of contents


This article describes how to migrate STM to a different server.


All STM versions


Note: Storage Manager versions 5.6 and newer use MariaDB. For versions prior to 5.6, substitute MySQL for MariaDB.

  1. Install Storage Manager on the new server. Make sure the version installed on the new server matches the version installed on the old server.
    For example: If Storage Manager 5.6.2 is installed and running on the old server, Storage Manager 5.6.2 MUST be installed and running on the new server.
  2. If the new server has a different IP or FQDN (Fully Qualified Domain Name) then follow these steps. Otherwise skip to step 3.
    1. Make sure all of the Storage Manager services are running on the old Storage Manager server.
    2. Log into the web console for the old Storage Manager server.
    3. Select Settings > Policies > Default OS Policy > Edit button (pencil icon) > Communications.
    4. Change the following options to match the new server: 
      • HTTP Port: Default (4319)
      • Server: IP or Domain Name
      • Trap Port : Defaults (162, 10162, 20162)
      • Community String: Default (public)
      • Override Agent Values: Yes
    5. Press Save.
    6. Press Push to add these changes to the push list. This will push the new parameters to the agents.
    7. Run the Agent Push Report at the top of the screen. This will list any agents that have a push pending. Refresh the website every 15-30 seconds until all of the agents clear from the Push Report list. If any agents fail it will be necessary to update them manually. Failures are usually caused by connectivity issues between the agent and Storage Manager server.
  3. Deactivate the Storage Manager license. If deactivation is not possible, a call to customer service will be needed to get the license reset.
  4. Stop the mariadb service on the old and new server. This will also stop all 5 Storage Manager services.
  5. Migrate the Storage Manager database from the old server to the new one. The default location for the database will be “<installed>\Program Files\Solarwinds\Storage Manager Server\mariadb\data\storage” for Windows and “/opt/Storage_Manager_Server/mariadb/data/storage" for Linux.  Make a copy of the entire subdirectory and copy it to the same location on the new server.
  6. Start mariadb, Storage Manager Collector, Storage Manager Event Receiver, Storage Manager Maintenance, Storage Manager Poller and the Storage Manager Web Services.
  7. Log into the Storage Manager website for the new server using your regular username, password and insert the license key obtained from your customer portal into Storage Manager. If no key is present in your customer portal, call customer service to get it reset. Storage Manager will run in evaluation mode for 30 days without a key.
  8. Note that any devices being monitored by the old collector must be switched to the new collector. There will be two entries in Storage Manager, one for the old server (this can be deleted if desired) and new server. Any devices that were being monitored by the old server must be modified to point to the new server or an external agent.
  9. Verify that Storage Manager is communicating with the devices being monitored. This can be verified by viewing the main console website. If there are any communication issues, contact technical support for assistance.
Last modified