How to Move DPA to another server

11/29/2018 10:28 PM

12/12/2025 4:37 PM

The following instructions explain how to move SolarWinds DPA Application to a different server.

If you need to migrate the DPA Repository database, please reference the following KB:

https://solarwindscore.my.site.com/SuccessCenter/s/article/Move-a-DPA-repository-on-SQL-Server?language=en_US

This KB will also allow you to continue to use your Existing DPA Repository Database server.  Please verify the repo.properties file in your ignite_config folder for connections from the DPA app-tier server to the Repo DB server, especially if they are on separate servers.
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 on how to move the repository. These instructions apply to all OS versions of DPA (Windows, UNIX, Linux, etc.).

Database Performance Analyzer

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).
   1. If the DPA_home\iwc\tomcat\ignite_config\idc\server.properties file has a value in this setting. java.max.heap.size=  Then run the batch files to recreate the service. See DPA heap memory steps from this article This step is needed because when the install was done above the file would have the default memory settings that are for monitoring up to 20 instances. If you had changed this seeing in the files from the older server and now have moved the file here the service needs to be recreated with the increased memory settings.
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 see this article.  

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. 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.
6. Replace the default files with the files from the older server
   1. If the DPA_home\iwc\tomcat\ignite_config\idc\server.properties file has a value in this setting. java.max.heap.size=  Then run the batch files to recreate the service. See DPA heap memory steps from this article This step is needed because when the install was done above the file would have the default memory settings that are for monitoring up to 20 instances. If you had changed this seeing in the files from the older server and now have moved the file here the service needs to be recreated with the increased memory settings.
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 see this article.