Moving or Copying a Server Monitoring Application to a Different Computer

Our server monitoring applications can be moved (or an existing installation copied) to a different machine by following the steps below. The steps are the same for the three core applications, although the specific items to be moved vary slightly.


NOTE: The steps below are for v4.0 and newer

Moving or Copying PA Server Monitor

  1. 1. Install PA Server Monitor on the new server. Use the same version as the old server. The original Setup.exe file is available on the old server at C:\Program Files\PA Server Monitor\Install.
  2. 2. If you have Satellites, use Bulk Config on the old server to "Satellites: Set Central Server Hosts" to add the new server's IP address and port it will use (port 81 by default)
  3. 3. On the old server, go to the Console and choose Configuration > Export Complete Configuration. Export server credentials (and then be very careful with the file!)
  4. 4. On the new server, import the configuration file that was exported above. Delete the configuration file with the server credentials.
  5. 5. Stop the PA Server Monitor service on both the old and new servers.
  6. 6. Copy the C:\Program Files\PA Server Monitor\Config directory from the old to the new server
  7. 7. Copy the C:\Program Files\PA Server Monitor\Databases directory from the old to the new server. You can skip this step if you don't want existing historical performance data.
    If you are using MS SQL Server and the database server is changing as well, disconnect the database, copy it to the new server, and reconnect it.
  8. 8. You may want to copy the SSL certificate in C:\Program Files\PA Server Monitor\CA to the new server. If you don't, a new one will be generated.
  9. 9. If you have added extra MIB files to your system, you should copy C:\Program Files\PA Server Monitor\MIBs to the new server.
  10. 10. Report settings were copied in step 6 above. Existing report files (the actual HTML files) will be regenerated on their normal schedules, so you should delete C:\Program Files\PA Server Monitor\Databases\ReportCleanup2.db on the new server (since there are no reports to clean up yet). If you really want to keep the existing report HTML files, copy C:\Program Files\PA Server Monitor\Reports from the old to the new computer, and leave the ReportCleanup2.db file alone.
  11. 11. Check to make sure the PA Server Monitor service is running as the user you want it to (by default on a new install it will use Local System).
  12. 12. If Windows Firewall is running, create a rule to open the port PA Server Monitor uses on the new server (port 81 by default).
  13. 13. Be sure to copy the registry value for InstallID under HKEY_LOCAL_MACHINE\software\(Wow6432Node if you have it)\PowerAdminServerMonitor from the old to the new server. This tells the new server that it owns the data in the database.
  14. 14. Under that same registry key on the new server, check the following values and adjust as necessary:
    DatabaseDirectory
    LogFilePath
    ReportDirectory
  15. 15. Start the PA Server Monitor service on the new server.
  16. 16. Copy any license files that you have to the new server. Start the PA Server Monitor Console so the licenses can be activated on the new server. When prompted whether you want to move the license, answer Yes.

Moving or Copying PA Storage Monitor
  1. 1. Install PA Storage Monitor on the new server. Use the same version as the old server. The original Setup.exe file is available on the old server at C:\Program Files\PA Storage Monitor\Install.
  2. 2. If you have Satellites, use Bulk Config on the old server to "Satellites: Set Central Server Hosts" to add the new server's IP address and port it will use (port 8080 by default)
  3. 3. On the old server, go to the Console and choose Configuration > Export Complete Configuration. Export server credentials (and then be very careful with the file!)
  4. 4. On the new server, import the configuration file that was exported above. Delete the configuration file with the server credentials.
  5. 5. Stop the PA Storage Monitor service on both the old and new servers.
  6. 6. Copy the C:\Program Files\PA Storage Monitor\Config directory from the old to the new server
  7. 7. Copy the C:\Program Files\PA Storage Monitor\Databases directory from the old to the new server. You can skip this step if you don't want existing historical performance data.
    If you are using MS SQL Server and the database server is changing as well, disconnect the database, copy it to the new server, and reconnect it.
  8. 8. You may want to copy the SSL certificate in C:\Program Files\PA Storage Monitor\CA to the new server. If you don't, a new one will be generated.
  9. 9. Report settings were copied in step 6 above. Existing report files (the actual HTML files) will be regenerated on their normal schedules, so you should delete C:\Program Files\PA Storage Monitor\Databases\ReportCleanup2.db on the new server (since there are no reports to clean up yet). If you really want to keep the existing report HTML files, copy C:\Program Files\PA Storage Monitor\Reports from the old to the new computer, and leave the ReportCleanup2.db file alone.
  10. 10. Check to make sure the PA Storage Monitor service is running as the user you want it to (by default on a new install it will use Local System).
  11. 11. If Windows Firewall is running, create a rule to open the port PA Storage Monitor uses on the new server (port 8080 by default).
  12. 12. Be sure to copy the registry value for InstallID under HKEY_LOCAL_MACHINE\software\(Wow6432Node if you have it)\PAStorageMonitor from the old to the new server. This tells the new server that it owns the data in the database.
  13. 13. Under that same registry key on the new server, check the following values and adjust as necessary:
    DatabaseDirectory
    LogFilePath
    ReportDirectory
  14. 14. Start the PA Storage Monitor service on the new server.
  15. 15. Copy any license files that you have to the new server. Start the PA Storage Monitor Console so the licenses can be activated on the new server. When prompted whether you want to move the license, answer Yes.

Copying a PA File Sight Installation
  1. 1. Install PA File Sight on the new server. Use the same version as the old server. The original Setup.exe file is available on the old server at C:\Program Files\PA File Sight\Install.
  2. 2. If you have Satellites, use Bulk Config on the old server to "Satellites: Set Central Server Hosts" to add the new server's IP address and port it will use (port 8000 by default)
  3. 3. On the old server, go to the Console and choose Configuration > Export Complete Configuration. Export server credentials (and then be very careful with the file!)
  4. 4. On the new server, import the configuration file that was exported above. Delete the configuration file with the server credentials.
  5. 5. Stop the PA File Sight service on both the old and new servers.
  6. 6. Copy the C:\Program Files\PA File Sight\Config directory from the old to the new server
  7. 7. Copy the C:\Program Files\PA File Sight\Databases directory from the old to the new server. You can skip this step if you don't want existing historical performance data.
    If you are using MS SQL Server and the database server is changing as well, disconnect the database, copy it to the new server, and reconnect it.
  8. 8. You may want to copy the SSL certificate in C:\Program Files\PA File Sight\CA to the new server. If you don't, a new one will be generated.
  9. 9. Report settings were copied in step 6 above. Existing report files (the actual HTML files) will be regenerated on their normal schedules, so you should delete C:\Program Files\PA File Sight\Databases\ReportCleanup2.db on the new server (since there are no reports to clean up yet). If you really want to keep the existing report HTML files, copy C:\Program Files\PA File Sight\Reports from the old to the new computer, and leave the ReportCleanup2.db file alone.
  10. 10. Check to make sure the PA File Sight service is running as the user you want it to (by default on a new install it will use Local System).
  11. 11. If Windows Firewall is running, create a rule to open the port PA File Sight uses on the new server (port 8000 by default).
  12. 12. Be sure to copy the registry value for InstallID under HKEY_LOCAL_MACHINE\software\(Wow6432Node if you have it)\PAFileSight from the old to the new server. This tells the new server that it owns the data in the database.
  13. 13. Under that same registry key on the new server, check the following values and adjust as necessary:
    DatabaseDirectory
    LogFilePath
    ReportDirectory
  14. 14. Start the PA File Sight service on the new server.
  15. 15. Copy any license files that you have to the new server. Start the PA File Sight Console so the licenses can be activated on the new server. When prompted whether you want to move the license, answer Yes.
 
“ With [major competitor's] ping reporting feature I get an email alert for *every* ping failure. Since it's normal to occasionally fail ping (busy network etc) my Inbox was constantly flooded with nuisance alerts. The way you have it implemented I only get the email alert if there is a real problem that needs my attention. ”
Dave G., Progeny Systems Corp, USA more customer quotes...
see customer list...