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.

Moving or Copying PA Server Monitor

Hint: Check each item as you go so none are skipped
1. 1. Installation: 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. Prepare Satellites: 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), along the old server's host and port.
3. 3. Export Configuration: On the old server, go to the Console, connect to Local host, and choose Configuration > Export Complete Configuration. Export server credentials (and then be very careful with the file!)
4. 4. Import Configuration: On the new server, go to the Console, connect to Local host, and choose Configuration > Import Complete Configuration using the configuration file that was exported above. This will move credentials and registry settings to the new server. Delete the configuration file with the server credentials.
5. 5. Stop Old and New Services: Stop the PA Server Monitor service on both the old and new servers. This is being done because copying configuration and data database files while the old service is running can cause database corruption. Quickly copy to a temporary location if you need to quickly get the old server running again.
6. 6. Copy Configuration Databases: Copy the C:\Program Files\PA Server Monitor\Config directory from the old to the new server
7. 7. Copy Database Files: 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 to the new SQL Server.
   
   The old service can be restarted now if necessary.
8. 8. (Optional) Copy SSL Certificate: You may want to copy the SSL certificate in C:\Program Files\PA Server Monitor\CA from the old to the new server. If you don't, a new one will be generated.
9. 9. (Optional) Copy MIB Files: 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. (Optional) Copy Report Files: 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).
11. 11. (Optional) Copy Icon Files: If you added your own custom icon files or icon settings, copy C:\Program Files\PA Server Monitor\Icons and C:\Program Files\PA Server Monitor\icons.ini to the new server.
12. 12. Check Run As Account: Check to make sure the new PA Server Monitor service is running as the user you want it to (by default on a new install it will use Local System).
13. 13. Check Windows Firewall: By default the installer in step 1 created a rule for Windows Firewall. Double-check that it is what you want.
14. 14. Verify InstallID: The registry value for InstallID under HKEY_LOCAL_MACHINE\software\PAServerMonitor should have been copied in step 4 - double check that it is the same.
15. 15. Verify Directories: Under that same registry key on the new server, some directory locations were copied from the old server. Make sure they are where you want them on the new server:
    
    DatabaseDirectory
    LogFilePath
    ReportDirectory
    
16. 16. Start New Service: Start the PA Server Monitor service on the new server. If you don't want any alerts yet, in the Console go to Alerts > Quiet!
17. 17. Copy License File: 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.
18. NOTE: If you had usernames and passwords defined in UserList.txt, you will have to re-enter them on the new server - that file canot be copied to the new server (passwords are encrypted with a machine-specific key).

Hint: Check each item as you go so none are skipped
1. 1. Installation: 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. Prepare Satellites: 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), along the old server's host and port.
3. 3. Export Configuration: On the old server, go to the Console, connect to Local host, and choose Configuration > Export Complete Configuration. Export server credentials (and then be very careful with the file!)
4. 4. Import Configuration: On the new server, go to the Console, connect to Local host, and choose Configuration > Import Complete Configuration using the configuration file that was exported above. This will move credentials and registry settings to the new server. Delete the configuration file with the server credentials.
5. 5. Stop Old and New Services: Stop the PA File Sight service on both the old and new servers. This is being done because copying configuration and data database files while the old service is running can cause database corruption. Quickly copy to a temporary location if you need to quickly get the old server running again.
6. 6. Copy Configuration Databases: Copy the C:\Program Files\PA File Sight\Config directory from the old to the new server
7. 7. Copy Database Files: 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 to the new SQL Server.
   
   The old service can be restarted now if necessary.
8. 8. (Optional) Copy SSL Certificate: You may want to copy the SSL certificate in C:\Program Files\PA Server Monitor\CA from the old to the new server. If you don't, a new one will be generated.
9. 9. (Optional) Copy Report Files: 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. (Optional) Copy Icon Files: If you added your own custom icon files or icon settings, copy C:\Program Files\PA Server Monitor\Icons and C:\Program Files\PA Server Monitor\icons.ini to the new server.
11. 11. Check Run As Account: 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).
12. 12. Check Windows Firewall: By default the installer in step 1 created a rule for Windows Firewall. Double-check that it is what you want.
13. 13. Verify InstallID: The registry value for InstallID under HKEY_LOCAL_MACHINE\software\PAFileSight should have been copied in step 4 - double check that it is the same.
14. 14. Verify Directories: Under that same registry key on the new server, some directory locations were copied from the old server. Make sure they are where you want them on the new server:
    
    DatabaseDirectory
    LogFilePath
    ReportDirectory
    
15. 15. Start New Service: Start the PA File Sight service on the new server. If you don't want any alerts yet, in the Console go to Alerts > Quiet!
16. 16. Copy License File: 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.
17. NOTE: If you had usernames and passwords defined in UserList.txt, you will have to re-enter them on the new server - that file canot be copied to the new server (passwords are encrypted with a machine-specific key).