Submit a ticketCall us

ebook60.pngHow to be a Cisco® ASA ace

Our eBook, Thou Shalt Not Pass…I Think?! can help you overcome the challenges of monitoring and managing Cisco ASA firewalls. This eBook is a great read if you’ve been frustrated with monitoring firewalls, managing ACL configs, and troubleshooting VPN connections.

Get your free eBook.

Home > Success Center > Database Performance Analyzer (DPA) > Move DPA to another server

Move DPA to another server

Created by Interspire Import, last modified by Robert Holtam on Nov 17, 2017

Views: 4,539 Votes: 3 Revisions: 17

Overview

The following instructions explain how to move SolarWinds DPA to a different server.  If you are also upgrading SolarWinds DPA to a different version, be sure to follow the specific instructions for that process. This is not a document for how to move the repository.  These instructions apply to all OS versions of DPA (Windows, UNIX, Linux, etc.).

Environment

  • All versions of DPA

Move the same version of DPA

  1. Install DPA on the new server.
  2. Deactivate your DPA licenses on the old server. See this article for instructions.
  3. Stop DPA on the old server.
  4. If the new server has a Windows OS, DPA will have been started automatically.  Shut down the "Ignite PI Server" service on the new Windows machine.
  5. Copy all files (EXCEPT cat.txt and java_loc.txt) in the DPA_home\iwc\tomcat\ignite_config directory from the old server to the new server (overwrite previous files).
  6. Start DPA on the new server by restarting the Ignite PI Server service (if it is a windows machine) or running the startup.sh script (if it is a UNIX/Linux machine). View the readme.txt file located in the top directory of the DPA installation if you need further information.
  7. Re-activate your DPA licenses on your new server.

Move and upgrade DPA at the same time

  1. Install DPA on the new server.
  2. Deactivate your DPA licenses on the old server. See this article for instructions.
  3. Stop DPA on the old server.
  4. If the new server has a Windows OS, DPA will have been started automatically. Shut down the "Ignite PI Server" service on the new Windows machine.
  5. Rename the DPA_home\iwc\tomcat\ignite_config directory to ignite_config_orig.
  6. Copy the following files from the previous DPA instance in the DPA_home\iwc\tomcat\ignite_config directory from the old server to the new server.
  7. Replace the following files with the newer version of the files and directly edit them for any edits that were made to the original copies in the DPA_home\iwc\tomcat\ignite_config\idc directory. (Changes have been made to the defaults of these files that we want to preserve with new releases. Therefore, any customization you may have made to these files will need to be re-edited.):
    1. server.properties 
    2. system.properties
  8. Start DPA on the new server by restarting the Ignite PI Server service (if it is a Windows machine) or running the startup.sh script (if it is a UNIX/Linux machine). View the readme.txt file located in the top directory of the DPA installation if you need further information.
  9. License your new SolarWinds DPA server using the new licenses in your SolarWinds Customer Portal. Depending on the SolarWinds DPA version, you might need to reset the licenses.
Last modified

Tags

Classifications

Public