Submit a ticketCall us

Webinar: Web Help Desk for HR, Facilities and Accounting Departments
This webinar will focus on use cases for HR, Facilities and Accounting.

Having a unified ticketing and asset management system for all the departments in your company can provide end-users with a seamless experience and make things easier for your IT team. Yet, with different business tasks and objectives, many departments don’t fully understand the capabilities of Web Help Desk and how the software can be customized for effective use in their departments.
Register Now.

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

Move DPA to another server

Created by Interspire Import, last modified by Melanie Boyd on May 01, 2017

Views: 892 Votes: 3 Revisions: 16

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. For DPA 9.1.85 and later, deactivate your DPA licenses on the old server. See this article for instructions.
  3. For 9.2 and above, save the licensing folder from the old installation (DPA_home\iwc\tomcat\licensing) and copy it to the new server.
  4. Stop DPA on the old server.
  5. 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.
  6. 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).
  7. 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.
  8. 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. For DPA 9.1.85 and later, deactivate your DPA licenses on the old server. See this article for instructions.
  3. For 9.2 and above, save the licensing folder from the old installation (DPA_home\iwc\tomcat\licensing) and copy it to the new server.
  4. Stop DPA on the old server.
  5. 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.
  6. Rename the DPA_home\iwc\tomcat\ignite_config directory to ignite_config_orig.
  7. 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.
  8. 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
  9. 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.
  10. 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
14:27, 1 May 2017

Tags

Classifications

Public